[html5] r1779 - /
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jun 16 02:57:15 PDT 2008
Author: ianh
Date: 2008-06-16 02:57:14 -0700 (Mon, 16 Jun 2008)
New Revision: 1779
Modified:
index
source
Log:
[e] (0) minor groundwork for upcoming url overhaul
Modified: index
===================================================================
--- index 2008-06-16 07:56:50 UTC (rev 1778)
+++ index 2008-06-16 09:57:14 UTC (rev 1779)
@@ -2488,7 +2488,8 @@
<p>This specification uses the term <em>document</em> to refer to any use
of HTML, ranging from short static documents to long essays or reports
with rich multimedia, as well as to fully-fledged interactive
- applications.
+ applications.</p>
+ <!-- XXXURL -->
<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
@@ -6195,11 +6196,20 @@
</ol>
<h4 id=urls><span class=secno>3.2.9 </span>URLs</h4>
+ <!-- XXXURL -->
<div class=big-issue>
<p>This section will do the following:</p>
<ul>
+ <li>define URL as IRI and replace all uses of URIs and IRIs in the rest
+ of the spec with URL
+
+ <li>define "valid URL" in terms of valid URIs and IRIs and replace that
+ concept through the spec to a pointer here, getting rid of references to
+ <a href="#refsRFC3986">[RFC3986]</a> <a
+ href="#refsRFC3987">[RFC3987]</a> outside this section
+
<li>define how to resolve relative URLs in markup attributes (using
XMLBase as defined elsewhere right now)
@@ -6231,14 +6241,6 @@
<p>query: don't expand %-encoded bytes. Re-encode unicode to the page's
encoding. Do not percent-encode.</p>
- <li>define URL as IRI and replace all uses of URIs and IRIs in the rest
- of the spec with URL
-
- <li>define "valid URL" in terms of valid URIs and IRIs and replace that
- concept through the spec to a pointer here, getting rid of references to
- <a href="#refsRFC3986">[RFC3986]</a> <a
- href="#refsRFC3987">[RFC3987]</a> outside this section
-
<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="#refsRFC3986">[RFC3986]</a> <a
@@ -32594,7 +32596,7 @@
<p>The <dfn id=href5 title=dom-location-href><code>href</code></dfn>
attribute returns the address of the page represented by the associated
- <code>Document</code> object, as an absolute IRI reference.
+ <code>Document</code> object, as an absolute URI or IRI reference.
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
@@ -32661,7 +32663,7 @@
rules given for URI decomposition attributes, with the <a href="#input"
title=concept-uda-input>input</a> being the address of the page
represented by the associated <code>Document</code> object, as an absolute
- IRI reference (same as the <code title=dom-location-href><a
+ URI or IRI reference (same as the <code title=dom-location-href><a
href="#href5">href</a></code> attribute), and the <a href="#common3"
title=concept-uda-setter>common setter action</a> being the same as
setting the <code title=dom-location-href><a href="#href5">href</a></code>
@@ -33333,7 +33335,7 @@
href="#refsRFC3987">[RFC3987]</a>
</li>
<!-- IRI,
- ifragment? XXX -->
+ ifragment? XXXURL (refer to parsing defined in this spec) -->
<li>
<p>If <i>fragid</i> is the empty string, then the indicated part of the
Modified: source
===================================================================
--- source 2008-06-16 07:56:50 UTC (rev 1778)
+++ source 2008-06-16 09:57:14 UTC (rev 1779)
@@ -746,6 +746,7 @@
or reports with rich multimedia, as well as to fully-fledged
interactive applications.</p>
+ <!-- XXXURL -->
<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 respectively. On the rare occasions where IRIs are not allowed
@@ -4653,7 +4654,7 @@
</ol>
- <h4>URLs</h4>
+ <h4>URLs</h4><!-- XXXURL -->
<div class="big-issue">
@@ -4661,6 +4662,14 @@
<ul>
+ <li>define URL as IRI and replace all uses of URIs and IRIs in the
+ rest of the spec with URL</li>
+
+ <li>define "valid URL" in terms of valid URIs and IRIs and replace
+ that concept through the spec to a pointer here, getting rid of
+ references to <a href="#refsRFC3986">[RFC3986]</a> <a
+ href="#refsRFC3987">[RFC3987]</a> outside this section</li>
+
<li>define how to resolve relative URLs in markup attributes
(using XMLBase as defined elsewhere right now)</li>
@@ -4687,14 +4696,6 @@
</li>
- <li>define URL as IRI and replace all uses of URIs and IRIs in the
- rest of the spec with URL</li>
-
- <li>define "valid URL" in terms of valid URIs and IRIs and replace
- that concept through the spec to a pointer here, getting rid of
- references to <a href="#refsRFC3986">[RFC3986]</a> <a
- href="#refsRFC3987">[RFC3987]</a> outside this section</li>
-
<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
@@ -30383,7 +30384,7 @@
<p>The <dfn title="dom-location-href"><code>href</code></dfn>
attribute returns the address of the page represented by the
- associated <code>Document</code> object, as an absolute IRI
+ associated <code>Document</code> object, as an absolute URI or IRI
reference.</p>
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
@@ -30445,11 +30446,11 @@
the rules given for URI decomposition attributes, with the <span
title="concept-uda-input">input</span> being the address of the page
represented by the associated <code>Document</code> object, as an
- absolute IRI reference (same as the <code
+ absolute URI or IRI reference (same as the <code
title="dom-location-href">href</code> attribute), and the <span
- title="concept-uda-setter">common setter action</span> being the same
- as setting the <code title="dom-location-href">href</code> attribute
- to the new output value.</p>
+ title="concept-uda-setter">common setter action</span> being the
+ same as setting the <code title="dom-location-href">href</code>
+ attribute to the new output value.</p>
<!--
<dfn title="dom-location-reload"><code>reload()</code></dfn>
@@ -31131,7 +31132,7 @@
<li><p>Let <i>fragid</i> be the <fragment> part of the
URI. <a href="#refsRFC3987">[RFC3987]</a></p></li> <!-- IRI,
- ifragment? XXX -->
+ ifragment? XXXURL (refer to parsing defined in this spec) -->
<li><p>If <i>fragid</i> is the empty string, then the indicated
part of the document is the top of the document.</p></li>
More information about the Commit-Watchers
mailing list