A development catalogue for DID method visibility — not a registry, not an endorsement
Select a use case from the list
Every method should self-assess. No more meaningless abandoned entries. The form ensures ecosystem discovery, cooperation, and prevents blind duplication.
| Level | Name | What It Means | Gate | Where |
|---|---|---|---|---|
| L0 | Listed | Legacy entry — name exists but no self-assessment. Should not exist going forward. | Pre-form era | This repo |
| L1 | Self-Assessed | Completed the Self-Assessment form. Understands the ecosystem, verified no blind duplication, documented use case and requirement coverage. Value: planning and understanding. | Form completed | did-extensions |
| L2 | PR Submitted | Author believes the method adds value after L1 discovery. Opens PR with JSON + Markdown spec. Community volunteers and watchlist approvers begin review. | PR opened | did-extensions |
| L3 | Under Review | PR open and under community review — comments, fixes, overlap justification in progress. Waiting for merge approval. Green light to proceed to Rubric once merged. | PR under review (~monthly batches) | did-extensions |
| L4 | Rubric-Reviewed | Formal standardization review. DID Rubric evaluation across 36 criteria in 8 categories by the working group. | WG evaluation (~yearly) | did-rubric (external) |
L1 → L2: Self-assessment is immediate. Once complete, you can open a PR at any time.
L2 → L3: PRs are reviewed in monthly batches. Community volunteers and approvers check: valid JSON, Markdown spec, overlap justification, and requirement coverage. Comments and fixes happen during this phase — this IS the conformance process.
L3 → L4: Methods under review that get merged can request Rubric evaluation at did-rubric. The WG evaluates ~1 method per year.
Important: Being listed or accepted creates no endorsement or obligation. This is a development catalogue for visibility and ecosystem coordination.
How well are W3C use cases covered by methods at L1+ (self-assessed or higher)?
Percentage of catalogued methods that cover each W3C requirement (any level).
Identifies underserved areas where new DID methods would add the most value to the ecosystem.
Active (L1+) methods per region.
Development lifecycle stages of active methods.
Cells show how many L1+ methods fully cover each requirement for each use case. Red = zero coverage, yellow = weak, green = strong.