html5/spec Overview.html,1.3091,1.3092

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv19883

Modified Files:
	Overview.html 
Log Message:
Reference the IDNA spec more reliably. (whatwg r3930)

Index: Overview.html
===================================================================
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
    &mdash; each component, in the same order, separated by U+002E FULL
-   STOP characters (".") &mdash; to <var title="">result</var>.</li>
+   STOP characters (".") &mdash; 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:14 UTC