- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 18 Sep 2009 20:37:30 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv4493 Modified Files: Overview.html Log Message: ref the wiki where appropriate. (whatwg r3906) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3067 retrieving revision 1.3068 diff -u -d -r1.3067 -r1.3068 --- Overview.html 18 Sep 2009 20:24:25 -0000 1.3067 +++ Overview.html 18 Sep 2009 20:37:27 -0000 1.3068 @@ -9658,9 +9658,7 @@ </dl><h5 id="other-metadata-names"><span class="secno">4.2.5.2 </span>Other metadata names</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/27">ISSUE-27</a> (rel-ownership) blocks progress to Last Call</span><p><dfn id="concept-meta-extensions" title="concept-meta-extensions">Extensions to the predefined set of metadata names</dfn> may be registered in the <a href="http://wiki.whatwg.org/wiki/MetaExtensions">WHATWG Wiki - MetaExtensions page</a>. - - <p>Anyone is free to edit the WHATWG Wiki MetaExtensions page at any + MetaExtensions page</a>. <a href="#refsWHATWGWIKI">[WHATWGWIKI]</a><p>Anyone is free to edit the WHATWG Wiki MetaExtensions page at any time to add a type. These new names must be specified with the following information:<dl><dt>Keyword</dt> @@ -10085,7 +10083,7 @@ 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 + PragmaExtensions page</a>. <a href="#refsWHATWGWIKI">[WHATWGWIKI]</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
Received on Friday, 18 September 2009 20:37:44 UTC