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

Add new properties to dcat: Catalog #72

Open
NatasaSofou opened this issue Sep 12, 2019 · 2 comments

Comments

@NatasaSofou
Copy link
Contributor

commented Sep 12, 2019

Add new properties dcat:catalog, dcat:service to dcat:Catalog

@andrea-perego

This comment has been minimized.

Copy link

commented Sep 12, 2019

GeoDCAT-AP already includes services as independent entities, and links catalogues to services using a generic property (dcat:hasPart).

dcat:service is a more specific and appropriate property than dcat:hasPart, so for sure it would be worth discussing its inclusion in GeoDCAT-AP - but taking into account backward compatibility (which may mean keep using at the same time dcat:hasPart) - see SEMICeu/GeoDCAT-AP#10

So, the question is whether dcat:service should be added in GeoDCAT-AP (which has a requirement for having service metadata) and then re-used in DCAT-AP metadata, when needed, or rather this property should be part of DCAT-AP itself (here the question is whether there is a need of having services as a resource type supported already in DCAT-AP).

@NatasaSofou

This comment has been minimized.

Copy link
Contributor Author

commented Sep 27, 2019

Proposed resolution: Add properties:

  • dcat:service
  • dcat:catalog
  • dcat:creator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.