[] (0) Define how to register new http-equiv values. (credit: ma)

git-svn-id: http://svn.whatwg.org/webapps@2548 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -337,7 +337,8 @@
        <li><a href=#standard-metadata-names><span class=secno>4.2.5.1 </span>Standard metadata names</a></li>
        <li><a href=#other-metadata-names><span class=secno>4.2.5.2 </span>Other metadata names</a></li>
        <li><a href=#pragma-directives><span class=secno>4.2.5.3 </span>Pragma directives</a></li>
-       <li><a href=#charset><span class=secno>4.2.5.4 </span>Specifying the document's character encoding</a></ol></li>
+       <li><a href=#other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma directives</a></li>
+       <li><a href=#charset><span class=secno>4.2.5.5 </span>Specifying the document's character encoding</a></ol></li>
      <li><a href=#the-style-element><span class=secno>4.2.6 </span>The <code>style</code> element</a></li>
      <li><a href=#styling><span class=secno>4.2.7 </span>Styling</a></ol></li>
    <li><a href=#scripting-1><span class=secno>4.3 </span>Scripting</a>
@@ -9099,7 +9100,49 @@ people expect to have work and what is necessary.
   any particular state in the document at a time.</p>
 
 
-  <h5 id=charset><span class=secno>4.2.5.4 </span>Specifying the document's character encoding</h5>
+  <h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma directives</h5>
+
+  <p><dfn id=concept-http-equiv-extensions title=concept-http-equiv-extensions>Extensions to the
+  predefined set of pragma directives</dfn> may, under certain
+  conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
+  PragmaExtensions page</a>.</p>
+
+  <p>Such extensions must use a name that is identical to a
+  previously-registered HTTP header defined in an RFC, and must have
+  behavior identical to that described for the HTTP header. Pragma
+  directions corresponding to headers describing metadata, or not
+  requiring specific user agent processing, must not be registered;
+  instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata
+  names</a>. Pragma directions corresponding to headers that affect
+  the HTTP processing model (e.g. caching) must not be registered, as
+  they would result in HTTP-level behavior being different for user
+  agents that implement HTML than for user agents that do not.</p>
+
+  <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
+  any time to add a pragma directive satisfying these conditions. Such
+  registrations must specify the following information:</p>
+
+  <dl><dt>Keyword</dt>
+
+   <dd><p>The actual name being defined.</dd>
+
+
+   <dt>Brief description</dt>
+
+   <dd><p>A short description of the purpose of the pragma
+   directive.</dd>
+
+
+   <dt>Specification</dt>
+
+   <dd>A link to an IETF RFC defining the corresponding HTTP header.</dd>
+
+  </dl><p>Conformance checkers must use the information given on the WHATWG
+  Wiki PragmaExtensions page to establish if a value not explicitly
+  defined in this specification is allowed or not.</p>
+
+
+  <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's character encoding</h5>
 
   <!-- XXX maybe the rest should move to "writing html" section,
   though if we do then we have to duplicate the requirements in the

source

@@ -9531,6 +9531,53 @@ people expect to have work and what is necessary.
   any particular state in the document at a time.</p>
 
 
+  <h5>Other pragma directives</h5>
+
+  <p><dfn title="concept-http-equiv-extensions">Extensions to the
+  predefined set of pragma directives</dfn> may, under certain
+  conditions, be registered in the <a
+  href="http://wiki.whatwg.org/wiki/PragmaExtensions">WHATWG Wiki
+  PragmaExtensions page</a>.</p>
+
+  <p>Such extensions must use a name that is identical to a
+  previously-registered HTTP header defined in an RFC, and must have
+  behavior identical to that described for the HTTP header. Pragma
+  directions corresponding to headers describing metadata, or not
+  requiring specific user agent processing, must not be registered;
+  instead, use <span title="concept-meta-extensions">metadata
+  names</span>. Pragma directions corresponding to headers that affect
+  the HTTP processing model (e.g. caching) must not be registered, as
+  they would result in HTTP-level behavior being different for user
+  agents that implement HTML than for user agents that do not.</p>
+
+  <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
+  any time to add a pragma directive satisfying these conditions. Such
+  registrations must specify the following information:</p>
+
+  <dl>
+
+   <dt>Keyword</dt>
+
+   <dd><p>The actual name being defined.</p></dd>
+
+
+   <dt>Brief description</dt>
+
+   <dd><p>A short description of the purpose of the pragma
+   directive.</p></dd>
+
+
+   <dt>Specification</dt>
+
+   <dd>A link to an IETF RFC defining the corresponding HTTP header.</dd>
+
+  </dl>
+
+  <p>Conformance checkers must use the information given on the WHATWG
+  Wiki PragmaExtensions page to establish if a value not explicitly
+  defined in this specification is allowed or not.</p>
+
+
   <h5 id="charset">Specifying the document's character encoding</h5>
 
   <!-- XXX maybe the rest should move to "writing html" section,