Proposed application profile
DCAT Application Profile for the UK
Updated 3 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
One way to describe UK public sector datasets and data services, so they can be found, judged and shared across every catalogue. Built on DCAT 3 and aligned with DCAT-AP, it evolves the xGov MEM.
Where do you want to start?
I describe data
You keep a catalogue or own a data asset. Build a record, check it and see what is mandatory for critical data assets.
I build or harvest
You write catalogue software, a harvester or a discovery service. Get the SHACL, JSON Schema, context and codelists.
I lead or decide
You are a chief data officer, policy coordinator or architect. See what changed, why, and how it fits the strategy.
I'm new to this
Start with what metadata is and why it matters, in plain English, with an Easy Read summary.
In short (Easy Read)
- Government holds a lot of data.
- People need to know what data there is, and how to get it.
- Metadata is the label on the data. It says what the data is, who looks after it and who can have it.
- This profile is a set of rules for writing those labels the same way everywhere.
- When everyone writes labels the same way, people can find data more easily.
- It is a proposal. People who look after government data will decide whether to use it.
Why one profile matters
Find it
A record written to one profile can be found by one search across every catalogue that uses it.
Judge it
Access rights, licence, coverage and quality are given the same way, so people can judge fitness before they ask.
Protect it
Security classification, personal data and sensitive data are explicit, so data is not shared where it should not be.
Reuse it
One record serves the department catalogue, the Data Asset Management return and the National Data Library.
At a glanceUpdated
14
21 of 22
Counts are calculated from the profile when the portal is built.
The profile in tablesUpdated
| Class | Properties | Mandatory |
|---|---|---|
| Dataset | 48 | 9 |
| Data service | 34 | 10 |
| Distribution | 18 | 1 |
| Dataset series | 9 | 2 |
| Catalogue | 15 | 3 |
| Catalogue record | 9 | 2 |
| Organisation | 4 | 1 |
| Contact point | 5 | 1 |
| Location | 4 | 0 |
| Period of time | 2 | 0 |
| Checksum | 2 | 2 |
| Relationship | 2 | 2 |
| Responsible role | 2 | 2 |
| Missing value | 2 | 2 |
All 89 properties are on every property.
Where it sits
A pan-UK public data infrastructure, from the people who use data down to the data itself. The profile is the shared record in the middle. 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).
StatusUpdated
Proposed. Not endorsed. To become a standard it needs, in order: review by the Metadata Implementation Working Group, a decision by the owning team in the Government Data directorate of the Government Digital Service, and endorsement by the Data Standards Authority Steering Board, as the xGov MEM had. Until then the xGov MEM remains the endorsed model.