Revision 769a5fb2f73384f9ca8beec6798a41c0f31aede7 authored by Alex Jansen on 06 December 2021, 12:41:01 UTC, committed by Alex Jansen on 06 December 2021, 12:41:01 UTC
1 parent 7070f88
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>
<!-- #### Static Doc Insert Head goes here -->
</head>
<body>
<!-- #### Static Doc Insert PageHead goes here -->
<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="/docs/extension.html">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>
<!-- #### Static Doc Insert Footer here -->
</body>
</html>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...