--- a/mpreq/MPTF-CP-Requirements.html Mon Jul 02 14:12:36 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html Mon Jul 02 14:56:31 2012 -0600
@@ -206,7 +206,7 @@
<section>
<h4>Container Format</h4>
- <h5>The content protection system must not advantage one
+ <h5>The content protection solution (the standard interface to support content protection) must not advantage one
specific container format over another.</h5>
<p>Specifically, the choice of container format should not
prevent the content protection system from operating.</p>
@@ -214,7 +214,7 @@
<section>
<h4>Mandatory Baseline</h4>
- <h5>The content protection solution must support at least one
+ <h5>The content protection solution (the standard interface to support content protection) must support at least one
mandatory method that can be used to enable interoperability
between different systems.</h5>
<p>Support for a baseline content protection solution allows at
@@ -224,7 +224,7 @@
<section>
<h4>Browser Independence</h4>
- <h5>Content protection methods must work with "open source"
+ <h5>The content protection solution (the standard interface defined to support content protection) must work with "open source"
browsers</h5>
<p>Specifically, the interface defined by the proposed solution
should be implementable in any browser without requiring any
@@ -264,43 +264,19 @@
</section>
<section>
- <h4>Identifiable Content Protection Method</h4>
- <h5>The particular content protection method required to use
- the content must be identifiable.</h5>
- <p>It must be possible to deduce from the media stream which
- content protection system (if any) is required to decrypt the
- media stream.</p>
- </section>
-
- <section>
- <h4>Common Parameters</h4>
- <h5>Any parameters required for use of the content protection
- method must be identified and specifiable.</h5>
- <p>It must be possible to determine from the media stream, the
- parameters that must be specified in order to decrypt the
- protected media stream. The primary parameters must be common
- across different content protection systems so that the unique
- details of the protection method are not required to be known in
- advance.</p>
- </section>
-
- <section>
<h4>Common Errors</h4>
<h5>Specific errors relevant to content protections must be
identified and reportable.</h5>
- <p>It must be possible to determine from the media stream, the
- possible errors that may occur in the decoding of the protected
- media stream. The primary errors must be common across different
+ <p>The primary errors must be common across different
content protection systems so that the unique details of the
protection method are not required to be known in advance</p>
</section>
<section>
<h4>Adaptive Bit Rate Media</h4>
- <h5>The content protection method must be compatible with the
- (new) media source element as described in the adaptive bit rate
- proposal.</h5>
- <p>The content protection method must work with adaptive bit
+ <h5>The content protection solution (the standard interface defined to support content protection) must be compatible with
+ adaptive bit rate media.</h5>
+ <p>The content protection solution must work with adaptive bit
rate streaming as well as traditional non-adaptive streaming
methods. This ensures that the content protection systems will
work with emerging streaming media types.</p>
@@ -365,18 +341,18 @@
the rights of users, owners and distributors of digital media
according to a mutually supported contract. The use case does not
stipulate the terms of any contract, it just requires the
- provision of tools that enable the terms of an anticipated
- contract. For users, this means provision of tools that can
- accurately determine a user's rights and tools allow or deny user
+ specification of features that enable the terms of an anticipated
+ contract. For users, this means specification of features that can
+ accurately determine a user's rights and the features to allow or deny user
access to content based on those rights.</p>
- <p>For a content owner, this use case requires the provision
- of tools that allow the owner to ensure compensation for the use
+ <p>For a content owner, this use case requires the specification
+ of features that allow the owner to ensure compensation for the use
of content owned by the owner according to the contract between
the owner, distributors and users. For the distributor, this use
- case requires the provision of tools that enable the secure
+ case requires the specification of features that enable the secure
distribution of content between owners and users such that the
contract between owners and users can be accurately executed and
- vioation of that contract can be prefented.</p>
+ vioation of that contract can be prevented.</p>
<p>Since all systems for providing the protection described
above are vulnerable and violation of the protections is
potentially lucrative, the system must be flexible enough to
@@ -552,16 +528,6 @@
<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>
@@ -677,11 +643,6 @@
<td>Playback of encrypted content</td>
<td><a href="#encrypted-content" 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>
Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed