--- a/mpreq/MPTF-ADB-Requirements.html Thu May 31 08:48:59 2012 -0600
+++ b/mpreq/MPTF-ADB-Requirements.html Thu Jun 07 01:08:00 2012 -0600
@@ -115,6 +115,12 @@
<dt><dfn>Adaptive Bit Rate</dfn></dt>
<dd>Adaptive bit rate media is characterized by short independent parallel media stream segments that can be individually selected and rendered according to some selective criteria. Typically, the parallel segments are differentiated by a feature such as required bandwidth, image resolution, etc.</dd>
+ <dt><dfn>Adaptive Bit Rate Method</dfn></dt>
+ <dd>An adaptive bit rate method refers to an algorithmically distict approach to implementing adaptive bit rate streaming.</dd>
+
+ <dt><dfn>Adaptive Bit Rate System</dfn></dt>
+ <dd>An adaptive bit rate system refers to a comprehensive implementation of adaptive bit rate streaming. HLS and Smooth Streaming, for example, would be considered adaptive bit rate streaming systems.</dd>
+
<dt><dfn>Open Source</dfn></dt>
<dd>Open source software can be defined in many ways. For the purposes of these requirements it is defined as software that is openly developed and maintained by groups of interested developers. In these requirements, it is not required that open source software may only call other open source software. However, all open interfaces must be sufficiently defined that other open software may be developed to call those same interfaces.</dd>
@@ -195,13 +201,13 @@
<section>
<h4>No ABR Method Preference</h4>
<h5>The ABR media system must not advantage one specific method over another.</h5>
- <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>
+ <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. Support for different ABR systems should not require any proprietary modification of the user agent</p>
</section>
<section>
<h4>Open Source Browsers</h4>
<h5>The ABR methods must work with "open source" browsers.</h5>
- <p>The ability for a browser vendor to implement playback of ABR media must not be restricted by the requirements of this document.</p>
+ <p>The ability for a browser vendor to implement playback of ABR media in accordance with the requirements in this document must be supported.</p>
</section>
<section>
@@ -213,7 +219,7 @@
<section>
<h4>Common Errors</h4>
<h5>Specific errors relevant to ABR media must be identified and reportable.</h5>
- <p>While specific implementations may include vendor-specific error codes, the error codes required for basic operation and diagnosis should be publicly specified.</p>
+ <p>While specific implementations may include vendor-specific error codes, the error codes required for basic operation and diagnosis should be publicly specified. However, the particular ABR systems to be supported is an implementation decision.</p>
</section>
<section>
@@ -606,7 +612,11 @@
</section>
</section>
+ <h3>Other Issues or Use Cases</h3>
+ <h2>Byte Range, Events, Events at start of request</h2>
+ <h2>(Others?)</h2>
</section>
+
<section>
<h2>Security</h2>
@@ -616,7 +626,9 @@
<section>
<h2>Identified Gaps</h2>
-
+ <p>
+ Are these really gaps?
+ </p>
<section>
<h3>Buffer Management</h3>
</section>
@@ -636,7 +648,7 @@
<ul>
<li>Make any necessary changes or refinements in this document</li>
- <li>Submit this document to appropriat W3C WC for development of specification.</li>
+ <li>Submit this document to the appropriate W3C WC (likely HTML) for development of specification.</li>
</ul>
</section>
@@ -646,26 +658,20 @@
<section>
<h3><a href=http://www.w3.org/2011/webtv/wiki/MPTF/HTML_adaptive_calls>Adaptive Bitrate calls for HTML5 <video> tag (WIP) (Duncan Rowden)</a></h3>
- <p>Description...</p>
+ <p>This proposal refers to work done in WHATWG regarding three implementation methods and their associated APIs.</p>
</section>
<section>
- <h3><a href=http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html>Mediasource specification (WIP) (Aaron Colwell, Kilroy Hughes, Mark Watson)</a></h3>
+ <h3><a href=http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html>Mediasource specification (Aaron Colwell, Kilroy Hughes, Mark Watson)</a></h3>
- <p>Description...</p>
+ <p>This proposal was jointly developed by Microsoft, Google and Netflix. It is comprehensive and is intended to meet the requirements described in this document.</p>
</section>
</section>
- <section>
- <h2>Related Works</h2>
-
- <p>Paragraph...</p>
- </section>
-
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>
- Many thanks to ...
+ Many thanks to the members of the Media Pipeline Task Force of the W3C Web & TV Interest Group who collaborated to create this requirements document and reviewed the proposals to be submitted to the HTML WG for inclusion in the HTML specification.
</p>
</section>
</body>
Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed