Add optional service endpoint discovery extension#43
Open
chongkan wants to merge 1 commit into
Open
Conversation
Non-normative extension for service endpoint discovery: - Well-known endpoint pattern for service registries - Inheritance from linked DID via alsoKnownAs - Resolution options (serviceDiscovery, serviceRegistryUrl) - Backwards compatible: disabled by default, core resolution unchanged Addresses w3c-ccg#38 Signed-off-by: Eduardo Chongkan <e.chongkan@gmail.com>
Collaborator
|
This doesn't really make any sense. The point of DID PKH is to be a purely generative DID method. |
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.
Summary
Adds a non-normative Service Endpoint Discovery section as an optional extension to did:pkh resolution.
Two discovery mechanisms
Backwards compatible
serviceDiscovery: falsein resolution options)Why this matters
did:pkh currently has no service endpoints. This means a verifier who resolves a did:pkh cannot discover how to send VP requests, initiate DIDComm messaging, or verify domain ownership. This extension provides a path without changing did:pkh's core design.
Related: #38 | W3C tracking
Signed-off-by: Eduardo Chongkan e.chongkan@gmail.com