--- a/tvprofile/tv-src.html Tue Jan 17 18:20:39 2012 +0100
+++ b/tvprofile/tv-src.html Thu Jan 19 13:15:43 2012 +0100
@@ -86,7 +86,7 @@
</section>
-<section class="informative">
+<section id="intro" class="informative">
<h2>Introduction</h2>
<section>
@@ -151,20 +151,20 @@
<section>
<h2>System Overview</h2>
- <div class=note>This section gives and overview of the typical architecture of an interactive TV services delivery system. The level of detail of this section is general and abstract: there is no attempt to provide an in-depth technical explanation of each component and of the interaction between them. Also in practice some logical component may be combined into one, and some component may be missing in some deployments and/or regions.</div>
+ <div class=note>This section gives and overview of the typical architecture of an interactive TV services delivery system. The level of detail of this section is general and abstract: there is no attempt to provide an in-depth technical explanation of each component and of the interaction between them. Also in practice some logical components may be combined into one, and some components may be missing in some deployments and/or regions.</div>
<p>
The main goal of this profile is to simplify and harmonize the production and delivery of <a>TV Services</a> to web enabled devices. For the purposes of this document a <dfn>TV service</dfn> is a commercial video service that may include elements of interactivity and that provides a coherent user experience. TV services are usually divided into two main groups: <dfn title="scheduled 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).
<p>
In order to consume them, users need a <dfn>device</dfn> that is able to present TV services. Traditionally TV services have been consumed mainly via <a>TV set</a>s or <a>STB</a>s connected to a display. Nowadays 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 TV services from any device.
<p>
- <a>TV service</a>s can be delivered to users via a variety of means. The most common means is via a uni-directional TV <dfn>broadcast network</dfn>. Different standards have been defined for such purpose, such as <a>DVB</a>, <a>ATSC</a>, <a>ISDB</a>. <a>TV service</a>s may also be delivered via bi-directional IP connections, mainly via the Internet. An emerging scenario is represented by content streamed directly between devices connected via the <dfn>home network</dfn>. The term <a>home network</a> refers to the networking infrastructure that facilitates communications between devices within the home. This may range from a single legacy IPv4 subnet to multiple IPv4 subnets and dual stack or IPv6 environments and will typically (but not always) be connected to the Internet.
+ <a>TV service</a>s can be delivered to users via a variety of means. The most common means is via a uni-directional TV <dfn>broadcast network</dfn>. Different standards have been defined for such purpose, such as <a>DVB</a>, <a>ATSC</a>, <a>ISDB</a>. <a>TV service</a>s may also be delivered via bi-directional IP connections, mainly via the Internet. An emerging scenario is represented by content streamed directly between devices connected via the <dfn>home network</dfn>. The term <a>home network</a> refers to the networking infrastructure that facilitates communications between devices within the home. This will typically (but not always) be connected to the Internet.
<p>
- To provide a level of interactivity, <a>TV service</a>s may be associated to or delivered as <a>application</a>s. For the purposes of this document the term <dfn>application</dfn> refers to a collection of documents and associated resources that 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, <a>device</a>s implement an <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn>browser</dfn>. The set of languages that are expected to be supported by <a>browser</a>s conforming to this specification are listed in <a href="#browser-environment" class="sectionRef"></a>.
+ To provide a level of interactivity, <a>TV service</a>s may be associated to or delivered as <a>application</a>s. For the purposes of this document the term <dfn>application</dfn> refers to a collection of documents and associated resources that 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, <a>device</a>s implement an <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn>browser</dfn>. The set of languages supported by <a>browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef"></a>.
</section>
</section>
-<section>
+<section id="terminology">
<h2>Terminology</h2>
<section id="conformance">
@@ -191,114 +191,148 @@
</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 id="app-environment">
+<h2>Application Environment</h2>
+ This section lists which languages are supported by <a>browser</a>s conforming to this profile and that can be used to author <a>application</a>s. <a>Browser</a>s may support more languages than the ones listed in this section.
- <section>
+ <section id="html">
<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>
+ <section id="scripting">
+ <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><a>Browser</a>s SHALL support <a class="externalDFN">scripting</a> as defined in [[!HTML5]]. </li>
+ <li><a>Browser</a>s SHALL support [[!ECMA-262]] scripting language</li>
+ </ul>
+ </section>
- <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><a>Browser</a>s SHALL support <a class="externalDFN">scripting</a> as defined in [[!HTML5]]. </li>
- <li><a>Browser</a>s 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. The following sections list modules and parameters that <a>browser</a>s conforming to this specification have to support.
- <div class="note"> TODO: this section is not complete yet. More modules needs to be added</div>
- <section>
- <h2>CSS3 Fonts</h2>
+ <section id="css">
+ <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. The following sections list modules and parameters that <a>browser</a>s conforming to this specification have to support.
+ <div class="note"> TODO: this section is not complete yet. More modules needs to be added</div>
+ <section id="css3-fonts">
+ <h2>CSS3 Fonts</h2>
The [[!CSS3-FONTS]] module describes how font properties are specified and how font resources are loaded dynamically.
The features marked as included below SHALL be supported by conforming <a>browser</a>s.
<dt>Properties</dt>
<dd>
<table class=profile>
<tr>
- <th scope="col">Name</th>
- <th scope="col">Included</th>
- <th scope="col">Notes</th>
- </tr>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
+ </tr>
<tr>
<td>font</td>
<td class="y">yes</td>
</tr>
- <tr>
- <td>font-size</td>
- <td class="y">yes</td>
- </tr>
- <tr>
- <td>font-size-adjust</td>
- <td class="n">no</td>
- </tr>
- <tr>
- <td>font-variant</td>
- <td class="y">yes</td>
- </tr>
+ <tr>
+ <td>font-size</td>
+ <td class="y">yes</td>
+ </tr>
+ <tr>
+ <td>font-size-adjust</td>
+ <td class="n">no</td>
+ </tr>
+ <tr>
+ <td>font-variant</td>
+ <td class="y">yes</td>
+ </tr>
</table>
</dd>
-
+
<dt>Descriptors</dt>
<dd>
<table class=profile>
<tr>
- <th scope="col">Name</th>
- <th scope="col">Included</th>
- <th scope="col">Notes</th>
- </tr>
- <tr>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
+ </tr>
+ <tr>
<td>font-family</td>
<td class="y">yes</td>
</tr>
- <tr>
- <td>font-stretch</td>
- <td class="n">no</td>
- </tr>
- <tr>
- <td>font-style</td>
- <td class="y">yes</td>
- </tr>
- <tr>
- <td>font-weight</td>
- <td class="y">yes</td>
- </tr>
+ <tr>
+ <td>font-stretch</td>
+ <td class="n">no</td>
+ </tr>
+ <tr>
+ <td>font-style</td>
+ <td class="y">yes</td>
+ </tr>
+ <tr>
+ <td>font-weight</td>
+ <td class="y">yes</td>
+ </tr>
</table>
</dd>
- </section>
+ </section>
- <section>
+ <section id="css3-mq">
<h2>CSS3 Media Queries</h2>
The [[!CSS3-MEDIAQUERIES]] module extend the functionality of media types by allowing more precise labeling of style sheets.
A conforming <a>browser</a> SHALL support media queries as defined in [[!CSS3-MEDIAQUERIES]].
<div class="issue">Maybe we want to list supported attributes anyway, in case more features are added to the spec after the profile is released.</div>
- </section>
</section>
- <section>
- <h2>Document Object Model (DOM)</h2>
+ <section id="css3-bg">
+ <h2>CSS3 Backgrounds and Borders</h2>
+ <div class="issue">This may need multiple subprofiles based on terminal capability</div>
+ [[!CSS3-BG]]
+ </section>
+ CSS Selectors
+
+ <section id="css3-2d-tf">
+ <h2>CSS3 2D Transform</h2>
+ <div class="issue">This may need multiple subprofiles based on terminal capability</div>
+ [[!CSS3-2D-TRANSFORMS]]
</section>
+
+ <section id="css3-3d-tf">
+ <h2>CSS3 3D Transform</h2>
+ <div class="issue">This may need multiple subprofiles based on terminal capability</div>
+ [[!CSS3-3D-TRANSFORMS]]
+ </section>
+
+
+ </section>
+
+ <section id="xhr">
+ <h2>XML HTTP Request</h2>
+ </section>
+
+ <section id="dom">
+ <h2>Document Object Model (DOM)</h2>
+ </section>
- <section>
- <h2>... (add more section for other web standards)</h2>
- </section>
+ <section>
+ <h2>... (add more section for other web standards)</h2>
</section>
<section>
<h2>Input Methods</h2>
<section>
+ <h2>Determine available input methods</h2>
+ <div class="issue">
+ <p>Is this important for TV app developers? (I think so)
+ <p>Some proprietary methods for some input methods exist, e.g. <a href="https://developer.mozilla.org/en/CSS/Media_queries#-moz-touch-enabled">-moz-touch-enabled</a>
+ But there seem to be no universal method to determine input capabilities. Need to discuss this with relevant WGs (CSS, WebApps, WebEvents)
+ </div>
+ </section>
+ <section>
<h2>Traditional Remote Controls</h2>
+ <div class="issue">Need to check the progress of DOM events in this area. See <a href="http://www.w3.org/TR/DOM-Level-3-Events/#remote-control">http://www.w3.org/TR/DOM-Level-3-Events/#remote-control</a></div>
</section>
<section>
<h2>Touch screens</h2>
+ [[!TOUCH-EVENTS]]
</section>
<section>
<h2>Mouse and Keyboard</h2>
@@ -315,7 +349,7 @@
</section>
<section>
- <h2>Formats and Protocols</h2>
+ <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
@@ -327,15 +361,35 @@
</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><h2>Exposing in-band media container Tracks</h2></section>
+ <section><h2>Discovery and Communication with Home Network Services</h2></section>
+
</section>
<section>
<h2>Testing</h2>
+ <div class="note">
+ Relevant test material can be found here:
+ <ul>
+ <li><a href="http://www.w3.org/Style/CSS/Test/">CSS tests</a></li>
+ <li><a href="http://w3c-test.org/">W3C Test Suite Framework</a></li>
+ </ul>
+ </div>
+ <section><h2>Testing Infrastructure</h2></section>
+
</section>
+
<section>
<h2>Performances</h2>
+ <div class="issue">
+ <ul>
+ <li>DO we need to identify different class of devices and associate different performance requirement? E.g. we could have 3 classes A,B,C and say A devices score less than x, B between x and y and C more then y (where x,y,z are defined for each benchmark)</li>
+ <li>How performances should be linked to requirements? E.g. if we have 3 classes and a feature N, should we say that A SHALL NOT support N, B may support N, C SHALL support N?</li>
+ </ul>
+ </div>
</section>
<section class='appendix'>