W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2008

html5/spec Overview.html,1.977,1.978

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 18 Jun 2008 21:21:20 +0000
To: public-html-commits@w3.org
Message-Id: <E1K955k-0002TO-89@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
yet more mindnumbingly boring preparation work for the upcoming URL reorg (whatwg r1788)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.977
retrieving revision 1.978
diff -u -d -r1.977 -r1.978
--- Overview.html	18 Jun 2008 08:20:12 -0000	1.977
+++ Overview.html	18 Jun 2008 21:21:17 -0000	1.978
@@ -31044,8 +31044,7 @@
   <p>The <code title=dom-navigator-registerContentHandler><a
    href="#registercontenthandler">registerContentHandler()</a></code> method
    would work equivalently, but for unknown MIME types instead of unknown
-   protocols.</p>
-  <!-- XXXURL XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
+   protocols.
 
   <h3 id=offline><span class=secno>4.7 </span>Offline Web applications</h3>
 
@@ -31056,15 +31055,18 @@
   <p class=big-issue>...
 
   <h4 id=appcache><span class=secno>4.7.2 </span>Application caches</h4>
+  <!-- XXXURL change to URL -->
 
   <p>An <dfn id=application0>application cache</dfn> is a collection of
    resources. An application cache is identified by the URI of a resource
-   manifest which is used to populate the cache.
+   manifest which is used to populate the cache.</p>
+  <!-- XXXURL change to URL -->
 
   <p>Application caches are versioned, and there can be different instances
    of caches for the same manifest URI, each having a different version. A
    cache is newer than another if it was created after the other (in other
-   words, caches in a group have a chronological order).
+   words, caches in a group have a chronological order).</p>
+  <!-- XXXURL change to URL -->
 
   <p>Each group of application caches for the same manifest URI have a common
    <dfn id=update0 title=concept-appcache-status>update status</dfn>, which
@@ -31089,7 +31091,7 @@
   <p>An application cache consists of:
 
   <ul>
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>One of more resources (including their out-of-band metadata, such as
      HTTP headers, if any), identified by URIs, each falling into one (or
      more) of the following categories:</p>
@@ -31106,7 +31108,7 @@
       attribute.
 
      <dt><dfn id=the-manifest title=concept-appcache-manifest>The
-      manifest</dfn>
+      manifest</dfn> <!-- XXXURL change to URL -->
 
      <dd>The resource corresponding to the URI that was given in an implicit
       entry's <code><a href="#html">html</a></code> element's <code
@@ -31137,6 +31139,7 @@
 
      <dt><dfn id=opportunistically
       title=concept-appcache-oppcache>Opportunistically cached entries</dfn>
+      <!-- XXXURL change to URL -->
 
      <dd>Resources whose URIs <a href="#matches"
       title=concept-appcache-matches-oppcache>matched</a> an <a
@@ -31150,11 +31153,13 @@
      <dd>Resources that were added to the cache by the <code
       title=dom-appcache-add><a href="#adduri">add()</a></code> method.
     </dl>
-
+    <!-- XXXURL change to URL -->
     <p class=note>A URI in the list can be flagged with multiple different
      types, and thus an entry can end up being categorized as multiple
      entries. For example, an entry can be an explicit entry and a dynamic
      entry at the same time.</p>
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>Zero or more <dfn id=opportunistic
     title=concept-appcache-oppcache-ns>opportunistic caching
@@ -31164,7 +31169,8 @@
     title=concept-appcache-fallback>fallback entry</a>. Each namespace URI
     prefix, when parsed as a URI, has the <a href="#same-origin">same
     origin</a> as <a href="#the-manifest" title=concept-appcache-manifest>the
-    manifest</a>.
+    manifest</a>.</li>
+   <!-- XXXURL change to URL -->
 
    <li>Zero or more URIs that form the <dfn id=online
     title=concept-appcache-onlinewhitelist>online whitelist</dfn>.
