[Question] On removal of recommended/optional DCAT-AP properties #156
Description
We are currently implementing mobilityDCAT-AP 1.0.1 and were wondering how to correctly handle the removed properties, e.g., Distribution.checksum. In the documentation, the following is stated:
The removal of optional or recommended properties from DCAT-AP aims to minimise the vocabulary size of mobilityDCAT-AP, avoiding any misinterpretations and multiple usage of properties among data senders.
Should this be read as "do not use these properties and treat them as cardinality 0..0. Use the proposed alternatives."? This is especially important when mixing multiple application profiles.
To use Distribution.checksum as an example, I cannot find it in the SHACL file.
Could this potentially be a separate subsection on https://github.com/mobilityDCAT-AP/mobilityDCAT-AP/wiki/Chapter-2:-Recommendations-for-the-deployment-of-mobilityDCAT%E2%80%90AP, as this is not explicitly mentioned yet?