Your choices apply to every page and are kept in this browser only.
Knowledge
Insights
Updated 4 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed
The profile in numbers and pictures: what it asks for, what changed, how the backlog was closed, what the extensions add and how good the examples are. Every chart has its data in a table.
In numbersUpdated
89
properties
14
classes
22
codelists
8
rules
10
sector extensions
8
models crosswalked
10
worked examples
40
defects fixed, each with a check
The modelUpdated
Properties on each class, by obligation
Mandatory
Recommended
Conditional
Optional
How much each class asks for. Datasets and data services carry the most.
The data as a table
Properties on each class, by obligation
Item
Mandatory
Recommended
Conditional
Optional
Total
Dataset
9
16
2
21
48
Data service
10
8
2
14
34
Distribution
1
4
0
13
18
Dataset series
2
3
0
4
9
Catalogue
3
9
0
3
15
Catalogue record
2
2
0
5
9
Organisation
1
1
0
2
4
Contact point
1
0
2
2
5
Location
0
1
0
3
4
Period of time
0
0
2
0
2
Checksum
2
0
0
0
2
Relationship
2
0
0
0
2
Responsible role
2
0
0
0
2
Missing value
2
0
0
0
2
Values in each codelistThe data as a table
Values in each codelist
Item
Values
Total
Jurisdictions
123
123
Update frequency
20
20
Theme
14
14
Checksum algorithms
12
12
Transfer safeguards
11
11
Service status
8
8
Sensitive data
7
7
Interface style
7
7
Geodetic observation techniques
7
7
Licences
6
6
Language
6
6
Spatial representation types
6
6
Personal data
5
5
Responsible role
5
5
Connection security
5
5
Use for artificial intelligence
5
5
Official statistics status
5
5
Reasons a value is missing
5
5
Security classification
4
4
Who can see this record
4
4
Open data triage outcome
4
4
Access rights
3
3
Change and the backlogUpdated
Properties by what changed from the xGov MEM
Most properties are new or kept; renames follow DCAT-AP.
The data as a table
Properties by what changed from the xGov MEM
Item
Properties
Total
new
56
56
unchanged
11
11
obligation-changed
7
7
codelist-mapped
3
3
uri-fixed
2
2
definition-fixed
2
2
example-fixed
1
1
range-relaxed
1
1
range-changed
1
1
value-restored
1
1
codelist-added
1
1
range-fixed
1
1
merged
1
1
renamed
1
1
The xGov MEM backlog, by outcome
All 22 open issues have an outcome.
The data as a table
The xGov MEM backlog, by outcome
Item
Issues
Total
resolved
19
19
owner
1
1
provisional
2
2
kept closed
6
6
Extensions and qualityUpdated
What each sector extension adds
New properties
Raised or narrowed
The data as a table
What each sector extension adds
Item
New properties
Raised or narrowed
Total
Health and care
10
4
14
Geospatial
5
3
8
Official statistics
5
3
8
Transport and mobility
5
1
6
High-value datasets (for EU exchange)
1
1
2
AI-ready
4
5
9
Data spaces
1
2
3
Private and voluntary sector
0
2
2
Energy
2
4
6
Geodesy
7
1
8
Quality score of each worked example, by dimension
Findability
Accessibility
Interoperability
Reusability
Contextuality
Out of 405 points, modelled on the EU metadata quality assessment (provenance K).
The data as a table
Quality score of each worked example, by dimension
Item
Findability
Accessibility
Interoperability
Reusability
Contextuality
Total
An open dataset with two files
80
50
110
75
20
335
An open event API
60
100
70
75
5
310
An internal API that needs an agre
30
100
110
75
5
320
A dataset series and one release i
50
0
30
10
0
90
One release in a series
70
0
30
75
5
180
A critical data asset (synthetic)
50
0
30
75
10
165
A catalogue (synthetic)
0
0
30
10
0
40
A harvested catalogue record (synt
0
0
30
0
10
40
Personal data shared across border
60
50
110
75
10
305
Values left empty on purpose (synt
0
0
30
75
10
115
Across borders and around the world
Jurisdictions by group and UK adequacy
Full adequacy
Partial
None listed or not a transfer
As the ICO listed adequacy (provenance K); check before relying on it.