Knowledge
Lineage explorer
Updated 2 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
Trace anything in the profile back to where it came from, and forward to what depends on it: 421 items and 1247 links, from the sources and the xGov MEM slots, through properties, classes, codelists and rules, to the worked examples and the tests that prove them.
TraceUpdated
- Sources (22)
- Classes (14)
- Codelists (17)
- Properties (129)
- xGov MEM slots (33)
- Rules (8)
- Deliberate breaks (tests) (31)
- Backlog issues (22)
- Worked examples (10)
- Extensions (10)
- Crosswalks (23)
- Defects (9)
- standard (64)
- Requirements (29)
Everything in the graphUpdated
Sources (22)
- Data Catalog Vocabulary (DCAT) Version 3
- UK Cross-Government Metadata Exchange Model
- Recording metadata to describe critical data assets
- Data Marketplace data catalogue metadata (JSON Schema and API)
- Guidelines and best practices for making government datasets ready for AI
- UK GEMINI
- HealthDCAT-AP Release 7
- GeoDCAT-AP 3.1.0
- StatDCAT-AP
- mobilityDCAT-AP
- MLDCAT-AP 3.0.0 and 3.1.0
- DCAT-AP HVD 3.0
- Eclipse Dataspace Protocol
- Croissant 1.1
- MEDIN discovery metadata standard
- HDR UK Gateway schemata
- Data Best Practice Guidance
- Code of Practice for Statistics
- org-id.guide
- ckanext-dcat
- DDI Codebook 2.5
- Dublin Core Metadata Element Set 1.1
Classes (14)
Codelists (17)
Properties (129)
- Title
- Description
- Summary
- Alternative title
- Identifier
- Other identifier
- Publisher
- Creator
- Contact point
- Access rights
- Rights statement
- Security classification
- Personal data
- Sensitive data
- Who can see this record
- Licence
- Release date
- Last updated
- Created
- Update frequency
- Theme
- Keyword
- Geographic coverage
- Spatial resolution (metres)
- Time period covered
- Time resolution
- Conforms to
- Reference data used
- Version
- Version notes
- Previous version
- Replaced by
- Expires
- Part of series
- Distribution
- Related resource
- Qualified relation
- Landing page
- Documentation
- Language
- Interface style
- Status
- Data quality
- Critical data asset
- Responsible role
- Access address
- Download address
- Media type
- Format
- Size (bytes)
- Checksum
- Access service
- Compression format
- Endpoint address
- Endpoint description
- Serves dataset
- Dataset
- Data service
- Home page
- Theme list used
- Catalogue record
- Describes
- Name
- Organisation type
- Team name
- Contact form
- Team email address
- Telephone
- Postal address
- Bounding box
- Geometry
- Centre point
- Place name
- Start date
- End date
- Algorithm
- Checksum value
- Role
- Organisation
- Applicable legislation
- Usage policy
- Where the data is held or sent
- Transfer safeguard
- Connection security
- Missing value
- Property left empty
- Why it is empty
- Source record
- Property added or changed on the way
- Health category
- Health theme
- Population covered
- Number of records
- Number of people
- Youngest typical age
- Oldest typical age
- Clinical coding system
- National data opt-out applied
- Trusted research environment
- Topic category
- Lineage
- Spatial representation type
- Purpose
- Statement
- Statistics status
- Dimension
- Measure
- Attribute
- Number of series
- Mobility theme
- Transport mode
- Network covered
- Georeferencing method
- Mobility data standard
- High-value dataset category
- Use for AI
- Data card
- Synthetic data
- Generated by
- Participant identifier
- Open data triage outcome
- Presumed open
- Reference frame
- Coordinate epoch
- Vertical reference
- Observation technique
- Horizontal uncertainty (metres)
- Vertical uncertainty (metres)
- Confidence level (per cent)
xGov MEM slots (33)
- title (xGov MEM)
- description (xGov MEM)
- summary (xGov MEM)
- alternativeTitle (xGov MEM)
- identifier (xGov MEM)
- publisher (xGov MEM)
- creator (xGov MEM)
- contactPoint (xGov MEM)
- accessRights (xGov MEM)
- securityClassification (xGov MEM)
- licence (xGov MEM)
- issued (xGov MEM)
- modified (xGov MEM)
- created (xGov MEM)
- updateFrequency (xGov MEM)
- theme (xGov MEM)
- keyword (xGov MEM)
- version (xGov MEM)
- distribution (xGov MEM)
- relatedResource (xGov MEM)
- serviceType (xGov MEM)
- serviceStatus (xGov MEM)
- downloadURL (xGov MEM)
- mediaType (xGov MEM)
- byteSize (xGov MEM)
- accessService (xGov MEM)
- endpointURL (xGov MEM)
- endpointDescription (xGov MEM)
- servesData (xGov MEM)
- contactName (xGov MEM)
- email (xGov MEM)
- telephone (xGov MEM)
- address (xGov MEM)
Rules (8)
- R-01: A contact point must give a contact form, a team mailbox, or both.
- R-02: A period of time must have a start date, an end date, or both.
- R-03: When access rights are commercial or internal, give a rights statement saying how to ask for the data.
- R-04: When the record describes a critical data asset, the properties marked mandatory for critical data assets must be given.
- R-05: The summary must be 250 characters or fewer.
- R-06: A team email address must be a mailto address. A contact form must be a web address.
- R-07: A period's end date must not be before its start date.
- R-08: When the data contains personal data and is held in or sent to anywhere outside the UK, give the transfer safeguard.
Deliberate breaks (tests) (31)
- contact without route
- email not mailto
- internal without rights
- critical asset incomplete
- summary too long
- period end before start
- period empty
- bad date
- distribution without access url
- service without endpoint
- personal data abroad without safeguard
- service personal data abroad
- jurisdiction not a code
- unknown transfer safeguard
- checksum algorithm not spdx
- missing value bad reason
- missing value no reason
- health without period
- geo without crs
- geo bad representation
- stats without status
- stats bad status
- transport without theme
- hvd without legislation
- ai without use
- ai bad use
- dataspace without policy
- org bad identifier
- energy without triage
- geodesy without frame
- geodesy bad technique
Backlog issues (22)
- Issue 86: Major overhaul tracking issue for the metadata exchange model and site
- Issue 78: Rename the repository and references to DCAT Application Profile for the UK
- Issue 76: Title examples in alternative title don't follow the rules for titles
- Issue 72: Distribution is incorrectly configured as an IRI or CURIE
- Issue 71: The contact point definition is the same as the email definition
- Issue 70: Launch release management, lock the specification and start formal change management
- Issue 69: The OS postcodes example names the wrong publisher
- Issue 63: Codelist pages don't link out to external vocabularies
- Issue 60: Add usage notes to access rights
- Issue 49: Recommend a taxonomy for theme values
- Issue 44: What to do if there is no applicable licence
- Issue 30: What to do with assets that don't have a modified date
- Issue 26: Indicate whether the data includes sensitive information
- Issue 25: Indicate whether the data includes personal identifiable information
- Issue 15: Add a home page for the point of contact
- Issue 13: Decide on a persistent identifier for the metadata model
- Issue 11: Include schemas in the documentation site
- Issue 5: Enable declaration of the metadata's access control
- Issue 4: Capture the schema of the underlying dataset
- Issue 3: Capture the reference data used and its resolution
- Issue 2: Capture the temporal extent of the data resource
- Issue 1: Capture the geospatial coverage of the data resource
Worked examples (10)
- An open dataset with two files
- An open event API
- An internal API that needs an agreement
- A dataset series and one release in it
- One release in a series
- A critical data asset (synthetic)
- A catalogue (synthetic)
- A harvested catalogue record (synthetic)
- Personal data shared across borders (synthetic)
- Values left empty on purpose (synthetic)
Extensions (10)
Crosswalks (23)
- CKAN with ckanext-dcat crosswalk
- Dublin Core (15 elements) crosswalk
- UK GEMINI 2.3 crosswalk
- HDR UK Gateway schema crosswalk
- Croissant 1.1 (ML datasets) crosswalk
- DDI Codebook (study level) crosswalk
- Atlan crosswalk
- Collibra Platform crosswalk
- data.world crosswalk
- Microsoft Purview (Data Map and Unified Catalog) crosswalk
- Apache Atlas crosswalk
- OpenMetadata (and Collate) crosswalk
- DataHub (and DataHub Cloud) crosswalk
- Unity Catalog (open source and Databricks) crosswalk
- Google Cloud Dataplex Universal Catalog crosswalk
- Snowflake (Horizon Catalog and Snowflake Open Catalog) crosswalk
- AWS Glue Data Catalog crosswalk
- Amazon SageMaker Catalog (Amazon DataZone) crosswalk
- Oracle Cloud Infrastructure Data Catalog crosswalk
- Cloudera (SDX) crosswalk
- Apache Polaris (Iceberg REST catalog) crosswalk
- OpenLineage (and Marquez) crosswalk
- Amundsen crosswalk
Defects (9)
- D-004: The duplicate-title check missed a real duplicate.
- D-009: Loading the critical data asset example into the record builder lost its licence.
- D-014: An unknown property name with a space crashed the Turtle export instead of being reported.
- D-015: The record builder’s Turtle dropped every property of a distribution that had its own address.
- D-029: LinkML's own validator rejected every worked example, so the LinkML file disagreed with the SHACL, JSON Schema and portal validators.
- D-033: Invented example data was shown under real names: the synthetic cross-border example gave the DVLA as its publisher, the synthetic base record for the sector extensions gave GDS, and the identifier guidance used company and charity numbers that could belong to real bodies.
- D-035: The OpenLineage documentation facet written by the weaver named schema version 1-0-1; the specification at the cited commit is 1-1-0.
- D-036: Where each product runs was written from background knowledge for all 31 products, and Secoda was shown as SaaS only, though Secoda documents a self-hosted, on-premises install.
- D-040: Code scanning found five weaknesses. The reference HTTP service returned internal error text to callers (posting null to /weave answered with a JavaScript TypeError message). The Copy buttons put back their label by re-parsing HTML kept in an attribute. A test treated any address containing github.com as GitHub. Two of the build's own HTML-stripping patterns missed upper-case or spaced closing tags.
standard (64)
- DCAT-AP-UK
- W3C DCAT 3
- DCAT-AP 3.0.1
- DCAT-AP HVD
- xGov MEM v0.1.0
- Data Marketplace schemas
- Future pan-UK metadata architecture
- Dublin Core Terms
- SKOS
- FOAF
- vCard ontology
- ADMS
- PROV-O
- DQV
- SPDX
- ISA Core Location
- GeoSPARQL
- ODRL 2.2
- EU Vocabularies
- ISO 3166 country codes
- IANA media types
- HealthDCAT-AP R7
- GeoDCAT-AP 3.1
- StatDCAT-AP
- mobilityDCAT-AP
- MLDCAT-AP 3.x
- BRegDCAT-AP
- Dataspace Protocol
- UK GEMINI 2.3
- MEDIN
- HDR UK Gateway schema
- Ofgem Data Best Practice
- ISO 19115
- INSPIRE metadata
- GML and INSPIRE nil reasons
- NATO Core Metadata Specification (ADatP-5636)
- DCAT-US 3.0
- DCAT-AP-NO
- DCAT-AP.de
- DCAT-AP-NL 3.0
- DCAT-AP_IT
- schema.org Dataset
- Croissant 1.1
- Dublin Core 15 elements
- DDI Codebook
- CKAN and ckanext-dcat
- Apache Atlas entity model
- OpenAPI
- SHACL
- JSON Schema 2020-12
- JSON-LD 1.1
- RDF 1.1 Turtle
- LinkML
- Model Context Protocol
- llms.txt
- Data Asset Management Policy
- Government Security Classifications
- UK GDPR and ICO transfer guidance
- Open Government Licence v3.0
- NCSC post-quantum timeline
- FIPS 203
- Code of Practice for Statistics
- WCAG 2.2
- org-id.guide
Requirements (29)
- RQ-01: Records can be exchanged with international and allied DCAT-based profiles without bespoke
- RQ-02: Finding a record never grants access to the data. Who may have the data is stated separate
- RQ-03: A catalogue record can say how the record itself must be handled, separately from the hand
- RQ-04: A record can say why a property is empty (unknown, withheld, not applicable, not collected
- RQ-05: Validation is machine-readable and gives one verdict wherever it runs.
- RQ-06: Conformance is claimed by level and by layer, and only after the matching tests pass.
- RQ-07: Specialist terms live in their own namespaces, as modules that can be required or left out
- RQ-08: The authoritative source of a record, and of each value changed on the way, survives harve
- RQ-09: Every mapping says what it loses.
- RQ-10: Asset, dataset, data product, data service and distribution have one meaning each, which p
- RQ-11: Organisations without an enterprise catalogue can still describe their assets, from a spre
- RQ-12: The profile works with the catalogue platforms departments already run, through configurat
- RQ-13: Validation works in disconnected and air-gapped environments, with no calls to the network
- RQ-14: The public profile describes OFFICIAL information only. Anything needing higher classifica
- RQ-15: Where allied exchange needs it, DCAT-AP-UK maps to the NATO Core Metadata Specification an
- RQ-16: Geospatial records reference GEMINI rather than repeat it.
- RQ-17: Catalogues and information asset registers work together without becoming two registers of
- RQ-18: Public artefacts never expose controlled semantics, and never name people or meetings from
- RQ-19: Missing metadata is collected from the business areas that hold it, without a central team
- RQ-20: Policing and justice systems can describe shared data with the same core, alongside their
- RQ-21: Metadata held in a catalogue platform's own model, such as the Apache Atlas types behind M
- RQ-22: A mapping never invents a value. No default description, licence, language, contact name o
- RQ-23: Precise positions say which reference frame and epoch they are in, how they were observed
- RQ-24: Geospatial records state their coordinate reference system, give resolution with a unit, a
- RQ-25: A record declares which profile, layers and versions it was written to.
- RQ-26: A release passes four gates. Reuse is assessed for every new term; every rule is traced to
- RQ-27: UK profiles agree which properties are mandatory, recommended and optional, so a record th
- RQ-28: Every requirement can be followed from its evidence to the properties, rules, tests, decis
- RQ-29: Partner overlays attach to the core without changing it. Core discovery stays open; overla