@@ -31227,7 +31233,7 @@
      CHARACTER TABULATION (tab) characters, followed by a single U+0023
      NUMBER SIGN (#) character, followed by zero or more characters other
      than U+000A LINE FEED (LF) and U+000D CARRIAGE RETURN (CR) characters.</p>
-
+    <!-- XXXURL change to URL -->
     <p class=note>Comments must be on a line on their own. If they were to be
      included on a line with a URI, the "#" would be mistaken for part of a
      fragment identifier.</p>
@@ -31281,13 +31287,14 @@
      zero or more U+0020 SPACE and U+0009 CHARACTER TABULATION (tab)
      characters. <a href="#references">[RFC3986]</a> <a
      href="#references">[RFC3987]</a></p>
-
+    <!-- XXXURL change to URL -->
     <p class=note>The URI or IRI references in data lines can't be empty
      strings, since those would be relative URIs to the manifest itself. Such
      lines would be confused with blank or invalid lines, anyway.</p>
   </dl>
 
-  <p>Manifests may contain sections more than once. Sections may be empty.
+  <p>Manifests may contain sections more than once. Sections may be empty.</p>
+  <!-- XXXURL change to URL -->
 
   <p>URIs that are to be fallback pages associated with <a
    href="#opportunistic" title=concept-appcache-oppcache-ns>opportunistic
@@ -31301,19 +31308,23 @@
    must have the <a href="#same-origin">same origin</a> as the manifest
    itself.
 
-  <p>An opportunistic caching namespace must not be listed more than once.
+  <p>An opportunistic caching namespace must not be listed more than once.</p>
+  <!-- XXXURL change to URL -->
 
   <p>URIs that the user agent is to put into the <a href="#online"
    title=concept-appcache-onlinewhitelist>online whitelist</a> must all be
    specified in online whitelist sections. (This is needed for any URI that
-   the page is intending to use to communicate back to the server.)
+   the page is intending to use to communicate back to the server.)</p>
+  <!-- XXXURL change to URL -->
 
   <p>URIs in the online whitelist section must not also be listed in explicit
    section, and must not be listed as fallback entries in the fallback
    section. (URIs in the online whitelist section may match opportunistic
-   caching namespaces, however.)
+   caching namespaces, however.)</p>
+  <!-- XXXURL change to URL -->
 
-  <p>Relative URIs must be given relative to the manifest's own URI.
+  <p>Relative URIs must be given relative to the manifest's own URI.</p>
+  <!-- XXXURL change to URL; maybe have explicit support for this in the URL section? -->
 
   <p>URIs in manifests must not have fragment identifiers.
 
@@ -31331,10 +31342,14 @@
    be replaced by U+FFFD REPLACEMENT CHARACTERs. (this isn't black-box
    testable since neither U+0000 nor U+FFFD are valid anywhere in the
    syntax and thus both will be treated the same anyway)-->
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">explicit URIs</var> be an initially empty list of <a
      href="#explicit" title=concept-appcache-explicit>explicit entries</a>.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">fallback URIs</var> be an initially empty mapping of
@@ -31342,6 +31357,8 @@
      title=concept-appcache-oppcache-ns>opportunistic caching namespaces</a>
      to <a href="#fallback0" title=concept-appcache-fallback>fallback
      entries</a>.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">online whitelist URIs</var> be an initially empty
@@ -31433,19 +31450,19 @@
     <dl class=switch>
      <dt>If <var title="">mode</var> is "explicit"
 
-     <dd>
+     <dd> <!-- XXXURL change to URL -->
       <p>If <var title="">line</var> is not a syntactically correct URI
        reference or IRI reference, then jump back to the step labeled "start
        of line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>Otherwise, resolve the URI reference or IRI reference to an absolute
        URI or IRI, and drop the fragment identifier, if any.</p>
-
+      <!-- XXXURL change to URL -->
       <p>Now, if the resource's URI has a different &lt;scheme> component
        than the manifest's URI (compared
        case-insensitively<!-- XXX ASCII -->), then jump back to the step
        labeled "start of line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>Otherwise, add this URI to the <var title="">explicit URIs</var>.</p>
 
      <dt>If <var title="">mode</var> is "fallback"
@@ -31463,32 +31480,32 @@
 
       <p>Strip any leading U+0020 SPACE or U+0009 CHARACTER TABULATION (tab)
        characters in <var title="">part two</var>.</p>
