Mapping ORKG resources and properties to external terminologies
In order to increase the data quality and interoperability, mapping/interlinking ORKG terminology to external terminology (or ontologies) is an important curation task. We should establish a preferred approach, in particular in terms of properties used for the mappings. Currently it is mostly (same as) but IMO it is not a great property because it remins of owl:sameAs, which has well defined semantics and implies a accordingly logic / reasoning, which in ORKG is hardly ever true. Perhaps properties such as (SKOS) exactMatch and closeMatch are better. Or perhaps managing mappings in a third-party service is even the more promising way to go, e.g. via a SSSOM service (https://mapping-commons.github.io/sssom/spec/).