This release introduces new core vocabulary including mechanisms for describing fact-check reviews, courses, and menus. It also introduces
a number of newly-proposed terms via the "pending" area, to encourage discussion, implementation feedback and other improvements.

The meta.schema.org extension contains terms primarily designed to support the implementation of the Schema.org vocabulary itself.

The pending.schema.org extension is a staging area for work-in-progress terms which have yet to be accepted into the core vocabulary. Pending terms are subject to change and should be used with caution.

In addition to numerous vocabulary-related improvements, we have added a new "How we work" document providing an overview of the project's approach to schema development, collaboration, versioning and change review.
In particular it documents the use of the new pending extension, which gives earlier access to proposed new schema designs,
as well the parallel webschemas.org site which shows the latest work-in-progress version of the entire schema.org site.

Version 2.2 (working name 'sdo-phobos'). This release combines a range of small additions across several areas of schema.org with an ongoing
concern for cleanup and integration of existing vocabulary. Notable additions include ExhibitionEvent,
Barcode, DataFeed, containsPlace, GeoCircle,
geoRadius, geoMidpoint, providerMobility
and actionPlatform. A number of changes improve our handling of Service description, including the
deprecation of the ProfessionalService construct. We have kept all the specific types that were previously
considered ProfessionalService but discourage the use of the type 'ProfessionalService' since it is easily confused with 'Service'.

Version 2.1 (working name 'sdo-ganymede') includes many small fixes, some new vocabulary, as well as the first release of the 'hosted extensions' mechanism, featuring bib(liographic) and auto(mobile) extensions for final review. A pre-release of this version of schema.org was available at sdo-ganymede.appspot.com/ for review.

Issue #137: Deprecated UserInteraction and its children in favor of a new type: InteractionCounter. InteractionCounter allows for reporting aggregated statistics by service and type. Thanks elf Pavlik for collaboration.

Issue #334: Updated the controlled values for accessibilityHazard shown in examples to follow latest community recommendations: 'noFlashing' is now 'noFlashingHazard', 'noMotionSimulation' is 'noMotionSimulationHazard', and 'noSound' is 'noSoundHazard'.

Issue #78: Multiple supertypes are now displayed properly. It is possible for several schema.org types to apply to a single thing, and for a type to have multiple parent types. This is relatively rare, but important to display. For example, anything that is a LocalBusiness is considered both an Organization and a Place; so all subtypes of LocalBusiness have both as supertypes. We can now show this more clearly, e.g. ElectronicsStore.

Added CSS for explicit styling () in releases page during Steering Group review of candidate releases.

Version 2.0 consolidates and integrates schema.org's existing vocabulary. This version features many updated definitions, type/property associations and term names that
improve consistency and usability. It also introduces a new extension system.
Version 2.0 adds various new terms including mainEntityOfPage and major contributions from the
Automotive Ontology community.

Issue #170: Clarifying CommentAction, Comment by deprecating UserComments. Several mentions of UserComments removed from other terms. 'inLanguage' supersedes 'language'. Added a resultComment property. UserInteraction and sub-types will be deprecated.

Issue #300: Answer is now a sub-type of Comment. The 'question' property expects 'Question' type for its values (rather than Text as in AskAction previously). Added resultComment on ReplyAction. Cleaned up examples.

Provider/Seller vocabulary: this update also clarifies how to use a set of related terms, integrating sections of schema.org that had developed
separately. Full details are documented at W3C
and in Github, alongside an overview document.
The provider property describes a service provider, service operator, or service performer, while
seller describe the entities which sell or offer a service on behalf of an actual service provider. We
introduce a more general broker property (replacing the over-specific bookingAgent),
as well as deprecating vendor and merchant in favour of seller.
Regarding flights and parcel delivery, carrier is
superseded by provider. Please also note that flightNumber should now be written in full (i.e. "UA110" rather than just "110").
See the supporting documents for details.

