Skip to content

Namespace of ex: in tests #276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ajnelson-nist opened this issue Feb 25, 2025 · 3 comments · May be fixed by #362 or #390
Open

Namespace of ex: in tests #276

ajnelson-nist opened this issue Feb 25, 2025 · 3 comments · May be fixed by #362 or #390
Assignees
@YoucTagh
Labels
Editorial (would not change implementations) Vocabularies For issues with the RDF files that the WG maintains
Milestone
Phase 1

Comments

@ajnelson-nist
Copy link
Contributor

I just ran grep -R '@prefix ex:' and noticed that the test IRIs are either similar to this...

./tests/sparql/pre-binding/unsupported-sparql-001.ttl:@prefix ex: <http://datashapes.org/sh/tests/sparql/pre-binding/unsupported-sparql-001.test#> .

... or this:

./tests/core/node/xone-duplicate-data.ttl:@prefix ex: <http://example.org/shacl-test/> .

Should these be unified, in domain and path style? The former scopes tests' IRIs nicely, but the latter avoids introducing a domain outside of W3C.
@ajnelson-nist ajnelson-nist added Editorial (would not change implementations) Vocabularies For issues with the RDF files that the WG maintains labels Feb 25, 2025
@nicholascar nicholascar added this to the Phase 1 milestone Mar 4, 2025
@YoucTagh
Copy link
Contributor

If I change all the prefixes to use http://example.com/ns# as in the core document, would that be good for you? @ajnelson-nist @afs @HolgerKnublauch

@YoucTagh YoucTagh self-assigned this Apr 14, 2025
@YoucTagh YoucTagh linked a pull request Apr 14, 2025 that will close this issue
Open
@ajnelson-nist
Copy link
Contributor Author

@YoucTagh Thank you, I think that's the right direction. We apparently have a line-endings issue to work through, though.

@nicholascar nicholascar linked a pull request May 26, 2025 that will close this issue
Open
@TallTed
Copy link
Member

TallTed commented Jun 11, 2025

We apparently have a line-endings issue to work through, though.

I'm not sure what the "line-endings issue" is. Could it be explicitly noted, possibly in its own issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YoucTagh YoucTagh

Labels
Editorial (would not change implementations) Vocabularies For issues with the RDF files that the WG maintains
Projects
None yet
Milestone
Phase 1
4 participants
@TallTed @nicholascar @ajnelson-nist @YoucTagh