[html5] r3246 - [e] (0) editorial cleanup and reference collection

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-13 17:28:55 -0700 (Sat, 13 Jun 2009)
New Revision: 3246

Modified:
   index
   source
Log:
[e] (0) editorial cleanup and reference collection

Modified: index
===================================================================
--- index	2009-06-14 00:21:04 UTC (rev 3245)
+++ index	2009-06-14 00:28:55 UTC (rev 3246)
@@ -4779,8 +4779,7 @@
    for instance, with a progressively interlaced JPEG or an HTML file,
    additional tasks may be queued to process the data as it is
    downloaded. The <a href=#task-source>task source</a> for these tasks is the
-   <a href=#networking-task-source>networking task source</a>.</p> <!-- XXX make sure each
-   use of 'fetch' defines what the appropriate task is -->
+   <a href=#networking-task-source>networking task source</a>.</p>
 
   </ol><p class=note>The <a href=#application-cache>application cache</a> processing model
   introduces some <a href=#changesToNetworkingModel>changes to the
@@ -4820,11 +4819,7 @@
   headers are equivalent to the authentication aspects of the FTP
   protocol.</p>
 
-  <p class=XXX>If there are any specific questions with what should
-  be considered equivalent to what, let me know, and I'll make it more
-  explicit for those cases.</p>
 
-
   <h4 id=encrypted-http-and-related-security-concerns><span class=secno>2.6.2 </span>Encrypted HTTP and related security concerns</h4>
 
   <p>Anything in this specification that refers to HTTP also applies
@@ -4910,8 +4905,7 @@
   <p>When comparing a string specifying a character encoding with the
   name or alias of a character encoding to determine if they are
   equal, user agents must use the Charset Alias Matching rules defined
-  in Unicode Technical Standard #22. <a href=#refsUTS22>[UTS22]</a></p> <!-- XXXrefs
-  http://unicode.org/reports/tr22/#Charset_Alias_Matching -->
+  in Unicode Technical Standard #22. <a href=#refsUTS22>[UTS22]</a></p>
 
   <p class=example>For instance, "GB_2312-80" and "g.b.2312(80)" are
   considered equivalent names.</p>
@@ -69942,7 +69936,7 @@
 
   <!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->
 
-  <!--
+  <!-- REFS
 
   [COMPUTABLE] On computable numbers, with an application to the
   Entscheidungsproblem. Alan M. Turing. In Proceedings of the London
@@ -69956,6 +69950,8 @@
 
   [UNICODECASE] Unicode Standard Annex #21, Case Mappings
 
+  [UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching
+
   -->
 
 

Modified: source
===================================================================
--- source	2009-06-14 00:21:04 UTC (rev 3245)
+++ source	2009-06-14 00:28:55 UTC (rev 3246)
@@ -4405,8 +4405,7 @@
    for instance, with a progressively interlaced JPEG or an HTML file,
    additional tasks may be queued to process the data as it is
    downloaded. The <span>task source</span> for these tasks is the
-   <span>networking task source</span>.</p> <!-- XXX make sure each
-   use of 'fetch' defines what the appropriate task is -->
+   <span>networking task source</span>.</p>
 
   </ol>
 
@@ -4449,11 +4448,7 @@
   headers are equivalent to the authentication aspects of the FTP
   protocol.</p>
 
-  <p class="XXX">If there are any specific questions with what should
-  be considered equivalent to what, let me know, and I'll make it more
-  explicit for those cases.</p>
 
-
   <h4>Encrypted HTTP and related security concerns</h4>
 
   <p>Anything in this specification that refers to HTTP also applies
@@ -4544,8 +4539,7 @@
   name or alias of a character encoding to determine if they are
   equal, user agents must use the Charset Alias Matching rules defined
   in Unicode Technical Standard #22. <a
-  href="#refsUTS22">[UTS22]</a></p> <!-- XXXrefs
-  http://unicode.org/reports/tr22/#Charset_Alias_Matching -->
+  href="#refsUTS22">[UTS22]</a></p>
 
   <p class="example">For instance, "GB_2312-80" and "g.b.2312(80)" are
   considered equivalent names.</p>
@@ -82488,7 +82482,7 @@
 
   <!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->
 
-  <!--
+  <!-- REFS
 
   [COMPUTABLE] On computable numbers, with an application to the
   Entscheidungsproblem. Alan M. Turing. In Proceedings of the London
@@ -82502,6 +82496,8 @@
 
   [UNICODECASE] Unicode Standard Annex #21, Case Mappings
 
+  [UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching
+
   -->