--- a/mpreq/MPTF-ADB-Requirements.html Fri Apr 13 13:03:37 2012 -0600
+++ b/mpreq/MPTF-ADB-Requirements.html Wed Apr 18 14:55:09 2012 -0600
@@ -12,7 +12,7 @@
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "WD",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "mptf-adb-rq",
@@ -111,6 +111,38 @@
<dl>
<dt><dfn>programme</dfn> (program)</dt>
<dd>A programme (program) comprises a single period of audio visual content. It is usually expected to be labeled in content directories or television programme guides as a single entity. This might include an episode of a television programme, a radio programme, or a movie.</dd>
+ <dt><dfn>Adaptive Bit Rate</dfn></dt>
+ <dd>Adaptive bit rate is ...</dd>
+ <dt><dfn>Open Source</dfn></dt>
+ <dd>Open source is ...</dd>
+ <dt><dfn>Common Time Base</dfn></dt>
+ <dd>Common time base is ...</dd>
+ <dt><dfn>Trick Play</dfn></dt>
+ <dd>Trick play is ...</dd>
+ <dt><dfn>Media Track</dfn></dt>
+ <dd>Media track is ...</dd>
+
+ <dt><dfn>Active IDs</dfn></dt>
+ <dd>The set of <a href="#source-id">source IDs</a> that are providing the <code><a href="http://dev.w3.org/html5/spec/media-elements.html#dom-videotrack-selected">selected video track</a></code> and the <code><a href="http://dev.w3.org/html5/spec/media-elements.html#dom-audiotrack-enabled">enabled audio tracks</a></code>.</dd>
+
+ <dt id="source-id">Source ID</dt>
+ <dd>An ID registered with <code><a href="#dom-sourceaddid">sourceAddId()</a></code> that identifies a distinct sequence of <a href="#init-segment">initialization segments</a> & <a href="#media-segment">media segments</a> appended to a specific <a href="#source-buffer">source buffer</a>.</dd>
+
+ <dt id="source-buffer">Source Buffer</dt>
+ <dd>A hypothetical buffer that contains the <a href="#media-segment">media segments</a> for a particular <a href="#source-id">source ID</a>. When <a href="#media-segment">media segments</a> are passed to <code><a href="#dom-sourceappend">sourceAppend()</a></code> they update the state of this buffer. The source buffer only allows a single <a href="#media-segment">media segment</a> to cover a specific point in the presentation timeline of each track. If a <a href="#media-segment">media segment</a> gets appended that contains media data overlapping (in presentation time) with media data from an existing segment, then the new media data will override the old media data. Since <a href="#media-segment">media segments</a> depend on <a href="#init-segment">initialization segments</a> the source buffer is also responsible for maintaining these associations. During playback, the media element pulls segment data out of the source buffers, demultiplexes it if necessary, and enqueues it into <a href="#track-buffer">track buffers</a> so it will get decoded and displayed. <code><a href="#dom-sourcebuffered">sourceBuffered()</a></code> describes the time ranges that are covered by <a href="#media-segment">media segments</a> in the source buffer.</dd>
+
+ <dt id="track-buffer">Track Buffer</dt>
+ <dd>A hypothetical buffer that represents initialization and media data for a single <code><a href="http://dev.w3.org/html5/spec/media-elements.html#audiotrack">AudioTrack</a></code> or <code><a href="http://dev.w3.org/html5/spec/media-elements.html#videotrack">VideoTrack</a></code> that has been queued for playback. This buffer may not exist in actual implementations, but it is intended to represent media data that will be decoded no matter what <a href="#media-segment">media segments</a> are appended to update the <a href="#source-buffer">source buffer</a>. This distinction is important when considering appends that happen close to the current playback position. Details about transfers between the <a href="#source-buffer">source buffer</a> and track buffers are given <a href="#source-buffer-to-track-buffer">here</a>.</dd>
+
+ <dt id="init-segment">Initialization Segment</dt>
+ <dd>A sequence of bytes that contains all of the initialization information required to decode a sequence of <a href="#media-segment">media segments</a>. This includes codec initialization data, trackID mappings for multiplexed segments, and timestamp offsets (e.g. edit lists). A moov box in MPEG4 is as an initialization segment. For WebM, the concatenation of the the EBML Header, Segment Header, Info element, and Tracks element are used as an initialization segment.</dd>
+
+ <dt id="media-segment">Media Segment</dt>
+ <dd>A sequence of bytes that contain packetized & timestamped media data for a portion of the presentation timeline. Media segments are always associated with the most recently appended <a href="#init-segment">initialization segment</a>. WebM cluster elements and MP4 movie fragment boxes are examples of media segments.</dd>
+
+ <dt id="random-access-point">Random Access Point</dt>
+ <dd>A position in a <a href="#media-segment">media segment</a> where decoding and continuous playback can begin without relying on any previous data in the segment. For video this tends to be the location of I-frames. In the case of audio, most audio frames can be treated as a random access point. Since video tracks tend to have a more sparse distribution of random access points, the location of these points are usually considered the random access points for multiplexed streams.</dd>
+
</dl>
</section>
@@ -213,7 +245,7 @@
</section>
<section>
- <h3><a href=http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html>Mediasource specification (WIP) (Aaron Colwell, Adrian Bateman, Mark Watson)</a></h3>
+ <h3><a href=http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html>Mediasource specification (WIP) (Aaron Colwell, Kilroy Hughes, Mark Watson)</a></h3>
<p>Description...</p>
</section>
--- a/mpreq/MPTF-CP-Requirements.html Fri Apr 13 13:03:37 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html Wed Apr 18 14:55:09 2012 -0600
@@ -12,7 +12,7 @@
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "WD",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "mptf-cp-rq",