--- a/tvprofile/tv-src.html Wed Jan 04 16:20:42 2012 +0100
+++ b/tvprofile/tv-src.html Wed Jan 04 16:33:26 2012 +0100
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<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 ===
@@ -90,7 +90,7 @@
<section>
<h2>Background</h2>
- <p>There is an increasing number of content provider 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 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, leading to multiple incompatible solutions addressing the same use case.</p>
+ <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>
</section>
@@ -110,22 +110,22 @@
<section>
<h2>Coordinate deployments</h2>
- 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.
+ 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.
</section>
<section>
<h2>Provide a complete application environment</h2>
- Many W3C specifications leave intentionally undefined some components that are essential to build a full application environment for interactive TV services. For example, the [[HTML5]] 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 [[HTML5]] 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.
+ Many W3C specifications leave intentionally undefined some components that are essential to build a full application environment for interactive TV services. For example, the [[HTML5]] 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 [[HTML5]] 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.
</section>
<section>
<h2>Do not reinvent the wheel</h2>
- 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.
+ 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.
</section>
<section>
<h2>A tunable meta-profile</h2>
- 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.
+ 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.
</section>
</section>