search

SEMICeu / DCAT-AP

This is the issue tracker for the maintenance of DCAT-AP
https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe
74 stars 24 forks source link

Add new properties to dcat: Catalog #72

Closed NatasaSofou closed 4 years ago

NatasaSofou commented 5 years ago

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

andrea-perego commented 5 years ago

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 https://github.com/SEMICeu/GeoDCAT-AP/issues/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 commented 4 years ago

Proposed resolution: Add properties:

bertvannuffelen commented 4 years ago

resolution: accepted proposal for properties dcat:service, dcat:catalog and dct:creator