Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use cn:hasName for inverse property of cn:isNameFor #4

Open
edmondchuc opened this issue Jan 28, 2025 · 0 comments
Open

Use cn:hasName for inverse property of cn:isNameFor #4

edmondchuc opened this issue Jan 28, 2025 · 0 comments

Comments

@edmondchuc
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant