chore: elaborate on json-ld context extension#181
Merged
mkollenstart merged 2 commits intoeclipse-dataspace-protocol-base:mainfrom Jun 17, 2025
Merged
Conversation
Co-authored-by: Maarten Kollenstart <maarten.kollenstart@tno.nl>
mkollenstart
approved these changes
Jun 17, 2025
mkollenstart
merged commit 4275593
into
eclipse-dataspace-protocol-base:main
3 checks 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.
What this PR changes/adds
This PR notes the possibility for term collisions between profiles.
Why it does that
There's a non-trivial risk of DSP-profiles defining terms resolving to diverging URIs. This is alluded to in the spec and will be elaborated in the best practices.
Linked Issue(s)
Closes #158
Created follow-up in best practices: eclipse-dataspace-protocol-base/BestPractices#17