[html5] r3582 - [] (0) Add text/ping registration.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-08-10 22:57:15 -0700 (Mon, 10 Aug 2009)
New Revision: 3582

Modified:
   index
   source
Log:
[] (0) Add text/ping registration.

Modified: index
===================================================================
--- index	2009-08-11 01:54:51 UTC (rev 3581)
+++ index	2009-08-11 05:57:15 UTC (rev 3582)
@@ -1042,7 +1042,8 @@
    <li><a href=#text/html><span class=secno>13.1 </span><code>text/html</code></a></li>
    <li><a href=#application/xhtml+xml><span class=secno>13.2 </span><code>application/xhtml+xml</code></a></li>
    <li><a href=#text/cache-manifest><span class=secno>13.3 </span><code>text/cache-manifest</code></a></li>
-   <li><a href=#application/microdata+json><span class=secno>13.4 </span><code>application/microdata+json</code></a></ol></li>
+   <li><a href=#text/ping><span class=secno>13.4 </span><code>text/ping</code></a></li>
+   <li><a href=#application/microdata+json><span class=secno>13.5 </span><code>application/microdata+json</code></a></ol></li>
  <li><a class=no-num href=#index>Index</a></li>
  <li><a class=no-num href=#references>References</a></li>
  <li><a class=no-num href=#acknowledgements>Acknowledgements</a></ol>
@@ -56558,7 +56559,8 @@
 
   <p>For URLs that are HTTP URLs, the requests must be performed by
   <a href=#fetch title=fetch>fetching</a> the specified URLs using the
-  POST method, with an entity body with the <a href=#mime-type>MIME type</a> <code title="">text/ping</code> consisting of the four-character string
+  POST method, with an entity body with the <a href=#mime-type>MIME type</a>
+  <code><a href=#text/ping>text/ping</a></code> consisting of the four-character string
   "<code title="">PING</code>". All relevant cookie and HTTP
   authentication headers must be included in the request. Which other
   headers are required depends on the URLs involved.</p>
@@ -77568,10 +77570,75 @@
   <code><a href=#text/cache-manifest>text/cache-manifest</a></code> resources.</p>
 
 
-  <h3 id=application/microdata+json><span class=secno>13.4 </span><dfn><code>application/microdata+json</code></dfn></h3>
+  <h3 id=text/ping><span class=secno>13.4 </span><dfn><code>text/ping</code></dfn></h3>
 
   <!--
    To: ietf-types at 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=#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 at 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=#ping>ping</a></code> attribute.</dd>
+   <dt>Author:</dt>
+   <dd>Ian Hickson <ian at 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>
+
+  <!--
+   To: ietf-types at iana.org
    Subject: Registration of media type application/microdata+json
   -->
 

Modified: source
===================================================================
--- source	2009-08-11 01:54:51 UTC (rev 3581)
+++ source	2009-08-11 05:57:15 UTC (rev 3582)
@@ -62033,8 +62033,8 @@
 
   <p>For URLs that are HTTP URLs, the requests must be performed by
   <span title="fetch">fetching</span> the specified URLs using the
-  POST method, with an entity body with the <span>MIME type</span> <code
-  title="">text/ping</code> consisting of the four-character string
+  POST method, with an entity body with the <span>MIME type</span>
+  <code>text/ping</code> consisting of the four-character string
   "<code title="">PING</code>". All relevant cookie and HTTP
   authentication headers must be included in the request. Which other
   headers are required depends on the URLs involved.</p>
@@ -86122,6 +86122,72 @@
   <code>text/cache-manifest</code> resources.</p>
 
 
+  <h3><dfn><code>text/ping</code></dfn></h3>
+
+  <!--
+   To: ietf-types at 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
+    <span>hyperlink auditing</span>, 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>text/ping</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 at 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">ping</code> attribute.</dd>
+   <dt>Author:</dt>
+   <dd>Ian Hickson <ian at hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>W3C and WHATWG</dd>
+  </dl>
+
+  <p>Fragment identifiers have no meaning with
+  <code>text/ping</code> resources.</p>
+
+
   <h3><dfn><code>application/microdata+json</code></dfn></h3>
 
   <!--