-
Notifications
You must be signed in to change notification settings - Fork 64
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
[wg/did] Document how current implementers interop using DID-core-v1 #438
Comments
A charitable restatement of the 2021 formal objection about interoperability is that in many protocols, after you read one specification you know what to do. But in this decentralized family of specifications, independent implementations need to read a specification for every DID Method that they handle natively, and the DID-core specification implies trusting a DID Resolver to get DID Documents from DID Methods that are handled using a third party service, instead of handled natively. What that means is that handling specific DID Methods is a business decision. In that, it is kind of like pointing your browser to gopher://gopher.quux.org:70/1/ in that leading browsers will not recognize the valid URL and instead point you at search results. Are these browsers failing to implement a Web standard? Yes, but they're not confused about it. Similarly, there will be DID Methods that your browser will not resolve into a DID Document, even with the help of a DID Resolver. They will not implement the whole family of protocols, and they will not be confused about it. |
The following chart would help visualize these issues. It would be reasonable to add fields like these to the DID Method registry, or provide a way to focus on which DID Methods have independent evaluations (as might be found in the DID Rubric) informing implementors about the issues:
|
Do you mean "it should be documented in the charter" (which is how I read your text literally, or "the charter should say that the WG will document it" (which seems more reasonable)? |
The charter was announced |
A good recommendation heard in the DID-WG charter discussion:
(note: I can edit attribution if speaker approves)
The text was updated successfully, but these errors were encountered: