Revision 919c65107f6824ef444ce5085c9106f84b26e890 authored by Dan Brickley on 23 March 2020, 20:31:19 UTC, committed by Dan Brickley on 23 March 2020, 20:31:19 UTC
This will settle into an HTML page here ASAP, but linking now for discoverability during drafting process.
1 parent 12362e3
extension.html
<!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>Extending Schemas - schema.org</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<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" />
<!-- ##### Generated insert [CSEScript-start] see scripts/genhtmlinserts.sh ##### -->
<!-- Enable CSE Search -->
<script>
(function() {
var cx = '013516846811604855281:nj5laplixaa'; // Insert your own Custom Search engine ID here
var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true;
gcse.src = 'https://cse.google.com/cse.js?cx=' + cx;
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s);
})();
</script>
<!-- ##### Generated insert [CSEScript-end] see scripts/genhtmlinserts.sh ##### -->
</head>
<body>
<!-- ##### Generated insert [DOCSHDR-start] see scripts/genhtmlinserts.sh ##### -->
<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 class="gcse-searchbox-only" data-resultsurl="search_results.html"></div>
</div>
</div>
</div>
</div>
</div>
<div id="selectionbar">
<div class="wrapper">
<ul>
<li>
<a href="documents.html" >Documentation</a>
</li>
<li>
<a href="schemas.html" >Schemas</a>
</li>
<li>
<a href="../">Home</a>
</li>
</ul>
</div>
</div>
<!-- ##### Generated insert [DOCSHDR-end] see scripts/genhtmlinserts.sh ##### -->
<div id="mainContent" class="faq">
<h1>Schema.org Extensions</h1>
<p>
Over the years, we have experimented with a couple of different extension mechanisms (see
<a href="/docs/old_extension.html">2011-2014</a> and
<a href="/docs/old_extension_2015.html">2014-2018</a> docs for details).
</p>
<p>
The primary motivation behind these models was to enable decentralized extension of the vocabulary.
However, we have come to realize that for adoption, we need a simpler model, where publishers
can be sure that a piece of vocabulary is indeed part of Schema.org. Until April 2019,
we relied primarily on the '<a href="/docs/old_extension_2015.html">hosted extensions</a>' mechanism
that used hosted subdomains of schema.org (such as bib.schema.org for the bibliography extension and
autos.schema.org for the autos extension). Going forward, the content of these hosted extensions are being
folded into schema.org, although each will retain an "entry point" page as before.
</p>
<p>
Terms from these hosted extensions are now considered fully part of schema.org, although they
remain tagged with a label corresponding to the extension it originated from. Over a period
of time, as usage of these terms gets intermingled with other terms, these labels may be dropped
or simplified.
</p>
<p>
One label --- '<a href="https://pending.schema.org/">pending</a>' --- is kept reserved for enabling us to more rapidly introduce
terms into schema.org, on an experimental basis. After a period of time of being in a
pending status, depending on usage, adoption, discussions etc. a term will be incorporated into
the core or get dropped.
</p>
<p>
External extensions, where a third party might want to host a broadly applicable extension
themselves (e.g., <a href="http://gs1.org/voc">http://gs1.org/voc</a>) will continue as before.
</p>
<p>
We continue to welcome improvements and additions to Schema.org, and to encourage public discussion
towards this in various groups both at W3C and elsewhere. Additions to schema.org will now come in
primarily via Pending. As always we place high emphasis on vocabulary that is likely to be consumed,
rather than merely published.
</p>
</div>
<div id="footer"><p>
<a href="../docs/terms.html">Terms and conditions</a></p>
</div>
</body>
</html>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...