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
Publishers behind http://schema.org URIs are unlikely to ever provide any RDF description, so why are those URIs declared as identifiers of RDFS classes in the http://schema.rdfs.org/all.rdf. For all I can see, http://schema.org/Person is the URI of an information resource, not of a class.
So I would rather have expected mirroring of the schema.org URIs by schema.rdfs.org URIs, the later fully dereferencable proper RDFS classes expliciting the semantics of the former, while keeping the reference to the source in some dcterms:source element.
The RDFa example in the schema.org documentation explicitly uses their URIs as classes and properties. So they are classes and properties, according to the URI owner. However, the URI owner is not configuring these URIs according to what we consider best practice. Maybe they'll fix this one day, and that should certainly be our long-term hope; and in the meantime, schema.rdfs.org provides the vocabulary documentation in RDF format, in a non-standard, out-of-band location.
IMHO, the value of schema.org lies in the (quasi-)standard set of vocabulary terms that are likely to achieve widespread adoption due to Google's backing. Minting a parallel set of URIs would just encourage fragmentation.
(copied from message at LOD list)
Publishers behind http://schema.org URIs are unlikely to ever provide any RDF description, so why are those URIs declared as identifiers of RDFS classes in the http://schema.rdfs.org/all.rdf. For all I can see, http://schema.org/Person is the URI of an information resource, not of a class.
So I would rather have expected mirroring of the schema.org URIs by schema.rdfs.org URIs, the later fully dereferencable proper RDFS classes expliciting the semantics of the former, while keeping the reference to the source in some dcterms:source element.
e.g., http://schema.rdfs.org/Person dcterms:source http://schema.org/Person
etc
The text was updated successfully, but these errors were encountered: