-
Notifications
You must be signed in to change notification settings - Fork 554
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
nquads parser creates one context per triple in the default graph #535
Comments
Closely related to #436. We should coordinate solutions. |
You are right, those issues related. So those are two different problems, fixing one requires fixing the other. Indeed, we should coordinate. |
Yes, I agree, this issue for the nquads parser is distinct. (I'll also look into coordinating a solution for RDFLib/rdflib-jsonld#34 with this. I wrote down #436 when I originally hit that. But attempting to resolve all parsing and serializing of datasets at once might have been too much.) |
hmm, one question wrt. the version in which this will be fixed, e.g. by merging #536 : as we use http://semver.org, is this a bug fix only (so 4.2.2) or an actual backwards incompatible change (5.x.x)? |
The current behaviour of the nquads parser is wrong, to a point that no one On Thu, Oct 29, 2015 at 3:43 PM, Jörn Hees notifications@github.com wrote:
|
fixed in #536 |
In nquads, the 4th component (graph id) of each line can be omitted, meaning that the triple belongs to the default graph.
Currently, the nquads parser puts every such triple in a different context, identified by a fresh BNode, which is clearly wrong.
E.g.:
The text was updated successfully, but these errors were encountered: