The profile
Sector extensions
Updated 11 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
Extensions add what a sector needs on top of DCAT-AP-UK, as DCAT-AP does for health, geospatial data and statistics. An extension never weakens the base: a record that conforms to an extension also conforms to DCAT-AP-UK.
How extensions work
- An extension may raise an obligation (optional or recommended to mandatory), narrow a cardinality, require a pattern, add properties and add classes. The build refuses an extension that would weaken the base.
- Each has its own SHACL shapes and JSON Schema (the base plus the extension), a worked example and at least one record that must fail. All three validators are held to the same verdict on them on every build.
- Choose one in the record builder, the record checker or the bulk checker, or pass it to the MCP server.
- Terms in another project’s namespace are that project’s. Terms this profile adds (dcatuk:) are provisional until reviewed with the sector (open register O-13).
The extensionsUpdated
Health and care
Describes health and care data well enough for a researcher or analyst to judge it before asking: who is covered, how many records, which clinical codes, and how access is controlled.
NHS bodies in all four nations, the UK Health Security Agency, social care, trusted research environments, health research charities and suppliers.
Geospatial
Adds what GeoDCAT-AP and UK GEMINI ask for: coverage, coordinate reference system, resolution, topic category and lineage, so geospatial records can sit in the same catalogue as everything else.
Mapping agencies, local authorities, environment and marine bodies, utilities, and anyone publishing location data to data.gov.uk or a spatial data infrastructure.
Official statistics
Says what status the statistics have under the Code of Practice, and describes their dimensions and measures so tables can be found by what they count, as StatDCAT-AP does.
The Office for National Statistics, departmental statistics teams, the devolved statistics offices, and any producer of statistics.
Transport and mobility
Says which mode of transport, which network and which data standard (TransXChange, NeTEx, SIRI, GTFS, DATEX II) a dataset uses, as mobilityDCAT-AP does for European national access points.
The Department for Transport, transport authorities, operators, the bus and rail open data services, and suppliers.
High-value datasets (for EU exchange)
Adds the two properties the DCAT-AP high-value datasets profile requires, so UK records can be harvested by EU catalogues that report under the EU high-value datasets regulation.
UK bodies that also publish into EU portals, take part in EU programmes, or whose data EU partners harvest.
AI-ready
Makes the record answer the questions an AI team asks first: may we train on it, is it synthetic, where is the data card, what policy applies, how good is it, and what period does it cover.
Anyone publishing data that may be used to train, fine-tune or evaluate AI models, and anyone building AI systems on public data.
Data spaces
Follows the Dataspace Protocol catalogue rules: every dataset carries a machine-readable usage policy, every distribution names the service that gives it, and the catalogue names its participant.
Organisations taking part in data spaces and connector networks, in the UK or with European and international partners.
Private and voluntary sector
GOV.UK organisation addresses only cover government. This extension asks for a registered identifier for every organisation, in the org-id.guide form, so a charity in Scotland, a company in Northern Ireland and a council in Wales are named the same way.
Companies, charities, social enterprises, mutuals, universities, housing associations and other bodies outside government that share data with it or publish their own.
Energy
Records the open data triage outcome for presumed-open energy system data, and asks for the Dublin Core elements the guidance requires. Every Dublin Core element already has a DCAT-AP-UK property.
Network companies and other parties obliged to follow Ofgem Data Best Practice, energy suppliers, and the energy data community.
Geodesy
A candidate module on top of the geospatial extension. It says which reference frame and epoch the coordinates are in, how they were observed, and how uncertain they are, so precise positions are not silently mixed across frames or dates. Requirement RQ-23.
Geodetic and positioning teams, national mapping and survey bodies, and anyone publishing coordinates, reference frame products or observation time series whose meaning depends on the frame, the epoch and the uncertainty.
Health and care ProposedUpdated
Describes health and care data well enough for a researcher or analyst to judge it before asking: who is covered, how many records, which clinical codes, and how access is controlled.
- For
- NHS bodies in all four nations, the UK Health Security Agency, social care, trusted research environments, health research charities and suppliers.
- Aligned to
- HealthDCAT-AP Release 7: HealthDCAT-AP Release 7S
- HDR UK Gateway dataset schema: HDR UK Gateway schemataS
- Identifier
https://w3id.org/dcat-ap-uk/ext/health(proposed; does not resolve yet)- How the UK differs
- HealthDCAT-AP names a Health Data Access Body under the European Health Data Space. The UK has none, so access is described by the rights statement and the trusted research environment address instead.
- Counts of people follow the publisher's disclosure control. Round them, and leave them out where disclosure control says so.
- The NHS national data opt-out applies in England only; say whether it has been applied.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Personal data | Dataset | Mandatory | dcatuk:personalData | Raised from recommended | Whether the data contains information about identifiable living people, and in what form. |
| Sensitive data | Dataset | Mandatory | dcatuk:sensitiveData | Raised from recommended | Whether the data contains information that needs extra care beyond being personal, such as special category data. |
| Time period covered | Dataset | Mandatory | dct:temporal | Raised from recommended | The period of time the data is about. |
| Geographic coverage | Dataset | Mandatory | dct:spatial | Raised from recommended | The geographic area the data is about. |
| Health category | Dataset | Recommended | healthdcatap:healthCategory | New | The category of health data, such as electronic health records, registries or genomic data. |
| Health theme | Dataset | Optional | healthdcatap:healthTheme | New | A disease, condition or topic the data is about, as an identifier. |
| Population covered | Dataset | Recommended | healthdcatap:populationCoverage | New | Who is in the data, in words, such as "patients registered with a GP practice in Wales". |
| Number of records | Dataset | Recommended | healthdcatap:numberOfRecords | New | How many records the data holds, rounded. |
| Number of people | Dataset | Recommended | healthdcatap:numberOfUniqueIndividuals | New | How many different people the data is about, rounded and subject to disclosure control. |
| Youngest typical age | Dataset | Optional | healthdcatap:minTypicalAge | New | The youngest age, in years, typical of people in the data. |
| Oldest typical age | Dataset | Optional | healthdcatap:maxTypicalAge | New | The oldest age, in years, typical of people in the data. |
| Clinical coding system | Dataset | Recommended | healthdcatap:hasCodingSystem | New | A coding system used in the data, such as SNOMED CT, ICD-10, OPCS-4 or the Dictionary of medicines and devices. |
| National data opt-out applied | Dataset | Recommended Provisional | dcatuk:nationalDataOptOut | New | Whether patients' national data opt-out choices have been applied to the data (England). |
| Trusted research environment | Dataset | Optional Provisional | dcatuk:trustedResearchEnvironment | New | The web page of the trusted research environment or secure data environment where approved people can use the data. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 215 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/health",
"title": "Synthetic GP appointments, Wales",
"description": "An invented dataset of GP appointments, used to show the health extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/internal",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/pseudonymised",
"licence": "ukcl:licences/data-sharing-agreement-required",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"rights": "Available to approved researchers in a trusted research environment, under a data sharing agreement. Ask through the contact form.",
"sensitiveData": [
"ukcl:sensitive-data/special-category"
],
"temporal": [
{
"startDate": "2020-01-01",
"endDate": "2025-12-31"
}
],
"spatial": [
"http://statistics.data.gov.uk/id/statistical-geography/W92000004"
],
"jurisdiction": [
"ukcl:jurisdiction/gb-wls"
],
"populationCoverage": "People registered with a GP practice in Wales.",
"numberOfRecords": "12000000",
"hasCodingSystem": [
"http://snomed.info/sct"
],
"nationalDataOptOut": "false",
"trustedResearchEnvironment": [
"https://example.org/tre"
]
}
Geospatial ProposedUpdated
Adds what GeoDCAT-AP and UK GEMINI ask for: coverage, coordinate reference system, resolution, topic category and lineage, so geospatial records can sit in the same catalogue as everything else.
- For
- Mapping agencies, local authorities, environment and marine bodies, utilities, and anyone publishing location data to data.gov.uk or a spatial data infrastructure.
- Aligned to
- GeoDCAT-AP 3.1.0: GeoDCAT-AP 3.1.0S
- UK GEMINI 2.3: UK GEMINI 2.3S
- MEDIN discovery metadata standard (marine): MEDIN discovery metadata standardS
- Identifier
https://w3id.org/dcat-ap-uk/ext/geospatial(proposed; does not resolve yet)- How the UK differs
- UK GEMINI is encoded in ISO 19139 XML. This extension is the DCAT side; the crosswalk on the adoption page maps the elements.
- Give the coordinate reference system as a standard the data conforms to, for example http://www.opengis.net/def/crs/EPSG/0/27700 for British National Grid.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Geographic coverage | Dataset | Mandatory | dct:spatial | Raised from recommended | The geographic area the data is about. |
| Conforms to | Dataset | Mandatory | dct:conformsTo | Raised from recommended | A standard, specification or schema the resource follows. |
| Spatial resolution (metres) | Dataset | Recommended | dcat:spatialResolutionInMeters | Raised from optional | The smallest distance the data can tell apart, in metres. |
| Topic category | Dataset | Recommended | geodcatap:topicCategory | New | An ISO 19115 topic category, such as boundaries, transportation or environment. |
| Lineage | Dataset | Recommended | dct:provenance | New | How the data was made, from what sources, and the processes applied. |
| Purpose | Dataset | Optional | geodcatap:purpose | New | Why the data was made. |
| Spatial representation type | Distribution | Recommended | adms:representationTechnique | New | How the geographic information in this distribution is represented, such as vector or grid, from the INSPIRE list that GeoDCAT-AP uses. |
| Conforms to | Data service | Mandatory | dct:conformsTo | Raised from recommended | A standard, specification or schema the resource follows. |
| Statement | Lineage statement (new class) | Mandatory | rdfs:label | New | The lineage, in words. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 330 of 405, good
{
"class": "Dataset",
"id": "https://www.data.gov.uk/dataset/2dfb82b4-741a-4b93-807e-11abb4bb0875/os-postcodes-data",
"title": "Postcode locations for Great Britain",
"alternative": "Code-Point Open",
"abstract": "Free point locations for every postcode unit in Great Britain.",
"description": "The location of every postcode unit in Great Britain as a single point, with the codes of the areas it falls in. Often used for service planning, simple routing and statistical analysis.",
"identifier": "2dfb82b4-741a-4b93-807e-11abb4bb0875",
"publisher": "https://www.gov.uk/government/organisations/ordnance-survey",
"creator": [
"https://www.gov.uk/government/organisations/ordnance-survey"
],
"contactPoint": [
{
"fn": "Ordnance Survey customer service",
"hasURL": "https://www.ordnancesurvey.co.uk/contact-us"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:QUARTERLY",
"theme": [
"ukcl:theme/mapping"
],
"keyword": [
"postcode",
"address",
"location"
],
"spatial": [
"http://statistics.data.gov.uk/id/statistical-geography/K03000001"
],
"issued": "2022-02-01",
"modified": "2026-08-01",
"version": "2026-08",
"language": [
"eulang:ENG"
],
"landingPage": [
"https://www.ordnancesurvey.co.uk/products/code-point-open"
],
"distribution": [
{
"class": "Distribution",
"title": "Postcode locations, GeoPackage",
"accessURL": [
"https://www.ordnancesurvey.co.uk/products/code-point-open"
],
"mediaType": "https://www.iana.org/assignments/media-types/application/geopackage+sqlite3",
"representationTechnique": "inspiresrt:vector"
}
],
"conformsTo": [
"http://www.opengis.net/def/crs/EPSG/0/27700"
],
"spatialResolutionInMeters": [
"1"
],
"topicCategory": [
"http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/location"
],
"lineage": [
{
"statement": "Point locations derived from address data, updated each quarter."
}
]
}
Official statistics ProposedUpdated
Says what status the statistics have under the Code of Practice, and describes their dimensions and measures so tables can be found by what they count, as StatDCAT-AP does.
- For
- The Office for National Statistics, departmental statistics teams, the devolved statistics offices, and any producer of statistics.
- Aligned to
- StatDCAT-AP: StatDCAT-APV
- Code of Practice for Statistics: Code of Practice for StatisticsV
- Identifier
https://w3id.org/dcat-ap-uk/ext/statistics(proposed; does not resolve yet)- How the UK differs
- StatDCAT-AP version 3 is being revised. Its namespace in version 1 is a placeholder; check it before relying on these terms (open register O-13).
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Statistics status | Dataset | Mandatory Provisional | dcatuk:statisticsStatus | New | The status of the statistics under the Code of Practice for Statistics. |
| Time period covered | Dataset | Mandatory | dct:temporal | Raised from recommended | The period of time the data is about. |
| Data quality | Dataset | Recommended | dqv:hasQualityAnnotation | Raised from optional | A link to a published statement or measurement of the quality of the data. |
| Part of series | Dataset | Recommended | dcat:inSeries | Raised from optional | The dataset series this dataset belongs to. |
| Dimension | Dataset | Recommended | statdcatap:dimension | New | A dimension the statistics are broken down by, such as area, age or year, as an identifier. |
| Measure | Dataset | Recommended | statdcatap:statMeasure | New | What the statistics count or measure, as an identifier. |
| Attribute | Dataset | Optional | statdcatap:attribute | New | An attribute of the observations, such as a unit or a status flag, as an identifier. |
| Number of series | Dataset | Optional | statdcatap:numSeries | New | How many time series the dataset holds. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 195 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/statistics",
"title": "Synthetic quarterly statistics",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"statisticsStatus": "ukcl:statistics-status/official",
"temporal": [
{
"startDate": "2015-01-01"
}
],
"dimension": [
"https://example.org/def/dimension/area"
],
"statMeasure": [
"https://example.org/def/measure/count"
]
}
Transport and mobility ProposedUpdated
Says which mode of transport, which network and which data standard (TransXChange, NeTEx, SIRI, GTFS, DATEX II) a dataset uses, as mobilityDCAT-AP does for European national access points.
- For
- The Department for Transport, transport authorities, operators, the bus and rail open data services, and suppliers.
- Aligned to
- mobilityDCAT-AP: mobilityDCAT-APV
- Identifier
https://w3id.org/dcat-ap-uk/ext/transport(proposed; does not resolve yet)- How the UK differs
- Uses UK data standards, such as TransXChange and NaPTAN, as values of the data standard property.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Geographic coverage | Dataset | Mandatory | dct:spatial | Raised from recommended | The geographic area the data is about. |
| Mobility theme | Dataset | Mandatory | mobilitydcatap:mobilityTheme | New | The kind of mobility data, such as timetables, real-time arrivals or road works, from the mobilityDCAT-AP vocabulary. |
| Transport mode | Dataset | Recommended | mobilitydcatap:transportMode | New | The mode of transport, such as bus, rail or cycling. |
| Network covered | Dataset | Recommended | mobilitydcatap:networkCoverage | New | The part of the network covered, such as the strategic road network. |
| Georeferencing method | Dataset | Optional | mobilitydcatap:georeferencingMethod | New | How locations are referenced, such as coordinates or a location referencing method. |
| Mobility data standard | Distribution | Recommended | mobilitydcatap:mobilityDataStandard | New | The data standard of the file or feed, such as TransXChange, NeTEx, SIRI, GTFS or DATEX II. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 325 of 405, good
{
"class": "Dataset",
"id": "https://example.org/dataset/transport",
"title": "Synthetic bus timetables",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"spatial": [
"http://statistics.data.gov.uk/id/statistical-geography/E92000001"
],
"mobilityTheme": [
"https://w3id.org/mobilitydcat-ap/mobility-theme/timetables"
],
"transportMode": [
"https://w3id.org/mobilitydcat-ap/transport-mode/bus"
],
"distribution": [
{
"class": "Distribution",
"accessURL": [
"https://example.org/timetables"
],
"mediaType": "https://www.iana.org/assignments/media-types/application/xml",
"mobilityDataStandard": [
"https://example.org/standard/transxchange"
]
}
]
}
High-value datasets (for EU exchange) ProposedUpdated
Adds the two properties the DCAT-AP high-value datasets profile requires, so UK records can be harvested by EU catalogues that report under the EU high-value datasets regulation.
- For
- UK bodies that also publish into EU portals, take part in EU programmes, or whose data EU partners harvest.
- Aligned to
- DCAT-AP HVD 3.0: DCAT-AP HVD 3.0S
- Identifier
https://w3id.org/dcat-ap-uk/ext/hvd(proposed; does not resolve yet)- How the UK differs
- The EU high-value datasets regulation (EU) 2023/138 does not apply in UK law. This extension is for exchange only; it creates no UK obligation.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| High-value dataset category | Dataset | Mandatory | dcatap:hvdCategory | New | The category of high-value dataset, from the EU high-value dataset categories vocabulary. |
| Applicable legislation | Dataset | Mandatory | dcatap:applicableLegislation | Raised from optional | Legislation that requires, governs or permits the publication or sharing of the resource. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 175 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/hvd",
"title": "Synthetic geospatial high-value dataset",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"hvdCategory": [
"http://data.europa.eu/bna/c_ac64a52d"
],
"applicableLegislation": [
"http://data.europa.eu/eli/reg_impl/2023/138/oj"
]
}
AI-ready ProposedUpdated
Makes the record answer the questions an AI team asks first: may we train on it, is it synthetic, where is the data card, what policy applies, how good is it, and what period does it cover.
- For
- Anyone publishing data that may be used to train, fine-tune or evaluate AI models, and anyone building AI systems on public data.
- Aligned to
- MLDCAT-AP 3.x: MLDCAT-AP 3.0.0 and 3.1.0S
- Croissant 1.1: Croissant 1.1S
- Guidelines for AI-ready datasets (January 2026): Guidelines and best practices for making government datasets ready for AIV
- Identifier
https://w3id.org/dcat-ap-uk/ext/ai-ready(proposed; does not resolve yet)- How the UK differs
- MLDCAT-AP describes models and their training data in detail. This extension covers the dataset side only; describe models with MLDCAT-AP itself.
- The use for AI is a statement by the owner. The licence and the usage policy remain what binds people.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Use for AI | Dataset | Mandatory Provisional | dcatuk:aiUse | New | Whether the data may be used to train, fine-tune or evaluate AI models. |
| Personal data | Dataset | Mandatory | dcatuk:personalData | Raised from recommended | Whether the data contains information about identifiable living people, and in what form. |
| Usage policy | Dataset | Recommended | odrl:hasPolicy | Raised from optional | A machine-readable policy, in the W3C Open Digital Rights Language (ODRL), saying what may and may not be done with the resource. |
| Data card | Dataset | Recommended Provisional | dcatuk:dataCard | New | A page that documents how the data was collected, what it contains, what it is for and its known gaps and biases. |
| Synthetic data | Dataset | Recommended Provisional | dcatuk:syntheticData | New | Whether the data was generated rather than collected. |
| Data quality | Dataset | Recommended | dqv:hasQualityAnnotation | Raised from optional | A link to a published statement or measurement of the quality of the data. |
| Time period covered | Dataset | Recommended | dct:temporal | Narrowed | The period of time the data is about. |
| Documentation | Dataset | Recommended | foaf:page | Raised from optional | A web page that documents the resource, such as a user guide or a methodology. |
| Generated by | Dataset | Optional | prov:wasGeneratedBy | New | The process, model or system that generated the data, as an identifier. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 195 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/ai-ready",
"title": "Synthetic AI training dataset",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"aiUse": "ukcl:ai-use/permitted",
"hasPolicy": [
"https://cyberdudeuk.github.io/dcat-ap-uk/downloads/policies/ogl-open.jsonld"
],
"dataCard": [
"https://example.org/data-card"
],
"syntheticData": "true",
"temporal": [
{
"startDate": "2024-01-01",
"endDate": "2025-12-31"
}
]
}
Data spaces ProposedUpdated
Follows the Dataspace Protocol catalogue rules: every dataset carries a machine-readable usage policy, every distribution names the service that gives it, and the catalogue names its participant.
- For
- Organisations taking part in data spaces and connector networks, in the UK or with European and international partners.
- Aligned to
- Eclipse Dataspace Protocol 1.0: Eclipse Dataspace ProtocolS
- Identifier
https://w3id.org/dcat-ap-uk/ext/dataspace(proposed; does not resolve yet)- How the UK differs
- The protocol's namespace is given as it was understood on 6 November 2026; check it against the release you use (open register O-13).
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Usage policy | Dataset | Mandatory | odrl:hasPolicy | Raised from optional | A machine-readable policy, in the W3C Open Digital Rights Language (ODRL), saying what may and may not be done with the resource. |
| Access service | Distribution | Mandatory | dcat:accessService | Raised from optional | A data service that gives access to this distribution. |
| Participant identifier | Catalogue | Mandatory | dspace:participantId | New | The identifier of the data space participant that provides the catalogue. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 225 of 405, good
{
"class": "Dataset",
"id": "https://example.org/dataset/dataspace",
"title": "Synthetic data space offer",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"hasPolicy": [
"https://example.org/policy/offer-1"
],
"distribution": [
{
"class": "Distribution",
"accessURL": [
"https://example.org/connector"
],
"accessService": [
"https://example.org/connector"
]
}
]
}
Private and voluntary sector ProposedUpdated
GOV.UK organisation addresses only cover government. This extension asks for a registered identifier for every organisation, in the org-id.guide form, so a charity in Scotland, a company in Northern Ireland and a council in Wales are named the same way.
- For
- Companies, charities, social enterprises, mutuals, universities, housing associations and other bodies outside government that share data with it or publish their own.
- Aligned to
- org-id.guide identifier lists: org-id.guideV
- Identifier
https://w3id.org/dcat-ap-uk/ext/organisations(proposed; does not resolve yet)- How the UK differs
- Identifiers take the form PREFIX-identifier, for example GB-COH-00000000 for a company, GB-CHC-0000000 for a charity in England and Wales, GB-SC-SC000000 in Scotland, GB-NIC-000000 in Northern Ireland, or XI-LEI-... for a legal entity identifier.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Identifier | Organisation | Mandatory | dct:identifier | Raised from recommended | The main identifier of the resource in the publisher's own catalogue. Pattern: ^[A-Z]{2}-[A-Z0-9]{2,8}-[A-Za-z0-9._/-]+$ |
| Organisation type | Organisation | Recommended | dct:type | Raised from optional | The kind of organisation, as GOV.UK lists it, for example ministerial department or executive agency. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 175 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/organisations",
"title": "Synthetic charity dataset",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": {
"class": "Agent",
"name": "Example Community Trust",
"identifier": "GB-CHC-0000000",
"agentType": "Registered charity"
},
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01"
}
Energy ProposedUpdated
Records the open data triage outcome for presumed-open energy system data, and asks for the Dublin Core elements the guidance requires. Every Dublin Core element already has a DCAT-AP-UK property.
- For
- Network companies and other parties obliged to follow Ofgem Data Best Practice, energy suppliers, and the energy data community.
- Aligned to
- Ofgem Data Best Practice Guidance (1 April 2026): Data Best Practice GuidanceS
- Identifier
https://w3id.org/dcat-ap-uk/ext/energy(proposed; does not resolve yet)- How the UK differs
- The triage outcomes follow the guidance as understood on 6 November 2026; Ofgem consulted on changing the triage approach in May 2026, so check the current guidance (open register O-13).
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Open data triage outcome | Dataset | Mandatory Provisional | dcatuk:openDataTriage | New | The outcome of open data triage for data that is presumed open. |
| Presumed open | Dataset | Recommended Provisional | dcatuk:presumedOpen | New | Whether the data falls under the presumed open principle. |
| Keyword | Dataset | Mandatory | dcat:keyword | Raised from recommended | Words or short phrases that people might search for, not already in the title or description. |
| Creator | Dataset | Recommended | dct:creator | Narrowed | The organisation that created or compiled the content of the resource. |
| Geographic coverage | Dataset | Recommended | dct:spatial | Narrowed | The geographic area the data is about. |
| Time period covered | Dataset | Recommended | dct:temporal | Narrowed | The period of time the data is about. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 175 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/energy",
"title": "Synthetic network capacity data",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"network capacity",
"electricity"
],
"modified": "2026-10-01",
"openDataTriage": "ukcl:open-data-triage/open",
"presumedOpen": "true"
}
Geodesy CandidateNew
A candidate module on top of the geospatial extension. It says which reference frame and epoch the coordinates are in, how they were observed, and how uncertain they are, so precise positions are not silently mixed across frames or dates. Requirement RQ-23.
- For
- Geodetic and positioning teams, national mapping and survey bodies, and anyone publishing coordinates, reference frame products or observation time series whose meaning depends on the frame, the epoch and the uncertainty.
- Aligned to
- GeoDCAT-AP 3.1.0: GeoDCAT-AP 3.1.0S
- Identifier
https://w3id.org/dcat-ap-uk/ext/geodesy(proposed; does not resolve yet)- How the UK differs
- A candidate for discussion with geodetic specialists, not an agreed module. Its terms are in the dcatuk namespace for now; whether modules get namespaces of their own is open (RQ-07).
- Details of stations and other infrastructure are left out on purpose. They can be sensitive, and belong in a controlled layer if they are needed at all.
- Give the frame and the vertical reference as standard identifiers, such as EPSG codes, and name a realisation rather than an ensemble. EPSG 9067 is ETRF2000, a realisation of ETRS89; EPSG 4258, the ETRS89 ensemble, is accurate only to about 0.1 metres. EPSG 5701 is ODN height. Codes checked at the EPSG registry on 6 November 2026. The epoch is a decimal year, such as 2025.0.
| Property | Class | Obligation | Term | Change | Definition |
|---|---|---|---|---|---|
| Geographic coverage | Dataset | Mandatory | dct:spatial | Raised from recommended | The geographic area the data is about. |
| Reference frame | Dataset | Mandatory Provisional | dcatuk:referenceFrame | New | The coordinate reference system or terrestrial reference frame, and its realisation, that the coordinates are given in. |
| Coordinate epoch | Dataset | Recommended Provisional | dcatuk:coordinateEpoch | New | The date the coordinates refer to, as a decimal year, for frames in which positions move over time. |
| Vertical reference | Dataset | Optional Provisional | dcatuk:verticalReference | New | The height system the vertical values use, such as a national height datum or the ellipsoid. |
| Observation technique | Dataset | Recommended Provisional | dcatuk:observationTechnique | New | How the positions or heights were observed. |
| Horizontal uncertainty (metres) | Dataset | Recommended Provisional | dcatuk:horizontalUncertainty | New | The typical horizontal uncertainty of the positions, in metres, at the confidence level given. |
| Vertical uncertainty (metres) | Dataset | Optional Provisional | dcatuk:verticalUncertainty | New | The typical vertical uncertainty, in metres, at the confidence level given. |
| Confidence level (per cent) | Dataset | Recommended Provisional | dcatuk:confidenceLevel | New | The confidence level the uncertainties are stated at, as a percentage, such as 95. |
SHACL shapes JSON Schema Example JSON Example Turtle
The worked example: Level 1: Core Quality 195 of 405, sufficient
{
"class": "Dataset",
"id": "https://example.org/dataset/geodesy",
"title": "Synthetic coordinate time series for a survey control network",
"description": "An invented dataset used to show an extension. It does not exist.",
"identifier": "synthetic-0001",
"publisher": "https://example.org/organisations/example-department",
"contactPoint": [
{
"fn": "Example data team",
"hasURL": "https://example.org/contact"
}
],
"accessRights": "ukcl:access-rights/open",
"securityClassification": "ukcl:security-classification/official",
"personalData": "ukcl:personal-data/none",
"licence": "http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
"accrualPeriodicity": "eufreq:MONTHLY",
"theme": [
"ukcl:theme/government"
],
"keyword": [
"example"
],
"modified": "2026-10-01",
"spatial": [
"http://statistics.data.gov.uk/id/statistical-geography/K03000001"
],
"referenceFrame": "http://www.opengis.net/def/crs/EPSG/0/9067",
"coordinateEpoch": "2025.0",
"observationTechnique": [
"ukcl:geodetic-technique/gnss"
],
"horizontalUncertainty": "0.01",
"verticalUncertainty": "0.02",
"confidenceLevel": "95"
}
Propose an extension
A sector body, or anyone, can propose an extension with the change request form. Say who it is for, what it adds, which standard it aligns to and which records would use it.