N3Parser: support escape sequences in local names #557
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to RDF 1.1 Turtle specification, the grammar accepts local names as production node, for ex
foaf:name
This local name can contain escape sequences:
which are enumerated as follows:
However, when trying to parse the following turtle with rdflib,
Source: Solid Data Interoperability Panel
The following error is returned:
I tracked the issue in the N3 parser in the following location. It is because the method breaks out of the loop when it finds the notNameChar
\
instead of considering an escape sequence.The following code change may be worth further investigation, as I am not sure what side-effect this may have.