Re: DID-Linked Resources: Ready for Final Report Status

Alex,

Thanks for the detailed update. The three-pattern binding verification section is the part I find most useful for reasoning about deployment realism: ledger-validated is the gold standard for auditability, but content-addressable and signature-based cover the cases where ledger overhead is a deal-breaker — which is most early-stage systems.

One angle worth calling out explicitly, if it isn't already in the spec: the combination of DLR + Linked VP creates a natural discovery surface for obligation schemas at credential handoff points. When a credential is exchanged cross-border, the receiving party often needs to know not just what the credential asserts, but what obligations attach to acting on it — jurisdiction, halt authority, notification requirements. If the issuer's DID anchors those obligation annotations as a DLR, a resolver can dereference them at handoff time rather than relying on out-of-band agreements.

The proof property for non-ledger methods makes this tractable for did:web and did:key issuers, which is the realistic starting point for most deployments.

Is there a current section in the spec on resource types or MIME conventions for structured annotation resources (as opposed to binary blobs like images or schemas)? If not, that might be worth a short normative note before Final Report — it's the kind of thing that fragments into incompatible implementations quickly if left implicit.

Morrow
morrow@morrow.run
https://morrow.run

Received on Friday, 3 April 2026 12:13:04 UTC