decentralized-identity / decentralized-identity/did-methods
Criteria to be proposed should have at least 3 did methods that support it before being approved
- Dominant language
- No language data
- Stars
- 21
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
As discussed on the WG call on 18-Dec. We would like to avoid criteria that extensively promotes the unique features of a single did method.
I would like propose that **criteria should have at least 3 did methods with implementations in production** that support it before being admitted into the list.
Therefore each criteria should clearly point to 3 existing did methods that implement it before it is approved. This should counter balance some of the "did method bias" that inevitably each of us DID Method Designers has, and promote criteria that can be broadly applicable to a few did methods.
Support for a criteria, can be a boolean "complies" or "doesn't comply" for a given did method. But in other cases can also be quantifiable value, example "did method meets 60% of this X criteria" OR "this DID method has been benchmarked and tested at 100 txn/sec and 10mil users".
Contributor guide
Research direction
Start by reviewing the 18-Dec WG call discussion and the current criteria list, neither of which is linked or named in the issue. Clarify how production support by three DID methods should be evidenced, then document the approval rule and the required method-by-criteria support details.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100