w3c
META PROPOSAL: Attestation of unique DID Method names: allow for multiple approaches
@msporny proposed restricted approach here: https://github.com/w3c/did-extensions/issues/595
In this Meta Proposal, I want to suggest that the DID method registration section in the spec be modified to support more than one attestation of unique DID Method names approaches that covers the following objectives:
- Removes the burden from the reviewers
- Removes the W3C from having to arbitrate DID method uniqueness issues
- Produces a tangible result in terms of authenticating/attesting to the uniqueness of new DID Method registration applications
The idea is to support, in the specification, more than one trivially easy-to-access attestation of unique DID Method names approach - with the goal of giving registrants/controllers at least a couple choices that they can choose from based on time, effort, and cost. For example, tradmarking is costly especially for registrants who do not have in-house legal council - more cost effective solution(s) are needed. The wording of the specification cannot be prejudiced for or against any registrant. In addition, a DID Method name may not be trademarkable: https://github.com/w3c/did-extensions/issues/595#issuecomment-2494098759
So what's on the table in terms of approaches to attestation (in order of strength: effectiveness, cost, time, and effort):
- DNS Registration: Leveraging what is already available using Internet Doman Name System (DNS) domain name registration. Examples of such an approach can be found in https://github.com/w3c/did-extensions/issues/590
- Registered trademarks per the concepts outlined here: https://github.com/w3c/did-extensions/issues/595
- Unregistered trademarks
- No attestation of uniqueness supplied in the application
NOTE: The implication of point 4 is that we add a field to the DID Method Name registration file to specify the registrant's attestation of unique DID Method names approach/evidence. This can be a simple text field with a link to the domain registration, a trademark statement, etc. An empty or missing field would default to class 4: No attestation of uniqueness provided. This field can also be used to ajudicate new applications that have or claim to have a stronger authentication. "attestation" is the proposed name of the field.
Q: More suggestions for additional attestation of unique DID Method names approaches? ...that would be simple in terms of effort, time and cost for the registrant and as well the reviewers and the W3C?
Other thoughts?
attestation is one suggestion for the name of this new field in a DID Method registration JSON document.
