You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, cn:isNameFor specifies that its inverse property is schema:name. This is problematic since schema:name in schema.org is defined as a sub-property of rdfs:label, which states that all object values are rdfs:Literal due to its rdfs:range definition.
We want to link between feature objects and compound name objects, not literals.
To resolve this, I would like to suggest cn:hasName as the new property as the inverse of cn:isNameFor.
The text was updated successfully, but these errors were encountered:
Currently,
cn:isNameFor
specifies that its inverse property isschema:name
. This is problematic sinceschema:name
in schema.org is defined as a sub-property ofrdfs:label
, which states that all object values arerdfs:Literal
due to itsrdfs:range
definition.We want to link between feature objects and compound name objects, not literals.
To resolve this, I would like to suggest
cn:hasName
as the new property as the inverse ofcn:isNameFor
.The text was updated successfully, but these errors were encountered: