- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 06 Jun 2008 02:05:52 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20896
Modified Files:
Overview.html
Log Message:
Many editorial changes around the word 'base', from refering to RFC3986 more directly, to changing 'base ten integer' to 'base-ten integer' (whatwg r1726)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.914
retrieving revision 1.915
diff -u -d -r1.914 -r1.915
--- Overview.html 5 Jun 2008 23:57:22 -0000 1.914
+++ Overview.html 6 Jun 2008 02:05:49 -0000 1.915
@@ -59,7 +59,7 @@
for HTML and XHTML</h2>
<h2 class="no-num no-toc" id=w3c-working>W3C Working Draft
- <!--ZZZ 5 June 2008-->9 June 2008</h2>
+ <!--ZZZ 6 June 2008-->9 June 2008</h2>
<dl><!-- ZZZ: replace '20080609' with '[CDATA]' -->
@@ -199,7 +199,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
- <!-- ZZZ 5 June 2008 --> 9 June 2008 Working Draft. <!--:ZZZ--></p>
+ <!-- ZZZ 6 June 2008 --> 9 June 2008 Working Draft. <!--:ZZZ--></p>
<!-- relationship to other work (required) -->
<p>This specification is also being produced by the <a
@@ -5441,7 +5441,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>
@@ -5454,7 +5454,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
@@ -5474,7 +5474,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>
@@ -5493,7 +5493,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
@@ -5509,7 +5509,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
@@ -5550,7 +5550,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.
@@ -5601,7 +5601,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
@@ -5621,7 +5621,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
@@ -5731,8 +5731,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
@@ -5751,7 +5751,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
@@ -5782,7 +5782,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
@@ -5836,8 +5836,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
@@ -5863,8 +5863,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
@@ -5897,7 +5897,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>
@@ -5972,7 +5972,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>.
@@ -6000,7 +6000,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>.
@@ -6274,7 +6274,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
@@ -6298,6 +6299,13 @@
href="#references">[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>
@@ -7655,9 +7663,12 @@
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>
@@ -8093,12 +8104,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="#references">[RFC2616]</a> <a href="#references">[RFC2068]</a>
@@ -8643,7 +8653,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>
@@ -25900,9 +25911,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
@@ -27234,11 +27246,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>
@@ -27443,9 +27455,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
@@ -31411,9 +31424,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="#references">[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="#references">[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,
@@ -32778,10 +32792,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
@@ -33249,7 +33264,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
@@ -35754,10 +35770,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
@@ -41377,7 +41393,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>
@@ -41474,7 +41490,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.
@@ -41557,7 +41573,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
@@ -41566,7 +41582,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
@@ -45985,11 +46001,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="#references">[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>
Received on Friday, 6 June 2008 02:06:27 UTC