DCAT-AP-UK: DCAT Application Profile for the UK
Help Site map

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

The crosswalkUpdated

Download as CSV. To convert records, use Check records.

xGov MEM to DCAT-AP-UK (33 xGov MEM properties mapped, 56 new)
xGov MEMDCAT-AP-UKChangeWhy
accessRightsAccess rights dct:accessRightsCodelist mappedSame three values (OPEN, COMMERCIAL, INTERNAL), now SKOS concepts mapped to the EU access-right vocabulary used by DCAT-AP. Usage notes added (issue 60).
accessServiceAccess service dcat:accessServiceUnchanged
addressPostal address vcard:hasAddressUnchanged
alternativeTitleAlternative title dct:alternativeExample fixedThe example for alternative title used title case, which conflicted with the rule for titles (issue 76).
byteSizeSize (bytes) dcat:byteSizeUnchanged
contactNameTeam name vcard:fnDefinition fixedDefined as the team, not a person, so records survive staff changes and carry no personal data.
contactPointContact point dcat:contactPointDefinition fixedThe definition was a copy of the email definition (issue 71). It now describes the contact point as a whole.
createdCreated dct:createdUnchanged
creatorCreator dct:creatorObligation changedMandatory in the xGov MEM. Recommended in general and mandatory for critical data assets, as the April 2026 guidance lists it.
descriptionDescription dct:descriptionUnchanged
distributionDistribution dcat:distributionRange fixedWas 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.
downloadURLDownload address dcat:downloadURLUnchanged
emailTeam email address vcard:hasEmailObligation changedMandatory in the xGov MEM. Now one of two routes: a contact form or a team mailbox, with the form preferred.
endpointDescriptionEndpoint description dcat:endpointDescriptionObligation changedMandatory in the xGov MEM; recommended, as in DCAT-AP.
endpointURLEndpoint address dcat:endpointURLObligation changedOptional 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.
identifierIdentifier dct:identifierRange relaxedWas 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.
issuedRelease date dct:issuedUnchanged
keywordKeyword dcat:keywordUnchanged
licenceLicence dct:licenseValue restoredThe 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.
mediaTypeMedia type dcat:mediaTypeObligation changedMandatory in the xGov MEM. Recommended now, as in DCAT-AP, because some distributions are web pages or services.
modifiedLast updated dct:modifiedObligation changedMandatory in the xGov MEM, but many sources do not provide it (issue 30). Recommended now, and never to be invented.
publisherPublisher dct:publisherRange changedWas 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).
relatedResourceRelated resource dct:relationUnchanged
securityClassificationSecurity classification dcatuk:securityClassificationProperty IRI fixedHad 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.
servesDataServes dataset dcat:servesDatasetRenamedRenamed to match DCAT. The property IRI was already dcat:servesDataset.
serviceStatusStatus adms:statusCodelist mappedSame phases, now SKOS concepts linked to the Service Manual.
serviceTypeInterface style dct:typeMergedThe 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.
summarySummary dct:abstractProperty IRI fixedThe xGov MEM used rdfs:comment, a generic comment property. dct:abstract is the Dublin Core term for a summary.
telephoneTelephone vcard:hasTelephoneUnchanged
themeTheme dcat:themeCodelist addedThe xGov MEM had no list of values (issue 49). The 14 data.gov.uk topics, read on 6 November 2026, are now the list.
titleTitle dct:titleUnchanged
updateFrequencyUpdate frequency dct:accrualPeriodicityCodelist mappedDublin Core frequency terms are mapped one to one to the EU frequency vocabulary that DCAT-AP requires. Old values are still accepted and converted.
versionVersion dcat:versionObligation changedMandatory in the xGov MEM; recommended now, because not every resource is versioned.
(none)Access address dcat:accessURLNewMissing from the xGov MEM. Mandatory in DCAT-AP; added so UK records harvest into European catalogues.
(none)Organisation prov:agentNew
(none)Organisation type dct:typeNew
(none)Algorithm spdx:algorithmNew
(none)Applicable legislation dcatap:applicableLegislationNew
(none)Bounding box dcat:bboxNew
(none)Centre point dcat:centroidNew
(none)Checksum spdx:checksumNew
(none)Checksum value spdx:checksumValueNew
(none)Compression format dcat:compressFormatNew
(none)Conforms to dct:conformsToNew
(none)Critical data asset dcatuk:criticalDataAssetNew
(none)Dataset dcat:datasetNew
(none)Documentation foaf:pageNew
(none)End date dcat:endDateNew
(none)Property added or changed on the way dcatuk:enrichedPropertyNew
(none)Expires schema:expiresNew
(none)Format dct:formatNew
(none)Geometry locn:geometryNew
(none)Role dcat:hadRoleNew
(none)Usage policy odrl:hasPolicyNew
(none)Contact form vcard:hasURLNew
(none)Home page foaf:homepageNew
(none)Part of series dcat:inSeriesNew
(none)Replaced by dct:isReplacedByNew
(none)Where the data is held or sent dcatuk:jurisdictionNew
(none)Landing page dcat:landingPageNew
(none)Language dct:languageNew
(none)Place name skos:prefLabelNew
(none)Who can see this record dcatuk:metadataAudienceNew
(none)Property left empty dcatuk:missingPropertyNew
(none)Why it is empty dcatuk:missingReasonNew
(none)Missing value dcatuk:missingValueNew
(none)Name foaf:nameNew
(none)Other identifier adms:identifierNew
(none)Personal data dcatuk:personalDataNew
(none)Previous version dcat:previousVersionNew
(none)Describes foaf:primaryTopicNew
(none)Responsible role prov:qualifiedAttributionNew
(none)Qualified relation dcat:qualifiedRelationNew
(none)Data quality dqv:hasQualityAnnotationNew
(none)Catalogue record dcat:recordNew
(none)Reference data used dcatuk:referenceDataNew
(none)Rights statement dct:rightsNew
(none)Sensitive data dcatuk:sensitiveDataNew
(none)Data service dcat:serviceNew
(none)Source record dct:sourceNew
(none)Geographic coverage dct:spatialNew
(none)Spatial resolution (metres) dcat:spatialResolutionInMetersNew
(none)Start date dcat:startDateNew
(none)Time period covered dct:temporalNew
(none)Time resolution dcat:temporalResolutionNew
(none)Theme list used dcat:themeTaxonomyNew
(none)Transfer safeguard dcatuk:transferMechanismNew
(none)Connection security dcatuk:transportSecurityNew
(none)Version notes adms:versionNotesNew
typeThe class (rdf:type)MergedThe 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.

