- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 27 Jun 2008 08:14:40 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv17410 Modified Files: Overview.html Log Message: fix references to RFCs 3986 and 7 (whatwg r1817) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1005 retrieving revision 1.1006 diff -u -d -r1.1005 -r1.1006 --- Overview.html 27 Jun 2008 08:04:11 -0000 1.1005 +++ Overview.html 27 Jun 2008 08:14:38 -0000 1.1006 @@ -2867,7 +2867,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="#references">[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: @@ -3056,6 +3057,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="#references">[RFC3986]</a> </ol> <div class=example> @@ -3082,17 +3084,20 @@ encoding <var title="">encoding</var>. <li>Replace the character with the percent-encoded form of those octets. + <a href="#references">[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="#references">[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="#references">[RFC3986]</a> <a href="#references">[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, @@ -3116,11 +3121,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="#references">[RFC3986]</a> <a - href="#references">[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 @@ -32113,7 +32113,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="#references">[RFC3986]</a></p> <div class=example> <p>If the user had visited a site at <code @@ -42037,8 +42038,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="#references">[RFC3986]</a> <a - href="#references">[RFC3987]</a></p> + of steps.</p> <li> <p>Return from the <code title=dom-window-postMessage><a @@ -46788,7 +46788,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="#references">[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>
Received on Friday, 27 June 2008 08:15:14 UTC