- From: poot <cvsmail@w3.org>
- Date: Mon, 21 Sep 2009 19:49:21 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: Reference the IDNA spec more reliably. (whatwg r3930) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3091&r2=1.3092&f=h http://html5.org/tools/web-apps-tracker?from=3929&to=3930 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3091 retrieving revision 1.3092 diff -u -d -r1.3091 -r1.3092 --- Overview.html 21 Sep 2009 10:37:49 -0000 1.3091 +++ Overview.html 21 Sep 2009 10:48:57 -0000 1.3092 @@ -2072,6 +2072,17 @@ </dd> + <dt>URIs, IRIs, IDNA</dt> + + <dd> + + <p>Implementations must support the the semantics of <span title="URLs">URLs</span> defined in the URI and IRI + specifications, as well as the semantics of IDNA domain names + defined in the <cite>Internationalizing Domain Names in + Applications (IDNA)</cite> specification. <a href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a> <a href="#refsRFC3490">[RFC3490]</a> + + </dd> + </dl><p>This specification does not <em>require</em> support of any particular network transport protocols, style sheet language, scripting language, or any of the DOM and WebAPI specifications @@ -4139,7 +4150,7 @@ </ol></div><h4 id="reversed-dns-identifiers"><span class="secno">2.4.9 </span>Reversed DNS identifiers</h4><p>A <dfn id="valid-reversed-dns-identifier">valid reversed DNS identifier</dfn> is a string that consists of a series of IDNA labels in reverse order (i.e. starting with the top-level domain), the prefix of which, when reversed and - converted to ASCII, corresponds to a registered domain.<p class="example">For instance, the string "<code title="">com.example.xn--74h</code>" is a <a href="#valid-reversed-dns-identifier">valid reversed DNS + converted to ASCII, corresponds to a registered domain. <a href="#refsRFC3490">[RFC3490]</a><p class="example">For instance, the string "<code title="">com.example.xn--74h</code>" is a <a href="#valid-reversed-dns-identifier">valid reversed DNS identifier</a> because the string "<code title="">example.com</code>" is a registered domain.<div class="impl"> <p>To check if a string is a <a href="#valid-reversed-dns-identifier">valid reversed DNS @@ -44208,7 +44219,7 @@ <li><p>Apply the IDNA ToUnicode algorithm to each component of the host part of the <a href="#origin">origin</a> tuple, and append the results — each component, in the same order, separated by U+002E FULL - STOP characters (".") — to <var title="">result</var>.</li> + STOP characters (".") — to <var title="">result</var>. <a href="#refsRFC3490">[RFC3490]</a></li> <li><p>If the port part of the <a href="#origin">origin</a> tuple gives a port that is different from the default port for the protocol given by
Received on Monday, 21 September 2009 10:49:57 UTC