* few more CSS sections
authorGiuseppe Pascale <giuseppep@opera.com>
Fri, 20 Jan 2012 17:47:44 +0100
changeset 36 1b57e6a6dd57
parent 35 30f5e85a1415
child 37 3e606a840aee
* few more CSS sections
tvprofile/tv-src.html
tvprofile/tv.html
--- a/tvprofile/tv-src.html	Fri Jan 20 15:09:15 2012 +0100
+++ b/tvprofile/tv-src.html	Fri Jan 20 17:47:44 2012 +0100
@@ -15,7 +15,7 @@
 					preProcess : [],
                
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "unofficial",
+          specStatus:           "ED",
           
           // the specification's short name, as in http://www.w3.org/TR/short-name/
           shortName:            "tv-profile",
@@ -69,7 +69,7 @@
           wgURI:        "http://www.w3.org/2011/webtv/",
           
           // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "[email protected]",
+          wgPublicList: "public-web-and-tv",
           
           // URI of the patent status for this WG, for Rec-track documents
           // !!!! IMPORTANT !!!!
@@ -231,6 +231,29 @@
 	<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>CSS Properties</h2>
+		<div class=note> <a href="http://www.w3.org/TR/CSS2/">http://www.w3.org/TR/CSS2/</a></div>		
+		</section>
+		
+		<section>
+		<h2>CSS Device Adaptation (viewport)</h2>
+		<div class=note><a href="http://www.w3.org/TR/css-device-adapt/">http://www.w3.org/TR/css-device-adapt/</a></div>
+		</section>			
+
+		<section>
+		<h2>CSS 'view-mode' Media Feature</h2>
+		<div class=note> <a href="http://www.w3.org/TR/view-mode/">http://www.w3.org/TR/view-mode/</a></div>		
+		</section>
+		
+		<section>
+		<h2>CSS Selectors</h2>
+				<div class=note> 
+				<a href="http://www.w3.org/TR/CSS21/selector.html">http://www.w3.org/TR/CSS21/selector.html</a> and 
+				<a href="http://www.w3.org/TR/css3-selectors/">http://www.w3.org/TR/css3-selectors/</a></div>
+		</section>
+		
 		<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.
@@ -302,8 +325,6 @@
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
 				[[!CSS3-BG]] 
 		</section>		
-		
-		
 		<section id="css3-2d-tf">
 		<h2>CSS3 2D Transform</h2>
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
@@ -315,8 +336,11 @@
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
 				[[!CSS3-3D-TRANSFORMS]] 
 		</section>
-			
-			
+		
+	
+		
+		
+		
 	</section>
 		
 	<section id="xhr">
