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
When compacting a JSON-LD with a @base context, I remarked different behaviour for URIs and URNs:
@base
URIs With a "@base": "http://example.com", a "@id":"http://example.com/nosec_sc" becomes "@id": "nosec_sc", which is expected.
"@base": "http://example.com"
"@id":"http://example.com/nosec_sc"
"@id": "nosec_sc"
Playground link
URNs With a "@base": "urn:something/", a "@id":"urn:something/no_sec" remains the same after compaction though we would expect a "@id":"no_sec".
"@base": "urn:something/"
"@id":"urn:something/no_sec"
"@id":"no_sec"
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When compacting a JSON-LD with a
@basecontext, I remarked different behaviour for URIs and URNs:URIs
With a
"@base": "http://example.com", a"@id":"http://example.com/nosec_sc"becomes"@id": "nosec_sc", which is expected.Playground link
URNs
With a
"@base": "urn:something/", a"@id":"urn:something/no_sec"remains the same after compaction though we would expect a"@id":"no_sec".Playground link
The text was updated successfully, but these errors were encountered: