Add class dcat:Resource

[mispichtig]

Add class dcat:Resource to DCAT-AP CH v3

Name and/or affiliation of the author:

Michèle Spichtig, OGD Office

Clear and concise description of the problem or requirement

For a semantic understanding of the DCAT-AP CH standard, it is important to add the class dcat:Resource to version 3.

Link to the class/property or section, screenshot (if helpful)

https://www.w3.org/TR/vocab-dcat-3/#Class:Resource

[FlorianFasmeyer]

Starting from the principle that we want to be compatible with DCAT-AP v3 (B.2 Alignment with DCAT-AP 3), there are structural discrepencies worth talking about:

Properties

• DCAT: Defines multiple properties for Catalogued Resource
• DCAT-AP: Does not define any properties for Catalogued Resource

Inheritance

• DCAT: Catalogued Resource is a superclass of:
  • dcat:Dataset
  • dcat:DataService
  • dcat:Catalog
  • Any other member of a dcat:Catalog.
• DCAT-AP: Catalogued Resource is super-class of:
  • Dataset
  • Data Service
  • Dataset Series

Notes on DCAT-AP:

• Catalogue no longer inherits from Catalogued Resource. Instead, all of its properties are implemented in its own class.
• Dataset Series now directly inherit from Catalogued Resource

UML Diagrams and Inheritance Details

The DCAT-AP CH UML is a hybrid combining elements from both DCAT and DCAT-AP, which results in noticeable inconsistencies:

• In this structure, Catalog inherits indirectly from Catalogued Resource, through the Dataset class (as in DCAT).
• Dataset, Dataset Series, and Data Service inherit directly from Catalogued Resource (as in DCAT-AP).

UML References:

• DCAT UML
• DCAT-AP UML
• DCAT-AP CH UML

Inheritence

Properties