Problem statement
DCAT 3 has a policy on usage of inverse properties, where the inverse properties may be used only in addition to the primary ones. In DCAT-AP 3.0, this was reflected by removal of the inverse properties from the profile.
GeoDCAT-AP 2.0.0 includes the following inverse properties:
dct:isVersionOf, which was to be replaced with dcat:isVersionOf following the alignment with DCAT 3 and DCAT-AP 3.0, which is an inverse property
foaf:isPrimaryTopicOf is used in several examples. This may be to improve readability compared to the usage of foaf:primaryTopic, but may also be confusing and encourage usage of just the inverse property.
Proposal
Follow the approach of DCAT-AP 3.0 and remove inverse properties from GeoDCAT-AP. Specifically:
deprecate dct:isVersionOf in favor of the new dcat:hasVersion (dct:hasVersion replacement) (#73)
change examples to use the primary foaf:primaryTopic
Problem statement DCAT 3 has a policy on usage of inverse properties, where the inverse properties may be used only in addition to the primary ones. In DCAT-AP 3.0, this was reflected by removal of the inverse properties from the profile. GeoDCAT-AP 2.0.0 includes the following inverse properties:
dct:isVersionOf
, which was to be replaced withdcat:isVersionOf
following the alignment with DCAT 3 and DCAT-AP 3.0, which is an inverse propertyfoaf:isPrimaryTopicOf
is used in several examples. This may be to improve readability compared to the usage offoaf:primaryTopic
, but may also be confusing and encourage usage of just the inverse property.Proposal Follow the approach of DCAT-AP 3.0 and remove inverse properties from GeoDCAT-AP. Specifically:
dct:isVersionOf
in favor of the newdcat:hasVersion
(dct:hasVersion
replacement) (#73)foaf:primaryTopic