> 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-content/specifications.md).
# Specifications
The draft GovStack-aligned specification for the Learning Content Repository Building Block — status, scope, and a map of the full specification.
{% hint style="warning" %}
**Working draft — not for implementation.** This is version 1.0, September 2026, prepared for Working Group development. It is not a final production standard and should not be implemented as one.
{% endhint %}
**Document type:** Building Block specification (GovStack specification template) · **Status:** Working draft for Working Group development · **Version:** 1.0 · **Date:** September 2026 · **Normative anchor:** Charter for Public Digital Learning Platforms (ITU, UNESCO, UNICEF, March 2026)
Learning Content — specified here as the Learning Content Repository (LCR) Building Block — treats curated learning content as shared digital public infrastructure: a managed public asset, curated by or on behalf of the competent education authority, described with standardised metadata, aligned to curriculum, and exposed through open APIs to any authorised consuming system, decoupled from any delivery channel or application.
The key words REQUIRED, RECOMMENDED, OPTIONAL, MUST, MUST NOT, SHOULD and MAY are used throughout as described in RFC 2119 and RFC 8174. Requirements carry stable identifiers (for example `LCR-MET-002`) so they can be referenced, tested and traced. The specification inherits the GovStack cross-functional requirements baseline and the GovStack Security Requirements, and references other Building Blocks rather than re-deriving their capabilities.
## Explore the specification
{% columns %}
{% column %}
[**Description**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/description.md) What the Building Block is, who it's for, and what it deliberately does not do.
{% endcolumn %}
{% column %}
[**Terminology**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/terminology.md) The vocabulary used throughout, including terms specific to this Building Block.
{% endcolumn %}
{% column %}
[**Key Digital Functionalities**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/key-digital-functionalities.md) The eleven things the repository does, in plain terms.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
[**Cross-Functional Requirements**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/cross-functional-requirements.md) Non-functional requirements extending the GovStack baseline for education content.
{% endcolumn %}
{% column %}
[**Functional Requirements**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/functional-requirements.md) Atomic, testable requirements, organised by functionality.
{% endcolumn %}
{% column %}
[**Data Structures**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/data-structures.md) The canonical, technology-agnostic information model.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
[**Service APIs**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/service-apis.md) The REST/JSON API surface and its conventions.
{% endcolumn %}
{% column %}
[**Internal Workflows**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/internal-workflows.md) The content lifecycle and other key internal processes.
{% endcolumn %}
{% column %}
[**Testing**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/testing.md) Conformance profiles and test classes.
{% endcolumn %}
{% endcolumns %}
[**Other Resources**](/experience-digital-transformation/dpi-for-education/learning-content/specifications/other-resources.md) — reference standards, supporting artefacts, and related Building Blocks.
Version history
| Version | Date | Contributor(s) | Comment |
| ------- | -------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 0.1 | August 2026 | J. Roberts | First working draft prepared for the inaugural session of the Working Group: full skeleton against the GovStack template with substantive draft content, candidate requirements and real-world examples for every section. Non-breaking. |
| 1.0 | September 2026 | C. Biscette, J. Roberts | Revision following Working Group review of sections 1–3 and the Registry Building Block briefings. Section numbering aligned to published Building Blocks. Data-role model introduced. Boundary with the Digital Registries BB restated. Relationship table corrected. Education-level scope recorded. Terminology split between the GovStack glossary and domain-specific terms. Testing section added. Non-breaking. |
---
# 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-content/specifications.md?ask=&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.