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

html5/spec Overview.html,1.969,1.970

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 17 Jun 2008 09:20:50 +0000
To: public-html-commits@w3.org
Message-Id: <E1K8XMw-0008RE-6z@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
work in progress along the path to writing the URL section (whatwg r1780)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.969
retrieving revision 1.970
diff -u -d -r1.969 -r1.970
--- Overview.html	16 Jun 2008 09:57:19 -0000	1.969
+++ Overview.html	17 Jun 2008 09:20:47 -0000	1.970
@@ -59,7 +59,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ-->16 June 2008</h2>
+    Editor's Draft <!--ZZZ-->17 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 16
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 17
    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) -->
@@ -2471,7 +2471,7 @@
 
    <dt>XML Base
 
-   <dd>
+   <dd> <!-- XXXURL remove entire entry, define it all in URLs section -->
     <p id=xmlBase>User agents must follow the rules given by XML Base to
      resolve relative URIs in HTML and XHTML fragments. That is the mechanism
      used in this specification for resolving relative URIs in DOM trees. <a
@@ -2593,7 +2593,7 @@
    of HTML, ranging from short static documents to long essays or reports
    with rich multimedia, as well as to fully-fledged interactive
    applications.</p>
-  <!-- XXXURL -->
+  <!-- XXXURL remove entire paragraph -->
 
   <p>For readability, the term URI is used to refer to both ASCII URIs and
    Unicode IRIs, as those terms are defined by RFC 3986 and RFC 3987
@@ -2890,15 +2890,16 @@
 
   <p>The <dfn id=referrer
    title=dom-document-referrer><code>referrer</code></dfn> attribute must
-   return either the URI of the <a href="#active">active document</a> of the
-   <a href="#source0">source browsing context</a> at the time the navigation
-   was started (that is, the page which <a href="#navigate"
-   title=navigate>navigated</a> the <a href="#browsing1">browsing context</a>
-   to the current document), or the empty string if there is no such
-   originating page, or if the UA has been configured not to report referrers
-   in this case, or if the navigation was initiated for a <a
-   href="#hyperlinks">hyperlink</a> with a <code title=rel-noreferrer><a
-   href="#noreferrer">noreferrer</a></code> keyword.
+   return either the <span title="the document's
+   address">address</span><!-- XXXDOXURL xref --> of the <a
+   href="#active">active document</a> of the <a href="#source0">source
+   browsing context</a> at the time the navigation was started (that is, the
+   page which <a href="#navigate" title=navigate>navigated</a> the <a
+   href="#browsing1">browsing context</a> to the current document), or the
+   empty string if there is no such originating page, or if the UA has been
+   configured not to report referrers in this case, or if the navigation was
+   initiated for a <a href="#hyperlinks">hyperlink</a> with a <code
+   title=rel-noreferrer><a href="#noreferrer">noreferrer</a></code> keyword.
 
   <p class=note>In the case of HTTP, the <code title=dom-document-referrer><a
    href="#referrer">referrer</a></code> DOM attribute will match the <code
@@ -2910,12 +2911,14 @@
    page does not (e.g. when navigating from an <code title="">https:</code>
    page to an <code title="">http:</code> page).
 
+  <hr>
+
   <p>The <dfn id=cookie0 title=dom-document-cookie><code>cookie</code></dfn>
    attribute represents the cookies of the resource.</p>
-  <!-- XXX which
-  resource? e.g. document.open() should return the cookies of the
-  document that called document.open(), not of about:blank or the
-  document that had .open() called on, as I understand it. -->
+  <!-- XXX this needs work; e.g. document.open() should return the
+  cookies of the document that called document.open(), not of
+  about:blank or the document that had .open() called on, as I
+  understand it. -->
 
   <p id=sandboxCookies>On getting, if the <a href="#sandboxed2">sandboxed
    origin browsing context flag</a> is set on the <a
@@ -2943,6 +2946,8 @@
    cookies are sent to which parts of the site, and are not in any way a
    security feature.
 
+  <hr>
+
   <p>The <dfn id=lastmodified
    title=dom-document-lastModified><code>lastModified</code></dfn> attribute,
    on getting, must return the date and time of the <code>Document</code>'s
@@ -3163,7 +3168,9 @@
    <dfn id=reflect>reflect</dfn> a particular <span>content attribute</span>.
    This means that on getting, the DOM attribute returns the current value of
    the content attribute, and on setting, the DOM attribute changes the value
