schema.org.notes.md

schema.org.notes.md

There are rdfs:domain and rdfs:range already. Why does schema.org use schema:domainIncludes and schema:rangeIncludes instead?

Answer:

Schema.org doesn't want you to do inferencing using certain properties. If I knew that

schema:name rdfs:domain schema:Person

then whenever I saw a schema:name defined for an object, I could infer that the object was of type schema:Person.

Schema.org uses schema:name for lots of things so uses schema:domainIncludes to indicate how you could or should use it but doesn't lock it down.

references

RDFS: same property for multiple domains

• https://stackoverflow.com/questions/23724182/rdfs-same-property-for-multiple-domains

Are schema:domainIncludes and rdfs:domain (as well as schema:rangeIncludes and rdfs:range) the same?

• https://stackoverflow.com/questions/61726754/are-schemadomainincludes-and-rdfsdomain-as-well-as-schemarangeincludes-and-r