HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/3552

File a bug

SVNBugCommentTime (UTC)
3552Include MIME type registration sections.2009-08-07 09:44
Index: source
===================================================================
--- source	(revision 3551)
+++ source	(revision 3552)
@@ -251,18 +251,18 @@
 
   <p>The first such concrete syntax is "HTML5". This is the format
   recommended for most authors. It is compatible with all legacy Web
-  browsers. If a document is transmitted with the MIME type <code
-  title="">text/html</code>, then it will be processed as an "HTML5"
+  browsers. If a document is transmitted with the MIME type
+  <code>text/html</code>, then it will be processed as an "HTML5"
   document by Web browsers.</p>
 
   <p>The second concrete syntax uses XML, and is known as
   "XHTML5". When a document is transmitted with an <span>XML MIME
-  type</span>, such as <code title="">application/xhtml+xml</code>,
-  then it is processed by an XML processor by Web browsers, and
-  treated as an "XHTML5" document. Authors are reminded that the
-  processing for XML and HTML differs; in particular, even minor
-  syntax errors will prevent an XML document from being rendered
-  fully, whereas they would be ignored in the "HTML5" syntax.</p>
+  type</span>, such as <code>application/xhtml+xml</code>, then it is
+  processed by an XML processor by Web browsers, and treated as an
+  "XHTML5" document. Authors are reminded that the processing for XML
+  and HTML differs; in particular, even minor syntax errors will
+  prevent an XML document from being rendered fully, whereas they
+  would be ignored in the "HTML5" syntax.</p>
 
   <p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
   represent the same content. For example, namespaces cannot be
@@ -9363,7 +9363,7 @@
     previous object, which is then returned.</p>
 
     <p>If the <var title="">type</var> argument is omitted or has the
-    value "<code title="">text/html</code>", then the resulting
+    value "<code>text/html</code>", then the resulting
     <code>Document</code> has an HTML parser associated with it, which
     can be given data to parse using <code
     title="dom-document-write">document.write()</code>. Otherwise, all
@@ -51341,11 +51341,11 @@
     title="">alternate</code>" to <var title="">x</var>. If the
     document being converted is an <span title="HTML documents">HTML
     document</span>, add a <code title="">type</code> attribute whose
-    value is the string "<code title="">text/html</code>" to <var
+    value is the string "<code>text/html</code>" to <var
     title="">x</var>. Otherwise, the document being converted is an
     <span title="XML documents">XML document</span>; add a <code
-    title="">type</code> attribute whose value is the string "<code
-    title="">application/xhtml+xml</code>" to <var
+    title="">type</code> attribute whose value is the string
+    "<code>application/xhtml+xml</code>" to <var
     title="">x</var>. Append a text node with its data set to
     <span>the document's current address</span> to <var
     title="">x</var>. Append <var title="">x</var> to the root element
@@ -54335,9 +54335,9 @@
 
     <p>Otherwise, the URL must be treated in a manner equivalent to an
     HTTP resource with a 200 OK response whose <span
-    title="Content-Type">Content-Type metadata</span> is <code
-    title="">text/html</code> and whose response body is the return
-    value converted to a string value.</p>
+    title="Content-Type">Content-Type metadata</span> is
+    <code>text/html</code> and whose response body is the return value
+    converted to a string value.</p>
 
     <p class="note">Certain contexts, in particular <code>img</code>
     elements, ignore the <span title="Content-Type">Content-Type
@@ -56309,8 +56309,7 @@
   <pre>EXAMPLE offline/clock/clock2.manifest</pre>
 
   <p>With a small change to the HTML file, the manifest (served as
-  <code title="">text/cache-manifest</code>) is linked to the
-  application:</p>
+  <code>text/cache-manifest</code>) is linked to the application:</p>
 
   <pre>EXAMPLE offline/clock/clock2.html</pre>
 
@@ -56597,11 +56596,11 @@
 
   <h5>Writing cache manifests</h5>
 
-  <p>Manifests must be served using the <code
-  title="">text/cache-manifest</code> MIME type. All resources served
-  using the <code title="">text/cache-manifest</code> MIME type must
-  follow the syntax of application cache manifests, as described in
-  this section.</p>
+  <p>Manifests must be served using the
+  <code>text/cache-manifest</code> MIME type. All resources served
+  using the <code>text/cache-manifest</code> MIME type must follow the
+  syntax of application cache manifests, as described in this
+  section.</p>
 
   <p>An application cache manifest is a text file, whose text is
   encoded using UTF-8. Data in application cache manifests is
@@ -57183,8 +57182,8 @@
     from <var title="">manifest URL</var>, and let <var
     title="">manifest</var> be that resource.</p>
 
-    <p>If the resource is labeled with the MIME type <code
-    title="">text/cache-manifest</code>, parse <var
+    <p>If the resource is labeled with the MIME type
+    <code>text/cache-manifest</code>, parse <var
     title="">manifest</var> according to the <span title="parse a
     manifest">rules for parsing manifests</span>, obtaining a list of
     <span title="concept-appcache-explicit">explicit entries</span>,
@@ -57264,8 +57263,8 @@
     cancels the download, or the parser for manifests fails when
     checking the magic signature), or if the server returned a
     redirect, or if the resource is labeled with a MIME type other
-    than <code title="">text/cache-manifest</code>, then run the
-    <span>cache failure steps</span>.</p>
+    than <code>text/cache-manifest</code>, then run the <span>cache
+    failure steps</span>.</p>
 
    </li>
 
@@ -59317,22 +59316,22 @@
 
     <dl class="switch">
 
-     <dt>"text/html"</dt>
+     <dt>"<code>text/html</code>"</dt>
      <dd>Follow the steps given in the <span
      title="navigate-html">HTML document</span> section, and abort
      these steps.</dd>
 
      <!-- an <span>XML MIME type</span> -->
-     <dt>Any type ending in "+xml"</dt>
-     <dt>"application/xml"</dt>
-     <dt>"text/xml"</dt>
+     <dt>Any type ending in "<code title="">+xml</code>"</dt>
+     <dt>"<code>application/xml</code>"</dt>
+     <dt>"<code>text/xml</code>"</dt>
      <dd>Follow the steps given in the <span title="navigate-xml">XML
      document</span> section. If that section determines that the
      content is <em>not</em> to be displayed as a generic XML
      document, then proceed to the next step in this overall set of
      steps. Otherwise, abort these steps.</dd>
 
-     <dt>"text/plain"</dt>
+     <dt>"<code>text/plain</code>"</dt>
      <dd>Follow the steps given in the <span
      title="navigate-text">plain text file</span> section, and abort
      these steps.</dd>
@@ -65957,8 +65956,7 @@
     string to the <code
     title="dom-DragEvent-dataTransfer">dataTransfer</code> member,
     associated with the <code
-    title="">application/microdata+json</code> format.</p> <!-- XXX
-    register -->
+    title="">application/microdata+json</code> format.</p>
 
    </li>
 
@@ -70086,6 +70084,91 @@
   <p>If an <code>EventSource</code> object is garbage collected while
   its connection is still open, the connection must be closed.</p>
 
+
+  <h4>IANA considerations</h4>
+
+  <p>This registration is for community review and will be submitted
+  to the IESG for review, approval, and registration with IANA.</p>
+
+  <h3><dfn><code>text/event-stream</code></dfn></h3>
+
+  <!--
+   To: ietf-types@iana.org
+   Subject: Registration of media type text/event-stream
+  -->
+
+  <dl>
+   <dt>Type name:</dt>
+   <dd>text</dd>
+   <dt>Subtype name:</dt>
+   <dd>event-stream</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>An event stream from an origin distinct from the origin of the
+    content consuming the event stream can result in information
+    leakage. To avoid this, user agents are required to apply CORS
+    semantics or block all cross-origin loads. <a
+    href="#refsCORS">[CORS]</a></p>
+
+    <p>Event streams can overwhelm a user agent; a user agent is
+    expected to apply suitable restrictions to avoid depleting local
+    resources because of an overabundance of information from an event
+    stream.</p>
+
+    <p>Servers can be overwhelmed if a situation develops in which the
+    server is causing clients to reconnect rapidly. Servers should use
+    a 5xx status code to indicate capacity problems, as this will
+    prevent conforming clients from reconnecting automatically.</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 and tools using Web services.
+   </dd>
+   <dt>Additional information:</dt>
+   <dd>
+    <dl>
+     <dt>Magic number(s):</dt>
+     <dd>No sequence of bytes can uniquely identify an event stream.</dd>
+     <dt>File extension(s):</dt>
+     <dd>No specific file extensions are 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 &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+   <dt>Intended usage:</dt>
+   <dd>Common</dd>
+   <dt>Restrictions on usage:</dt>
+   <dd>This format is only expected to be used by dynamic open-ended
+   streams served using HTTP or a similar protocol. Finite resources
+   are not expected to be labeled with this type.</dd>
+   <dt>Author:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+  </dl>
+
+  <p>Fragment identifiers have no meaning with
+  <code>text/event-stream</code> resources.</p>
+
   <!--END eventsource--><!--START html5-->
 
 
@@ -71631,7 +71714,7 @@
 
   <h5>IANA considerations</h5>
 
-  <h6>Registrarion of ws: scheme</h6>
+  <h6>Registration of ws: scheme</h6>
 
   <dl>
 
@@ -71672,7 +71755,7 @@
   </dl>
 
 
-  <h6>Registrarion of wss: scheme</h6>
+  <h6>Registration of wss: scheme</h6>
 
   <dl>
 
@@ -71719,7 +71802,7 @@
   port 815.</p>
 
 
-  <h6>HTTP Upgrade keyword</h6>
+  <h6>Registration of the "WebSocket" HTTP Upgrade keyword</h6>
 
   <dl>
 
@@ -72601,8 +72684,8 @@
 
   <h2 id="syntax"><dfn>The HTML syntax</dfn></h2>
 
-  <p class="note">This section only describes the rules for <code
-  title="">text/html</code> resources. Rules for XML resources are
+  <p class="note">This section only describes the rules for
+  <code>text/html</code> resources. Rules for XML resources are
   discussed in the section below entitled "<span>The XHTML
   syntax</span>".</p>
 
@@ -80744,7 +80827,7 @@
   <hr>
 
   <p>Data mining tools and other user agents that perform operations
-  on <code title="">text/html</code> content without running scripts,
+  on <code>text/html</code> content without running scripts,
   evaluating CSS or XPath expressions, or otherwise exposing the
   resulting DOM to arbitrary content, may "support namespaces" by just
   asserting that their DOM node analogues are in certain namespaces,
@@ -81184,9 +81267,8 @@
   <h2><dfn id="xhtml">The XHTML syntax</dfn></h2>
 
   <p class="note">This section only describes the rules for XML
-  resources. Rules for <code title="">text/html</code> resources are
-  discussed in the section above entitled "<span>The HTML
-  syntax</span>".</p>
+  resources. Rules for <code>text/html</code> resources are discussed
+  in the section above entitled "<span>The HTML syntax</span>".</p>
 
 
   <div class="impl">
@@ -85730,7 +85812,340 @@
 
 
 
+  <h2 class="no-num">IANA considerations</h2>
 