-
+      <!-- XXXURL change to URL -->
       <p>If <var title="">part one</var> and <var title="">part two</var> are
        not both syntactically correct URI or IRI references, then jump back
        to the step labeled "start of line".</p>
-
+      <!-- XXXURL use algorithms -->
       <p>Resolve the URI or IRI references in <var title="">part one</var>
        and <var title="">part two</var> to absolute URIs or IRIs, and drop
        the fragment identifiers, if any.</p>
-
+      <!-- XXXURL change to URL -->
       <p>If the absolute URI or IRI corresponding to <var title="">part
        one</var> is already in the <var title="">fallback URIs</var> mapping
        as an <a href="#opportunistic"
        title=concept-appcache-oppcache-ns>opportunistic caching
        namespace</a>, then jump back to the step labeled "start of line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>If the absolute URI or IRI corresponding to <var title="">part
        one</var> does not have the <a href="#same-origin">same origin</a> as
        the manifest's URI, then jump back to the step labeled "start of
        line".</p>
-      <!-- SECURITY -->
+      <!-- SECURITY --> <!-- XXXURL change to URL -->
       <p>If the absolute URI or IRI corresponding to <var title="">part
        two</var> has a different &lt;scheme> component than the manifest's
        URI (compared case-insensitively<!-- XXX
       ASCII -->), then jump
        back to the step labeled "start of line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>Otherwise, add the absolute URI or IRI corresponding to <var
        title="">part one</var> to the <var title="">fallback URIs</var>
        mapping as an <a href="#opportunistic"
@@ -31499,18 +31516,18 @@
 
      <dt>If <var title="">mode</var> is "online whitelist"
 
-     <dd>
+     <dd> <!-- XXXURL change to URL -->
       <p>If <var title="">line</var> is not a syntactically correct URI
        reference or IRI reference, then jump back to the step labeled "start
        of line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>Otherwise, resolve the URI reference or IRI reference to an absolute
        URI or IRI, and drop the fragment identifier, if any.</p>
-
+      <!-- XXXURL change to URL -->
       <p>Now, if the resource's URI has a different &lt;scheme> component
        than the manifest's URI, then jump back to the step labeled "start of
        line".</p>
-
+      <!-- XXXURL change to URL -->
       <p>Otherwise, add this URI to the <var title="">online whitelist
        URIs</var>.</p>
     </dl>
@@ -31518,12 +31535,15 @@
    <li>
     <p>Jump back to the step labeled "start of line". (That step jumps to the
      next, and last, step when the end of the file is reached.)
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Return the <var title="">explicit URIs</var> list, the <var
      title="">fallback URIs</var> mapping, and the <var title="">online
      whitelist URIs</var>.
   </ol>
+  <!-- XXXURL change to URL -->
 
   <p>Relative URI references and IRI references resolved to absolute URIs or
    IRIs in the above algorithm must be resolved according to section 5.1 of
@@ -31552,16 +31572,21 @@
    ui the first time they cache themselves (right now the original cache is
    done without notifications to the browsing contexts)
 
-  <ol>
+  <ol><!-- XXXURL change to URL -->
+
    <li>
     <p>Let <var title="">manifest URI</var> be the URI of the <a
      href="#the-manifest" title=concept-appcache-manifest>manifest</a> of the
      cache to be updated.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">cache group</var> be the group of <a
      href="#application0" title="application cache">application caches</a>
      identified by <var title="">manifest URI</var>.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">cache</var> be the most recently updated <a
@@ -31578,7 +31603,7 @@
      <i>checking</i>. This entire step must be performed as one atomic
      operation so as to avoid race conditions.
 
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>If there is already a resource with the URI of <var title="">manifest
      URI</var> in <var title="">cache</var>, and that resource is categorized
      as a <a href="#the-manifest"
@@ -31605,7 +31630,7 @@
      indicating to the user that the user agent is checking for the
      availability of updates.</p>
 
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>Fetch the resource from <var title="">manifest URI</var>, and let <var
      title="">manifest</var> be that resource.</p>
 
@@ -31676,6 +31701,8 @@
      with a cache in <var title="">cache group</var>. The default action of
      this event should be the display of some sort of user interface
      indicating to the user that a new version is being downloaded.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If this is an <a href="#upgrade"
@@ -31685,21 +31712,29 @@
      title="">manifest URI</span>, being a new version in <var title="">cache
      group</var>. Otherwise, let <var title="">new cache</var> and <var
      title="">cache</var> be the same version of the application cache.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Let <var title="">file list</var> be an empty list of URIs with flags.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Add all the URIs in the list of <a href="#explicit"
      title=concept-appcache-explicit>explicit entries</a> obtained by parsing
      <var title="">manifest</var> to <var title="">file list</var>, each
      flagged with "explicit entry".
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Add all the URIs in the list of <a href="#fallback0"
      title=concept-appcache-fallback>fallback entries</a> obtained by parsing
      <var title="">manifest</var> to <var title="">file list</var>, each
      flagged with "fallback entry".
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If this is an <a href="#upgrade"
@@ -31712,6 +31747,8 @@
      caching namespaces</a> obtained by parsing <var title="">manifest</var>
      to <var title="">file list</var>, each flagged with "opportunistic
      entry".
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If this is an <a href="#upgrade"
@@ -31719,6 +31756,8 @@
      URIs of <a href="#implicit" title=concept-appcache-implicit>implicit
      entries</a> in <var title="">cache</var> to <var title="">file
      list</var>, each flagged with "implicit entry".
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If this is an <a href="#upgrade"
@@ -31726,13 +31765,15 @@
      URIs of <a href="#dynamic3" title=concept-appcache-dynamic>dynamic
      entries</a> in <var title="">cache</var> to <var title="">file
      list</var>, each flagged with "dynamic entry".
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If any URI is in <var title="">file list</var> more than once, then
      merge the entries into one entry for that URI, that entry having all the
      flags that the original entries had.
 
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>For each URI in <var title="">file list</var>, run the following
      steps. These steps may be run in parallel for two or more of the URIs at
      a time.</p>
@@ -31778,27 +31819,37 @@
      <li>
       <p>Otherwise, the fetching succeeded. Store the resource in the <var
        title="">new cache</var>.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If the URI being processed was flagged as an "explicit entry" in
        <var title="">file list</var>, then categorize the entry as an <a
        href="#explicit" title=concept-appcache-explicit>explicit entry</a>.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If the URI being processed was flagged as a "fallback entry" in <var
        title="">file list</var>, then categorize the entry as a <a
        href="#fallback0" title=concept-appcache-fallback>fallback entry</a>.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If the URI being processed was flagged as a "opportunistic entry" in
        <var title="">file list</var>, then categorize the entry as an <a
        href="#opportunistically"
        title=concept-appcache-oppcache>opportunistically cached entry</a>.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If the URI being processed was flagged as an "implicit entry" in
        <var title="">file list</var>, then categorize the entry as a <a
        href="#implicit" title=concept-appcache-implicit>implicit entry</a>.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If the URI being processed was flagged as an "dynamic entry" in <var
@@ -31811,6 +31862,8 @@
      if it's not there already, and categorize this entry (whether newly
      added or not) as <a href="#the-manifest"
      title=concept-appcache-manifest>the manifest</a>.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Store the list of <a href="#opportunistic"
@@ -31818,6 +31871,8 @@
      and the URIs of the <a href="#fallback0"
      title=concept-appcache-fallback>fallback entries</a> that they map to,
      in the new cache.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Store the URIs that form the new <a href="#online"
@@ -31842,7 +31897,7 @@
    <li>
     <p>If this is a <a href="#cache" title=concept-appcache-cache>cache
      attempt</a>, then:</p>
-
+    <!-- XXXURL change to URL -->
     <p id=flagAsCandidateForCache-result>Associate any <code>Document</code>
      objects that were <a href="#flagAsCandidateForCache">flagged as
      candidates</a> for this manifest URI's caches with <var
@@ -31908,7 +31963,8 @@
   <p>The processing model of application caches for offline support in Web
    applications is part of the <a href="#navigate"
    title=navigate>navigation</a> model, but references the algorithms defined
-   in this section.
+   in this section.</p>
+  <!-- XXXURL change to URL -->
 
   <p>A URI <dfn id=matches title=concept-appcache-matches-oppcache>matches an
    opportunistic caching namespace</dfn> if there exists an <a
