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
{{ message }}
This repository was archived by the owner on Apr 26, 2022. It is now read-only.
Issue #7 discussion uses arguments based on a schema.org property domain, but schema.org itself does not define property domains in the formal sense of rdfs:domain. Actually schema.org loosely defines "expected" or "suggested" or "allowed" properties for a given type. At http://schema.org/docs/gs.html#schemaorg_types one can read that a type "has" properties.
The semantics of rdfs:domain is harder : bearing a property entails to be an instance of the class defined by the property domain.
The interpretation of the schema.org type-has-property declarations in terms of rdfs:domain is an assumption made by rdfs.schema.org, but do we agree this is correct?
The text was updated successfully, but these errors were encountered:
Just stumbled upon this issue via Google, so don't know whether it is current... but Schema.org's official OWL version does use rdfs:domain to make domain constraints explicit.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue #7 discussion uses arguments based on a schema.org property domain, but schema.org itself does not define property domains in the formal sense of rdfs:domain. Actually schema.org loosely defines "expected" or "suggested" or "allowed" properties for a given type. At http://schema.org/docs/gs.html#schemaorg_types one can read that a type "has" properties.
The semantics of rdfs:domain is harder : bearing a property entails to be an instance of the class defined by the property domain.
The interpretation of the schema.org type-has-property declarations in terms of rdfs:domain is an assumption made by rdfs.schema.org, but do we agree this is correct?
The text was updated successfully, but these errors were encountered: