A DID method is a small specification document, technically. But the act of submitting a DID method to the W3C registry, of having it reviewed by the community of identity standards practitioners, of having it accepted into the public list — this is more than a technical act. It is a form of community-anchored consecration.
The lineage matters. The x.500 directory standards of the 1980s established that identity could be represented as structured data with a registry. The LDAP refinements of the 1990s made the architecture deployable at internet scale. OAuth and OpenID Connect in the 2000s established federation as the dominant pattern for cross-platform authentication. The W3C DID Core specification of the 2020s represents the next step: a registry of methods rather than a registry of identifiers, allowing the architecture to support many different anchoring strategies.
Each step in this lineage required two things. A technical innovation that addressed a previously-unsolved problem. And community acceptance through the standards bodies — the rounds of review, the implementation experience, the working group consensus that a contribution belongs in the lineage.
The W3C DID Method Registry process embodies the second of these. It is not a fast process. It is not a marketing event. A method is submitted, reviewed by working group members and the broader community, revised based on feedback, and eventually accepted (or not) based on whether the contribution meets the criteria the working group has developed.
The criteria are substantive: does the method comply with DID Core, does the security analysis hold up, does the privacy analysis hold up, does the conformance documentation match what implementations actually do. The working group's review is rigorous because the registry's value depends on the rigor; a registry full of poorly-reviewed methods would be useless.
When a method is accepted, what's been accepted is not just technical conformance. The community of standards practitioners has implicitly agreed that the method belongs in the lineage. The acceptance carries weight because the practitioners are reputable, the process is transparent, and the criteria are public.
The civilizational meaning of this kind of consecration. Across history, secular societies have developed institutions for accrediting work that meets community standards. Academic peer review, professional licensing, building code compliance, certificate authority audits. Each of these is a process for the community to say "this work meets our shared standards; we accept it."
The W3C DID Method Registry serves a similar function for identity infrastructure. It is the community's mechanism for accrediting which methods belong in the shared standards lineage. The acceptance is not a one-time event; it carries with it ongoing accountability to the community's standards.
For Solidus, the submission of did:solidus to the W3C DID Method Registry is participation in this process. We are not asking for marketing approval; we are asking for technical and community review. The first round of review produced feedback; we revised; subsequent rounds have continued the process. Whether and when the method is accepted depends on the working group's assessment of whether the contribution meets the standards.
The deeper meaning of "registered" — when it eventually happens for did:solidus or any peer method — is the community's acknowledgment that the method belongs in the lineage. The acknowledgment matters more than the technical badge; the badge is a side-effect of the deeper acknowledgment.
This is one of the durable values of standards bodies. The W3C, the DIF, the IETF, the ISO. Each represents a community-anchored accreditation function that has been developed over decades. The work the standards bodies do is patient, technical, often invisible to the broader public. The civilizational value is real.
The reader who comes to this article asking "why does the W3C registry matter" gets the answer: because the registry is the community's mechanism for accrediting which methods belong in the standards lineage, and the lineage is the foundation of credible identity infrastructure at internet scale.
For the broader civic conversation about identity infrastructure, support for the standards bodies is the durable contribution. Not advocacy for any specific vendor; not advocacy for any specific method. Advocacy for the institutions that accredit the work and maintain the lineage. Solidus is one of many contributors to those institutions. The institutions matter more than any individual contributor.
The next century of digital coordination will rely on identity infrastructure that traces back to the standards work being done in this decade. The W3C DID Method Registry, the DIF working groups, the IETF protocol drafts — these are the durable lineage. The methods that survive will be the methods that earned community acceptance through these institutions.
Top comments (0)