> 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/other-resources.md).

# Other Resources

## Reference standards and crosswalks

| Area                        | Crosswalk                                                                      |
| --------------------------- | ------------------------------------------------------------------------------ |
| Educational metadata        | Core profile ↔ IEEE LOM, Dublin Core, LRMI / schema.org                        |
| Curriculum and competencies | Curriculum model ↔ 1EdTech CASE, CEDS                                          |
| Packaging                   | Manifest ↔ IMS Common Cartridge                                                |
| Vocabularies                | Term sets ↔ SKOS; education levels ↔ ISCED 2011                                |
| Harvesting                  | Harvesting API ↔ OAI-PMH                                                       |
| Rights                      | Rights object ↔ Creative Commons, SPDX                                         |
| Accessibility               | Accessibility description ↔ schema.org accessibility properties, WCAG-informed |
| Language                    | Language tagging ↔ IETF BCP 47                                                 |

Full crosswalk tables are maintained in the Sources and Standards Register.

## Supporting artefacts

OpenAPI 3.x definitions for the Service APIs; JSON Schemas for the Data Structures entities; vocabulary term sets in SKOS; the learning content ontology and curriculum mapping model; content quality and curriculum-alignment rubric guidance; sequence diagrams for the Internal Workflows; the conformance test suite and sample data; and the Sources and Standards Register.

## Content quality and curriculum-alignment guidance

The rubric — the criteria a content item must meet to be published, the evidence recorded, the curation roles involved, and the method for assessing curriculum alignment — is published as a supporting artefact. Publicly documented quality frameworks from operating repositories offer validated starting points: Oak National Academy publishes curriculum principles (knowledge-rich, sequenced and coherent, evidence-informed, flexible, diverse, accessible), and the OECS quality standards framework scores each asset against five standards on a four-point scale with banded outcomes. This specification requires that a published rubric exists and is auditable; it does not prescribe which.

## Related Building Blocks and Digital Public Goods

**Consumed:** Identity, Consent, Information Mediator, Digital Registries. **Adjacent and distinct:** Content Management System, Registration, Workflow. **Sibling education Building Blocks:** Education Data, Learning Verifiable Credentials.

Candidate reference implementations and evidence sources recorded in the Sources and Standards Register include Sunbird and DIKSHA components, Kolibri, Oak National Academy's openly licensed content and API, Finland's aoe.fi, Norway's NDLA, and the OECS Learning Hub.

## Glossary, contributors and version conventions

The glossary is in Terminology, maintained alongside the GovStack common terminology. Contributors are recorded by role and organisation. The specification uses semantic versioning; every published revision is summarised on the Specifications landing page.


---

# 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/other-resources.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.