> 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/terminology.md). # Terminology Definitions reuse established international sources wherever they exist. This section does not duplicate the GovStack common terminology; it references it and defines only what is specific to this Building Block. ## Terms adopted from the GovStack common terminology | Term | Note on use here | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Metadata | Used throughout. Educational metadata (below) is the domain-specific profile | | Digital Public Infrastructure (DPI) | The class of shared systems to which this Building Block belongs | | Digital Public Good (DPG) | Referenced in the cross-functional requirements | | Adaptor | The optional component mapping an existing API to the GovStack specification — relevant to any authority with a repository predating this specification | | Registry | A collection of documents of a specific type | | User | See also the narrower data role *user* below | | Federation | Under Single Source of Truth, distributed custody of non-duplicated items, not replication | ## Terms defined by this specification | Term | Definition | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Repository | The managed collection of learning content and its metadata, together with the services that make it discoverable and retrievable. Distinguished from the registry that may manifest it | | Learning resource (learning object) | A discrete, reusable unit of learning content described by metadata and addressable via the repository | | Learning content | Educational material curated and managed by the repository, independent of any delivery channel | | Content item | A specific, versioned learning resource held under management | | Document | A single record in a collection. Here, typically a content item's metadata record, or a registered file | | Dataset | One or more fields drawn from one or more documents, grouped for a purpose. Datasets are the externally facing object: documents are created, read, updated, verified and cancelled through a dataset model | | Curriculum | The official structure of intended learning, organised into nodes with associated learning outcomes | | Curriculum framework | A named, versioned curriculum as published by a competent authority. A repository may hold alignments against more than one | | Curriculum node | An addressable element of a curriculum framework — a subject, stage, unit or statement | | Competency | The ability to apply knowledge, skills, attitudes and/or values to perform a task: what a learner is able to do | | Learning outcome | A statement of what a learner is expected to know or be able to do, to which content or curriculum is aligned | | Curriculum alignment | A recorded, independently addressable association between a content item and one or more curriculum nodes or competencies | | Assertor | The party that asserts a curriculum alignment. Recorded on every alignment record with the date and review status, so a consuming system can judge the authority behind the assertion | | Educational metadata | The standardised, machine-readable descriptive profile held for a learning resource | | Metadata record | The complete set of educational metadata held for one version of one content item | | Machine-readable | Structured in a defined, documented format that software can parse and act upon without human interpretation or bespoke extraction. A digitised resource carrying no structural markup — a scanned page image, or a document whose content is not tagged — is not machine-readable for the purposes of this specification, although it is digital | | Accessibility | The degree to which a learning resource can be perceived, operated and understood by learners with disabilities, including through assistive technology. Described in metadata by features present and known limitations | | Authorised | Qualifying any party whose identity has been authenticated and whose permission to perform the requested operation has been established through the Identity Building Block and the applicable consent or data-sharing agreement | | Consuming system | Any external application that discovers or retrieves content via the repository's APIs | | Authoritative content | Content issued or mandated by the competent education authority. The property derives from who published it | | Trusted content | Content that has passed the published assurance process of the repository. The property derives from what it has been through. Authoritative and trusted are independent properties: open content from a third party may be trusted without being authoritative | | Ontology / controlled vocabulary | A formal, shared set of concepts and terms used to classify and relate content semantically | | Granularity | The size and self-containedness of a learning resource. Permitted values are published in the granularity vocabulary | | Curation | The reviewed process by which content is assessed, described, aligned and approved for publication | | Provenance | Recorded information on the origin, authorship, licensing and review history of a content item | | Content package / manifest | A structured bundle of content components and the machine-readable manifest describing them | | Rights / licensing | The recorded terms under which a content item may be used, including open licences | | Open Educational Resources (OER) | Learning materials released under licences permitting free use and adaptation | | Harvesting | The bulk retrieval of repository metadata by an authorised external catalogue | | Human-in-the-loop | A design in which an accountable person reviews and decides on every AI-assisted output before it takes effect | The data roles — owner, custodian, maintainer, user and issuer — are defined under Actors and Roles. {% hint style="info" %} **Evidence.** Terminology is interoperability, not pedantry. The 1EdTech CASE specification exists because "standard", "framework", "outcome" and "competency" meant different things in every jurisdiction. The same reasoning drives the separation of competency from learning outcome above: in technical and vocational contexts the two are routinely distinguished, and a specification that merges them exports the ambiguity to every implementer. {% endhint %} --- # 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/terminology.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.