Downloads
Downloads and API
Updated 1 section on this page is new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
Every file is generated from the profile source on each build, so they always agree. They are static files: use the addresses as a simple read-only API.
The profile in every format
| File | What it is for | Media type |
|---|---|---|
| SHACL shapes | Check RDF records with any SHACL engine. | text/turtle |
| JSON Schema 2020-12 | Check records in the compact JSON form. | application/schema+json |
| JSON-LD context | Turn compact JSON records into RDF. | application/ld+json |
| LinkML schema | For continuity with the xGov MEM toolchain. Not yet checked by LinkML tools. | application/yaml |
| Terms the profile adds | RDFS and OWL definitions of the dcatuk: terms. | text/turtle |
| Codelists (SKOS, Turtle) | Every UK codelist as a SKOS concept scheme. | text/turtle |
| Codelists (SKOS, JSON-LD) | The same, as JSON-LD. | application/ld+json |
| Codelists (CSV) | Every value, its identifier and its EU match. | text/csv |
| Data dictionary (CSV) | Every property on every class with obligations and lineage. | text/csv |
| xGov MEM crosswalk (CSV) | xGov MEM property to DCAT-AP-UK property. | text/csv |
| Backlog register (CSV) | Every xGov MEM backlog item and how it was dealt with. | text/csv |
| Profile for tools (JSON) | What the browser validator reads. Also for other tools, such as the Metadata Weaver. | application/json |
| Organisations (JSON) | GOV.UK organisations for publisher and creator. | application/json |
| This list, as DCAT (JSON-LD) | A DCAT-AP-UK description of these downloads. | application/ld+json |
| This list, as DCAT (Turtle) | The same, as Turtle. | text/turtle |
| Cross-reference manifest | Shared keys for the sister portals: properties, codelists and terms. | application/json |
ExamplesUpdated
| Example | Formats |
|---|---|
| An open dataset with two files | json · jsonld · ttl |
| An open event API | json · jsonld · ttl |
| An internal API that needs an agreement | json · jsonld · ttl |
| A dataset series and one release in it | json · jsonld · ttl |
| One release in a series | json · jsonld · ttl |
| A critical data asset (synthetic) | json · jsonld · ttl |
| A catalogue (synthetic) | json · jsonld · ttl |
| A harvested catalogue record (synthetic) | json · jsonld · ttl |
| Personal data shared across borders (synthetic) | json · jsonld · ttl |
| Values left empty on purpose (synthetic) | json · jsonld · ttl |
Test records for suppliers
The repository holds records that must pass (the examples) and records that must fail (tests/fixtures/invalid.yaml), each naming the rule it breaks. A product that claims conformance should accept every example and reject every failing record. The repository’s own tests hold the SHACL shapes, the JSON Schema and the browser validator to exactly that.
How to use them
- Check a Turtle file:
pyshacl -s dcat-ap-uk.shacl.ttl -d record.ttl - Check a compact JSON record: validate it against
dcat-ap-uk.schema.jsonwith any Draft 2020-12 validator. - Declare conformance: give your catalogue
dct:conformsTo <https://w3id.org/dcat-ap-uk/1.0>once the namespace is registered.