Closed steveraysteveray closed 10 months ago
In some cases they may be replaced by
owl:equivalentClass
owl:equivalentProperty
skos:exactMatch
which probably cause less pain.
True. For now, we have qudt:exactMatch instead. In the future, if a need for one of the owl or skos relations becomes clear, a quick SPARQL query could fix that.
Has the use of qudt:exactMatch eliminated the problem? So the new policy is that only qudt:exactMatch will be used and you have already proliferated this change throughout the schema and vocabularies? And which OWL reasoners were affected?
...as it causes problems with OWL reasoners.