Skip to content

Assured Open Data Publication

This specification defines additional metadata and policy requirements for the publication of Assured Open Data within a Scheme. It builds on the Open Data Publication and Data Catalog Records specifications by introducing dataset assurance levels and control over the licenses used for datasets.

Note: This document uses US English. To align with W3C and other prevalent standards, IB1 uses US English in its technical specifications and technical documentation.

RDF Prefixes

This specification uses the following prefixes:

  dcat:    http://www.w3.org/ns/dcat#
  dcterms: http://purl.org/dc/terms/
  ib1:     https://registry.trust.ib1.org/ns/1.0#

Dependencies

A Scheme using this specification must also adopt the following specifications:

It is recommended that the Scheme uses common vocabulary and definitions from the following specifications:

Metadata

Each dataset must include an ib1:datasetAssurance term.

The value of this term must be a URL identifying a dataset assurance level defined in a specification adopted by the Scheme. Where the Scheme adopts Generic Dataset Assurance Levels, the value must be one of the URLs defined in that specification.

The dataset must comply with all requirements defined by the selected assurance level.

If this field is not present, the dataset is not considered assured. The handling of unassured open datasets is outside the scope of this specification.

License Validation

Each Scheme using this specification must publish a machine-readable Open Data Allowed Licenses policy using an ib1:Policy resource in the Registry.

This policy must have:

  • A ib1:policyPurpose of https://registry.trust.ib1.org/assured-open-data/policy-purpose/AllowedLicenses

  • One or more ib1:allowedLicense fields, each containing the URL of an approved license.

The license used in the dcterms:license field of each dataset must match one of the values listed in this policy.

The Directory will reject datasets where the license is not explicitly allowed by the policy.

Example

@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix ib1: <https://registry.trust.ib1.org/ns/1.0#> .

<https://data.example.org/emissions-report/2024-01>
    a dcat:Dataset ;
    dcterms:title "Monthly Emissions Report January 2024" ;
    dcterms:description "CO2 emissions data for January 2024 reported by local authorities." ;
    dcterms:publisher <https://directory.core.trust.ib1.org/member/456789> ,
                      <https://example.org/publisher> ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    dcterms:conformsTo <https://registry.core.trust.ib1.org/scheme/assured-open-data/standard/emissions-report> ;
    dcat:keyword "emissions"@en, "CO2"@en, "local-authority"@en ;
    ib1:dataSchema <https://registry.core.trust.ib1.org/scheme/assured-open-data/format/generic-emissions/1.0> ;
    ib1:sensitivityClass <https://registry.trust.ib1.org/sensitivity-class/IB1-O> ;
    ib1:datasetAssurance <https://registry.trust.ib1.org/assurance-level/IB1-Level1> ;
    ib1:trustFramework <https://registry.core.trust.ib1.org/trust-framework> ;
    ib1:scheme <https://registry.core.trust.ib1.org/scheme/assured-open-data> ;
    dcat:distribution <https://data.example.org/emissions-report/2024-01/csv> ;
    dcat:inSeries <https://data.example.org/emissions-report> ;
    dcat:version "1.2.0" ;
    dcat:versionNotes "Minor update to field names for compliance with CSV schema v1.0" ;
.

<https://data.example.org/emissions-report/2024-01/csv>
    a dcat:Distribution ;
    dcterms:description "CSV download of the January 2024 emissions report" ;
    dcat:downloadURL <https://data.example.org/emissions-report/2024-01.csv> ;
    dcat:mediaType "text/csv" ;
    ib1:dataSchema <https://registry.core.trust.ib1.org/scheme/assured-open-data/format/emissions/1.0> ;
.

<https://data.example.org/emissions-report>
    a dcat:DatasetSeries ;
    dcterms:title "Monthly Emissions Reports from Local Authorities" ;
.