search

mobilityDCAT-AP / mobilityDCAT-AP

Repository of the metadata specification mobilityDCAT-AP
https://w3id.org/mobilitydcat-ap
Creative Commons Attribution 4.0 International
9 stars 4 forks source link

Dataset class: mandatory frequency proprety #22

Closed Bfrichet2 closed 2 months ago

Bfrichet2 commented 4 months ago

Dear

I noticed in your mobilityDCAT-AP profile frequency property is a MUST in the meaning of 1st section of RFC 2119 in the definition of the Dataset object type.

This is a clear restriction regarding to DCAT AP specifications as both DCAT AP 2 and 3 set this property as OPTIONNAL in the meaning of ther 5th section of RFC 2119.

Therefore I would align the requirement

I think this is a very surprising position as that property is "Recommended" in the current version of DCAT AP 3 (https://semiceu.github.io/DCAT-AP/releases/3.0.0/#quick-reference). Many data provider in my country do not maintain such an information. Moreover this is not a metadata element that is required for INSPIRE dataset which means INSPIRE datasets won't have such a property on the one hand or this will go against once only principle on the other hand.

Therefore I strongly recommend to specify this property as OPTIONNAL or as RECOMMANDED in the meaning of 5th and 3rd sections of RFC 2119.

Regards,

peterlubrich commented 3 months ago

mobilityDCAT-AP is an extension to DCAT-AP. Following the DCAT-AP extension guidelines, we are allowed to raise obligation levels of classes or properties. We are doing so in several cases, when we feel that certain metadata information is crucial for mobility data. Mobility data may have update cycles between 1 year (maybe geodata) and 1 millisecond (Automated Driving) . Thus, mobility datasets should be distinguishable via this property, so it is mandatory.

Bfrichet2 commented 2 months ago

@peterlubrich thank you for your answer. As some dcat:Dataset are created from the INSPIRE legal framework and as the INSPIRE metadata does not include anything concerning update frequency it is quite clear to me that this property won't be provided in that case (at least without revision of EC 1205/2008 Regulation). In that perspective I strongly recommend to specify as a SHOULD and not as MUST otherwise you already know that many dcat:Dataset aren't to be compliant with this non-legally binding profile.