Cardinality of dcat:downloadURL

[claaboudi]

Cardinality of dcat:downloadURL (optional) should be 0...n (instead of 1...n).

[bertvannuffelen]

@claaboudi this is the outcome of the proposal in #49. From the changelog, the proposed restriction are:

• dcat :accessURL, Cardinality: 1..n -> 1..1 (mandatory property)
• dcat :downloadURL, Cardinality: 0..n -> 0..1 (optional property)

but on page 17 of the specification:

• dcat:downloadURL is still 1..n instead (to be corrected)

The occurrence of accessURL is correct in the specification.

[init-dcat-ap-de]

Even though we initiated this idea we would like to bring a use case for multiple download URLs to the table: especially for bigger files, it could be useful to offer multiple sources where they could be found, to increase the availablity or for load balancing.

Another solution could be, to specify that the Checksum is always for the downloadURL (if given), never for the accessURL.

[bertvannuffelen]

@init-dcat-ap-de how do we proceed with this request? Do we retract the extra range restrictions and replace it with the latest request?

[bertvannuffelen]

resolution: maintain the original cardinality request as it more naturally fits the semantics of a Distribution.

[bertvannuffelen]

after reconsideration this resolution has been retracted and this topic will be added for future-work

[akuckartz]

this topic will be added for future-work

Where and when?