# Understanding DID-Linked Resources

## Overview

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](https://www.w3.org/TR/did-core/).

## Contents

Read the guides below to understand the context, rationale and design decisions involved in the DID-Linked Resource (DLR) implementation on cheqd.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Context for developing DID-Linked Resources</strong></mark></td><td>Understand the rationale for creating DID-Linked Resources and how they improve the current paradigm.</td><td><a href="understanding-dlrs/context">context</a></td></tr><tr><td><mark style="color:blue;"><strong>Technical composition of DID-Linked Resources</strong></mark></td><td>Understand the requirements and technical composition for DID-Linked Resources.</td><td><a href="understanding-dlrs/technical-composition">technical-composition</a></td></tr><tr><td><mark style="color:blue;"><strong>Referencing DID-Linked Resources in VCs</strong></mark></td><td>Learn how to embed DID-Linked Resources into the body of credentials for different purposes.</td><td><a href="understanding-dlrs/referencing">referencing</a></td></tr></tbody></table>

## Architecture for DID-Linked Resources

If you are interested in diving into the full architectural decisions for DID-Linked Resources, head to our ADR and the emerging W3C specification.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>ADR 002: DID-Linked Resources</strong></mark></td><td>Read up on the full architectural considerations and decisions that went into the initial design of DID-Linked Resources</td><td><a href="../../architecture/adr-list/adr-002-did-linked-resources">adr-002-did-linked-resources</a></td></tr><tr><td><mark style="color:blue;"><strong>W3C DID-Linked Resources</strong></mark></td><td>Keep up to date with the formal standardisation of DID-Linked Resources at the World Wide Web Consortium (W3C).</td><td><a href="https://w3c-ccg.github.io/DID-Linked-Resources/">https://w3c-ccg.github.io/DID-Linked-Resources/</a></td></tr></tbody></table>

As a general architectural overview for DID-Linked Resources, see the diagram below:

<figure><img src="https://3569764573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVAMvpKH7PYzvXA6u6Cn%2Fuploads%2Fgit-blob-2ce8ddd6f105d9f01bf41c2dddf881544c50894a%2FDID-Linked-Resources-Relationship.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for AnonCreds using DID-Linked Resources

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:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>cheqd AnonCreds Object Method</strong></mark></td><td>Understand how cheqd supports AnonCreds natively on its ledger, and start issuing and verifying AnonCreds using our supported SDKs.</td><td><a href="../../advanced/anoncreds">anoncreds</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cheqd.io/product/studio/did-linked-resources/understanding-dlrs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.