<commit_before><!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>How we work - schema.org</title>
    <meta name="description" content="Schema.org is a set of extensible schemas that enables webmasters to embed
    structured data on their web pages for use by search engines and other applications." />
    <link rel="stylesheet" type="text/css" href="schemaorg.css" />
    <link href="prettify.css" type="text/css" rel="stylesheet" />
    <script type="text/javascript" src="prettify.js">
    </script>
    <script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js"></script>

<script type="text/javascript">
      $(document).ready(function(){
        prettyPrint();
        setTimeout(function(){

    $('.atn').each(function(i) {
      if (($(this).text() == 'itemscope') || ($(this).text() == 'itemtype') || ($(this).text() == 'itemprop') || ($(this).text() == 'itemid') || ($(this).text() == 'time') || ($(this).text() == 'datetime') || ($(this).text() == 'vocab') || ($(this).text() == 'property') || ($(this).text() == 'typeOf') || ($(this).text() == 'rel'))
        $(this).addClass('custom');
    });

        }, 500);
      });
</script>

<style>

  .tag    { color: #000; }    /* div, span, etc   */
  .atn    { color: #000; }    /* href, datetime,  */
  .custom { color: #660003; } /* itemscope, itemtype, etc,. */

  dt { font-weight: bold; padding: 0.3em 0 0.4em 0;}
</style>

</head>
<body>
    <div id="container">
        <div id="intro">
            <div id="pageHeader">
              <div class="wrapper">
				<div id="sitename">
				<h1>
					<a href="/">schema.org</a>
				</h1>
				</div>

<div id="cse-search-form" style="width: 400px;"></div>

<script type="text/javascript" src="//www.google.com/jsapi"></script>
<script type="text/javascript">
  google.load('search', '1', {language : 'en', style : google.loader.themes.ESPRESSO});
  google.setOnLoadCallback(function() {
    var customSearchControl = new google.search.CustomSearchControl('013516846811604855281:nj5laplixaa');
    customSearchControl.setResultSetSize(google.search.Search.FILTERED_CSE_RESULTSET);
    var options = new google.search.DrawOptions();
    options.enableSearchboxOnly("../docs/search_results.html", null, false, '#');
    customSearchControl.draw('cse-search-form', options);
  }, true);
</script>


              </div>
            </div>
        </div>
    </div>

            <div id="selectionbar">
               <div class="wrapper">
                <ul>
                    <li class="activelink">
                      <a href="../docs/documents.html">Documentation</a></li>
                    <li >
                      <a href="../docs/schemas.html">Schemas</a></li>
                    <li >
                      <a href="../.">Home</a></li>
                </ul>
                </div>

            </div>
        <div style="padding: 14px; float: right;" id="languagebox"></div>

  <div id="mainContent">

<h1>How We Work</h1>

<p>
This document provides a brief overview of schema.org's process for developing and
changing schemas. It accompanies the <a href="about.html">about schema.org</a> page
which describes the organizational structure of the project.
</p>

<p>
<b>Note</b>: the <a href="http://schema.org/">schema.org</a> site contains the officially released
  version of schema.org, while <a href="http://webschemas.org/">webschemas.org</a> is> the very latest
  work-in-progress development branch of schema.org containing more recent fixes and improvements but which may
  contain changes that do not represent the consensus of the wider community or of the project <a href="/about.html#cgsg">steering group</a>. See <a href="#pending">"pending"</a>
  below for more details.
</p>

<p>This document contains a minimal amount of technical detail sufficient to explain
  our approach to schema evolution. Operational details for project collaborators can be found via
  the <a href="https://www.w3.org/community/schemaorg/how-we-work/">how we work</a>
  section of the <a href="https://www.w3.org/community/schemaorg/">Schema.org W3C Community Group</a>.
</p>

<h2>Overview</h2>

<p id="#ataglance">A quick summary.</p>

<ul>
  <li>Most materials on schema.org are updated via <a href="http://schema.org/docs/releases.html">official named releases</a> (every few weeks).</li>
  <li>Simple improvements around supporting documentation, examples, sofware bugs etc. can be fast-tracked by the project <a href="about.html#cgsg">steering group</a> as "Early Access Fixes"; these are
    also recorded in the <a href="http://schema.org/docs/releases.html">releases</a> page, which may also be updated in between formal releases.</li>
  <li>Improvements are discussed in our <a href="http://www.w3.org/community/schemaorg">community group</a> at W3C, typically in the project's <a href="http://github.com/schemaorg/schemaorg/issues">github issue tracker</a>.</li>
  <li>A work-in-progress development version of the site named "<a href="http://webschemas.org/">webschemas.org</a>" is maintained by the <a href="#webmaster">project webmaster</a> based on github and W3C community group discussions, proposals and change requests. It forms the basis for periodic "release candidates" and reflects the current state of the project's public Github repository.</li>
  <li>A "live" hosted extension dedicated to "pending" new vocabulary proposals is maintained as part of this process at <a href="http://pending.webschemas.org/">pending.webschemas.org</a>, and can be updated by the <a href="#webmaster">project webmaster</a> immediately, rather than
    waiting for a full official release. This serves to highlight possible new vocabulary improvements but may not always reflect wider consensus in the community and steering groups.</li>
  <li>Periodically, snapshots of the community's <em>rough consensus</em> are published as release candidates by the project webmaster, for review by the <a href="about.html#cgsg">steering group</a>.</li>
  <li>After steering group <a href="#w3rel">review</a> and approval, the schema.org site is updated with the new release by the project webmaster.</li>
</ul>



<h2>Versioning and change control</h2>
<p>
Schema.org is developed incrementally. Since 2011 we have published several
substantial updates a year. These are known as <em>releases</em> and are
documented on the <a href="/docs/releases.html">releases</a> page. Each release
has a name that is assigned upon publication (e.g. "2.1"). Recent releases have
also been given project-internal code names prior to launch, e.g. "sdo-phobos",
which makes it easier to decide upon the final name (e.g. "2.9" versus "3.0") as the work
develops.
</p>

<p>
The content of each release is based on public discussions hosted on W3C's
community group platform and on the Github site. All <a href="/docs/releases.html">changes</a> to the
project have been through unanimous agreement of the Steering Group membership, strongly
informed by the opinions, contributions and discussions in the wider community.
</p>

<p>
Recently we have been expanding on this model with two types of <a href="extension.html">extension</a> vocabulary: hosted and external extensions.
Hosted extensions are effectively part of schema.org but "tagged" within a subdomain (e.g. <a href="http://bib.schema.org/">bib.schema.org</a>,
<a href="http://auto.schema.org/">auto.schema.org</a>). External extensions (e.g.
see <a href="http://blog.schema.org/2016/02/gs1-milestone-first-schemaorg-external.html">GS1's Web Vocabulary</a>) are published elsewhere on the Web, and are typically managed by other
organizations with their own processes, versioning systems and collaboration mechanisms. Hosted extensions are managed and published as part
of the schema.org project, with their design often led by one or more dedicated community groups.
</p>

<p>
For general use, publishers and consumers are encouraged to use the latest release and to use simple non-versioned schema.org URLs such as 'http://schema.org/Place'
in structured data applications. However there are settings in which more precise versioning is important. Schema.org also provides dated snapshots of each release, including
both human and machine readable definitions of the schema.org core vocabulary. These are linked from the <a href="releases.html">releases page</a>. In addition,
the <a href="/schemaVersion">schemaVersion</a> property has been defined to provide a way for documents to indicate the specific intended version of schema.org's
definitions. Finally, all changes to the site and its underlying software are now <a href="https://github.com/schemaorg/schemaorg/">published via Github</a>.
</p>

<h2>Schema structure</h2>

<p>The schema.org site contains:</p>

<ul>
 <li>A homepage and a few <a href="/docs/documents.html">overview documents</a> such as this.</li>
 <li>Term definitions - one page for each term. Every schema.org term is either a type (e.g. <a href="/Event">Event</a>),
   a property (e.g. <a href="/workPerformed">workPerformed</a>),
   or an enumerated value (e.g. <a href="/ReservationCancelled">ReservationCancelled</a>). Definitions consist of an identifier such as "<code>Event</code>",
   a short textual (HTML) definition, including cross-references and links, as well some factual metadata about the terms. The approach we
   use is based on <a href="https://www.w3.org/TR/rdf-schema/">W3C RDFS</a> with some <a href="#schemalang">customizations</a> summarized below.
 </li>
 <li>Machine-readable files (not intended for humans):
   <ul>
     <li><a href="/docs/schema_org_rdfa.html">schema_org_rdfa.html</a> - the underlying technical definition of the (core) schemas. Hosted extensions are represented in similar files, see data/ext/* in the github repository.</li><commit_msg>Added anchor for pointing to the JSON-LD context section.<commit_after><!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>How we work - schema.org</title>
    <meta name="description" content="Schema.org is a set of extensible schemas that enables webmasters to embed
    structured data on their web pages for use by search engines and other applications." />
    <link rel="stylesheet" type="text/css" href="schemaorg.css" />
    <link href="prettify.css" type="text/css" rel="stylesheet" />
    <script type="text/javascript" src="prettify.js">
    </script>
    <script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js"></script>

<script type="text/javascript">
      $(document).ready(function(){
        prettyPrint();
        setTimeout(function(){

    $('.atn').each(function(i) {
      if (($(this).text() == 'itemscope') || ($(this).text() == 'itemtype') || ($(this).text() == 'itemprop') || ($(this).text() == 'itemid') || ($(this).text() == 'time') || ($(this).text() == 'datetime') || ($(this).text() == 'vocab') || ($(this).text() == 'property') || ($(this).text() == 'typeOf') || ($(this).text() == 'rel'))
        $(this).addClass('custom');
    });

        }, 500);
      });
</script>

<style>

  .tag    { color: #000; }    /* div, span, etc   */
  .atn    { color: #000; }    /* href, datetime,  */
  .custom { color: #660003; } /* itemscope, itemtype, etc,. */

  dt { font-weight: bold; padding: 0.3em 0 0.4em 0;}
</style>

</head>
<body>
    <div id="container">
        <div id="intro">
            <div id="pageHeader">
              <div class="wrapper">
				<div id="sitename">
				<h1>
					<a href="/">schema.org</a>
				</h1>
				</div>

<div id="cse-search-form" style="width: 400px;"></div>

<script type="text/javascript" src="//www.google.com/jsapi"></script>
<script type="text/javascript">
  google.load('search', '1', {language : 'en', style : google.loader.themes.ESPRESSO});
  google.setOnLoadCallback(function() {
    var customSearchControl = new google.search.CustomSearchControl('013516846811604855281:nj5laplixaa');
    customSearchControl.setResultSetSize(google.search.Search.FILTERED_CSE_RESULTSET);
    var options = new google.search.DrawOptions();
    options.enableSearchboxOnly("../docs/search_results.html", null, false, '#');
    customSearchControl.draw('cse-search-form', options);
  }, true);
</script>


              </div>
            </div>
        </div>
    </div>

            <div id="selectionbar">
               <div class="wrapper">
                <ul>
                    <li class="activelink">
                      <a href="../docs/documents.html">Documentation</a></li>
                    <li >
                      <a href="../docs/schemas.html">Schemas</a></li>
                    <li >
                      <a href="../.">Home</a></li>
                </ul>
                </div>

            </div>
        <div style="padding: 14px; float: right;" id="languagebox"></div>

  <div id="mainContent">

<h1>How We Work</h1>

<p>
This document provides a brief overview of schema.org's process for developing and
changing schemas. It accompanies the <a href="about.html">about schema.org</a> page
which describes the organizational structure of the project.
</p>

<p>
<b>Note</b>: the <a href="http://schema.org/">schema.org</a> site contains the officially released
  version of schema.org, while <a href="http://webschemas.org/">webschemas.org</a> is> the very latest
  work-in-progress development branch of schema.org containing more recent fixes and improvements but which may
  contain changes that do not represent the consensus of the wider community or of the project <a href="/about.html#cgsg">steering group</a>. See <a href="#pending">"pending"</a>
  below for more details.
</p>

<p>This document contains a minimal amount of technical detail sufficient to explain
  our approach to schema evolution. Operational details for project collaborators can be found via
  the <a href="https://www.w3.org/community/schemaorg/how-we-work/">how we work</a>
  section of the <a href="https://www.w3.org/community/schemaorg/">Schema.org W3C Community Group</a>.
</p>

<h2>Overview</h2>

<p id="#ataglance">A quick summary.</p>

<ul>
  <li>Most materials on schema.org are updated via <a href="http://schema.org/docs/releases.html">official named releases</a> (every few weeks).</li>
  <li>Simple improvements around supporting documentation, examples, sofware bugs etc. can be fast-tracked by the project <a href="about.html#cgsg">steering group</a> as "Early Access Fixes"; these are
    also recorded in the <a href="http://schema.org/docs/releases.html">releases</a> page, which may also be updated in between formal releases.</li>
  <li>Improvements are discussed in our <a href="http://www.w3.org/community/schemaorg">community group</a> at W3C, typically in the project's <a href="http://github.com/schemaorg/schemaorg/issues">github issue tracker</a>.</li>
  <li>A work-in-progress development version of the site named "<a href="http://webschemas.org/">webschemas.org</a>" is maintained by the <a href="#webmaster">project webmaster</a> based on github and W3C community group discussions, proposals and change requests. It forms the basis for periodic "release candidates" and reflects the current state of the project's public Github repository.</li>
  <li>A "live" hosted extension dedicated to "pending" new vocabulary proposals is maintained as part of this process at <a href="http://pending.webschemas.org/">pending.webschemas.org</a>, and can be updated by the <a href="#webmaster">project webmaster</a> immediately, rather than
    waiting for a full official release. This serves to highlight possible new vocabulary improvements but may not always reflect wider consensus in the community and steering groups.</li>
  <li>Periodically, snapshots of the community's <em>rough consensus</em> are published as release candidates by the project webmaster, for review by the <a href="about.html#cgsg">steering group</a>.</li>
  <li>After steering group <a href="#w3rel">review</a> and approval, the schema.org site is updated with the new release by the project webmaster.</li>
</ul>



<h2>Versioning and change control</h2>
<p>
Schema.org is developed incrementally. Since 2011 we have published several
substantial updates a year. These are known as <em>releases</em> and are
documented on the <a href="/docs/releases.html">releases</a> page. Each release
has a name that is assigned upon publication (e.g. "2.1"). Recent releases have
also been given project-internal code names prior to launch, e.g. "sdo-phobos",
which makes it easier to decide upon the final name (e.g. "2.9" versus "3.0") as the work
develops.
</p>

<p>
The content of each release is based on public discussions hosted on W3C's
community group platform and on the Github site. All <a href="/docs/releases.html">changes</a> to the
project have been through unanimous agreement of the Steering Group membership, strongly
informed by the opinions, contributions and discussions in the wider community.
</p>

<p>
Recently we have been expanding on this model with two types of <a href="extension.html">extension</a> vocabulary: hosted and external extensions.
Hosted extensions are effectively part of schema.org but "tagged" within a subdomain (e.g. <a href="http://bib.schema.org/">bib.schema.org</a>,
<a href="http://auto.schema.org/">auto.schema.org</a>). External extensions (e.g.
see <a href="http://blog.schema.org/2016/02/gs1-milestone-first-schemaorg-external.html">GS1's Web Vocabulary</a>) are published elsewhere on the Web, and are typically managed by other
organizations with their own processes, versioning systems and collaboration mechanisms. Hosted extensions are managed and published as part
of the schema.org project, with their design often led by one or more dedicated community groups.
</p>

<p>
For general use, publishers and consumers are encouraged to use the latest release and to use simple non-versioned schema.org URLs such as 'http://schema.org/Place'
in structured data applications. However there are settings in which more precise versioning is important. Schema.org also provides dated snapshots of each release, including
both human and machine readable definitions of the schema.org core vocabulary. These are linked from the <a href="releases.html">releases page</a>. In addition,
the <a href="/schemaVersion">schemaVersion</a> property has been defined to provide a way for documents to indicate the specific intended version of schema.org's
definitions. Finally, all changes to the site and its underlying software are now <a href="https://github.com/schemaorg/schemaorg/">published via Github</a>.
</p>

<h2>Schema structure</h2>

<p>The schema.org site contains:</p>

<ul>
 <li>A homepage and a few <a href="/docs/documents.html">overview documents</a> such as this.</li>
 <li>Term definitions - one page for each term. Every schema.org term is either a type (e.g. <a href="/Event">Event</a>),
   a property (e.g. <a href="/workPerformed">workPerformed</a>),
   or an enumerated value (e.g. <a href="/ReservationCancelled">ReservationCancelled</a>). Definitions consist of an identifier such as "<code>Event</code>",
   a short textual (HTML) definition, including cross-references and links, as well some factual metadata about the terms. The approach we
   use is based on <a href="https://www.w3.org/TR/rdf-schema/">W3C RDFS</a> with some <a href="#schemalang">customizations</a> summarized below.
 </li>
 <li>Machine-readable files (not intended for humans):
   <ul id="jsonldcontext">
     <li><a href="/docs/schema_org_rdfa.html">schema_org_rdfa.html</a> - the underlying technical definition of the (core) schemas. Hosted extensions are represented in similar files, see data/ext/* in the github repository.</li>
{'fraction_non_alphanumeric': 0.14123726857658922, 'fraction_numerical': 0.009633234659575536, 'mean_word_length': 3.8924889543446244, 'pattern_counts': {'":': 0, '<': 377, '<?xml version=': 0, '>': 379, 'https://': 8, 'lorem ipsum': 0, 'www.': 12, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7015218', 'n_tokens_mistral': 6067, 'n_tokens_neox': 5682, 'n_words': 2018}