@@ -31924,7 +31980,7 @@
    an opportunistic caching namespace can match more than one application
    cache at a time, but only matches one namespace in each cache.
 
-  <div class=example>
+  <div class=example> <!-- XXXURL change to URL -->
    <p>If a manifest <code title="">http://example.com/app1/manifest</code>
     declares that <code title="">http://example.com/resources/images</code>
     should be opportunistically cached, and the user navigates to <code
@@ -31933,6 +31989,7 @@
     title="">http://example.com/app1/manifest</code> contains a namespace
     with a match for that URI.</p>
   </div>
+  <!-- XXXURL change to URL -->
 
   <p>When the <dfn id=application2
    title=concept-appcache-init-with-attribute>application cache selection
@@ -31943,7 +32000,7 @@
    <dt>If the resource is not being loaded as part of navigation of a <a
     href="#top-level">top-level browsing context</a>
 
-   <dd>
+   <dd> <!-- XXXURL change to URL -->
     <p>As an optimization, if the resource was loaded from an <a
      href="#application0">application cache</a>, and the manifest URI of that
      cache doesn't match the manifest URI with which the algorithm was
@@ -31955,6 +32012,7 @@
      caches.</p>
    </dd>
    <!-- otherwise, we're talking top-level browsing contexts only: -->
+   <!-- XXXURL change to URL -->
 
    <dt>If the resource being loaded was loaded from an application cache and
     the URI of that application cache's manifest is the same as the manifest
@@ -31964,6 +32022,8 @@
     <p>Associate the <code>Document</code> with the cache from which it was
      loaded. Invoke the <a href="#application1">application cache update
      process</a>.</p>
+   </dd>
+   <!-- XXXURL change to URL -->
 
    <dt>If the resource being loaded was loaded from an application cache and
     the URI of that application cache's manifest is <em>not</em> the same as
@@ -31992,13 +32052,16 @@
     but it was loaded using HTTP GET or equivalent
 
    <dd>
-    <ol>
+    <ol><!-- XXXURL change to URL -->
+
      <li>
       <p>If the manifest URI does not have the <a href="#same-origin">same
        origin</a> as the resource's own URI, then invoke the <a
        href="#application3"
        title=concept-appcache-init-no-attribute>application cache selection
        algorithm</a> again, but without a manifest, and abort these steps.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If there is already an <a href="#application0">application cache</a>
@@ -32011,6 +32074,8 @@
        associate the <code>Document</code> with that cache, invoke the <a
        href="#application1">application cache update process</a>, and abort
        these steps.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li id=flagAsCandidateForCache>
       <p>Flag the resource's <code>Document</code> as a candidate for this
@@ -32018,6 +32083,8 @@
        href="#flagAsCandidateForCache-result">associated with an application
        cache identified by this manifest URI</a> later, when such an <a
        href="#application0">application cache</a> is ready.
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>If there is already an <a href="#application0">application cache</a>
@@ -32032,6 +32099,8 @@
        removing any other categories it might have), and abort these steps.
        (An <a href="#application1">application cache update process</a> is
        already in progress.)
+     </li>
+     <!-- XXXURL change to URL -->
 
      <li>
       <p>Otherwise, there is no matching <a href="#application0">application
@@ -32073,12 +32142,16 @@
    <li>
     <p>If the resource is not to be fetched using the HTTP GET mechanism or
      equivalent, then fetch the resource normally and abort these steps.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If the resource's URI, ignoring its fragment identifier if any, is
      listed in the <a href="#application0">application cache</a>'s <a
      href="#online" title=concept-appcache-onlinewhitelist>online
      whitelist</a>, then fetch the resource normally and abort these steps.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If the resource's URI is <a href="#implicit"
@@ -32092,7 +32165,7 @@
      entry</a> in the <a href="#application0">application cache</a>, then
      fetch the resource from the cache and abort these steps.
 
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>If the resource's URI has the <a href="#same-origin">same origin</a>
      as the manifest's URI, and the start of the resource's URI's
      &lt;path&gt; component is exactly matched by the &lt;path&gt; component
