-
Notifications
You must be signed in to change notification settings - Fork 1
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
Escaping issue? #3
Comments
Hi, the good news is: I can reproduce the problem with the following model: @prefix dc: <http://purl.org/spar/datacite/> .
@prefix doi: <https://doi.org/> .
@prefix : <http://example.org#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
:something a :publication ;
rdfs:label "Paper title" ;
dc:hasIdentifier doi:10.1137\/1.9781611970937 . turtle-formatter and owl-cli also use Jena as an RDF library, which provides multiple ways to parse a file. As it did not use the same method as |
After some investigation, it seems this is caused by Jena's internal RDF parsers handling escapes differently. The RIOT parser which handles this correctly is added automatically via service loading when |
@renefritze The fix for the broken parsing is done. Furthermore, serialization of escapes was broken as well (see #4). Both fixes are in the just released owl-cli version 1.2.0. |
Excellent, thank you. |
I want to format a Turtle file that looks something like this:
The forward slash escaping is necessary for us to pass validation with
riot
from the Jena package. Inputting above text intoowl write
I get (Where line/col matches the slash position)Is this an issue with the input parser? Is
riot
wrong in validating this?The text was updated successfully, but these errors were encountered: