-
Notifications
You must be signed in to change notification settings - Fork 154
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
Absolute context is made relative #304
Comments
I still believe this is an issue, but we are switching our processing to using the external URI when parsing the incoming RDF and then translating the subsequent graph. Thanks. fcrepo/fcrepo#1847 |
@whikloj thx for reporting this issue. Apologizing for the late response.
(https://json-ld.org/spec/latest/json-ld-api/#dfn-base-iris) and
(https://www.w3.org/TR/json-ld11/) So the remote context you gave ( |
If the remote context is not relative and seems to be a http URI don't prefix the base IRI to it. The remote context is not validated nor tested if it's resolvable. It's just tested if it's not a relative URI - which is totally possible and would, in conjunction with a base IRI, made into valid remote context. See #304.
If the remote context is not relative and seems to be a http URI don't prefix the base IRI to it. The remote context is not validated nor tested if it's resolvable. It's just tested if it's not a relative URI - which is totally possible and would, in conjunction with a base IRI, made into valid remote context. See #304.
Fix in master. Should come into next release. |
I'll say up front that my Json-LD spec fluency is not strong. Anyways...
We are using opaque IRI IDs internally and transforming them to URIs when returned to users to avoid storing hostnames.
It appears like the changes (perhaps in response to #232) is causing us some trouble.
I wrote a small class based on the area of Jena that seemed to be failing.
https://gist.github.com/whikloj/29f61a883dd14cb0cf17e2f292621957
My two tests are as follows.
With regular URI as the it works
With an opaque IRI is does not
This might be faulty understanding on our or Apache Jena's side, but it seems like using an IRI does not work as you are only expecting URIs. So I thought I would raise it here first. Thanks
The text was updated successfully, but these errors were encountered: