-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DID method governance #6
Comments
please don't tell me what methods i should support. That said governance specs and audited providers will be required in many applications. |
You're right. I think the spec should definitely not contain instructions on what "official" DID methods a client "must" support, that wouldn't be very decentralized :) But the spec could contain some basic thoughts and guidelines on how one can make a decision what DID method(s) to support in a DID resolver. Some people would want to agree on supporting a shared set of methods (for interoperability), while others would support their own preferred DID method(s). |
Looking at this older issuer.. The main DID spec has some thoughts on method governance: https://w3c.github.io/did-spec/#unique-did-method-names. Also, the DID WG charter says it will "Establish a deterministic mapping between DID method identifiers and the resolution process used to resolve that DID method." So I am not sure if we need to say anything about this in the DID Resolution spec. I guess we can keep the issue open just in case.. |
This spec should include guidelines or pointers to information on which DID methods a DID resolver should support, or how the list of supported DID methods can be customized or changed dynamically.
E.g. explain the DID method registry:
https://w3c-ccg.github.io/did-method-registry/
Also see this mailing list thread:
https://lists.w3.org/Archives/Public/public-credentials/2018Jun/0119.htmlt
The text was updated successfully, but these errors were encountered: