Adopt
Avoiding lock-in and technical debt
Updated 1 section on this page is new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
Metadata locked in one product's model is the most expensive kind of technical debt: every new catalogue, every merger of departments and every new partner means rekeying it. An open, mandated standard turns that debt into an asset that moves with you. This page says how DCAT-AP-UK prevents lock-in, now and later, and what to write in contracts so suppliers adopt it and every other open standard this portal names.
The clauses are a starting point for commercial and legal teams, not legal or commercial advice. Adapt them to the procurement route, the framework and the contract in use, and to the law of the nation it is made under.
How an open standard prevents lock-in and debt
Your metadata leaves with you
Every record can be exported in one published, versioned format and re-imported anywhere that speaks it. Changing supplier becomes a migration, not a rebuild.
Debt it prevents: Bespoke export scripts, rekeying and lost history at exit.
Suppliers compete on product, not on format
When every product reads and writes the same records, buyers can switch, run two side by side, or buy best of breed for each job.
Debt it prevents: Paying to stay because leaving costs more.
Conformance you can test
Shapes, schemas, a conformance kit and three validators held to one verdict turn "supports open standards" into something a buyer can check before signing and at every release.
Debt it prevents: Claims that fail in production, found too late.
Change by version, in the open
Minor versions only add; breaking changes wait for a major version with notice and a migration route. Products can plan instead of patching.
Debt it prevents: Silent schema drift and emergency fixes.
One base, many sectors
Sector extensions only add to the base, so a health or geospatial product stays interoperable with everything else.
Debt it prevents: Parallel sector models that never join up.
Bridges to what you have now
Crosswalks and the weaver carry records from CKAN, DCAT-US, schema.org, Dublin Core, DDI and the xGov MEM, so adoption does not need a big bang.
Debt it prevents: Legacy formats nobody can retire.
Ready for what comes next
Algorithms recorded as identifiers, AI permissions and usage policies in ODRL, and exports for AI tools mean new requirements arrive as new values, not new systems.
Debt it prevents: Rebuilding for post-quantum cryptography, AI and data spaces.
Survives reorganisation
Records name roles and organisations by stable identifiers, so a machinery of government change updates a link, not every record.
Debt it prevents: Orphaned records after departments merge or split.
Now and later
| Risk | When it bites | How DCAT-AP-UK answers it |
|---|---|---|
| Proprietary metadata model with no full export | Now: at every exit, merger or second product | Contract for full export in DCAT-AP-UK at any time, without charge, tested with the conformance kit. |
| Export exists but drops fields or relationships | Now: found at migration | Round-trip tests: import, export and compare, property by property. |
| Vendor-specific identifiers in every record | Later: at reorganisation or exit | Stable, resolvable identifiers owned by the buyer; GOV.UK and registered organisation identifiers for agents. |
| API that only the vendor’s tools can use | Now | A documented open API (OpenAPI) and a harvestable catalogue file. |
| Custom fields that no one else understands | Later: as needs grow | New needs go through the change process or a sector extension, not private fields. |
| Old standard versions kept alive by one product | Later: every release | Support each new minor version within an agreed time, stated in the contract. |
| Classical-only cryptography and weak checksums | Later: the post-quantum migration to 2035 | Algorithms as identifiers, strong checksums, and a recorded migration plan. |
| AI use of data decided by the product, not the owner | Now and growing | Use for AI and ODRL usage policies held in the record, owned by the buyer. |
| Paid connectors for every new partner | Later: at every new exchange | Open, documented exchange formats and harvesting with no per-connection charge. |
The policy behind it
- The UK Open Standards Principles ask government to choose open standards for software interoperability, data and document formats, and to avoid lock-in. K
- The Technology Code of Practice asks teams to make things open, use open standards and avoid being locked into one supplier. K
- The Service Standard asks services to use open standards and common components where they exist. K
- The Data Asset Management Policy asks for critical data assets to be described consistently so they can be found and managed. Data asset management policy in governmentV
- The Roadmap for modern digital government 2025 to 2030 sets out shared standards and a joined-up data infrastructure. A roadmap for modern digital government 2025 to 2030V
What to put in the contract
Clauses grouped by what they protect. Copy them into an invitation to tender, a call-off or a framework schedule, with the schedule of standards below.
1. Open standards
- 1.1 The Supplier shall comply with the open standards in the Schedule of Standards at the requirement level shown, and with any later minor version within six months of its publication.
- 1.2 Where the Supplier's product holds, publishes or exchanges metadata about datasets, data services or catalogues, it shall import and export records that conform to DCAT-AP-UK version 1.2 or later, in Turtle and JSON-LD, including every sector extension named in the Order.
- 1.3 The Supplier shall not substitute a proprietary format, vocabulary or identifier scheme where the Schedule names an open one, and shall not add private fields where a standard property exists.
- 1.4 Where the Supplier believes a requirement cannot be met by an open standard, it shall say so in writing before contract award, with the reason and the proposed alternative, for the Buyer's decision.
2. Conformance and evidence
- 2.1 Before acceptance, and with each major release, the Supplier shall run the published DCAT-AP-UK conformance kit and give the Buyer the results: every pass case accepted, every fail case rejected with the rule named, and a round trip that keeps every property.
- 2.2 The Supplier shall state the conformance level (1, 2 or 3) its product supports and shall not claim a level its evidence does not show.
- 2.3 The Buyer may run the conformance kit, the SHACL shapes or the JSON Schema against the product at any time.
3. Data and metadata ownership and portability
- 3.1 All metadata, records, identifiers, codelists, usage policies and lineage created or held for the Buyer are the Buyer's, whatever product holds them.
- 3.2 The Supplier shall provide a complete export of all of it in DCAT-AP-UK, and of the data in open formats, on request, at any time, within ten working days, without charge.
- 3.3 Identifiers shall be ones the Buyer controls, or open registered identifiers; the Supplier's internal identifiers shall not be the only key.
- 3.4 The Supplier shall publish a harvestable catalogue file and a documented open API (OpenAPI) for reading and writing records, with no charge per connection or per partner.
4. Exit and transition
- 4.1 At exit the Supplier shall give a full, tested export as above, an account of every field mapping and any loss, and reasonable help to the incoming supplier, at the rates in the contract.
- 4.2 The Supplier shall not delete the Buyer's metadata until the Buyer confirms the export is complete and conforms.
- 4.3 An exit plan, including the export, shall be kept up to date and tested at least once a year.
5. Change, versions and technical debt
- 5.1 The Supplier shall support each new minor version of DCAT-AP-UK and of the standards in the Schedule within six months, and each major version within an agreed migration period.
- 5.2 The Supplier shall tell the Buyer of any change to its product that affects conformance, before it is released.
- 5.3 The Supplier shall keep a register of deviations from the Schedule, with a plan and date to remove each, and report it quarterly.
6. Security, privacy and the future
- 6.1 The Supplier shall record the cryptographic algorithms protecting the Buyer's data and services as identifiers, support strong checksums (SHA-256 or stronger), and provide a plan to migrate to post-quantum cryptography in line with the NCSC timeline.
- 6.2 The Supplier shall keep each record's security classification, personal data status, jurisdictions and transfer safeguard, and shall not move data outside the jurisdictions recorded without the Buyer's written agreement.
- 6.3 The Supplier shall not use the Buyer's data or metadata to train, fine-tune or evaluate AI models except as the record's use for AI and usage policy allow.
7. Accessibility and openness
- 7.1 User interfaces shall meet WCAG 2.2 at level AA, with a published accessibility statement.
- 7.2 Contact points shall be stored as team names and contact form addresses; the product shall not require a named person or a personal email address.
Download the clauses and schedule (Markdown)
Schedule of standardsUpdated
Every standard named in this portal, with the requirement a buyer can set. Defaults follow each standard’s group; the buyer decides.
| Standard | Group | Requirement | Applies |
|---|---|---|---|
| DCAT-AP-UK | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| W3C DCAT 3 | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| DCAT-AP 3.0.1 | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| DCAT-AP HVD | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| xGov MEM v0.1.0 | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| Data Marketplace schemas | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| Future pan-UK metadata architecture | DCAT family | Must | Wherever the product holds, publishes or exchanges metadata. |
| Dublin Core Terms | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| SKOS | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| FOAF | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| vCard ontology | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| ADMS | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| PROV-O | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| DQV | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| SPDX | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| ISA Core Location | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| GeoSPARQL | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| ODRL 2.2 | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| EU Vocabularies | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| ISO 3166 country codes | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| IANA media types | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| HealthDCAT-AP R7 | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| GeoDCAT-AP 3.1 | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| StatDCAT-AP | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| mobilityDCAT-AP | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| MLDCAT-AP 3.x | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| BRegDCAT-AP | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| Dataspace Protocol | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| UK GEMINI 2.3 | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| MEDIN | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| HDR UK Gateway schema | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| Ofgem Data Best Practice | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| ISO 19115 | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| INSPIRE metadata | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| GML and INSPIRE nil reasons | Vocabularies reused | Must | As DCAT-AP-UK uses them; no private substitutes. |
| NATO Core Metadata Specification (ADatP-5636) | Sector profiles | Must, where the sector applies | When the buyer names the sector extension. |
| DCAT-US 3.0 | Other national profiles | Should | Accept for exchange with partner countries. |
| DCAT-AP-NO | Other national profiles | Should | Accept for exchange with partner countries. |
| DCAT-AP.de | Other national profiles | Should | Accept for exchange with partner countries. |
| DCAT-AP-NL 3.0 | Other national profiles | Should | Accept for exchange with partner countries. |
| DCAT-AP_IT | Other national profiles | Should | Accept for exchange with partner countries. |
| schema.org Dataset | Other metadata models | Should | Import and export, through the weaver mappings or natively. |
| Croissant 1.1 | Other metadata models | Should | Import and export, through the weaver mappings or natively. |
| Dublin Core 15 elements | Other metadata models | Should | Import and export, through the weaver mappings or natively. |
| DDI Codebook | Other metadata models | Should | Import and export, through the weaver mappings or natively. |
| CKAN and ckanext-dcat | Other metadata models | Should | Import and export, through the weaver mappings or natively. |
| OpenAPI | Formats and validation | Must | For publishing, validation and interfaces. |
| SHACL | Formats and validation | Must | For publishing, validation and interfaces. |
| JSON Schema 2020-12 | Formats and validation | Must | For publishing, validation and interfaces. |
| JSON-LD 1.1 | Formats and validation | Must | For publishing, validation and interfaces. |
| RDF 1.1 Turtle | Formats and validation | Must | For publishing, validation and interfaces. |
| LinkML | Formats and validation | Must | For publishing, validation and interfaces. |
| Model Context Protocol | Formats and validation | Must | For publishing, validation and interfaces. |
| llms.txt | Formats and validation | Must | For publishing, validation and interfaces. |
| Data Asset Management Policy | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| Government Security Classifications | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| UK GDPR and ICO transfer guidance | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| Open Government Licence v3.0 | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| NCSC post-quantum timeline | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| FIPS 203 | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| Code of Practice for Statistics | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| WCAG 2.2 | UK policy, law and security | Must comply | As law, policy or guidance requires. |
| org-id.guide | UK policy, law and security | Must comply | As law, policy or guidance requires. |
Checking suppliers keep to it
- Ask for the conformance kit results with every bid, and again at acceptance.
- Run a test exit within the first year: export everything, load it into another product or the portal's bulk checker, and compare.
- Review the deviations register at every quarterly review, and agree dates to remove each.
- Add DCAT-AP-UK conformance to the definition of done for every release the supplier ships.
- Use the requirement levels in the schedule as evaluation criteria, weighted for the work.
The supplier conformance kit gives the evidence; the claim form records it.