[html5] r3880 - [] (0) Update ws: and wss: registration.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Sep 17 03:11:49 PDT 2009
Author: ianh
Date: 2009-09-17 03:11:48 -0700 (Thu, 17 Sep 2009)
New Revision: 3880
Modified:
index
source
Log:
[] (0) Update ws: and wss: registration.
Modified: index
===================================================================
--- index 2009-09-16 22:47:45 UTC (rev 3879)
+++ index 2009-09-17 10:11:48 UTC (rev 3880)
@@ -112,7 +112,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML5</h1>
- <h2 class="no-num no-toc" id=draft-standard-—-16-september-2009>Draft Standard — 16 September 2009</h2>
+ <h2 class="no-num no-toc" id=draft-standard-—-17-september-2009>Draft Standard — 17 September 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -47860,8 +47860,8 @@
<li><p>If the <a href=#parent-browsing-context>parent browsing context</a>'s <a href=#active-document>active
document</a> does not have the <span>same</span> <a href=#effective-script-origin>effective
- script origin</a> as the script that is accessing the <code title=dom-frameElement><a href=#dom-frameelement>frameElement</a></code> attribute, then throw
- a <code><a href=#security_err>SECURITY_ERR</a></code> exception.</li>
+ script origin</a> as the <a href=#first-script>first script</a>, then throw a
+ <code><a href=#security_err>SECURITY_ERR</a></code> exception.</li>
<li><p>Otherwise, return the <a href=#browsing-context-container>browsing context
container</a> for <var title="">b</var>.</li>
Modified: source
===================================================================
--- source 2009-09-16 22:47:45 UTC (rev 3879)
+++ source 2009-09-17 10:11:48 UTC (rev 3880)
@@ -74151,11 +74151,11 @@
<dt>URI scheme syntax.</dt>
<dd>
- <p>In ABNF terms using the terminals from the IRI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3987">[RFC3987]</a></p>
- <pre>"ws" ":" ihier-part [ "?" iquery ]</pre>
+ <p>In ABNF terms using the terminals from the URI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3986">[RFC3986]</a></p>
+ <pre>"ws" ":" hier-part [ "?" query ]</pre>
<p>The path and query components form the resource name sent to
the server to identify the kind of service desired. Other
- components have the meanings described in RFC3987.</p>
+ components have the meanings described in RFC3986.</p>
</dd>
<dt>URI scheme semantics.</dt>
@@ -74163,8 +74163,24 @@
using the Web Socket protocol.</dd>
<dt>Encoding considerations.</dt>
- <dd>See RFC3987. <a href="#refsRFC3987">[RFC3987]</a></dd>
+ <dd>
+ <p>Characters in the host component that are excluded by the
+ 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>
+
+ <p>Characters in other components that are excluded by the syntax
+ defined above must be converted from Unicode to ASCII by first
+ encoding the characters as UTF-8 and then replacing the
+ corresponding bytes using their percent-encoded form as defined in
+ the URI and IRI specification. <a
+ href="#refsRFC3986">[RFC3986]</a> <a
+ href="#refsRFC3987">[RFC3987]</a></p>
+
+ </dd>
+
<dt>Applications/protocols that use this URI scheme name.</dt>
<dd>Web Socket protocol.</dd>
@@ -74202,11 +74218,11 @@
<dt>URI scheme syntax.</dt>
<dd>
- <p>In ABNF terms using the terminals from the IRI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3987">[RFC3987]</a></p>
- <pre>"ws" ":" ihier-part [ "?" iquery ]</pre>
+ <p>In ABNF terms using the terminals from the URI specifications: <a href="#refsRFC5234">[RFC5234]</a> <a href="#refsRFC3986">[RFC3986]</a></p>
+ <pre>"wss" ":" hier-part [ "?" query ]</pre>
<p>The path and query components form the resource name sent to
the server to identify the kind of service desired. Other
- components have the meanings described in RFC3987.</p>
+ components have the meanings described in RFC3986.</p>
</dd>
<dt>URI scheme semantics.</dt>
@@ -74214,8 +74230,24 @@
using the Web Socket protocol, encrypted using TLS.</dd>
<dt>Encoding considerations.</dt>
- <dd>See RFC3987. <a href="#refsRFC3987">[RFC3987]</a></dd>
+ <dd>
+ <p>Characters in the host component that are excluded by the
+ 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>
+
+ <p>Characters in other components that are excluded by the syntax
+ defined above must be converted from Unicode to ASCII by first
+ encoding the characters as UTF-8 and then replacing the
+ corresponding bytes using their percent-encoded form as defined in
+ the URI and IRI specification. <a
+ href="#refsRFC3986">[RFC3986]</a> <a
+ href="#refsRFC3987">[RFC3987]</a></p>
+
+ </dd>
+
<dt>Applications/protocols that use this URI scheme name.</dt>
<dd>Web Socket protocol over TLS.</dd>
More information about the Commit-Watchers
mailing list