--- a/tvprofile/tv-src.html Fri Jan 13 18:34:13 2012 +0100
+++ b/tvprofile/tv-src.html Mon Jan 16 20:17:00 2012 +0100
@@ -91,7 +91,7 @@
<section>
<h2>Background</h2>
- <p>There is an increasing number of content providers worldwide that are deploying interactive TV services based on web technologies. In order to achieve that, many organizations and companies have created profiles of web technologies suitable for use in a specific market and/or region. These profiles are supersets, subsets or both of several W3C specifications. Often these documents have been written without a direct involvement of relevant W3C working groups. Furthermore not always these different groups were aware of each other, leading to different profiles in different regions and markets. In some cases also extensions to web standards have been designed, leading to multiple incompatible solutions addressing the same use case.</p>
+ <p>There is an increasing number of content and service providers worldwide that are deploying interactive TV services based on web technologies. In order to achieve that, many organizations and companies have created profiles of web technologies suitable for use in a specific market and/or region. These profiles are supersets, subsets or both of several W3C specifications. Often these documents have been written without a direct involvement of relevant W3C working groups. Furthermore not always these different groups were aware of each other, leading to different profiles in different regions and markets. In some cases also extensions to web standards have been designed, leading to multiple incompatible solutions addressing the same use case.</p>
<p>The goal of this document is to reduce fragmentation and eliminate the needs for extensions, by providing a common meta-profile that allows external organizations to align with W3C and with each other. While is not possible to provide a profile that cover all needs of different organizations and stakeholders, this meta-profile tries to keep at a minimum the variables involved in defining new profiles, providing a common reference framework that different organization can reuse.</p>
</section>
@@ -133,6 +133,7 @@
<section>
<h2>Audience</h2>
+ ...
</section>
<section>
@@ -147,6 +148,19 @@
<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>
+ <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>
+ <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.
+ <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>.
+ </section>
</section>
@@ -164,32 +178,18 @@
<ul>
<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>DVB</dfn>:tbd</li>
+ <li><dfn>ATSC</dfn>:tbd</li>
+ <li><dfn>ISDB</dfn>:tbd</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>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>
@@ -198,7 +198,7 @@
<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]].
+ <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.
@@ -214,34 +214,34 @@
<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.
+ 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>
- 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 user-agent.
+ 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="parameters" >
+ <table class=profile>
<tr>
- <th>Name</th>
- <th>Notes</th>
- <th>Included</th>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
</tr>
<tr>
- <td>font</td><td></td>
+ <td>font</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-size</td><td></td>
+ <td>font-size</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-size-adjust</td><td></td>
+ <td>font-size-adjust</td>
<td class="n">no</td>
</tr>
<tr>
- <td>font-variant</td><td></td>
+ <td>font-variant</td>
<td class="y">yes</td>
</tr>
</table>
@@ -249,26 +249,26 @@
<dt>Descriptors</dt>
<dd>
- <table class="parameters">
+ <table class=profile>
<tr>
- <th>Name</th>
- <th>Notes</th>
- <th>Included</th>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
</tr>
<tr>
- <td>font-family</td><td></td>
+ <td>font-family</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-stretch</td><td></td>
+ <td>font-stretch</td>
<td class="n">no</td>
</tr>
<tr>
- <td>font-style</td><td></td>
+ <td>font-style</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-weight</td><td></td>
+ <td>font-weight</td>
<td class="y">yes</td>
</tr>
</table>