Open sabinem opened 3 years ago
This is in my opinion of paramount importance. It is of little interest to tell people that DCAT-AP CH wants to be interoperable but it lacks mandatory or recommended classes and properties from DCAT-AP. Neither should I, as a data publisher on opendata.swiss, have to keep 2 different documents at hand to be sure to be compliant. As stated in the original post, the CH documentation should be enough
Dear @AFoletti, we updated the description based on your remarks. I hope it's clearer that way?
Dear @AFoletti, we updated the description based on your remarks. I hope it's clearer that way?
It is, thanks!
Property: DCAT-AP properties that are not specified in DCAT-AP CH Class: DCAT-AP classes that are not specified in DCAT-AP CH Conformance Problem: Currently all mandatory and recommended classes and properties from DCAT-AP are defined in DCAT-AP-CH. Portal managers (“data receivers”) and data publishers (“data providers”) need guidance on what it means for them if a class or property is specified in DCAT-AP but not in DCAT-AP CH: can they use it, will the data portal support it? Proposal:
Possible consequences on opendata.swiss