-
Notifications
You must be signed in to change notification settings - Fork 555
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
Unexpected recursive context inclusion exception #2778
Comments
The problem is that fails1.jsonld.json references both https://w3id.org/ro/crate/1.1/context and https://w3id.org/ro/terms/workflow-run, but https://w3id.org/ro/terms/workflow-run itself also references https://w3id.org/ro/crate/1.1/context.
|
What I wonder is why encountering the same context a second time needs to raise an exception at all? Why can't we simply skip it? I tried replacing the exception with a skip, |
Hi, I'm involved into https://github.com/ResearchObject community, and I'm writing some code to parse RO-Crate JSON-LD representation, in order to perform further processing. Meanwhile I was doing some tests using RDFLib 7.0.0, I guess I have uncovered a corner case bug in its embedded JSON-LD processor plugin, and I have been able to narrow the test code and contents which fire it.
Using next code:
works as expected with next attached toy files:
(single context, it is the URI to the current RO-Crate context)
(list of contexts, being the URI to the current RO-Crate context and an inline term)
But it fails with next one:
(list of contexts, one it is the URI to the current RO-Crate context and the second is the URI to a CSV of term definitions)
raising
Surprisingly, next ones work (at the beginning I thought it was an issue with the current context):
(list of contexts, one it is the URI to the current RO-Crate context and the second is the URI to the previous RO-Crate context)
(list of contexts, one it is the URI to the previous RO-Crate context and the second is the URI to a CSV of term definitions)
The text was updated successfully, but these errors were encountered: