[html5] r6131 - [e] (0) prepare an rtc extract for easier review by those who only want to revie [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu May 12 12:10:19 PDT 2011
Author: ianh
Date: 2011-05-12 12:10:17 -0700 (Thu, 12 May 2011)
New Revision: 6131
Modified:
complete.html
index
source
Log:
[e] (0) prepare an rtc extract for easier review by those who only want to review the rtc stuff
Modified: complete.html
===================================================================
--- complete.html 2011-05-12 06:58:07 UTC (rev 6130)
+++ complete.html 2011-05-12 19:10:17 UTC (rev 6131)
@@ -13242,7 +13242,9 @@
+<!--PEERCONNECTION-->
<h2 id=semantics><span class=secno>4 </span>The elements of HTML</h2>
+<!--PEERCONNECTION-->
<h3 id=the-root-element><span class=secno>4.1 </span>The root element</h3>
@@ -21965,8 +21967,9 @@
-
+<!--PEERCONNECTION-->
<h3 id=embedded-content-1><span class=secno>4.8 </span>Embedded content</h3>
+<!--PEERCONNECTION-->
<h4 id=the-img-element><span class=secno>4.8.1 </span>The <dfn><code>img</code></dfn> element</h4>
@@ -26237,8 +26240,9 @@
</div>
-
+<!--PEERCONNECTION-->
<h4 id=media-elements><span class=secno>4.8.10 </span>Media elements</h4>
+<!--PEERCONNECTION-->
<p><dfn id=media-element title="media element">Media elements</dfn>
(<code><a href=#the-audio-element>audio</a></code> and <code><a href=#the-video-element>video</a></code>, in this specification)
@@ -26350,9 +26354,13 @@
present audio data, or video and audio data, to the user. This is
referred to as <dfn id=media-data>media data</dfn> in this section, since this
section applies equally to <a href=#media-element title="media element">media
- elements</a> for audio or for video. The term <dfn id=media-resource>media
- resource</dfn> is used to refer to the complete set of media data,
- e.g. the complete video file, or complete audio file.</p>
+ elements</a> for audio or for video.
+<!--PEERCONNECTION-->
+ The term <dfn id=media-resource>media resource</dfn> is used to refer to the complete
+ set of media data, e.g. the complete video file, or complete audio
+ file.
+<!--PEERCONNECTION-->
+ </p>
<p>A <a href=#media-resource>media resource</a> can have multiple audio and video
tracks. For the purposes of a <a href=#media-element>media element</a>, the video
@@ -28817,8 +28825,9 @@
</div>
-
+<!--PEERCONNECTION-->
<h5 id=media-resources-with-multiple-media-tracks><span class=secno>4.8.10.10 </span>Media resources with multiple media tracks</h5>
+<!--PEERCONNECTION-->
<p>A <a href=#media-resource>media resource</a> can have multiple embedded audio
and video tracks. For example, in addition to the primary video and
@@ -28869,16 +28878,19 @@
</div>
+<!--PEERCONNECTION-->
<h6 id=tracklist-objects><span class=secno>4.8.10.10.1 </span><code><a href=#tracklist>TrackList</a></code> objects</h6>
<!-- should probably move this section out since it is also used by
the video conferencing stuff -->
+<!--PEERCONNECTION-->
<p>The <code><a href=#multipletracklist>MultipleTrackList</a></code> and
<code><a href=#exclusivetracklist>ExclusiveTrackList</a></code> interfaces, used by the attributes
defined in the previous section, are substantially similar. Their
common features are defined in the <code><a href=#tracklist>TrackList</a></code> interface,
from which they both inherit.</p>
+<!--PEERCONNECTION-->
<pre class=idl>interface <dfn id=tracklist>TrackList</dfn> {
readonly attribute unsigned long <a href=#dom-tracklist-length title=dom-TrackList-length>length</a>;
@@ -29163,6 +29175,7 @@
selection -->
</div>
+<!--PEERCONNECTION-->
<h5 id=synchronising-multiple-media-elements><span class=secno>4.8.10.11 </span>Synchronising multiple media elements</h5>
Modified: index
===================================================================
--- index 2011-05-12 06:58:07 UTC (rev 6130)
+++ index 2011-05-12 19:10:17 UTC (rev 6131)
@@ -1337,7 +1337,7 @@
differ in a small number of ways. The main difference is that the
W3C version does not include some newer features, such as:</p>
- <ul class=brief><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONTROLLER-->
+ <ul class=brief><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
<li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
<li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TTVTT-->
<li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
@@ -13267,7 +13267,9 @@
+<!--PEERCONNECTION-->
<h2 id=semantics><span class=secno>4 </span>The elements of HTML</h2>
+<!--PEERCONNECTION-->
<h3 id=the-root-element><span class=secno>4.1 </span>The root element</h3>
@@ -21990,8 +21992,9 @@
-
+<!--PEERCONNECTION-->
<h3 id=embedded-content-1><span class=secno>4.8 </span>Embedded content</h3>
+<!--PEERCONNECTION-->
<h4 id=the-img-element><span class=secno>4.8.1 </span>The <dfn><code>img</code></dfn> element</h4>
@@ -26265,8 +26268,9 @@
</div>
-
+<!--PEERCONNECTION-->
<h4 id=media-elements><span class=secno>4.8.10 </span>Media elements</h4>
+<!--PEERCONNECTION-->
<p><dfn id=media-element title="media element">Media elements</dfn>
(<code><a href=#the-audio-element>audio</a></code> and <code><a href=#the-video-element>video</a></code>, in this specification)
@@ -26378,9 +26382,13 @@
present audio data, or video and audio data, to the user. This is
referred to as <dfn id=media-data>media data</dfn> in this section, since this
section applies equally to <a href=#media-element title="media element">media
- elements</a> for audio or for video. The term <dfn id=media-resource>media
- resource</dfn> is used to refer to the complete set of media data,
- e.g. the complete video file, or complete audio file.</p>
+ elements</a> for audio or for video.
+<!--PEERCONNECTION-->
+ The term <dfn id=media-resource>media resource</dfn> is used to refer to the complete
+ set of media data, e.g. the complete video file, or complete audio
+ file.
+<!--PEERCONNECTION-->
+ </p>
<p>A <a href=#media-resource>media resource</a> can have multiple audio and video
tracks. For the purposes of a <a href=#media-element>media element</a>, the video
@@ -28845,8 +28853,9 @@
</div>
-
+<!--PEERCONNECTION-->
<h5 id=media-resources-with-multiple-media-tracks><span class=secno>4.8.10.10 </span>Media resources with multiple media tracks</h5>
+<!--PEERCONNECTION-->
<p>A <a href=#media-resource>media resource</a> can have multiple embedded audio
and video tracks. For example, in addition to the primary video and
@@ -28897,16 +28906,19 @@
</div>
+<!--PEERCONNECTION-->
<h6 id=tracklist-objects><span class=secno>4.8.10.10.1 </span><code><a href=#tracklist>TrackList</a></code> objects</h6>
<!-- should probably move this section out since it is also used by
the video conferencing stuff -->
+<!--PEERCONNECTION-->
<p>The <code><a href=#multipletracklist>MultipleTrackList</a></code> and
<code><a href=#exclusivetracklist>ExclusiveTrackList</a></code> interfaces, used by the attributes
defined in the previous section, are substantially similar. Their
common features are defined in the <code><a href=#tracklist>TrackList</a></code> interface,
from which they both inherit.</p>
+<!--PEERCONNECTION-->
<pre class=idl>interface <dfn id=tracklist>TrackList</dfn> {
readonly attribute unsigned long <a href=#dom-tracklist-length title=dom-TrackList-length>length</a>;
@@ -29191,6 +29203,7 @@
selection -->
</div>
+<!--PEERCONNECTION-->
<h5 id=synchronising-multiple-media-elements><span class=secno>4.8.10.11 </span>Synchronising multiple media elements</h5>
Modified: source
===================================================================
--- source 2011-05-12 06:58:07 UTC (rev 6130)
+++ source 2011-05-12 19:10:17 UTC (rev 6131)
@@ -70,7 +70,7 @@
W3C version does not include some newer features, such as:</p>
<ul class="brief">
- <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--PEERCONTROLLER-->
+ <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
<li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li> <!--PING-->
<li>The <span>WebVTT</span> format and some <span>text track</span> API features.</li> <!--TTVTT-->
<li>Rules for <a href="#atom">converting HTML to Atom</a>.</li> <!--MD-->
@@ -13993,7 +13993,9 @@
+<!--START rtc--><!--PEERCONNECTION-->
<h2 id="semantics">The elements of HTML</h2>
+<!--END rtc--><!--PEERCONNECTION-->
<h3>The root element</h3>
@@ -23625,8 +23627,9 @@
-
+<!--START rtc--><!--PEERCONNECTION-->
<h3>Embedded content</h3>
+<!--END rtc--><!--PEERCONNECTION-->
<h4>The <dfn><code>img</code></dfn> element</h4>
@@ -28388,8 +28391,9 @@
</div>
-
+<!--START rtc--><!--PEERCONNECTION-->
<h4>Media elements</h4>
+<!--END rtc--><!--PEERCONNECTION-->
<p><dfn title="media element">Media elements</dfn>
(<code>audio</code> and <code>video</code>, in this specification)
@@ -28506,9 +28510,13 @@
present audio data, or video and audio data, to the user. This is
referred to as <dfn>media data</dfn> in this section, since this
section applies equally to <span title="media element">media
- elements</span> for audio or for video. The term <dfn>media
- resource</dfn> is used to refer to the complete set of media data,
- e.g. the complete video file, or complete audio file.</p>
+ elements</span> for audio or for video.
+<!--START rtc--><!--PEERCONNECTION-->
+ The term <dfn>media resource</dfn> is used to refer to the complete
+ set of media data, e.g. the complete video file, or complete audio
+ file.
+<!--END rtc--><!--PEERCONNECTION-->
+ </p>
<p>A <span>media resource</span> can have multiple audio and video
tracks. For the purposes of a <span>media element</span>, the video
@@ -31451,8 +31459,9 @@
</div>
-
+<!--START rtc--><!--PEERCONNECTION-->
<h5>Media resources with multiple media tracks</h5>
+<!--END rtc--><!--PEERCONNECTION-->
<p>A <span>media resource</span> can have multiple embedded audio
and video tracks. For example, in addition to the primary video and
@@ -31509,16 +31518,19 @@
</div>
+<!--START rtc--><!--PEERCONNECTION-->
<h6><code>TrackList</code> objects</h6>
<!-- should probably move this section out since it is also used by
the video conferencing stuff -->
+<!--END rtc--><!--PEERCONNECTION-->
<p>The <code>MultipleTrackList</code> and
<code>ExclusiveTrackList</code> interfaces, used by the attributes
defined in the previous section, are substantially similar. Their
common features are defined in the <code>TrackList</code> interface,
from which they both inherit.</p>
+<!--START rtc--><!--PEERCONNECTION-->
<pre class="idl">interface <dfn>TrackList</dfn> {
readonly attribute unsigned long <span title="dom-TrackList-length">length</span>;
@@ -31849,6 +31861,7 @@
selection -->
</div>
+<!--END rtc--><!--PEERCONNECTION-->
<h5>Synchronising multiple media elements</h5>
@@ -83951,7 +83964,7 @@
"justifycenter", "justifyright", "justifyfull", "indent", "outdent"
-->
-<!--END w3c-html--><!--PEERCONNECTION-->
+<!--START rtc--><!--END w3c-html--><!--PEERCONNECTION-->
<div data-component="other Hixie drafts (editor: Ian Hickson)">
<h2>Video conferencing and peer-to-peer communication</h2>
@@ -85985,7 +85998,7 @@
</div>
-<!--START w3c-html--><!--PEERCONNECTION-->
+<!--END rtc--><!--START w3c-html--><!--PEERCONNECTION-->
<!--END html--><!--END dev-html--><!--END w3c-html-->
@@ -107919,7 +107932,7 @@
<!--END microdata--><!--START w3c-html--><!--MD-->
-<!--END w3c-html--><!--PEERCONNECTION-->
+<!--START rtc--><!--END w3c-html--><!--PEERCONNECTION-->
<h3><dfn><code>application/html-peer-connection-data</code></dfn></h3>
<p>This registration is for community review and will be submitted
@@ -108001,7 +108014,7 @@
<p>Fragment identifiers used with <code>text/html</code> resources
refer to <span>the indicated part of the document</span>.</p>
-<!--START w3c-html--><!--PEERCONNECTION-->
+<!--END rtc--><!--START w3c-html--><!--PEERCONNECTION-->
<!--END w3c-html--><!--PING-->
@@ -111816,7 +111829,7 @@
<!--START html-device--><!--START microdata--><!--START 2dcontext--><!--START postmsg--><!--START w3c-html-->
<!--START websocket-api--><!--START storage--><!--START eventsource--><!--START workers-->
<!--START whatwg-workers--><!--START vocabs--><!--START vCard--><!--START vEvent--><!--START work-->
-<!--START webvtt-->
+<!--START webvtt--><!--START rtc-->
<h2 class="no-num" id="references">References</h2><!--REFS-->
@@ -112696,7 +112709,7 @@
</dl>
-<!--END webvtt-->
+<!--END webvtt--><!--END rtc-->
<!--END whatwg-workers--><!--END vocabs--><!--END vCard--><!--END vEvent--><!--END work-->
<!--END websocket-api--><!--END storage--><!--END eventsource--><!--END workers-->
<!--END html-device--><!--END microdata--><!--END 2dcontext--><!--END postmsg--><!--END w3c-html-->
@@ -113478,10 +113491,10 @@
<li><img alt="A calendar grid with a clock in the upper right
hand corner." src="sample-datetime-ui-3"></li>
-->
-<!--START webvtt-->
+<!--START webvtt--><!--START rtc-->
</body>
</html>
-<!--END webvtt-->
+<!--END webvtt--><!--END rtc-->
<!--END html--><!--END dev-html--><!--END w3c-html-->
<!--END complete--><!--END epub-->
<!--END validation-->
\ No newline at end of file
More information about the Commit-Watchers
mailing list