Added more to the use cases
authorClarke Stevens <c.stevens@cablelabs.com>
Thu, 10 May 2012 08:53:24 -0600
changeset 57 58c03016a085
parent 56 295c06616c5d
child 58 4dc173eb5b23
Added more to the use cases
mpreq/MPTF-CP-Requirements.html
mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate
--- a/mpreq/MPTF-CP-Requirements.html	Thu May 10 06:51:33 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html	Thu May 10 08:53:24 2012 -0600
@@ -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 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.</p>
             
             <p>Possible implementation:</p>
             <ul>
@@ -328,7 +328,7 @@
             <dl>
             <dt>Description</dt>
             <dd>
-            <p>A ...</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 that implements the baseline CDM.</p>
             
             <p>Possible implementation:</p>
             <ul>
@@ -369,7 +369,7 @@
             <dl>
             <dt>Description</dt>
             <dd>
-            <p>A ...</p>
+            <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>Possible implementation:</p>
             <ul>
@@ -413,12 +413,12 @@
             </section>
             
             <section>
-            <h3>U5. Support for Playback of Encrypted Content</h3>
+            <h3>U5. Support for Playback of Encrypted Adaptive Bit-rate Content</h3>
             
             <dl>
             <dt>Description</dt>
             <dd>
-            <p>A ...</p>
+            <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>Possible implementation:</p>
             <ul>
Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed