> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications.md).

# Specifications

The Learning Verifiable Credentials (LVC) specification

A practical guide for education authorities that want learners' certificates, diplomas and other credentials to be trusted, portable and quick to verify. It helps a ministry choose among three ways of issuing verifiable credentials, from digitally signed documents to learner-held digital credentials, according to its connectivity, institutional capacity and existing systems, and to implement and run the chosen option with its own institutions rather than depending on a single vendor. It builds on open standards and on implementations already in use, and includes procurement clauses a government can reuse.

Designed for ministries of education and labour, qualifications and accreditation authorities, examination boards, universities and training providers, and the technical teams and suppliers that build credential systems for them; as well as development partners financing education digital transformation.

{% hint style="warning" %}
**Working draft:** This is an interim version; sections marked *Coming Soon* will be completed in the next phase.
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><strong>1. Overview</strong></p><p>Why this matters, and what is in scope.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/1.-overview.md">1. Overview</a></td></tr><tr><td><p><strong>2. Conformance Profiles</strong></p><p>The three options — LVC-1, LVC-2, LVC-3 — and how to choose between them.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/2.-conformance-profiles.md">2. Conformance Profiles</a></td></tr><tr><td><p><strong>3. Use Cases</strong></p><p>Seven use cases showing how the three profiles work in practice.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/3.-use-cases.md">3. Use Cases</a></td></tr><tr><td><p><strong>4. Ecosystem &#x26; Trust</strong></p><p>Who does what, and how a verifier knows an issuer is genuine and authorised.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/4.-ecosystem-and-trust.md">4. Ecosystem &amp; Trust</a></td></tr><tr><td><p><strong>5. Data Models</strong></p><p>What a credential contains: credential types, languages and controlled vocabularies.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/5.-data-models.md">5. Data Models</a></td></tr><tr><td><p><strong>6. Specification</strong></p><p>Terminology and requirements.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/6.-specification.md">6. Specification</a></td></tr><tr><td><p><strong>7. Procurement (RFP) Clauses</strong></p><p>Clauses written to be inserted directly into tender documents.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/7.-procurement-rfp-clauses.md">7. Procurement (RFP) Clauses</a></td></tr><tr><td><p><strong>8. Sources &#x26; Standards</strong></p><p>The reference backbone: every public standard and source this specification cites.</p></td><td><a href="/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications/8.-sources-and-standards.md">8. Sources &amp; Standards</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/dpi-for-education/learning-verifiable-credentials/specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.