Alignment with DCAT-AP

[JohannesLipp]

Assure full compatibility for the DCAT application profile (DCAT-AP) of the European Union in version 2.0.0 (https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/release/200).

[JohannesLipp]

Overview of DCAT-AP constraints and their implications to the IDS Infomodel

• skos:Concept
  • used in Concept
  • skos:prefLabel 1..*
  • Suggested Action: Adopt
  • tbd: ids:Concept is abstract, but never used. How to continue?
• skos:ConceptScheme
  • Not used
  • dct:title 1..*
  • Suggested Action: None
• rdf:Resource
• dcat:Catalog
  • used in Catalog
  • dct:description 1..*, dct:title 1..*, dct:publisher 1..1
  • Action: tbd: Currently, we handle ids:Catalog differently from DCAT, as we do not specify these fields explicitly.
• dcat:Distribution
  • used in DigitalContent and Representation
  • dcat:accessURL 1..1
  • Action: tdb: Compatibility of ids:accessUrl with dcat:accessURL
• dcat:Dataset
  • used in DigitalContent (and its subclass Resource)
  • dct:description 1..*, dct:title 1..*
  • Action: Adopt
• dcat:DataService, dcat:CatalogRecord, dcat:Relationship
  • not used
• spdx:Checksum
  • not used (ids:checkSum instead), is optional anyway

[JohannesLipp]

For all ids terms, we need to introduce idsm:notNull annotations. Also, we need to integrate the above-mentioned restrictions into SHACL shapes.

[HaydarAk]

FYI: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/distribution/dcat-ap-12-shacl

[clange]

@JohannesLipp as #391 was merged, could you please clarify what still remains to be done in order to achieve full DCAT-AP compatibility? To my understanding we are ready in a technical sense but need to discuss whether in a general IDS environment it will make sense to enforce the same "mandatory attributes" as DCAT-AP does. DCAT-AP compatibility is increasingly being requested, see https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/90.

[JohannesLipp]

The following steps would be required to do so:

1. Content: Use the EC's DCAT-AP SHACL shapes to validate all relevant classes in the IDS infomodel and subsequently integrate these into our validation shapes.
2. Infrastructure: Design and implement a way to enforce validation and compatibility in the IDS components.