Skip to content
DID.is Documentation

Normative Standards Registry & Bibliography

Authoritative Normative Bibliography

Section titled “Authoritative Normative Bibliography”

1.1 Authoritative Normative Bibliography

Section titled “1.1 Authoritative Normative Bibliography”

The following registry establishes the formal, normative reference baseline for DID.is. Every cryptographic algorithm, data model transformation, wire protocol exchange, and error serialization in resolver-core is bound to these published specifications.

1.1.1 W3C Decentralized Identity & Verifiable Credentials

Section titled “1.1.1 W3C Decentralized Identity & Verifiable Credentials”
  • [W3C DID Core 1.0]
    Decentralized Identifiers (DIDs) v1.0: Core Architecture, Data Model, and Representations
    Status: W3C Recommendation (2022-07-19)
    Canonical URI: https://www.w3.org/TR/did-core/
    Normative Scope: Abstract data model, verification methods (id, type, controller, publicKeyMultibase, publicKeyJwk), verification relationships (authentication, assertionMethod, keyAgreement, capabilityInvocation, capabilityDelegation), production representations (application/did+json, application/did+ld+json).
  • [W3C DID Core 1.1]
    Decentralized Identifiers (DIDs) v1.1
    Status: W3C Candidate Recommendation Snapshot (2024-04-11)
    Canonical URI: https://www.w3.org/TR/did-core-1.1/
    Normative Scope: Context namespace evolution (https://www.w3.org/ns/did/v1.1), dereferencing parameters (service, relativeRef, versionId, versionTime), representation metadata profiles.
  • [W3C DID Resolution v1.0]
    DID Resolution (v1.0)
    Status: W3C Candidate Recommendation Draft (2024-03) / W3C CCG Working Draft
    Canonical URI: https://w3c.github.io/did-resolution/
    Normative Scope: Abstract resolve / dereference algorithm, ResolutionMetadata, DocumentMetadata, media type content negotiation, exact document ID verification (doc.id == requested_did), and error taxonomy.
  • [W3C VC Data Model 2.0]
    Verifiable Credentials Data Model v2.0
    Status: W3C Recommendation (2024-05-16)
    Canonical URI: https://www.w3.org/TR/vc-data-model-2.0/
    Normative Scope: Core credential data model, context URI https://www.w3.org/ns/credentials/v2, validFrom and validUntil timestamps, single-subject integrity constraints, VC-JOSE securing mechanism profile.
  • [W3C VC Data Model 1.1]
    Verifiable Credentials Data Model v1.1: Expressing Verifiable Information on the Web
    Status: W3C Recommendation (2019-11-19, amended 2022-03-03)
    Canonical URI: https://www.w3.org/TR/vc-data-model/
    Normative Scope: Legacy credential syntax, context URI https://www.w3.org/2018/credentials/v1, issuanceDate and expirationDate, legacy VC-JWT claim mirroring (vc wrapper claim, sub, iss, nbf, exp).
  • [W3C VC Data Integrity 1.0]
    Verifiable Credential Data Integrity 1.0
    Status: W3C Recommendation (2024-05-16)
    Canonical URI: https://www.w3.org/TR/vc-data-integrity/
    Normative Scope: Abstract cryptographic proof framework, DataIntegrityProof syntax, canonicalization transformation pipeline, proof configuration separation, unchained proof assertions.
  • [W3C Data Integrity EdDSA Cryptosuites v1.0]
    Data Integrity EdDSA Cryptosuites v1.0
    Status: W3C Recommendation (2024-05-16)
    Canonical URI: https://www.w3.org/TR/vc-di-eddsa/
    Normative Scope: eddsa-jcs-2022 cryptosuite specification, Ed25519 multikey parsing, SHA-256 combined transformed hashing, strict RFC 8032 signature verification (verify_strict).
  • [W3C Data Integrity ECDSA Cryptosuites v1.0]
    Data Integrity ECDSA Cryptosuites v1.0
    Status: W3C Recommendation (2024-05-16)
    Canonical URI: https://www.w3.org/TR/vc-di-ecdsa/
    Normative Scope: ecdsa-jcs-2019 cryptosuite specification with NIST P-256 (secp256r1), lower-$s$ signature normalization, SEC1 point validation.
  • [W3C Bitstring Status List v1.0]
    Bitstring Status List v1.0
    Status: W3C Recommendation (2024)
    Canonical URI: https://www.w3.org/TR/vc-bitstring-status-list/
    Normative Scope: BitstringStatusListEntry, multibase base64url encoded bitstrings ('u' prefix), Gzip decompression bounds, 131,072-bit minimum sizing, fail-closed revocation authority.

1.1.2 IETF Standards Track Specifications

Section titled “1.1.2 IETF Standards Track Specifications”
  • [RFC 8785]
    JSON Canonicalization Scheme (JCS)
    Status: IETF Standards Track (June 2020)
    Canonical URI: https://www.rfc-editor.org/rfc/rfc8785
    Normative Scope: Lexicographical UTF-16 code unit property sorting (§3.2.3), whitespace elimination (§3.2.1), IEEE-754 binary64 float formatting via Ryu algorithm (§3.2.2.3), subnormal float handling, and deterministic JSON serialization.
  • [RFC 7515]
    JSON Web Signature (JWS)
    Status: IETF Standards Track (May 2015)
    Canonical URI: https://www.rfc-editor.org/rfc/rfc7515
    Normative Scope: Compact serialization (header.payload.signature), detached signature verification, JOSE algorithm profiles (EdDSA, ES256, ES256K), mandatory crit rejection, rejection of alg: none.
  • [RFC 7519]
    JSON Web Token (JWT)
    Status: IETF Standards Track (May 2015)
    Canonical URI: https://www.rfc-editor.org/rfc/rfc7519
    Normative Scope: Standard registered claims (iss, sub, aud, exp, nbf, iat, jti), NumericDate temporal evaluation, clock skew boundaries ($\pm 60\text{s}$).
  • [RFC 7638]
    JSON Web Key (JWK) Thumbprint
    Status: IETF Standards Track (September 2015)
    Canonical URI: https://www.rfc-editor.org/rfc/rfc7638
    Normative Scope: SHA-256 base64url thumbprints over required canonical JWK members for EC (crv, kty, x, y) and OKP (crv, kty, x) keys.
  • [RFC 9457]
    Problem Details for HTTP APIs
    Status: IETF Standards Track (July 2023, Obsoleting RFC 7807)
    Canonical URI: https://www.rfc-editor.org/rfc/rfc9457
    Normative Scope: Machine-readable error response envelopes (application/problem+json), standard fields (type, title, status, detail, instance), and domain extensions (code, resolution_metadata).

1.1.3 Autonomous Agent Protocols & Community Specifications

Section titled “1.1.3 Autonomous Agent Protocols & Community Specifications”
  • [MCP]
    Model Context Protocol (MCP)
    Status: Open Specification (Anthropic / Model Context Protocol Organization)
    Canonical URI: https://modelcontextprotocol.io/
    Normative Scope: Streamable HTTP Transports across Current Stateless (2026-07-28) and Legacy Session Handshake (2025-11-25) profiles; JSON-RPC 2.0 message framing; JCS SHA-256 tool fingerprinting; dual-tier declared vs. heuristic risk classification; Unicode and prompt injection safety guards.
  • [LF A2A]
    Agent-to-Agent (A2A) Protocol v1.0.0
    Status: Linux Foundation Open Specification (v1.0.0)
    Canonical URI: https://github.com/a2aprotocol/spec
    Normative Scope: Autonomous agent card discovery via /.well-known/agent-card.json, interface binding declarations (JSONRPC, GRPC, HTTP+JSON), detached JWS card signature verification, jku JWK Set retrieval.
  • [DIF did:webvh]
    did:webvh Method Specification v1.0
    Status: Decentralized Identity Foundation (DIF) Community Specification
    Canonical URI: https://identity.foundation/didwebvh/
    Normative Scope: Verifiable state transition history log (did.jsonl), SHA-256 Base58BTC SCID generation, pre-rotation key commitments (nextKeyHashes), witness threshold verification.
  • [DIF did:jwk]
    The did:jwk Method Specification
    Status: Decentralized Identity Foundation (DIF) Community Specification
    Canonical URI: https://identity.foundation/did-jwk/
    Normative Scope: Deterministic DID document generation from base64url-encoded JWK; strict private key member rejection.
  • [W3C CCG did:key]
    The did:key Method v0.9
    Status: W3C Credentials Community Group (CCG) Report
    Canonical URI: https://w3c-ccg.github.io/did-method-key/
    Normative Scope: Multibase/Multicodec public key derivation, keyAgreement isolation for X25519, curve point decompression.
  • [W3C CCG did:web]
    Target did:web Method Specification
    Status: W3C Credentials Community Group (CCG) Report
    Canonical URI: https://w3c-ccg.github.io/did-method-web/
    Normative Scope: Domain to HTTPS URL resolution, anti-evasion rules, document ID exact matching.
  • [DID.is Delegation Receipt v1]
    DID.is Delegation Receipt v1
    Status: Experimental Specification (DID.is Proprietary)
    Canonical URI: docs/STANDARDS_REFERENCE.md#53-didis-delegation-receipt-v1-experimental-specification–didis-proprietary
    Normative Scope: Compact JWS capability delegation tokens (typ: didis-delegation+jwt), SHA-256 prf parent hash linkage, monotonic capability attenuation, DAG acyclicity enforcement.