Knowledge
Reuse across government
New This page is new since 1.2.0-rc.1 (2026-11-06). Everything that changed
Most of what a catalogue team needs already exists somewhere in government: an endorsed standard, a vocabulary, a register, a catalogue product or a toolkit. This page lists the public pieces that fit with DCAT-AP-UK, what each is for, and how to use it alongside the profile. Nothing here is endorsed by this portal; check each one with its owner before relying on it.
Standards bodies and catalogues of standards
3 assets
Data Standards Authority, Linked Data community place, Future data architecture
Data models
6 assets
Digital identity vocabulary, Digital archiving metadata schema, Planning data specification, Planning Inspectorate data model, Education Provider Registry models, UK Parliament ontologies
Registers and reference data
3 assets
Linked Data Registry, DfE reference data, MoG Navigator
Catalogues and discovery
5 assets
Government API catalogue, Federated API discovery model, API standards linting, Data Marketplace API (2023), JNCC catalogue
Frameworks
4 assets
Data Sharing Risk Framework, Public Sector Data Quality Commons, Data asset management capability playbooks, The Knowledge Web
What exists, and how to use it with DCAT-AP-UK
| Asset | Kind | Owner | What it is | How to use it with DCAT-AP-UK | Licence | Last changed |
|---|---|---|---|---|---|---|
| Data Standards Authority | Standards bodies and catalogues of standards | Government Digital Service | Endorsed standards, guidance (reference data, APIs, spreadsheets) and the person data standard project. | Declare conformance to its endorsed standards (listed above). Follow its reference data guidance for codelists. | OGL v3.0 | V |
| Linked Data community place | Standards bodies and catalogues of standards | Government Data community | The cross-government linked data subgroup: meeting notes and resources. | A community to review the RDF side of the profile, its shapes and namespace. | OGL v3.0 | V |
| Future data architecture | Standards bodies and catalogues of standards | Government Digital Service | Principles and patterns for government data architecture, including metadata-based discovery. | DCAT-AP-UK is the record its metadata-based discovery pattern needs; its principle 6 is why the profile exists. | none stated | V |
| Digital identity vocabulary | Data models | GOV.UK One Login | A linked data vocabulary for identity credentials, published as documentation, JSON Schemas and code types. | A model for publishing a vocabulary the same way: one source, many generated artefacts. | MIT | V |
| Digital archiving metadata schema | Data models | The National Archives | JSON Schemas for the metadata of born-digital records transferred to The National Archives. | Map where a dataset is also a public record; records retention and transfer metadata live here, not in DCAT-AP-UK. | MIT | V |
| Planning data specification | Data models | Planning data (MHCLG) | Datasets, fields, datatypes and codelists for planning data, as CSV and Markdown. | A sector specification a planning dataset conforms to; give it in conforms to. | MIT | V |
| Planning Inspectorate data model | Data models | Planning Inspectorate | JSON Schemas for the Planning Inspectorate data model. | Give the schema as the conforms to of a distribution. | MIT | V |
| Education Provider Registry models | Data models | Department for Education | A governance ontology, SKOS taxonomy and SHACL shapes for the registry, kept with Gherkin behaviour. | One of the few public SKOS and SHACL models in government: a reference for codelists and shapes done the same way. | MIT | V |
| UK Parliament ontologies | Data models | UK Parliament | Ontologies for parliamentary data, in Turtle and Markdown. | Link from datasets about Parliament to its terms. | none stated | V |
| Linked Data Registry | Registers and reference data | UK Government Linked Data (UKGovLD) | Software for running registers of linked data terms, with versioning and status (used for environmental and other registers). | A way to host the DCAT-AP-UK codelists as a register with change history, if the owning team wants one. | Apache 2.0 | V |
| DfE reference data | Registers and reference data | Department for Education | A uniform interface to reference data lists used across education services. | Codelists for education datasets; link their values rather than copy them. | MIT | V |
| MoG Navigator | Registers and reference data | Government Data community | Machinery of government changes as data, each with a status (confirmed or reported). | Keeps publisher and creator links right when departments change, as in July 2026. | MIT | V |
| Government API catalogue | Catalogues and discovery | Government Digital Service | The list of government APIs behind api.gov.uk, as CSV. | Every API there can become a DCAT-AP-UK data service; the OpenAPI converter does the first step. | MIT | V |
| Federated API discovery model | Catalogues and discovery | Data Standards Authority | A minimal, push-and-pull model for discovering APIs across catalogues. | Its fields map to the data service class; the crosswalk keeps both in step. | OGL v3.0 | V |
| API standards linting | Catalogues and discovery | Data Standards Authority | Spectral rules that check OpenAPI descriptions against the government API standards. | Run before converting an OpenAPI description to a data service record. | OGL v3.0 | V |
| Data Marketplace API (2023) | Catalogues and discovery | Government Digital Service | The first Data Marketplace API: a triplestore of DCAT records with a FastAPI front. | Its records are the real-world test above. | none stated | V |
| JNCC catalogue | Catalogues and discovery | Joint Nature Conservation Committee | A metadata and data product catalogue with a REST API. | A geospatial catalogue the geospatial extension and GEMINI crosswalk serve. | none stated | V |
| Data Sharing Risk Framework | Frameworks | Department for Digital | Tools to help organisations assess the risk of sharing data. | Use alongside access rights, security classification and transfer safeguard when deciding what a record says about sharing. | MIT (code) | V |
| Public Sector Data Quality Commons | Frameworks | Open prototype (not official) | A data quality hub: checks, frameworks and standards that apply, learning. | Measure the quality the quality properties describe; the Data Quality Framework sits behind both. | MIT and OGL v3.0 | V |
| Data asset management capability playbooks | Frameworks | Open prototype (not official) | Step-by-step guidance on governance, cataloguing and quality for critical data assets, following the DAM policy. | The how-to for recording a critical data asset with this profile. | MIT and OGL v3.0 | V |
| The Knowledge Web | Frameworks | Open prototype (not official) | An ontology-backed map of government data standards and governance artefacts, in one offline HTML file. | Another way to navigate the standards this profile relies on. | Apache 2.0 | V |
Standards the Data Standards Authority endorses
The Data Standards Authority's catalogue of endorsed standards. A dataset that follows one of these says so with conforms to, using the specification address below, so a buyer or a harvester can find every dataset that uses it. Read from its repository V.
| Standard | Short name | Use it for | Give this in conforms to |
|---|---|---|---|
| Algorithmic Transparency Recording Standard | ATRS | A data service or dataset used in an algorithmic tool links to its transparency record. | https://www.gov.uk/government/publications/algorithmic-transparency-template |
| Beneficial Ownership Data Standard 0.3 | BODS | Datasets of who owns or controls companies. | https://standard.openownership.org/en/0.3.0/about/index.html |
| Digital Object Identifier System | DOI | Give a DOI as the identifier or an other identifier, so the dataset can be cited. | https://ieeexplore.ieee.org/document/771073 |
| ISO 20022 financial messages | ISO 20022 | Payment and financial message datasets and services. | https://www.iso20022.org/iso-20022-message-definitions |
| OpenDocument Format 1.2 | ODF | Give the ODF media type for documents and spreadsheets in a distribution. | https://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html |
| Open Referral UK | ORUK | Datasets and APIs of local services, such as directories of support. | https://openreferraluk.org/about-standard |
| CSV files (RFC 4180) | RFC 4180 | A CSV distribution conforms to RFC 4180; say so, and give text/csv as the media type. | https://tools.ietf.org/html/rfc4180 |
| security.txt | security.txt | Data services publish a security.txt so problems can be reported. | https://securitytxt.org |
| 360Giving Data Standard | 360Giving | Grants datasets. | https://standard.threesixtygiving.org/en/latest/reference/#spreadsheet-format |
| UK GEMINI | GEMINI | Geospatial records; the geospatial extension maps to it. | https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules/ |
| Unique Property Reference Number | UPRN | Datasets about property and addresses key on UPRN; say so in conforms to. | https://www.gov.uk/government/publications/open-standards-for-government/identifying-property-and-street-information |
What government code actually uses
Counts are repositories with at least one file that uses the standard or names the product, from public GitHub only. A low count does not mean a standard is little used: much metadata lives in catalogue products, not in public code. From the GitHub Repos Asset Catalogue P.
Repositories with at least one file that uses the standard, from the GitHub Repos Asset Catalogue standards scan.
The data as a table
| Item | Repositories | Total |
|---|---|---|
| OpenAPI | 384 | 384 |
| JSON Schema | 116 | 116 |
| CSVW | 22 | 22 |
| ISO 19115 / 19139 | 19 | 19 |
| DDI | 13 | 13 |
| DCAT | 12 | 12 |
| SKOS | 11 | 11 |
| Dublin Core | 10 | 10 |
| schema.org | 9 | 9 |
| SDMX (RDF) | 8 | 8 |
| Frictionless Data Package | 4 | 4 |
| PROV-O | 3 | 3 |
| LinkML | 3 | 3 |
| SHACL | 2 | 2 |
| Croissant | 1 | 1 |
| xGov MEM | 1 | 1 |
Repositories that configure or name the product. Most products are configured in the product itself, not in public code.
The data as a table
| Item | Repositories | Total |
|---|---|---|
| CKAN | 58 | 58 |
| DataHub | 14 | 14 |
| GeoNetwork or CSW | 11 | 11 |
| AWS Glue Data Catalog | 8 | 8 |
| Microsoft Purview | 7 | 7 |
| Databricks Unity Catalog | 6 | 6 |
| Amundsen | 4 | 4 |
| Informatica | 2 | 2 |
OpenAPI and JSON Schema dominate, which is why DCAT-AP-UK publishes a JSON Schema and turns an OpenAPI description into a data service record. Linked data standards (DCAT, SKOS, PROV-O, SHACL) are rarer in public code, so the portal's tools hide RDF unless you ask for it. CKAN is by far the most common catalogue product, which is why the CKAN crosswalk and the ckanext-dcat route come first in the adoption toolkit.
The 2023 Data Marketplace records, checked against DCAT-AP-UK
The Data Marketplace API repository publishes example DCAT records in Turtle for its triplestore: 4 datasets, 3 data services and 7 distributions. They were checked against the DCAT-AP-UK SHACL shapes with pySHACL. Two of the nine files did not parse, because they use a prefix they never declare. Source: the Data Marketplace API repository V.
| Problem | Count |
|---|---|
| Access rights, publisher, creator and licence given as text, where the profile expects a link to a codelist value or an organisation | 27 |
| Access rights or a theme not from the profile codelists | 15 |
| Contact email in a form the shapes do not accept (the portal prefers a contact form) | 14 |
| No security classification on a dataset or data service | 7 |
| A distribution without an access URL | 7 |
| Rule R-03: no rights statement, while the access rights could not be read as open (they were text) | 7 |
| Update frequency not from the EU frequency list | 4 |
| Type, status, endpoint and access service values in the wrong form | 16 |
| Total | 97 |
Every problem is one the weaver and the xGov MEM conversion already fix or flag: text turned into codelist values, organisations turned into links, a missing classification asked for. None needs a change to the profile. This is the migration the adoption toolkit describes, measured on real government records.
How this list was made
The GitHub Repos Asset Catalogue lists 12,251 UK public-sector repositories (from the cross-government open source scraper, read on 8 October 2026). Its descriptions and topics were searched for metadata, catalogue, vocabulary, schema, register, standard, quality, sharing and discovery terms (517 matches). Its standards scan, which reads files in the repositories, was used for the evidence below. The closest 24 repositories were then cloned and read on 6 November 2026, to confirm what each holds, its licence and when it last changed. Archived repositories are left out. Repositories linked to national security work are left out of this public page.