Strategy
How it fits the strategy
Updated 1 section on this page is new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
The profile is one small part of a bigger plan: making public sector data easy to find and use across the UK. This page shows which parts of that plan it serves, and where its limits are.
What it serves
| Strategy or policy | How the profile serves it |
|---|---|
| Future pan-UK metadata architecture (DCAT-AP-UK founding specification and architecture blueprint)P | The architecture names DCAT-AP-UK as the shared record across UK data ecosystems, with domain profiles, validation and migration from the xGov MEM. This portal implements that record, its sector extensions, its validators and its migration tools, so the architecture has something working to test against. |
| A roadmap for modern digital government 2025 to 2030V | Platforms to share and use data need records that mean the same thing in every catalogue. The profile is that shared meaning. |
| National Data Library: progress update, January 2026V | A single trusted gateway to public sector data needs findable, consistent, honest records. The profile gives harvestable records with the access, licence and quality signals users need. |
| Data asset management policy in governmentV | Departments must manage and report metadata about critical data assets. The critical data asset switch makes the guidance's attributes mandatory in the same record the catalogue already holds, so returns can be built, not retyped. |
| Recording metadata to describe critical data assetsV | Every attribute the guidance lists is crosswalked to a property. Where the guidance is inconsistent (created and dateCreated), the profile picks one term and records the alias. |
| Metadata Based Discovery of Data Sets and Sources (draft pattern, version 1.0)V | The pattern needs a canonical metadata record that harvesters map to. The profile, with its shapes and JSON Schema, is proposed as that record, so each adapter maps to one target. |
| Cross-government data sharing principles (draft)V | Principle 6 asks for common standards for sharing. The profile is one, reusing DCAT and DCAT-AP rather than inventing. |
| Guidelines and best practices for making government datasets ready for AIV | Metadata quality is a pillar. Conforms to, time and place covered, quality annotation and the schema.org crosswalk help machines as well as people judge a dataset. |
A pan-UK public data infrastructure
Read from the top, people find data; read from the bottom, bodies keep their own data and describe it once. The layers are the author’s model, drawn from the sources below K.
- People and systems: Researchers, service teams, policy makers and the public find, judge and ask for data.
- Gateways and returns: The National Data Library, the Data Marketplace and Data Asset Management returns read the same records.
- Harvest and discovery: Discovery services collect records, map them to the shared record and make them searchable.
- The shared record (this profile): DCAT-AP-UK: one meaning for every record, with shapes to check it.
- Catalogues: Each body describes its assets once, in its own catalogue.
- Data held by public bodies: Datasets and services stay with the bodies accountable for them (federate first).
Four nations
England-only rules are not presented as UK-wide. Check each nation’s position before relying on it K.
| Nation | What applies | Languages to record | Notes |
|---|---|---|---|
| England | The Data Asset Management Policy applies to UK government departments and their arm's-length bodies. Councils are not in scope; the profile is good practice for them. | English | data.gov.uk is becoming the National Data Library. |
| Scotland | Devolved bodies are not in scope of the UK policy. The profile can be adopted voluntarily. Scottish catalogues such as statistics.gov.scot and the Scottish spatial data infrastructure publish linked data and geospatial metadata. | English, Scottish Gaelic (GLA), Scots (SCO) | Gaelic language plans apply to some bodies. Give titles and descriptions in both languages where the body has one. |
| Wales | Devolved bodies are not in scope of the UK policy. The profile can be adopted voluntarily. Data Map Wales publishes geospatial metadata. | Welsh (CYM) and English | The Welsh Language Standards mean Welsh must not be treated less favourably: give the title and description in Welsh, tagged cy, as well as English. |
| Northern Ireland | Northern Ireland departments are not in scope of the UK policy. The profile can be adopted voluntarily. OpenDataNI publishes open data. | English, Irish (GLE), Ulster Scots (SCO) | Section 75 equality duties apply to public authorities. |
| UK-wide | UK government departments that cover more than one nation follow the policy for the whole department. | All of the above | Use GSS codes for areas so records from every nation can be compared. |
Limits
- The profile describes data; it does not move it, grant access to it or check its quality.
- The Data Asset Management Policy names no metadata standard. Using this profile for returns needs a decision by the owning team.
- The strategic roadmap for public sector data had not been published when this was written. When it is, check this page against it.
- Mappings marked K need a specialist review before endorsement.
Related profiles and models
- schema.org Dataset: Used by search engines. The portal shows the schema.org term for each property where one exists. K
- Croissant (MLCommons): Metadata for machine learning datasets, built on schema.org. Relevant to AI-ready data. K
- GeoDCAT-AP: The geospatial extension of DCAT-AP, aligned with INSPIRE and ISO 19115. K
- StatDCAT-AP: For statistical data; a version 3 is being revised. K
SourcesUpdated
| Source | Publisher | Date | Role |
|---|---|---|---|
| Future pan-UK metadata architecture (DCAT-AP-UK founding specification and architecture blueprint)P | co-cddo on GitHub (private repository; access needed) | 2026-06-05 | The architecture blueprint for harmonising metadata across the UK's data ecosystems, with DCAT-AP-UK as its shared record. This portal is offered as a working implementation of that profile. The repository is private, so its contents are not reproduced here. |
| Data Catalog Vocabulary (DCAT) Version 3V | W3C | 2024-08-22 | Base standard. W3C Recommendation. |
| DCAT-AP 3.0.1V | SEMIC, Interoperable Europe | 2025-10-27 | The European application profile. DCAT-AP-UK keeps its mandatory properties so UK records can be harvested with European tools. |
| UK Cross-Government Metadata Exchange ModelV | Central Digital and Data Office | 2023-11-08 | The endorsed model this profile evolves (release v0.1.0, last changed July 2024). |
| Recording metadata to describe critical data assetsV | GOV.UK | 2026-04-16 | The core metadata the Data Asset Management Policy asks for. Its attributes are crosswalked to this profile. |
| Data asset management policy in governmentV | GOV.UK | 2026-05-27 | Requires departments and arm's-length bodies to manage metadata about critical data assets in their catalogues and report it to GDS. It names no metadata standard. |
| Using metadata to describe data assets in a data catalogueV | GOV.UK, recommended open standards for government | 2023-09-28 | The open standard that recommends DCAT 3 and points to the xGov MEM. |
| Data Marketplace data catalogue metadata (JSON Schema and API)V | co-cddo on GitHub | 2026-04-08 | How the Data Marketplace exchanges records. Its properties are crosswalked. |
| Metadata Based Discovery of Data Sets and Sources (draft pattern, version 1.0)V | GDS Data Architecture function | 2026-09 | Future-state architecture. It needs a shared canonical metadata record; DCAT-AP-UK is proposed as that record. |
| Cross-government data sharing principles (draft)V | GDS Data Architecture function | 2026 | Principle 6, use common standards for sharing. |
| A roadmap for modern digital government 2025 to 2030V | UK Parliament (written statement, Department for Science, Innovation and Technology) | 2026-01-19 | Commits to the National Data Library and to platforms to share and use data. |
| National Data Library: progress update, January 2026V | GOV.UK | 2026-01-26 | Says public sector data must be easier to find; data.gov.uk is becoming the National Data Library. |
| Guidelines and best practices for making government datasets ready for AIV | GOV.UK | 2026-01-19 | Data and metadata quality is one of its four pillars. |
| Government Security Classifications Policy, version 2.0V | Cabinet Office | 2024-08 | The classification values. |
| UK GEMINI 2.3S | Association for Geographic Information | The UK standard for geospatial metadata. Geospatial publishers follow it as well as this profile. | |
| data.gov.uk topicsV | data.gov.uk | 2026-11-06 | The theme list. |
| GOV.UK organisations APIP | GOV.UK | 2026-10-31 | The organisation list for publisher and creator, read by the GitHub Repos Asset Catalogue on 31 October 2026 (1,271 organisations). |