# data-gov.info Metadata Schema — Version 1.0 **Formal methodology document** · Status: Draft for publication · Date: 2026-11-07 Modeled on the re3data.org Metadata Schema (v4.0) conventions: versioned, with per-property occurrence rules and controlled vocabularies. Published under CC BY 4.0. Schema changes follow semantic versioning; every published snapshot of `portals.json` names the schema version it conforms to. --- ## 1. Scope and unit of description The unit of description is a **government open data portal**: a web service operated by or on behalf of a public authority whose primary purpose is publishing open government data. Included: national, supranational, regional/municipal and thematic government portals. Excluded: research-data repositories (covered by re3data), private aggregators, single-dataset services. **Inclusion criteria (all must hold):** (i) operated by/for a public authority; (ii) publishes data intended for reuse (not only documents); (iii) publicly reachable; (iv) has a stable URL. **Exclusion/retirement:** portal unreachable for 2 consecutive quarterly checks → `status: dead`; merged portals point to successor via `superseded_by`. ## 2. Identifiers Every record carries a stable slug `id` (lowercase, ISO-based). The canonical citable identifier is the record URL `https://data-gov.info/portal/{id}`. Each published quarterly snapshot of the full dataset receives a **DOI** (see §6), so figures are citable as *dataset-version + record*. ## 3. Property table Occurrence: 1 = mandatory, 0–1 = optional, 0–n / 1–n = repeatable. ⊙ = value-object (see §4). | # | Property | Occ. | Type / vocabulary | Description | |---|---|---|---|---| | 1 | id | 1 | slug `[a-z0-9-]` | Stable record identifier | | 2 | country | 1 | string (EN) | Country/entity name | | 3 | iso | 1 | ISO 3166-1 alpha-2 (+ `EU`) | Country code | | 4 | region | 1 | CV: Europe-West/East/North/South, Americas, Asia-Pacific, Africa, MENA, Europe | Macro-region | | 5 | level | 1 | CV: supranational, national, regional, municipal, thematic | Administrative level | | 6 | name | 1 | string | Portal name (usually domain) | | 7 | url | 1 | URL | Canonical portal address | | 8 | operator | 1 | string | Responsible public authority | | 9 | launched | 0–1 | year | First public launch | | 10 | platform | 1 | CV: CKAN, uData, Socrata, Magda, OpenDataSoft, ArcGIS Hub, custom | Software platform | | 11 | api.type | 0–1 | string (CV-seeded: CKAN v3, DCAT, SPARQL, SODA, REST) | Machine access | | 12 | api.url | 0–1 | URL | API root | | 13 | api.robots | 0–1 | string | Crawl policy as observed (verbatim) | | 14 | license | 1 | SPDX id or named national licence | Default data licence | | 15 | languages | 1–n | BCP-47 | Interface languages | | 16 | legal_basis | 0–1 | string | Founding law/regulation | | 17 | datasets | 0–1 | ⊙ value-object | Dataset count | | 18 | publishers | 0–1 | ⊙ value-object | Count of publishing bodies | | 19 | odm2025 | 0–1 | object {cluster CV: Trendsetter/Fast-tracker/Follower/Beginner; score %; rank; yoy; trust} | EU Open Data Maturity assessment | | 20 | hvd_coverage | 0–1 | CV: full, partial, none, n/a | EU High-Value Datasets coverage | | 21 | history | 0–n | list of ⊙ dated measurements | Time series of measurements | | 22 | status | 1 | CV: active, active-stale, active-degraded, dead | Operational status | | 23 | superseded_by | 0–1 | id | Successor record | | 24 | verified | 0–1 | object {by, role, date, ref} | Operator verification (§5) | | 25 | sources | 1–n | URL | Evidence for the record | | 26 | last_verified | 1 | ISO 8601 date | Last editorial review | | 27 | notes | 0–1 | string | Free-text caveats | ## 4. Value-objects and trust levels Every measured quantity is an object, never a bare number: ```json {"value": 40000, "qualifier": "40,000+; annual registry editions counted separately", "date": "2026-04-24", "method": "official statement", "trust": "B", "source": "https://…"} ``` `method` CV: `api` · `homepage counter` · `official statement` · `secondary` · `estimate`. **Trust levels (ordered):** | Level | Name | Definition | |---|---|---| | **A** | Measured | Obtained by data-gov.info from the portal's official API on `date` | | **V** | Verified by operator | Confirmed or supplied by the portal operator through the self-claim process (§5); displayed with the operator badge | | **B** | Official statement | Dated public statement by the operator/government | | **C** | Secondary | Authoritative third party (EU ODM report, CKAN Ecosystem, peer-reviewed source) | | **D** | Estimate | Editorial estimate; always displayed with the «≈» mark | Precedence when values conflict: most recent A > V > B > C > D. Rankings and league tables use A/V/B values only; D values are shown but never ranked. A quarterly pipeline run appends the new measurement to `history[]` rather than overwriting. ## 5. Operator verification (`verified`) Set only via the self-claim process (see the Self-Claim Process document): a representative of the operating authority confirms the record from an official domain. Verification covers descriptive fields at the date given; measured values keep their own per-value trust. Verification expires after 24 months (`verified.date` older → badge greys out to "previously verified"). ## 6. Versioning, snapshots and DOI - Schema: semantic versioning; this document is `schema 1.0.0`. Additive optional fields → minor; breaking changes → major, with migration notes. - Data: the live `portals.json` is continuous; each quarter a frozen snapshot `portals-YYYYQn.json` is archived and receives a DOI. - DOI route (pragmatic order): **(1) Zenodo** — immediate, free, versioned DOIs with a concept-DOI for the series; suitable from day one. **(2) DataCite direct** — once the catalog has institutional backing: membership via a national consortium member (for Ukraine, DataCite members operate via EOSC/national nodes; ГО «Закарпатська медична асоціація» can act as the publishing organisation) using repository account + Fabrica; prefix fees apply. Zenodo DOIs are DataCite DOIs, so route 1 does not block route 2. ### Draft DataCite/Zenodo deposition metadata (application text) > **Title:** data-gov.info Registry of Government Open Data Portals — Quarterly Snapshot > **Creator:** Kryzhevskyi, Viacheslav (data-gov.info); **Publisher:** data-gov.info / Zakarpattia Medical Association NGO > **Resource type:** Dataset · **License:** CC BY 4.0 · **Language:** en > **Description:** A curated, trust-scored registry of government open data portals worldwide. Each record describes one portal in 27 properties (schema 1.0.0), including platform, API, licence, legal basis, EU Open Data Maturity assessment and a time series of dataset counts. Every measured value carries {value, qualifier, date, method, trust}, with five trust levels from API-measured (A) to estimate (D) and operator-verified (V). Quarterly snapshots are frozen and versioned; this DOI series enables citation of specific figures at specific dates. > **Methodology URL:** https://data-gov.info/methodology · **Related identifier:** https://data-gov.info (IsSupplementTo) > **Subjects:** open government data; data portals; e-government; open data maturity; metadata registry ## 7. Editorial process Quarterly cycle: automated API sweep (robots-respecting, ≤2 requests/portal) → diff review → editorial approval → snapshot + DOI → changelog entry. Out-of-cycle changes only via self-claims or error reports. All changes are public in the git history of `portals.json`.