--- a/mpreq/MPTF-ADB-Requirements.html	Wed Apr 18 16:49:58 2012 -0600
+++ b/mpreq/MPTF-ADB-Requirements.html	Thu Apr 19 08:55:48 2012 -0600
@@ -153,6 +153,7 @@
         
         <section>
             <h3>General</h3>
+        
                 <section>
                 <h4>Compatibility with widely deployed standards</h4>
                     <p>One of the primary purposes for standardizing the way the media elements use adaptive bitrate streaming is to enable different existing and future adaptive bitrate streming methods to work consistently with HTML5 media tags. Therefore, media tags must work with the widely deployed adaptive bitrate methods that are available now.</p>

--- a/mpreq/MPTF-CP-Requirements.html	Wed Apr 18 16:49:58 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html	Thu Apr 19 08:55:48 2012 -0600
@@ -121,66 +121,77 @@
         
         <section>
             <h3>General</h3>
-                <section>
-                <h4>Compatibility with widely deployed standards</h4>
-                    <p>Several ...</p>
-                </section>
- 
-                <section>
-                <h4>The &lt;video&gt; tag should be used to specify the video in HTML.</h4>
-                    <p>Desription...</p>
-                </section>
-        
-                <section>
-                <h4>A common time reference must be unambiguously defined for combining tracks with different time references and for "continuous" tracks. Overlapping track segments must also be handled. (DASH may provide a reasonable model.)</h4>
-                    <p>Desription...</p>
-                </section>
+        <section>
+        <h4>Content protection methods must enable the rights of the user as specified in the agreement (See item 1 in Backgroud section above).</h4>
+        <p>Description...</p>
+        </section>
         
-                <section>
-                <h4>Search and trick-play must be unambiguously defined in the context of this common time reference (e.g. anchor point and offset).</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>The ability of the user agent to play a piece of content must be determined quickly and with reasonable accuracy (e.g. using CanPlayType(codec, level, profile) or other means)</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>The ABR media system must not advantage one specific method over another.</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>The ABR methods must work with "open source" browsers.</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>ABR media must be useable in HTML5</h4>
-                    <p>Desription...</p>
-
-                    <p>SUGGESTION: Drop this requirement. Some of it is handed by requirement 4. The rest would be handled in Script. Therefore, it is not necessary. ---The particular ABR system required to use the content must be identifiable.</p>
-                </section>
+        <section>
+        <h4>Content protection methods must protect the rights of the content owners as specified in the agreement.</h4>
+        <p>Description...</p>
+        </section>
         
-                <section>
-                <h4>Any parameters required for use of the ABR system must be identified and specifiable.</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>Specific errors relevant to ABR media must be identified and reportable.</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>It should be possible to seamlessly splice content with a discontinuous timeline (such as advertising) into the presentation [this requirement may conflict with (2)?]</h4>
-                    <p>Desription...</p>
-                </section>
-
-                <section>
-                <h4>(Others)</h4>
-                </section>
+        <section>
+        <h4>Content protection methods must protect the rights of the distribution service provider as specified in the agreement.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>The content protection system must not advantage one specific container format over another.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>The content protection solution must support at least one mandatory method that can be used to enable interoperability between different systems.</h4>
+        <p>Description...</p>
+        <h5>This method should be unencumbered with IPR</h5>
+        </section>
+        
+        <section>
+        <h5>Content protection methods must work with "open source" browsers. Specifically, the interface defined by the proposed solution should be implementable in any browser without requiring any privileged information. This scope of this requirement is limited to the interface defined in the proposed solution.</h5>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>Content protection must be useable in HTML5</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>(consensus not yet reached) Content protection must be useable with specific HTML5 features such as media elements (and features (such as timed tracks) within these elements).</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>(consensus not yet reached) Media element features that are available in an implementation must be available for encrypted content as well as unencrypted content.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>The particular content protection method required to use the content must be identifiable.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>Any parameters required for use of the content protection method must be identified and specifiable.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>Specific errors relevant to content protections must be identified and reportable.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>The content protection method must be compatible with the (new) media source element as described in the adaptive bit rate proposal.</h4>
+        <p>Description...</p>
+        </section>
+        
+        <section>
+        <h4>Others...</h4>
+        <p>Description...</p>
+        </section>
+        
         </section>
 
     </section>

Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed