What's changed
What's changed from the xGov MEM
Updated 1 section on this page is new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
Every property of the xGov MEM maps to the profile, so existing records convert automatically. 21 of the 22 open backlog items are resolved here; the rest need the owner. 56 properties are new, mostly from that backlog.
In summary
- Built on the DCAT 3 Recommendation instead of a working draft, and aligned with DCAT-AP 3.0.1 so records harvest into European tools.
- Every bug in the backlog is fixed: the contact point definition, the distribution range, the missing security classification IRI, the wrong example publisher and the title case examples.
- New requirements from the working group are in: geographic coverage, time period, schema, personal data, sensitive data, reference data and who can see a record.
- Critical data assets get their own mandatory properties, from the April 2026 guidance.
- Codelists are linked data, mapped to EU vocabularies. Themes use the data.gov.uk topics.
- Contact points prefer a contact form and never name a person.
- Release management: semantic versions, a change request form, release assets and a release gate.
The crosswalkUpdated
Download as CSV. To convert records, use Check records.
| xGov MEM | DCAT-AP-UK | Change | Why |
|---|---|---|---|
accessRights | Access rights dct:accessRights | Codelist mapped | Same three values (OPEN, COMMERCIAL, INTERNAL), now SKOS concepts mapped to the EU access-right vocabulary used by DCAT-AP. Usage notes added (issue 60). |
accessService | Access service dcat:accessService | Unchanged | |
address | Postal address vcard:hasAddress | Unchanged | |
alternativeTitle | Alternative title dct:alternative | Example fixed | The example for alternative title used title case, which conflicted with the rule for titles (issue 76). |
byteSize | Size (bytes) dcat:byteSize | Unchanged | |
contactName | Team name vcard:fn | Definition fixed | Defined as the team, not a person, so records survive staff changes and carry no personal data. |
contactPoint | Contact point dcat:contactPoint | Definition fixed | The definition was a copy of the email definition (issue 71). It now describes the contact point as a whole. |
created | Created dct:created | Unchanged | |
creator | Creator dct:creator | Obligation changed | Mandatory in the xGov MEM. Recommended in general and mandatory for critical data assets, as the April 2026 guidance lists it. |
description | Description dct:description | Unchanged | |
distribution | Distribution dcat:distribution | Range fixed | Was only an IRI or CURIE, so a distribution could not be described in the same record (issue 72). Now a Distribution node or its IRI. |
downloadURL | Download address dcat:downloadURL | Unchanged | |
email | Team email address vcard:hasEmail | Obligation changed | Mandatory in the xGov MEM. Now one of two routes: a contact form or a team mailbox, with the form preferred. |
endpointDescription | Endpoint description dcat:endpointDescription | Obligation changed | Mandatory in the xGov MEM; recommended, as in DCAT-AP. |
endpointURL | Endpoint address dcat:endpointURL | Obligation changed | Optional in the xGov MEM because of the security risk of publishing internal addresses. Mandatory in DCAT-AP; the guidance now says what to give instead. |
identifier | Identifier dct:identifier | Range relaxed | Was restricted to an IRI or CURIE. A plain literal now, as in DCAT, so local catalogue identifiers can be used; the record IRI carries the web identity. |
issued | Release date dct:issued | Unchanged | |
keyword | Keyword dcat:keyword | Unchanged | |
licence | Licence dct:license | Value restored | The xGov MEM had no way to say "no licence, ask for an agreement" after it moved to LinkML (issue 44). The value is restored as a concept. |
mediaType | Media type dcat:mediaType | Obligation changed | Mandatory in the xGov MEM. Recommended now, as in DCAT-AP, because some distributions are web pages or services. |
modified | Last updated dct:modified | Obligation changed | Mandatory in the xGov MEM, but many sources do not provide it (issue 30). Recommended now, and never to be invented. |
publisher | Publisher dct:publisher | Range changed | Was a GOV.UK organisation slug from a 2023 copy of the list (1,176 entries). Now an agent identified by its GOV.UK organisation address, from the list read on 31 October 2026 (1,271 entries, closed organisations kept and flagged). |
relatedResource | Related resource dct:relation | Unchanged | |
securityClassification | Security classification dcatuk:securityClassification | Property IRI fixed | Had no property IRI at all, so it could not be exchanged as linked data. NOT_APPLICABLE is withdrawn: public sector data always has a classification. |
servesData | Serves dataset dcat:servesDataset | Renamed | Renamed to match DCAT. The property IRI was already dcat:servesDataset. |
serviceStatus | Status adms:status | Codelist mapped | Same phases, now SKOS concepts linked to the Service Manual. |
serviceType | Interface style dct:type | Merged | The xGov MEM had both "type" (an rdf:type IRI, required) and "serviceType" (dct:type). rdf:type now comes from the class, and dct:type holds the interface style. |
summary | Summary dct:abstract | Property IRI fixed | The xGov MEM used rdfs:comment, a generic comment property. dct:abstract is the Dublin Core term for a summary. |
telephone | Telephone vcard:hasTelephone | Unchanged | |
theme | Theme dcat:theme | Codelist added | The xGov MEM had no list of values (issue 49). The 14 data.gov.uk topics, read on 6 November 2026, are now the list. |
title | Title dct:title | Unchanged | |
updateFrequency | Update frequency dct:accrualPeriodicity | Codelist mapped | Dublin Core frequency terms are mapped one to one to the EU frequency vocabulary that DCAT-AP requires. Old values are still accepted and converted. |
version | Version dcat:version | Obligation changed | Mandatory in the xGov MEM; recommended now, because not every resource is versioned. |
| (none) | Access address dcat:accessURL | New | Missing from the xGov MEM. Mandatory in DCAT-AP; added so UK records harvest into European catalogues. |
| (none) | Organisation prov:agent | New | |
| (none) | Organisation type dct:type | New | |
| (none) | Algorithm spdx:algorithm | New | |
| (none) | Applicable legislation dcatap:applicableLegislation | New | |
| (none) | Bounding box dcat:bbox | New | |
| (none) | Centre point dcat:centroid | New | |
| (none) | Checksum spdx:checksum | New | |
| (none) | Checksum value spdx:checksumValue | New | |
| (none) | Compression format dcat:compressFormat | New | |
| (none) | Conforms to dct:conformsTo | New | |
| (none) | Critical data asset dcatuk:criticalDataAsset | New | |
| (none) | Dataset dcat:dataset | New | |
| (none) | Documentation foaf:page | New | |
| (none) | End date dcat:endDate | New | |
| (none) | Property added or changed on the way dcatuk:enrichedProperty | New | |
| (none) | Expires schema:expires | New | |
| (none) | Format dct:format | New | |
| (none) | Geometry locn:geometry | New | |
| (none) | Role dcat:hadRole | New | |
| (none) | Usage policy odrl:hasPolicy | New | |
| (none) | Contact form vcard:hasURL | New | |
| (none) | Home page foaf:homepage | New | |
| (none) | Part of series dcat:inSeries | New | |
| (none) | Replaced by dct:isReplacedBy | New | |
| (none) | Where the data is held or sent dcatuk:jurisdiction | New | |
| (none) | Landing page dcat:landingPage | New | |
| (none) | Language dct:language | New | |
| (none) | Place name skos:prefLabel | New | |
| (none) | Who can see this record dcatuk:metadataAudience | New | |
| (none) | Property left empty dcatuk:missingProperty | New | |
| (none) | Why it is empty dcatuk:missingReason | New | |
| (none) | Missing value dcatuk:missingValue | New | |
| (none) | Name foaf:name | New | |
| (none) | Other identifier adms:identifier | New | |
| (none) | Personal data dcatuk:personalData | New | |
| (none) | Previous version dcat:previousVersion | New | |
| (none) | Describes foaf:primaryTopic | New | |
| (none) | Responsible role prov:qualifiedAttribution | New | |
| (none) | Qualified relation dcat:qualifiedRelation | New | |
| (none) | Data quality dqv:hasQualityAnnotation | New | |
| (none) | Catalogue record dcat:record | New | |
| (none) | Reference data used dcatuk:referenceData | New | |
| (none) | Rights statement dct:rights | New | |
| (none) | Sensitive data dcatuk:sensitiveData | New | |
| (none) | Data service dcat:service | New | |
| (none) | Source record dct:source | New | |
| (none) | Geographic coverage dct:spatial | New | |
| (none) | Spatial resolution (metres) dcat:spatialResolutionInMeters | New | |
| (none) | Start date dcat:startDate | New | |
| (none) | Time period covered dct:temporal | New | |
| (none) | Time resolution dcat:temporalResolution | New | |
| (none) | Theme list used dcat:themeTaxonomy | New | |
| (none) | Transfer safeguard dcatuk:transferMechanism | New | |
| (none) | Connection security dcatuk:transportSecurity | New | |
| (none) | Version notes adms:versionNotes | New | |
type | The class (rdf:type) | Merged | The class of a record gives its type; there is no separate type property. |
The backlog
Read from the xGov MEM repository on 2026-11-06 V: 99 issues and pull requests, of which 22 issues and 12 pull requests were open. Contributors are not named.
| Issue | Title | Status | How it was dealt with | Where |
|---|---|---|---|---|
| #86 | Major overhaul tracking issue for the metadata exchange model and site | Resolved | This repository is the overhaul. Its six workstreams map to this repository: dependencies and infrastructure (one build script, no generator chain to keep patched), schema fixes (every model bug below), documentation and site (the portal), new requirements (spatial, temporal, schema, personal and sensitive data), governance and release management (versioning, change requests, the release gate) and community (issue forms and Discussions). The tracking issue in co-cddo can be closed with a link here once the owners agree. | What's changed from the xGov MEM, Design and governance |
| #78 | Rename the repository and references to DCAT Application Profile for the UK | Resolved | A new repository, as the discussion suggested for a completely new solution: the model is no longer generated with LinkML and the site is no longer MkDocs. The old repository can be archived with a pointer here (ADR 0001). Old identifiers are kept in the crosswalk so existing records still map. | ADR 0001, What's changed from the xGov MEM |
| #76 | Title examples in alternative title don't follow the rules for titles | Resolved | Examples now follow the sentence case rule they illustrate, and a check fails the build if an example title is in title case. | Alternative title, Title, C-EX-02 |
| #72 | Distribution is incorrectly configured as an IRI or CURIE | Resolved | A distribution can now be described in the same record or referred to by its IRI. The SHACL shape and JSON Schema both accept either. | Distribution |
| #71 | The contact point definition is the same as the email definition | Resolved | Contact point is now defined as the contact as a whole. Team name, contact form and team mailbox each have their own definitions. A contact form is the preferred route; a team mailbox is allowed; a named person is not. | Contact point, Team name, Contact form, Team email address, Contact point |
| #70 | Launch release management, lock the specification and start formal change management | Resolved | Semantic versioning, a change request form, a public change log, a release gate that must pass, and released files as assets (JSON Schema, SHACL, JSON-LD context, codelists) rather than a source zip, as the discussion asked. | Design and governance |
| #69 | The OS postcodes example names the wrong publisher | Resolved | The example is rebuilt from the public record and credits Ordnance Survey as publisher and creator. | example |
| #63 | Codelist pages don't link out to external vocabularies | Resolved | The portal is generated by this repository's own script, so every concept links to its scheme and to the matching EU concept. The LinkML limitation no longer applies. | Codelists |
| #60 | Add usage notes to access rights | Resolved | Usage notes for each value, the difference from licence and security classification, and a rights statement for anything not open. | Access rights, Access rights |
| #49 | Recommend a taxonomy for theme values | Resolved | The 14 data.gov.uk topics are the theme list, as the issue proposed, each with a readable identifier rather than a search address, and mapped to the EU data themes. The cross-government taxonomy can replace it when published. | Theme |
| #44 | What to do if there is no applicable licence | Resolved | The "data sharing agreement required" value is restored, with a rights statement to describe the agreement. | Licence, Rights statement, Licences |
| #30 | What to do with assets that don't have a modified date | Resolved | Last updated is recommended, not mandatory, and must never be invented. The created and release dates cover the rest. | Last updated |
| #26 | Indicate whether the data includes sensitive information | Resolved | A sensitive data property with a codelist (special category, criminal offence, children, commercially sensitive, security sensitive). | Sensitive data, Sensitive data |
| #25 | Indicate whether the data includes personal identifiable information | Resolved | A personal data property, mandatory for critical data assets, with values for none, personal, pseudonymised, anonymised and not yet known. | Personal data, Personal data |
| #15 | Add a home page for the point of contact | Resolved | The contact point takes a web address (vcard:hasURL), which is also the preferred route as a contact form. | Contact form |
| #13 | Decide on a persistent identifier for the metadata model | Needs the owner | w3id.org is proposed (https://w3id.org/dcat-ap-uk/), and every identifier in the profile already uses it. Registering the redirect is a pull request to the w3id.org repository, to be made by the owning team. Until then the identifiers do not resolve, and the portal says so. | Design and governance |
| #11 | Include schemas in the documentation site | Resolved | JSON Schema, SHACL, JSON-LD context, LinkML, SKOS codelists, CSV and examples in Turtle and JSON-LD are all downloadable, with a DCAT description of them. | Downloads and API |
| #5 | Enable declaration of the metadata's access control | Resolved, provisional | A "who can see this record" property with four provisional levels, separate from the access rights of the data. Marked provisional: the issue asked for research with catalogue owners and information assurance, which has not been done. | Who can see this record, Who can see this record |
| #4 | Capture the schema of the underlying dataset | Resolved | Conforms to (dct:conformsTo), as DCAT recommends and the issue proposed, with guidance by format and a link to the Tabular data standard. Mandatory for critical data assets. | Conforms to |
| #3 | Capture the reference data used and its resolution | Resolved, provisional | A provisional "reference data used" property that links to the classification or code list (for example age bands) and its version. | Reference data used |
| #2 | Capture the temporal extent of the data resource | Resolved | Time period covered (dct:temporal) with start and end dates, as the discussion recommended, plus time resolution and dataset series for repeated releases such as a census. | Time period covered, Time resolution, Dataset series |
| #1 | Capture the geospatial coverage of the data resource | Resolved | Geographic coverage (dct:spatial) using, in order of preference, a GSS code or other controlled area identifier, a bounding box or a geometry, as the discussion concluded. The guidance names the "about the area" versus "located in the area" ambiguity raised in the thread, and points geospatial publishers to UK GEMINI. | Geographic coverage, Location |
| Issue | Title | Kept |
|---|---|---|
| #73 | Replace DataResource with CataloguedResource, as in DCAT 3 | DCAT 3 has no separate resource class in this profile; shared properties are listed on each class. |
| #56 | Potential changes to metadata standards to support APIs | Data services use conformsTo for the interface standard and dct:type for the interface style, as the discussion suggested. |
| #57 | Improved guidance for the mediaType property | Guidance carried over, with IANA addresses. |
| #45 | Usage notes for the version property | Guidance carried over. |
| #17 | accessRights should be mandatory for datasets and data services | Still mandatory. |
| #6 | An organisation missing from the government organisations list | The list is now read from GOV.UK, with closed organisations kept and flagged so old records still resolve. |
| Pull request | What it does | Status | Why |
|---|---|---|---|
| #99 | Delete the Docker image workflow | Superseded | This repository has no Docker build. |
| #84, 82, 90-98 | Ten Dependabot updates to the Python toolchain (pytest, markdown, pygments, idna, urllib3, pymdown-extensions, requests, soupsieve, setuptools, zipp, certifi) | Superseded | This repository does not use LinkML or MkDocs. Its own dependencies are pinned in requirements.txt. |
Alignment with DCAT-AP
The UK profile keeps every mandatory property of DCAT-AP 3.0.1V, so any record that conforms here is a valid DCAT-AP record for those properties. It adds UK requirements on top.
| Class | Mandatory in DCAT-AP 3.0.1 | Mandatory here too | Also mandatory in the UK |
|---|---|---|---|
| Catalogue | Publisher, Description, Title | Yes | None |
| Catalogue record | Last updated, Describes | Yes | None |
| Dataset | Title, Description | Yes | Identifier, Publisher, Contact point, Access rights, Security classification, Licence, Update frequency |
| Dataset series | Title, Description | Yes | None |
| Distribution | Access address | Yes | None |
| Data service | Title, Endpoint address | Yes | Description, Identifier, Publisher, Contact point, Access rights, Security classification, Licence, Status |
| Organisation | Name | Yes | None |
| Checksum | Algorithm, Checksum value | Yes | None |
| Relationship | Role, Related resource | Yes | None |
The 2026 guidance for critical data assets
Recording metadata to describe critical data assetsV. The guidance does not label every attribute; the obligations here follow its wording and its list of mandatory information.
| Guidance attribute | DCAT-AP-UK property | Obligation here |
|---|---|---|
title | Title | Dataset: Mandatory; Data service: Mandatory; Distribution: Optional |
description | Description | Dataset: Mandatory; Data service: Mandatory; Distribution: Recommended |
alternativeTitle | Alternative title | Dataset: Optional |
identifier | Identifier | Dataset: Mandatory; Data service: Mandatory; Distribution: Optional |
creator | Creator | Dataset: Recommended (M for critical data assets); Data service: Optional |
accessRights | Access rights | Dataset: Mandatory; Data service: Mandatory; Distribution: Optional |
licence | Rights statement | Dataset: Conditional; Data service: Conditional |
securityClassification | Security classification | Dataset: Mandatory; Data service: Mandatory |
licence | Licence | Dataset: Mandatory; Data service: Mandatory; Distribution: Recommended |
dateCreated | Created | Dataset: Recommended (M for critical data assets) |
temporalCoverage | Time period covered | Dataset: Recommended (M for critical data assets) |
conformsTo | Conforms to | Dataset: Recommended (M for critical data assets); Data service: Recommended; Distribution: Optional |
supersededBy | Replaced by | Dataset: Optional |
expires | Expires | Dataset: Optional |
mediaType | Media type | Distribution: Recommended |
The Data Marketplace schema
Data Marketplace data catalogue metadata (JSON Schema and API)V.
| Data Marketplace | DCAT-AP-UK | IRI |
|---|---|---|
title | Title | dct:title |
description | Description | dct:description |
publisher | Publisher | dct:publisher |
creator | Creator | dct:creator |
contactPoint | Contact point | dcat:contactPoint |
accessRights | Access rights | dct:accessRights |
securityClassification | Security classification | dcatuk:securityClassification |
license | Licence | dct:license |
updateFrequency | Update frequency | dct:accrualPeriodicity |
theme | Theme | dcat:theme |
keyword | Keyword | dcat:keyword |
distribution | Distribution | dcat:distribution |
status | Status | adms:status |
accessURL | Access address | dcat:accessURL |
downloadURL | Download address | dcat:downloadURL |
mediaType | Media type | dcat:mediaType |
format | Format | dct:format |
accessService | Access service | dcat:accessService |