--- a/tvprofile/tv.html	Fri Jan 20 15:09:15 2012 +0100
+++ b/tvprofile/tv.html	Fri Jan 20 17:47:44 2012 +0100
@@ -475,20 +475,20 @@
 pre.sh_sourceCode .sh_paren { color: red; }
 pre.sh_sourceCode .sh_attribute { color: #006400; }
 
-</style><link href="tv.css" rel="stylesheet" type="text/css" charset="utf-8"><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&amp;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-20-january-2012">Unofficial Draft 20 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>
+</style><link href="tv.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
+	<body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">Web&amp;TV profile (provisional title)</h1><h2 id="subtitle">Guidelines for integration of interactive TV services in a Browser-based environment</h2><h2 id="w3c-editor-s-draft-20-january-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 20 January 2012</h2><dl><dt>This version:</dt><dd><a href=""></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/tv-profile/">http://www.w3.org/TR/tv-profile/</a></dd><dt>Previous version:</dt><dd>none</dd><dt>Editor:</dt><dd><span>Giuseppe Pascale</span>, <a href="http://www.opera.com/">Opera</a></dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2012 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</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="#intro" 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="#system-overview" class="tocxref"><span class="secno">3. </span>System Overview</a></li><li class="tocline"><a href="#application-model" class="tocxref"><span class="secno">4. </span>Application model</a><ul class="toc"><li class="tocline"><a href="#launching-applications" class="tocxref"><span class="secno">4.1 </span>Launching applications</a></li><li class="tocline"><a href="#client-side-applications" class="tocxref"><span class="secno">4.2 </span>Client side applications</a></li></ul></li><li class="tocline"><a href="#app-environment" class="tocxref"><span class="secno">5. </span>Application Environment</a><ul class="toc"><li class="tocline"><a href="#html" class="tocxref"><span class="secno">5.1 </span>HTML</a></li><li class="tocline"><a href="#scripting" class="tocxref"><span class="secno">5.2 </span>Scripting</a></li><li class="tocline"><a href="#css" class="tocxref"><span class="secno">5.3 </span>CSS</a><ul class="toc"><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">5.3.1 </span>CSS3 Fonts</a></li><li class="tocline"><a href="#css3-mq" class="tocxref"><span class="secno">5.3.2 </span>CSS3 Media Queries</a></li><li class="tocline"><a href="#css3-bg" class="tocxref"><span class="secno">5.3.3 </span>CSS3 Backgrounds and Borders</a></li><li class="tocline"><a href="#css3-2d-tf" class="tocxref"><span class="secno">5.3.4 </span>CSS3 2D Transform</a></li><li class="tocline"><a href="#css3-3d-tf" class="tocxref"><span class="secno">5.3.5 </span>CSS3 3D Transform</a></li></ul></li><li class="tocline"><a href="#xhr" class="tocxref"><span class="secno">5.4 </span>XML HTTP Request</a></li><li class="tocline"><a href="#dom" class="tocxref"><span class="secno">5.5 </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">5.6 </span>... (add more section for other web standards)</a></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">5.7 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#determine-available-input-methods" class="tocxref"><span class="secno">5.7.1 </span>Determine available input methods</a></li><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">5.7.2 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">5.7.3 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">5.7.4 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">5.7.5 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">5.8 </span>Content Developers Guidelines</a></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">6. </span>Formats and Protocols </a><ul class="toc"><li class="tocline"><a href="#exposing-transport-metadata-to-applications" class="tocxref"><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</a></li><li class="tocline"><a href="#discovery-and-communication-with-home-network-services" class="tocxref"><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</a></li></ul></li><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">7. </span>Testing</a><ul class="toc"><li class="tocline"><a href="#testing-infrastructure" class="tocxref"><span class="secno">7.1 </span>Testing Infrastructure</a></li></ul></li><li class="tocline"><a href="#performances" class="tocxref"><span class="secno">8. </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><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This document was published by the <a href="http://www.w3.org/2011/webtv/">Web and TV IG</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:[email protected]">[email protected]</a> (<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-web-and-tv/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#intro" 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="#system-overview" class="tocxref"><span class="secno">3. </span>System Overview</a></li><li class="tocline"><a href="#application-model" class="tocxref"><span class="secno">4. </span>Application model</a><ul class="toc"><li class="tocline"><a href="#launching-applications" class="tocxref"><span class="secno">4.1 </span>Launching applications</a></li><li class="tocline"><a href="#client-side-applications" class="tocxref"><span class="secno">4.2 </span>Client side applications</a></li></ul></li><li class="tocline"><a href="#app-environment" class="tocxref"><span class="secno">5. </span>Application Environment</a><ul class="toc"><li class="tocline"><a href="#html" class="tocxref"><span class="secno">5.1 </span>HTML</a></li><li class="tocline"><a href="#scripting" class="tocxref"><span class="secno">5.2 </span>Scripting</a></li><li class="tocline"><a href="#css" class="tocxref"><span class="secno">5.3 </span>CSS</a><ul class="toc"><li class="tocline"><a href="#css-properties" class="tocxref"><span class="secno">5.3.1 </span>CSS Properties</a></li><li class="tocline"><a href="#css-device-adaptation--viewport" class="tocxref"><span class="secno">5.3.2 </span>CSS Device Adaptation (viewport)</a></li><li class="tocline"><a href="#css--view-mode--media-feature" class="tocxref"><span class="secno">5.3.3 </span>CSS 'view-mode' Media Feature</a></li><li class="tocline"><a href="#css-selectors" class="tocxref"><span class="secno">5.3.4 </span>CSS Selectors</a></li><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">5.3.5 </span>CSS3 Fonts</a></li><li class="tocline"><a href="#css3-mq" class="tocxref"><span class="secno">5.3.6 </span>CSS3 Media Queries</a></li><li class="tocline"><a href="#css3-bg" class="tocxref"><span class="secno">5.3.7 </span>CSS3 Backgrounds and Borders</a></li><li class="tocline"><a href="#css3-2d-tf" class="tocxref"><span class="secno">5.3.8 </span>CSS3 2D Transform</a></li><li class="tocline"><a href="#css3-3d-tf" class="tocxref"><span class="secno">5.3.9 </span>CSS3 3D Transform</a></li></ul></li><li class="tocline"><a href="#xhr" class="tocxref"><span class="secno">5.4 </span>XML HTTP Request</a></li><li class="tocline"><a href="#dom" class="tocxref"><span class="secno">5.5 </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">5.6 </span>... (add more section for other web standards)</a></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">5.7 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#determine-available-input-methods" class="tocxref"><span class="secno">5.7.1 </span>Determine available input methods</a></li><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">5.7.2 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">5.7.3 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">5.7.4 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">5.7.5 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">5.8 </span>Content Developers Guidelines</a></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">6. </span>Formats and Protocols </a><ul class="toc"><li class="tocline"><a href="#exposing-transport-metadata-to-applications" class="tocxref"><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</a></li><li class="tocline"><a href="#discovery-and-communication-with-home-network-services" class="tocxref"><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</a></li></ul></li><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">7. </span>Testing</a><ul class="toc"><li class="tocline"><a href="#testing-infrastructure" class="tocxref"><span class="secno">7.1 </span>Testing Infrastructure</a></li></ul></li><li class="tocline"><a href="#performances" class="tocxref"><span class="secno">8. </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 id="intro" class="informative section">
 <!--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>
-	<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>   	
+	<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 <acronym title="World Wide Web Consortium">W3C</acronym> specifications. Often these documents have been written without a direct involvement of relevant <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> 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">
@@ -497,12 +497,12 @@
 
 		<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.
+		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 <acronym title="World Wide Web Consortium">W3C</acronym> specifications. Often, these external documents become obsolete when the <acronym title="World Wide Web Consortium">W3C</acronym> improves the related specifications since the <acronym title="World Wide Web Consortium">W3C</acronym> has little or no knowledge of these external documents. By working on a common TV profile within <acronym title="World Wide Web Consortium">W3C</acronym> it becomes easier to closely align external organizations with <acronym title="World Wide Web Consortium">W3C</acronym> and with each other and allows the <acronym title="World Wide Web Consortium">W3C</acronym> 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.
+			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 <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> 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">
@@ -512,7 +512,7 @@
 
 		<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.   
+		  Many <acronym title="World Wide Web Consortium">W3C</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> 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">
@@ -629,8 +629,29 @@
 	<h3><span class="secno">5.3 </span>CSS</h3>
 		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 href="#dfn-browser" class="internalDFN">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>
+	
+		<div id="css-properties" class="section">
+		<h4><span class="secno">5.3.1 </span>CSS Properties</h4>
+		<div class="note"> <a href="http://www.w3.org/TR/CSS2/">http://www.w3.org/TR/CSS2/</a></div>		
+		</div>
+		
+		<div id="css-device-adaptation--viewport" class="section">
+		<h4><span class="secno">5.3.2 </span>CSS Device Adaptation (viewport)</h4>
+		<div class="note"><a href="http://www.w3.org/TR/css-device-adapt/">http://www.w3.org/TR/css-device-adapt/</a></div>
+		</div>			
+
+		<div id="css--view-mode--media-feature" class="section">
+		<h4><span class="secno">5.3.3 </span>CSS 'view-mode' Media Feature</h4>
+		<div class="note"> <a href="http://www.w3.org/TR/view-mode/">http://www.w3.org/TR/view-mode/</a></div>		
+		</div>
+		<div id="css-selectors" class="section">
+		<h4><span class="secno">5.3.4 </span>CSS Selectors</h4>
+				<div class="note"> 
+				<a href="http://www.w3.org/TR/CSS21/selector.html">http://www.w3.org/TR/CSS21/selector.html</a> and 
+				<a href="http://www.w3.org/TR/css3-selectors/">http://www.w3.org/TR/css3-selectors/</a></div>
+		</div>
 		<div id="css3-fonts" class="section">
-		<h4><span class="secno">5.3.1 </span>CSS3 Fonts</h4>
+		<h4><span class="secno">5.3.5 </span>CSS3 Fonts</h4>
 			The [<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-FONTS">CSS3-FONTS</a></cite>] module describes how font properties are specified and how font resources are loaded dynamically.
 			The features marked as included below <em class="rfc2119" title="shall">shall</em> be supported by conforming <a href="#dfn-browser" class="internalDFN">browser</a>s. 
 			<dt>Properties</dt>
@@ -689,32 +710,33 @@
 		</div>
 			
 		<div id="css3-mq" class="section">
-			<h4><span class="secno">5.3.2 </span>CSS3 Media Queries</h4>
+			<h4><span class="secno">5.3.6 </span>CSS3 Media Queries</h4>
 				The [<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-MEDIAQUERIES">CSS3-MEDIAQUERIES</a></cite>] module extend the functionality of media types by allowing more precise labeling of style sheets.
 				A conforming <a href="#dfn-browser" class="internalDFN">browser</a> <em class="rfc2119" title="shall">shall</em> support media queries as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-MEDIAQUERIES">CSS3-MEDIAQUERIES</a></cite>].
 				<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>
 		</div>
 		
 		<div id="css3-bg" class="section">
-		<h4><span class="secno">5.3.3 </span>CSS3 Backgrounds and Borders</h4>
+		<h4><span class="secno">5.3.7 </span>CSS3 Backgrounds and Borders</h4>
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
 				[<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-BG">CSS3-BG</a></cite>] 
 		</div>		
-		
-		
 		<div id="css3-2d-tf" class="section">
-		<h4><span class="secno">5.3.4 </span>CSS3 2D Transform</h4>
+		<h4><span class="secno">5.3.8 </span>CSS3 2D Transform</h4>
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
 				[<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-2D-TRANSFORMS">CSS3-2D-TRANSFORMS</a></cite>] 
 		</div>
 			
 		<div id="css3-3d-tf" class="section">
-		<h4><span class="secno">5.3.5 </span>CSS3 3D Transform</h4>
+		<h4><span class="secno">5.3.9 </span>CSS3 3D Transform</h4>
 			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
 				[<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-3D-TRANSFORMS">CSS3-3D-TRANSFORMS</a></cite>] 
 		</div>
-			
-			
+		
+	
+		
+		
+		
 	</div>
 		
 	<div id="xhr" class="section">
@@ -740,26 +762,25 @@
 					<li>touch screen</li>
 					<li>TV Remote</li>
 				</ul>
-				On the other end there are also mixed solutions. So another possible sub-classification is:
+				On the other end there are also mixed solutions. So another possible classification for input is:
 				<ul>
-					<li>Pointers
+					<li>Pointer based:
 					<ul>
 						<li>accurate pointing (mouse, trackball, stylus touch)</li>
 						<li>rough pointing (finger touch, wii)</li>
 						<li>no pointing
 					</li></ul>
 					</li>
-					<li>Keyboard
+					<li>Key based:
 						<ul>
  							<li>full keyboard (desktop, laptop, blackberry)</li>
  							<li>limited keyboard (TV remote, nintendo ds, feature phones)</li>
 							<li>no keyboard</li>
 						</ul>
 					</li>
-					</ul>				
-					
+					</ul>
 					<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)
+					But there seem to be no universal method to determine input capabilities.	Need to discuss this with relevant WGs (CSS, WebApps, WebEvents)
 			</p></div>
 		</div>
 		<div id="traditional-remote-controls" class="section">
@@ -819,7 +840,7 @@
 		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/framework/">W3C Test Suite Framework</a></li>		
+			<li><a href="http://w3c-test.org/framework/"><acronym title="World Wide Web Consortium">W3C</acronym> Test Suite Framework</a></li>		
 		</ul>	
 	</div>
 	<div id="testing-infrastructure" class="section"><h3><span class="secno">7.1 </span>Testing Infrastructure</h3></div>