Skip to content

Commit

Permalink
[e] (0) Reference the IDNA spec more reliably.
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7416

git-svn-id: http://svn.whatwg.org/webapps@3930 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Sep 21, 2009
1 parent 81fd546 commit 51bbe93
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 6 deletions.
15 changes: 13 additions & 2 deletions index
Original file line number Diff line number Diff line change
Expand Up @@ -2275,6 +2275,17 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

</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
Expand Down Expand Up @@ -4584,7 +4595,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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>
Expand Down Expand Up @@ -49150,7 +49161,7 @@ interface <dfn id=window>Window</dfn> {
<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
Expand Down
27 changes: 23 additions & 4 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -1309,6 +1309,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

</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
Expand Down Expand Up @@ -4164,7 +4179,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<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
Expand Down Expand Up @@ -55453,7 +55469,8 @@ interface <dfn>Window</dfn> {
<li><p>Apply the IDNA ToUnicode algorithm to each component of the
host part of the <span>origin</span> 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>.</p></li>
STOP characters (".") &mdash; 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
Expand Down Expand Up @@ -74401,7 +74418,8 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
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
Expand Down Expand Up @@ -74468,7 +74486,8 @@ Proxy-authorization: Basic ZWRuYW1vZGU6bm9jYXBlcyE=</pre>
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
Expand Down

0 comments on commit 51bbe93

Please sign in to comment.