Documentation

Site information

Getting started
A simple introduction to microdata and using schema.org for marking up your site.
Frequently asked questions
How we work
Releases
Full history of recent releases.

Schemas
The actual schemas, arranged in a hierarchy, with a page for each item in the schema.
The full type hierarchy
The full type hierarchy, in a single file.
Data model
A brief note on the data model used, etc.
Style guide
Naming conventions and related patterns for schema authoring.
Developers
Developer-oriented information about schema.org.
Vocabulary definition download
Download definition files for core vocabulary and extensions.
Extension mechanism
The extension mechanism that can be used to extend the schemas.
Schema.org COVID-19 response
US CDC Data Table fields.
Overview of dataset-related vocabulary
External enumerations (blog post)
How to use external controlled lists to add detail.

Health and medical types
Notes on the health and medical types under MedicalEntity.
Hotels
Background information and examples on the types and properties for marking up hotels and other accommodations using e.g. Hotel and HotelRoom.
Autos
Bckground information on marking up automobiles.
Banks and financial institutions
Background information and examples on the types and properties for marking up banks and their products e.g. MortgageLoan and ExchangeRateSpecification.

Schema.org blog
Schema.org Community Group

Since April 2015, the W3C Schema.org Community Group is the main forum for schema collaboration, and provides the [email protected] mailing list for discussions. Schema.org issues are tracked on GitHub and coordinated via the group.

Earlier discussions can be found in W3C's public-vocabs group. There was also a google group used during 2011.

Prior to 2014, the W3C Web Schemas group hosted a collection of proposals for additions and improvements to schema.org.
Search
A custom search across all these discussions and sites is also available.
General feedback form
Please give us feedback, report bugs, etc. For technical feedback, GitHub is preferred.