Consider using/adding DCAT to represent our metadata #640
Description
Remarks:
- This means importing it in the knowledge engine ontology.
- This could increase the size of metadata graph patterns (if we decide to include these DCAT statements in our graph patterns) and thus increase the resources usage when reasoning about this metadata.
- We could also only include it in our ontology (as domain knowledge) and use this domain knowledge to reason about some of the properties.
- We could publish the DCAT catalogue of a particular Knowledge Engine Runtime (or SC?) via our REST API.
- DCAT 3 also supports data services, which the TKE would provide.
- Eclipse dataspace components already uses DCAT to represent its catalogues and datasets.
See latest DCAT specification: https://www.w3.org/TR/vocab-dcat-3/