- From: poot <cvsmail@w3.org>
- Date: 2011年4月14日 18:20:18 -0400
- To: public-html-diffs@w3.org
- Message-Id: <E1QAUte-0005FN-GU@jay.w3.org>
hixie: apply wg decision (whatwg r6007) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4829&r2=1.4830&f=h http://html5.org/tools/web-apps-tracker?from=6006&to=6007 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.4829 retrieving revision 1.4830 diff -u -d -r1.4829 -r1.4830 --- Overview.html 14 Apr 2011 00:58:20 -0000 1.4829 +++ Overview.html 14 Apr 2011 22:18:07 -0000 1.4830 @@ -564,8 +564,10 @@ <li><a href="#urls"><span class="secno">2.6 </span>URLs</a> <ol> <li><a href="#terminology-0"><span class="secno">2.6.1 </span>Terminology</a></li> - <li><a href="#dynamic-changes-to-base-urls"><span class="secno">2.6.2 </span>Dynamic changes to base URLs</a></li> - <li><a href="#interfaces-for-url-manipulation"><span class="secno">2.6.3 </span>Interfaces for URL manipulation</a></ol></li> + <li><a href="#parsing-urls"><span class="secno">2.6.2 </span>Parsing URLs</a></li> + <li><a href="#resolving-urls"><span class="secno">2.6.3 </span>Resolving URLs</a></li> + <li><a href="#dynamic-changes-to-base-urls"><span class="secno">2.6.4 </span>Dynamic changes to base URLs</a></li> + <li><a href="#interfaces-for-url-manipulation"><span class="secno">2.6.5 </span>Interfaces for URL manipulation</a></ol></li> <li><a href="#fetching-resources"><span class="secno">2.7 </span>Fetching resources</a> <ol> <li><a href="#concept-http-equivalent"><span class="secno">2.7.1 </span>Protocol concepts</a></li> @@ -5139,7 +5141,16 @@ the empty string, a string consisting of only <a href="#space-character" title="space character">space characters</a>, or is a media query that matches the user's environment according to the definitions given in the - Media Queries specification. <a href="#refsMQ">[MQ]</a><h3 id="urls"><span class="secno">2.6 </span>URLs</h3><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/56">ISSUE-56</a> (urls-webarch) blocks progress to Last Call</span><h4 id="terminology-0"><span class="secno">2.6.1 </span>Terminology</h4><p>A <dfn id="url">URL</dfn> is a string used to identify a resource.<p>A <a href="#url">URL</a> is a <dfn id="valid-url">valid URL</dfn> if at least one of + Media Queries specification. <a href="#refsMQ">[MQ]</a><h3 id="urls"><span class="secno">2.6 </span>URLs</h3><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/56">ISSUE-56</a> (urls-webarch) blocks progress to Last Call</span><p>This specification defines the term <a href="#url">URL</a>, and defines + various algorithms for dealing with URLs, because for historical + reasons the rules defined by the URI and IRI specifications are not + a complete description of what HTML user agents need to implement to + be compatible with Web content.<p class="note">The term "URL" in this specification is used in a + manner distinct from the precise technical meaning it is given in + RFC 3986. Readers familiar with that RFC will find it easier to read + <em>this</em> specification if they pretend the term "URL" as used + herein is really called something else altogether. This is a + <a href="#willful-violation">willful violation</a> of RFC 3986. <a href="#refsRFC3986">[RFC3986]</a><h4 id="terminology-0"><span class="secno">2.6.1 </span>Terminology</h4><p>A <dfn id="url">URL</dfn> is a string used to identify a resource.<p>A <a href="#url">URL</a> is a <dfn id="valid-url">valid URL</dfn> if at least one of the following conditions holds:<ul><li><p>The <a href="#url">URL</a> is a valid URI reference <a href="#refsRFC3986">[RFC3986]</a>.</li> <li><p>The <a href="#url">URL</a> is a valid IRI reference and it has no @@ -5158,24 +5169,140 @@ it, it is a <a href="#valid-url">valid URL</a>.<p>A string is a <dfn id="valid-non-empty-url-potentially-surrounded-by-spaces">valid non-empty URL potentially surrounded by spaces</dfn> if, after <a href="#strip-leading-and-trailing-whitespace" title="strip leading and trailing whitespace">stripping leading and trailing whitespace</a> from - it, it is a <a href="#valid-non-empty-url">valid non-empty URL</a>.<div class="impl"> + it, it is a <a href="#valid-non-empty-url">valid non-empty URL</a>.<p>This specification defines the URL + <dfn id="about:legacy-compat"><code>about:legacy-compat</code></dfn> as a reserved, though + unresolvable, <code title="">about:</code> URI, for use in <a href="#syntax-doctype" title="syntax-doctype">DOCTYPE</a>s in <a href="#html-documents">HTML + documents</a> when needed for compatibility with XML tools. <a href="#refsABOUT">[ABOUT]</a><p>This specification defines the URL + <dfn id="about:srcdoc"><code>about:srcdoc</code></dfn> as a reserved, though + unresolvable, <code title="">about:</code> URI, that is used as + <a href="#the-document-s-address">the document's address</a> of <a href="#an-iframe-srcdoc-document" title="an iframe srcdoc + document"><code>iframe</code> <code title="attr-iframe-srcdoc">srcdoc</code> documents</a>. <a href="#refsABOUT">[ABOUT]</a><div class="impl"> + + <h4 id="parsing-urls"><span class="secno">2.6.2 </span>Parsing URLs</h4> <p>To <dfn id="parse-a-url">parse a URL</dfn> <var title="">url</var> into its - component parts, the user agent must use the <span class="XXX">parse - an address</span> algorithm defined by the IRI specification. <a href="#refsRFC3987">[RFC3987]</a></p> + component parts, the user agent must use the following steps:</p> - <p>Parsing a URL can fail. If it does not, then it results in the - following components, again as defined by the IRI specification:</p> + <ol><li><p>Strip leading and trailing <a href="#space-character" title="space + character">space characters</a> from <var title="">url</var>.</li> - <ul class="brief"><li><dfn id="url-scheme" title="url-scheme"><scheme></dfn></li> - <li><dfn id="url-host" title="url-host"><host></dfn></li> - <li><dfn id="url-port" title="url-port"><port></dfn></li> - <li><dfn id="url-hostport" title="url-hostport"><hostport></dfn></li> - <li><dfn id="url-path" title="url-path"><path></dfn></li> - <li><dfn id="url-query" title="url-query"><query></dfn></li> - <li><dfn id="url-fragment" title="url-fragment"><fragment></dfn></li> - <li><dfn id="url-host-specific" title="url-host-specific"><host-specific></dfn></li> - </ul><hr><p>To <dfn id="resolve-a-url">resolve a URL</dfn> to an <a href="#absolute-url">absolute URL</a> + <li> + + <p>Parse <var title="">url</var> in the manner defined by RFC + 3986, with the following exceptions:</p> + + <ul><li>Add all characters with code points less than or equal to + U+0020 or greater than or equal to U+007F to the + <unreserved> production.</li> + + <li>Add the characters U+0022, U+003C, U+003E, U+005B .. U+005E, + U+0060, and U+007B .. U+007D to the <unreserved> + production. + <!-- <!-- + 0022 QUOTATION MARK + 003C LESS-THAN SIGN + 003E GREATER-THAN SIGN + 005B LEFT SQUARE BRACKET + 005C REVERSE SOLIDUS + 005D RIGHT SQUARE BRACKET + 005E CIRCUMFLEX ACCENT + 0060 GRAVE ACCENT + 007B LEFT CURLY BRACKET + 007C VERTICAL LINE + 007D RIGHT CURLY BRACKET + --> + </li> + + <li>Add a single U+0025 PERCENT SIGN character as a second + alternative way of matching the <pct-encoded> production, + except when the <pct-encoded> is used in the + <reg-name> production.</li> + + <li>Add the U+0023 NUMBER SIGN character to the characters + allowed in the <fragment> production.</li> + + + </ul></li> + + <li> + + <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. <a href="#refsRFC3986">[RFC3986]</a></p> + + <p>Otherwise, parsing <var title="">url</var> was successful; the + components of the URL are substrings of <var title="">url</var> + defined as follows:</p> + + <dl><dt><dfn id="url-scheme" title="url-scheme"><scheme></dfn></dt> + + <dd><p>The substring matched by the <scheme> production, if any.</dd> + + + <dt><dfn id="url-host" title="url-host"><host></dfn></dt> + + <dd><p>The substring matched by the <host> production, if any.</dd> + + + <dt><dfn id="url-port" title="url-port"><port></dfn></dt> + + <dd><p>The substring matched by the <port> production, if any.</dd> + + + <dt><dfn id="url-hostport" title="url-hostport"><hostport></dfn></dt> + + <dd><p>If there is a <scheme> component and a <port> + component and the port given by the <port> component is + different than the default port defined for the protocol given by + the <scheme> component, then <hostport> is the + substring that starts with the substring matched by the + <host> production and ends with the substring matched by the + <port> production, and includes the colon in between the + two. Otherwise, it is the same as the <host> component.</p> + + + <dt><dfn id="url-path" title="url-path"><path></dfn></dt> + + <dd> + + <p>The substring matched by one of the following productions, if + one of them was matched:</p> + + <ul class="brief"><li><path-abempty></li> + <li><path-absolute></li> + <li><path-noscheme></li> + <li><path-rootless></li> + <li><path-empty></li> + </ul></dd> + + + <dt><dfn id="url-query" title="url-query"><query></dfn></dt> + + <dd><p>The substring matched by the <query> production, if any.</dd> + + + <dt><dfn id="url-fragment" title="url-fragment"><fragment></dfn></dt> + + <dd><p>The substring matched by the <fragment> production, if any.</dd> + + + <dt><dfn id="url-host-specific" title="url-host-specific"><host-specific></dfn></dt> + + <dd><p>The substring that <em>follows</em> the substring matched + by the <authority> production, or the whole string if the + <authority> production wasn't matched.</dd> + + </dl></li> + + </ol><p class="note">These parsing rules are a <a href="#willful-violation">willful + violation</a> of RFC 3986 and RFC 3987 (which do not define error + handling), motivated by a desire to handle legacy content. <a href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a></p> + + </div><h4 id="resolving-urls"><span class="secno">2.6.3 </span>Resolving URLs</h4><p>Resolving a URL is the process of taking a relative URL and + obtaining the absolute URL that it implies.<div class="impl"> + + <p>To <dfn id="resolve-a-url">resolve a URL</dfn> to an <a href="#absolute-url">absolute URL</a> relative to either another <a href="#absolute-url">absolute URL</a> or an element, the user agent must use the following steps. Resolving a URL can result in an error, in which case the URL is not resolvable.</p> @@ -5273,11 +5400,112 @@ </ol></li> - <li><p>Return the result of applying the <span class="XXX">resolve - an address</span> algorithm defined by the IRI specification to - resolve <var title="">url</var> relative to <var title="">base</var> using encoding <var title="">encoding</var>. <a href="#refsRFC3987">[RFC3987]</a></li> + <li><p><a href="#parse-a-url" title="parse a URL">Parse</a> <var title="">url</var> into its component parts.</li> - </ol></div><p>A <a href="#url">URL</a> is an <dfn id="absolute-url">absolute URL</dfn> if <a href="#resolve-a-url" title="resolve a url">resolving</a> it results in the same output + <li> + + <p>If parsing <var title="">url</var> resulted in a <a href="#url-host" title="url-host"><host></a> component, then replace the + matching substring of <var title="">url</var> with the string that + results from expanding any sequences of percent-encoded octets in + that component that are valid UTF-8 sequences into Unicode + characters as defined by UTF-8.</p> + + <p>If any percent-encoded octets in that component are not valid + UTF-8 sequences, then return an error and abort these steps.</p> + + <p>Apply the IDNA ToASCII algorithm to the matching substring, + with both the AllowUnassigned and UseSTD3ASCIIRules flags + set. Replace the matching substring with the result of the ToASCII + algorithm.</p> + + <p>If ToASCII fails to convert one of the components of the + string, e.g. because it is too long or because it contains invalid + characters, then return an error and abort these steps. <a href="#refsRFC3490">[RFC3490]</a></p> + + </li> + + <li> + + <p>If parsing <var title="">url</var> resulted in a <a href="#url-path" title="url-path"><path></a> component, then replace the + matching substring of <var title="">url</var> with the string that + results from applying the following steps to each character other + than U+0025 PERCENT SIGN (%) that doesn't match the original + <path> production defined in RFC 3986:</p> + + <ol><li>Encode the character into a sequence of octets as defined by + UTF-8.</li> + + <li>Replace the character with the percent-encoded form of those + octets. <a href="#refsRFC3986">[RFC3986]</a></li> + + </ol><div class="example"> + + <p>For instance if <var title="">url</var> was "<code title="">//example.com/a^b☺c%FFd%z/?e</code>", then the + <a href="#url-path" title="url-path"><path></a> component's substring + would be "<code title="">/a^b☺c%FFd%z/</code>" and the two + characters that would have to be escaped would be "<code title="">^</code>" and "<code title="">☺</code>". The + result after this step was applied would therefore be that <var title="">url</var> now had the value "<code title="">//example.com/a%5Eb%E2%98%BAc%FFd%z/?e</code>".</p> + + </div> + + </li> + + <li> + + <p>If parsing <var title="">url</var> resulted in a <a href="#url-query" title="url-query"><query></a> component, then replace the + matching substring of <var title="">url</var> with the string that + results from applying the following steps to each character other + than U+0025 PERCENT SIGN (%) that doesn't match the original + <query> production defined in RFC 3986:</p> + + <ol><li>If the character in question cannot be expressed in the + encoding <var title="">encoding</var>, then replace it with a + single 0x3F octet (an ASCII question mark) and skip the remaining + substeps for this character.</li> + + <li>Encode the character into a sequence of octets as defined by + the encoding <var title="">encoding</var>.</li> + + <li>Replace the character with the percent-encoded form of those + octets. <a href="#refsRFC3986">[RFC3986]</a></li> + + </ol></li> + + <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>). <a href="#refsRFC3986">[RFC3986]</a></li> + + <li> + + <p>Apply any relevant conformance criteria of RFC 3986 and RFC + 3987, 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, e.g. a <code title="">data:</code> URI using the + "<code title="">//</code>" server-based naming authority syntax, + then user agents are to treat this as an error instead.</p> + + </li> + + <li><p>Let <var title="">result</var> be the target URI (<var title="">T</var>) returned by the Relative Resolution + algorithm.</li> + + <li><p>If <var title="">result</var> uses a scheme with a + server-based naming authority, replace all U+005C REVERSE SOLIDUS + (\) characters in <var title="">result</var> with U+002F SOLIDUS + (/) characters.</li> + + <li><p>Return <var title="">result</var>.</li> + + </ol><p class="note">Some of the steps in these rules, for example the + processing of U+005C REVERSE SOLIDUS (\) characters, are a + <a href="#willful-violation">willful violation</a> of RFC 3986 and RFC 3987, motivated + by a desire to handle legacy content. <a href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a></p> + + </div><p>A <a href="#url">URL</a> is an <dfn id="absolute-url">absolute URL</dfn> if <a href="#resolve-a-url" title="resolve a url">resolving</a> it results in the same output regardless of what it is resolved relative to, and that output is not a failure.<p>An <a href="#absolute-url">absolute URL</a> is a <dfn id="hierarchical-url">hierarchical URL</dfn> if, when <a href="#resolve-a-url" title="resolve a url">resolved</a> and then <a href="#parse-a-url" title="parse a url">parsed</a>, there is a character immediately @@ -5285,21 +5513,9 @@ and it is a U+002F SOLIDUS character (/).<p>An <a href="#absolute-url">absolute URL</a> is an <dfn id="authority-based-url">authority-based URL</dfn> if, when <a href="#resolve-a-url" title="resolve a url">resolved</a> and then <a href="#parse-a-url" title="parse a url">parsed</a>, there are two characters immediately after the <a href="#url-scheme" title="url-scheme"><scheme></a> - component and they are both U+002F SOLIDUS characters (//).<hr><p>This specification defines the URL - <dfn id="about:legacy-compat"><code>about:legacy-compat</code></dfn> as a reserved, though - unresolvable, <code title="">about:</code> URI, for use in <a href="#syntax-doctype" title="syntax-doctype">DOCTYPE</a>s in <a href="#html-documents">HTML - documents</a> when needed for compatibility with XML tools. <a href="#refsABOUT">[ABOUT]</a><p>This specification defines the URL - <dfn id="about:srcdoc"><code>about:srcdoc</code></dfn> as a reserved, though - unresolvable, <code title="">about:</code> URI, that is used as - <a href="#the-document-s-address">the document's address</a> of <a href="#an-iframe-srcdoc-document" title="an iframe srcdoc - document"><code>iframe</code> <code title="attr-iframe-srcdoc">srcdoc</code> documents</a>. <a href="#refsABOUT">[ABOUT]</a><p class="note">The term "URL" in this specification is used in a - manner distinct from the precise technical meaning it is given in - RFC 3986. Readers familiar with that RFC will find it easier to read - <em>this</em> specification if they pretend the term "URL" as used - herein is really called something else altogether. This is a - <a href="#willful-violation">willful violation</a> of RFC 3986. <a href="#refsRFC3986">[RFC3986]</a><div class="impl"> + component and they are both U+002F SOLIDUS characters (//).<div class="impl"> - <h4 id="dynamic-changes-to-base-urls"><span class="secno">2.6.2 </span>Dynamic changes to base URLs</h4> + <h4 id="dynamic-changes-to-base-urls"><span class="secno">2.6.4 </span>Dynamic changes to base URLs</h4> <p>When an <code title="attr-xml-base"><a href="#the-xml:base-attribute-xml-only">xml:base</a></code> attribute changes, the attribute's element, and all descendant elements, are @@ -5361,7 +5577,7 @@ </dd> - </dl></div><h4 id="interfaces-for-url-manipulation"><span class="secno">2.6.3 </span>Interfaces for URL manipulation</h4><p>An interface that has a complement of <dfn id="url-decomposition-idl-attributes">URL decomposition IDL + </dl></div><h4 id="interfaces-for-url-manipulation"><span class="secno">2.6.5 </span>Interfaces for URL manipulation</h4><p>An interface that has a complement of <dfn id="url-decomposition-idl-attributes">URL decomposition IDL attributes</dfn> has seven attributes with the following definitions:<pre class="idl extract"> attribute DOMString <a href="#dom-uda-protocol" title="dom-uda-protocol">protocol</a>; attribute DOMString <a href="#dom-uda-host" title="dom-uda-host">host</a>;
Received on Thursday, 14 April 2011 22:20:21 UTC