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

html5/spec Overview.html,1.1003,1.1004

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 27 Jun 2008 06:25:01 +0000
To: public-html-commits@w3.org
Message-Id: <E1KC7OH-0003tV-Sl@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
Urlification of the 'links' section. (whatwg r1815)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1003
retrieving revision 1.1004
diff -u -d -r1.1003 -r1.1004
--- Overview.html	27 Jun 2008 04:17:43 -0000	1.1003
+++ Overview.html	27 Jun 2008 06:24:58 -0000	1.1004
@@ -36239,8 +36239,7 @@
    title="">?</code> placeholder feature of the <code
    title=dom-sqltransaction-executeSql><a
    href="#executesql">executeSql()</a></code> method, and to never construct
-   SQL statements on the fly.</p>
-  <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
+   SQL statements on the fly.
 
   <h3 id=links><span class=secno>5.11 </span>Links</h3>
 
@@ -36249,12 +36248,11 @@
   <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>.</p>
-  <!-- XXXURL change to URL -->
+   elements, represent <dfn id=hyperlinks title=hyperlink>hyperlinks</dfn>.
 
   <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 <a
-   href="#valid">valid URL</a>. This URI is the <em>destination resource</em>
+   href="#valid">valid URL</a>. This URL is the <em>destination resource</em>
    of the hyperlink.
 
   <div class=note>
@@ -36277,14 +36275,14 @@
    title=attr-hyperlink-target><code>target</code></dfn> attribute, if
    present, must be a <a href="#valid10">valid browsing context name or
    keyword</a>. User agents use this name when <a
-   href="#following0">following hyperlinks</a>.</p>
-  <!-- XXXURL change to URL -->
+   href="#following0">following hyperlinks</a>.
 
   <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
+   attribute, if present, gives the URLs of the resources that are interested
    in being notified if the user follows the hyperlink. The value must be a
-   space separated list of one or more URIs (or IRIs). The value is used by
-   the user agent when <a href="#following0">following hyperlinks</a>.
+   space separated list of one or more <span>valid URLs</span>. The value is
+   used by the user agent when <a href="#following0">following
+   hyperlinks</a>.
 
   <p>For <code><a href="#a">a</a></code> and <code><a
    href="#area">area</a></code> elements that represent hyperlinks, the
@@ -36327,18 +36325,14 @@
 
   <h4 id=following><span class=secno>5.11.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.</p>
-  <!-- XXXURL change to URL -->
-
-  <p>The URI of the hyperlink is URI given by resolving the <code
+   to the <a href="#url">URL</a> given by the <code
    title=attr-hyperlink-href><a href="#href6">href</a></code> attribute of
-   that hyperlink relative to the hyperlink's element. In the case of
-   server-side image maps, the URI of the hyperlink must further have its
-   <var><a href="#hyperlink2">hyperlink suffix</a></var> appended to it.
+   that hyperlink. In the case of server-side image maps, the URL of the
+   hyperlink must further have its <var><a href="#hyperlink2">hyperlink
+   suffix</a></var> appended to it.
 
   <p>If the user indicated a specific browsing context when following the
    hyperlink, or if the user agent is configured to follow hyperlinks by
@@ -36388,7 +36382,6 @@
    href="#source0">source browsing context</a>.
 
   <h5 id=hyperlink0><span class=secno>5.11.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
@@ -36396,39 +36389,40 @@
    the user follows the hyperlink, the user agent must take the <code
    title=attr-hyperlink-ping><a href="#ping">ping</a></code> attribute's
    value, <span title="split the string on spaces">split that string on
-   spaces</span>, treat each resulting token as a URI (resolving relative
-   URIs according to <span>element's base URI</span><!--
-  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.</p>
-  <!-- XXXURL change to URL -->
+   spaces</span>, <a href="#resolve" title="resolve a url">resolve</a> each
+   resulting token, and then should send a request (as described below) to
+   each of the resulting <a href="#absolute" title="absolute URL">absolute
+   URLs</a>. (Tokens that fail to resolve are ignored.) This may be done in
+   parallel with the primary request, and is independent of the result of
+   that request.
 
   <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
    title="">Referer</code> headers. Based on the user's preferences, UAs may
    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).</p>