-   of the content attribute to the given value.
+   of the content attribute to the given value.</p>
+  <!-- XXXURL refer to URLs and use the "resolve to absolute URL"
+  algorithm -->
 
   <p>If a reflecting DOM attribute is a <code>DOMString</code> attribute
    whose content attribute is defined to contain a URI, then on getting, the
@@ -3171,7 +3178,9 @@
    an absolute URI, and on setting, must set the content attribute to the
    specified literal value. If the content attribute is absent, the DOM
    attribute must return the default value, if the content attribute has one,
-   or else the empty string.
+   or else the empty string.</p>
+  <!-- XXXURL refer to URLs and use the "resolve to absolute URL"
+  algorithm -->
 
   <p>If a reflecting DOM attribute is a <code>DOMString</code> attribute
    whose content attribute is defined to contain one or more URIs, then on
@@ -6314,15 +6323,12 @@
      <a href="#references">[RFC3986]</a> <a
      href="#references">[RFC3987]</a> outside this section
 
-    <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, using the <dfn
-     id=scripts0>script's base URI</dfn> maybe
+    <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> outside this section
 
-    <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 parse URLs (maybe by deferring to RFCs)
 
     <li>
      <p>define how to handle URIs that contain non-ascii characters (and it's
@@ -6345,12 +6351,15 @@
      <p>query: don't expand %-encoded bytes. Re-encode unicode to the page's
       encoding. Do not percent-encode.</p>
 
-    <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> outside this section
+    <li>define how to resolve relative URLs in markup attributes (using
+     XMLBase as defined elsewhere right now)
 
-    <li>define how to parse URLs (maybe by deferring to RFCs)
+    <li>define how to resolve relative URLs in APIs, using the <dfn
+     id=scripts0>script's base URI</dfn> maybe
+
+    <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 "an <dfn id=elements2>element's base URI</dfn>" and make the
      various places that talk about a base URI in the context of an element
@@ -7398,7 +7407,8 @@
    href="#application2" title=concept-appcache-init-with-attribute>has an
    effect</a> during the early stages of document load. Changing the
    attribute dynamically thus has no effect (and thus, no DOM API is provided
-   for this attribute).
+   for this attribute).</p>
+  <!-- XXXURL change to URL (non-normative) -->
 
   <p class=note>Later <code><a href="#base">base</a></code> elements can't
    affect the resolving of relative URIs in <code title=attr-html-manifest><a
@@ -7535,6 +7545,7 @@
            attribute DOMString <a href="#target0" title=dom-base-target>target</a>;
 };</pre>
   </dl>
+  <!-- XXXURL change to URL (non-normative) -->
 
   <p>The <code><a href="#base">base</a></code> element allows authors to
    specify the document's base URI for the purposes of resolving relative
@@ -7551,14 +7562,16 @@
    attribute, or both.
 
   <p>The <dfn id=href title=attr-base-href><code>href</code></dfn> content
-   attribute, if specified, must contain a URI (or IRI).
+   attribute, if specified, must contain a valid URI (or IRI).</p>
+  <!-- XXXURL change to "attributes defined to take URLs" or some such -->
 
   <p>A <code><a href="#base">base</a></code> element, if it has an <code
    title=attr-base-href><a href="#href">href</a></code> attribute, must come
    before any other elements in the tree that have attributes with URIs
    (except the <code><a href="#html">html</a></code> element and its <code
    title=attr-html-manifest><a href="#manifest">manifest</a></code>
-   attribute).
+   attribute).</p>
+  <!-- XXXURL move to URLs section -->
 
   <p>User agents must use the value of the <code
    title=att-base-href>href</code> attribute of the first <code><a
@@ -7569,7 +7582,8 @@
    3986 ("Establishing a Base URI": "Base URI Embedded in Content"). This
    base URI from RFC 3986 is referred to by the algorithm given in XML Base,
    which <a href="#xmlBase">is a normative part of this specification</a>. <a
