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

html5/spec Overview.html,1.978,1.979

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 18 Jun 2008 23:32:24 +0000
To: public-html-commits@w3.org
Message-Id: <E1K978a-00026u-V7@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
final bunch of annotations for url preparation (whatwg r1789)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.978
retrieving revision 1.979
diff -u -d -r1.978 -r1.979
--- Overview.html	18 Jun 2008 21:21:17 -0000	1.978
+++ Overview.html	18 Jun 2008 23:32:22 -0000	1.979
@@ -30119,7 +30119,6 @@
    <code>preventDefault()</code> method must be called when the function
    returns true instead.</p>
   <!-- IE actually uncancels the event if the function returns true -->
-  <!-- XXX update the following to match DOM3 Events -->
 
   <p>All event handler attributes on an element, whether set to null or to a
    function, must be registered as event listeners on the element, as if the
@@ -32994,7 +32993,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 -->
+  <!-- XXXURL change to URL -->
 
   <p>The <code><a href="#location2">Location</a></code> interface also has
    the complement of <a href="#uri-decomposition">URI decomposition
@@ -33164,7 +33163,7 @@
      affect the browsing context, then abort these steps and proceed with
      that mechanism instead.
 
-   <li>
+   <li> <!-- XXXURL change to URL -->
     <p>If the new resource is to be fetched using HTTP GET or equivalent, and
      if the browsing context being navigated is a <a
      href="#top-level">top-level browsing context</a>, then check if there
@@ -33179,7 +33178,7 @@
      must then fetch the resource from the <a href="#select0"
      title=concept-appcache-selection>most appropriate application cache</a>
      of those that match.</p>
