Estate
The estate: four portals
Four open portals for data in the public sector, each with its own owner, purpose, audience and status. They link to each other and share keys; they do not merge or copy each other's content. The comparison was made by reading each portal's repository on 6 November 2026. "Not seen" means it was not found in that review and may exist.
The four portals
South
DCAT-AP-UK (this portal)
How do we describe it so others can find it?
Proposed standard, not endorsed
Not sure where to start? The estate compass suggests a route across all four. DCAT-AP-UK is its South bearing: the ground everything else stands on, because nothing can be found, governed or improved until it is described.
The architecture it implements
The Future pan-UK metadata architecture (DCAT-AP-UK founding specification and architecture blueprint)P sets out DCAT-AP-UK as the shared record for the UK’s data ecosystems. This portal is a working implementation of that record: the profile, its sector extensions, validators, migration from the xGov MEM and the adoption toolkit. The repository is private, so its contents are not reproduced here; reconciling the two is on the open register (O-14).
Compared like for like: content
| DAM playbooks | DQ Commons | Repos catalogue | DCAT-AP-UK | |
|---|---|---|---|---|
| DAM Policy requirements, step by step | Yes | Partly | Partly | Partly The metadata part only: what a critical data asset record must contain |
| Metadata standard, normative | No | No | No | Yes The profile itself: classes, properties, obligations, codelists, rules |
| Cataloguing method | Yes | Yes | Partly | Partly What to record; the DAM playbooks own how to run cataloguing |
| Crosswalks between metadata models | Partly | Yes | Partly | Yes xGov MEM, the 2026 guidance, Data Marketplace, DCAT-AP, schema.org |
| Codelists as linked data (SKOS) | Not seen | Partly | Not seen | Yes 12 codelists and 1,271 organisations |
| Roles and personas | Yes | Yes | Yes | Yes Seven proto-personas, untested |
| Strategy alignment | Yes | Partly | Partly | Yes Roadmap, NDL, DAM Policy, discovery pattern, sharing principles, AI-ready data |
| Data quality method | Yes | Yes | Partly | No Links to the Commons; records carry a quality annotation |
| Evidence from public code | No | No | Yes | No |
Compared like for like: features
| DAM playbooks | DQ Commons | Repos catalogue | DCAT-AP-UK | |
|---|---|---|---|---|
| Build a record in the browser | No | Partly | No | Yes Record builder with live validation and three output formats |
| Check records in the browser, nothing uploaded | No | Yes | No | Yes Validator, including conversion from xGov MEM records |
| Search and command palette | Yes | Yes | Yes | Yes |
| Glossary tooltips and display options | Yes | Partly | Yes | Yes |
| Site map | Yes | Yes | Partly | Yes |
| Guided tours and tutorials | Yes | Yes | Yes | Yes Tours on seven pages, six tutorials with progress, and role routes |
| Display options in the masthead | Yes | Yes | Partly | Yes Theme, text size, spacing, contrast, motion and link style, kept in this browser |
| User guide | Yes | Yes | Not seen | Yes Tasks, questions people ask and where to get help |
| Interactive lineage and traceability | Not seen | Yes | Not seen | Yes Trace any property, rule, test, standard or defect, up and down |
| Data visualisation of the portal’s own data | Not seen | Not seen | Not seen | Yes Eight charts built from the profile, each with a table |
| Metadata weaver and crosswalk matrix | Not seen | Partly | Not seen | Yes Seven readers and nine writers, every field threaded |
| Map of related standards | Not seen | Partly | Not seen | Yes About 60 standards and 80 typed links, filterable |
| Supplier conformance kit and reference API | Not seen | Not seen | Not seen | Yes Test records with expected verdicts, badges, a command line, an HTTP API and a GitHub Action |
| Class diagrams, value types and a feedback link on every page (from the xGov MEM) | Partly | Partly | Not seen | Yes A UML-style diagram on each class page |
| Open data downloads and static API | Yes | Yes | Yes | Yes Every artefact, with a DCAT description of the downloads |
| Cross-reference manifest (xref.json) | Yes | Yes | Partly | Yes |
| MCP server for AI assistants | Yes | Yes | Not seen | Yes Nine tools, using the portal’s own validator; tested on every build |
| Offline copy | Not seen | Yes | Yes | Partly Each release attaches the site as a zip; pages work from disk |
Compared like for like: trust and quality
| DAM playbooks | DQ Commons | Repos catalogue | DCAT-AP-UK | |
|---|---|---|---|---|
| Source label on each fact | Yes | Partly | Yes | Yes V, K, P and U codes |
| Automated accessibility checks | Yes | Yes | Yes | Yes |
| Scheduled health checks | Yes | Yes | Yes | Yes Weekly: sources, review date, page weight |
| Independent engines checked against each other | No | Yes | Partly | Yes SHACL, JSON Schema and the browser validator must agree on every test record |
| Every check proven by a deliberate break | Yes | Yes | Yes | Yes |
What each gains from the others
- DCAT-AP-UK to DAM capability playbooks: The cataloguing playbook can cite DCAT-AP-UK as the agreed field set instead of its own proposed crosswalk, once the profile is endorsed.
- DCAT-AP-UK to Public Sector Data Quality Commons: The Metadata Weaver can read profile.json and the JSON-LD context, so "describe once" outputs a record that conforms.
- DCAT-AP-UK to GitHub Repos Asset Catalogue: The catalogue's DCAT JSON-LD feeds can declare conformance to the profile and use its organisation identifiers.
- Public Sector Data Quality Commons to DCAT-AP-UK: Records link quality reports through dqv:hasQualityAnnotation; the Commons supplies the reports.
- DAM capability playbooks to DCAT-AP-UK: The critical data asset rules come from the policy the playbooks explain; their roles name who records what.
- GitHub Repos Asset Catalogue to DCAT-AP-UK: The organisations list (register R3, GOV.UK slugs) is reused from the catalogue rather than copied by hand.
Shared keys
Published in xref.json, in the same shape as the sister portals’ manifests.
| Key | Used for | Where |
|---|---|---|
| GOV.UK organisation slug | publisher and creator | organisations.json; the catalogue's org crosswalk |
| DCAT-AP-UK property name | what a field means | xref.json (properties) |
| Codelist concept | access rights, themes, classifications | xref.json (codelists) |
| Glossary term id | shared vocabulary | xref.json (terms) |
Journeys across portals
- Record a critical data asset: DAM capability playbooks (What the policy requires) then DCAT-AP-UK (Build the record with critical data asset switched on) then Public Sector Data Quality Commons (Check the quality of the data) then DAM capability playbooks (Report and sustain)
- Buy or replace a catalogue tool: Public Sector Data Quality Commons (Compare products and lock-in) then DCAT-AP-UK (Ask suppliers to pass the test records) then GitHub Repos Asset Catalogue (See who already runs the tool)
- Build a discovery service: GitHub Repos Asset Catalogue (Find catalogue code that already exists) then DCAT-AP-UK (Map every source to the shared record) then Public Sector Data Quality Commons (Score metadata quality)