handle sameAs and deprecation in resources
Opened this issue · 0 comments
rob-metalinkage commented
resources could gather all the known properties of a resource using the owl:sameAs semantics, deduplicating object values.
In addition status highlighting for deprecated could use a (configurable) predicate value to point users to the resource they should use by preference.
Should owl:sameAs semantics be used this way if the subject is marked deprecated? If not then strict semantics suggests sameAs cannot have different status values.