-  <!-- XXXURL change to URL, algorithms? -->
+   altogether, or selectively ignore URLs in the list (e.g. ignoring any
+   third-party URLs).</p>
+  <!-- XXX fetching -->
 
-  <p>For URIs that are HTTP URIs, the requests must be performed using the
+  <p>For URLs that are HTTP URLs, 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><!-- XXXURL change to URL; XXXDOCURL -->
+   Which other headers are required depends on the URls involved.
 
-   <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>
+  <dl class=switch>
+   <dt>If both the <span title="the document's
+    address">address</span><!-- XXXDOCURL --> of the <code>Document</code>
+    object containing the hyperlink being audited and the ping URL 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
+    with, as its value, the <span title="the document's
+    address">address</span><!-- XXXDOCURL --> of the document containing the
     hyperlink, and a <code title="">Ping-To</code> HTTP header with, as its
-    value, the address of the target of the hyperlink. The request must not
-    include a <code title="">Referer</code> HTTP header.
+    value, the address of the <a href="#absolute">absolute URL</a> of the
+    target of the hyperlink. The request must not include a <code
+    title="">Referer</code> HTTP header.
 
    <dt>Otherwise, if the origins are different, but the document containing
     the hyperlink being audited was not retrieved over an encrypted
@@ -36455,13 +36449,12 @@
   <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></p>
-  <!-- XXXURL change to URL -->
+   href="#references">[RFC2965]</a>
 
   <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
    following the hyperlink will also cause secondary requests to be sent in
-   the background, possibly including listing the actual target URIs.
+   the background, possibly including listing the actual target URLs.
 
   <div class=note>
    <p>The <code title=attr-hyperlink-ping><a href="#ping">ping</a></code>
@@ -36473,9 +36466,8 @@
     href="#ping">ping</a></code> attribute provides these advantages to the
     user over those alternatives:</p>
 
-   <ul><!-- XXXURL change to URL -->
-
-    <li>It allows the user to see the final target URI unobscured.
+   <ul>
+    <li>It allows the user to see the final target URL unobscured.
 
     <li>It allows the UA to inform the user about the out-of-band
      notifications.
@@ -36934,11 +36926,10 @@
   <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.</p>
-  <!-- XXXURL change to URL -->
+   for the page as a whole.
 
   <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
+   title="">mailto:</code> URL giving the e-mail address of the author. <a
    href="#references">[MAILTO]</a>
 
   <p><strong>Synonyms</strong>: For historical reasons, user agents must also
@@ -38901,8 +38892,7 @@
    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>".</p>
-  <!-- XXXURL change URI to URL -->
+   title="">text/uri-list</code>".
 
   <p>The <dfn id=getdata title=dom-DataTransfer-getData><code>getData(<var
    title="">format</var>)</code></dfn> method must return the data that is
@@ -38912,9 +38902,9 @@
    title="">text/plain</code>". If the <var title="">format</var> is "<code
    title="">URL</code>", then the data associated with the "<code
    title="">text/uri-list</code>" format must be parsed as appropriate for
-   <code title="">text/uri-list</code> data, and the first URI from the list
+   <code title="">text/uri-list</code> data, and the first URL from the list
    must be returned. If there is no data with that format, or if there is but
-   it has no URIs, then the method must return the empty string. <a
+   it has no URLs, then the method must return the empty string. <a
    href="#references">[RFC2483]</a>
 
   <p>The <dfn id=types title=dom-DataTransfer-types><code>types</code></dfn>
@@ -40110,7 +40100,8 @@
    providing a tree-based approach to document state). Such UI models should
    be based upon the single <a href="#undo-transaction">undo transaction
    history</a> described in this section, however, such that to a script
-   there is no detectable difference.
+   there is no detectable difference.</p>
+  <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
 
   <h3 id=command><span class=secno>6.10 </span>Command APIs</h3>
 
Received on Friday, 27 June 2008 06:25:41 GMT

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