feat: introduces optional JSON-LD context for management API #4470
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
wolf4ood
added
enhancement
wolf4ood
force-pushed
the
feat/4466_bundle_management_context
branch
4 times, most recently
from
c54fb37
to
25f3071
Compare
wolf4ood
requested review from
ndr-brt,
bscholtes1A,
jimmarino,
paullatzelsperger,
ronjaquensel and
juliapampus
as code owners
paullatzelsperger
approved these changes
Sep 16, 2024
...-api-test-runner/src/test/java/org/eclipse/edc/test/e2e/managementapi/SerdeEndToEndTest.java
Outdated
Show resolved
Hide resolved
wolf4ood
force-pushed
the
feat/4466_bundle_management_context
branch
from
2b2f122
to
9eacd54
Compare
ndr-brt
approved these changes
Sep 16, 2024
This was referenced Sep 16, 2024
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.
What this PR changes/adds
introduces optional JSON-LD context for management API
Why it does that
improves JSON-LD objects in management APIs
Further notes
management-api-json-ld-contextextensionmanagement-context-v1.jsonldmoved in thejson-ldextension@vocabandedcnamespace definition are not loaded in the default scope (*) but each scope registers them@vocabis still possible with theedc.jsonld.vocab.disableconfig. If it's disabled the registerNamespace implementation will skip itTo activate the JSON-LD context in the management API set
edc.management.context.enabled=trueSince the @vocab and
edcprefixes are removed from the default scope but registered in each scope separately,this is a breaking change only for people that, when extending EDC uses the JsonLd service and do not specify the scope when compacting., or for extensions that use a custom scope but do not register
@vocabandedcdirectly.Linked Issue(s)
Closes #4466
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.