Every open xGov MEM issue (22), and how it was dealt with
IssueTitleStatusHow it was dealt withWhere
#86Major overhaul tracking issue for the metadata exchange model and siteResolvedThis 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
#78Rename the repository and references to DCAT Application Profile for the UKResolvedA 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
#76Title examples in alternative title don't follow the rules for titlesResolvedExamples 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
#72Distribution is incorrectly configured as an IRI or CURIEResolvedA 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
#71The contact point definition is the same as the email definitionResolvedContact 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
#70Launch release management, lock the specification and start formal change managementResolvedSemantic 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
#69The OS postcodes example names the wrong publisherResolvedThe example is rebuilt from the public record and credits Ordnance Survey as publisher and creator.example
#63Codelist pages don't link out to external vocabulariesResolvedThe 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
#60Add usage notes to access rightsResolvedUsage notes for each value, the difference from licence and security classification, and a rights statement for anything not open.Access rights, Access rights
#49Recommend a taxonomy for theme valuesResolvedThe 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
#44What to do if there is no applicable licenceResolvedThe "data sharing agreement required" value is restored, with a rights statement to describe the agreement.Licence, Rights statement, Licences
#30What to do with assets that don't have a modified dateResolvedLast updated is recommended, not mandatory, and must never be invented. The created and release dates cover the rest.Last updated
#26Indicate whether the data includes sensitive informationResolvedA sensitive data property with a codelist (special category, criminal offence, children, commercially sensitive, security sensitive).Sensitive data, Sensitive data
#25Indicate whether the data includes personal identifiable informationResolvedA personal data property, mandatory for critical data assets, with values for none, personal, pseudonymised, anonymised and not yet known.Personal data, Personal data
#15Add a home page for the point of contactResolvedThe contact point takes a web address (vcard:hasURL), which is also the preferred route as a contact form.Contact form
#13Decide on a persistent identifier for the metadata modelNeeds the ownerw3id.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
#11Include schemas in the documentation siteResolvedJSON 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
#5Enable declaration of the metadata's access controlResolved, provisionalA "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
#4Capture the schema of the underlying datasetResolvedConforms 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
#3Capture the reference data used and its resolutionResolved, provisionalA provisional "reference data used" property that links to the classification or code list (for example age bands) and its version.Reference data used
#2Capture the temporal extent of the data resourceResolvedTime 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
#1Capture the geospatial coverage of the data resourceResolvedGeographic 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
Closed issues whose outcome the profile keeps
IssueTitleKept
#73Replace DataResource with CataloguedResource, as in DCAT 3DCAT 3 has no separate resource class in this profile; shared properties are listed on each class.
#56Potential changes to metadata standards to support APIsData services use conformsTo for the interface standard and dct:type for the interface style, as the discussion suggested.
#57Improved guidance for the mediaType propertyGuidance carried over, with IANA addresses.
#45Usage notes for the version propertyGuidance carried over.
#17accessRights should be mandatory for datasets and data servicesStill mandatory.
#6An organisation missing from the government organisations listThe list is now read from GOV.UK, with closed organisations kept and flagged so old records still resolve.
Open pull requests in the xGov MEM repository
Pull requestWhat it doesStatusWhy
#99Delete the Docker image workflowSupersededThis repository has no Docker build.
#84, 82, 90-98Ten Dependabot updates to the Python toolchain (pytest, markdown, pygments, idna, urllib3, pymdown-extensions, requests, soupsieve, setuptools, zipp, certifi)SupersededThis 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.

