| description |
|---|
Understanding the context and construction of DID-Linked Resources |
Our objective in building DID-Linked Resources on cheqd is to improve the way resources are stored, referenced and retrieved for our partners and the broader SSI community, in line with the existing W3C DID Core standard.
| Context for developing DID-Linked Resources | Understand the rationale for creating DID-Linked Resources and how they improve the current paradigm. | context.md |
| Technical composition of DID-Linked Resources | Understand the requirements and technical composition for DID-Linked Resources. | |
| Referencing DID-Linked Resources in VCs | Learn how to embed DID-Linked Resources into the body of credentials for different purposes. |
If you are interested in diving into the full architectural decisions for DID-Linked Resources, head to our ADR and the emerging W3C specification.
| ADR 002: DID-Linked Resources | Read up on the full architectural considerations and decisions that went into the initial design of DID-Linked Resources | adr-002-did-linked-resources.md |
| W3C DID-Linked Resources | Keep up to date with the formal standardisation of DID-Linked Resources at the World Wide Web Consortium (W3C). | https://w3c-ccg.github.io/DID-Linked-Resources/ |
As a general architectural overview for DID-Linked Resources, see the diagram below:
One of the functions of DID-Linked Resources is enabling support for AnonCreds on cheqd, where previously these were tied into the Hyperledger Indy ecosystem. Take a look at our AnonCreds documentation here:
| cheqd AnonCreds Object Method | Understand how cheqd supports AnonCreds natively on its ledger, and start issuing and verifying AnonCreds using our supported SDKs. | anoncreds |