1. Current status
Neither identifier currently claims standards-body registration. did:sizuq is not yet listed in the W3C DID Methods collection, and sq is not yet present in the IANA Uniform Resource Identifier (URI) Schemes registry.
| Identifier | Specification | External status |
|---|---|---|
did:sizuq | DID Method Specification | Editor’s Draft · not yet listed in W3C DID Methods |
sq: | URI Scheme Specification | Editor’s Draft · not yet registered by IANA |
2. did:sizuq and W3C DID Extensions
The W3C DID Methods document is a discovery registry for known DID methods. Its own text makes clear that inclusion is not W3C endorsement of a method or its underlying technology. A method specification must define its method-specific syntax and the operations necessary to create, read or resolve, update, and deactivate identifiers in accordance with DID Core requirements.
The did:sizuq draft defines a self-certifying method-specific identifier, deterministic operation serialization, signed state transitions, recovery, deactivation, resolution behavior, security and privacy considerations, and a reproducible test vector.
3. sq: and the IANA URI Schemes registry
The intended registration class for sq is Provisional under RFC 7595. Provisional registration is designed for schemes that are intended for use beyond a private environment even when the scheme is not part of a finalized standard. The registry policy for provisional names is First Come First Served, provided the request is complete and the name is available.
The sq: specification defines syntax, comparison rules, resolution and dereferencing behavior, interoperability considerations, security and privacy considerations, and its relationship to the did:sizuq identity root.
4. What registration means
Registry inclusion primarily prevents naming collisions and gives implementers a stable place to discover the defining specification. It does not certify an application, guarantee adoption, or transfer cryptographic trust to W3C, IANA, a hosted gateway, or the Sizuq project.
For did:sizuq, trust is established by validating the method’s signed operation history. For sq:, the URI remains an identifier; a gateway or service endpoint is transport and must not be treated as proof of control over the identity root.
5. Implementation evidence
A stable public fixture exercises the complete sq: path: fetch a did:sizuq operation history, verify the creation proof and derived identifier, discover the declared resource service, and dereference two resources without changing their canonical identifiers.
A separate dependency-free resolver passes the normative vector and a persistent public pilot history containing rotation, recovery, and deactivation. It shares no runtime code with the primary core implementation, though both implementations are currently maintained by the Sizuq project.
6. Stability policy
Draft revisions may clarify validation rules, error behavior, service profiles, or interoperability requirements. Changes that would reinterpret an already-created DID, alter cryptographic inputs, or change the identity meaning of an existing sq: URI require an explicit version transition rather than a silent change in semantics.
Once a stable version is declared, the goal is that independently written implementations can derive the same DID state from the same operation history and preserve the same canonical sq: identifier across compatible services.