-
Notifications
You must be signed in to change notification settings - Fork 165
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
IRI with space #780
Comments
I assume this is related to #69 (and that there is no strict checking on generating/writing IRIs because it impacts performance) |
Also related to #712 |
Signed-off-by: James Leigh <james.leigh@ontotext.com>
Signed-off-by: James Leigh <james.leigh@ontotext.com>
Signed-off-by: James Leigh <james.leigh@ontotext.com>
Importing a ttl file with the TURTLE format, line 1 of which is this: |
I now believe that my errors reported here were based on inappropriate use of the APIs. By switching to Model-based parsing before adding to the repo, all errors disappeared. |
Fix #780: Validate IRI by default when parsing RDF files
Signed-off-by: James Leigh <james.leigh@ontotext.com> Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
…-rdf4j#780-validate-iri Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
Signed-off-by: James Leigh <james.leigh@ontotext.com> Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
Signed-off-by: James Leigh <james.leigh@ontotext.com> Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
Signed-off-by: James Leigh <james.leigh@ontotext.com> Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
…4j#780-validate-iri Fix eclipse-rdf4j#780: Validate IRI by default when parsing RDF files Signed-off-by: Heshan Jayasinghe <shanujse@gmail.com>
File
input.ttl
contains IRI with encoded space:The Turtle parser is able to read this IRI (with encoded spaces) as a valid IRI.
However Turtle writer does not encode the space on output, resulting in:
When we try to load this statement the parser fail with:
A simple program can be utilized to reproduce this error:
This problem also propagates to the querying remote SPARQL endpoints.
The same issue can be experienced when using N-Triples, however for JSON-LD and RDF/XML no error is given.
The comment in TurtleParser suggest that the \n and similar (spaces?) should be handled as errors.
It's not clear what is an intended behaviour.
Tested with rdf4j 2.2 .
The text was updated successfully, but these errors were encountered: