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
72 stars 24 forks source link

dct:coverage for Distributions #197

Closed sabinem closed 2 years ago

sabinem commented 3 years ago

In DCAT-AP-CH we have a property dct:coverage on dcat:Distribtution. I kind of struggle with this property:

Our most important use case: We have Datasets that cover all election in Switzerland from a certain year to another year and where each distribution covers the election results of just one year. For these datasets we use the coverage property on distribution and the property value is the election date.

What is your opinion on that custom dct:coverage property in our application profile. It has the range dct:LocationPeriodOrJurisdiction and the domain dcat:Distribution and dcat:Dataset. Does this conform DCAT-AP. Or can we replace it an any way with a property of DCAT-AP.

Help with this issue would be very much appreciated

jakubklimek commented 3 years ago

each distribution covers the election results of just one year

This is, however, an anti-pattern (see the note in Distribution), as the distributions should differ only in format, not in content. For this use case, you should use the dataset relation constructs. E.g. in Czechia, we use dcterms:hasPart and dcterms:isPartOf to build a dataset hierarchy, where the top dataset has no distributions, and the contained datasets are the "per year" datasets, parts of the top dataset. This is per the usage note of Relationship, which then supports more complex relations.

init-dcat-ap-de commented 3 years ago

@jakubklimek is right, but before implementing series of Datasets in another Swiss-special way, take a look at the state of DCAT3: https://www.w3.org/TR/vocab-dcat-3/#Class:Dataset_Series