-
+    <!-- XXXURL JSURI issue -->
     <p>Otherwise, start fetching the specified resource in the appropriate
      manner (e.g. performing an HTTP GET or POST operation, or reading the
      file from disk, or executing script in the case of a <a
@@ -33204,7 +33203,7 @@
      user agent may allow the user to cancel this navigation attempt or start
      other navigation attempts.
 
-   <li>
+   <li> <!-- XXXURL change to URL, "fetch"? -->
     <p>If the resource was not fetched from an <a
      href="#application0">application cache</a>, and was to be fetched using
      HTTP GET or equivalent, and its URI <a href="#matches"
@@ -33230,7 +33229,7 @@
        title=concept-appcache-foreign>foreign</a>, then the user agent must
        discard the failed load and instead continue along these steps using
        <var title="">candidate</var> as the resource.</p>
-
+      <!-- XXXURL change to URL -->
       <p>For the purposes of session history (and features that depend on
        session history, e.g. bookmarking) the user agent must use the URI of
        the resource that was requested (the one that matched the
@@ -33454,7 +33453,8 @@
    that must be used when determining the character encoding according to the
    rules given in the above specifications. Once the character encoding is
    established, the <a href="#character1">document's character encoding</a>
-   must be set to that character encoding.
+   must be set to that character encoding.</p>
+  <!-- XXXURL change to URL, (algorithms?) -->
 
   <p>If the root element, as parsed according to the XML specifications cited
    above, is found to be an <code><a href="#html">html</a></code> element
@@ -33467,7 +33467,8 @@
    Otherwise, as soon as the root element is inserted into the DOM, the user
    agent must run the <a href="#application3"
    title=concept-appcache-init-no-attribute>application cache selection
-   algorithm</a> with no manifest.
+   algorithm</a> with no manifest.</p>
+  <!-- XXXURL change to URL -->
 
   <p class=note>Because the processing of the <code
    title=attr-html-manifest><a href="#manifest">manifest</a></code> attribute
@@ -33648,6 +33649,7 @@
 
   <h4 id=scroll-to-fragid><span class=secno>4.9.8 </span><dfn id=navigating0
    title=navigate-fragid>Navigating to a fragment identifier</dfn></h4>
+  <!-- XXXURL change to URL; XXXDOCURL? -->
 
   <p>When a user agent is supposed to navigate to a fragment identifier, then
    the user agent must <a href="#update2">update the session history with the
@@ -33675,7 +33677,8 @@
    following processing model must be followed to determine what <a
    href="#the-indicated">the indicated part of the document</a> is.
 
-  <ol>
+  <ol><!-- XXXURL algorithms -->
+
    <li>
     <p>Let <i>fragid</i> be the &lt;fragment&gt; part of the URI. <a
      href="#references">[RFC3987]</a>
@@ -33817,6 +33820,8 @@
     <p>If the <i>specified entry</i> is a state object or the first entry for
      a <code>Document</code>, the user agent must <a href="#activating0"
      title="activate the state object">activate that entry</a>.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>If the <i>specified entry</i> has a URI that differs from the <a
@@ -35733,7 +35738,8 @@
    this information to the third party along with any identifying information
    (names, credit card numbers, addresses) obtained by the site. If a third
    party cooperates with multiple sites to obtain such information, a profile
-   can still be created.
+   can still be created.</p>
+  <!-- XXXURL change to URL -->
 
   <p>However, user tracking is to some extent possible even with no
    cooperation from the user agent whatsoever, for instance by using session
@@ -35829,7 +35835,8 @@
   <p>The <code><a href="#a">a</a></code>, <code><a
    href="#area">area</a></code>, and <code><a href="#link">link</a></code>
    elements can, in certain situations described in the definitions of those
-   elements, represent <dfn id=hyperlinks title=hyperlink>hyperlinks</dfn>.
+   elements, represent <dfn id=hyperlinks title=hyperlink>hyperlinks</dfn>.</p>
+  <!-- XXXURL change to URL -->
 
   <p>The <dfn id=href6 title=attr-hyperlink-href><code>href</code></dfn>
    attribute on a hyperlink element must have a value that is a valid URI (or
@@ -35855,7 +35862,8 @@
    title=attr-hyperlink-target><code>target</code></dfn> attribute, if
    present, must be a <a href="#valid9">valid browsing context name or
    keyword</a>. User agents use this name when <a
-   href="#following0">following hyperlinks</a>.
+   href="#following0">following hyperlinks</a>.</p>
+  <!-- XXXURL change to URL -->
 
   <p>The <dfn id=ping title=attr-hyperlink-ping><code>ping</code></dfn>
    attribute, if present, gives the URIs of the resources that are interested
@@ -35904,10 +35912,12 @@
 
   <h4 id=following><span class=secno>4.12.2 </span><dfn
    id=following0>Following hyperlinks</dfn></h4>
+  <!-- XXXURL change to URL -->
 
   <p>When a user <em>follows a hyperlink</em>, the user agent must <a
    href="#navigate">navigate</a> a <a href="#browsing1">browsing context</a>
-   to the URI of the hyperlink.
+   to the URI of the hyperlink.</p>
+  <!-- XXXURL change to URL -->
 
   <p>The URI of the hyperlink is URI given by resolving the <code
    title=attr-hyperlink-href><a href="#href6">href</a></code> attribute of
@@ -35963,6 +35973,7 @@
    href="#source0">source browsing context</a>.
 
   <h5 id=hyperlink0><span class=secno>4.12.2.1. </span>Hyperlink auditing</h5>
+  <!-- XXXURL change to URL, algorithms -->
 
   <p>If an <code><a href="#a">a</a></code> or <code><a
    href="#area">area</a></code> hyperlink element has a <code
@@ -35975,7 +35986,8 @@
   XXXURL -->)
    and then should send a request (as described below) to each of the
    resulting URIs. This may be done in parallel with the primary request, and
-   is independent of the result of that request.
+   is independent of the result of that request.</p>
+  <!-- XXXURL change to URL -->
 
   <p>User agents should allow the user to adjust this behavior, for example
    in conjunction with a setting that disables the sending of HTTP <code
@@ -35983,17 +35995,19 @@
    either <a href="#ignored">ignore</a> the <code
    title=attr-hyperlink-ping><a href="#ping">ping</a></code> attribute
    altogether, or selectively ignore URIs in the list (e.g. ignoring any
-   third-party URIs).
+   third-party URIs).</p>
+  <!-- XXXURL change to URL, algorithms? -->
 
   <p>For URIs that are HTTP URIs, the requests must be performed using the
    POST method (with an empty entity body in the request). All relevant
    cookie and HTTP authentication headers must be included in the request.
    Which other headers are required depends on the URIs involved.
 
-  <dl class=switch>
-   <dt>If both the URI of the <code>Document</code> object containing the
-    hyperlink being audited and the ping URI have the <a
-    href="#same-origin">same origin</a>
+  <dl class=switch><!-- XXXURL change to URL; XXXDOCURL -->
+
+   <dt>If both the <span title="the document's address">address</span> of the
+    <code>Document</code> object containing the hyperlink being audited and
+    the ping URI have the <a href="#same-origin">same origin</a>
 
    <dd>The request must include a <code title="">Ping-From</code> HTTP header
     with, as its value, the location of the document containing the
@@ -36026,7 +36040,8 @@
   <p>User agents must ignore any entity bodies returned in the responses, but
    must, unless otherwise specified by the user, honor the HTTP headers
    (including, in particular, redirects and HTTP cookie headers). <a
-   href="#references">[RFC2965]</a>
+   href="#references">[RFC2965]</a></p>
+  <!-- XXXURL change to URL -->
 
   <p>When the <code title=attr-hyperlink-ping><a href="#ping">ping</a></code>
    attribute is present, user agents should clearly indicate to the user that
@@ -36043,7 +36058,8 @@
     href="#ping">ping</a></code> attribute provides these advantages to the
     user over those alternatives:</p>
 
-   <ul>
+   <ul><!-- XXXURL change to URL -->
+
     <li>It allows the user to see the final target URI unobscured.
 
     <li>It allows the UA to inform the user about the out-of-band
@@ -36503,7 +36519,8 @@
   <p>For <code><a href="#link">link</a></code> elements, the <code
    title=rel-author><a href="#author">author</a></code> keyword indicates
    that the referenced document provides further information about the author
-   for the page as a whole.
+   for the page as a whole.</p>
+  <!-- XXXURL change to URL -->
 
   <p class=note>The "referenced document" can be, and often is, a <code
    title="">mailto:</code> URI giving the e-mail address of the author. <a
@@ -37242,10 +37259,12 @@
    described above, with the "proposal" status.
 
   <p>This specification does not define how new values will get approved. It
-   is expected that the Wiki will have a community that addresses this.
+   is expected that the Wiki will have a community that addresses this.</p>
+  <!-- XXXURL change to URL -->
 
   <h3 id=interfaces><span class=secno>4.13 </span>Interfaces for URI
    manipulation</h3>
+  <!-- XXXURL change to URL -->
 
   <p>An interface that has a complement of <dfn id=uri-decomposition>URI
    decomposition attributes</dfn> will have seven attributes with the
@@ -37260,19 +37279,23 @@
            attribute DOMString <a href="#search1" title=dom-uda-search>search</a>;
            attribute DOMString <a href="#hash0" title=dom-uda-hash>hash</a>;
 </pre>
+  <!-- XXXURL change to URL -->
 
   <p>The attributes defined to be URI decomposition attributes must act as
    described for the attributes with the same corresponding names in this
-   section.
+   section.</p>
+  <!-- XXXURL change to URL -->
 
   <p>In addition, an interface with a complement of URI decomposition
    attributes will define an <dfn id=input
    title=concept-uda-input>input</dfn>, which is a URI that the attributes
    act on, and a <dfn id=common3 title=concept-uda-setter>common setter
    action</dfn>, which is a set of steps invoked when any of the attributes'
-   setters are invoked.
+   setters are invoked.</p>
+  <!-- XXXURL change to URL -->
 
-  <p>The seven URI decomposition attributes have similar requirements.
+  <p>The seven URI decomposition attributes have similar requirements.</p>
+  <!-- XXXURL change to URL -->
 
   <p>On getting, if the <a href="#input" title=concept-uda-input>input</a>
    fulfills the condition given in the "getter condition" column
@@ -37281,7 +37304,8 @@
    URI given in the "component" column, with any prefixes specified in the
    "prefix" column appropriately added to the start of the string and any
    suffixes specified in the "suffix" column appropriately added to the end
-   of the string. Otherwise, the attribute must return the empty string.
+   of the string. Otherwise, the attribute must return the empty string.</p>
+  <!-- XXXURL change to URL; algorithms or something? -->
 
   <p>On setting, the new value must first be mutated as described by the
    "setter preprocessor" column, then mutated by %-escaping any characters in
@@ -37294,7 +37318,8 @@
    user agent must let <var title="">output</var> be equal to the <a
    href="#input" title=concept-uda-input>input</a>. Finally, the user agent
    must invoke the <a href="#common3" title=concept-uda-setter>common setter
-   action</a> with the value of <var title="">output</var>.
+   action</a> with the value of <var title="">output</var>.</p>
+  <!-- XXXURL change to URL -->
 
   <p>When replacing a component in the URI, if the component is part of an
    optional group in the URI syntax consisting of a character followed by the
@@ -37304,7 +37329,8 @@
   <p class=note>The previous paragraph applies in particular to the "<code
    title="">:</code>" before a &lt;port> component, the "<code
    title="">?</code>" before a &lt;query> component, and the "<code
-   title="">#</code>" before a &lt;fragment> component.
+   title="">#</code>" before a &lt;fragment> component.</p>
+  <!-- XXXURL change to URL; algorithms -->
 
   <p>The rules for parsing and constructing URIs are described in RFC 3986
    and RFC 3987. <a href="#references">[RFC3986]</a> <a
@@ -38684,7 +38710,8 @@
    value "<code title="">Text</code>", then it must be treated as "<code
    title="">text/plain</code>". If the <var title="">format</var> is "<code
    title="">URL</code>", then it must be treated as "<code
-   title="">text/uri-list</code>".
+   title="">text/uri-list</code>".</p>
+  <!-- XXXURL change URI to URL -->
 
   <p>The <dfn id=getdata title=dom-DataTransfer-getData><code>getData(<var
    title="">format</var>)</code></dfn> method must return the data that is
@@ -39984,7 +40011,8 @@
 
    <dd><strong>Value:</strong> The string "<code title="">true</code>" if the
     expression given for the "State" above is true, the string "<code
-    title="">false</code>" otherwise.
+    title="">false</code>" otherwise.</dd>
+   <!-- XXXURL change to URL -->
 
    <dt><dfn id=createlink
     title=command-createLink><code>createLink</code></dfn>
@@ -40090,7 +40118,8 @@
    <dd><strong>State:</strong> Always false.
 
    <dd><strong>Value:</strong> Always the string "<code
-    title="">false</code>".
+    title="">false</code>".</dd>
+   <!-- XXXURL change to URL -->
 
    <dt><dfn id=insertimage
     title=command-insertImage><code>insertImage</code></dfn>
@@ -40501,13 +40530,15 @@
   void <a href="#addeventsource" title=dom-RemoteEventTarget-addEventSource>addEventSource</a>(in DOMString src);
   void <a href="#removeeventsource" title=dom-RemoteEventTarget-removeEventSource>removeEventSource</a>(in DOMString src);
 };</pre>
+  <!-- XXXURL change to URL; algorithms? -->
 
   <p>When the <dfn id=addeventsource
    title=dom-RemoteEventTarget-addEventSource><code>addEventSource(<var
    title="">src</var>)</code></dfn> method is invoked, the user agent must
    add the URI specified in <var title="">src</var> to the <a
    href="#list-of3" title=concept-event-source-list>list of event sources</a>
-   for that object. The same URI can be registered multiple times.
+   for that object. The same URI can be registered multiple times.</p>
+  <!-- XXXURL change to URL -->
 
   <p>When the <dfn id=removeeventsource
    title=dom-RemoteEventTarget-removeEventSource><code>removeEventSource(<var
@@ -40516,7 +40547,8 @@
    href="#list-of3" title=concept-event-source-list>list of event sources</a>
    for that object. If the same URI has been registered multiple times,
    removing it must remove only one instance of that URI for each invocation
-   of the <code title=removeEventSource>removeEventSource()</code> method.
+   of the <code title=removeEventSource>removeEventSource()</code> method.</p>
+  <!-- XXXURL algorithms -->
 
   <p>Relative URIs must be resolved relative to <span
    class=big-issue>...</span>.
@@ -40527,7 +40559,8 @@
   <p>Each object implementing the <code>EventTarget</code> and <code><a
    href="#remoteeventtarget0">RemoteEventTarget</a></code> interfaces has a
    <dfn id=list-of3 title=concept-event-source-list>list of event
-   sources</dfn> that are registered for that object.
+   sources</dfn> that are registered for that object.</p>
+  <!-- XXXURL change to URL; algorithms for 'fetch'? -->
 
   <p>When a new URI is added to this list, the user agent should, as soon as
    all currently executing scripts (if any) have finished executing, and if
@@ -40557,6 +40590,7 @@
    <li>The <dfn id=last-event title=concept-event-stream-last-event-id>last
     event ID string</dfn>. This must initially be the empty string.
   </ul>
+  <!-- XXXURL change to URL -->
 
   <p>In general, the semantics of the transport protocol specified by the
    URIs for the event sources must be followed, including HTTP caching rules.
@@ -40625,14 +40659,16 @@
   <p>HTTP 300 Multiple Choices responses should be handled automatically if
    possible (treating the responses as if they were 302 Found responses
    pointing to the appropriate resource), and otherwise must be treated as
-   HTTP 404 responses.
+   HTTP 404 responses.</p>
+  <!-- XXXURL change to URL -->
 
   <p>HTTP 301 Moved Permanently responses must cause the user agent to
    reconnect using the new server specified URI instead of the previously
    specified URI for all subsequent requests for this event source. (It
    doesn't affect other event sources with the same URI unless they also
    receive 301 responses, and it doesn't affect future sessions, e.g. if the
-   page is reloaded.)
+   page is reloaded.)</p>
+  <!-- XXXURL change to URL -->
 
   <p>HTTP 302 Found, 303 See Other, and 307 Temporary Redirect responses must
    cause the user agent to connect to the new server-specified URI, but if
@@ -40814,6 +40850,8 @@
      href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">NCName</a>, set the
      <var title="">data</var> buffer and the <var title="">event name</var>
      buffer to the empty string and abort these steps.
+   </li>
+   <!-- XXXURL change to URL -->
 
    <li>
     <p>Otherwise, create an event that uses the <code><a
@@ -40937,7 +40975,8 @@
   <p>Legacy proxy servers are known to, in certain cases, drop HTTP
    connections after a short timeout. To protect against such proxy servers,
    authors can include a comment line (one starting with a ':' character)
-   every 15 seconds or so.
+   every 15 seconds or so.</p>
+  <!-- XXXURL change to URL -->
 
   <p>Authors wishing to relate event source connections to each other or to
    specific documents previously served might find that relying on IP
@@ -46566,7 +46605,7 @@
      href="#html-namespace0">HTML namespace</a>. Append it to the
      <code>Document</code> object. Put this element in the <a
      href="#stack">stack of open elements</a>.</p>
-
+    <!-- XXXURL change to URL; algorithms (with care) -->
     <p id=parser-appcache>If the token has an attribute "manifest", then run
      the <a href="#application2"
      title=concept-appcache-init-with-attribute>application cache selection
@@ -46577,7 +46616,7 @@
      Otherwise, run the <a href="#application3"
      title=concept-appcache-init-no-attribute>application cache selection
      algorithm</a> with no manifest. <a href="#references">[RFC3986]</a></p>
-    <!-- XXX when dealing with
+    <!-- XXXURL when dealing with
     microsyntaxes-urls, hoist all this into that section so we can get
     rid of "URI" here -->
     
Received on Wednesday, 18 June 2008 23:42:06 GMT

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