feat: add did doc registration and align well-known version endpoint #122
Conversation
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
jimmarino
approved these changes
Feb 21, 2025
mkollenstart
approved these changes
Feb 27, 2025
mkollenstart
merged commit 7db54af
into
eclipse-dataspace-protocol-base:main
1 check passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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
The PR changes the definition of the well-known http versioning endpoint in a non-compatible manner and adds (building on that) normative statements how to publicize a
CatalogServicein a did document.Why it does that
Reasons are laid out in the ticket.
Further notes
The did-core standard was added as an informative reference. There are no automated tests for json/json-ld-compatibility and deserialization as those are concerns for the did-spec.
Linked Issue(s)
Closes #44