GeoDCAT-AP: GeoDCAT-AP XSLT returns multiple dcat:landingPage's

06/08/2015

References

This issue has been reported by Hans Overbeek.

http://joinup.ec.europa.eu/mailman/archives/dcat_application_profile-geo/2015-June/000094.html
http://joinup.ec.europa.eu/mailman/archives/dcat_application_profile-geo/2015-June/000098.html

Explanation

We use dcat:landingPage in GeoDCAT-AP when a resource locator is missing a function code, and we may have more than one resource locator like this. The max cardinality of dcat:landingPage is 1 in DCAT-AP. However, the DCAT definition of dcat:landingPage does not require at most 1 landing page per dataset - see: http://www.w3.org/TR/vocab-dcat/#Property:dataset_landingpage

There's a proposal under consideration in the DCAT-AP WG to drop the max cardinality constraint - see related issue: 

https://joinup.ec.europa.eu/node/144726/

If this proposal will not be accepted, we have to find a way to solve this issue in GeoDCAT-AP, at least, from the implementation side.

Component

Code

Category

bug

Comments

Mon, 23/05/2016 - 12:27

In DCAT-AP 1.1, the max cardinality of dcat:landingPage has been change from 1 to N.

Closing the issue.

The content of this field is kept private and will not be shown publicly.