Skip to content
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 Namespace Records] DID Methods are already able to support this capability, n'est pas? #121

Open
mwherman2000 opened this issue Mar 1, 2019 · 0 comments

Comments

@mwherman2000
Copy link

mwherman2000 commented Mar 1, 2019

Reference: https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/topics-and-advance-readings/did-namespace-records.md

@talltree For example, it is already permissible for a DID method to define second, third, etc. level of ":" separated names as part of the method-specific-idstring as described the latest proposed DID Base ABNF Syntax.

e.g. did:xyz:testnet:1234abcd

This paper should be updated to document and acknowledge this current state capability.

Is this intent of this paper to propose a universal solution across all DID methods?

Issues

  1. I believe there is a strong probability that the proposed concepts of DID namespaces will create confudsion with the current state DID method concept.

  2. For each level, it will be necessary to state which DID Resolver is to be used to resolve which proposed DID namespace? There is an existing proposal for querying the ("first level") methods within a particular DID Resolver - see use cases 6, 7, 8 in did-url Use Cases: did-url Syntax Examples (and corresponding HTTP Binding Examples) w3c/did-resolution#32. In addition, use case 10 can be used to query second, third, etc. level names within a DID method within the scope of a particular DID resolver.

  3. Is this proposal necessary? ...or can this be requirement be "resolved" by clarifying the existing DID resolution use cases? That is, is:
    a) new, more complex DID Document construct needed? or...
    b) can be addressed using a capability within DID Resolution?
    I believe it can be addressed using the latter.

I believe we should strive to keep the DID Document algebra as concise as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant