[html5] r3930 - [e] (0) Reference the IDNA spec more reliably. Fixing http://www.w3.org/Bugs/Pub [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-21 03:55:40 -0700 (Mon, 21 Sep 2009)
New Revision: 3930

Modified:
   index
   source
Log:
[e] (0) Reference the IDNA spec more reliably.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7416

Modified: index
===================================================================
--- index	2009-09-21 10:44:33 UTC (rev 3929)
+++ index	2009-09-21 10:55:40 UTC (rev 3930)
@@ -2275,6 +2275,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
@@ -4584,7 +4595,7 @@
   <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>
+  converted to ASCII, corresponds to a registered domain. <a href=#refsRFC3490>[RFC3490]</a></p>
 
   <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.</p>
@@ -49150,7 +49161,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

Modified: source
===================================================================
--- source	2009-09-21 10:44:33 UTC (rev 3929)
+++ source	2009-09-21 10:55:40 UTC (rev 3930)
@@ -1309,6 +1309,21 @@
 
    </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
@@ -4164,7 +4179,8 @@
   <p>A <dfn>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>
+  converted to ASCII, corresponds to a registered domain. <a
+  href="#refsRFC3490">[RFC3490]</a></p>
 
   <p class="example">For instance, the string "<code
   title="">com.example.xn--74h</code>" is a <span>valid reversed DNS
@@ -55453,7 +55469,8 @@
    <li><p>Apply the IDNA ToUnicode algorithm to each component of the
    host part of the <span>origin</span> tuple, and append the results
    — each component, in the same order, separated by U+002E FULL
-   STOP characters (".") — to <var title="">result</var>.</p></li>
+   STOP characters (".") — to <var title="">result</var>. <a
+   href="#refsRFC3490">[RFC3490]</a></p></li>
 
    <li><p>If the port part of the <span>origin</span> tuple gives a port
    that is different from the default port for the protocol given by
@@ -74401,7 +74418,8 @@
     syntax defined above must be converted from Unicode to ASCII by
     applying the IDNA ToASCII algorithm to the Unicode host name, with
     both the AllowUnassigned and UseSTD3ASCIIRules flags set, and
-    using the result of this algorithm as the host in the URI.</p>
+    using the result of this algorithm as the host in the URI. <a
+    href="#refsRFC3490">[RFC3490]</a></p>
 
     <p>Characters in other components that are excluded by the syntax
     defined above must be converted from Unicode to ASCII by first
@@ -74468,7 +74486,8 @@
     syntax defined above must be converted from Unicode to ASCII by
     applying the IDNA ToASCII algorithm to the Unicode host name, with
     both the AllowUnassigned and UseSTD3ASCIIRules flags set, and
-    using the result of this algorithm as the host in the URI.</p>
+    using the result of this algorithm as the host in the URI. <a
+    href="#refsRFC3490">[RFC3490]</a></p>
 
     <p>Characters in other components that are excluded by the syntax
     defined above must be converted from Unicode to ASCII by first