JSON-LD @Context postprocessing #33
Merged
Conversation
This file contains 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
uv can take care of fetching the right version of Python and set up a virtualenv hiding everything behind `uv run main.py`
|
Could you please try to rebase your patchset on top (and confirm that works for you as well?) |
…ing-description-toolchain-tmp into jsonld-postprocessing
yes it works. |
… original LinkML types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
LinkML JSON-LD Context generator does not currently generate the
@containerkeyword. The@containervalues can be[@list, @set, @language, @indexl]. This PR updates the LinkML schemas and addresses the limitation with post-processing.Also, handling default_types and exactly_one_of expressions are not supported in the generation, with post processing it is handled here.