1 of 9

Dataverse DCAT 3.0

TNO GDN

Start presentation

2 of 9

Introduction

              • Sjaak Derksen
              • Enterprise Architect
              • Geological Survey of the Netherlands
              • Part of TNO, Netherlands Organisation for Applied Scientific Research

DCAT Plugin

3 of 9

Agenda

              • Challenges
              • Solution
              • Implementation

4 of 9

Challenges

DCAT Plugin

  • There is no “one” DCAT
  • Many nations have their own DCAT application profile
  • Many sectors have their own application profile
    • GeoDCAT-AP (European, Spatial, INSPIRE)
    • ResearchDCAT-AP (European, Open Science)
    • EnergyDCAT-AP (Sectoral)
    • TransportDCAT-AP (Sectoral)
    • StatDCAT-AP (European, statistics)
    • Etc.

Family of Dutch national DCAT standards

5 of 9

Solution

DCAT Plugin

  • Make the plugin externally configurable.
  • Support one common code base
  • Allow for contributing additional configurations to support other application profiles.
    • Vannilla (provided):
      • Mapping / Configuration: 4 .property files
    • DCAT AP NL 3.0 (provided):
      • Mapping / Configuration: 5 .property files
      • Additional required metadata: 1 TSV metadata block for mandatory AP NL 3.0
  • Verify each configuration / mapping according application profile with SHApe Conformance Language (SHACL) in a unit test example mapping for compliance to national – or sectoral application profiles.
    • For instance: the Dutch DCAT AP NL 3.0 SHACL standard.
  • Code / documentation can be found here.

6 of 9

Implementation

DCAT Plugin

Dataverse

DCAT plugin

TSV

Language bundle (.properties)

per metadata block: “AP NL 3.0 mandatory” has its own block

root (.properties)

catalog (.properties)

dataset (.properties)

distribution (.properties)

service (.properties)

DCAT / JSON LD

metadata

DCAT / XML RDF

DCAT / Turtle

configuration / mapping

7 of 9

Implementation

DCAT Plugin

  • Identifies the mapping location (environment property)
  • Reads the .property configuration files
  • Performs basic configuration validation
    • Detects erroneous, missing, or empty elements
  • Standardises the input as JSON object
    • all forms: datasetJSON, datasetORE, datasetFileDetails, datasetSchema.org, dataCiteXML
  • Enables construction of the entity relational DCAT model
  • Allows selection of input via JSONPath or constants
  • Allows merging and formatting of output (e.g. version)
  • Provides 3 output formats: JSON-LD, RDF-XML and Turtle
  • Includes SHACL (SHApe Constraint Language) in unit test to verify mappings

​

8 of 9

Implementation

DCAT Plugin

root (.properties)

catalog (.properties)

dataset (.properties)

distribution (.properties)

service (.properties)

9 of 9

Thanks for your attention

DCAT Plugin

9

sjaak.derksen@tno.nl

Princetonlaan 6, 3584 CB Utrecht, Nederland.

Closure + Photo