--- a/tvprofile/tv-src.html Wed Jan 04 16:37:00 2012 +0100
+++ b/tvprofile/tv-src.html Thu Jan 05 17:06:55 2012 +0100
@@ -136,6 +136,15 @@
<section>
<h2>Scope</h2>
+ The scope of this document is limited to:
+ <ul>
+ <li>provide references to a set of languages that shall be supported by <a>device</a>s and can be used by <a title="content provider">content</a> and <a>service provider<a>s to author content and services to be presented to the <a>end user</a>.</li>
+ <li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
+ </ul>
+ <p>
+ The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
+ <p>
+ The scope of this document is not to describe a unique end-to-end delivery system. In particular, mandating a specific end-to-end network configuration (including network protocols, video codecs, video streaming technologies and so on) is out of scope for this document. Nonetheless this document may describe how some specific technologies may be combined together in order to provide a functional <a>TV service</a>.
</section>
</section>
@@ -149,41 +158,71 @@
<p>
For the purposes of the present document, the following definitions apply:
<ul>
- <li><dfn>STB</dfn>: a set-top box (STB) is a device that can be connected to a <a>TV set</a> or other display devices to enable presentation of content coming from a variety of sources - such as received via <a>broadcast network</a>s, <a>broadband network</a>s or streamed from other devices.</li>
+ <li><dfn>STB</dfn>: a set-top box (STB) is a <a>device</a> that can be connected to a <a>TV set</a> or other display devices to enable presentation of content coming from a variety of sources - such as received via <a>broadcast network</a>s, <a>broadband network</a>s or streamed from other devices.</li>
<li><dfn>TV set</dfn>: A display device that can presents content from a variety of sources - such as received via <a>broadcast network</a>s,<a>broadband network</a>s or streamed from other devices.</li>
+ <li><dfn>TV service</dfn>: A providing commercial video service that may include elements of interactivity and provides a coherent user experience. TV services are usually divided into two main groups: <dfn title="schedule service">scheduled</dfn> or <dfn title="linear service">linear</dfn> services are the ones that have to be consumed by the user at the particular point in time when they are offered (e.g. a broadcast TV channel); <dfn title="on-demand service">on-demand</dfn> services are the ones that can be consumed by the user at any point in time (e.g. web video portals).</li>
+ <li><dfn>device</dfn>: for the purposes of this document, a device is any piece of equipment owned by the user that is able to presentat <a>TV service</a>s to the end user. Note that this is a generic term that also includes the <a>TV set</a> and <a>STB</a> terms defined in this document.</li>
<li><dfn>broadband network</dfn>: bi-directional IP connection</li>
<li><dfn>broadcast network</dfn>: classical uni-directional TV broadcast networks such as DVB, ATSC, ISDB.
+ <li><dfn>user</dfn>: is the consumer of <a>TV service</a>s. Traditionally TV services have been consumed only via <a>TV set</a>s or <a>STB</a>s connected to a display. Nowadays end users have a wide range of devices (e.g. PC, laptops,smartphones, tablets) available both in their home and outside and expect to be able to access to services from any device.</li>
+ <li><dfn>service provider</dfn>: aggregates content from one or more <a>content provider</a>s and offer them to the end user for consumption.</li>
+ <li><dfn>content provider</dfn>: the author of a piece of content that is later sold or licensed to <a>service provider</a>s and consumed by the <a>user</a>s.</li>
</ul>
</p>
</section>
</section>
-
+<section class="informative">
+<h2>Overview</h2>
+
+ <section>
+ <h2>System Architecture</h2>
+ <div class="note"> TODO: briefly describe the system architecture, just to explain how content is delivered to devices via a multitude of networks and which components of the overall architecture are in scope for this document. This section is just informative and should help the reader to understand which parts of the system architecture are covered by this spec but should not try to be an encyclopedic explanation of TV systems </div>
+ </section>
-<section>
-<h2>Overview</h2>
+ <section>
+ <h2>Application Model</h2>
+ The term <dfn>application</dfn> is used to refer to a collection of documents and associated resources that can be used to provide a <a>TV service</a> and are authored using a set of languages commonly referred to as "web technologies" or "web standards". In order to be able to run <a>application</a>s, devices implement an interactive user-agent commonly referred to as <dfn>browser</dfn>. The set of languages that are expected to be supported by the browser running on a <a>device</a> are listed in <a href="#browser-environment" class="sectionRef"></a>.
+ </section>
+
+</section>
+
+<section id=browser-environment>
+<h2>Browser Application Environment</h2>
+ This section list which languages are supported by <a>browser</a>s conforming to this profile. <a>Browser</a>s may support more languages than the ones listed in this section.
+
+ <section>
+ <h2>HTML</h2>
+ <p>HTML is the markup language used to describe documents on the web. This profile rely on the 5th revision of HTML, also known as HTML5.
+ <p>The [[!HTML5]] specification defines conformance requirements for user-agents and documents. <a>Application</a>s and authoring tools SHALL comply with conformance requirements for documents unless differently specified in this document. <a>Browser</a>s SHALL comply with conformance requirements for user agents unless differently specified in this document; in particular browsers SHALL support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [[!HTML5]].
+ <div class="issue">Do we need support for both syntaxes or can we go just for the HTML syntax?</div>
+
+ <p>HTML5 (by design) does not provide mechanisms for media-specific customization of presentation although several mechanisms to hook into languages and technologies that allow such customization are provided. Languages that are expected to be supported by <a>browser</a>s in connection with HTML5 are listed in the following sections.
+
+ <section>
+ <h2>Scripting</h2>
+ <dfn>Scripts</dfn> are small programs that can be embedded into <a>application</a>s. While defining features that rely on scripting, HTML5 do not mandate support for scripting for all user agents. Furthermore scripting is defined using a syntax that in most cases is independent from the underlying scripting language. For such reasons, this profile add the following additional requirements:
+ <ul>
+ <li>Browser SHALL support <a class="externalDFN">scripting</a> as defined in [[!HTML5]]. </li>
+ <li>Browser SHALL support [[!ECMA-262]] scripting language</li>
+ </ul>
+ </section>
+
+ <section>
+ <h2>CSS</h2>
+ Support for CSS as a whole is not required by HTML5, even though some features are defined in terms of specific CSS requirements.
+ <div class="note"> TODO: list requirements for CSS support,i.e. which modules needs to be supported. ALso need to discuss if a further profiling inside each module is needed.</i>
+ </section>
<section>
- <h2>System Architecture</h2>
-
+ <h2>Document Object Model (DOM)</h2>
</section>
- <section>
- <h2>Components and interfaces</h2>
- </section>
-</section>
-<section>
-<h2>Application Model</h2>
-
-</section>
-
-<section>
- <h2>User Experience</h2>
-
- <section>
- <h2>Content Developers Guidelines</h2>
+ <section>
+ <h2>... (add more section for other web standards)</h2>
+ </section>
</section>
-
+
<section>
<h2>Input Methods</h2>
<section>
@@ -200,16 +239,36 @@
</section>
</section>
+ <section class="informative">
+ <h2>Content Developers Guidelines</h2>
+ </section>
+
</section>
<section>
<h2>Formats and Protocols</h2>
+ <div class=note>The aim of this section is to collect in one document the result of the discussion going on in different groups, like the HNTF or the MPTF of the web&tv IG. Therefore it should describe things like:
+ <ul>
+ <li>adaptive streaming
+ <li>parental control
+ <li>content protection
+ <li>Subtitles (webvtt,TTML etc.)
+ <li>discovery and control of home network services
+ <li>...
+ </ul>
+
+ and describe how these functionalities can be accessed by an application/user. If new specs needs to be written (as currently being discussed in different places) we need to decide if such specs should be part of this document or external documents referenced by this one (I prefer the second option). Note that ins some cases you have multiple protocols for the same functionalities, but we could still describe a unique way to expose such multiple protocols to the application/user.</div>
+
</section>
+<section>
+ <h2>Performances</h2>
+</section>
<section class='appendix'>
<h2>Acknowledgements</h2>
<p> Thanks to ... for their contributions to this document</p>
+ <!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
</section>
--- a/tvprofile/tv.html Wed Jan 04 16:37:00 2012 +0100
+++ b/tvprofile/tv.html Thu Jan 05 17:06:55 2012 +0100
@@ -476,11 +476,11 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="http://www.w3.org/StyleSheets/TR/w3c-unofficial" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><div class="head"><p></p><h1 class="title" id="title">Web&TV profile (provisional title)</h1><h2 id="subtitle">Guidelines for integration of interactive TV services in a Browser-based environment</h2><h2 id="unofficial-draft-04-january-2012">Unofficial Draft 04 January 2012</h2><dl><dt>Editor:</dt><dd><span>Giuseppe Pascale</span>, <a href="http://www.opera.com/">Opera</a></dd>
+ <body style="display: inherit; "><div class="head"><p></p><h1 class="title" id="title">Web&TV profile (provisional title)</h1><h2 id="subtitle">Guidelines for integration of interactive TV services in a Browser-based environment</h2><h2 id="unofficial-draft-05-january-2012">Unofficial Draft 05 January 2012</h2><dl><dt>Editor:</dt><dd><span>Giuseppe Pascale</span>, <a href="http://www.opera.com/">Opera</a></dd>
</dl><p class="copyright">This document is licensed under a <a class="subfoot" href="http://creativecommons.org/licenses/by/3.0/" rel="license">Creative Commons Attribution 3.0 License</a>.</p><hr></div>
<div id="abstract" class="introductory section"><h2>Abstract</h2>
-</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p>This document is merely a public working draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organisation.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#background" class="tocxref"><span class="secno">1.1 </span>Background</a></li><li class="tocline"><a href="#design-goals" class="tocxref"><span class="secno">1.2 </span>Design Goals</a><ul class="toc"><li class="tocline"><a href="#avoid-obsolesce" class="tocxref"><span class="secno">1.2.1 </span>Avoid obsolesce</a></li><li class="tocline"><a href="#improve-interoperability" class="tocxref"><span class="secno">1.2.2 </span>Improve interoperability</a></li><li class="tocline"><a href="#coordinate-deployments" class="tocxref"><span class="secno">1.2.3 </span>Coordinate deployments</a></li><li class="tocline"><a href="#provide-a-complete-application-environment" class="tocxref"><span class="secno">1.2.4 </span>Provide a complete application environment</a></li><li class="tocline"><a href="#do-not-reinvent-the-wheel" class="tocxref"><span class="secno">1.2.5 </span>Do not reinvent the wheel</a></li><li class="tocline"><a href="#a-tunable-meta-profile" class="tocxref"><span class="secno">1.2.6 </span>A tunable meta-profile</a></li></ul></li><li class="tocline"><a href="#audience" class="tocxref"><span class="secno">1.3 </span>Audience</a></li><li class="tocline"><a href="#scope" class="tocxref"><span class="secno">1.4 </span>Scope</a></li></ul></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">2. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2.1 </span>Conformance</a></li><li class="tocline"><a href="#definitions" class="tocxref"><span class="secno">2.2 </span>Definitions</a></li></ul></li><li class="tocline"><a href="#overview" class="tocxref"><span class="secno">3. </span>Overview</a><ul class="toc"><li class="tocline"><a href="#system-architecture" class="tocxref"><span class="secno">3.1 </span>System Architecture</a></li><li class="tocline"><a href="#components-and-interfaces" class="tocxref"><span class="secno">3.2 </span>Components and interfaces</a></li></ul></li><li class="tocline"><a href="#application-model" class="tocxref"><span class="secno">4. </span>Application Model</a></li><li class="tocline"><a href="#user-experience" class="tocxref"><span class="secno">5. </span>User Experience</a><ul class="toc"><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">5.1 </span>Content Developers Guidelines</a></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">5.2 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">5.2.1 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">5.2.2 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">5.2.3 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">5.2.4 </span>Other input devices</a></li></ul></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">6. </span>Formats and Protocols</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
+</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p>This document is merely a public working draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organisation.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#background" class="tocxref"><span class="secno">1.1 </span>Background</a></li><li class="tocline"><a href="#design-goals" class="tocxref"><span class="secno">1.2 </span>Design Goals</a><ul class="toc"><li class="tocline"><a href="#avoid-obsolesce" class="tocxref"><span class="secno">1.2.1 </span>Avoid obsolesce</a></li><li class="tocline"><a href="#improve-interoperability" class="tocxref"><span class="secno">1.2.2 </span>Improve interoperability</a></li><li class="tocline"><a href="#coordinate-deployments" class="tocxref"><span class="secno">1.2.3 </span>Coordinate deployments</a></li><li class="tocline"><a href="#provide-a-complete-application-environment" class="tocxref"><span class="secno">1.2.4 </span>Provide a complete application environment</a></li><li class="tocline"><a href="#do-not-reinvent-the-wheel" class="tocxref"><span class="secno">1.2.5 </span>Do not reinvent the wheel</a></li><li class="tocline"><a href="#a-tunable-meta-profile" class="tocxref"><span class="secno">1.2.6 </span>A tunable meta-profile</a></li></ul></li><li class="tocline"><a href="#audience" class="tocxref"><span class="secno">1.3 </span>Audience</a></li><li class="tocline"><a href="#scope" class="tocxref"><span class="secno">1.4 </span>Scope</a></li></ul></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">2. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2.1 </span>Conformance</a></li><li class="tocline"><a href="#definitions" class="tocxref"><span class="secno">2.2 </span>Definitions</a></li></ul></li><li class="tocline"><a href="#overview" class="tocxref"><span class="secno">3. </span>Overview</a><ul class="toc"><li class="tocline"><a href="#system-architecture" class="tocxref"><span class="secno">3.1 </span>System Architecture</a></li><li class="tocline"><a href="#application-model" class="tocxref"><span class="secno">3.2 </span>Application Model</a></li></ul></li><li class="tocline"><a href="#browser-environment" class="tocxref"><span class="secno">4. </span>Browser Application Environment</a><ul class="toc"><li class="tocline"><a href="#html" class="tocxref"><span class="secno">4.1 </span>HTML</a><ul class="toc"><li class="tocline"><a href="#scripting" class="tocxref"><span class="secno">4.1.1 </span>Scripting</a></li><li class="tocline"><a href="#css" class="tocxref"><span class="secno">4.1.2 </span>CSS</a></li><li class="tocline"><a href="#document-object-model--dom" class="tocxref"><span class="secno">4.1.3 </span>Document Object Model (DOM)</a></li><li class="tocline"><a href="#x...--add-more-section-for-other-web-standards" class="tocxref"><span class="secno">4.1.4 </span>... (add more section for other web standards)</a></li></ul></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">4.2 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">4.2.1 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">4.2.2 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">4.2.3 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">4.2.4 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">4.3 </span>Content Developers Guidelines</a></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">5. </span>Formats and Protocols</a></li><li class="tocline"><a href="#performances" class="tocxref"><span class="secno">6. </span>Performances</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
<div class="informative section" id="introduction">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
@@ -533,7 +533,16 @@
<div id="scope" class="section">
<h3><span class="secno">1.4 </span>Scope</h3>
- </div>
+ The scope of this document is limited to:
+ <ul>
+ <li>provide references to a set of languages that shall be supported by <a href="#dfn-device" class="internalDFN">device</a>s and can be used by <a title="content provider" href="#dfn-content-provider" class="internalDFN">content</a> and <a href="#dfn-service-provider" class="internalDFN">service provider</a><a>s to author content and services to be presented to the </a><a>end user</a>.</li>
+ <li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
+ </ul>
+ <p>
+ The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a href="#dfn-user" class="internalDFN">user</a> would be expected to have on their devices are out of scope.
+ </p><p>
+ The scope of this document is not to describe a unique end-to-end delivery system. In particular, mandating a specific end-to-end network configuration (including network protocols, video codecs, video streaming technologies and so on) is out of scope for this document. Nonetheless this document may describe how some specific technologies may be combined together in order to provide a functional <a href="#dfn-tv-service" class="internalDFN">TV service</a>.
+ </p></div>
</div>
@@ -548,71 +557,122 @@
<p>
For the purposes of the present document, the following definitions apply:
</p><ul>
- <li><dfn id="dfn-stb">STB</dfn>: a set-top box (STB) is a device that can be connected to a <a href="#dfn-tv-set" class="internalDFN">TV set</a> or other display devices to enable presentation of content coming from a variety of sources - such as received via <a href="#dfn-broadcast-network" class="internalDFN">broadcast network</a>s, <a href="#dfn-broadband-network" class="internalDFN">broadband network</a>s or streamed from other devices.</li>
+ <li><dfn id="dfn-stb">STB</dfn>: a set-top box (STB) is a <a href="#dfn-device" class="internalDFN">device</a> that can be connected to a <a href="#dfn-tv-set" class="internalDFN">TV set</a> or other display devices to enable presentation of content coming from a variety of sources - such as received via <a href="#dfn-broadcast-network" class="internalDFN">broadcast network</a>s, <a href="#dfn-broadband-network" class="internalDFN">broadband network</a>s or streamed from other devices.</li>
<li><dfn id="dfn-tv-set">TV set</dfn>: A display device that can presents content from a variety of sources - such as received via <a href="#dfn-broadcast-network" class="internalDFN">broadcast network</a>s,<a href="#dfn-broadband-network" class="internalDFN">broadband network</a>s or streamed from other devices.</li>
+ <li><dfn id="dfn-tv-service">TV service</dfn>: A providing commercial video service that may include elements of interactivity and provides a coherent user experience. TV services are usually divided into two main groups: <dfn title="schedule service" id="dfn-schedule-service">scheduled</dfn> or <dfn title="linear service" id="dfn-linear-service">linear</dfn> services are the ones that have to be consumed by the user at the particular point in time when they are offered (e.g. a broadcast TV channel); <dfn title="on-demand service" id="dfn-on-demand-service">on-demand</dfn> services are the ones that can be consumed by the user at any point in time (e.g. web video portals).</li>
+ <li><dfn id="dfn-device">device</dfn>: for the purposes of this document, a device is any piece of equipment owned by the user that is able to presentat <a href="#dfn-tv-service" class="internalDFN">TV service</a>s to the end user. Note that this is a generic term that also includes the <a href="#dfn-tv-set" class="internalDFN">TV set</a> and <a href="#dfn-stb" class="internalDFN">STB</a> terms defined in this document.</li>
<li><dfn id="dfn-broadband-network">broadband network</dfn>: bi-directional IP connection</li>
<li><dfn id="dfn-broadcast-network">broadcast network</dfn>: classical uni-directional TV broadcast networks such as DVB, ATSC, ISDB.
- </li></ul>
+ </li><li><dfn id="dfn-user">user</dfn>: is the consumer of <a href="#dfn-tv-service" class="internalDFN">TV service</a>s. Traditionally TV services have been consumed only via <a href="#dfn-tv-set" class="internalDFN">TV set</a>s or <a href="#dfn-stb" class="internalDFN">STB</a>s connected to a display. Nowadays end users have a wide range of devices (e.g. PC, laptops,smartphones, tablets) available both in their home and outside and expect to be able to access to services from any device.</li>
+ <li><dfn id="dfn-service-provider">service provider</dfn>: aggregates content from one or more <a href="#dfn-content-provider" class="internalDFN">content provider</a>s and offer them to the end user for consumption.</li>
+ <li><dfn id="dfn-content-provider">content provider</dfn>: the author of a piece of content that is later sold or licensed to <a href="#dfn-service-provider" class="internalDFN">service provider</a>s and consumed by the <a href="#dfn-user" class="internalDFN">user</a>s.</li>
+ </ul>
<p></p>
</div>
</div>
-
+<div class="informative section" id="overview">
+<!--OddPage--><h2><span class="secno">3. </span>Overview</h2><p><em>This section is non-normative.</em></p>
+
+ <div id="system-architecture" class="section">
+ <h3><span class="secno">3.1 </span>System Architecture</h3>
+ <div class="note"> TODO: briefly describe the system architecture, just to explain how content is delivered to devices via a multitude of networks and which components of the overall architecture are in scope for this document. This section is just informative and should help the reader to understand which parts of the system architecture are covered by this spec but should not try to be an encyclopedic explanation of TV systems </div>
+ </div>
-<div id="overview" class="section">
-<!--OddPage--><h2><span class="secno">3. </span>Overview</h2>
-
- <div id="system-architecture" class="section">
- <h3><span class="secno">3.1 </span>System Architecture</h3>
-
- </div>
- <div id="components-and-interfaces" class="section">
- <h3><span class="secno">3.2 </span>Components and interfaces</h3>
- </div>
-</div>
-
-<div id="application-model" class="section">
-<!--OddPage--><h2><span class="secno">4. </span>Application Model</h2>
-
+ <div id="application-model" class="section">
+ <h3><span class="secno">3.2 </span>Application Model</h3>
+ The term <dfn id="dfn-application">application</dfn> is used to refer to a collection of documents and associated resources that can be used to provide a <a href="#dfn-tv-service" class="internalDFN">TV service</a> and are authored using a set of languages commonly referred to as "web technologies" or "web standards". In order to be able to run <a href="#dfn-application" class="internalDFN">application</a>s, devices implement an interactive user-agent commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages that are expected to be supported by the browser running on a <a href="#dfn-device" class="internalDFN">device</a> are listed in <a href="#browser-environment" class="sectionRef">section 4. Browser Application Environment</a>.
+ </div>
+
</div>
-<div id="user-experience" class="section">
- <!--OddPage--><h2><span class="secno">5. </span>User Experience</h2>
+<div id="browser-environment" class="section">
+<!--OddPage--><h2><span class="secno">4. </span>Browser Application Environment</h2>
+ This section list which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile. <a href="#dfn-browser" class="internalDFN">Browser</a>s may support more languages than the ones listed in this section.
- <div id="content-developers-guidelines" class="section">
- <h3><span class="secno">5.1 </span>Content Developers Guidelines</h3>
+ <div id="html" class="section">
+ <h3><span class="secno">4.1 </span>HTML</h3>
+ <p>HTML is the markup language used to describe documents on the web. This profile rely on the 5th revision of HTML, also known as HTML5.
+ </p><p>The [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification defines conformance requirements for user-agents and documents. <a href="#dfn-application" class="internalDFN">Application</a>s and authoring tools <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for documents unless differently specified in this document. <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>].
+ </p><div class="issue">Do we need support for both syntaxes or can we go just for the HTML syntax?</div>
+
+ <p>HTML5 (by design) does not provide mechanisms for media-specific customization of presentation although several mechanisms to hook into languages and technologies that allow such customization are provided. Languages that are expected to be supported by <a href="#dfn-browser" class="internalDFN">browser</a>s in connection with HTML5 are listed in the following sections.
+
+ </p><div id="scripting" class="section">
+ <h4><span class="secno">4.1.1 </span>Scripting</h4>
+ <dfn id="dfn-scripts">Scripts</dfn> are small programs that can be embedded into <a href="#dfn-application" class="internalDFN">application</a>s. While defining features that rely on scripting, HTML5 do not mandate support for scripting for all user agents. Furthermore scripting is defined using a syntax that in most cases is independent from the underlying scripting language. For such reasons, this profile add the following additional requirements:
+ <ul>
+ <li>Browser <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">scripting</a> as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. </li>
+ <li>Browser <em class="rfc2119" title="shall">shall</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] scripting language</li>
+ </ul>
+ </div>
+
+ <div id="css" class="section">
+ <h4><span class="secno">4.1.2 </span>CSS</h4>
+ Support for CSS as a whole is not required by HTML5, even though some features are defined in terms of specific CSS requirements.
+ <div class="note"> TODO: list requirements for CSS support,i.e. which modules needs to be supported. ALso need to discuss if a further profiling inside each module is needed.
+ </div></div>
+
+ <div id="document-object-model--dom" class="section">
+ <h4><span class="secno">4.1.3 </span>Document Object Model (DOM)</h4>
+ </div>
+
+ <div id="x...--add-more-section-for-other-web-standards" class="section">
+ <h4><span class="secno">4.1.4 </span>... (add more section for other web standards)</h4>
+ </div>
+ </div>
+
+ <div id="input-methods" class="section">
+ <h3><span class="secno">4.2 </span>Input Methods</h3>
+ <div id="traditional-remote-controls" class="section">
+ <h4><span class="secno">4.2.1 </span>Traditional Remote Controls</h4>
+ </div>
+ <div id="touch-screens" class="section">
+ <h4><span class="secno">4.2.2 </span>Touch screens</h4>
+ </div>
+ <div id="mouse-and-keyboard" class="section">
+ <h4><span class="secno">4.2.3 </span>Mouse and Keyboard</h4>
+ </div>
+ <div id="other-input-devices" class="section">
+ <h4><span class="secno">4.2.4 </span>Other input devices</h4>
+ </div>
</div>
- <div id="input-methods" class="section">
- <h3><span class="secno">5.2 </span>Input Methods</h3>
- <div id="traditional-remote-controls" class="section">
- <h4><span class="secno">5.2.1 </span>Traditional Remote Controls</h4>
- </div>
- <div id="touch-screens" class="section">
- <h4><span class="secno">5.2.2 </span>Touch screens</h4>
- </div>
- <div id="mouse-and-keyboard" class="section">
- <h4><span class="secno">5.2.3 </span>Mouse and Keyboard</h4>
- </div>
- <div id="other-input-devices" class="section">
- <h4><span class="secno">5.2.4 </span>Other input devices</h4>
- </div>
+ <div class="informative section" id="content-developers-guidelines">
+ <h3><span class="secno">4.3 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
</div>
</div>
<div id="formats-and-protocols" class="section">
- <!--OddPage--><h2><span class="secno">6. </span>Formats and Protocols</h2>
+ <!--OddPage--><h2><span class="secno">5. </span>Formats and Protocols</h2>
+ <div class="note">The aim of this section is to collect in one document the result of the discussion going on in different groups, like the HNTF or the MPTF of the web&tv IG. Therefore it should describe things like:
+ <ul>
+ <li>adaptive streaming
+ </li><li>parental control
+ </li><li>content protection
+ </li><li>Subtitles (webvtt,TTML etc.)
+ </li><li>discovery and control of home network services
+ </li><li>...
+ </li></ul>
+
+ and describe how these functionalities can be accessed by an application/user. If new specs needs to be written (as currently being discussed in different places) we need to decide if such specs should be part of this document or external documents referenced by this one (I prefer the second option). Note that ins some cases you have multiple protocols for the same functionalities, but we could still describe a unique way to expose such multiple protocols to the application/user.</div>
+
</div>
+<div id="performances" class="section">
+ <!--OddPage--><h2><span class="secno">6. </span>Performances</h2>
+</div>
<div class="appendix section" id="acknowledgements">
<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p> Thanks to ... for their contributions to this document</p>
+ <!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
</div>
-<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
-</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</a>
-</dd></dl></div></div></body></html>
+<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a>
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/html5"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/html5">http://www.w3.org/TR/html5</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file