We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
Currently when a prefixed IRI has an escaped non-alphanumeric character, the IRI gets parsed incorrectly.
For example, this query:
PREFIX a: <a:a> Select * where { bind(a:a\/s as ?x) }
Results to this JSON with the value of the IRI being a:aa\\/s:
a:aa\\/s
{ "queryType": "SELECT", "variables": [ {} ], "where": [ { "type": "bind", "variable": { "termType": "Variable", "value": "x" }, "expression": { "termType": "NamedNode", "value": "a:aa\\/s" } } ], "type": "query", "prefixes": { "a": "a:a" } }
But the value of the IRI should be a:aa/s:
a:aa/s
{ "queryType": "SELECT", "variables": [ {} ], "where": [ { "type": "bind", "variable": { "termType": "Variable", "value": "x" }, "expression": { "termType": "NamedNode", "value": "a:aa/s" } } ], "type": "query", "prefixes": { "a": "a:a" } }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Currently when a prefixed IRI has an escaped non-alphanumeric character, the IRI gets parsed incorrectly.
For example, this query:
Results to this JSON with the value of the IRI being
a:aa\\/s
:But the value of the IRI should be
a:aa/s
:The text was updated successfully, but these errors were encountered: