--- a/tvprofile/tv.html Wed Jan 04 16:33:26 2012 +0100
+++ b/tvprofile/tv.html Wed Jan 04 16:37:00 2012 +0100
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head>
- <title>Web&TV meta-profile (provisional title)</title>
+ <title>Web&TV profile (provisional title)</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<!--
=== NOTA BENE ===
@@ -476,68 +476,88 @@
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 meta-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-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>
</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="#audience" class="tocxref"><span class="secno">1.2 </span>Audience</a></li><li class="tocline"><a href="#scope" class="tocxref"><span class="secno">1.3 </span>Scope</a></li></ul></li><li class="tocline"><a href="#goals" class="tocxref"><span class="secno">2. </span>Goals</a><ul class="toc"><li class="tocline"><a href="#avoid-obsolesce" class="tocxref"><span class="secno">2.1 </span>Avoid obsolesce</a></li><li class="tocline"><a href="#avoid-fragmentation" class="tocxref"><span class="secno">2.2 </span>Avoid fragmentation</a></li><li class="tocline"><a href="#coordinate-deployments" class="tocxref"><span class="secno">2.3 </span>Coordinate deployments</a></li><li class="tocline"><a href="#provide-a-complete-application-environment" class="tocxref"><span class="secno">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">2.5 </span>Do not reinvent the wheel</a></li><li class="tocline"><a href="#a-tunable-meta-profile" class="tocxref"><span class="secno">2.6 </span>A tunable meta-profile</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="#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 class="informative section" id="introduction">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
<div id="background" class="section">
<h3><span class="secno">1.1 </span>Background</h3>
-
- In the past decades, many attempts have been made to create profiles suitable for use in a specific market and/or region, particularly in the TV space, by external organizations. These groups have created documents which are supersets, subsets or both of several W3C specifications. Often these documents have been developed 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 by different groups, leading to multiple incompatible solutions addressing the same use case.
-
- By working on a common meta-profile within W3C it becomes easier to closely align external organizations with W3C and with each other. It also allows the W3C to move this profile forward on a regular basis to avoid obsolescence. While is not possible to provide a profile that cover all needs of different organizations and stakeholder, this documents tries to provide a meta-profile that try to keep at a minimum the variables involved in defining such profiles, making it a base that each external organization can use as a component.
+ <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>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>
</div>
+ <div id="design-goals" class="section">
+ <h3><span class="secno">1.2 </span>Design Goals</h3>
+ This sections list the goals that have driven the work on this document.
+
+ <div id="avoid-obsolesce" class="section">
+ <h4><span class="secno">1.2.1 </span>Avoid obsolesce</h4>
+ In the past decades, many attempts have been made to create profiles suitable for use in a specific market and/or region, particularly in the TV space, by external organizations. These groups have created documents which are supersets, subsets or both of several W3C specifications. Often, these external documents become obsolete when the W3C improves the related specifications since the W3C has little or no knowledge of these external documents. By working on a common TV profile within W3C it becomes easier to closely align external organizations with W3C and with each other and allows the W3C to move this profile forward on a regular basis to avoid obsolescence.
+ </div>
+
+ <div id="improve-interoperability" class="section">
+ <h4><span class="secno">1.2.2 </span>Improve interoperability</h4>
+ Use of web technologies in different markets and regions to create interactive TV services is increasing. TV services are not relegated anymore to <a href="#dfn-tv-set" class="internalDFN">TV set</a>s and <a href="#dfn-stb" class="internalDFN">STB</a>s but can be presented on a wide range of devices. Different organizations and companies have have defined their own profiles of web technologies that can be used in a given ecosystem to author content. These profiles are supersets, subsets or both of several W3C specifications. The proliferation of such profiles is making challenging to write content that works well across devices. By working on a common TV profile within W3C it becomes easier to closely align ongoing efforts of web based TV services in order to avoid fragmentation.
+ </div>
+
+ <div id="coordinate-deployments" class="section">
+ <h4><span class="secno">1.2.3 </span>Coordinate deployments</h4>
+ The range of technologies available to web applications developers is theoretically wide. In practice, content developers have to fight with different levels of support of different specifications by different devices. This is inevitable since each implementer necessarily need to make a choice on what to implement and when. While in some ecosystems is fine to leave to each implementer to choose his own roadmap, in other ecosystems there is a need for coordination in order to harmonize the development cycle of the different stakeholders and provide a good user experience.
+ </div>
+
+ <div id="provide-a-complete-application-environment" class="section">
+ <h4><span class="secno">1.2.4 </span>Provide a complete application environment</h4>
+ Many W3C specifications leave intentionally undefined some components that are essential to build a full application environment for interactive TV services. For example, the [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification rely on "relevant specifications" to define rules for processing and rendering data coming from a media stream via an in-band track. Other examples of "variables" that are not specified in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] are supported video codecs or image formats. The same apply to other W3C specifications. Furthermore to provide a complete application environment, different specifications needs to be combined into one product, increasing the number of options and hence the level of fragmentation. This document aims to combine together relevant specification to provide a complete environment that can be used by different organizations as an application environment for their interactive TV services.
+ </div>
+
+ <div id="do-not-reinvent-the-wheel" class="section">
+ <h4><span class="secno">1.2.5 </span>Do not reinvent the wheel</h4>
+ Some groups defined or discussed extensions to existing web technologies in order to cover use cases relevant for such groups. Sometime different groups have designed multiple incompatible extensions to cover the same use case. Other times what at a first look was identified as a gap in the web platform is resulted in actually being already supported reusing existing specifications. Since many use cases are common among different regions and organizations, by making the result of such analysis available in one document the risk that different groups defines new technologies to cover areas that are already well covered by existing specification (hence causing fragmentation) is reduced.
+ </div>
+
+ <div id="a-tunable-meta-profile" class="section">
+ <h4><span class="secno">1.2.6 </span>A tunable meta-profile</h4>
+ A profile document is generally beneficial for the industry because it provides a common environment that all different stakeholders can rely on with the ultimate goal of providing the best possible user experience. In doing this, several things need to be considered that sometimes go beyond technical standard activities and are rather close to business model of stakeholders. Furthermore, there are many different devices capable of presenting interactive TV services with different hardware capabilities that may also vary over time. Therefore is impossible to find a profile that suites all business models and devices. It is still beneficial though to identify and define all common parts in a meta profile that can be tuned as needed by other organizations, trying to keep the differences at a minimum.
+ </div>
+
+ </div>
+
<div id="audience" class="section">
- <h3><span class="secno">1.2 </span>Audience</h3>
+ <h3><span class="secno">1.3 </span>Audience</h3>
</div>
<div id="scope" class="section">
- <h3><span class="secno">1.3 </span>Scope</h3>
+ <h3><span class="secno">1.4 </span>Scope</h3>
</div>
</div>
-<div class="informative section" id="goals">
-<!--OddPage--><h2><span class="secno">2. </span>Goals</h2><p><em>This section is non-normative.</em></p>
-This sections list the goals that have driven the work on this document.
+<div id="terminology" class="section">
+<!--OddPage--><h2><span class="secno">2. </span>Terminology</h2>
+ <div id="conformance" class="section"><h3><span class="secno">2.1 </span>Conformance</h3><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 <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>, and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
- <div id="avoid-obsolesce" class="section">
- <h3><span class="secno">2.1 </span>Avoid obsolesce</h3>
- In the past decades, many attempts have been made to create profiles suitable for use in a specific market and/or region, particularly in the TV space, by external organizations. These groups have created documents which are supersets, subsets or both of several W3C specifications. Often, these external documents become obsolete when the W3C improves the related specifications since the W3C has little or no knowledge of these external documents. By working on a common TV profile within W3C it becomes easier to closely align external organizations with W3C and with each other and allows the W3C to move this profile forward on a regular basis to avoid obsolescence.
- </div>
-
- <div id="avoid-fragmentation" class="section">
- <h3><span class="secno">2.2 </span>Avoid fragmentation</h3>
- Use of web technologies in different markets and regions to create interactive TV services is increasing. Different organizations and companies have have defined their own profiles of web technologies that can be used in a given ecosystem to author content. These profiles are supersets, subsets or both of several W3C specifications. The proliferation of such profiles is making challenging to write content that works well across devices. By working on a common TV profile within W3C it becomes easier to closely align ongoing efforts of web based TV services in order to avoid fragmentation.
</div>
-
- <div id="coordinate-deployments" class="section">
- <h3><span class="secno">2.3 </span>Coordinate deployments</h3>
- The range of technologies available for web applications developers is so theoretically wide. In practice content developers have to fight with different levels of support of different specification by different devices. This is inevitable since each implementer necessarily need to make a choice on what to implement and when. While in some ecosystems is fine to leave to each implementer to choose his own roadmap, in other ecosystems there is a need for coordination in order to harmonize the development cycle of the different stakeholders (CE manufacturers, Content providers, Content Authors, etc.) and provide a good user experience.
+ <div id="definitions" class="section">
+ <h3><span class="secno">2.2 </span>Definitions</h3>
+ <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-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-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>
+ <p></p>
</div>
+</div>
+
- <div id="provide-a-complete-application-environment" class="section">
- <h3><span class="secno">2.4 </span>Provide a complete application environment</h3>
- Many W3C specifications leave intentionally undefined some components that are essential to build a full application environment for interactive TV services. For example, the [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification rely on "relevant specifications" to define rules for processing and rendering data coming from a media stream via an in-band track. Other examples of "variables" that are not specified in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] are supported video codecs or image formats. The same apply to other specifications. Furthermore to provide a complete application environment, different specifications needs to be combined into one product, increasing the number of options and hence the level of fragmentation. This document aims to combine together relevant specification to provide a complete environment that can be used by different organization as application environment for their interactive TV services.
- </div>
-
- <div id="do-not-reinvent-the-wheel" class="section">
- <h3><span class="secno">2.5 </span>Do not reinvent the wheel</h3>
- Some groups (both inside and outside W3C) have done an analysis of available web technologies in order to see if they were suitable to cover relevant use cases. Often what at a first look was identified as a gap in the web platform is resulted in actually being already supported reusing existing specifications. Since many use cases are common among different regions and organization, by making the result of such analysis available in one document the risk that different groups defines new technologies to cover areas that are already well covered by existing specification (hence causing fragmentation) is reduced.
- </div>
-
- <div id="a-tunable-meta-profile" class="section">
- <h3><span class="secno">2.6 </span>A tunable meta-profile</h3>
- A profile document is generally beneficial for the industry because it provides a common environment that all different stake holders can rely on with the ultimate goal of providing the best possible user experience. In doing this, several things need to be considered that sometimes goes beyond technical standard activities and is rather close to business model of stake holders. Furthermore, there are many different devices capable of presenting interactive TV services with different hardware capabilities that may also vary over time. Is then impossible to find a profile that suites all business models and devices, is possible to keep such differences at a minimum, identifying all the common parts in a meta profile that can be tuned as needed by other organizations.
- </div>
-
-</div>
<div id="overview" class="section">
<!--OddPage--><h2><span class="secno">3. </span>Overview</h2>
@@ -593,7 +613,6 @@
</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><p>No normative references.</p></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>
+<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>