DCAT-AP 3.0.1 mandatory properties, and what the UK adds
ClassMandatory in DCAT-AP 3.0.1Mandatory here tooAlso mandatory in the UK
CataloguePublisher, Description, TitleYesNone
Catalogue recordLast updated, DescribesYesNone
DatasetTitle, DescriptionYesIdentifier, Publisher, Contact point, Access rights, Security classification, Licence, Update frequency
Dataset seriesTitle, DescriptionYesNone
DistributionAccess addressYesNone
Data serviceTitle, Endpoint addressYesDescription, Identifier, Publisher, Contact point, Access rights, Security classification, Licence, Status
OrganisationNameYesNone
ChecksumAlgorithm, Checksum valueYesNone
RelationshipRole, Related resourceYesNone

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.

Attributes in "Recording metadata to describe critical data assets" (16 April 2026)
Guidance attributeDCAT-AP-UK propertyObligation here
titleTitleDataset: Mandatory; Data service: Mandatory; Distribution: Optional
descriptionDescriptionDataset: Mandatory; Data service: Mandatory; Distribution: Recommended
alternativeTitleAlternative titleDataset: Optional
identifierIdentifierDataset: Mandatory; Data service: Mandatory; Distribution: Optional
creatorCreatorDataset: Recommended (M for critical data assets); Data service: Optional
accessRightsAccess rightsDataset: Mandatory; Data service: Mandatory; Distribution: Optional
licenceRights statementDataset: Conditional; Data service: Conditional
securityClassificationSecurity classificationDataset: Mandatory; Data service: Mandatory
licenceLicenceDataset: Mandatory; Data service: Mandatory; Distribution: Recommended
dateCreatedCreatedDataset: Recommended (M for critical data assets)
temporalCoverageTime period coveredDataset: Recommended (M for critical data assets)
conformsToConforms toDataset: Recommended (M for critical data assets); Data service: Recommended; Distribution: Optional
supersededByReplaced byDataset: Optional
expiresExpiresDataset: Optional
mediaTypeMedia typeDistribution: Recommended

The Data Marketplace schema

Data Marketplace data catalogue metadata (JSON Schema and API)V.

Data Marketplace JSON Schema properties (co-cddo/data-catalogue-metadata, read 6 November 2026)
Data MarketplaceDCAT-AP-UKIRI
titleTitledct:title
descriptionDescriptiondct:description
publisherPublisherdct:publisher
creatorCreatordct:creator
contactPointContact pointdcat:contactPoint
accessRightsAccess rightsdct:accessRights
securityClassificationSecurity classificationdcatuk:securityClassification
licenseLicencedct:license
updateFrequencyUpdate frequencydct:accrualPeriodicity
themeThemedcat:theme
keywordKeyworddcat:keyword
distributionDistributiondcat:distribution
statusStatusadms:status
accessURLAccess addressdcat:accessURL
downloadURLDownload addressdcat:downloadURL
mediaTypeMedia typedcat:mediaType
formatFormatdct:format
accessServiceAccess servicedcat:accessService

Search the portal

Keyboard shortcuts

/ or Ctrl K
Search
?
These shortcuts
Esc
Close menus, tooltips and dialogs
Arrow keys
Move between tabs and search results