Skip to content

SPARQL Query Results XML Format Errata #5

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.

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

Closed
2 tasks done
afs opened this issue Feb 9, 2023 · 4 comments · Fixed by #33
Closed
2 tasks done

SPARQL Query Results XML Format Errata #5

afs opened this issue Feb 9, 2023 · 4 comments · Fixed by #33

Comments

@afs
Copy link
Contributor

afs commented Feb 9, 2023

From https://www.w3.org/2013/sparql-errata#rdf-sparql-XMLres

@domel
Copy link
Contributor

domel commented Feb 13, 2023

Regarding the 2005 vs 2007 namespace. Which one do we choose to treat as the appropriate one? The examples in the doc are 2005 but the schemas are 2007.

@afs
Copy link
Contributor Author

afs commented Feb 13, 2023

https://www.w3.org/2005/sparql-results says it replaces 2005/06.

https://www.w3.org/2005/06/sparqlResults says it is replaced by https://www.w3.org/2005/sparql-results.

So I'm not clear what the right answer is or if there is a non-breaking right answer.

We may need to see what deployed systems implement.

It is as if the schema is called https://www.w3.org/2005/sparql-results and the schema defines terms in the XML namespace http://www.w3.org/2007/SPARQL/results#.

http://www.w3.org/2007/SPARQL/results# does not dereference.

@rubensworks
Copy link
Member

I believe the namespace http://www.w3.org/2005/sparql-results# is the desired one.

It may be just the targetNamespace in https://www.w3.org/2007/SPARQL/result.xsd that is incorrect, and may have to be updated to http://www.w3.org/2005/sparql-results#.

@rubensworks
Copy link
Member

Now that #7 has been merged, the only thing that remains, is to update the links to the rnc, rng, and xsd files before this issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants