Class · Recommended
Data service
Updated 14 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
A set of operations, such as an API, that gives access to one or more datasets or data processing functions.
How it connectsUpdated
The data service in the middle; on the left, what links to it; on the right, what it links to. Under the map, the lists its values come from.
- CLASS · MANDATORY a mandatory class
- CLASS another class
- links to, named on the line
Select a card for its details. Line labels name the properties that make each link.
The map as a list
- Catalogue links to Data service by service
- Distribution links to Data service by access service
- Data service links to Organisation by publisher, creator
- Data service links to Contact point by contact point
- Data service links to Dataset by serves
- Data service links to Missing value by missing value
Values for 13 of its properties come from these lists:
- GOV.UK organisations
- Access rights
- Security classification
- Licences
- Service status
- Interface style
- Theme
- Language
- Personal data
- Who can see this record
- Jurisdictions
- Transfer safeguards
- Connection security
PropertiesUpdated
What a record of this kind can say, grouped by whether it must, should or may be filled in. Select a name for how to fill it in.
Mandatory (10)New
| Name | What it is | Value | How many |
|---|---|---|---|
| Title | The name of the resource, in plain English. | text | 1..n |
| Description | A plain English account of what the resource contains and what it can be used for. | text | 1..n |
| Identifier | The main identifier of the resource in the publisher's own catalogue. | literal | 1 |
| Endpoint address | The root address of the service. | url | 1..n |
| Publisher | The organisation responsible for making the resource available. | object: Organisation | 1 |
| Contact point | Where to ask questions about the resource or give feedback on it. | object: Contact point | 1..n |
| Access rights | Who can get the data, and on what terms. | concept | 1 |
| Security classification | The classification under the Government Security Classifications Policy that the data itself carries. | concept | 1 |
| Licence | The licence under which the resource can be used. | iri | 1 |
| Status | Where a data service is in its life, from discovery to retirement. | concept | 1 |
Conditional (2)New
| Name | What it is | Value | How many |
|---|---|---|---|
| Rights statement | A statement of any restriction on access or use, such as the data sharing agreement or legal gateway needed. | text | 0..n |
| Transfer safeguard | The basis under UK GDPR on which personal data in the resource may be sent outside the UK. | concept | 0..n |
Recommended (8)New
| Name | What it is | Value | How many |
|---|---|---|---|
| Interface style | For a data service, the kind of interface. | concept | 0..1 |
| Conforms to | A standard, specification or schema the resource follows. | iri | 0..n |
| Endpoint description | A description of what the service does and how to call it, such as an OpenAPI document. | url | 0..n |
| Serves dataset | A dataset this service gives access to. | iri | 0..n |
| Release date | The date the resource was first made available. | date | 0..1 |
| Last updated | The date the content of the resource last changed. | date | 0..1 |
| Theme | The broad subject of the resource, from a controlled list. | concept | 0..n |
| Keyword | Words or short phrases that people might search for, not already in the title or description. | text | 0..n |
Optional (14)New
| Name | What it is | Value | How many |
|---|---|---|---|
| Critical data asset | Whether the resource is a critical data asset under the Data Asset Management Policy. | boolean | 0..1 |
| Creator | The organisation that created or compiled the content of the resource. | object: Organisation | 0..n |
| Summary | A one-sentence summary of the resource, of no more than 250 characters. | text | 0..1 |
| Version | The version of the resource. | literal | 0..1 |
| Landing page | A web page where people can find out about the resource and how to get it. | url | 0..n |
| Documentation | A web page that documents the resource, such as a user guide or a methodology. | url | 0..n |
| Language | The language or languages of the resource. | concept | 0..n |
| Personal data | Whether the data contains information about identifiable living people, and in what form. | concept | 0..1 |
| Who can see this record | Who is allowed to see the metadata record itself. | concept | 0..1 |
| Applicable legislation | Legislation that requires, governs or permits the publication or sharing of the resource. | iri | 0..n |
| Usage policy | A machine-readable policy, in the W3C Open Digital Rights Language (ODRL), saying what may and may not be done with the resource. | iri | 0..n |
| Where the data is held or sent | Every country or territory where the data is stored or processed, or to which it is sent. | concept | 0..n |
| Connection security | The kind of key exchange the service's endpoint uses to protect data in transit, classical or post-quantum. | concept | 0..1 |
| Missing value | A property this record leaves empty on purpose, and why. | object: Missing value | 0..n |
Mandatory properties in detailUpdated
Title dct:title
The name of the resource, in plain English.
- Obligation
- Mandatory
- Cardinality
- 1..n
- 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
Description dct:description
A plain English account of what the resource contains and what it can be used for.
- Obligation
- Mandatory
- Cardinality
- 1..n
- 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
Identifier dct:identifier
The main identifier of the resource in the publisher's own catalogue.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Endpoint address dcat:endpointURL
The root address of the service.
- Obligation
- Mandatory
- Cardinality
- 1..n
- 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.
Publisher dct:publisher
The organisation responsible for making the resource available.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Contact point dcat:contactPoint
Where to ask questions about the resource or give feedback on it.
- Obligation
- Mandatory
- Cardinality
- 1..n
- 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
Access rights dct:accessRights
Who can get the data, and on what terms.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Security classification dcatuk:securityClassificationUpdated
The classification under the Government Security Classifications Policy that the data itself carries.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Licence dct:license
The licence under which the resource can be used.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Status adms:status
Where a data service is in its life, from discovery to retirement.
- Obligation
- Mandatory
- Cardinality
- 1
- 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
Conditional properties in detailUpdated
Rights statement dct:rights
A statement of any restriction on access or use, such as the data sharing agreement or legal gateway needed.
- Obligation
- Conditional Mandatory when access rights are commercial or internal.
- Cardinality
- 0..n
- 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
Transfer safeguard Provisional dcatuk:transferMechanismUpdated
The basis under UK GDPR on which personal data in the resource may be sent outside the UK.
- Obligation
- Conditional Mandatory when the data contains personal data and is held in or sent to anywhere outside the UK (rule R-08).
- Cardinality
- 0..n
- 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
Recommended properties in detailUpdated
Interface style dct:type
For a data service, the kind of interface.
- Obligation
- Recommended
- Cardinality
- 0..1
- 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
Conforms to dct:conformsTo
A standard, specification or schema the resource follows.
- Obligation
- Recommended
- Cardinality
- 0..n
- 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
Endpoint description dcat:endpointDescription
A description of what the service does and how to call it, such as an OpenAPI document.
- Obligation
- Recommended
- Cardinality
- 0..n
- IRI
dcat:endpointDescription- Value
- url
- Since the xGov MEM
- Obligation changed. Mandatory in the xGov MEM; recommended, as in DCAT-AP.
Serves dataset dcat:servesDataset
A dataset this service gives access to.
- Obligation
- Recommended
- Cardinality
- 0..n
- IRI
dcat:servesDataset- Value
- iri
- Since the xGov MEM
- Renamed (was
servesData). Renamed to match DCAT. The property IRI was already dcat:servesDataset.
Release date dct:issued
The date the resource was first made available.
- Obligation
- Recommended
- Cardinality
- 0..1
- 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
Last updated dct:modified
The date the content of the resource last changed.
- Obligation
- Recommended
- Cardinality
- 0..1
- 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
Theme dcat:theme
The broad subject of the resource, from a controlled list.
- Obligation
- Recommended
- Cardinality
- 0..n
- 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
Keyword dcat:keyword
Words or short phrases that people might search for, not already in the title or description.
- Obligation
- Recommended
- Cardinality
- 0..n
- 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
Optional properties in detailUpdated
Critical data asset dcatuk:criticalDataAsset
Whether the resource is a critical data asset under the Data Asset Management Policy.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Creator dct:creator
The organisation that created or compiled the content of the resource.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
Summary dct:abstract
A one-sentence summary of the resource, of no more than 250 characters.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Version dcat:version
The version of the resource.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Landing page dcat:landingPage
A web page where people can find out about the resource and how to get it.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
Documentation foaf:page
A web page that documents the resource, such as a user guide or a methodology.
- Obligation
- Optional
- Cardinality
- 0..n
- IRI
foaf:page- Value
- url
- Since the xGov MEM
- New
Language dct:language
The language or languages of the resource.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
Personal data dcatuk:personalData
Whether the data contains information about identifiable living people, and in what form.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Who can see this record Provisional dcatuk:metadataAudience
Who is allowed to see the metadata record itself.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Applicable legislation dcatap:applicableLegislation
Legislation that requires, governs or permits the publication or sharing of the resource.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
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.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
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.
- Obligation
- Optional
- Cardinality
- 0..n
- 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
Connection security Provisional dcatuk:transportSecurity
The kind of key exchange the service's endpoint uses to protect data in transit, classical or post-quantum.
- Obligation
- Optional
- Cardinality
- 0..1
- 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
Missing value dcatuk:missingValueNew
A property this record leaves empty on purpose, and why.
- Obligation
- Optional
- Cardinality
- 0..n
- 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