Dataset class: mandatory frequency proprety

[mobilitydcat-ap]

Dataset class: mandatory frequency proprety

[peterlubrich]

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]

@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.