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 cardinality constraint max 1 on dcat:temporalResolution #114

Closed bertvannuffelen closed 2 years ago

bertvannuffelen commented 4 years ago

From the comment on https://github.com/SEMICeu/DCAT-AP/issues/78#issuecomment-554794438, and https://github.com/SEMICeu/DCAT-AP/issues/76#issuecomment-554794160

Just like on the dataset level: I think both dcat:temporalResolution and dcat:spatialResolutionInMeters should have a maximum cardinality of 1, currently it says "0..n" in the specification.

bertvannuffelen commented 2 years ago

To the community:

2 topics here: a) Do we restrict the spatialResolution & temporalResolution for a dataset? b) Do we restrict the spatialResolution & temporalResolution for a distribution?

If no support for either of the proposals is given, then the proposal is not to apply the restrictions.

bertvannuffelen commented 2 years ago

wg of 21 oct 2021 decided to apply the max cardinality in order to remove the incoherency between the usagenote text which refers to the minimum value. And to apply this in all cases.

andrea-perego commented 2 years ago

@bertvannuffelen :

wg of 21 oct 2021 decided to apply the max cardinality in order to remove the incoherency between the usagenote text which refers to the minimum value. And to apply this in all cases.

Although this would make sense for distributions, setting the max cardinality to 1 for datasets will be in contrast with the practice of publishing multiple distributions of the same dataset, each with different resolution - e.g., the NUTS.

bertvannuffelen commented 2 years ago

In the WG the attention was drawn to the word "minimum". So in the example, the minimum (most precise) resolution of all NUTS distributions should be used as value for the resolution.