Temporal resolution cardinality `[0..*]`, while `[0..1]` in DCAT-AP

[jakubklimek]

DCAT-AP defines temporal resolution on Dataset and Distribution, with [0..1] cardinality.

GeoDCAT-AP defines temporal resolution on Data Service, Dataset and Distribution with [0..*] cardinality.

At least with Dataset and Distribution, GeoDCAT-AP breaks the profiling relation.

The proposal is to reduce the cardinality in GeoDCAT-AP to [0..1] definitely in Dataset and Distribution, supported by the wording of the definitions The minimum time period resolvable....

With Data Service, there are two options:

1. There can be a parallel drawn to the spatial resolution, also [0..*], but then a usage note should be added "Represents the capabilities of the data service, i.e. in which temporal resolutions it can serve the data.", similarly to Spatial resolution in meters
2. The cardinality can be constrained to [0..*], but then the same could be done for the spatial resolutions