-   href="#references">[RFC3986]</a>
+   href="#references">[RFC3986]</a></p>
+  <!-- XXXURL move to URLs section -->
 
   <p>If the base URI given by this attribute is a relative URI, it must be
    resolved relative to the higher-level base URIs (i.e. the base URI from
@@ -7577,7 +7591,8 @@
    an absolute base URI. All <code title=attr-xml-base><a
    href="#xmlbase">xml:base</a></code> attributes must be ignored when
    resolving relative URIs in this <code title=attr-base-href><a
-   href="#href">href</a></code> attribute.
+   href="#href">href</a></code> attribute.</p>
+  <!-- XXXURL leave this here, but make it clearer -->
 
   <p class=note>If there are multiple <code><a href="#base">base</a></code>
    elements with <code title=att-base-href>href</code> attributes, all but
@@ -7660,7 +7675,7 @@
 
   <p>The destination of the link is given by the <dfn id=href1
    title=attr-link-href><code>href</code></dfn> attribute, which must be
-   present and must contain a URI (or IRI). If the <code
+   present and must contain a valid URI (or IRI). If the <code
    title=attr-link-href><a href="#href1">href</a></code> attribute is absent,
    then the element does not define a link.
 
@@ -7718,8 +7733,8 @@
    <li>The title of the resource (given by the <code title=attr-link-title><a
     href="#title2">title</a></code> attribute).
 
-   <li>The URI of the resource (given by the <code title=attr-link-href><a
-    href="#href1">href</a></code> attribute).
+   <li>The address of the resource (given by the <code
+    title=attr-link-href><a href="#href1">href</a></code> attribute).
 
    <li>The language of the resource (given by the <code
     title=attr-link-hreflang><a href="#hreflang">hreflang</a></code>
@@ -7836,7 +7851,11 @@
    specified on <code><a href="#link">link</a></code> elements that do not
    have a <code title=attr-link-rel><a href="#rel">rel</a></code> attribute
    that specifies the <code title=rel-icon><a href="#icon3">icon</a></code>
-   keyword.
+   keyword.</p>
+  <!-- XXXURL just change "not relative to base URIs set by the
+  document (e.g. using a <code>base</code> element or <code
+  title="attr-xml-base">xml:base</code> attributes)" to something like
+  "not using the rules in this specification" or some such -->
 
   <p>Some versions of HTTP defined a <code title="">Link:</code> header, to
    be processed like a series of <code><a href="#link">link</a></code>
@@ -8126,7 +8145,8 @@
    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 just change to URL? -->
 
   <p>Metadata names whose values are to be URIs must not be proposed or
    accepted. Links must be represented using the <code><a
@@ -8386,6 +8406,8 @@
      <li>
       <p>Strip any U+0009 CHARACTER TABULATION, U+000A LINE FEED (LF), and
        U+000D CARRIAGE RETURN (CR) characters from <var title="">url</var>.
+     </li>
+     <!-- XXXURL refer to algorithm -->
 
      <li>
       <p>Resolve the <var title="">url</var> value to an absolute URI using
@@ -8442,6 +8464,7 @@
      the page is to be reloaded; in the latter case the integer represents a
      number of seconds before the page is to be replaced by the page at the
      given URI.</p>
+    <!-- XXXURL -->
   </dl>
 
   <p>There must not be more than one <code><a href="#meta0">meta</a></code>
@@ -8710,9 +8733,10 @@
 
    <dd>
     <p>For <code><a href="#link">link</a></code> elements, the location must
-     be the URI given by the element's <code title=attr-link-href><a
-     href="#href1">href</a></code> content attribute. For <code><a
-     href="#style1">style</a></code> elements, there is no location.
+     be the URI<!--XXXURL absolute URL --> given by the element's <code
+     title=attr-link-href><a href="#href1">href</a></code> content attribute.
+     For <code><a href="#style1">style</a></code> elements, there is no
+     location.
 
    <dt>The intended destination media for style information (<code
     title=dom-stylesheet-media>media</code> DOM attribute)
@@ -10198,7 +10222,8 @@
   </dl>
 
   <p>The <code><a href="#blockquote">blockquote</a></code> element represents
-   a section that is quoted from another source.
+   a section that is quoted from another source.</p>
+  <!-- XXXURL rephrase somehow -->
 
   <p>Content inside a <code><a href="#blockquote">blockquote</a></code> must
    be quoted from another source, whose URI, if it has one, should be cited
@@ -10206,8 +10231,8 @@
    attribute.
 
   <p>If the <code title=attr-blockquote-cite><a href="#cite">cite</a></code>
-   attribute is present, it must be a URI (or IRI). User agents should allow
-   users to follow such citation links.
+   attribute is present, it must be a valid URI (or IRI). User agents should
+   allow users to follow such citation links.
 
   <p>If a <code><a href="#blockquote">blockquote</a></code> element is <a
    href="#preceded">preceded or followed</a> by a single <a
@@ -10993,15 +11018,16 @@
    from another source.
 
   <p>Quotation punctuation (such as quotation marks), if any, must be placed
-   inside the <code><a href="#q">q</a></code> element.
+   inside the <code><a href="#q">q</a></code> element.</p>
+  <!-- XXXURL copy blockquote paragraph -->
 
   <p>Content inside a <code><a href="#q">q</a></code> element must be quoted
    from another source, whose URI, if it has one, should be cited in the <dfn
    id=cite1 title=attr-q-cite><code>cite</code></dfn> attribute.
 
   <p>If the <code title=attr-q-cite><a href="#cite1">cite</a></code>
-   attribute is present, it must be a URI (or IRI). User agents should allow
-   users to follow such citation links.
+   attribute is present, it must be a valid URI (or IRI). User agents should
+   allow users to follow such citation links.
 
   <p>If a <code><a href="#q">q</a></code> element is contained (directly or
    indirectly) in a <a href="#paragraph">paragraph</a> that contains a single
@@ -13382,14 +13408,14 @@
    href="#del">del</a></code> elements</h4>
 
   <p>The <dfn id=cite3 title=attr-mod-cite><code>cite</code></dfn> attribute
-   may be used to specify a URI that explains the change. When that document
-   is long, for instance the minutes of a meeting, authors are encouraged to
-   include a fragment identifier pointing to the specific part of that
-   document that discusses the change.
+   may be used to specify the address of a document that explains the change.
+   When that document is long, for instance the minutes of a meeting, authors
+   are encouraged to include a fragment identifier pointing to the specific
+   part of that document that discusses the change.
 
   <p>If the <code title=attr-mod-cite><a href="#cite3">cite</a></code>
-   attribute is present, it must be a URI (or IRI) that explains the change.
-   User agents should allow users to follow such citation links.
+   attribute is present, it must be a valid URI (or IRI) that explains the
+   change. User agents should allow users to follow such citation links.
 
   <p>The <dfn id=datetime1
    title=attr-mod-datetime><code>datetime</code></dfn> attribute may be used
@@ -13743,9 +13769,9 @@
 
   <p><strong>Authoring requirements</strong>: The <code title=attr-img-src><a
    href="#src">src</a></code> attribute must be present, and must contain a
-   URI (or IRI).
+   valid URI (or IRI).
 
-  <p class=big-issue>Should we restrict the URI to pointing to an image?
+  <p class=big-issue>Should we restrict the URL to pointing to an image?
    What's an image? Is PDF an image? (Safari supports PDFs in &lt;img>
    elements.) How about SVG? (Opera supports those). WMFs? XPMs? HTML?
 
@@ -14161,8 +14187,8 @@
 
   <p>The <code title=attr-img-src><a href="#src">src</a></code> attribute, on
    setting, must cause the user agent to immediately begin to download the
-   specified resource<!-- XXX xref what fetching means, how to resolve
-  URIs in attributes (including those not in the DOM) -->,
+   specified resource<!-- XXX xref what fetching means, XXXURL how to
+  resolve URLs in attributes (including those not in the DOM) -->,
    unless the user agent cannot support images, or its support for images has
    been disabled.
 
@@ -14388,11 +14414,12 @@
    nested <a href="#browsing1">browsing context</a>.
 
   <p>The <dfn id=src1 title=attr-iframe-src><code>src</code></dfn> attribute,
-   if present, must be a URI (or IRI) to a page that the nested <a
+   if present, must be a valid URI (or IRI) of a page that the nested <a
    href="#browsing1">browsing context</a> is to contain. When the browsing
    context is created, if the attribute is present, the user agent must <a
-   href="#navigate">navigate</a> this browsing context to the given URI, with
-   <a href="#replacement">replacement enabled</a>, and with the <code><a
+   href="#navigate">navigate</a> this browsing context to the given
+   URI<!-- XXXURL resolve relative URLs -->, with <a
+   href="#replacement">replacement enabled</a>, and with the <code><a
    href="#iframe">iframe</a></code> element's document's <a
    href="#browsing1">browsing context</a> as the <a href="#source0">source
    browsing context</a>. If the user <a href="#navigate"
@@ -14404,8 +14431,10 @@
 
   <p>Whenever the <code title=attr-iframe-src><a href="#src1">src</a></code>
    attribute is set, the nested <a href="#browsing1">browsing context</a>
-   must be <a href="#navigate" title=navigate>navigated</a> to the given URI,
-   with the <code><a href="#iframe">iframe</a></code> element's document's <a
+   must be <a href="#navigate" title=navigate>navigated</a> to the given
+   URI<!-- XXXURL
+  resolve relative URLs -->, with the <code><a
+   href="#iframe">iframe</a></code> element's document's <a
    href="#browsing1">browsing context</a> as the <a href="#source0">source
    browsing context</a>.
 
@@ -14608,9 +14637,11 @@
    document</a> has the <a href="#same-origin">same origin</a> as the
    <code><a href="#iframe">iframe</a></code> element's document, or the <a
    href="#browsing1">browsing context</a>'s <a href="#active">active
-   document</a>'s <em>URI</em> has the <a href="#same-origin">same origin</a>
-   as the <code><a href="#iframe">iframe</a></code> element's document, the
-   following requirements apply:
+   document</a>'s <em><a href="#address"><span title="the document's
+   address">address</span><!-- XXX xref --></a></em> has the <a
+   href="#same-origin">same origin</a> as the <code><a
+   href="#iframe">iframe</a></code> element's document, the following
+   requirements apply:
 
   <ul>
    <li>
@@ -14804,7 +14835,8 @@
 
   <p>The <dfn id=src3 title=attr-embed-src><code>src</code></dfn> attribute
    gives the address of the resource being embedded. The attribute must be
-   present and contain a URI (or IRI).
+   present and contain a valid URI (or IRI).</p>
+  <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->
 
   <p>If the <code title=attr-embed-src><a href="#src3">src</a></code>
    attribute is missing, then the <code><a href="#embed">embed</a></code>
@@ -14959,7 +14991,7 @@
 
   <p>The <dfn id=data title=attr-object-data><code>data</code></dfn>
    attribute, if present, specifies the address of the resource. If present,
-   the attribute must be a URI (or IRI).
+   the attribute must be a valid URI (or IRI).
 
   <p>The <dfn id=type6 title=attr-object-type><code>type</code></dfn>
    attribute, if present, specifies the type of the resource. If present, the
@@ -15422,7 +15454,7 @@
   <p>The <dfn id=poster title=attr-video-poster><code>poster</code></dfn>
    attribute gives the address of an image file that the user agent can show
    while no video data is available. The attribute, if present, must contain
-   a URI (or IRI).
+   a valid URI (or IRI).
 
   <p class=note>The image given by the <code title=attr-video-poster><a
    href="#poster">poster</a></code> attribute is intended to be a <i>poster
@@ -15771,7 +15803,7 @@
 
   <p>The <dfn id=src5 title=attr-source-src><code>src</code></dfn> attribute
    gives the address of the <a href="#media10">media resource</a>. The value
-   must be a URI (or IRI). This attribute must be present.
+   must be a valid URI (or IRI). This attribute must be present.
 
   <p>The <dfn id=type8 title=attr-source-type><code>type</code></dfn>
    attribute gives the type of the <a href="#media10">media resource</a>, to
@@ -16120,7 +16152,7 @@
   <p>The <dfn id=src7 title=attr-media-src><code>src</code></dfn> content
    attribute on <a href="#media7" title="media element">media elements</a>
    gives the address of the media resource (video, audio) to show. The
-   attribute, if present, must contain a URI (or IRI).
+   attribute, if present, must contain a valid URI (or IRI).
 
   <p>If the <code title=attr-media-src><a href="#src7">src</a></code>
    attribute of a <a href="#media7">media element</a> that is already in a
@@ -16232,7 +16264,7 @@
    must return the empty string if the <a href="#media7">media element</a>'s
    <code title=dom-media-networkState><a
    href="#networkstate">networkState</a></code> has the value <a
-   href="#empty" title=dom-media-EMPTY>EMPTY</a>, and the absolute URL of the
+   href="#empty" title=dom-media-EMPTY>EMPTY</a>, and the absolute URI of the
    <a href="#chosen">chosen media resource</a> otherwise.
 
   <h5 id=network0><span class=secno>3.11.10.3. </span>Network states</h5>
@@ -23534,8 +23566,8 @@
 
   <p>The <dfn id=src9 title=attr-script-src><code>src</code></dfn> attribute,
    if specified, gives the address of the external script resource to use.
-   The value of the attribute must be a URI (or IRI) to a script resource of
-   the type given by the <code title=attr-script-type><a
+   The value of the attribute must be a valid URI (or IRI) to a script
+   resource of the type given by the <code title=attr-script-type><a
    href="#type11">type</a></code> attribute, if the attribute is present, or
    of the type "<code title="">text/javascript</code>", if the attribute is
    absent.
@@ -24167,8 +24199,8 @@
    represents a target for events generated by a remote server.
 
   <p>The <dfn id=src11 title=attr-event-source-src><code>src</code></dfn>
-   attribute, if specified, must give a URI (or IRI) pointing to a resource
-   that uses the <code>text/event-stream</code> format.
+   attribute, if specified, must give a valid URI (or IRI) pointing to a
+   resource that uses the <code>text/event-stream</code> format.
 
   <p>When the element is inserted into the document, if it has the <code
    title=attr-event-source-src><a href="#src11">src</a></code> attribute
@@ -25861,9 +25893,9 @@
    <dd>Invoke the <code title=dom-provider-getRowImage><a
     href="#getrowimage">getRowImage()</a></code> method with a <code><a
     href="#rowspecification">RowSpecification</a></code> object representing
-    the row in question. The return value is a string representing a URI (or
-    IRI) to an image. Relative URIs must be interpreted relative to the
-    <code><a href="#datagrid0">datagrid</a></code>'s <a href="#elements2"
+    the row in question. The return value is a string representing a valid
+    URI (or IRI) to an image. Relative URIs must be interpreted relative to
+    the <code><a href="#datagrid0">datagrid</a></code>'s <a href="#elements2"
     title="element's base URI">base URI</a>. If the method returns the empty
     string, null, or if the method is not defined, then the row has no
     associated image.
@@ -26442,7 +26474,7 @@
 
   <p>The <dfn id=icon title=attr-command-icon><code>icon</code></dfn>
    attribute gives a picture that represents the command. If the attribute is
-   specified, the attribute's value must contain a URI (or IRI).
+   specified, the attribute's value must contain a valid URI (or IRI).
 
   <p>The <dfn id=hidden title=attr-command-hidden><code>hidden</code></dfn>
    attribute is a <a href="#boolean0">boolean attribute</a> that, if present,
@@ -28960,11 +28992,12 @@
    href="#browsing1">browsing context</a> or opening and navigating an <a
    href="#auxiliary0">auxiliary browsing context</a>.
 
-  <p>The method has four arguments, though they are all optional.
+  <p>The method has four arguments, though they are all optional.</p>
+  <!-- XXXURL rfc2119 this paragraph -->
 
-  <p>The first argument, <var title="">url</var>, gives a URI (or IRI) for a
-   page to load in the browsing context. If no arguments are provided, then
-   the <var title="">url</var> argument defaults to
+  <p>The first argument, <var title="">url</var>, gives a valid URI (or IRI)
+   for a page to load in the browsing context. If no arguments are provided,
+   then the <var title="">url</var> argument defaults to
    "<code>about:blank</code><!-- XXX xref -->". The argument must be resolved
    to an absolute URI by <span class=big-issue>...</span>
 
@@ -35590,8 +35623,8 @@
    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 URI (or IRI).
-   This URI is the <em>destination resource</em> of the hyperlink.
+   attribute on a hyperlink element must have a value that is a valid URI (or
+   IRI). This URI is the <em>destination resource</em> of the hyperlink.
 
   <div class=note>
    <p>The <code title=attr-hyperlink-href><a href="#href6">href</a></code>
@@ -35729,10 +35762,11 @@
    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 <a href="#elements2">element's base URI</a>) 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.
+   URIs according to <a href="#elements2">element's base URI</a><!--
+  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>User agents should allow the user to adjust this behavior, for example
    in conjunction with a setting that disables the sending of HTTP <code
Received on Tuesday, 17 June 2008 09:21:28 GMT

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