The profile
Every property
Updated 8 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
All 89 properties in alphabetical order, with what they mean, why they matter, how to fill them in and where they came from.
A
Access address dcat:accessURL
A web address that gives access to the distribution, such as a landing page, a download page or an API.
- IRI
dcat:accessURL- Value
- url
- Why it matters
- The one address every distribution must have, so people can always get to it.
- Not to be confused with
- Download address, which is a direct link to a file.
- Since the xGov MEM
- New. Missing from the xGov MEM. Mandatory in DCAT-AP; added so UK records harvest into European catalogues.
- Also known as
- Data Marketplace:
accessURL; schema.org:urlK - Used on
- Distribution
Access rights dct:accessRights
Who can get the data, and on what terms.
- IRI
dct:accessRights- Value
- concept, from Access rights
- Why it matters
- Tells people at once whether they can have the data and how to ask for it.
- Not to be confused with
- Licence (what you may do with it once you have it) and security classification (how it must be protected).
- How to fill it in
- Choose open when anyone can have it without asking; commercial when it is available for a fee or under commercial terms; internal when it is only available to the public sector, or to named organisations, under an agreement. Say what the restriction is in the rights statement when it is not open.
- Example
ukcl:access-rights/open- Since the xGov MEM
- 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).
- Also known as
- 2026 guidance:
accessRights; Data Marketplace:accessRights - Backlog
- #60 #5
- Used on
- Dataset, Data service, Distribution
Access service dcat:accessService
A data service that gives access to this distribution.
- IRI
dcat:accessService- Value
- iri
- Since the xGov MEM
- Unchanged
- Also known as
- Data Marketplace:
accessService - Used on
- Distribution
Algorithm spdx:algorithm
The algorithm used to calculate the checksum, from the SPDX list.
- IRI
spdx:algorithm- Value
- concept, from Checksum algorithms
- Why it matters
- Lets people check a file with the same algorithm, and lets owners find files still checked with weak algorithms.
- How to fill it in
- Use SHA-256 or stronger. For files that must stay trustworthy for many years, prefer SHA-384, SHA-512 or SHA3. MD5 and SHA-1 are accepted so old records still conform, but the validator warns about them (rule Q-01): they are broken against deliberate tampering today. Quantum computers do not break these hash functions in the way they break public-key cryptography; see the quantum-ready page.
- Example
spdx:checksumAlgorithm_sha256- Since the xGov MEM
- New
- Used on
- Checksum
Alternative title dct:alternative
Another name the resource is known by, such as an abbreviation or a former name.
- IRI
dct:alternative- Value
- text
- Why it matters
- Helps people who know the resource by an informal name to find it.
- Not to be confused with
- Title, the formal name.
- How to fill it in
- Follow the same rules as the title, including sentence case. Do not repeat the title.
- Example
Code-Point Open- Since the xGov MEM
- Example fixed (was
alternativeTitle). The example for alternative title used title case, which conflicted with the rule for titles (issue 76). - Also known as
- 2026 guidance:
alternativeTitle; schema.org:alternateNameK - Backlog
- #76
- Used on
- Dataset
Applicable legislation dcatap:applicableLegislation
Legislation that requires, governs or permits the publication or sharing of the resource.
- IRI
dcatap:applicableLegislation- Value
- iri
- Why it matters
- Shows the legal basis at once, and lets catalogues group resources by the law that applies, as DCAT-AP 3 does.
- Not to be confused with
- Rights statement (what a person must do to get the data) and conforms to (a technical standard the data follows).
- How to fill it in
- Give the legislation.gov.uk address of the Act or regulation, for example https://www.legislation.gov.uk/ukpga/2017/30 for the Digital Economy Act 2017. For EU law, give its European Legislation Identifier (ELI) address. Give one value per law.
- Example
https://www.legislation.gov.uk/ukpga/2017/30- Since the xGov MEM
- New
- Used on
- Dataset, Data service
B
Bounding box dcat:bbox
The rectangle that contains the area, as Well-Known Text in WGS 84.
C
Catalogue record dcat:record
A record describing an entry in the catalogue.
- IRI
dcat:record- Value
- iri
- Since the xGov MEM
- New
- Used on
- Catalogue
Centre point dcat:centroid
The centre point of the area, as Well-Known Text.
Checksum spdx:checksum
A value that lets people check the file they downloaded is complete and unchanged.
- IRI
spdx:checksum- Value
- object: Checksum
- Since the xGov MEM
- New
- Used on
- Distribution
Checksum value spdx:checksumValue
The checksum, in lower-case hexadecimal.
- IRI
spdx:checksumValue- Value
- literal
- Since the xGov MEM
- New
- Used on
- Checksum
Compression format dcat:compressFormat
The format the file is compressed in, as an IANA media type.
- IRI
dcat:compressFormat- Value
- iri
- Since the xGov MEM
- New
- Used on
- Distribution
Conforms to dct:conformsTo
A standard, specification or schema the resource follows.
- IRI
dct:conformsTo- Value
- iri
- Why it matters
- Tells technical users how the data is structured before they get it, and lets tools check it.
- How to fill it in
- For a dataset, link to its schema (for example a CSV on the Web metadata file, a JSON Schema or an XML schema) or the data standard it follows. Tabular data should follow the Tabular data standard. For a data service, link to the standard the interface follows (for example OpenAPI 3.1 or OGC API - Features), not the data.
- Example
https://www.gov.uk/government/publications/recommended-open-standards-for-government/tabular-data-standard- Since the xGov MEM
- New
- Also known as
- 2026 guidance:
conformsTo; schema.org:conformsTo (dct)K - Backlog
- #4 #56
- Used on
- Dataset, Data service, Distribution, Catalogue, Catalogue record
Connection security Provisional dcatuk:transportSecurity
The kind of key exchange the service's endpoint uses to protect data in transit, classical or post-quantum.
- IRI
dcatuk:transportSecurity- Value
- concept, from Connection security
- Why it matters
- Turns the catalogue into part of the cryptographic inventory the NCSC asks organisations to build by 2028, so services still using only classical key exchange can be found and migrated.
- How to fill it in
- Say what the endpoint negotiates today. Choose hybrid when it offers a post-quantum key exchange (ML-KEM, FIPS 203) alongside a classical one. Update it when the service changes. This describes the service; it does not make it secure.
- Example
ukcl:transport-security/tls13-classical- Since the xGov MEM
- New
- Used on
- Data service
Contact form vcard:hasURL
The address of a contact form or contact page for the team.
- IRI
vcard:hasURL- Value
- url
- Why it matters
- The preferred contact route. It keeps addresses private and can be pointed at a new team when things change.
- Since the xGov MEM
- New
- Backlog
- #15
- Used on
- Contact point
Contact point dcat:contactPoint
Where to ask questions about the resource or give feedback on it.
- IRI
dcat:contactPoint- Value
- object: Contact point
- Why it matters
- Gives people a route to the team that can answer questions about the resource.
- Not to be confused with
- Publisher (an organisation) and the contact point's own properties (form, email, telephone).
- How to fill it in
- Give a team, never a named person. A contact form is the preferred route: it keeps addresses private and can be moved when teams change. An address for a shared team mailbox is allowed; a personal address is not.
- Since the xGov MEM
- Definition fixed. The definition was a copy of the email definition (issue 71). It now describes the contact point as a whole.
- Also known as
- Data Marketplace:
contactPoint; schema.org:contactPoint (via publisher)K - Backlog
- #71 #15
- Used on
- Dataset, Data service, Dataset series, Catalogue
Created dct:created
The date the content of the resource was created or compiled.
- IRI
dct:created- Value
- date
- Why it matters
- Helps people judge whether the data is valid for the period they care about.
- Example
2003-04-01- Since the xGov MEM
- Unchanged
- Also known as
- 2026 guidance:
dateCreated; schema.org:dateCreatedK - Used on
- Dataset
Creator dct:creator
The organisation that created or compiled the content of the resource.
- IRI
dct:creator- Value
- object: Organisation, from GOV.UK organisations
- Why it matters
- Lets people judge how reliable the resource is and who knows most about it.
- Not to be confused with
- Publisher (who makes it available) and contact point.
- How to fill it in
- Use the same identifiers as for the publisher. A resource can have more than one creator.
- Example
https://www.gov.uk/government/organisations/ordnance-survey- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM. Recommended in general and mandatory for critical data assets, as the April 2026 guidance lists it.
- Also known as
- 2026 guidance:
creator; Data Marketplace:creator; schema.org:creatorK - Used on
- Dataset, Data service
Critical data asset dcatuk:criticalDataAsset
Whether the resource is a critical data asset under the Data Asset Management Policy.
- IRI
dcatuk:criticalDataAsset- Value
- boolean
- Why it matters
- Switches on the extra properties the policy and its guidance require, and lets departments build their return from catalogue records.
- How to fill it in
- A critical data asset is shared with another public sector organisation to deliver an essential purpose or process. Answer true or false. When true, the properties marked "mandatory for critical data assets" must be given.
- Example
true- Since the xGov MEM
- New
- Used on
- Dataset, Data service
D
Data quality dqv:hasQualityAnnotation
A link to a published statement or measurement of the quality of the data.
- IRI
dqv:hasQualityAnnotation- Value
- iri
- Why it matters
- Lets people see how fit the data is for their use, and lets the Data Quality Commons tools read it.
- How to fill it in
- Link to a data quality report, a Data Quality Vocabulary measurement or a quality action plan.
- Since the xGov MEM
- New
- Used on
- Dataset
Data service dcat:service
A data service listed in the catalogue.
- IRI
dcat:service- Value
- iri
- Since the xGov MEM
- New
- Used on
- Catalogue
Dataset dcat:dataset
A dataset listed in the catalogue.
- IRI
dcat:dataset- Value
- iri
- Since the xGov MEM
- New
- Used on
- Catalogue
Describes foaf:primaryTopic
The dataset or data service this record describes.
- IRI
foaf:primaryTopic- Value
- iri
- Since the xGov MEM
- New
- Used on
- Catalogue record
Description dct:description
A plain English account of what the resource contains and what it can be used for.
- IRI
dct:description- Value
- text
- Why it matters
- Lets people decide whether the resource answers their question before they ask for it.
- Not to be confused with
- Abstract (a one-sentence summary for search results) and keyword (single words or phrases).
- How to fill it in
- Say what the data is about, who or what it covers, how it was collected and what it is good for. Put warnings about use in the access rights or the licence, not here.
- Example
The location of every postcode unit in Great Britain, as a single point, with the local authority and ward it falls in.- Since the xGov MEM
- Unchanged
- Also known as
- 2026 guidance:
description; Data Marketplace:description; schema.org:descriptionK - Used on
- Dataset, Data service, Distribution, Dataset series, Catalogue
Distribution dcat:distribution
A form in which the data can be got, such as a file or an API.
- IRI
dcat:distribution- Value
- object: Distribution
- Why it matters
- Tells people how to get the data and in what format.
- How to fill it in
- Describe each format separately. A distribution can be described in the same record or referred to by its identifier.
- Since the xGov MEM
- 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.
- Also known as
- Data Marketplace:
distribution; schema.org:distributionK - Backlog
- #72
- Used on
- Dataset
Documentation foaf:page
A web page that documents the resource, such as a user guide or a methodology.
- IRI
foaf:page- Value
- url
- Since the xGov MEM
- New
- Used on
- Dataset, Data service
Download address dcat:downloadURL
A direct link to a file.
- IRI
dcat:downloadURL- Value
- url
- Since the xGov MEM
- Unchanged
- Also known as
- Data Marketplace:
downloadURL; schema.org:contentUrlK - Used on
- Distribution
E
End date dcat:endDate
The last day the data covers.
- IRI
dcat:endDate- Value
- date
- Since the xGov MEM
- New
- Backlog
- #2
- Used on
- Period of time
Endpoint address dcat:endpointURL
The root address of the service.
- IRI
dcat:endpointURL- Value
- url
- Why it matters
- Where systems send requests.
- How to fill it in
- For a service that is not public, give the address of its API gateway or developer portal rather than an internal host name: publishing internal host names helps attackers.
- Since the xGov MEM
- 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.
- Used on
- Data service
Endpoint description dcat:endpointDescription
A description of what the service does and how to call it, such as an OpenAPI document.
- IRI
dcat:endpointDescription- Value
- url
- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM; recommended, as in DCAT-AP.
- Used on
- Data service
Expires schema:expires
The date after which the resource should no longer be used.
- IRI
schema:expires- Value
- date
- Since the xGov MEM
- New
- Also known as
- 2026 guidance:
expires; schema.org:expiresK - Used on
- Dataset
F
Format dct:format
The file type, from the EU file type list, where there is no IANA media type.
- IRI
dct:format- Value
- iri
- Since the xGov MEM
- New
- Also known as
- Data Marketplace:
format - Used on
- Distribution
G
Geographic coverage dct:spatial
The geographic area the data is about.
- IRI
dct:spatial- Value
- object: Location
- Why it matters
- Lets people find data for a place, and see at a glance whether it covers the area they need.
- How to fill it in
- Prefer the identifier of a standard area: a GSS code from the ONS (for example K02000001 for the United Kingdom) for statistical and administrative areas, or another controlled list such as national parks. Use a bounding box or a geometry only where no named area fits. Say whether the data covers the whole area or only some places in it (issue 1). For geospatial data, also follow UK GEMINI.
- Example
http://statistics.data.gov.uk/id/statistical-geography/K03000001- Since the xGov MEM
- New
- Also known as
- schema.org:
spatialCoverageK - Backlog
- #1
- Used on
- Dataset, Dataset series, Catalogue
Geometry locn:geometry
The exact shape of the area, as Well-Known Text.
H
Home page foaf:homepage
The home page of the catalogue or the organisation.
- IRI
foaf:homepage- Value
- url
- Since the xGov MEM
- New
- Backlog
- #15
- Used on
- Catalogue, Organisation
I
Identifier dct:identifier
The main identifier of the resource in the publisher's own catalogue.
- IRI
dct:identifier- Value
- literal
- Why it matters
- Lets systems tell records apart, avoid duplicates and link to the same resource across catalogues.
- Not to be confused with
- The record's web address (its IRI), which should also be stable, and other identifiers (use "other identifier").
- How to fill it in
- Use an identifier that will not change, even if the resource moves or the organisation is reorganised. Opaque, non-sequential identifiers are best. Do not reuse an identifier for a different resource.
- Example
2dfb82b4-741a-4b93-807e-11abb4bb0875- Since the xGov MEM
- 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.
- Also known as
- 2026 guidance:
identifier; schema.org:identifierK - Used on
- Dataset, Data service, Distribution, Organisation
Interface style dct:type
For a data service, the kind of interface.
- IRI
dct:type- Value
- concept, from Interface style
- How to fill it in
- The class of the record (dataset, data service) is given by its RDF type and is not repeated here. For a data service, use this property for the interface style, and conformsTo for the exact standard.
- Example
ukcl:service-type/rest- Since the xGov MEM
- 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.
- Backlog
- #56
- Used on
- Data service
K
Keyword dcat:keyword
Words or short phrases that people might search for, not already in the title or description.
- IRI
dcat:keyword- Value
- text
- Why it matters
- Adds ways for people to find the resource.
- Example
postcode- Since the xGov MEM
- Unchanged
- Also known as
- Data Marketplace:
keyword; schema.org:keywordsK - Used on
- Dataset, Data service
L
Landing page dcat:landingPage
A web page where people can find out about the resource and how to get it.
- IRI
dcat:landingPage- Value
- url
- Why it matters
- Gives people somewhere to go that will still work if a download link changes.
- Since the xGov MEM
- New
- Also known as
- schema.org:
urlK - Used on
- Dataset, Data service
Language dct:language
The language or languages of the resource.
- IRI
dct:language- Value
- concept, from Language
- Why it matters
- Lets people find data in Welsh, Gaelic, Irish or other languages, and supports bodies with language duties.
- How to fill it in
- Give every language the resource is available in.
- Example
eulang:ENG- Since the xGov MEM
- New
- Also known as
- schema.org:
inLanguageK - Used on
- Dataset, Data service, Distribution, Catalogue
Last updated dct:modified
The date the content of the resource last changed.
- IRI
dct:modified- Value
- date
- Why it matters
- Helps people judge whether the data is current enough for their use.
- Not to be confused with
- The date the metadata record changed, which belongs on the catalogue record.
- How to fill it in
- Give it whenever you know it. If you do not know it, leave it out rather than using the date the record was harvested: a false date is worse than none (issue 30).
- Example
2026-08-01- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM, but many sources do not provide it (issue 30). Recommended now, and never to be invented.
- Also known as
- schema.org:
dateModifiedK - Backlog
- #30
- Used on
- Dataset, Data service, Distribution, Dataset series, Catalogue, Catalogue record
Licence dct:license
The licence under which the resource can be used.
- IRI
dct:license- Value
- iri, from Licences
- Why it matters
- Tells people what they may do with the data once they have it.
- Not to be confused with
- Access rights (whether they can have it) and rights statement (what restricts access).
- How to fill it in
- Link to the licence, for example the Open Government Licence v3.0. If there is no licence and a data sharing agreement is needed, use the value "data sharing agreement required" and describe the agreement in the rights statement.
- Example
http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/- Since the xGov MEM
- 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.
- Also known as
- 2026 guidance:
licence; Data Marketplace:license; schema.org:licenseK - Backlog
- #44
- Used on
- Dataset, Data service, Distribution, Catalogue
M
Media type dcat:mediaType
The file format, as an IANA media type.
- IRI
dcat:mediaType- Value
- iri
- Why it matters
- Tells people whether they have the software to open the file.
- How to fill it in
- Use the IANA media type address, for example https://www.iana.org/assignments/media-types/text/csv. Plain values such as text/csv are accepted and converted.
- Example
https://www.iana.org/assignments/media-types/text/csv- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM. Recommended now, as in DCAT-AP, because some distributions are web pages or services.
- Also known as
- 2026 guidance:
mediaType; Data Marketplace:mediaType; schema.org:encodingFormatK - Used on
- Distribution
Missing value dcatuk:missingValueNew
A property this record leaves empty on purpose, and why.
- IRI
dcatuk:missingValue- Value
- object: Missing value
- Why it matters
- Lets a strict harvester tell a value that is unknown, withheld or not applicable from one that was simply forgotten, without guessing.
- Not to be confused with
- Leaving the property out, which says nothing about why it is empty.
- How to fill it in
- Use it for recommended or optional properties you cannot give. It never satisfies a mandatory property, which must have a value; the validator warns if you try (rule Q-02). Say withheld only when a value exists but cannot be published in this record.
- Example
{"missingProperty": "dct:temporal", "missingReason": "unknown"}- Since the xGov MEM
- New
- Used on
- Dataset, Data service, Catalogue record
N
Name foaf:name
The name of the organisation.
- IRI
foaf:name- Value
- text
- Since the xGov MEM
- New
- Used on
- Organisation
O
Organisation prov:agent
The organisation that plays the role.
- IRI
prov:agent- Value
- iri
- Since the xGov MEM
- New
- Used on
- Responsible role
Organisation type dct:type
The kind of organisation, as GOV.UK lists it, for example ministerial department or executive agency.
- IRI
dct:type- Value
- literal
- Since the xGov MEM
- New
- Used on
- Organisation
Other identifier adms:identifier
Any other identifier the resource is known by, such as one in a national or sector register.
- IRI
adms:identifier- Value
- literal
- Why it matters
- Joins records about the same resource held in different catalogues.
- How to fill it in
- Record every identifier you know about, for example a data.gov.uk dataset identifier or a register entry.
- Since the xGov MEM
- New
- Used on
- Dataset
P
Part of series dcat:inSeries
The dataset series this dataset belongs to.
Personal data dcatuk:personalData
Whether the data contains information about identifiable living people, and in what form.
- IRI
dcatuk:personalData- Value
- concept, from Personal data
- Why it matters
- Lets people see early whether a data protection impact assessment and a lawful basis will be needed.
- How to fill it in
- Answer for the data, not the metadata. Choose unknown only while you find out, and say who is finding out in the rights statement.
- Example
ukcl:personal-data/none- Since the xGov MEM
- New
- Backlog
- #25
- Used on
- Dataset, Data service
Place name skos:prefLabel
The name of the place, from a gazetteer where there is one.
Postal address vcard:hasAddress
A postal address for the team.
- IRI
vcard:hasAddress- Value
- literal
- Since the xGov MEM
- Unchanged (was
address) - Used on
- Contact point
Previous version dcat:previousVersion
The version this one replaces in a sequence.
- IRI
dcat:previousVersion- Value
- iri
- Since the xGov MEM
- New
- Used on
- Dataset
Property added or changed on the way dcatuk:enrichedPropertyNew
A property whose value was added or changed by the harvester or converter, rather than taken from the source record.
- IRI
dcatuk:enrichedProperty- Value
- iri
- Why it matters
- Shows which values the original publisher did not give, so nobody is held accountable for, or misled by, values someone else added.
- How to fill it in
- Give the property's prefixed name, such as dcat:theme, once for each property the harvester filled or changed.
- Example
dcat:theme- Since the xGov MEM
- New
- Used on
- Catalogue record
Property left empty dcatuk:missingPropertyNew
The property that has no value, as its prefixed name or full IRI.
- IRI
dcatuk:missingProperty- Value
- iri
- How to fill it in
- Use the name as it appears on the property's page, such as dct:temporal or dcat:spatialResolutionInMeters.
- Example
dct:temporal- Since the xGov MEM
- New
- Used on
- Missing value
Publisher dct:publisher
The organisation responsible for making the resource available.
- IRI
dct:publisher- Value
- object: Organisation, from GOV.UK organisations
- Why it matters
- Says who is accountable for the resource being available, and to whom questions about access go.
- Not to be confused with
- Creator (who made the content) and contact point (where to send questions).
- How to fill it in
- Use the organisation's GOV.UK organisation address (for example https://www.gov.uk/government/organisations/ordnance-survey), or the equivalent register entry for a body that is not on GOV.UK. Never name a person.
- Example
https://www.gov.uk/government/organisations/ordnance-survey- Since the xGov MEM
- 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).
- Also known as
- Data Marketplace:
publisher; schema.org:publisherK - Backlog
- #69
- Used on
- Dataset, Data service, Dataset series, Catalogue
Q
Qualified relation dcat:qualifiedRelation
A related resource together with the kind of relationship.
- IRI
dcat:qualifiedRelation- Value
- object: Relationship
- Since the xGov MEM
- New
- Used on
- Dataset
R
Reference data used Provisional dcatuk:referenceData
A code list, classification or set of groupings the data uses, such as age bands or a geography.
- IRI
dcatuk:referenceData- Value
- iri
- Why it matters
- Lets people see whether two datasets can be compared or joined, because they use the same groupings.
- How to fill it in
- Provisional. Link to the classification or code list, with its version, for example a published age band classification (issue 3).
- Since the xGov MEM
- New
- Backlog
- #3
- Used on
- Dataset
Related resource dct:relation
Another resource closely related to this one, such as the report the data supports.
- IRI
dct:relation- Value
- iri
- Since the xGov MEM
- Unchanged (was
relatedResource) - Used on
- Dataset, Relationship
Release date dct:issued
The date the resource was first made available.
- IRI
dct:issued- Value
- date
- Why it matters
- Helps people judge how current it is.
- How to fill it in
- Use ISO 8601. Include a time with Z or an offset if you release more than one version a day.
- Example
2022-02-01- Since the xGov MEM
- Unchanged
- Also known as
- schema.org:
datePublishedK - Used on
- Dataset, Data service, Distribution, Catalogue, Catalogue record
Replaced by dct:isReplacedBy
A newer resource that replaces this one.
- IRI
dct:isReplacedBy- Value
- iri
- Why it matters
- Stops people using an out-of-date resource.
- Since the xGov MEM
- New
- Also known as
- 2026 guidance:
supersededBy; schema.org:(none)K - Used on
- Dataset
Responsible role prov:qualifiedAttribution
An organisation and the role it plays for the resource, such as data owner or data steward.
- IRI
prov:qualifiedAttribution- Value
- object: Responsible role
- Why it matters
- Records accountability as the Data Asset Management Policy asks, without naming people.
- How to fill it in
- Name a role and an organisation, never a person. People change jobs; roles survive reorganisation.
- Since the xGov MEM
- New
- Used on
- Dataset
Rights statement dct:rights
A statement of any restriction on access or use, such as the data sharing agreement or legal gateway needed.
- IRI
dct:rights- Value
- text
- Why it matters
- Explains what a person must do to get data that is not open.
- How to fill it in
- Name the kind of agreement and the legal basis, for example a data sharing agreement under the Digital Economy Act 2017. Link to the process for asking.
- Since the xGov MEM
- New
- Also known as
- 2026 guidance:
licence - Backlog
- #44
- Used on
- Dataset, Data service
Role dcat:hadRole
The role in the relationship or attribution.
- IRI
dcat:hadRole- Value
- concept, from Responsible role
- Since the xGov MEM
- New
- Used on
- Relationship, Responsible role
S
Security classification dcatuk:securityClassificationUpdated
The classification under the Government Security Classifications Policy that the data itself carries.
- IRI
dcatuk:securityClassification- Value
- concept, from Security classification
- Why it matters
- Stops data being shared with people or systems that cannot protect it, and keeps catalogues in scope.
- Not to be confused with
- Access rights (who may have it). On a catalogue record the same property gives the classification of the record itself, which is usually OFFICIAL even when the data is not (RQ-03).
- How to fill it in
- Most public sector data is OFFICIAL. Use the OFFICIAL-SENSITIVE marking where it applies. Records about SECRET or TOP SECRET data must not be put in an OFFICIAL catalogue; the Data Asset Management Policy covers OFFICIAL assets only.
- Example
ukcl:security-classification/official- Since the xGov MEM
- 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.
- Also known as
- 2026 guidance:
securityClassification; Data Marketplace:securityClassification - Used on
- Dataset, Data service, Catalogue record
Sensitive data dcatuk:sensitiveData
Whether the data contains information that needs extra care beyond being personal, such as special category data.
- IRI
dcatuk:sensitiveData- Value
- concept, from Sensitive data
- Why it matters
- Supports the data share request process, which handles sensitive data differently.
- How to fill it in
- Choose every value that applies.
- Example
ukcl:sensitive-data/none- Since the xGov MEM
- New
- Backlog
- #26
- Used on
- Dataset
Serves dataset dcat:servesDataset
A dataset this service gives access to.
- IRI
dcat:servesDataset- Value
- iri
- Since the xGov MEM
- Renamed (was
servesData). Renamed to match DCAT. The property IRI was already dcat:servesDataset. - Used on
- Data service
Size (bytes) dcat:byteSize
The size of the file in bytes.
- IRI
dcat:byteSize- Value
- integer
- Example
14330000- Since the xGov MEM
- Unchanged
- Also known as
- schema.org:
contentSizeK - Used on
- Distribution
Source record dct:sourceNew
The original metadata record this record was harvested or converted from.
- IRI
dct:source- Value
- iri
- Why it matters
- Lets anyone go back to the authoritative description, and stops a harvested copy from being mistaken for the original.
- Not to be confused with
- Describes (the dataset or service), and the dataset's own provenance, which is about the data rather than the record.
- How to fill it in
- Give the web address of the record in the catalogue it came from. DCAT-AP uses the same property for source metadata (RQ-08).
- Example
https://example.org/catalogue/record/road-casualties- Since the xGov MEM
- New
- Used on
- Catalogue record
Spatial resolution (metres) dcat:spatialResolutionInMeters
The smallest distance the data can tell apart, in metres.
Start date dcat:startDate
The first day the data covers.
- IRI
dcat:startDate- Value
- date
- Example
2021-03-21- Since the xGov MEM
- New
- Backlog
- #2
- Used on
- Period of time
Status adms:status
Where a data service is in its life, from discovery to retirement.
- IRI
adms:status- Value
- concept, from Service status
- Example
ukcl:service-status/live- Since the xGov MEM
- Codelist mapped. Same phases, now SKOS concepts linked to the Service Manual.
- Also known as
- Data Marketplace:
status - Used on
- Data service
Summary dct:abstract
A one-sentence summary of the resource, of no more than 250 characters.
- IRI
dct:abstract- Value
- text
- Why it matters
- Shown in lists of search results, where the full description is too long.
- Not to be confused with
- Description, which gives the full account.
- How to fill it in
- If you leave it out, catalogues may show the start of the description instead.
- Example
Free point locations for every postcode in Great Britain.- Limit
- 250 characters
- Since the xGov MEM
- Property IRI fixed (was
summary). The xGov MEM used rdfs:comment, a generic comment property. dct:abstract is the Dublin Core term for a summary. - Also known as
- schema.org:
abstractK - Used on
- Dataset, Data service
T
Team email address vcard:hasEmail
A shared team mailbox, as a mailto address. Never a personal address.
- IRI
vcard:hasEmail- Value
- How to fill it in
- Prefer a contact form. If you give an address, it must be a shared mailbox that will outlive any one person.
- Since the xGov MEM
- Obligation changed (was
email). Mandatory in the xGov MEM. Now one of two routes: a contact form or a team mailbox, with the form preferred. - Used on
- Contact point
Team name vcard:fn
The name of the team to contact. Never a person's name.
- IRI
vcard:fn- Value
- literal
- Since the xGov MEM
- Definition fixed (was
contactName). Defined as the team, not a person, so records survive staff changes and carry no personal data. - Backlog
- #71
- Used on
- Contact point
Telephone vcard:hasTelephone
A team telephone number.
- IRI
vcard:hasTelephone- Value
- literal
- Since the xGov MEM
- Unchanged (was
telephone) - Used on
- Contact point
Theme dcat:theme
The broad subject of the resource, from a controlled list.
- IRI
dcat:theme- Value
- concept, from Theme
- Why it matters
- Lets people browse by subject, and catalogues group the same subjects across publishers.
- Not to be confused with
- Keyword, which is free text.
- How to fill it in
- Choose one or more themes from the DCAT-AP-UK theme list, which uses the data.gov.uk topics. Each is mapped to the EU data themes, so records also make sense to European tools. The cross-government taxonomy from the master and reference data working group will replace or extend it when it is published (issue 49).
- Example
ukcl:theme/mapping- Since the xGov MEM
- 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.
- Also known as
- Data Marketplace:
theme; schema.org:aboutK - Backlog
- #49
- Used on
- Dataset, Data service, Dataset series
Theme list used dcat:themeTaxonomy
The list of themes the catalogue uses to classify its records.
- IRI
dcat:themeTaxonomy- Value
- iri
- Since the xGov MEM
- New
- Used on
- Catalogue
Time period covered dct:temporal
The period of time the data is about.
- IRI
dct:temporal- Value
- object: Period of time
- Why it matters
- Lets people find data for the years they need. It is not the date the data was published.
- How to fill it in
- Give a start date, an end date, or both. An open-ended period has only a start date. Each census is its own dataset in a series.
- Since the xGov MEM
- New
- Also known as
- 2026 guidance:
temporalCoverage; schema.org:temporalCoverageK - Backlog
- #2
- Used on
- Dataset, Dataset series
Time resolution dcat:temporalResolution
The smallest period the data can tell apart, as an ISO 8601 duration.
Title dct:title
The name of the resource, in plain English.
- IRI
dct:title- Value
- text
- Why it matters
- Helps people find and recognise the resource in search results.
- Not to be confused with
- Alternative title (a shorter or informal name) and identifier (a code, not a name).
- How to fill it in
- Use sentence case. Include the topic and, where it helps, the place and period. Avoid acronyms and jargon, or spell them out. Give a Welsh title too where the publisher has Welsh language duties, tagged with the language.
- Example
Postcode locations for Great Britain- Since the xGov MEM
- Unchanged
- Also known as
- 2026 guidance:
title; Data Marketplace:title; schema.org:nameK - Backlog
- #76
- Used on
- Dataset, Data service, Distribution, Dataset series, Catalogue
Transfer safeguard Provisional dcatuk:transferMechanismUpdated
The basis under UK GDPR on which personal data in the resource may be sent outside the UK.
- IRI
dcatuk:transferMechanism- Value
- concept, from Transfer safeguards
- Why it matters
- Lets a person asking for data see at once whether a restricted transfer is covered, and lets catalogues report on cross-border personal data.
- How to fill it in
- Needed when the data contains personal data and is held in or sent to anywhere outside the UK (rule R-08). Follow the guidance from the Information Commission (the ICO, called the Information Commissioner's Office until 29 October 2026) on international transfers, updated on 15 January 2026. This records the basis; it is not legal advice and does not replace a transfer risk assessment.
- Example
ukcl:transfer-mechanism/uk-adequacy- Since the xGov MEM
- New
- Used on
- Dataset, Data service
U
Update frequency dct:accrualPeriodicity
How often the resource is updated.
- IRI
dct:accrualPeriodicity- Value
- concept, from Update frequency
- Why it matters
- Lets people plan when to come back, and harvesters plan when to check for changes.
- How to fill it in
- Choose from the EU frequency list that DCAT-AP uses. If it is not updated on a schedule, choose irregular; if it will never be updated, choose never.
- Example
eufreq:QUARTERLY- Since the xGov MEM
- Codelist mapped (was
updateFrequency). 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. - Also known as
- Data Marketplace:
updateFrequency - Used on
- Dataset, Dataset series
Usage policy odrl:hasPolicyUpdated
A machine-readable policy, in the W3C Open Digital Rights Language (ODRL), saying what may and may not be done with the resource.
- IRI
odrl:hasPolicy- Value
- iri
- Why it matters
- Lets software, including AI systems and data space connectors, read permissions and prohibitions without a person reading the licence: for example whether the data may be used to train AI models.
- Not to be confused with
- Licence (the legal document) and rights statement (words for people). The policy expresses them for machines; it does not replace them.
- How to fill it in
- Give the web address of a published ODRL policy. Start from the policy templates on the AI-ready page. Where a licence and a policy disagree, the licence wins: say so in the rights statement.
- Example
https://cyberdudeuk.github.io/dcat-ap-uk/downloads/policies/ogl-open.jsonld- Since the xGov MEM
- New
- Used on
- Dataset, Data service, Distribution
V
Version dcat:version
The version of the resource.
- IRI
dcat:version- Value
- literal
- Why it matters
- Lets people tell versions apart and cite the one they used.
- How to fill it in
- Follow the resource's own versioning scheme, such as a semantic version or a release date in the form yyyy-mm-dd.
- Example
2026-08- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM; recommended now, because not every resource is versioned.
- Also known as
- schema.org:
versionK - Used on
- Dataset, Data service
Version notes adms:versionNotes
What changed in this version.
- IRI
adms:versionNotes- Value
- text
- Since the xGov MEM
- New
- Used on
- Dataset
W
Where the data is held or sent Provisional dcatuk:jurisdiction
Every country or territory where the data is stored or processed, or to which it is sent.
- IRI
dcatuk:jurisdiction- Value
- concept, from Jurisdictions
- Why it matters
- Makes cross-border flows visible before anyone asks for the data, so the right transfer safeguards can be checked. Covers the UK nations, the Crown Dependencies, the British Overseas Territories, the Commonwealth and any other country.
- Not to be confused with
- Spatial coverage (the places the data is about). Data about Wales may be held in Ireland.
- How to fill it in
- Choose every place that applies, including where a supplier or cloud region holds it. Use the UK nations when it stays in the UK. For a country not on the list, use its ISO 3166-1 code in the same form, for example ukcl:jurisdiction/br.
- Example
ukcl:jurisdiction/gb-eng- Since the xGov MEM
- New
- Used on
- Dataset, Data service
Who can see this record Provisional dcatuk:metadataAudience
Who is allowed to see the metadata record itself.
- IRI
dcatuk:metadataAudience- Value
- concept, from Who can see this record
- Why it matters
- Lets internal records be harvested into shared catalogues while keeping them away from people who should not see them.
- Not to be confused with
- Access rights, which are about the data, not the record.
- How to fill it in
- Provisional. The levels are a starting point for research with catalogue owners and information assurance (issue 5).
- Since the xGov MEM
- New
- Backlog
- #5
- Used on
- Dataset, Data service, Catalogue record
Why it is empty dcatuk:missingReasonNew
The reason the property has no value, from a list based on the GML and INSPIRE nil reasons.
- IRI
dcatuk:missingReason- Value
- concept, from Reasons a value is missing
- How to fill it in
- Choose the most specific reason. Withheld says a value exists but is not divulged in this record.
- Example
ukcl:missing-reason/unknown- Since the xGov MEM
- New
- Used on
- Missing value