W3C home > Mailing lists > Public > public-html-diffs@w3.org > December 2008

spec/Overview.html 1.1719 2548 Define how to register new http-equiv va

From: poot <cvsmail@w3.org>
Date: Sat, 20 Dec 2008 18:47:41 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20081220094742.10AB42BBFC@toro.w3.mag.keio.ac.jp>

Define how to register new http-equiv values. (credit: ma) (whatwg
r2548)

Refresh state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1719.html#attr-meta-http-equiv-refresh
4.2.5.5 Specifying the document's character encoding
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1719.html#charset
character encoding declaration
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1719.html#character-encoding-declaration
4.2.5.4 Other pragma directives
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1719.html#other-pragma-directives

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1718&r2=1.1719&f=h
http://html5.org/tools/web-apps-tracker?from=2547&to=2548

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1718
retrieving revision 1.1719
diff -u -d -r1.1718 -r1.1719
--- Overview.html	20 Dec 2008 09:21:48 -0000	1.1718
+++ Overview.html	20 Dec 2008 09:45:01 -0000	1.1719
@@ -271,7 +271,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>
@@ -7475,7 +7476,38 @@
    </dd>
 
   </dl><p>There must not be more than one <code><a href=#meta>meta</a></code> element with
-  any particular state in the document at a time.<h5 id=charset><span class=secno>4.2.5.4 </span>Specifying the document's character encoding</h5><!-- XXX maybe the rest should move to "writing html" section,
+  any particular state in the document at a time.<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>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>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:<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.<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
   parsing section for conformance checkers --><p>A <dfn id=character-encoding-declaration>character encoding declaration</dfn> is a mechanism by
   which the character encoding used to store or transmit a document is
Received on Saturday, 20 December 2008 09:48:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT