Ljw issue369 (#1088)

* Adds `ping` attribute for hyperlink auditing section to links
* Updates IANA considerations

Fix #369

sections/attributes.include

@@ -554,6 +554,14 @@
       <td>Pattern to be matched by the form control's value</td>
       <td>Regular expression matching the JavaScript <i>Pattern</i> production</td>
     </tr>
+
+        <tr>
+      <th><code>ping</code></th>
+      <td><{a}>, <{area}></td>
+      <td>URLs to ping</td>
+      <td><a>Set of comma-separated tokens</a> consisting of valid non-empty URLs</td>
+    </tr>
+
     <tr>
       <th><code>placeholder</code></th>
       <td><{input}>; <{textarea}></td>

sections/elements.include

@@ -27,6 +27,7 @@
          <{links/href}>;
          <{links/target}>;
          <{links/download}>;
+	 <{links/ping}>;
          <{links/rel}>;
          <{links/hreflang}>;
          <{links/type}>;
@@ -69,6 +70,7 @@
          <{links/href}>;
          <{links/target}>;
          <{links/download}>;
+	 <{links/ping}>;
          <{links/rel}>;
          <{links/hreflang}>;
          <{links/type}>;

sections/iana.include

@@ -8,8 +8,6 @@
  ██  ██     ██ ██   ███ ██     ██
 ████ ██     ██ ██    ██ ██     ██
 -->
-<!-- This section ostensibly kept up to date by [email protected] -->
-
 <h2 id="iana">IANA considerations</h2>
 
 <h3 id="text-html"><code>text/html</code></h3>
@@ -234,4 +232,126 @@
   :: <cite>Custom scheme and content handlers</cite>, HTML Living Standard:
       <a href="https://html.spec.whatwg.org/#custom-handlers">https://html.spec.whatwg.org/#custom-handlers</a>
 
+<h3 id="text-ping">text/ping</h3>
+
+  <p>This registration is for community review and will be submitted to the IESG for review,
+  approval, and registration with IANA.</p>
+
+  <!--
+  To: [email protected]   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>
+    <dl>
+    <dt><code data-x="">charset</code></dt>
+    <dd>The charset parameter may be provided. The parameter's value must be "<code data-x="">utf-8</code>". This parameter serves no purpose; it is only allowed for compatibility with legacy servers.</dd>
+    </dl>
+  </dd>
+
+  <dt>Encoding considerations:</dt>
+  <dd>Not applicable.</dd>
+
+  <dt>Security considerations:</dt>
+  <dd>If used exclusively in the fashion described in the context of <a>hyperlink auditing</a>, this type introduces no new security concerns.</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 (`<code data-x="">PING</code>`).</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 &amp; email address to contact for further information:</dt>
+  <dd>  :: World Wide Web Consortium &lt;[email protected]&gt;</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 <{links/ping}ping}> >attribute.</dd>
+
+   <dt>Author:</dt>
+   <dd>Ian Hickson &lt;[email protected]></dd>
+
+   <dt>Change controller:</dt>
+   <dd>W3C</dd>
+  </dl>
+
+Fragments have no meaning with text/ping resources.
+
+<h3 id="sec-ping-to"><dfn>ping-to</dfn></h3>
+
+This section describes a header for registration in the Permanent Message Header Field Registry. <ref spec=RFC3864>
+
+  <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</dd> 
+
+  <dt>Specification document(s):</dt> 
+  <dd> This document is the relevant specification. </dd> 
+
+  <dt>Related information:</dt> 
+  <dd>None.</dd> 
+  </dl>
+
+<h3 id="sec-ping-from"><dfn>ping-from</dfn></h3>
+
+This section describes a header for registration in the Permanent Message Header Field Registry. <ref spec=RFC3864>
+
+  <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</dd> 
+
+  <dt>Specification document(s):</dt> 
+  <dd> This document is the relevant specification. </dd> 
+
+  <dt>Related information:</dt> 
+  <dd>None.</dd> 
+  </dl>
+
 </section>

sections/semantics-document-metadata.include

@@ -407,7 +407,7 @@
   that the element can be used where <a>phrasing content</a> is expected.
 
   Two categories of links can be created using the <{link}> element:
-  <a>Links to external resources</a> and <a>hyperlinks</a>. The [[#sec-link-types]] section defines
+  <a>Links to external resources</a> and <a>hyperlinks</a>. The <a>link types</a> section defines
   whether a particular link type is an external resource or a hyperlink. One <{link}> element can
   create multiple links (of which some might be [=external resource links=] and some might
   be [=hyperlinks=]); exactly which and how many links are created depends on the keywords given in