@@ -32249,7 +32322,8 @@
    title=dom-appcache-add><a href="#adduri">add()</a></code> method, with the
    oldest entry being the zeroth entry, and the most recently added entry
    having the index <span><code title=dom-appcache-length><a
-   href="#length8">length</a></code>-1</span>.
+   href="#length8">length</a></code>-1</span>.</p>
+  <!-- XXXURL change to URL -->
 
   <p>The <dfn id=itemindex4 title=dom-appcache-item><code>item(<var
    title="">index</var>)</code></dfn> method must return the absolute URI of
@@ -32271,15 +32345,21 @@
     <p>If the <code><a href="#applicationcache">ApplicationCache</a></code>
      object is not associated with any application cache, then raise an
      <code>INVALID_STATE_ERR</code> exception and abort these steps.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <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="#references">[RFC3986]</a> <a href="#references">[RFC3987]</a>
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p class=big-issue>resolve relative URIs; on failure, raise a
      <code>SYNTAX_ERR</code> exception
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If there is already a resource in in the <a
@@ -32289,6 +32369,8 @@
      that entry is categorized as a <a href="#dynamic3"
      title=concept-appcache-dynamic>dynamic entry</a> and return and abort
      these steps.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If <var title="">uri</var> has a different &lt;scheme> component than
@@ -32297,6 +32379,8 @@
 
    <li>
     <p>Return, but do not abort these steps.
+   </li>
+   <!-- XXXURL change to URL, maybe xref "fetch"? -->
 
    <li>
     <p>Fetch the resource referenced by <var title="">uri</var>.
@@ -32326,7 +32410,8 @@
    target of Progress Events, much like the <a
    href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest-2/Overview.html?content-type=text/html;%20charset=utf-8#xmlhttprequesteventtarget-interface">XMLHttpRequestEventTarget</a>
    interface. This would also make this far more complex to spec and
-   implement.
+   implement.</p>
+  <!-- XXXURL algorithms -->
 
   <p>The <dfn id=remove1 title=dom-appcache-remove><code>remove(<var
    title="">uri</var>)</code></dfn> method must remove the <a
@@ -32515,7 +32600,8 @@
    return the object implementing the <code><a
    href="#history2">History</a></code> interface for that <code><a
    href="#window">Window</a></code> object's <a href="#active">active
-   document</a>.
+   document</a>.</p>
+  <!-- XXXURL change to URL -->
 
   <p><code><a href="#history2">History</a></code> objects represent their <a
    href="#browsing1">browsing context</a>'s session history as a flat list of
@@ -32526,7 +32612,8 @@
    position, and other information associated with it.
 
   <p class=note>This does not imply that the user interface need be linear.
-   See the <a href="#history-notes">notes below</a>.
+   See the <a href="#history-notes">notes below</a>.</p>
+  <!-- XXXURL change to URL -->
 
   <p>URIs without associated <a href="#state" title="state object">state
    objects</a> are added to the session history as the user (or script)
@@ -32585,11 +32672,13 @@
    algorithms given below, act as if they had not. When the user or script
    navigates back or forwards to a page which has no in-memory DOM objects,
    any other entries that shared the same <code>Document</code> object with
-   it must share the new object as well.
+   it must share the new object as well.</p>
+  <!-- XXXURL change to URL -->
 
   <p>When state object entries are added, a URI can be provided. This URI is
    used to replace the state object entry if the <code>Document</code> is
-   evicted.
+   evicted.</p>
+  <!-- XXXURL change to URL -->
 
   <p>When a user agent discards the DOM from an entry in the session history,
    it must also discard all the entries that share that <code>Document</code>
@@ -32687,15 +32776,16 @@
   <p>The <dfn id=pushstate title=dom-history-pushState><code>pushState(<var
    title="">data</var>, <var title="">title</var>, <var
    title="">url</var>)</code></dfn> method adds a state object to the
-   history.
+   history.</p>
+  <!-- XXXURL algorithms XXXDOCURL -->
 
   <p>When this method is invoked, the user agent must first check the third
    argument. If a third argument is specified, then the user agent must
    verify that the third argument is a valid URI or IRI (as defined by RFC
    3986 and 3987), and if so, that, after resolving it to an absolute URI, it
-   is either identical to the document's URI, or that it differs from the
-   document's URI only in the &lt;query&gt;, &lt;abs_path&gt;, and/or
-   &lt;fragment&gt; parts, as applicable (the &lt;query&gt; and
+   is either identical to <span>the document's address</span>, or that it
+   differs from that address only in the &lt;query&gt;, &lt;abs_path&gt;,
+   and/or &lt;fragment&gt; parts, as applicable (the &lt;query&gt; and
    &lt;abs_path&gt; parts can only be the same if the document's URI uses a
    hierarchical &lt;scheme&gt;). If the verification fails (either because
    the argument is syntactically incorrect, or differs in a way not described
@@ -32712,7 +32802,8 @@
    href="#current1">current entry</a> is the last entry in the session
    history, or if there are no entries after the <a href="#current1">current
    entry</a> that reference the same <code>Document</code> object, then no
-   entries are removed.
+   entries are removed.</p>
+  <!-- XXXURL change to URL -->
 
   <p>Then, the user agent must add a state object entry to the session
    history, after the <a href="#current1">current entry</a>, with the
@@ -32781,6 +32872,7 @@
      bubbles but is not cancelable and has no default action.
   </ol>
   <!-- XXX onpopstate should be defined somewhere -->
+  <!-- XXXURL check with DOM3 Events -->
 
   <pre
    class=idl>interface <dfn id=popstateevent>PopStateEvent</dfn> : Event {
@@ -32822,10 +32914,10 @@
    href="#active">active document</a>.
 
   <p><code><a href="#location2">Location</a></code> objects provide a
-   representation of the URI of their document, and allow the <a
-   href="#current1">current entry</a> of the <a href="#browsing1">browsing
-   context</a>'s session history to be changed, by adding or replacing
-   entries in the <code title=dom-history><a
+   representation of <span title="the document's address">their document's
+   address</span>, and allow the <a href="#current1">current entry</a> of the
+   <a href="#browsing1">browsing context</a>'s session history to be changed,
+   by adding or replacing entries in the <code title=dom-history><a
    href="#history1">history</a></code> object.
 
   <pre class=idl>interface <dfn id=location2>Location</dfn> {
@@ -32834,7 +32926,8 @@
   void <a href="#replace" title=dom-location-replace>replace</a>(in DOMString url);
   void <span title=dom-location-reload>reload</span>();
 
-  // <a href="#uri-decomposition">URI decomposition attributes</a> <!-- blame brendan for these "innovative" names -->
+  <!-- XXXURL change to URL
+ -->  // <a href="#uri-decomposition">URI decomposition attributes</a> <!-- blame brendan for these "innovative" names -->
            attribute DOMString <a href="#protocol" title=dom-location-protocol>protocol</a>;
            attribute DOMString <a href="#host" title=dom-location-host>host</a>;
            attribute DOMString <a href="#hostname" title=dom-location-hostname>hostname</a>;
@@ -32843,6 +32936,7 @@
            attribute DOMString <a href="#search" title=dom-location-search>search</a>;
            attribute DOMString <a href="#hash" title=dom-location-hash>hash</a>;
 };</pre>
+  <!-- XXXURL change to URL -->
 
   <p>The <dfn id=href5 title=dom-location-href><code>href</code></dfn>
    attribute returns the address of the page represented by the associated
@@ -32889,7 +32983,8 @@
   <p class=note>If the <a href="#script2">script execution context</a> of a
    script isn't a <code><a href="#window">Window</a></code> object, then it
    can't ever get to a <code><a href="#location2">Location</a></code> object
-   to call these methods.
+   to call these methods.</p>
+  <!-- XXXURL algorithms -->
 
   <p>Relative <var title="">url</var> arguments for <code
    title=dom-location-assign><a href="#assign">assign()</a></code> and <code
@@ -32899,6 +32994,7 @@
   <!-- XXX what about if
   the base URI is data: or javascript: or about: or something else
   without a way to resolve base URIs? -->
+  <!-- XXXURLXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
 
   <p>The <code><a href="#location2">Location</a></code> interface also has
    the complement of <a href="#uri-decomposition">URI decomposition
Received on Wednesday, 18 June 2008 21:21:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:57 GMT