Added a new CreativeWork type, WebSite: "A WebSite is a set of related web pages and other items typically
served from a single web domain and accessible via URLs." Also adopts the suggestion made by the BibExtend group and other
collaborators, to broaden the isPartOf property, which now relates any CreativeWork to any other CreativeWork.
This release also makes the Potential Actions documentation available in HTML.
Several markup fixes from Stéphane Corlosquet, alongside
improvements to the consistency of encoding /
associatedMedia property definitions thanks to Dan Scott.
(announcement)

This release introduced the notion of a Role type to schema.org. See the blog post
for details. The Role mechanism applies across all of schema.org, and allows simple statements to be elaborated or
qualified, for example with temporal information. Other changes in this release include the addition of a
license property, and some documentation of properties used internally by schema.org's documentation system
(Property, Class, supersededBy, inverseOf).
Fixed an embarrassing typo - "dead" - in the diet property - thanks, Dan Scott. Various other
small changes - listed in the preview announcement.
(announcement and
candidate release)

1.5 (2014-05-27)

Tweaks and fixes.

Tweaks to definition of 'keywords' to indicate that comma-separated entries are expected.
Several typo fixes from Stéphane Corlosquet. Adds a new icaoCode
text-valued property for Airport.
Updated description for flightNumber to note "not including the airline IATA code".
Added missing Actions-related definitions (urlTemplate, valueName).
(announcement)

1.4(2014-05-16)

Examples, examples, examples.

Added two examples to accompany workPerformed. Added several local business, company contact and music event examples.
Several glitch and typo fixes including MedicalEnumeration, thanks to Dan Scott.
announcement blog post

(candidate release drafted as '1.0g'; not
formally announced but included in the change
to github-based publishing)

1.0f(2014-02-05)

Not-for-profit Offer and other fixes.

This version adapts the wording around the Offer type to suit non-profit scenarios,
such as libraries. Thanks to Dan Scott and the BibExtend group for these proposals.
This change broadens the definition of Offer and makes associated changes to
ItemAvailability and
OfferItemCondition, typically rewording "the item for sale" to
simply say "the item". The itemOffered property is now defined more
appropriately as "The item being offered." rather than "...sold.". The "seller"
property is now defined as "The organization or person making the offer.", a compromise to support
its use for more kinds of offer.
(candidate release
and announcement)

Introduced a (past-tense) Actions vocabulary (see wiki)
This updated added an Action type, supporting properties, and a substantial set of subtypes. It was
followed in 2014 by a mechanism for describing potential actions.
(announcement)

Adds sameAs property to Thing that makes it easier to indicate identifying URLs for entities
being described (wiki).
The citation property has been moved up to CreativeWork, from
MedicalScholarlyArticle (wiki).
Thanks to the BibExtend group for suggesting this small but useful improvement.

Added additionalType property (wiki).
"An additional type for the
item, typically used for adding more specific types from external
vocabularies in microdata syntax. This is a relationship between
something and a class that the thing is in. In RDFa syntax, it is
better to use the native RDFa syntax - the 'typeof' attribute - for
multiple types. Schema.org tools may have only weaker understanding of
extra types, in particular those defined externally."
(announcement)

This release added substantial vocabulary in the medical/health domain (around 100 classes, 200 properties). The additions are
mainly organized beneath the MedicalEntity type. An
overview document is also provided. From the blog post:

"This collaborative project drew upon search expertise from the schema.org partners but also gained immeasurably through feedback from expert reviewers including the US NCBI; physicians at Harvard, Duke and other institutions, as well as from several health Web sites. Contributions from the W3C Healthcare and Lifesciences group and Web Schemas community also helped bridge the complex worlds of Web standards, search and medicine/healthcare."

Converged URL/Url spelling. After WebSchemas discussion, consensus was:
For each of embedURL, contentURL, downloadURL, ensure there is an equivalent property named with mixed-case: 'embedUrl', 'contentUrl', 'downloadUrl'.

Note: this table is not currently complete - it misses 0.92-0.94 and any changes between 2011-06-02 and 2012-04-21(0.91). See also Linked Open Vocabularies entry.