--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/mpreq/MPTF-ADB-Requirements.html Fri Apr 13 13:03:37 2012 -0600
@@ -0,0 +1,235 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>MPTF Requirements for Adaptive Bit Rate Streaming</title>
+ <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+ <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script class='remove'>
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "mptf-adb-rq",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ // subtitle : "an excellent document",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ // copyrightStart: "2005"
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ // previousPublishDate: "1977-03-15",
+ // previousMaturity: "WD",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Clarke Stevens", url: "http://example.org/",
+ company: "CableLabs", companyURL: "http://www.cablelabs.com" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [
+ // { name: "Your Name", url: "http://example.org/",
+ // company: "Your Company", companyURL: "http://example.com/" },
+ //],
+
+ // name of the WG
+ wg: "Media Pipeline Task Force of the Web & TV IG",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/webtv/wiki/MPTF",
+
+ // name (without the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "spec-writers-anonymous",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "",
+ };
+ </script>
+ </head>
+ <body>
+ <section id='abstract'>
+ The MPTF is a subset of the Web and TV Interest Group. The goal of MPTF is to discuss requirements placed on the HTML5 video, audio and media interfaces by media formats that used for Web and TV applications. The MPTF also proposes APIs that meet these requirements.
+ </section>
+
+ <section id="sotd">
+ Recommendations in this document...
+ </section>
+
+ <section>
+ <h2>Introduction</h2>
+ <p>A majority of Internet traffic is now streaming video.</p>
+
+ <p>However, there are currently no standards or common conventions to provide commercial quality IP streaming video across different platforms and between unrelated companies.</p>
+ </section>
+
+ <section>
+ <h2>Conformance</h2>
+
+ <p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
+
+ <p>The key words MUST, MUST NOT, SHALL, SHOULD and SHOULD NOT in this specification are to be interpreted as described in RFC 2119 [[RFC2119]].</p>
+
+ <p>This specification only applies to one class of product: <dfn>W3C Technical Reports</dfn>. A number of specifications may be created to address the requirements enumerated in this document. In some cases the union of multiple parts of different specifications may be needed to address a single requirement. Nevertheless, this document speaks only of <dfn>conforming specifications</dfn>.</p>
+
+ <p>Conforming specifications are ones that address one or more requirements listed in this document. Conforming specifications should attempt to address SHOULD level requirements requirements unless there is a technically valid reason not to do so.</p>
+ </section>
+
+ <section>
+ <h2>Terminology</h2>
+
+ <dl>
+ <dt><dfn>programme</dfn> (program)</dt>
+ <dd>A programme (program) comprises a single period of audio visual content. It is usually expected to be labeled in content directories or television programme guides as a single entity. This might include an episode of a television programme, a radio programme, or a movie.</dd>
+ </dl>
+ </section>
+
+ <section>
+ <h2>MPTF Requirements for Adaptive Bit Rate Streaming</h2>
+
+ <p>This section list the requirements that conforming specification(s) would need to adopt in order to ensure a common interface and interpretation for the playback and control of adaptive bit rate media. These requirements are the result of an interactive process of feedback and discussion within the Media Pipeline Task Force of the Web and TV Interest Group</p>
+
+ <section>
+ <h3>General</h3>
+ <section>
+ <h4>Compatibility with widely deployed standards</h4>
+ <p>Several ...</p>
+ </section>
+
+ <section>
+ <h4>The <video> 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>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>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>
+
+ </section>
+
+ <section>
+ <h2>Use Cases</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Security</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Next Steps</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Proposals</h2>
+
+ <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>
+ </section>
+
+ <section>
+ <h3><a href=http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html>Mediasource specification (WIP) (Aaron Colwell, Adrian Bateman, Mark Watson)</a></h3>
+
+ <p>Description...</p>
+ </section>
+ </section>
+
+ <section>
+ <h2>Related Works</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section class='appendix'>
+ <h2>Acknowledgements</h2>
+ <p>
+ Many thanks to ...
+ </p>
+ </section>
+ </body>
+</html>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/mpreq/MPTF-CP-Requirements.html Fri Apr 13 13:03:37 2012 -0600
@@ -0,0 +1,235 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>MPTF Requirements for Content Protection</title>
+ <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+ <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script class='remove'>
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "mptf-cp-rq",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ // subtitle : "an excellent document",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ // copyrightStart: "2005"
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ // previousPublishDate: "1977-03-15",
+ // previousMaturity: "WD",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Clarke Stevens", url: "http://example.org/",
+ company: "CableLabs", companyURL: "http://www.cablelabs.com" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [
+ // { name: "Your Name", url: "http://example.org/",
+ // company: "Your Company", companyURL: "http://example.com/" },
+ //],
+
+ // name of the WG
+ wg: "Media Pipeline Task Force of the Web & TV IG",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/webtv/wiki/MPTF",
+
+ // name (without the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "spec-writers-anonymous",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "",
+ };
+ </script>
+ </head>
+ <body>
+ <section id='abstract'>
+ The MPTF is a subset of the Web and TV Interest Group. The goal of MPTF is to discuss requirements placed on the HTML5 video, audio and media interfaces by media formats that used for Web and TV applications. The MPTF also proposes APIs that meet these requirements.
+ </section>
+
+ <section id="sotd">
+ Recommendations in this document...
+ </section>
+
+ <section>
+ <h2>Introduction</h2>
+ <p>A majority of Internet traffic is now streaming video.</p>
+
+ <p>However, there are currently no standards or common conventions in HTML to provide the level of content protection required by some content owners. As a result, content owners must support multiple, non-interoperable private content protection solutions.</p>
+ </section>
+
+ <section>
+ <h2>Conformance</h2>
+
+ <p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
+
+ <p>The key words MUST, MUST NOT, SHALL, SHOULD and SHOULD NOT in this specification are to be interpreted as described in RFC 2119 [[RFC2119]].</p>
+
+ <p>This specification only applies to one class of product: <dfn>W3C Technical Reports</dfn>. A number of specifications may be created to address the requirements enumerated in this document. In some cases the union of multiple parts of different specifications may be needed to address a single requirement. Nevertheless, this document speaks only of <dfn>conforming specifications</dfn>.</p>
+
+ <p>Conforming specifications are ones that address one or more requirements listed in this document. Conforming specifications should attempt to address SHOULD level requirements requirements unless there is a technically valid reason not to do so.</p>
+ </section>
+
+ <section>
+ <h2>Terminology</h2>
+
+ <dl>
+ <dt><dfn>programme</dfn> (program)</dt>
+ <dd>A programme (program) comprises a single period of audio visual content. It is usually expected to be labeled in content directories or television programme guides as a single entity. This might include an episode of a television programme, a radio programme, or a movie.</dd>
+ </dl>
+ </section>
+
+ <section>
+ <h2>MPTF Requirements for Adaptive Bit Rate Streaming</h2>
+
+ <p>This section list the requirements that conforming specification(s) would need to adopt in order to ensure a common interface and interpretation for the playback and control of adaptive bit rate media. These requirements are the result of an interactive process of feedback and discussion within the Media Pipeline Task Force of the Web and TV Interest Group</p>
+
+ <section>
+ <h3>General</h3>
+ <section>
+ <h4>Compatibility with widely deployed standards</h4>
+ <p>Several ...</p>
+ </section>
+
+ <section>
+ <h4>The <video> 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>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>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>
+
+ </section>
+
+ <section>
+ <h2>Use Cases</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Security</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Next Steps</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section>
+ <h2>Proposals</h2>
+
+ <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>
+ </section>
+
+ <section>
+ <h3><a href=http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html>Mediasource specification (WIP) (Aaron Colwell, Adrian Bateman, Mark Watson)</a></h3>
+
+ <p>Description...</p>
+ </section>
+ </section>
+
+ <section>
+ <h2>Related Works</h2>
+
+ <p>Paragraph...</p>
+ </section>
+
+ <section class='appendix'>
+ <h2>Acknowledgements</h2>
+ <p>
+ Many thanks to ...
+ </p>
+ </section>
+ </body>
+</html>