- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 19 Jul 2008 18:44:23 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/pubnotes
In directory hutz:/tmp/cvs-serv10283
Modified Files:
Overview.html Overview.src.html
Log Message:
Posting structured data, Server-sent events, eventsource
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.320
retrieving revision 1.321
diff -u -d -r1.320 -r1.321
--- Overview.html 18 Jul 2008 12:11:57 -0000 1.320
+++ Overview.html 19 Jul 2008 18:44:20 -0000 1.321
@@ -12,7 +12,7 @@
</head>
<body><div class="head"><div><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>HTML 5 Publication Notes</h1><h2>
W3C
- Editor’s Draft <em>18 July 2008</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a id="latestED" href="http://dev.w3.org/html5/pubnotes/Overview.src.html">http://dev.w3.org/html5/pubnotes/Overview.src.html</a><script type="text/ecmascript">
+ Editor’s Draft <em>20 July 2008</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a id="latestED" href="http://dev.w3.org/html5/pubnotes/Overview.src.html">http://dev.w3.org/html5/pubnotes/Overview.src.html</a><script type="text/ecmascript">
var id = "$Id$";
var a = document.getElementById('cvsVersionLink');
var xs = id.match(/ ([0-9]\.[0-9.]+) /);
@@ -36,7 +36,7 @@
of the changes without necessarily needing to read the
specification itself.</p>
<div class="ednote"><h4 class="ednoteHeader">Editorial note</h4><p>This document was generated on
- <b>2008-07-18T21:07:12+09:00</b>.</p></div></div>
+ <b>2008-07-20T03:43:53+09:00</b>.</p></div></div>
<div id="status">
<h2>Status of this Document</h2>
<p><em>
@@ -46,7 +46,7 @@
report can be found in the <a href="http://www.w3.org/TR/">W3C technical
reports index</a> at http://www.w3.org/TR/.
</em></p><p>
- This document is the 18 July 2008 <b>Editor’s Draft</b> of
+ This document is the 20 July 2008 <b>Editor’s Draft</b> of
<cite>HTML 5 Publication Notes</cite>.
Please send comments about this document to
@@ -166,7 +166,7 @@
<ul>
<li id="script_wd2-toc"><a href="#script_wd2">Section 4.10.1, The script element</a>
</li>
-<li id="the-event-source_wd2-toc"><a href="#the-event-source_wd2">Section 4.10.3, The eventsource element</a>
+<li id="the-eventsource_wd2-toc"><a href="#the-eventsource_wd2">Section 4.10.3, The eventsource element</a>
</li>
</ul>
</li>
@@ -200,7 +200,7 @@
<ul>
<li id="event1_wd2-toc"><a href="#event1_wd2">Section 7.1, Event definitions</a>
</li>
-<li id="server-sent-events_wd2-toc"><a href="#server-sent-events_wd2">Section 7.2, Server-sent DOM events</a>
+<li id="server-sent-events_wd2-toc"><a href="#server-sent-events_wd2">Section 7.2, Server-sent events</a>
</li>
<li id="network_wd2-toc"><a href="#network_wd2">Section 7.3, Web sockets [formerly “Network connections”]</a>
</li>
@@ -214,6 +214,8 @@
</li>
<li id="posting0_wd2-toc"><a href="#posting0_wd2">Section 7.4.4, Posting message ports</a>
</li>
+<li id="posting1_wd2-toc"><a href="#posting1_wd2">Section 7.4.5, Posting structured data</a>
+</li>
</ul>
</li>
<li id="channel0_wd2-toc"><a href="#channel0_wd2">Section 7.5 [NEW], Channel messaging</a>
@@ -1782,12 +1784,12 @@
element.</q></li>
</ul>
</div>
- <div id="the-event-source_wd2" class="section">
- <h2>Section 4.10.3, The eventsource element <a class="hash" href="#the-event-source_wd2">#</a> <a class="toc-bak" href="#the-event-source_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#the-event-source">Section 4.10.3, The eventsource element</a>” in the
+ <div id="the-eventsource_wd2" class="section">
+ <h2>Section 4.10.3, The eventsource element <a class="hash" href="#the-eventsource_wd2">#</a> <a class="toc-bak" href="#the-eventsource_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#the-eventsource">Section 4.10.3, The eventsource element</a>” in the
current “Editor’s Draft”
version of the specification.</p><p class="spec-link">View
- “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#the-event-source">Section 4.10.3, The eventsource element</a>”
+ “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#the-eventsource">Section 4.10.3, The eventsource element</a>”
in a
diff-marked version of the specification, showing
changes made between
@@ -1800,7 +1802,7 @@
<li>The element was renamed to
<code class="element">eventsource</code>
(it had been “event-source” in previous
- drafts.</li>
+ drafts).</li>
<li>For consistency with the conformance
requirements specified in the “URLs” section,
extensive revisions were made to text that
@@ -2301,7 +2303,7 @@
same client to communicate with each other. This section
defines APIs for
enabling those classes of communication; specifically,
- APIs for cross-document messaging, for server-sent DOM
+ APIs for cross-document messaging, for server-sent
events, for “Web Sockets” (for enabling
Web applications to maintain bidirectional
communications with their originating server),
@@ -2328,14 +2330,29 @@
was added to the interface definition for the
<code>MessageEvent</code>
interface.</li>
+ <li>The following statements were added:
+ <blockquote>
+ <p><q>The messagePort attribute represents, in
+ cross-document messaging and channel messaging
+ the MessagePort being sent, if any.</q></p>
+ <p><q>Unless otherwise specified, when the user
+ agent creates and dispatches a message event in
+ the algorithms described in the following
+ sections, the lastEventId attribute must be the
+ empty string, the origin attribute must be the
+ empty string, the source attribute must be null,
+ and the messagePort attribute must be
+ null.</q></p>
+ </blockquote>
+ </li>
</ul>
</div>
<div id="server-sent-events_wd2" class="section">
- <h2>Section 7.2, Server-sent DOM events <a class="hash" href="#server-sent-events_wd2">#</a> <a class="toc-bak" href="#server-sent-events_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#server-sent-events">Section 7.2, Server-sent DOM events</a>” in the
+ <h2>Section 7.2, Server-sent events <a class="hash" href="#server-sent-events_wd2">#</a> <a class="toc-bak" href="#server-sent-events_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#server-sent-events">Section 7.2, Server-sent events</a>” in the
current “Editor’s Draft”
version of the specification.</p><p class="spec-link">View
- “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#server-sent-events">Section 7.2, Server-sent DOM events</a>”
+ “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#server-sent-events">Section 7.2, Server-sent events</a>”
in a
diff-marked version of the specification, showing
changes made between
@@ -2347,6 +2364,10 @@
expect it. In this section, the following changes were
made.</p>
<ul>
+ <li>The section and the mechanism it describes were
+ renamed to <q>Server-sent events</q> (previous
+ drafts had use the term “Server-sent DOM
+ events”).</li>
<li>In the “The RemoteEventTarget interface”
subsection, statements related to the
<code>src</code>
@@ -2361,6 +2382,10 @@
<code>src</code>
parameter,
and to using the resulting <q>absolute URL</q>.</li>
+ <li>In the “Interpreting an event stream”
+ subsection, some revisions were made to the part of
+ the algorithm that user agents are required to run
+ when dispatching and event.</li>
</ul>
</div>
<div id="network_wd2" class="section">
@@ -2498,6 +2523,22 @@
argument” form) of the <code class="method">postMessage()</code>
method.</p>
</div>
+ <div id="posting1_wd2" class="section">
+ <h2>Section 7.4.5, Posting structured data <a class="hash" href="#posting1_wd2">#</a> <a class="toc-bak" href="#posting1_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#posting1">Section 7.4.5, Posting structured data</a>” in the
+ current “Editor’s Draft”
+ version of the specification.</p><p class="spec-link">View
+
+ “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#posting1">Section 7.4.5, Posting structured data</a>”
+ in a
+ diff-marked version of the specification, showing
+ changes made between
+ 10 June 2008
+ and
+ current “Editor’s Draft”.</p></div>
+ <p>This newly added section is currently a
+ placeholder, with an editorial note about its
+ intended purpose.</p>
+ </div>
</div>
<div id="channel0_wd2" class="section">
<h2>Section 7.5 [NEW], Channel messaging <a class="hash" href="#channel0_wd2">#</a> <a class="toc-bak" href="#channel0_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#channel0">Section 7.5 [NEW], Channel messaging</a>” in the
Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.312
retrieving revision 1.313
diff -u -d -r1.312 -r1.313
--- Overview.src.html 18 Jul 2008 12:11:58 -0000 1.312
+++ Overview.src.html 19 Jul 2008 18:44:20 -0000 1.313
@@ -963,7 +963,7 @@
element.</q></li>
</ul>
</section>
- <section id=the-event-source_wd2>
+ <section id=the-eventsource_wd2>
<h2>Section 4.10.3, The eventsource element</h2>
<p>In this section, the following changes were
made:</p>
@@ -971,7 +971,7 @@
<li>The element was renamed to
<code class=element>eventsource</code>
(it had been “event-source” in previous
- drafts.</li>
+ drafts).</li>
<li>For consistency with the conformance
requirements specified in the “URLs” section,
extensive revisions were made to text that
@@ -1358,7 +1358,7 @@
same client to communicate with each other. This section
defines APIs for
enabling those classes of communication; specifically,
- APIs for cross-document messaging, for server-sent DOM
+ APIs for cross-document messaging, for server-sent
events, for “Web Sockets” (for enabling
Web applications to maintain bidirectional
communications with their originating server),
@@ -1375,15 +1375,34 @@
was added to the interface definition for the
<code>MessageEvent</code>
interface.</li>
+ <li>The following statements were added:
+ <blockquote>
+ <p><q>The messagePort attribute represents, in
+ cross-document messaging and channel messaging
+ the MessagePort being sent, if any.</q></p>
+ <p><q>Unless otherwise specified, when the user
+ agent creates and dispatches a message event in
+ the algorithms described in the following
+ sections, the lastEventId attribute must be the
+ empty string, the origin attribute must be the
+ empty string, the source attribute must be null,
+ and the messagePort attribute must be
+ null.</q></p>
+ </blockquote>
+ </li>
</ul>
</section>
<section id=server-sent-events_wd2>
- <h2>Section 7.2, Server-sent DOM events</h2>
+ <h2>Section 7.2, Server-sent events</h2>
<p>This section describes a mechanism for allowing
servers to dispatch DOM events into documents that
expect it. In this section, the following changes were
made.</p>
<ul>
+ <li>The section and the mechanism it describes were
+ renamed to <q>Server-sent events</q> (previous
+ drafts had use the term “Server-sent DOM
+ events”).</li>
<li>In the “The RemoteEventTarget interface”
subsection, statements related to the
<code>src</code>
@@ -1398,6 +1417,10 @@
<code>src</code>
parameter,
and to using the resulting <q>absolute URL</q>.</li>
+ <li>In the “Interpreting an event stream”
+ subsection, some revisions were made to the part of
+ the algorithm that user agents are required to run
+ when dispatching and event.</li>
</ul>
</section>
<section id=network_wd2>
@@ -1477,6 +1500,12 @@
class=method>postMessage()</code>
method.</p>
</section>
+ <section id=posting1_wd2>
+ <h2>Section 7.4.5, Posting structured data</h2>
+ <p>This newly added section is currently a
+ placeholder, with an editorial note about its
+ intended purpose.</p>
+ </section>
</section>
<section id=channel0_wd2>
<h2>Section 7.5 [NEW], Channel messaging</h2>
Received on Saturday, 19 July 2008 18:44:57 UTC