W3C home > Mailing lists > Public > public-html-diffs@w3.org > July 2009

hixie: Allow conformance checkers to be used offline. (whatwg r3433)

From: poot <cvsmail@w3.org>
Date: Fri, 17 Jul 2009 10:09:37 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090717010937.9C97F2BC69@toro.w3.mag.keio.ac.jp>
hixie: Allow conformance checkers to be used offline. (whatwg r3433)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2558&r2=1.2559&f=h
http://html5.org/tools/web-apps-tracker?from=3432&to=3433

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2558
retrieving revision 1.2559
diff -u -d -r1.2558 -r1.2559
--- Overview.html	17 Jul 2009 00:57:08 -0000	1.2558
+++ Overview.html	17 Jul 2009 01:08:16 -0000	1.2559
@@ -9152,11 +9152,14 @@
 
   <p>Conformance checkers must use the information given on the WHATWG
   Wiki MetaExtensions page to establish if a value not explicitly
-  defined in this specification is allowed or not. When an author uses
-  a new type not defined by either this specification or the Wiki
-  page, conformance checkers should offer to add the value to the
-  Wiki, with the details described above, with the "proposal"
-  status.</p>
+  defined in this specification is allowed or not. Conformance
+  checkers may cache this information (e.g. for performance reasons or
+  to avoid the use of unreliable network connectivity).</p>
+
+  <p>When an author uses a new type not defined by either this
+  specification or the Wiki page, conformance checkers should offer to
+  add the value to the Wiki, with the details described above, with
+  the "proposal" status.</p>
 
   </div><p>This specification does not define how new values will get
   approved. It is expected that the Wiki will have a community that
@@ -9516,7 +9519,9 @@
 
   </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><!-- READ ME WHEN EDITING: if we ever move this to the "writing
+  defined in this specification is allowed or not. Conformance
+  checkers may cache this information (e.g. for performance reasons or
+  to avoid the use of unreliable network connectivity).<h5 id="charset"><span class="secno">4.2.5.5 </span>Specifying the document's character encoding</h5><!-- READ ME WHEN EDITING: if we ever move this to the "writing
   HTML" section, then we have to duplicate the requirements in the
   parsing section for conformance checkers, and we have to make sure
   that the requirements for charset="" apply even in XML, for the
@@ -47930,11 +47935,14 @@
 
   <p>Conformance checkers must use the information given on the WHATWG
   Wiki RelExtensions page to establish if a value not explicitly
-  defined in this specification is allowed or not. When an author uses
-  a new type not defined by either this specification or the Wiki
-  page, conformance checkers should offer to add the value to the
-  Wiki, with the details described above, with the "proposal"
-  status.</p>
+  defined in this specification is allowed or not. Conformance
+  checkers may cache this information (e.g. for performance reasons or
+  to avoid the use of unreliable network connectivity).</p>
+
+  <p>When an author uses a new type not defined by either this
+  specification or the Wiki page, conformance checkers should offer to
+  add the value to the Wiki, with the details described above, with
+  the "proposal" status.</p>
 
   </div><p>This specification does not define how new values will get
   approved. It is expected that the Wiki will have a community that
Received on Friday, 17 July 2009 01:10:14 GMT

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