-
Notifications
You must be signed in to change notification settings - Fork 201
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
Support for schema:domainIncludes and schema:rangeIncludes #178
Comments
I would very much like this as well! Whoever implements this: you may also want to support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the visual editor it would be great if one could use the less restrictive schema:domainIncludes and schema:rangeIncludes when describing relationships between classes. Visually, it's great to show that eg schema:author could be a relationship between a schema:Rating and a schema:Person, but as it is now, this would infer a
rdfs:domain schema:Rating
on schema:author which is not correct (other things than ratings can also have authors). The correct way to model it would be to model the relationship from owl:Thing to schema:Person, but then the unfamiliar reader will not understand it.So my suggestion is to support the less restrictive properties to simply indicate that the relationship "could exist" between the instances of those two classes.
The text was updated successfully, but these errors were encountered: