Provide an option to allow (and ignore) additional keys in a JSON-LD document#63
Merged
Raphael-Gazzotti merged 1 commit intoopenMetadataInitiative:pipelinefrom Oct 2, 2025
Conversation
Raphael-Gazzotti
approved these changes
Oct 2, 2025
Raphael-Gazzotti
merged commit 09b53e0
into
openMetadataInitiative:pipeline
1 check passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At present, if any additional keys are found in a JSON-LD document, a NameError is raised.
This PR adds an option
ignore_unexpected_keysto theload()method to ignore such additional keys. The default is still to raise the NameError.The motivation is to handle openMINDS JSON-LD documents generated by other tools, such as the EBRAINS Knowledge Graph, which adds extra keys in non-openMINDS namespaces, such as "http://schema.org/identifier".