html5/spec Overview.html,1.966,1.967

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv23029

Modified Files:
	Overview.html 
Log Message:
notes for urls, and typo fixes (whatwg r1777)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.966
retrieving revision 1.967
diff -u -d -r1.966 -r1.967
--- Overview.html	13 Jun 2008 19:16:13 -0000	1.966
+++ Overview.html	16 Jun 2008 07:20:28 -0000	1.967
@@ -59,7 +59,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ-->13 June 2008</h2>
+    Editor's Draft <!--ZZZ-->16 June 2008</h2>
 
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
@@ -207,7 +207,7 @@
 
   <p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
    the W3C working group responsible for this specification's progress along
-   the W3C Recommendation track. <!--ZZZ:--> This specification is the 13
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 16
    June 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
   <!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
   <!-- relationship to other work (required) -->
@@ -6314,9 +6314,26 @@
      doesn't have a path hierarchy (e.g. data:, javascript:, about:blank
      URLs)
 
-    <li>define how to handle URIs that contain non-ascii characters (and it's
-     not the same as handling as IRIs, especially if the character encoding
-     of the document isn't UTF-8)
+    <li>
+     <p>define how to handle URIs that contain non-ascii characters (and it's
+      not the same as handling as IRIs, especially if the character encoding
+      of the document isn't UTF-8)</p>
+
+     <p>First parse it (we need to define that. For some schemes it's not per
+      spec -- e.g. apparently for ftp: we should split from hosts on ';').
+      Then handle each bit as follows:</p>
+
+     <p>scheme: no further processing (treat %-escaped characters literally,
+      treat unicode characters as unicode characters).</p>
+
+     <p>host: expand %-encoded bytes to Unicode as UTF-8, treat unicode
+      characters as per IDN.</p>
+
+     <p>path: don't expand %-encoded bytes. Re-encode unicode to UTF-8 and
+      percent-encode.</p>
+
+     <p>query: don't expand %-encoded bytes. Re-encode unicode to the page's
+      encoding. Do not percent-encode.</p>
 
     <li>define URL as IRI and replace all uses of URIs and IRIs in the rest
      of the spec with URL
@@ -6324,12 +6341,12 @@
     <li>define "valid URL" in terms of valid URIs and IRIs and replace that
      concept through the spec to a pointer here, getting rid of references to
      <a href="#references">[RFC3986]</a> <a
-     href="#references">[RFC3987]</a>
+     href="#references">[RFC3987]</a> outside this section
 
     <li>define "valid URL reference" in terms of valid URI references and IRI
      references and replace that concept through the spec to a pointer here,
      getting rid of references to <a href="#references">[RFC3986]</a> <a
-     href="#references">[RFC3987]</a>
+     href="#references">[RFC3987]</a> outside this section
 
     <li>define how to parse URLs (maybe by deferring to RFCs)
 
@@ -9571,8 +9588,8 @@
          outlinee</var> element.
 
        <li>
-        <p><i>Loop:</i> If <var title="">current section</var> has no child
-         sections, stop these steps.
+        <p><i>Finding the deepest child:</i> If <var title="">current
+         section</var> has no child sections, stop these steps.
 
        <li>
         <p>Let <var title="">current section</var> be the last child <a
@@ -9580,7 +9597,7 @@
          <var title="">current section</var>.
 
        <li>
-        <p>Go back to the substep labeled <i>Loop</i>.
+        <p>Go back to the substep labeled <i>finding the deepest child</i>.
       </ol>
 
      <dt>When exiting a <a href="#sectioning0">sectioning content</a> element
@@ -9629,10 +9646,10 @@
 
        <li>
         <p>If the element being entered has a <a href="#rank">rank</a> lower
-         than the rank of the heading of the <var title="">candidate
-         section</var>, then create a new <a href="#section0"
-         title=concept-section>section</a>, and append it to <var
-         title="">candidate section</var>. (This does not change which
+         than the <a href="#rank">rank</a> of the heading of the <var
+         title="">candidate section</var>, then create a new <a
+         href="#section0" title=concept-section>section</a>, and append it to
+         <var title="">candidate section</var>. (This does not change which
          section is the last section in the outline.) Let <var
          title="">current section</var> be this new section. Let the element
          being entered be the new heading for the <var title="">current

Received on Monday, 16 June 2008 07:21:06 UTC