Schema.org

Important Links and Official Channels The Schema.org Website ( The Schema.org Blog ( Releases and Release History ( This is the Schema.org project repository. It contains all the schemas, examples and software used to publish Schema.org. For the site itself, please see Schema.org instead. Issues and proposals are managed here by collaborators around the project, especially participants of the W3C Schema.org Community Group. If you are interested in participating please join the group at the W3C, introduce yourself and find or file issues here that engage your interest. If you are new to Git and Github, there's a useful introduction to Github in the W3C Wiki. Issue 1 will link to per-release entry points, or else navigate issues via label or milestone within Github. Every change to the site comes via discussions here. Substantive changes are recorded in our release notes. A preview of the draft new release notes can be found as part of the test site for our next release. Every month or so, after final review by the Schema.org Steering Group and wider community, we make a formal release. Regarding CC and opensource licenses for documents and software, see our FAQ entry. We are always interested in practical suggestions for improvements to Schema.org, and our collection of schemas has been growing gradually since our launch in 2011. Note that Schema.org does not attempt to capture the full detail of web content; it is necessarily a simplification of a more complex reality. This means that there will be many cases where adding more detail to Schema.org will look possible. However, in the interests of keeping Schema.org simple and usable for publishers and webmasters, we will often choose not to add such detail. Schema.org uses web standards such as JSON-LD, Microdata and RDFa to allow for independent extension (for example, see GS1's vocabulary). We are also highly unlikely to take on large-scale reorganizations of Schema.org's terminology if they are motivated solely by considerations of elegance, "proper modeling", ontological purity or conceptual unification. Although the project founders and team are familiar with - and respectful of - the traditions behind such concerns, the scale, scope and nature of Schema.org have required us to trade elegance and global consistency for a somewhat scruffier notion of incremental evolution and a pragmatic tolerance for a style that would be out of place in a formal ontology. Proposals for unifying cross-domain logic-based knowledge structures may be better received (e.g. in the Ontolog community). We sometimes introduce types without dedicated property associations, simply for markup usability reasons. In a formal ontology, this is often considered poor modeling. However, logically equivalent structures can result in many more errors from publishers/webmasters unfamiliar with the underlying formal concepts behind JSON-LD or RDF/S. Schema.org is not a closed system, and other initiatives e.g. Wikidata or GS1 have defined many other terms that can be mixed in alongside those we define at Schema.org. We also make efforts to align our designs to relevant external standards and initiatives, even when it reduces the global elegance of Schema.org considered alone. For example in a bibliographic or cultural heritage context, we may be influenced by initiatives like MARC, BibFrame, and FRBR, while for e-commerce, we collaborated with Good Relations and GS1. Schema.org's news-related terms were heavily influenced by incorporating IPTC's rNews design, alongside collaborations with fact checkers, the Trust Project, and others. Our TV and Music related vocabularies are heavily influenced by working with the BBC and the European Broadcasting Union, alongside the Music ontology and MusicBrainz; our schemas reflect these prior designs. We prefer to collaborate in this way, improving Schema.org incrementally and working to polish, integrate and blend such designs rather than produce our own pure mod