[html5] r1555 - /

Wed May 7 17:37:14 PDT 2008

Author: ianh
Date: 2008-05-07 17:37:13 -0700 (Wed, 07 May 2008)
New Revision: 1555

Modified:
   header-whatwg
   index
   source
Log:
[e] (0) More issues with URIs -- add more things I need to define, make the application cache api raise errors on invalid uris

Modified: header-whatwg
===================================================================

--- header-whatwg	2008-05-08 00:28:23 UTC (rev 1554)
+++ header-whatwg	2008-05-08 00:37:13 UTC (rev 1555)
@@ -1,4 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">>
 <html lang="en-US-x-hixie">
  <head>
   <title>HTML 5</title>

Modified: index
===================================================================
--- index	2008-05-08 00:28:23 UTC (rev 1554)
+++ index	2008-05-08 00:37:13 UTC (rev 1555)
@@ -1,5 +1,9 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 
+<html>
+ <body>
+  <p>>
+
 <html lang=en-US-x-hixie>
  <head>
   <title>HTML 5</title>
@@ -5957,13 +5961,29 @@
     <li>define how to resolve relative URLs in markup attributes (using
      XMLBase as defined elsewhere right now)
 
+    <li>define how to resolve relative URLs in APIs
+
     <li>define what it means to resolve a relative URL when the base URL
      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>define URL as IRI and replace all uses of URIs and IRIs in the rest
      of the spec with URL
 
+    <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="#refsRFC3986">[RFC3986]</a> <a
+     href="#refsRFC3987">[RFC3987]</a>
+
+    <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="#refsRFC3986">[RFC3986]</a> <a
+     href="#refsRFC3987">[RFC3987]</a>
+
     <li>define how to parse URLs (maybe by deferring to RFCs)
    </ul>
   </div>
@@ -30472,9 +30492,15 @@
      <code>INVALID_STATE_ERR</code> exception and abort these steps.
 
    <li>
-    <p class=big-issue>resolve relative URIs
+    <p>If <var title="">uri</var> is not a valid URI reference, then raise a
+     <code>SYNTAX_ERR</code> exception and abort these steps. <a
+     href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a>
 
    <li>
+    <p class=big-issue>resolve relative URIs; on failure, raise a
+     <code>SYNTAX_ERR</code> exception
+
+   <li>
     <p>If there is already a resource in in the <a
      href="#application0">application cache</a> with which the <code><a
      href="#applicationcache">ApplicationCache</a></code> object is

Modified: source
===================================================================
--- source	2008-05-08 00:28:23 UTC (rev 1554)
+++ source	2008-05-08 00:37:13 UTC (rev 1555)
@@ -4441,13 +4441,30 @@
     <li>define how to resolve relative URLs in markup attributes
     (using XMLBase as defined elsewhere right now)</li>
 
+    <li>define how to resolve relative URLs in APIs</li>
+
     <li>define what it means to resolve a relative URL when the base
     URL doesn't have a path hierarchy (e.g. data:, javascript:,
     about:blank URLs)</li>
 
+    <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>
+
     <li>define URL as IRI and replace all uses of URIs and IRIs in the
     rest of the spec with URL</li>
 
+    <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="#refsRFC3986">[RFC3986]</a> <a
+    href="#refsRFC3987">[RFC3987]</a></li>
+
+    <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="#refsRFC3986">[RFC3986]</a> <a
+    href="#refsRFC3987">[RFC3987]</a></li>
+
     <li>define how to parse URLs (maybe by deferring to RFCs)</li>
 
    </ul>
@@ -28337,8 +28354,14 @@
    <code>INVALID_STATE_ERR</code> exception and abort these
    steps.</p></li>
 
-   <li><p class="big-issue">resolve relative URIs</p></li>
+   <li><p>If <var title="">uri</var> is not a valid URI reference,
+   then raise a <code>SYNTAX_ERR</code> exception and abort these
+   steps. <a href="#refsRFC3986">[RFC3986]</a> <a
+   href="#refsRFC3987">[RFC3987]</a></p></li>
 
+   <li><p class="big-issue">resolve relative URIs; on failure, raise a
+   <code>SYNTAX_ERR</code> exception</p></li>
+
    <li><p>If there is already a resource in in the <span>application
    cache</span> with which the <code>ApplicationCache</code> object is
    associated that has the address <var title="">uri</var>, then


