--- a/mpreq/MPTF-ADB-Requirements.html Thu May 10 08:53:24 2012 -0600
+++ b/mpreq/MPTF-ADB-Requirements.html Thu May 31 08:48:59 2012 -0600
@@ -127,9 +127,6 @@
<dt><dfn>Media Track</dfn></dt>
<dd>Media tracks are individual streams of media that may optionally be combined into an aggregated track. For example a video track and one or more audio tracks are typically combined in a feature film. Other media tracks include closed captioning, alternate language tracks and special features.</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><dfn>Source ID</dfn></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>
--- a/mpreq/MPTF-CP-Requirements.html Thu May 10 08:53:24 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html Thu May 31 08:48:59 2012 -0600
@@ -115,7 +115,7 @@
</section>
<section>
- <h2>MPTF Requirements for Adaptive Bit Rate Streaming</h2>
+ <h2>MPTF Requirements for Content Protection</h2>
<p>This section list the requirements that conforming specification(s) would need to adopt in order to ensure a common interface and interpretation for the playback and control of adaptive bit rate media. These requirements are the result of an interactive process of feedback and discussion within the Media Pipeline Task Force of the Web and TV Interest Group</p>
@@ -287,7 +287,7 @@
<dl>
<dt>Description</dt>
<dd>
- <p>This use case describes the need for a system that is flexible enough to support different implementations of content protection. Specifically, it must not unreasonably limit the container format to a design that excludes common implementations.</p>
+ <p>This use case describes the need for a system that is flexible enough to support different implementations of content protection. Specifically, it must not unreasonably limit the container format to a design that excludes common implementations. The system must be flexible enough to multiple content protection systems simultaneously. For example, it must be capble of playing back programming in one supported protection system, then switching to another supported protection system on a subsequent piece of programming.</p>
<p>Possible implementation:</p>
<ul>
@@ -328,7 +328,7 @@
<dl>
<dt>Description</dt>
<dd>
- <p>This use case describes a baseline CDM that can be implemented by a user agent in any browser. A baseline CDM ensures that there is a way for content to be encoded that allows for interoperability between implementations. If a content provider encodes content compatible with the baseline CDM, it should be playable on any client platform that implements the baseline CDM.</p>
+ <p>This use case describes a baseline CDM that can be implemented by a user agent in any browser. A baseline CDM ensures that there is a way for content to be encoded that allows for interoperability between implementations. If a content provider encodes content compatible with the baseline CDM, it should be playable on any client platform.</p>
<p>Possible implementation:</p>
<ul>
@@ -359,6 +359,14 @@
<td>Define a mandatory basline content protection method</td>
<td><a href="#mandatory-baseline" class="sectionRef"></a></td>
</tr>
+ <tr>
+ <td>Common parameters used to control content-protection method</td>
+ <td><a href="#common-parameters" class="sectionRef"></a></td>
+ </tr>
+ <tr>
+ <td>Identification of the content-protection method used</td>
+ <td><a href="#identifiable-content-protection-method" class="sectionRef"></a></td>
+ </tr>
</table></dd>
</dl>
</section>
@@ -369,7 +377,7 @@
<dl>
<dt>Description</dt>
<dd>
- <p>In this use case, the ability to get access to content is depedent upon the use of compatible content formats and legitimate credentials. These requirements can be met by any browser.</p>
+ <p>In this use case, the ability to get access to content is dependent upon the use of compatible content formats and legitimate credentials. These requirements must be implementatable by any browser and the implementation must report common errors.</p>
<p>Possible implementation:</p>
<ul>
@@ -413,12 +421,12 @@
</section>
<section>
- <h3>U5. Support for Playback of Encrypted Adaptive Bit-rate Content</h3>
+ <h3>U5. The player must support playback of Encrypted Adaptive Bit-rate Content</h3>
<dl>
<dt>Description</dt>
<dd>
- <p>In this use case, adaptive bit-rate encrypted content is played back. The encryption method doesn't limit the ability to play the content. Specifically, the fragmented nature of adaptive bit-rate content doesn't limit the use of the encryption method.</p>
+ <p>In this use case, a player renders encrypted adaptive bit-rate content. The encryption method doesn't limit the ability of the player to play the content. Specifically, the fragmented nature of adaptive bit-rate content doesn't limit the use of the encryption method.</p>
<p>Possible implementation:</p>
<ul>
@@ -453,18 +461,6 @@
<td>Identification of the content-protection method used</td>
<td><a href="#identifiable-content-protection-method" class="sectionRef"></a></td>
</tr>
- <tr>
- <td>Common parameters used to control content-protection method</td>
- <td><a href="#common-parameters" class="sectionRef"></a></td>
- </tr>
- <tr>
- <td>Common errors reported for different content-protection methods</td>
- <td><a href="#common-errors" class="sectionRef"></a></td>
- </tr>
- <tr>
- <td>Support for playback of content-protected adaptive bit-rate media</td>
- <td><a href="#adaptive-bit-rate-media" class="sectionRef"></a></td>
- </tr>
</table></dd>
</dl>
</section>
Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed