Add a "notEquivalentTo" property to the vocab files?

[UlrikeS91]

This came up during the openMINDS dev meeting in the context of mapping schema.org vocab to populate the "semanticEquivalent" in both properties.json and types.json.

I came across one example where the property name is identical to ours, but the definition is too narrow to fit our property: https://schema.org/amount (definition: The amount of money.).

Therefore, we cannot add this under "semanticEquivalent" but it would be great if we could map it as something like "notEquivalentTo" (or "notToBeConfusedWith" as @olinux suggested 😉). This way the work could be captured and that we have indeed identified this as not equivalent. By leaving "semanticEquivalent" empty, it could either mean that it has not been mapped yet or that the checked properties from other (meta)data models did not fit. The ambiguity is a bit of a problem.