Schema.org for Developers
This is a placeholder page for developer-oriented information about schema.org. In particular it gives access to machine-readable representations of our schemas.
Machine Readable Term Definitions
Machine-readable definitions of individual terms are available as JSON-LD, embedded into the term page html.
Vocabulary Definition Files
To assist developers, files containing the definition of the current version of the Schema.org vocabulary are available for download in common RDF formats.
Experimental/Unsupported
The following representations are experimental and may change or be removed in future releases.
D3 RDFS in JSON-LD
A simplification of the Schema.org type hierarchy, in which each type has at most one super-type, represented in a hybrid format that combines JSON-LD, RDFS and D3: tree.jsonld.
This file is made available to support developers using the D3 JavaScript library for manipulating documents based on data. It uses JSON-LD to declare that D3’s default “children” JSON field represents “subClassOf” relationships, but expressed in the reverse direction (example usage).
OWL
As an experimental feature, an OWL definition file schemaorg.owl is available. It includes the core and all current extensions to the vocabulary.
The structure of the file differs from the above vocabulary definition files, in that schema:domainIncludes
and schema:rangeIncludes
values are converted into rdfs:domain
and rdfs:range
values using owl:unionOf
to capture the multiplicity of values. Included in the range values are the, implicit within the vocabulary, default values of Text, URL, and Role.
This file has been made available to enable the representation of the vocabulary in some OWL-based modeling tools. The mapping into OWL is an approximation, and should not be considered an authoritative definition for Schema.org’s terms; see datamodel page for details. As an experimental feature, there are no expectations as to its interpretation by any third party tools.