Closed ioanano closed 6 years ago
According to MD, this could be corrected in a bug-fix release. This should not break any existing implementations, assuming they do not rely on inference engines. There should be no problem as long as they use the recommended URIs. If they do rely on inference engines, they would already have created invalid references - but no cases have been reported.
Since this issue is the same as the one referring to the range of Spatial, it will continue to be treated in that thread.
The fact that the range of dct:spatial in CPSV-AP is declared to be skos:Concept is an error - DCMI defines the range as dct:Location. That the object of the property is defined as a skos:Concept is irrelevant - usage as the object of the property triggers the inference that it is alo as a dct:Location. The current definition in CPSV-AP breaks that inference.