Guideline about usage of DCAT fields desired for proper interoperability #273
Description
I understand that the EDC makes use of DCAT for the catalog, but I would appreciate more guidance from the DSP specification (or maybe a non-normative part) on how to interpret fields in context of Data Spaces. I could nowhere find further details about following exemplarily fields and how an implementation of the DSP should interpret these. If we want to achieve interoperability for DSP, we need to give more guidance on proper interpretation.
- dcterms:publisher is for example used on Core EDC here. DCAT defines it as "The entity responsible for making the resource available."
- In context of Data Spaces a developer could interpret this field to be set as the source's provider. If I offer public data via my Connector implementing DSP this could make sense.
- Another interpretation could be, that this is always the Connector "Owner", as he/she is responsible for making the resource available.
- dcterms:creator is referenced in DSP here. Maybe this is more clear to refer to the creator of the referenced data, but could also easily be misunderstood to be set as the data offer creator.