+  <!-- http://www.w3.org/2002/06/registering-mediatype.html -->
+
+  <p>This registration is for community review and will be submitted
+  to the IESG for review, approval, and registration with IANA.</p>
+
+  <h3><dfn><code>text/html</code></dfn></h3>
+
+  <!--
+   To: ietf-types@iana.org
+   Subject: Registration of media type text/html
+  -->
+
+  <!--
+    Obsoletes:
+    http://www.ietf.org/rfc/rfc2854
+   -->
+
+  <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 <span>document's character
+      encoding</span>, overriding any <span title="character encoding
+      declaration">character encoding declarations</span> 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 the preferred name for that
+      encoding. <a href="#refsIANACHARSET">[IANACHARSET]</a></p>
+     </dd>
+    </dl>
+   </dd>
+   <dt>Encoding considerations:</dt>
+   <dd>See the section on <span title="character encoding
+   declaration">character encoding declarations</span>.</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>img</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>text/html</code> type asserts that the resource is
+    an <span title="HTML documents">HTML document</span> using
+    <span>the HTML syntax</span>.
+   </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="#MIMESNIFF">[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 &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;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 &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+  </dl>
+
+  <p>Fragment identifiers used with <code>text/html</code> resources
+  refer to <span>the indicated part of the document</span>.</p>
+
+
+  <h3><dfn><code>application/xhtml+xml</code></dfn></h3>
+
+  <!--
+   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="#refsRFC3023">[RFC3023]</a></dd>
+   <dt>Optional parameters:</dt>
+   <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
+   <dt>Encoding considerations:</dt>
+   <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
+   <dt>Security considerations:</dt>
+   <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
+   <dt>Interoperability considerations:</dt>
+   <dd>Same as for <code>application/xml</code> <a href="#refsRFC3023">[RFC3023]</a></dd>
+   <dt>Published specification:</dt>
+   <dd>
+    Labeling a resource with the <code>application/xhtml+xml</code>
+    type asserts that the resource is an XML document that likely has
+    a root element from the <span>HTML namespace</span>. As such, the
+    relevant specifications are the XML specification, the Namespaces
+    in XML specification, and this specification. <a
+    href="#refsXML">[XML]</a> <a href="#refsXMLNAMES">[XMLNAMES]</a>
+   </dd>
+   <dt>Applications that use this media type:</dt>
+   <dd>Same as for <code>application/xml</code> <a href="#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="#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 <span>HTML namespace</span>.</dd>
+     <dt>Macintosh file type code(s):</dt>
+     <dd><code title="">TEXT</code></dd>
+    </dl>
+   </dd>
+   <dt>Person &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;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 &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+  </dl>
+
+  <p>Fragment identifiers used with <code>application/xhtml+xml</code>
+  resources have the same semantics as with any XML MIME type. <a
+  href="#refsRFC3023">[RFC3023]</a></p>
+
+
+  <h3><dfn><code>text/cache-manifest</code></dfn></h3>
+
+  <!--
+   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 US-ASCII 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 &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;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 &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+  </dl>
+
+  <p>Fragment identifiers have no meaning with
+  <code>text/cache-manifest</code> resources.</p>
+
+
+  <h3><dfn><code>application/microdata+json</code></dfn></h3>
+
+  <!--
+   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="#refsJSON">[JSON]</a></dd>
+   <dt>Optional parameters:</dt>
+   <dd>Same as for <code>application/json</code> <a href="#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="#refsJSON">[JSON]</a></dd>
+   <dt>Interoperability considerations:</dt>
+   <dd>Same as for <code>application/json</code> <a href="#refsJSON">[JSON]</a></dd>
+   <dt>Published specification:</dt>
+   <dd>
+
+    Labeling a resource with the
+    <code>application/microdata+json</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="#refsJSON">[JSON]</a>
+
+   </dd>
+   <dt>Applications that use this media type:</dt>
+   <dd>Same as for <code>application/json</code> <a href="#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="#refsJSON">[JSON]</a></dd>
+     <dt>File extension(s):</dt>
+     <dd>Same as for <code>application/json</code> <a href="#refsJSON">[JSON]</a></dd>
+     <dt>Macintosh file type code(s):</dt>
+     <dd>Same as for <code>application/json</code> <a href="#refsJSON">[JSON]</a></dd>
+    </dl>
+   </dd>
+   <dt>Person &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;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 &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+  </dl>
+
+  <p>Fragment identifiers used with
+  <code>application/microdata+json</code> resources have the same
+  semantics as when used with <code>application/json</code>. <a
+  href="#refsJSON">[JSON]</a></p>
+
+
+
   <h2 class="no-num">Index</h2>
 
   <p><i>This section is non-normative.</i></p>
@@ -86535,7 +86950,6 @@
        field is not focused, the value is displayed differently. Seems
        like this would also be useful e.g. for <output> or something so
        you can display localised dates, etc.
- XXX * update text/html RFC
  XXX * password and confirm password: can we have a way to do client-side
        validation of this?
  XXX * <input type="search">
@@ -86632,7 +87046,6 @@
  XXX * s/raise/throw/g
  XXX * be clearer about arrays/lists/collections being zero-based
        despite using the term "/index/th".
- XXX * update RFC 2854 (text/html reg)
 -->
 
  </body>

|