Cardinality of spatial and temporal coverage

Published on: 03/04/2013

In INSPIRE, datasets may have multiple spatial and/or temporal coverages.

The proposal is to support this possibility.






Thu, 04/04/2013 - 16:56

DCAT already supports these as properties of Dataset/Catalog using dct:temporal and dct:spatial respectively. 

I suggest including them as optional properties. 

Thu, 04/04/2013 - 19:26

In Draft 1, they are proposed as optional already -- spatial for both Dataset and Catalog, temporal for Dataset.

Thu, 04/04/2013 - 19:34

Actually, the issue was about the max cardinality for this properties (1 or many?) which is not explicitly specified in the draft.

See related issue.

Thu, 04/04/2013 - 20:04

My proposal would be to give all properties cardinality unlimited.

Fri, 05/04/2013 - 13:35

I agree with Makx. Unlimited cardinality.

Mon, 15/04/2013 - 20:07


The proposed resolution is to add clarification in chapter 7 that all properties have unlimited cardinality; mandatory properties 1..n, optional properties 0..n.

Tue, 16/04/2013 - 14:23

All properties with unlimited cardinality; mandatory properties 1..n, optional properties 0..n. could be quite confusing in general and also a relevant problem in same cases. Let's see some examples:

- Multiple descriptions or titles for a given Instance.

- Multiple identifiers for a given Dataset.

- Multiple release dates for a given Dataset or Catalog. 

- Multiple licenses for a given Distribution.

- Multiple byteSizes for a given Distribution.

and so on...

I think a more detailed case-by-case analysis may be needed for cardinality.

Wed, 17/04/2013 - 11:46

Yes, you are right. I will include a proposal for cardinality for all properties in the Application Profile in the next version.

On your specific points:

  • mulitple names and descriptions are possible to allow for parallel language versions
  • mulitple identifiers are possible to allow for local identifieres, DOIs, ARKs and other types of identifiers
  • mulitple release dates would indeed not be useful
  • mulitple licences for the same distribution would indeed be a problem
  • byteSize is not in the Application Profile

Fri, 26/04/2013 - 10:54

Cardinalities have been specified in Draft 2.