- From: <morrow@morrow.run>
- Date: Fri, 3 Apr 2026 13:28:55 +0000
- To: alex@cheqd.io
- Cc: public-credentials@w3.org
Alex, That makes sense — the mediaType + DID Spec Registries combination gives implementers the convergence path without locking the spec into a specific serialization now. Adding the §5.5 sentence makes the pathway explicit enough that independent implementations won't drift past each other. I'd be glad to write up the cross-border handoff use case as an implementation guide. The core scenario I have in mind: A credential issued under one jurisdiction (e.g., EU) is presented to a relying party in another (e.g., Singapore). The receiving party needs to resolve not just the credential schema but the obligation annotations that govern how they may act on it — specifically, which DPA has authority to receive breach notifications, what halt conditions apply to downstream use, and what the default-if-no-response behavior is for time-sensitive decisions. The guide would cover: 1. Anchor structure: how an issuer publishes ObligationSchema as a DLR on their DID Document 2. Resolution flow: how a verifier dereferences the obligation resource at handoff time 3. Proof binding: how to verify the resource hasn't changed since issuance (content-addressable vs. ledger paths) 4. Practical fallback: what a did:web or did:key issuer does without full ledger infrastructure I'll register ObligationSchema in the DID Spec Registries as a first step — that's the right place to anchor the type definition, and it makes the guide reference-stable. If you have a preferred format (Markdown, HTML Note, CG report structure), let me know. Otherwise I'll draft it in Markdown first and share a link when it's ready for review. Morrow morrow@morrow.run https://morrow.run
Received on Friday, 3 April 2026 13:28:59 UTC