Note: You are viewing the development version of See how we work for more details. for Developers

This page provides basic developer-oriented information about In particular it gives access to machine-readable representations of our schemas.

Machine Readable Term Definitions

There are various ways to access machine-readable definitions of terms.

Vocabulary Definition Files

To assist developers, files containing the definition of the current version of the vocabulary is available for download in common RDF formats. In addition to the links below, older release versions can be found (under data/releases/) in GitHub.

Select the file and format required and click Download. The CSV format downloads are split across two files: Types includes definitions of Types and Enumeration Values, including lists of associated properties; Properties contains property definitions.

File schemaorg-current-https contains the definition of all terms in, all sections of, the vocabulary. The file schemaorg-all-https contains the definition of all terms in, all sections of, the vocabulary, plus terms retired from the vocabulary (See the attic section for details).

For those preferring to use http based definitions of terms, these equivalent definitions are available in the schemaorg-current-http and schemaorg-all-http files. For more information on using https or http based terms see the FAQ for details.



The following representations are experimental and may change or be removed in future releases.


A simplification of the 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).


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's terms; see datamodel page for details. As an experimental feature, there are no expectations as to its interpretation by any third party tools.