Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guideline about usage of DCAT fields desired for proper interoperability #273

Open
SebastianOpriel opened this issue Sep 24, 2024 · 0 comments

Comments

@SebastianOpriel
Copy link
Member

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant