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
We also expect that often, where we expect a property value of type Person, Place, Organization or some other subClassOf Thing, we will get a text string.
So, where we say that the range of some property is schema:Person, we should expect to get a simple string value some of the time. Possible answers:
We document proper usage. While some improper usage is expected and consumers should deal with it, we don't have to document such usage.
Well, who said that schema:Person is disjoint from strings? In fact, we could translate the quote above into RDFS like this:
xsd:string rdfs:subClassOf schema:Thing.
The text was updated successfully, but these errors were encountered:
From the schema.org documentation:
So, where we say that the range of some property is
schema:Person
, we should expect to get a simple string value some of the time. Possible answers:schema:Person
is disjoint from strings? In fact, we could translate the quote above into RDFS like this:xsd:string rdfs:subClassOf schema:Thing.
The text was updated successfully, but these errors were encountered: