[html5] r1726 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jun 5 19:05:15 PDT 2008
Author: ianh
Date: 2008-06-05 19:05:15 -0700 (Thu, 05 Jun 2008)
New Revision: 1726
Modified:
index
source
Log:
[e] (0) Many editorial changes around the word 'base', from refering to RFC3986 more directly, to changing 'base ten integer' to 'base-ten integer'
Modified: index
===================================================================
--- index 2008-06-05 23:57:18 UTC (rev 1725)
+++ index 2008-06-06 02:05:15 UTC (rev 1726)
@@ -25,7 +25,7 @@
<h1 id=html-5>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft>Draft Recommendation — 5 June
+ <h2 class="no-num no-toc" id=draft>Draft Recommendation — 6 June
2008</h2>
<p>You can take part in this work. <a
@@ -5350,7 +5350,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly four characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that number
+ interpret the resulting sequence as a base-ten integer. Let that number
be the <var title="">year</var>.
<li>
@@ -5363,7 +5363,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that number
+ interpret the resulting sequence as a base-ten integer. Let that number
be the <var title="">month</var>.
<li>If <var title="">month</var> is not a number in the range
@@ -5383,7 +5383,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that number
+ interpret the resulting sequence as a base-ten integer. Let that number
be the <var title="">day</var>.
<li>
@@ -5402,7 +5402,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that number
+ interpret the resulting sequence as a base-ten integer. Let that number
be the <var title="">hour</var>.
<li>If <var title="">hour</var> is not a number in the range
@@ -5418,7 +5418,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that number
+ interpret the resulting sequence as a base-ten integer. Let that number
be the <var title="">minute</var>.
<li>If <var title="">minute</var> is not a number in the range
@@ -5459,7 +5459,7 @@
</ol>
<li>
- <p>Interpret <var title="">second</var> as a base ten number (possibly
+ <p>Interpret <var title="">second</var> as a base-ten number (possibly
with a fractional part). Let that number be <var title="">second</var>
instead of the string version.
@@ -5510,7 +5510,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">timezone<sub title="">hours</sub></var>.
<li>If <var title="">timezone<sub title="">hours</sub></var> is not a
@@ -5530,7 +5530,7 @@
<p><a href="#collect">Collect a sequence of characters</a> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">timezone<sub title="">minutes</sub></var>.
<li>If <var title="">timezone<sub title="">minutes</sub></var> is not a
@@ -5640,8 +5640,8 @@
however.)
<li>
- <p>Interpret the sequence of characters collected in step 5 as a base
- ten integer, and let that number be <var title="">year</var>.
+ <p>Interpret the sequence of characters collected in step 5 as a
+ base-ten integer, and let that number be <var title="">year</var>.
<li>
<p>Advance <var title="">position</var> past the U+002D HYPHEN-MINUS
@@ -5660,7 +5660,7 @@
<li>
<p>Interpret the sequence of characters collected two steps ago as a
- base ten integer, and let that number be <var title="">month</var>.
+ base-ten integer, and let that number be <var title="">month</var>.
<li>If <var title="">month</var> is not a number in the range
1 ≤ <var title="">month</var> ≤ 12, then the
@@ -5691,7 +5691,7 @@
<li>
<p>Interpret the sequence of characters collected two steps ago as a
- base ten integer, and let that number be <var title="">day</var>.
+ base-ten integer, and let that number be <var title="">day</var>.
<li>
<p>If <var title="">day</var> is not a number in the range
@@ -5745,8 +5745,8 @@
string is invalid.
<li>
- <p>Interpret the sequence of characters collected two steps ago as a base
- ten integer, and let that number be <var title="">hour</var>.
+ <p>Interpret the sequence of characters collected two steps ago as a
+ base-ten integer, and let that number be <var title="">hour</var>.
<li>
<p>If <var title="">hour</var> is not a number in the range
@@ -5772,8 +5772,8 @@
long, then the string is invalid.
<li>
- <p>Interpret the sequence of characters collected two steps ago as a base
- ten integer, and let that number be <var title="">minute</var>.
+ <p>Interpret the sequence of characters collected two steps ago as a
+ base-ten integer, and let that number be <var title="">minute</var>.
<li>
<p>If <var title="">minute</var> is not a number in the range
@@ -5806,7 +5806,7 @@
<li>
<p>Interpret the sequence of characters collected two steps ago as a
- base ten number (possibly with a fractional part), and let that number
+ base-ten number (possibly with a fractional part), and let that number
be <var title="">second</var>.
<li>
@@ -5881,7 +5881,7 @@
string is invalid.
<li>
- <p>Interpret the sequence collected in the last step as a base ten
+ <p>Interpret the sequence collected in the last step as a base-ten
number, and let that number be <var title="">timezone<sub
title="">hours</sub></var>.
@@ -5909,7 +5909,7 @@
string is invalid.
<li>
- <p>Interpret the sequence collected in the last step as a base ten
+ <p>Interpret the sequence collected in the last step as a base-ten
number, and let that number be <var title="">timezone<sub
title="">minutes</sub></var>.
@@ -6183,7 +6183,8 @@
<li>define how to resolve relative URLs in markup attributes (using
XMLBase as defined elsewhere right now)
- <li>define how to resolve relative URLs in APIs
+ <li>define 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
@@ -6207,6 +6208,13 @@
href="#refsRFC3987">[RFC3987]</a>
<li>define how to parse URLs (maybe by deferring to RFCs)
+
+ <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
+ use that definition
+
+ <li>make the language used to refer to resolving a base URI consistent
+ throughout, maybe make it hyperlink to a definition each time
</ul>
</div>
@@ -7564,10 +7572,13 @@
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). Furthermore, as it is processed before any <code><a
- href="#base">base</a></code> elements are seen, its value is not subject
- to being made relative to any base URI.
+ for this attribute).
+ <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
+ href="#manifest">manifest</a></code> attributes, as the attributes are
+ processed before those elements are seen.
+
<h3 id=document><span class=secno>3.7 </span>Document metadata</h3>
<h4 id=the-head><span class=secno>3.7.1 </span>The <dfn
@@ -8002,12 +8013,11 @@
<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>
- elements. When processing links, those must be taken into consideration as
- well. For the purposes of ordering, links defined by HTTP headers must be
- assumed to come before any links in the document, in the order that they
- were given in the HTTP entity header. Relative URIs in these headers must
- be resolved according to the rules given in HTTP, not relative to base
- URIs set by the document (e.g. using a <code><a
+ elements. If supported, for the purposes of ordering links defined by HTTP
+ headers must be assumed to come before any links in the document, in the
+ order that they were given in the HTTP entity header. Relative URIs in
+ these headers are resolved according to the rules given in HTTP, not
+ relative to base URIs set by the document (e.g. using a <code><a
href="#base">base</a></code> element or <code
title=attr-xml-base>xml:base</code> attributes). <a
href="#refsRFC2616">[RFC2616]</a> <a href="#refsRFC2068">[RFC2068]</a>
@@ -8552,7 +8562,8 @@
<li>
<p>Resolve the <var title="">url</var> value to an absolute URI using
- the base URI of the <code><a href="#meta0">meta</a></code> element.
+ <a href="#elements2" title="element's base URI">the base URI</a> of
+ the <code><a href="#meta0">meta</a></code> element.
<li>
<p>Perform one or more of the following steps:</p>
@@ -25809,9 +25820,10 @@
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 base URI. If the method
- returns the empty string, null, or if the method is not defined, then the
- row has no associated image.
+ <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.
<dt>To obtain a context menu appropriate for a particular row
@@ -27143,11 +27155,11 @@
from the element's <code>src</code> attribute. <!--If it is
an <code>object</code> element then the URI is taken from the
<code>data</code> attribute. -->
- Relative URIs must be resolved relative to the base URI of the image
- element. <!-- If it is an
- <code>svg</code> element then the URI is formed by taking the URI of
- the document and appending a "#" (U+0023 NUMBER SIGN) and the ID of
- the element.-->
+ Relative URIs must be resolved relative to the <a href="#elements2"
+ title="element's base URI">base URI</a> of the image element.
+ <!-- If it is an <code>svg</code> element then
+ the URI is formed by taking the URI of the document and appending a
+ "#" (U+0023 NUMBER SIGN) and the ID of the element.-->
If no image is found, then the Icon facet is left blank.
<p>The <a href="#hidden1" title=command-facet-HiddenState>Hidden State</a>
@@ -27352,9 +27364,10 @@
<p>The <a href="#icon1" title=command-facet-Icon>Icon</a> for the command
is the absolute URI resulting from resolving the value of the element's
<code title=attr-command-icon><a href="#icon">icon</a></code> attribute as
- a URI relative to the element's base URI. If the element has no <code
- title=attr-command-icon><a href="#icon">icon</a></code> attribute then the
- command has no <a href="#icon1" title=command-facet-Icon>Icon</a>.
+ a URI relative to the <a href="#elements2">element's base URI</a>. If the
+ element has no <code title=attr-command-icon><a
+ href="#icon">icon</a></code> attribute then the command has no <a
+ href="#icon1" title=command-facet-Icon>Icon</a>.
<p>The <a href="#hidden1" title=command-facet-HiddenState>Hidden State</a>
of the command is true (hidden) if the element has a <code
@@ -31320,9 +31333,10 @@
</ol>
<p>Relative URI references and IRI references resolved to absolute URIs or
- IRIs in the above algorithm must use the manifest's URI as the Base URI
- from the Retrieval URI for the purposes reference resolution as defined by
- RFC 3986. <a href="#refsRFC3986">[RFC3986]</a>
+ IRIs in the above algorithm must be resolved according to section 5.1 of
+ RFC3986 (i.e. relative to the base URI from the encapsulating entity or
+ the URI used to retrieve the entity, since there is no way to embed a base
+ URI in the manifest itself). <a href="#refsRFC3986">[RFC3986]</a>
<p class=note>If a resource is listed in both the online whitelist and in
the explicit section, then that resource will be downloaded and cached,
@@ -32687,10 +32701,11 @@
<p>Relative <var title="">url</var> arguments for <code
title=dom-location-assign><a href="#assign">assign()</a></code> and <code
title=dom-location-replace><a href="#replace">replace()</a></code> must be
- resolved relative to the base URI of the script that made the method call.</p>
- <!-- XXX what about if the base URI is data: or
- javascript: or about: or something else without a way to resolve
- base URIs? -->
+ resolved relative to the <a href="#scripts0" title="script's base
+ URI">base URI of the script</a> that made the method call.</p>
+ <!-- XXX what about if
+ the base URI is data: or javascript: or about: or something else
+ without a way to resolve base URIs? -->
<p>The <code><a href="#location2">Location</a></code> interface also has
the complement of <a href="#uri-decomposition">URI decomposition
@@ -33158,7 +33173,8 @@
href="#manifest">manifest</a></code>, then, as soon as the element is
inserted into the DOM, the user agent must run the <a href="#application2"
title=concept-appcache-init-with-attribute>application cache selection
- algorithm</a> with the value of that attribute as the manifest URI.
+ algorithm</a> with the value of that attribute, resolved relative to the
+ <a href="#elements2">element's base URI</a>, as the manifest URI.
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
@@ -35663,10 +35679,10 @@
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 element's base URI) 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>) 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
@@ -41286,7 +41302,7 @@
and <a href="#space" title="space character">space characters</a>.
<li>The root element, in the form of an <code><a
- href="#html">html</a></code> <a href="#elements2"
+ href="#html">html</a></code> <a href="#elements3"
title=syntax-elements>element</a>.
<li>Any number of <a href="#comments0" title=syntax-comments>comments</a>
@@ -41383,7 +41399,7 @@
<h4 id=elements0><span class=secno>8.1.2 </span>Elements</h4>
- <p>There are five different kinds of <dfn id=elements2
+ <p>There are five different kinds of <dfn id=elements3
title=syntax-elements>elements</dfn>: void elements, CDATA elements,
RCDATA elements, foreign elements, and normal elements.
@@ -41466,7 +41482,7 @@
is <em>not</em> marked as self-closing can have <a href="#text2"
title=syntax-text>text</a>, <a href="#character3"
title=syntax-charref>character references</a>, <a href="#cdata0"
- title=syntax-cdata>CDATA blocks</a>, other <a href="#elements2"
+ title=syntax-cdata>CDATA blocks</a>, other <a href="#elements3"
title=syntax-elements>elements</a>, and <a href="#comments0"
title=syntax-comments>comments</a>, but the text must not contain the
character U+003C LESS-THAN SIGN (<code><</code>) or an <a
@@ -41475,7 +41491,7 @@
<p>Normal elements can have <a href="#text2" title=syntax-text>text</a>, <a
href="#character3" title=syntax-charref>character references</a>, other <a
- href="#elements2" title=syntax-elements>elements</a>, and <a
+ href="#elements3" title=syntax-elements>elements</a>, and <a
href="#comments0" title=syntax-comments>comments</a>, but the text must
not contain the character U+003C LESS-THAN SIGN (<code><</code>) or an
<a href="#ambiguous" title=syntax-ambiguous-ampersand>ambiguous
@@ -45894,11 +45910,17 @@
<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
- algorithm</a> with the value of that attribute as the manifest URI.
+ algorithm</a> with the value of that attribute as the manifest URI,
+ resolving relative URIs according to section 5.1 of RFC3986 as if there
+ was no base URI embedded in content (i.e. relative to the base URI from
+ the encapsulating entity or the URI used to retrieve the entity).
Otherwise, run the <a href="#application3"
title=concept-appcache-init-no-attribute>application cache selection
- algorithm</a> with no manifest.</p>
-
+ algorithm</a> with no manifest. <a href="#refsRFC3986">[RFC3986]</a></p>
+ <!-- XXX when dealing with
+ microsyntaxes-urls, hoist all this into that section so we can get
+ rid of "URI" here -->
+
<p>Switch the <span>insertion mode</span> to "<a href="#before5"
title="insertion mode: before head">before head</a>".</p>
Modified: source
===================================================================
--- source 2008-06-05 23:57:18 UTC (rev 1725)
+++ source 2008-06-06 02:05:15 UTC (rev 1726)
@@ -3835,7 +3835,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly four characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">year</var>.</p></li>
<li><p>If <var title="">position</var> is beyond the end of <var
@@ -3847,7 +3847,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">month</var>.</p></li>
<li>If <var title="">month</var> is not a number in the range
@@ -3866,7 +3866,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">day</var>.</p></li>
<li><p>If <var title="">day</var> is not a number in the range
@@ -3882,7 +3882,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">hour</var>.</p></li>
<li>If <var title="">hour</var> is not a number in the range
@@ -3897,7 +3897,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then fail. Otherwise,
- interpret the resulting sequence as a base ten integer. Let that
+ interpret the resulting sequence as a base-ten integer. Let that
number be the <var title="">minute</var>.</p></li>
<li>If <var title="">minute</var> is not a number in the range
@@ -3937,7 +3937,7 @@
</li>
- <li><p>Interpret <var title="">second</var> as a base ten number
+ <li><p>Interpret <var title="">second</var> as a base-ten number
(possibly with a fractional part). Let that number be <var
title="">second</var> instead of the string version.</p></li>
@@ -3986,7 +3986,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then
- fail. Otherwise, interpret the resulting sequence as a base ten
+ fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the <var
title="">timezone<sub title="">hours</sub></var>.</p></li>
@@ -4007,7 +4007,7 @@
<li><p><span>Collect a sequence of characters</span> in the range
U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9). If the collected
sequence is not exactly two characters long, then
- fail. Otherwise, interpret the resulting sequence as a base ten
+ fail. Otherwise, interpret the resulting sequence as a base-ten
integer. Let that number be the <var
title="">timezone<sub title="">minutes</sub></var>.</p></li>
@@ -4116,7 +4116,7 @@
algorithm, however.)</p></li>
<li><p>Interpret the sequence of characters collected in step 5 as
- a base ten integer, and let that number be <var
+ a base-ten integer, and let that number be <var
title="">year</var>.</p></li>
<li><p>Advance <var title="">position</var> past the U+002D
@@ -4132,7 +4132,7 @@
two digits long, then the string is invalid.</p></li>
<li><p>Interpret the sequence of characters collected two steps ago
- as a base ten integer, and let that number be <var
+ as a base-ten integer, and let that number be <var
title="">month</var>.</p></li>
<li>If <var title="">month</var> is not a number in the range
@@ -4160,7 +4160,7 @@
two digits long, then the string is invalid.</p></li>
<li><p>Interpret the sequence of characters collected two steps
- ago as a base ten integer, and let that number be <var
+ ago as a base-ten integer, and let that number be <var
title="">day</var>.</p></li>
<li><p>If <var title="">day</var> is not a number in the range
@@ -4212,7 +4212,7 @@
then the string is invalid.</p></li>
<li><p>Interpret the sequence of characters collected two steps
- ago as a base ten integer, and let that number be <var
+ ago as a base-ten integer, and let that number be <var
title="">hour</var>.</p></li>
<li><p>If <var title="">hour</var> is not a number in the range
@@ -4235,7 +4235,7 @@
two digits long, then the string is invalid.</p></li>
<li><p>Interpret the sequence of characters collected two steps
- ago as a base ten integer, and let that number be <var
+ ago as a base-ten integer, and let that number be <var
title="">minute</var>.</p></li>
<li><p>If <var title="">minute</var> is not a number in the range
@@ -4263,7 +4263,7 @@
DIGIT NINE (9), then the string is invalid.</p></li>
<li><p>Interpret the sequence of characters collected two steps
- ago as a base ten number (possibly with a fractional part), and
+ ago as a base-ten number (possibly with a fractional part), and
let that number be <var title="">second</var>.</p></li>
<li><p>If <var title="">second</var> is not a number in the range
@@ -4336,7 +4336,7 @@
the string is invalid.</p></li>
<li><p>Interpret the sequence collected in the last step as a
- base ten number, and let that number be <var
+ base-ten number, and let that number be <var
title="">timezone<sub title="">hours</sub></var>.</p></li>
<li>If <var title="">timezone<sub title="">hours</sub></var> is not a
@@ -4359,7 +4359,7 @@
sequence is not exactly two characters long, then the string is invalid.</p></li>
<li><p>Interpret the sequence collected in the last step as a
- base ten number, and let that number be <var
+ base-ten number, and let that number be <var
title="">timezone<sub title="">minutes</sub></var>.</p></li>
<li>If <var title="">timezone<sub title="">minutes</sub></var> is not a
@@ -4646,7 +4646,8 @@
<li>define how to resolve relative URLs in markup attributes
(using XMLBase as defined elsewhere right now)</li>
- <li>define how to resolve relative URLs in APIs</li>
+ <li>define how to resolve relative URLs in APIs, using the
+ <dfn>script's base URI</dfn> maybe</li>
<li>define what it means to resolve a relative URL when the base
URL doesn't have a path hierarchy (e.g. data:, javascript:,
@@ -4672,6 +4673,14 @@
<li>define how to parse URLs (maybe by deferring to RFCs)</li>
+ <li>define "an <dfn>element's base URI</dfn>" and make the various
+ places that talk about a base URI in the context of an element use
+ that definition</li>
+
+ <li>make the language used to refer to resolving a base URI
+ consistent throughout, maybe make it hyperlink to a definition
+ each time</li>
+
</ul>
</div>
@@ -6034,11 +6043,14 @@
only <span title="concept-appcache-init-with-attribute">has an
effect</span> 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). Furthermore, as it is processed before
- any <code>base</code> elements are seen, its value is not subject to
- being made relative to any base URI.</p>
+ provided for this attribute).</p>
+ <p class="note">Later <code>base</code> elements can't affect the
+ resolving of relative URIs in <code
+ title="attr-html-manifest">manifest</code> attributes, as the
+ attributes are processed before those elements are seen.</p>
+
<h3>Document metadata</h3>
<h4>The <dfn><code>head</code></dfn> element</h4>
@@ -6423,11 +6435,10 @@
<p>Some versions of HTTP defined a <code title="">Link:</code>
header, to be processed like a series of <code>link</code> elements.
- When processing links, those must be taken into consideration as
- well. For the purposes of ordering, links defined by HTTP headers
- must be assumed to come before any links in the document, in the
- order that they were given in the HTTP entity header. Relative URIs
- in these headers must be resolved according to the rules given in
+ If supported, for the purposes of ordering links defined by HTTP
+ headers must be assumed to come before any links in the document, in
+ the order that they were given in the HTTP entity header. Relative
+ URIs in these headers are resolved according to the rules given in
HTTP, 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). <a
@@ -6931,7 +6942,8 @@
title="">url</var>.</p></li>
<li><p>Resolve the <var title="">url</var> value to an absolute
- URI using the base URI of the <code>meta</code> element.</p></li>
+ URI using <span title="element's base URI">the base URI</span> of
+ the <code>meta</code> element.</p></li>
<li>
@@ -23575,9 +23587,9 @@
<code>RowSpecification</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>datagrid</code>'s base URI. If the method returns the empty
- string, null, or if the method is not defined, then the row has no
- associated image.</dd>
+ <code>datagrid</code>'s <span title="element's base URI">base
+ URI</span>. If the method returns the empty string, null, or if the
+ method is not defined, then the row has no associated image.</dd>
<dt>To obtain a context menu appropriate for a particular row</dt>
@@ -24862,11 +24874,11 @@
be taken from the element's <code>src</code> attribute. <!--If it is
an <code>object</code> element then the URI is taken from the
<code>data</code> attribute. --> Relative URIs must be resolved
- relative to the base URI of the image element. <!-- If it is an
- <code>svg</code> element then the URI is formed by taking the URI of
- the document and appending a "#" (U+0023 NUMBER SIGN) and the ID of
- the element.--> If no image is found, then the Icon facet is left
- blank.</p>
+ relative to the <span title="element's base URI">base URI</span> of
+ the image element. <!-- If it is an <code>svg</code> element then
+ the URI is formed by taking the URI of the document and appending a
+ "#" (U+0023 NUMBER SIGN) and the ID of the element.--> If no image
+ is found, then the Icon facet is left blank.</p>
<p>The <span title="command-facet-HiddenState">Hidden State</span>
and <span title="command-facet-DisabledState">Disabled State</span>
@@ -25071,9 +25083,9 @@
<p>The <span title="command-facet-Icon">Icon</span> for the command
is the absolute URI resulting from resolving the value of the
element's <code title="attr-command-icon">icon</code> attribute as a
- URI relative to the element's base URI. If the element has no <code
- title="attr-command-icon">icon</code> attribute then the command has
- no <span title="command-facet-Icon">Icon</span>.</p>
+ URI relative to the <span>element's base URI</span>. If the element
+ has no <code title="attr-command-icon">icon</code> attribute then
+ the command has no <span title="command-facet-Icon">Icon</span>.</p>
<p>The <span title="command-facet-HiddenState">Hidden State</span>
of the command is true (hidden) if the element has a <code
@@ -29176,9 +29188,10 @@
</ol>
<p>Relative URI references and IRI references resolved to absolute
- URIs or IRIs in the above algorithm must use the manifest's URI as
- the Base URI from the Retrieval URI for the purposes reference
- resolution as defined by RFC 3986. <a
+ URIs or IRIs in the above algorithm must be resolved according to
+ section 5.1 of RFC3986 (i.e. relative to the base URI from the
+ encapsulating entity or the URI used to retrieve the entity, since
+ there is no way to embed a base URI in the manifest itself). <a
href="#refsRFC3986">[RFC3986]</a></p>
<p class="note">If a resource is listed in both the online whitelist
@@ -30545,10 +30558,10 @@
<p>Relative <var title="">url</var> arguments for <code
title="dom-location-assign">assign()</code> and <code
title="dom-location-replace">replace()</code> must be resolved
- relative to the base URI of the script that made the method
- call.</p> <!-- XXX what about if the base URI is data: or
- javascript: or about: or something else without a way to resolve
- base URIs? -->
+ relative to the <span title="script's base URI">base URI of the
+ script</span> that made the method call.</p> <!-- XXX what about if
+ the base URI is data: or javascript: or about: or something else
+ without a way to resolve base URIs? -->
<p>The <code>Location</code> interface also has the complement of
<span>URI decomposition attributes</span>, <dfn
@@ -31030,10 +31043,11 @@
<p>If the root element, as parsed according to the XML
specifications cited above, is found to be an <code>html</code>
element with an attribute <code
- title="attr-html-manifest">manifest</code>, then, as soon as
- the element is inserted into the DOM, the user agent must run the
- <span title="concept-appcache-init-with-attribute">application cache
- selection algorithm</span> with the value of that attribute as the
+ title="attr-html-manifest">manifest</code>, then, as soon as the
+ element is inserted into the DOM, the user agent must run the <span
+ title="concept-appcache-init-with-attribute">application cache
+ selection algorithm</span> with the value of that attribute,
+ resolved relative to the <span>element's base URI</span>, as the
manifest URI. Otherwise, as soon as the root element is inserted
into the DOM, the user agent must run the <span
title="concept-appcache-init-no-attribute">application cache
@@ -33490,10 +33504,10 @@
title="attr-hyperlink-ping">ping</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 element's base URI) 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>
+ relative URIs according to <span>element's base URI</span>) 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>
<p>User agents should allow the user to adjust this behavior, for
example in conjunction with a setting that disables the sending of
@@ -42993,9 +43007,15 @@
then run the <span
title="concept-appcache-init-with-attribute">application cache
selection algorithm</span> with the value of that attribute as the
- manifest URI. Otherwise, run the <span
+ manifest URI, resolving relative URIs according to section 5.1 of
+ RFC3986 as if there was no base URI embedded in content
+ (i.e. relative to the base URI from the encapsulating entity or
+ the URI used to retrieve the entity). Otherwise, run the <span
title="concept-appcache-init-no-attribute">application cache
- selection algorithm</span> with no manifest.</p>
+ selection algorithm</span> with no manifest. <a
+ href="#refsRFC3986">[RFC3986]</a></p><!-- XXX when dealing with
+ microsyntaxes-urls, hoist all this into that section so we can get
+ rid of "URI" here -->
<p>Switch the <span>insertion mode</span> to "<span
title="insertion mode: before head">before head</span>".</p>
More information about the Commit-Watchers
mailing list