--- a/mpreq/MPTF-ADB-Requirements.html	Wed Apr 18 15:31:06 2012 -0600
+++ b/mpreq/MPTF-ADB-Requirements.html	Wed Apr 18 16:18:08 2012 -0600
@@ -155,59 +155,52 @@
             <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,the mediatags must work with the adaptive bitrate methods that are available now.</p>
+                    <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>
                 </section>
  
                 <section>
-                <h4>The &lt;video&gt; tag should be used to specify the video in HTML.</h4>
-                    <p>Desription...</p>
+                <h4>The &lt;video&gt; and &lt;audio&gt; tags should be used to specify video and audio in HTML. </h4>
+                    <p>In the past, the &lt;obj&gt; tag has been used to add non-standard functionality to HTML pages. In order to provide more consistent functionality, the &lt;video&gt; and &lt;audio&gt; elements were added to HTML. This allows for consistent handling of streaming media between different browsers and encoded with different codecs. In order to maintain this consistency, streaming media should be specified with streaming media tags rather than generic tags.</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>
+                    <p>Frequently, it is necessary to synchronize serveral different steaming content sources. For example, audio tracks must be synchronized with streaming video or the experience of watching the video becomes unpleasant. Synchronization is also important for advertising, closed caption and other streaming media features. Since different streaming media sources have different time references, a strategy for synchronizing these different references must be adopted.</p>
+                </section>
+        
+                <section>
+                    <h4>It should be possible to seamlessly splice content with a discontinuous timeline (such as advertising) into the presentation.</h4>
+                    <p>In addition to a common time reference, mapping to that common time reference must be seamless enough to enable continuous playback from sources spliced relative to different time bases.</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>
+                    <p>A common time reference is also important in the context of trick play. Pausing, advancing or rewinding media content must be done accurately and within a common reference. This is necessary in order to advance or rewind to exact locations or the adjust the playback lockation by precise increments.</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>
+                    <p>With media content available from sources around the world, it is important to quickly determine whether various content sources can be rendered. Therefore this determinitaion must be madew with a minimum of overhead.</p>
                 </section>
 
                 <section>
                 <h4>The ABR media system must not advantage one specific method over another.</h4>
-                    <p>Desription...</p>
+                    <p>HTML aspires to be a level playing field. This philosophy enables innovation to flourish and allows superior solutions to become quickly implemnted and adopted. ABR media systems are and should continue to be innovative solutions within this spirit of openness.</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>
+                    <p>The ability for a browser vendor to implement playback of ABR media must not be restricted by the requirements of this document.</p>
                 </section>
         
                 <section>
                 <h4>Any parameters required for use of the ABR system must be identified and specifiable.</h4>
-                    <p>Desription...</p>
+                    <p>While specific implementations may include vendor-specific parameters for special features, the parameters required for basic playback should be publicly specified.</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>
+                    <p>While specific implementations may include vendor-specific error codes, the error codes required for basic operation and diagnosis should be publicly specified.</p>
                 </section>
 
                 <section>

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