- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 03 Dec 2009 15:10:19 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv6234
Added Files:
iana.html
Log Message:
new
--- NEW FILE: iana.html ---
<!DOCTYPE HTML>
<!-- when publishing, change bits marked ZZZ --><html lang="en-US-x-Hixie"><head><title>13 IANA considerations — HTML 5</title><style type="text/css">
pre { margin-left: 2em; white-space: pre-wrap; }
h2 { margin: 3em 0 1em 0; }
h3 { margin: 2.5em 0 1em 0; }
h4 { margin: 2.5em 0 0.75em 0; }
h5, h6 { margin: 2.5em 0 1em; }
h1 + h2, h1 + h2 + h2 { margin: 0.75em 0 0.75em; }
h2 + h3, h3 + h4, h4 + h5, h5 + h6 { margin-top: 0.5em; }
p { margin: 1em 0; }
hr:not(.top) { display: block; background: none; border: none; padding: 0; margin: 2em 0; height: auto; }
dl, dd { margin-top: 0; margin-bottom: 0; }
dt { margin-top: 0.75em; margin-bottom: 0.25em; clear: left; }
dt + dt { margin-top: 0; }
dd dt { margin-top: 0.25em; margin-bottom: 0; }
dd p { margin-top: 0; }
dd dl + p { margin-top: 1em; }
dd table + p { margin-top: 1em; }
p + * > li, dd li { margin: 1em 0; }
dt, dfn { font-weight: bold; font-style: normal; }
dt dfn { font-style: italic; }
pre, code { font-size: inherit; font-family: monospace; font-variant: normal; }
pre strong { color: black; font: inherit; font-weight: bold; background: yellow; }
pre em { font-weight: bolder; font-style: normal; }
@media screen { code { color: orangered; } code :link, code :visited { color: inherit; } }
var sub { vertical-align: bottom; font-size: smaller; position: relative; top: 0.1em; }
table { border-collapse: collapse; border-style: hidden hidden none hidden; }
table thead { border-bottom: solid; }
table tbody th:first-child { border-left: solid; }
table tbody th { text-align: left; }
table td, table th { border-left: solid; border-right: solid; border-bottom: solid thin; vertical-align: top; padding: 0.2em; }
blockquote { margin: 0 0 0 2em; border: 0; padding: 0; font-style: italic; }
.bad, .bad *:not(.XXX) { color: gray; border-color: gray; background: transparent; }
.matrix, .matrix td { border: none; text-align: right; }
.matrix { margin-left: 2em; }
.dice-example { border-collapse: collapse; border-style: hidden solid solid hidden; border-width: thin; margin-left: 3em; }
.dice-example caption { width: 30em; font-size: smaller; font-style: italic; padding: 0.75em 0; text-align: left; }
.dice-example td, .dice-example th { border: solid thin; width: 1.35em; height: 1.05em; text-align: center; padding: 0; }
.toc dfn, h1 dfn, h2 dfn, h3 dfn, h4 dfn, h5 dfn, h6 dfn { font: inherit; }
img.extra { float: right; }
pre.idl { border: solid thin; background: #EEEEEE; color: black; padding: 0.5em 1em; }
pre.idl :link, pre.idl :visited { color: inherit; background: transparent; }
pre.css { border: solid thin; background: #FFFFEE; color: black; padding: 0.5em 1em; }
pre.css:first-line { color: #AAAA50; }
dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #EEFFEE; }
hr + dl.domintro, div.impl + dl.domintro { margin-top: 2.5em; margin-bottom: 1.5em; }
dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
dl.domintro dd p { margin: 0.5em 0; }
dl.switch { padding-left: 2em; }
dl.switch > dt { text-indent: -1.5em; }
dl.switch > dt:before { content: '\21AA'; padding: 0 0.5em 0 0; display: inline-block; width: 1em; text-align: right; line-height: 0.5em; }
dl.triple { padding: 0 0 0 1em; }
dl.triple dt, dl.triple dd { margin: 0; display: inline }
dl.triple dt:after { content: ':'; }
dl.triple dd:after { content: '\A'; white-space: pre; }
.diff-old { text-decoration: line-through; color: silver; background: transparent; }
.diff-chg, .diff-new { text-decoration: underline; color: green; background: transparent; }
a .diff-new { border-bottom: 1px blue solid; }
h2 { page-break-before: always; }
h1, h2, h3, h4, h5, h6 { page-break-after: avoid; }
h1 + h2, hr + h2.no-toc { page-break-before: auto; }
p > span:not([title=""]):not([class="XXX"]):not([class="impl"]), li > span:not([title=""]):not([class="XXX"]):not([class="impl"]) { border-bottom: solid #9999CC; }
div.head { margin: 0 0 1em; padding: 1em 0 0 0; }
div.head p { margin: 0; }
div.head h1 { margin: 0; }
div.head .logo { float: right; margin: 0 1em; }
div.head .logo img { border: none } /* remove border from top image */
div.head dl { margin: 1em 0; }
p.copyright { font-size: x-small; font-style: oblique; margin: 0; }
body > .toc > li { margin-top: 1em; margin-bottom: 1em; }
body > .toc.brief > li { margin-top: 0.35em; margin-bottom: 0.35em; }
body > .toc > li > * { margin-bottom: 0.5em; }
body > .toc > li > * > li > * { margin-bottom: 0.25em; }
.toc, .toc li { list-style: none; }
.brief { margin-top: 1em; margin-bottom: 1em; line-height: 1.1; }
.brief li { margin: 0; padding: 0; }
.brief li p { margin: 0; padding: 0; }
.category-list { margin-top: -0.75em; margin-bottom: 1em; line-height: 1.5; }
.category-list::before { content: '\21D2\A0'; font-size: 1.2em; font-weight: 900; }
.category-list li { display: inline; }
.category-list li:not(:last-child)::after { content: ', '; }
.category-list li > span, .category-list li > a { text-transform: lowercase; }
.category-list li * { text-transform: none; } /* don't affect <code> nested in <a> */
.XXX { color: #E50000; background: white; border: solid red; padding: 0.5em; margin: 1em 0; }
.XXX > :first-child { margin-top: 0; }
p .XXX { line-height: 3em; }
.annotation { border: solid thin black; background: #0C479D; color: white; position: relative; margin: 8px 0 20px 0; }
.annotation:before { position: absolute; left: 0; top: 0; width: 100%; height: 100%; margin: 6px -6px -6px 6px; background: #333333; z-index: -1; content: ''; }
.annotation :link, .annotation :visited { color: inherit; }
.annotation :link:hover, .annotation :visited:hover { background: transparent; }
.annotation span { border: none ! important; }
.note { color: green; background: transparent; font-family: sans-serif; }
.warning { color: red; background: transparent; }
.note, .warning { font-weight: bolder; font-style: italic; }
p.note, div.note { padding: 0.5em 2em; }
span.note { padding: 0 2em; }
.note p:first-child, .warning p:first-child { margin-top: 0; }
.note p:last-child, .warning p:last-child { margin-bottom: 0; }
.warning:before { font-style: normal; }
p.note:before { content: 'Note: '; }
p.warning:before { content: '\26A0 Warning! '; }
.bookkeeping:before { display: block; content: 'Bookkeeping details'; font-weight: bolder; font-style: italic; }
.bookkeeping { font-size: 0.8em; margin: 2em 0; }
.bookkeeping p { margin: 0.5em 2em; display: list-item; list-style: square; }
h4 { position: relative; z-index: 3; }
h4 + .element, h4 + div + .element { margin-top: -2.5em; padding-top: 2em; }
.element {
background: #EEEEFF;
color: black;
margin: 0 0 1em 0.15em;
padding: 0 1em 0.25em 0.75em;
border-left: solid #9999FF 0.25em;
position: relative;
z-index: 1;
}
.element:before {
position: absolute;
z-index: 2;
top: 0;
left: -1.15em;
height: 2em;
width: 0.9em;
background: #EEEEFF;
content: ' ';
border-style: none none solid solid;
border-color: #9999FF;
border-width: 0.25em;
}
.example { display: block; color: #222222; background: #FCFCFC; border-left: double; margin-left: 2em; padding-left: 1em; }
td > .example:only-child { margin: 0 0 0 0.1em; }
.tall-and-narrow {
font-size: 0.6em;
column-width: 25em;
column-gap: 1em;
-moz-column-width: 25em;
-moz-column-gap: 1em;
-webkit-column-width: 25em;
-webkit-column-gap: 1em;
}
ul.domTree, ul.domTree ul { padding: 0 0 0 1em; margin: 0; }
ul.domTree li { padding: 0; margin: 0; list-style: none; position: relative; }
ul.domTree li li { list-style: none; }
ul.domTree li:first-child::before { position: absolute; top: 0; height: 0.6em; left: -0.75em; width: 0.5em; border-style: none none solid solid; content: ''; border-width: 0.1em; }
ul.domTree li:not(:last-child)::after { position: absolute; top: 0; bottom: -0.6em; left: -0.75em; width: 0.5em; border-style: none none solid solid; content: ''; border-width: 0.1em; }
ul.domTree span { font-style: italic; font-family: serif; }
ul.domTree .t1 code { color: purple; font-weight: bold; }
ul.domTree .t2 { font-style: normal; font-family: monospace; }
ul.domTree .t2 .name { color: black; font-weight: bold; }
ul.domTree .t2 .value { color: blue; font-weight: normal; }
ul.domTree .t3 code, .domTree .t4 code, .domTree .t5 code { color: gray; }
ul.domTree .t7 code, .domTree .t8 code { color: green; }
ul.domTree .t10 code { color: teal; }
</style><style type="text/css">
.applies thead th > * { display: block; }
.applies thead code { display: block; }
.applies tbody th { whitespace: nowrap; }
.applies td { text-align: center; }
.applies .yes { background: yellow; }
.matrix, .matrix td { border: none; text-align: right; }
.matrix { margin-left: 2em; }
.dice-example { border-collapse: collapse; border-style: hidden solid solid hidden; border-width: thin; margin-left: 3em; }
.dice-example caption { width: 30em; font-size: smaller; font-style: italic; padding: 0.75em 0; text-align: left; }
.dice-example td, .dice-example th { border: solid thin; width: 1.35em; height: 1.05em; text-align: center; padding: 0; }
#table-example-1 { border: solid thin; border-collapse: collapse; margin-left: 3em; }
#table-example-1 * { font-family: "Essays1743", serif; line-height: 1.01em; }
#table-example-1 caption { padding-bottom: 0.5em; }
#table-example-1 thead, #table-example-1 tbody { border: none; }
#table-example-1 th, #table-example-1 td { border: solid thin; }
#table-example-1 th { font-weight: normal; }
#table-example-1 td { border-style: none solid; vertical-align: top; }
#table-example-1 th { padding: 0.5em; vertical-align: middle; text-align: center; }
#table-example-1 tbody tr:first-child td { padding-top: 0.5em; }
#table-example-1 tbody tr:last-child td { padding-bottom: 1.5em; }
#table-example-1 tbody td:first-child { padding-left: 2.5em; padding-right: 0; width: 9em; }
#table-example-1 tbody td:first-child::after { content: leader(". "); }
#table-example-1 tbody td { padding-left: 2em; padding-right: 2em; }
#table-example-1 tbody td:first-child + td { width: 10em; }
#table-example-1 tbody td:first-child + td ~ td { width: 2.5em; }
#table-example-1 tbody td:first-child + td + td + td ~ td { width: 1.25em; }
.apple-table-examples { border: none; border-collapse: separate; border-spacing: 1.5em 0em; width: 40em; margin-left: 3em; }
.apple-table-examples * { font-family: "Times", serif; }
.apple-table-examples td, .apple-table-examples th { border: none; white-space: nowrap; padding-top: 0; padding-bottom: 0; }
.apple-table-examples tbody th:first-child { border-left: none; width: 100%; }
.apple-table-examples thead th:first-child ~ th { font-size: smaller; font-weight: bolder; border-bottom: solid 2px; text-align: center; }
.apple-table-examples tbody th::after, .apple-table-examples tfoot th::after { content: leader(". ") }
.apple-table-examples tbody th, .apple-table-examples tfoot th { font: inherit; text-align: left; }
.apple-table-examples td { text-align: right; vertical-align: top; }
.apple-table-examples.e1 tbody tr:last-child td { border-bottom: solid 1px; }
.apple-table-examples.e1 tbody + tbody tr:last-child td { border-bottom: double 3px; }
.apple-table-examples.e2 th[scope=row] { padding-left: 1em; }
.apple-table-examples sup { line-height: 0; }
</style><link href="data:text/css," rel="stylesheet" title="Complete specification"><link href="data:text/css,.impl%20%7B%20display:%20none;%20%7D" rel="alternate stylesheet" title="Author documentation only"><link href="data:text/css,.impl%20%7B%20background:%20%23FFEEEE;%20%7D" rel="alternate stylesheet" title="Highlight implementation requirements"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css">
<script src="link-fixup.js"></script>
<link href="obsolete.html" title="12 Obsolete features" rel="prev">
<link href="spec.html#contents" title="Table of contents" rel="index">
<link href="index.html" title="Index" rel="next">
</head><body onload="fixBrokenLink(); fixBrokenLink()"><div class="head">
<p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72"></a></p>
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
</div><nav>
<a href="obsolete.html">← 12 Obsolete features</a> –
<a href="spec.html#contents">Table of contents</a> –
<a href="index.html">Index →</a>
</nav><p>This is revision 1.3518.</p>
<h2 id="iana"><span class="secno">13 </span>IANA considerations</h2><!-- http://www.w3.org/2002/06/registering-mediatype.html --><h3 id="text-html"><span class="secno">13.1 </span><dfn><code>text/html</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type text/html
--><!--
Obsoletes:
http://www.ietf.org/rfc/rfc2854
Include a request to retire RFC 2854 persuant to section 6.4 of RFC 2026.
--><dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
<dd>html</dd>
<dt>Required parameters:</dt>
<dd>No required parameters</dd>
<dt>Optional parameters:</dt>
<dd>
<dl><dt><code title="">charset</code></dt>
<dd>
<p>The <code title="">charset</code> parameter may be provided
to definitively specify the <a href="dom.html#document-s-character-encoding">document's character
encoding</a>, overriding any <a href="semantics.html#character-encoding-declaration" title="character encoding
declaration">character encoding declarations</a> in the
document. The parameter's value must be the name of the
character encoding used to serialize the file, must be a valid
character encoding name, and must be an <a href="infrastructure.html#ascii-case-insensitive">ASCII
case-insensitive</a> match for the <a href="infrastructure.html#preferred-mime-name">preferred MIME
name</a> for that encoding. <a href="references.html#refsIANACHARSET">[IANACHARSET]</a></p>
</dd>
</dl></dd>
<dt>Encoding considerations:</dt>
<dd>See the section on <a href="semantics.html#character-encoding-declaration" title="character encoding
declaration">character encoding declarations</a>.</dd>
<dt>Security considerations:</dt>
<dd>
<p>Entire novels have been written about the security
considerations that apply to HTML documents. Many are listed in
this document, to which the reader is referred for more
details. Some general concerns bear mentioning here, however:</p>
<p>HTML is scripted language, and has a large number of APIs (some
of which are described in this document). Script can expose the
user to potential risks of information leakage, credential
leakage, cross-site scripting attacks, cross-site request
forgeries, and a host of other problems. While the designs in this
specification are intended to be safe if implemented correctly, a
full implementation is a massive undertaking and, as with any
software, user agents are likely to have security bugs.</p>
<p>Even without scripting, there are specific features in HTML
which, for historical reasons, are required for broad
compatibility with legacy content but that expose the user to
unfortunate security problems. In particular, the <code><a href="text-level-semantics.html#the-img-element">img</a></code>
element can be used in conjunction with some other features as a
way to effect a port scan from the user's location on the
Internet. This can expose local network topologies that the
attacker would otherwise not be able to determine.</p>
</dd>
<dt>Interoperability considerations:</dt>
<dd>
Rules for processing both conforming and non-conforming content
are defined in this specification.
</dd>
<dt>Published specification:</dt>
<dd>
This document is the relevant specification. Labeling a resource
with the <code><a href="#text-html">text/html</a></code> type asserts that the resource is
an <a href="dom.html#html-documents" title="HTML documents">HTML document</a> using
<a href="syntax.html#syntax">the HTML syntax</a>.
</dd>
<dt>Applications that use this media type:</dt>
<dd>
Web browsers, tools for processing Web content, HTML authoring
tools, search engines, validators.
</dd>
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
<dd>No sequence of bytes can uniquely identify an HTML
document. More information on detecting HTML documents is
available in the Content-Type Processing Model specification. <a href="references.html#refsMIMESNIFF">[MIMESNIFF]</a></dd>
<dt>File extension(s):</dt>
<dd>"<code title="">html</code>" and "<code title="">htm</code>"
are commonly, but certainly not exclusively, used as the
extension for HTML documents.</dd>
<dt>Macintosh file type code(s):</dt>
<dd><code title="">TEXT</code></dd>
</dl></dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Intended usage:</dt>
<dd>Common</dd>
<dt>Restrictions on usage:</dt>
<dd>No restrictions apply.</dd>
<dt>Author:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers used with <code><a href="#text-html">text/html</a></code> resources
refer to <a href="history.html#the-indicated-part-of-the-document">the indicated part of the document</a>.</p><h3 id="application-xhtml-xml"><span class="secno">13.2 </span><dfn><code>application/xhtml+xml</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type application/xhtml+xml
--><!--
Obsoletes:
http://www.ietf.org/rfc/rfc3236.txt
--><dl><dt>Type name:</dt>
<dd>application</dd>
<dt>Subtype name:</dt>
<dd>xhtml+xml</dd>
<dt>Required parameters:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Optional parameters:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Encoding considerations:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Security considerations:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Interoperability considerations:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Published specification:</dt>
<dd>
Labeling a resource with the <code><a href="#application-xhtml-xml">application/xhtml+xml</a></code>
type asserts that the resource is an XML document that likely has
a root element from the <a href="syntax.html#html-namespace-0">HTML namespace</a>. As such, the
relevant specifications are the XML specification, the Namespaces
in XML specification, and this specification. <a href="references.html#refsXML">[XML]</a> <a href="references.html#refsXMLNS">[XMLNS]</a>
</dd>
<dt>Applications that use this media type:</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
<dd>Same as for <code>application/xml</code> <a href="references.html#refsRFC3023">[RFC3023]</a></dd>
<dt>File extension(s):</dt>
<dd>"<code title="">xhtml</code>" and "<code title="">xht</code>"
are sometimes used as extensions for XML resources that have a
root element from the <a href="syntax.html#html-namespace-0">HTML namespace</a>.</dd>
<dt>Macintosh file type code(s):</dt>
<dd><code title="">TEXT</code></dd>
</dl></dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Intended usage:</dt>
<dd>Common</dd>
<dt>Restrictions on usage:</dt>
<dd>No restrictions apply.</dd>
<dt>Author:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers used with <code><a href="#application-xhtml-xml">application/xhtml+xml</a></code>
resources have the same semantics as with any <a href="infrastructure.html#xml-mime-type">XML MIME
type</a>. <a href="references.html#refsRFC3023">[RFC3023]</a></p><h3 id="text-cache-manifest"><span class="secno">13.3 </span><dfn><code>text/cache-manifest</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type text/cache-manifest
--><dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
<dd>cache-manifest</dd>
<dt>Required parameters:</dt>
<dd>No parameters</dd>
<dt>Optional parameters:</dt>
<dd>No parameters</dd>
<dt>Encoding considerations:</dt>
<dd>Always UTF-8.</dd>
<dt>Security considerations:</dt>
<dd>
<p>Cache manifests themselves pose no immediate risk unless
sensitive information is included within the
manifest. Implementations, however, are required to follow
specific rules when populating a cache based on a cache manifest,
to ensure that certain origin-based restrictions are
honored. Failure to correctly implement these rules can result in
information leakage, cross-site scripting attacks, and the
like.</p>
</dd>
<dt>Interoperability considerations:</dt>
<dd>
Rules for processing both conforming and non-conforming content
are defined in this specification.
</dd>
<dt>Published specification:</dt>
<dd>
This document is the relevant specification.
</dd>
<dt>Applications that use this media type:</dt>
<dd>
Web browsers.
</dd>
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
<dd>Cache manifests begin with the string "<code title="">CACHE
MANIFEST</code>", followed by either a U+0020 SPACE character, a
U+0009 CHARACTER TABULATION (tab) character, a U+000A LINE FEED
(LF) character, or a U+000D CARRIAGE RETURN (CR) character.</dd>
<dt>File extension(s):</dt>
<dd>"<code title="">manifest</code>"</dd>
<dt>Macintosh file type code(s):</dt>
<dd>No specific Macintosh file type codes are recommended for this type.</dd>
</dl></dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Intended usage:</dt>
<dd>Common</dd>
<dt>Restrictions on usage:</dt>
<dd>No restrictions apply.</dd>
<dt>Author:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers have no meaning with
<code><a href="#text-cache-manifest">text/cache-manifest</a></code> resources.</p><h3 id="text-ping"><span class="secno">13.4 </span><dfn><code>text/ping</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type text/ping
--><dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
<dd>ping</dd>
<dt>Required parameters:</dt>
<dd>No parameters</dd>
<dt>Optional parameters:</dt>
<dd>No parameters</dd>
<dt>Encoding considerations:</dt>
<dd>Not applicable.</dd>
<dt>Security considerations:</dt>
<dd>
<p>If used exclusively in the fashion described in the context of
<a href="history.html#hyperlink-auditing">hyperlink auditing</a>, this type introduces no new
security concerns.</p>
</dd>
<dt>Interoperability considerations:</dt>
<dd>
Rules applicable to this type are defined in this specification.
</dd>
<dt>Published specification:</dt>
<dd>
This document is the relevant specification.
</dd>
<dt>Applications that use this media type:</dt>
<dd>
Web browsers.
</dd>
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
<dd><code><a href="#text-ping">text/ping</a></code> resources always consist of the four
bytes 0x50 0x49 0x4E 0x47 (ASCII 'PING').</dd>
<dt>File extension(s):</dt>
<dd>No specific file extension is recommended for this type.</dd>
<dt>Macintosh file type code(s):</dt>
<dd>No specific Macintosh file type codes are recommended for this type.</dd>
</dl></dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Intended usage:</dt>
<dd>Common</dd>
<dt>Restrictions on usage:</dt>
<dd>Only intended for use with HTTP POST requests generated as part
of a Web browser's processing of the <code title="attr-hyperlink-ping"><a href="history.html#ping">ping</a></code> attribute.</dd>
<dt>Author:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers have no meaning with
<code><a href="#text-ping">text/ping</a></code> resources.</p><h3 id="application-microdata-json"><span class="secno">13.5 </span><dfn><code>application/microdata+json</code></dfn></h3><p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p><!--
To: ietf-types@iana.org
Subject: Registration of media type application/microdata+json
--><dl><dt>Type name:</dt>
<dd>application</dd>
<dt>Subtype name:</dt>
<dd>microdata+json</dd>
<dt>Required parameters:</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Optional parameters:</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Encoding considerations:</dt>
<dd>Always UTF-8.</dd>
<dt>Security considerations:</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Interoperability considerations:</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Published specification:</dt>
<dd>
Labeling a resource with the
<code><a href="#application-microdata-json">application/microdata+json</a></code> type asserts that the
resource is a JSON text that consists of an object with a single
entry called "<code title="">items</code>" consisting of an array
of entries, each of which consists of an object with two entries,
one called "<code title="">type</code>" whose value is an array of
strings, and one called "<code title="">properties</code>" whose
value is an object whose entries each have a value consisting of
an array of either objects or strings, the objects being of the
same form as the objects in the aforementioned "<code title="">items</code>" entry. As such, the relevant specifications
are the JSON specification and this specification. <a href="references.html#refsJSON">[JSON]</a>
</dd>
<dt>Applications that use this media type:</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Additional information:</dt>
<dd>
<dl><dt>Magic number(s):</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>File extension(s):</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
<dt>Macintosh file type code(s):</dt>
<dd>Same as for <code>application/json</code> <a href="references.html#refsJSON">[JSON]</a></dd>
</dl></dd>
<dt>Person & email address to contact for further information:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Intended usage:</dt>
<dd>Common</dd>
<dt>Restrictions on usage:</dt>
<dd>No restrictions apply.</dd>
<dt>Author:</dt>
<dd>Ian Hickson <ian@hixie.ch></dd>
<dt>Change controller:</dt>
<dd>W3C and WHATWG</dd>
</dl><p>Fragment identifiers used with
<code><a href="#application-microdata-json">application/microdata+json</a></code> resources have the same
semantics as when used with <code>application/json</code>. <a href="references.html#refsJSON">[JSON]</a></p><h3 id="ping-from"><span class="secno">13.6 </span><dfn title="http-ping-from"><code>Ping-From</code></dfn></h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href="references.html#refsRFC3864">[RFC3864]</a></p><dl><dt>Header field name</dt>
<dd>Ping-From</dd>
<dt>Applicable protocol</dt>
<dd>http</dd>
<dt>Status</dt>
<dd>standard</dd>
<dt>Author/Change controller</dt>
<dd>W3C and WHATWG</dd>
<dt>Specification document(s)</dt>
<dd>
This document is the relevant specification.
</dd>
<dt>Related information</dt>
<dd>None.</dd>
</dl><h3 id="ping-to"><span class="secno">13.7 </span><dfn title="http-ping-to"><code>Ping-To</code></dfn></h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>This section describes a header field for registration in the
Permanent Message Header Field Registry. <a href="references.html#refsRFC3864">[RFC3864]</a></p><dl><dt>Header field name</dt>
<dd>Ping-To</dd>
<dt>Applicable protocol</dt>
<dd>http</dd>
<dt>Status</dt>
<dd>standard</dd>
<dt>Author/Change controller</dt>
<dd>W3C and WHATWG</dd>
<dt>Specification document(s)</dt>
<dd>
This document is the relevant specification.
</dd>
<dt>Related information</dt>
<dd>None.</dd>
</dl></body></html>
Received on Thursday, 3 December 2009 15:10:29 UTC