[html5] r1817 - [e] (0) fix references to RFCs 3986 and 7
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jun 27 01:14:04 PDT 2008
Author: ianh
Date: 2008-06-27 01:14:03 -0700 (Fri, 27 Jun 2008)
New Revision: 1817
Modified:
index
source
Log:
[e] (0) fix references to RFCs 3986 and 7
Modified: index
===================================================================
--- index 2008-06-27 08:03:36 UTC (rev 1816)
+++ index 2008-06-27 08:14:03 UTC (rev 1817)
@@ -2763,7 +2763,8 @@
<p>If <var title="">url</var> doesn't match the <URI-reference>
production, even after the above changes are made to the ABNF definitions,
- then parsing the URL fails with an error.
+ then parsing the URL fails with an error. <a
+ href="#refsRFC3986">[RFC3986]</a>
<p>If parsing <var title="">url</var> was successful, then the components
of the URL are substrings of <var title="">url</var> defined as follows:
@@ -2952,6 +2953,7 @@
<li>Encode the character into a sequence of octets as defined by UTF-8.
<li>Replace the character with the percent-encoded form of those octets.
+ <a href="#refsRFC3986">[RFC3986]</a>
</ol>
<div class=example>
@@ -2978,17 +2980,20 @@
encoding <var title="">encoding</var>.
<li>Replace the character with the percent-encoded form of those octets.
+ <a href="#refsRFC3986">[RFC3986]</a>
</ol>
<li>
<p>Apply the algorithm described in RFC 3986 section 5.2 Relative
Resolution, using <var title="">url</var> as the potentially relative
URI reference (<var title="">R</var>), and <var title="">base</var> as
- the base URI (<var title="">Base</var>).
+ the base URI (<var title="">Base</var>). <a
+ href="#refsRFC3986">[RFC3986]</a>
<li>
<p>Apply any relevant conformance criteria of RFC 3986 and RFC 3987,
- returning an error and aborting these steps if appropriate.</p>
+ returning an error and aborting these steps if appropriate. <a
+ href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a></p>
<p class=example>For instance, if an absolute URI that would be returned
by the above algorithm violates the restrictions specific to its scheme,
@@ -3012,11 +3017,6 @@
<p>This section will do the following:</p>
<ul>
- <li>replace all uses of URIs and IRIs in the rest of the spec with URL
-
- <li>get rid of references to <a href="#refsRFC3986">[RFC3986]</a> <a
- href="#refsRFC3987">[RFC3987]</a> outside this section
-
<li>make the language used to refer to resolving a base URI consistent
throughout, maybe make it hyperlink to a definition each time
@@ -32009,7 +32009,8 @@
user agent must <a href="#resolve" title="resolve a URL">resolve</a> the
URL, and then every character in the URL that doesn't match the
<query> production defined in RFC 3986 must be replaced by the
- percent-encoded form of the character.</p>
+ percent-encoded form of the character. <a
+ href="#refsRFC3986">[RFC3986]</a></p>
<div class=example>
<p>If the user had visited a site at <code
@@ -41933,8 +41934,7 @@
single U+002A ASTERISK character ("*"), and <a href="#parse0"
title="parse a url">parsing</a> it as a <a href="#url">URL</a> fails,
then throw a <code>SYNTAX_ERR</code> exception and abort the overall set
- of steps. <a href="#refsRFC3490">[RFC3986]</a> <a
- href="#refsRFC3490">[RFC3987]</a></p>
+ of steps.</p>
<li>
<p>Return from the <code title=dom-window-postMessage><a
@@ -46684,7 +46684,7 @@
Otherwise, if there is no such attribute or resolving it fails, run the
<a href="#application3"
title=concept-appcache-init-no-attribute>application cache selection
- algorithm</a> with no manifest. <a href="#refsRFC3986">[RFC3986]</a></p>
+ algorithm</a> with no manifest.</p>
<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-27 08:03:36 UTC (rev 1816)
+++ source 2008-06-27 08:14:03 UTC (rev 1817)
@@ -1016,7 +1016,7 @@
<p>If <var title="">url</var> doesn't match the
<URI-reference> production, even after the above changes are
made to the ABNF definitions, then parsing the URL fails with an
- error.</p>
+ error. <a href="#refsRFC3986">[RFC3986]</a></p>
<p>If parsing <var title="">url</var> was successful, then the
components of the URL are substrings of <var title="">url</var>
@@ -1216,7 +1216,7 @@
UTF-8.</li>
<li>Replace the character with the percent-encoded form of those
- octets.</li>
+ octets. <a href="#refsRFC3986">[RFC3986]</a></li>
</ol>
@@ -1251,7 +1251,7 @@
the encoding <var title="">encoding</var>.</li>
<li>Replace the character with the percent-encoded form of those
- octets.</li>
+ octets. <a href="#refsRFC3986">[RFC3986]</a></li>
</ol>
@@ -1261,13 +1261,14 @@
Relative Resolution, using <var title="">url</var> as the
potentially relative URI reference (<var title="">R</var>), and
<var title="">base</var> as the base URI (<var
- title="">Base</var>).</p></li>
+ title="">Base</var>). <a href="#refsRFC3986">[RFC3986]</a></p></li>
<li>
<p>Apply any relevant conformance criteria of RFC 3986 and RFC
3987, returning an error and aborting these steps if
- appropriate.</p>
+ appropriate. <a href="#refsRFC3986">[RFC3986]</a> <a
+ href="#refsRFC3987">[RFC3987]</a></p>
<p class="example">For instance, if an absolute URI that would be
returned by the above algorithm violates the restrictions specific
@@ -1294,12 +1295,6 @@
<ul>
- <li>replace all uses of URIs and IRIs in the rest of the spec with
- URL</li>
-
- <li>get rid of references to <a href="#refsRFC3986">[RFC3986]</a>
- <a href="#refsRFC3987">[RFC3987]</a> outside this section</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>
@@ -29640,7 +29635,7 @@
URL">resolve</span> the URL, and then every character in the URL
that doesn't match the <query> production defined in RFC
3986 must be replaced by the percent-encoded form of the
- character.</p>
+ character. <a href="#refsRFC3986">[RFC3986]</a></p>
<div class="example">
@@ -39539,8 +39534,7 @@
is not a single U+002A ASTERISK character ("*"), and <span
title="parse a url">parsing</span> it as a <span>URL</span> fails,
then throw a <code>SYNTAX_ERR</code> exception and abort the
- overall set of steps. <a href="#refsRFC3490">[RFC3986]</a> <a
- href="#refsRFC3490">[RFC3987]</a></p>
+ overall set of steps.</p>
</li>
@@ -43798,8 +43792,7 @@
URL</span>. Otherwise, if there is no such attribute or resolving
it fails, run the <span
title="concept-appcache-init-no-attribute">application cache
- selection algorithm</span> with no manifest. <a
- href="#refsRFC3986">[RFC3986]</a></p>
+ selection algorithm</span> with no manifest.</p>
<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