general renaming
authorGiuseppe Pascale <giuseppep@opera.com>
Tue, 13 Mar 2012 18:10:08 +0100
changeset 41 12ae15b25664
parent 40 66665b220f94
child 42 7178511229c7
general renaming
media-profile/Overview-20120207.html
media-profile/Overview-src.html
media-profile/Overview.html
media-profile/style.css
media-profile/tv-20120207.html
media-profile/tv-src.html
media-profile/tv.css
media-profile/tv.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/media-profile/Overview-20120207.html	Tue Mar 13 18:10:08 2012 +0100
@@ -0,0 +1,888 @@
+<!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&amp;TV profile (provisional title)</title>
+		<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+    <!-- 
+      === NOTA BENE ===
+      For the three scripts below, if your spec resides on dev.w3 you can check them
+      out in the same tree and use relative links so that they'll work offline,
+     -->
+		
+		
+  <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a {
+    text-decoration:    none;
+}
+
+a .secno {
+    color:  #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+    border-top: 1px solid #ff4500;
+    border-bottom: 1px solid #ff4500;
+    padding:    1em;
+    margin-top: 1em;
+}
+
+pre.example::before {
+    content:    "Example";
+    display:    block;
+    width:      150px;
+    background: #ff4500;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+    padding:    1em;
+    margin: 1em 0em 0em;
+    border: 1px solid #f00;
+    background: #ffc;
+}
+
+.issue::before {
+    content:    "Issue";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #f00;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+.note {
+    margin: 1em 0em 0em;
+    padding:    1em;
+    border: 2px solid #cff6d9;
+    background: #e2fff0;
+}
+
+.note::before {
+    content:    "Note";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #cff6d9;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+    border: solid #bebebe 1px;
+    margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+    margin: 1.5em 0.5em 1em 1em;
+    font-weight: bold;
+    font-style: italic;
+}
+
+span.practicelab   { background: #dfffff; }
+
+span.practicelab {
+    position: relative;
+    padding: 0 0.5em;
+    top: -1.5em;
+}
+
+p.practicedesc {
+    margin: 1.5em 0.5em 1em 1em;
+}
+
[email protected] screen {
+    p.practicedesc {
+        position: relative;
+        top: -2em;
+        padding: 0;
+        margin: 1.5em 0.5em -1em 1em;
+    }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+  background-color: white;
+  color: black;
+  font-style: normal;
+  font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
+pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+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-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-07-february-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 07 February 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><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="#packaged-applications" class="tocxref"><span class="secno">4.2 </span>Packaged 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><ul class="toc"><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">5.3.5.1 </span>Testing</a></li></ul></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-1" 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 <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">
+	<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 <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 <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">
+		<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 <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">
+		<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.3 </span>Audience</h3>
+	...
+	</div>
+	
+	<div id="scope" class="section">
+	<h3><span class="secno">1.4 </span>Scope</h3>
+		The scope of this document is limited to:
+		<ul>
+			<li>provide references to a set of languages that shall be supported by <a href="#dfn-device" class="internalDFN">device</a>s and can be used by <a title="content provider">content</a> and <a>service provider</a><a>s to author content and services to be presented to the </a><a>end user</a>.</li>
+			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
+		</ul>
+		<p>
+		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
+		</p><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 href="#dfn-tv-service" class="internalDFN">TV service</a>.    
+	</p></div>
+	
+</div>
+
+<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>
+	
+	<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 <a href="#dfn-device" class="internalDFN">device</a> 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>broadband network</a>s or streamed from other devices. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a href="#dfn-tv-service" class="internalDFN">TV service</a>s</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>broadband network</a>s or streamed from other devices.</li>
+			<li><dfn id="dfn-dvb">DVB</dfn>:tbd</li>
+			<li><dfn id="dfn-atsc">ATSC</dfn>:tbd</li>
+			<li><dfn id="dfn-isdb">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></p>
+	</div>
+</div>
+
+<div id="system-overview" class="section">
+	<!--OddPage--><h2><span class="secno">3. </span>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 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 id="dfn-tv-service">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" id="dfn-scheduled-service">scheduled</dfn> or <dfn title="linear service" id="dfn-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" id="dfn-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><p>
+		In order to consume them, users need a <dfn id="dfn-device">device</dfn> that is able to present TV services. Traditionally TV services have been consumed via <a href="#dfn-tv-set" class="internalDFN">TV set</a>s or <a href="#dfn-stb" class="internalDFN">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><p>
+		<a href="#dfn-tv-service" class="internalDFN">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 id="dfn-broadcast-network">broadcast network</dfn>. Different standards have been defined for such purpose, such as <a href="#dfn-dvb" class="internalDFN">DVB</a>, <a href="#dfn-atsc" class="internalDFN">ATSC</a>, <a href="#dfn-isdb" class="internalDFN">ISDB</a>. <a href="#dfn-tv-service" class="internalDFN">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 id="dfn-home-network">home network</dfn>. The term <a href="#dfn-home-network" class="internalDFN">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><p>
+		To provide a level of interactivity, <a href="#dfn-tv-service" class="internalDFN">TV service</a>s may be associated to or delivered as <a href="#dfn-application" class="internalDFN">application</a>s.
+</p></div>
+
+<div id="application-model" class="section">
+<!--OddPage--><h2><span class="secno">4. </span>Application model</h2>
+	
+	For the purposes of this document the term <dfn id="dfn-application">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 href="#dfn-application" class="internalDFN">application</a>s, <a href="#dfn-device" class="internalDFN">device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef">section 5. Application Environment</a>.
+	
+	<div class="informative section" id="launching-applications">
+		<h3><span class="secno">4.1 </span>Launching applications</h3><p><em>This section is non-normative.</em></p>
+	</div>
+	
+	<div id="packaged-applications" class="section">
+	<h3><span class="secno">4.2 </span>Packaged applications</h3>
+	<div class="issue"> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></p></div>
+		While <a href="#dfn-application" class="internalDFN">application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a href="#dfn-browser" class="internalDFN">browser</a> when required, sometimes a single download and installation on a <a href="#dfn-device" class="internalDFN">device</a> is desirable. In order to enable this, <a href="#dfn-device" class="internalDFN">device</a>s <em class="rfc2119" title="shall">shall</em> support the packaging format defined by the [<cite><a class="bibref" rel="biblioentry" href="#bib-WIDGETS">WIDGETS</a></cite>] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a href="#dfn-browser" class="internalDFN">browser</a>.
+	</div>
+</div>
+
+
+<div id="app-environment" class="section">
+<!--OddPage--><h2><span class="secno">5. </span>Application Environment</h2>
+ This section lists which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile and that can be used to author <a href="#dfn-application" class="internalDFN">application</a>s. <a href="#dfn-browser" class="internalDFN">Browser</a>s may support more languages than the ones listed in this section.
+
+	<div id="html" class="section">
+	<h3><span class="secno">5.1 </span>HTML</h3>
+		<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><p>The [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification defines conformance requirements for user agents and documents. <a href="#dfn-application" class="internalDFN">Application</a>s and authoring tools <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for documents unless differently specified in this document. <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>].
+		</p><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 href="#dfn-browser" class="internalDFN">browser</a>s in connection with HTML5 are listed in the following sections. 
+	</p></div>
+	<div id="scripting" class="section">
+	<h3><span class="secno">5.2 </span>Scripting</h3>
+		<dfn id="dfn-scripts">Scripts</dfn> are small programs that can be embedded into <a href="#dfn-application" class="internalDFN">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 href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">scripting</a> as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. </li>
+			<li><a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] scripting language</li> 
+		</ul>
+	</div>
+
+	<div id="css" class="section">
+	<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.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. 
+			<p>
+			</p><dt>Properties</dt>
+			<dd>
+			<table class="profile">
+  		<tbody><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>
+			</tbody></table>
+			</dd>
+				
+			<dt>Descriptors</dt>
+			<dd>
+			<table class="profile">
+  		<tbody><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>
+			</tbody></table>
+			</dd>
+			<div id="testing" class="section">
+			<h5><span class="secno">5.3.5.1 </span>Testing</h5>
+			
+			</div>
+		</div>
+			
+		<div id="css3-mq" class="section">
+			<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.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.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.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">
+	<h3><span class="secno">5.4 </span>XML HTTP Request</h3>
+	</div>
+	
+	<div id="dom" class="section">
+	<h3><span class="secno">5.5 </span>Document Object Model (DOM)</h3>
+	</div>
+
+	<div id="x...--add-more-section-for-other-web-standards" class="section">
+	<h3><span class="secno">5.6 </span>... (add more section for other web standards)</h3>
+	</div>
+			
+	<div id="input-methods" class="section">
+		<h3><span class="secno">5.7 </span>Input Methods</h3>
+		<div id="determine-available-input-methods" class="section">
+		<h4><span class="secno">5.7.1 </span>Determine available input methods</h4>
+			<div class="issue">
+				<p>I think we may want to be able to differentiate at least between these 3 set ups:
+				</p><ul>
+					<li>keyboard and mouse</li>
+					<li>touch screen</li>
+					<li>TV Remote</li>
+				</ul>
+				On the other end there are also mixed solutions. So another possible classification for input is:
+				<ul>
+					<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>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>
+					<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)
+			</p></div>
+		</div>
+		<div id="traditional-remote-controls" class="section">
+			<h4><span class="secno">5.7.2 </span>Traditional Remote Controls</h4>
+			<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>
+		</div>
+		<div id="touch-screens" class="section">
+			<h4><span class="secno">5.7.3 </span>Touch screens</h4>
+			[<cite><a class="bibref" rel="biblioentry" href="#bib-TOUCH-EVENTS">TOUCH-EVENTS</a></cite>]
+		</div>
+		<div id="mouse-and-keyboard" class="section">
+			<h4><span class="secno">5.7.4 </span>Mouse and Keyboard</h4>
+		</div>
+		<div id="other-input-devices" class="section">
+			<h4><span class="secno">5.7.5 </span>Other input devices</h4>
+		</div>
+	</div>
+	
+	<div class="informative section" id="content-developers-guidelines">
+		<h3><span class="secno">5.8 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
+	</div>
+	
+</div>
+
+<div id="formats-and-protocols" class="section">
+	<!--OddPage--><h2><span class="secno">6. </span>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&amp;tv IG. Therefore it should describe things like:
+			<ul>
+				<li>adaptive streaming
+				</li><li>parental control
+				</li><li>content protection
+				</li><li>Subtitles (webvtt,TTML etc.)
+				</li><li>discovery and control of home network services
+				</li><li>dynamic insertion of advertising into live broadcast
+				</li><li>...
+			</li></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> 
+
+		<div id="exposing-transport-metadata-to-applications" class="section"><h3><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</h3></div>
+		<div id="discovery-and-communication-with-home-network-services" class="section">
+		<h3><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</h3>
+			<div class="note">
+				No standard available at the moment. Useful references:
+				<ul>
+					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
+					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
+					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
+				</ul>			
+			</div>		
+		</div>
+			
+</div>
+
+<div id="testing-1" class="section">
+<!--OddPage--><h2><span class="secno">7. </span>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/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>
+	
+
+</div>
+
+<div id="performances" class="section">
+	<!--OddPage--><h2><span class="secno">8. </span>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 <em class="rfc2119" title="shall not">shall not</em> support N, B may support N, C <em class="rfc2119" title="shall">shall</em> support N?</li>
+		</ul>
+	</div>
+</div>
+
+<div class="appendix section" id="acknowledgements">
+	<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+	<p> Thanks to ... for their contributions to this document</p>
+	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
+	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
+</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><dl class="bibliography"><dt id="bib-CSS3-2D-TRANSFORMS">[CSS3-2D-TRANSFORMS]</dt><dd>Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href="http://www.w3.org/TR/css3-2d-transforms/"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-2d-transforms/">http://www.w3.org/TR/css3-2d-transforms/</a> 
+</dd><dt id="bib-CSS3-3D-TRANSFORMS">[CSS3-3D-TRANSFORMS]</dt><dd>Dean Jackson; David Hyatt; Chris Marrin. <a href="http://www.w3.org/TR/css3-3d-transforms/"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-3d-transforms/">http://www.w3.org/TR/css3-3d-transforms</a> 
+</dd><dt id="bib-CSS3-BG">[CSS3-BG]</dt><dd>Elika J. Etemad; Bert Bos; Brad Kemper. <a href="http://www.w3.org/TR/css3-background/"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-background/">http://www.w3.org/TR/css3-background/</a> 
+</dd><dt id="bib-CSS3-FONTS">[CSS3-FONTS]</dt><dd>John Daggett (Mozilla). <a href="http://www.w3.org/TR/css3-fonts"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href="http://www.w3.org/TR/css3-fonts">http://www.w3.org/TR/css3-fonts</a> 
+</dd><dt id="bib-CSS3-MEDIAQUERIES">[CSS3-MEDIAQUERIES]</dt><dd>H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href="http://www.w3.org/TR/css3-mediaqueries/"><cite>Media Queries</cite></a>  URL: <a href="http://www.w3.org/TR/css3-mediaqueries/">http://www.w3.org/TR/css3-mediaqueries/</a> 
+</dd><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> 
+</dd><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><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><dt id="bib-TOUCH-EVENTS">[TOUCH-EVENTS]</dt><dd>Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href="http://www.w3.org/TR/touch-events/"><cite>Touch Events version 1</cite></a> URL: <a href="http://www.w3.org/TR/touch-events/">http://www.w3.org/TR/touch-events</a>
+</dd><dt id="bib-WIDGETS">[WIDGETS]</dt><dd>Marcos Cáceres. <a href="http://www.w3.org/TR/widgets/"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/widgets/">http://www.w3.org/TR/widgets/</a> 
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/media-profile/Overview-src.html	Tue Mar 13 18:10:08 2012 +0100
@@ -0,0 +1,465 @@
+<!DOCTYPE html>
+<html>
+	<head>
+		<title>Web Media profile</title>
+		<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+    <!-- 
+      === NOTA BENE ===
+      For the three scripts below, if your spec resides on dev.w3 you can check them
+      out in the same tree and use relative links so that they'll work offline,
+     -->
+		<script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+		<!--<script src='2009/dap/ReSpec.js/js/respec.js' class='remove'></script> -->
+		<script class='remove'>		
+
+		var respecConfig = {
+					preProcess : [],
+               
+          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+          specStatus:           "ED",
+          
+          // the specification's short name, as in http://www.w3.org/TR/short-name/
+          shortName:            "webtv-profile",
+
+          // if your specification has a subtitle that goes below the main
+          // formal title, define it here
+          subtitle   :  "Guidelines for integration of interactive media services in a browser-based environment",
+
+          // if you wish the publication date to be other than today, set this
+          // publishDate:  "2009-08-06",
+
+          // if the specification's copyright date is a range of years, specify
+          // the start date here:
+          // copyrightStart: "2005"
+
+          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+          // and its maturity status
+          // previousPublishDate:  "1977-03-15",
+          // previousMaturity:  "WD",
+
+          // if there a publicly available Editor's Draft, this is the link
+          edDraftURI:           "",
+
+          // if this is a LCWD, uncomment and set the end of its review period
+          // lcEnd: "2009-08-05",
+
+          // if you want to have extra CSS, append them to this list
+          // it is recommended that the respec.css stylesheet be kept
+          extraCSS:	["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css",
+          						//"2009/dap/ReSpec.js/css/respec.css",
+          						"tv.css"],
+
+          // editors, add as many as you like
+          // only "name" is required
+          editors:  [
+              { name: "Giuseppe Pascale", url: "",
+                company: "Opera", companyURL: "http://www.opera.com/" },
+          ],
+          // authors, add as many as you like. 
+          // This is optional, uncomment if you have authors as well as editors.
+          // only "name" is required. Same format as editors.
+
+          //authors:  [
+          //    { name: "Your Name", url: "http://example.org/",
+          //      company: "Your Company", companyURL: "http://example.com/" },
+          //],
+          
+          // name of the WG
+          wg:           "Web and TV IG",
+          
+          // URI of the public WG page
+          wgURI:        "http://www.w3.org/2011/webtv/",
+          
+          // name (with the @w3c.org) of the public mailing to which comments are due
+          wgPublicList: "public-web-and-tv",
+          
+          // URI of the patent status for this WG, for Rec-track documents
+          // !!!! IMPORTANT !!!!
+          // This is important for Rec-track documents, do not copy a patent URI from a random
+          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+          // Team Contact.
+          wgPatentURI:  "",
+      };
+      
+		</script>
+  </head>
+	<body>
+<section id='abstract'>
+			
+</section>
+
+<section id="intro" class="informative">
+<h2>Introduction</h2>
+
+	<section>
+	<h2>Background</h2>
+	<p>There is an increasing number of content and service providers worldwide that are deploying interactive video 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>
+	
+	<section>
+	<h2>Design Goals</h2>
+		This sections list the goals that have driven the work on this document.
+
+		<section>
+		<h2>Avoid obsolesce</h2>
+		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.
+	</section>
+	
+		<section>
+		<h2>Improve interoperability</h2>
+			Use of web technologies in different markets and regions to create interactive TV services is increasing. TV services are not relegated anymore to <a>TV set</a>s and <a>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.
+	</section>
+	
+		<section>
+		<h2>Coordinate deployments</h2>
+		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 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 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 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>
+
+	<section>
+	<h2>Audience</h2>
+	...
+	</section>
+	
+	<section>
+	<h2>Scope</h2>
+		The scope of this document is limited to:
+		<ul>
+			<li>provide references to a set of languages that shall be supported by <a>device</a>s and can be used by <a title="content provider">content</a> and <a>service provider<a>s to author content and services to be presented to the <a>end user</a>.</li>
+			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
+		</ul>
+		<p>
+		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
+		<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>
+
+<section id="terminology">
+<h2>Terminology</h2>
+
+	<section id="conformance">
+	
+	</section>
+	
+	<section>				
+	<h3>Definitions</h3>
+	<p>
+		For the purposes of the present document, the following definitions apply:
+		<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. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a>TV service</a>s</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>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>
+	<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 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 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 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.
+</section>
+
+<section>
+<h2>Application model</h2>
+	
+	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 class="informative">
+		<h2>Launching applications</h2>
+	</section>
+	
+	<section>
+	<h2>Packaged applications</h2>
+	<div class=issue> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></div>
+		While <a>application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a>browser</a> when required, sometimes a single download and installation on a <a>device</a> is desirable. In order to enable this, <a>device</a>s MUST support the packaging format defined by the [[!WIDGETS]] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a>browser</a>.
+	</section>
+</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 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 MUST comply with conformance requirements for documents unless differently specified in this document. <a>Browser</a>s MUST comply with conformance requirements for user agents unless differently specified in this document; in particular browsers MUST 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 MUST support <a class="externalDFN">scripting</a> as defined in [[!HTML5]]. </li>
+			<li><a>Browser</a>s MUST support [[!ECMA-262]] scripting language</li> 
+		</ul>
+	</section>
+
+	<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. 
+	
+		<section id="css-properties">
+		<h2>CSS Properties</h2>
+		<a>Browser</a>s MUST support [[!CSS21]].
+		</section>
+		
+		<section id="css-at-rules">
+			<h2>CSS AT-rules</h2>
+			<div class="note">
+				<ul>
+				<li><a href="http://www.w3.org/TR/CSS2/syndata.html#at-rules">http://www.w3.org/TR/CSS2/syndata.html#at-rules</a></li>
+				<li><a href="http://www.w3.org/TR/css3-syntax/#at-rules">http://www.w3.org/TR/css3-syntax/#at-rules</a></li>
+				</ul>
+			</div>
+		</section>
+
+		<section id="css3-box">
+			<h2>CSS3 Basic Box Model</h2>
+			<div class="note"><a href="http://www.w3.org/TR/css3-box/">http://www.w3.org/TR/css3-box/</a></div>
+		</section>
+
+		<section id="css3-ui">
+			<h2>CSS3 Basic User Interface</h2>
+			<div class="note"><a href="http://www.w3.org/TR/css3-ui/">http://www.w3.org/TR/css3-ui/</a></div>
+		</section>
+		
+		<section id="css3-text">
+			<h2>CSS3 Text Module</h2>
+			<div class="note"><a href="http://dev.w3.org/csswg/css3-text/">http://dev.w3.org/csswg/css3-text/</a></div>
+		</section>		
+		
+		<section id="css3-multicol">
+			<h2>CSS3 Multi-column Layout</h2>
+			<div class="note"><a href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412/">http://www.w3.org/TR/2011/CR-css3-multicol-20110412/</a></div>
+		</section>
+		
+		<section id="cssom-view">
+			<h2>CSSOM View</h2>
+			<div class="note"><a href="http://dev.w3.org/csswg/cssom-view/">http://dev.w3.org/csswg/cssom-view/</a></div>
+		</section>
+		
+		
+		<section id="css-viewport">
+		<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 id="css-viewmode">
+		<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>
+		<div class=issue> Industry specifications may define additional mapping between CSS view modes and "system" view modes defined by such specifications</div>
+		</section>
+		
+		<section id="css-selectors">
+		<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.
+		</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> MUST 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 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>
+				
+		<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 id="css3-transitions"> 
+			<h2>CSS3 Transitions</h2>
+			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
+			<div class="note"><a href="http://www.w3.org/TR/css3-transitions/">http://www.w3.org/TR/css3-transitions/</a></div>
+		</section>
+			
+		
+	</section>
+		
+	<section id="xhr">
+	<h2>XML HTTP Request</h2>
+		<div class=note><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></div>	
+	</section>
+	
+	<section id="dom">
+	<h2>Document Object Model (DOM)</h2>
+	<div note="issue">
+		Should be enough to rely on HTML5 here, i.e. on this section
+		<a href="http://dev.w3.org/html5/spec/Overview.html#dependencies">http://dev.w3.org/html5/spec/Overview.html#dependencies</a>
+	</div>
+	</section>
+		
+	<section>
+		<h2>Input Methods</h2>
+		<section>
+		<h2>Determine available input methods</h2>
+			<div class="issue">
+				<p>I think we may want to be able to differentiate at least between these 3 set ups:
+				<ul>
+					<li>keyboard and mouse</li>
+					<li>touch screen</li>
+					<li>TV Remote</li>
+				</ul>
+				On the other end there are also mixed solutions. So another possible classification for input is:
+				<ul>
+					<li>Pointer based:
+					<ul>
+						<li>accurate pointing (mouse, trackball, stylus touch)</li>
+						<li>rough pointing (finger touch, wii)</li>
+						<li>no pointing
+					</ul>
+					</li>
+					<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>
+					<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>
+		</section>
+		<section>
+			<h2>Other input devices</h2>
+		</section>
+	</section>
+	
+	<section class="informative">
+		<h2>Content Developers Guidelines</h2>
+	</section>
+	
+</section>
+
+<section>
+	<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
+				<li>parental control
+				<li>content protection
+				<li>Subtitles (webvtt,TTML etc.)
+				<li>discovery and control of home network services
+				<li>dynamic insertion of advertising into live broadcast
+				<li>...
+			</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 Transport Metadata to Applications</h2></section>
+		<section>
+		<h2>Discovery and Communication with Home Network Services</h2>
+			<div class="note">
+				No standard available at the moment. Useful references:
+				<ul>
+					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
+					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
+					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
+				</ul>			
+			</div>		
+		</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/framework/">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 MUST NOT support N, B may support N, C MUST support N?</li>
+		</ul>
+	</div>
+</section>
+
+<section class='appendix'>
+	<h2>Acknowledgements</h2>
+	<p> Thanks to ... for their contributions to this document</p>
+	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
+	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
+</section>
+
+	</body>
+</html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/media-profile/Overview.html	Tue Mar 13 18:10:08 2012 +0100
@@ -0,0 +1,873 @@
+<!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 Media profile</title>
+		<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+    <!-- 
+      === NOTA BENE ===
+      For the three scripts below, if your spec resides on dev.w3 you can check them
+      out in the same tree and use relative links so that they'll work offline,
+     -->
+		
+		<!--<script src='2009/dap/ReSpec.js/js/respec.js' class='remove'></script> -->
+		
+  <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a {
+    text-decoration:    none;
+}
+
+a .secno {
+    color:  #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+    border-top: 1px solid #ff4500;
+    border-bottom: 1px solid #ff4500;
+    padding:    1em;
+    margin-top: 1em;
+}
+
+pre.example::before {
+    content:    "Example";
+    display:    block;
+    width:      150px;
+    background: #ff4500;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+    padding:    1em;
+    margin: 1em 0em 0em;
+    border: 1px solid #f00;
+    background: #ffc;
+}
+
+.issue::before {
+    content:    "Issue";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #f00;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+.note {
+    margin: 1em 0em 0em;
+    padding:    1em;
+    border: 2px solid #cff6d9;
+    background: #e2fff0;
+}
+
+.note::before {
+    content:    "Note";
+    display:    block;
+    width:  150px;
+    margin: -1.5em 0 0.5em 0;
+    font-weight:    bold;
+    border: 1px solid #cff6d9;
+    background: #fff;
+    padding:    3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+    border: solid #bebebe 1px;
+    margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+    margin: 1.5em 0.5em 1em 1em;
+    font-weight: bold;
+    font-style: italic;
+}
+
+span.practicelab   { background: #dfffff; }
+
+span.practicelab {
+    position: relative;
+    padding: 0 0.5em;
+    top: -1.5em;
+}
+
+p.practicedesc {
+    margin: 1.5em 0.5em 1em 1em;
+}
+
[email protected] screen {
+    p.practicedesc {
+        position: relative;
+        top: -2em;
+        padding: 0;
+        margin: 1.5em 0.5em -1em 1em;
+    }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+  background-color: white;
+  color: black;
+  font-style: normal;
+  font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
+pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+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-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 Media profile</h1><h2 id="subtitle">Guidelines for integration of interactive video services in a browser-based environment</h2><h2 id="w3c-editor-s-draft-28-february-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 28 February 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/webtv-profile/">http://www.w3.org/TR/webtv-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><p>
+			
+</p></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="#packaged-applications" class="tocxref"><span class="secno">4.2 </span>Packaged 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-at-rules" class="tocxref"><span class="secno">5.3.2 </span>CSS AT-rules</a></li><li class="tocline"><a href="#css3-box" class="tocxref"><span class="secno">5.3.3 </span>CSS3 Basic Box Model</a></li><li class="tocline"><a href="#css3-ui" class="tocxref"><span class="secno">5.3.4 </span>CSS3 Basic User Interface</a></li><li class="tocline"><a href="#css3-text" class="tocxref"><span class="secno">5.3.5 </span>CSS3 Text Module</a></li><li class="tocline"><a href="#css3-multicol" class="tocxref"><span class="secno">5.3.6 </span>CSS3 Multi-column Layout</a></li><li class="tocline"><a href="#cssom-view" class="tocxref"><span class="secno">5.3.7 </span>CSSOM View</a></li><li class="tocline"><a href="#css-viewport" class="tocxref"><span class="secno">5.3.8 </span>CSS Device Adaptation (viewport)</a></li><li class="tocline"><a href="#css-viewmode" class="tocxref"><span class="secno">5.3.9 </span>CSS 'view-mode' Media Feature</a></li><li class="tocline"><a href="#css-selectors" class="tocxref"><span class="secno">5.3.10 </span>CSS Selectors</a></li><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">5.3.11 </span>CSS3 Fonts</a></li><li class="tocline"><a href="#css3-mq" class="tocxref"><span class="secno">5.3.12 </span>CSS3 Media Queries</a></li><li class="tocline"><a href="#css3-bg" class="tocxref"><span class="secno">5.3.13 </span>CSS3 Backgrounds and Borders</a></li><li class="tocline"><a href="#css3-2d-tf" class="tocxref"><span class="secno">5.3.14 </span>CSS3 2D Transform</a></li><li class="tocline"><a href="#css3-3d-tf" class="tocxref"><span class="secno">5.3.15 </span>CSS3 3D Transform</a></li><li class="tocline"><a href="#css3-transitions" class="tocxref"><span class="secno">5.3.16 </span>CSS3 Transitions</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="#input-methods" class="tocxref"><span class="secno">5.6 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#determine-available-input-methods" class="tocxref"><span class="secno">5.6.1 </span>Determine available input methods</a></li><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">5.6.2 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">5.6.3 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">5.6.4 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">5.6.5 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">5.7 </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 video 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">
+	<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 <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 <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">
+		<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 <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">
+		<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.3 </span>Audience</h3>
+	...
+	</div>
+	
+	<div id="scope" class="section">
+	<h3><span class="secno">1.4 </span>Scope</h3>
+		The scope of this document is limited to:
+		<ul>
+			<li>provide references to a set of languages that shall be supported by <a href="#dfn-device" class="internalDFN">device</a>s and can be used by <a title="content provider">content</a> and <a>service provider</a><a>s to author content and services to be presented to the </a><a>end user</a>.</li>
+			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
+		</ul>
+		<p>
+		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
+		</p><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 href="#dfn-tv-service" class="internalDFN">TV service</a>.    
+	</p></div>
+	
+</div>
+
+<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>
+	
+	<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 <a href="#dfn-device" class="internalDFN">device</a> 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>broadband network</a>s or streamed from other devices. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a href="#dfn-tv-service" class="internalDFN">TV service</a>s</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>broadband network</a>s or streamed from other devices.</li>
+			<li><dfn id="dfn-dvb">DVB</dfn>:tbd</li>
+			<li><dfn id="dfn-atsc">ATSC</dfn>:tbd</li>
+			<li><dfn id="dfn-isdb">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></p>
+	</div>
+</div>
+
+<div id="system-overview" class="section">
+	<!--OddPage--><h2><span class="secno">3. </span>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 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 id="dfn-tv-service">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" id="dfn-scheduled-service">scheduled</dfn> or <dfn title="linear service" id="dfn-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" id="dfn-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><p>
+		In order to consume them, users need a <dfn id="dfn-device">device</dfn> that is able to present TV services. Traditionally TV services have been consumed via <a href="#dfn-tv-set" class="internalDFN">TV set</a>s or <a href="#dfn-stb" class="internalDFN">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><p>
+		<a href="#dfn-tv-service" class="internalDFN">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 id="dfn-broadcast-network">broadcast network</dfn>. Different standards have been defined for such purpose, such as <a href="#dfn-dvb" class="internalDFN">DVB</a>, <a href="#dfn-atsc" class="internalDFN">ATSC</a>, <a href="#dfn-isdb" class="internalDFN">ISDB</a>. <a href="#dfn-tv-service" class="internalDFN">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 id="dfn-home-network">home network</dfn>. The term <a href="#dfn-home-network" class="internalDFN">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><p>
+		To provide a level of interactivity, <a href="#dfn-tv-service" class="internalDFN">TV service</a>s may be associated to or delivered as <a href="#dfn-application" class="internalDFN">application</a>s.
+</p></div>
+
+<div id="application-model" class="section">
+<!--OddPage--><h2><span class="secno">4. </span>Application model</h2>
+	
+	For the purposes of this document the term <dfn id="dfn-application">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 href="#dfn-application" class="internalDFN">application</a>s, <a href="#dfn-device" class="internalDFN">device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef">section 5. Application Environment</a>.
+	
+	<div class="informative section" id="launching-applications">
+		<h3><span class="secno">4.1 </span>Launching applications</h3><p><em>This section is non-normative.</em></p>
+	</div>
+	
+	<div id="packaged-applications" class="section">
+	<h3><span class="secno">4.2 </span>Packaged applications</h3>
+	<div class="issue"> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></p></div>
+		While <a href="#dfn-application" class="internalDFN">application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a href="#dfn-browser" class="internalDFN">browser</a> when required, sometimes a single download and installation on a <a href="#dfn-device" class="internalDFN">device</a> is desirable. In order to enable this, <a href="#dfn-device" class="internalDFN">device</a>s <em class="rfc2119" title="shall">shall</em> support the packaging format defined by the [<cite><a class="bibref" rel="biblioentry" href="#bib-WIDGETS">WIDGETS</a></cite>] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a href="#dfn-browser" class="internalDFN">browser</a>.
+	</div>
+</div>
+
+
+<div id="app-environment" class="section">
+<!--OddPage--><h2><span class="secno">5. </span>Application Environment</h2>
+ This section lists which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile and that can be used to author <a href="#dfn-application" class="internalDFN">application</a>s. <a href="#dfn-browser" class="internalDFN">Browser</a>s may support more languages than the ones listed in this section.
+
+	<div id="html" class="section">
+	<h3><span class="secno">5.1 </span>HTML</h3>
+		<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><p>The [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification defines conformance requirements for user agents and documents. <a href="#dfn-application" class="internalDFN">Application</a>s and authoring tools <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for documents unless differently specified in this document. <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>].
+		</p><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 href="#dfn-browser" class="internalDFN">browser</a>s in connection with HTML5 are listed in the following sections. 
+	</p></div>
+	<div id="scripting" class="section">
+	<h3><span class="secno">5.2 </span>Scripting</h3>
+		<dfn id="dfn-scripts">Scripts</dfn> are small programs that can be embedded into <a href="#dfn-application" class="internalDFN">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 href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">scripting</a> as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. </li>
+			<li><a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] scripting language</li> 
+		</ul>
+	</div>
+
+	<div id="css" class="section">
+	<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-at-rules" class="section">
+			<h4><span class="secno">5.3.2 </span>CSS AT-rules</h4>
+			<div class="note">
+				<ul>
+				<li><a href="http://www.w3.org/TR/CSS2/syndata.html#at-rules">http://www.w3.org/TR/CSS2/syndata.html#at-rules</a></li>
+				<li><a href="http://www.w3.org/TR/css3-syntax/#at-rules">http://www.w3.org/TR/css3-syntax/#at-rules</a></li>
+				</ul>
+			</div>
+		</div>
+
+		<div id="css3-box" class="section">
+			<h4><span class="secno">5.3.3 </span>CSS3 Basic Box Model</h4>
+			<div class="note"><a href="http://www.w3.org/TR/css3-box/">http://www.w3.org/TR/css3-box/</a></div>
+		</div>
+
+		<div id="css3-ui" class="section">
+			<h4><span class="secno">5.3.4 </span>CSS3 Basic User Interface</h4>
+			<div class="note"><a href="http://www.w3.org/TR/css3-ui/">http://www.w3.org/TR/css3-ui/</a></div>
+		</div>
+		
+		<div id="css3-text" class="section">
+			<h4><span class="secno">5.3.5 </span>CSS3 Text Module</h4>
+			<div class="note"><a href="http://dev.w3.org/csswg/css3-text/">http://dev.w3.org/csswg/css3-text/</a></div>
+		</div>		
+		
+		<div id="css3-multicol" class="section">
+			<h4><span class="secno">5.3.6 </span>CSS3 Multi-column Layout</h4>
+			<div class="note"><a href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412/">http://www.w3.org/TR/2011/CR-css3-multicol-20110412/</a></div>
+		</div>
+		
+		<div id="cssom-view" class="section">
+			<h4><span class="secno">5.3.7 </span>CSSOM View</h4>
+			<div class="note"><a href="http://dev.w3.org/csswg/cssom-view/">http://dev.w3.org/csswg/cssom-view/</a></div>
+		</div>
+		
+		
+		<div id="css-viewport" class="section">
+		<h4><span class="secno">5.3.8 </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-viewmode" class="section">
+		<h4><span class="secno">5.3.9 </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 class="issue"> Industry specifications may define additional mapping between CSS view modes and "system" view modes defined by such specifications</div>
+		</div>
+		
+		<div id="css-selectors" class="section">
+		<h4><span class="secno">5.3.10 </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.11 </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.
+		</div>
+		
+			
+		<div id="css3-mq" class="section">
+			<h4><span class="secno">5.3.12 </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.13 </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.14 </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.15 </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 id="css3-transitions" class="section"> 
+			<h4><span class="secno">5.3.16 </span>CSS3 Transitions</h4>
+			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
+			<div class="note"><a href="http://www.w3.org/TR/css3-transitions/">http://www.w3.org/TR/css3-transitions/</a></div>
+		</div>
+			
+		
+	</div>
+		
+	<div id="xhr" class="section">
+	<h3><span class="secno">5.4 </span>XML HTTP Request</h3>
+		<div class="note"><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></div>	
+	</div>
+	
+	<div id="dom" class="section">
+	<h3><span class="secno">5.5 </span>Document Object Model (DOM)</h3>
+	<div note="issue">
+		Is it enough to rely on HTML5 here? I.s. on this section
+		<a href="http://dev.w3.org/html5/spec/Overview.html#dependencies">http://dev.w3.org/html5/spec/Overview.html#dependencies</a>
+	</div>
+	</div>
+		
+	<div id="input-methods" class="section">
+		<h3><span class="secno">5.6 </span>Input Methods</h3>
+		<div id="determine-available-input-methods" class="section">
+		<h4><span class="secno">5.6.1 </span>Determine available input methods</h4>
+			<div class="issue">
+				<p>I think we may want to be able to differentiate at least between these 3 set ups:
+				</p><ul>
+					<li>keyboard and mouse</li>
+					<li>touch screen</li>
+					<li>TV Remote</li>
+				</ul>
+				On the other end there are also mixed solutions. So another possible classification for input is:
+				<ul>
+					<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>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>
+					<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)
+			</p></div>
+		</div>
+		<div id="traditional-remote-controls" class="section">
+			<h4><span class="secno">5.6.2 </span>Traditional Remote Controls</h4>
+			<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>
+		</div>
+		<div id="touch-screens" class="section">
+			<h4><span class="secno">5.6.3 </span>Touch screens</h4>
+			[<cite><a class="bibref" rel="biblioentry" href="#bib-TOUCH-EVENTS">TOUCH-EVENTS</a></cite>]
+		</div>
+		<div id="mouse-and-keyboard" class="section">
+			<h4><span class="secno">5.6.4 </span>Mouse and Keyboard</h4>
+		</div>
+		<div id="other-input-devices" class="section">
+			<h4><span class="secno">5.6.5 </span>Other input devices</h4>
+		</div>
+	</div>
+	
+	<div class="informative section" id="content-developers-guidelines">
+		<h3><span class="secno">5.7 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
+	</div>
+	
+</div>
+
+<div id="formats-and-protocols" class="section">
+	<!--OddPage--><h2><span class="secno">6. </span>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&amp;tv IG. Therefore it should describe things like:
+			<ul>
+				<li>adaptive streaming
+				</li><li>parental control
+				</li><li>content protection
+				</li><li>Subtitles (webvtt,TTML etc.)
+				</li><li>discovery and control of home network services
+				</li><li>dynamic insertion of advertising into live broadcast
+				</li><li>...
+			</li></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> 
+
+		<div id="exposing-transport-metadata-to-applications" class="section"><h3><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</h3></div>
+		<div id="discovery-and-communication-with-home-network-services" class="section">
+		<h3><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</h3>
+			<div class="note">
+				No standard available at the moment. Useful references:
+				<ul>
+					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
+					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
+					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
+				</ul>			
+			</div>		
+		</div>
+			
+</div>
+
+<div id="testing" class="section">
+<!--OddPage--><h2><span class="secno">7. </span>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/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>
+	
+
+</div>
+
+<div id="performances" class="section">
+	<!--OddPage--><h2><span class="secno">8. </span>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 <em class="rfc2119" title="shall not">shall not</em> support N, B may support N, C <em class="rfc2119" title="shall">shall</em> support N?</li>
+		</ul>
+	</div>
+</div>
+
+<div class="appendix section" id="acknowledgements">
+	<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+	<p> Thanks to ... for their contributions to this document</p>
+	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
+	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
+</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><dl class="bibliography"><dt id="bib-CSS3-2D-TRANSFORMS">[CSS3-2D-TRANSFORMS]</dt><dd>Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href="http://www.w3.org/TR/css3-2d-transforms/"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-2d-transforms/">http://www.w3.org/TR/css3-2d-transforms/</a> 
+</dd><dt id="bib-CSS3-3D-TRANSFORMS">[CSS3-3D-TRANSFORMS]</dt><dd>Dean Jackson; David Hyatt; Chris Marrin. <a href="http://www.w3.org/TR/css3-3d-transforms/"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-3d-transforms/">http://www.w3.org/TR/css3-3d-transforms</a> 
+</dd><dt id="bib-CSS3-BG">[CSS3-BG]</dt><dd>Elika J. Etemad; Bert Bos; Brad Kemper. <a href="http://www.w3.org/TR/css3-background/"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-background/">http://www.w3.org/TR/css3-background/</a> 
+</dd><dt id="bib-CSS3-FONTS">[CSS3-FONTS]</dt><dd>John Daggett (Mozilla). <a href="http://www.w3.org/TR/css3-fonts"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href="http://www.w3.org/TR/css3-fonts">http://www.w3.org/TR/css3-fonts</a> 
+</dd><dt id="bib-CSS3-MEDIAQUERIES">[CSS3-MEDIAQUERIES]</dt><dd>H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href="http://www.w3.org/TR/css3-mediaqueries/"><cite>Media Queries</cite></a>  URL: <a href="http://www.w3.org/TR/css3-mediaqueries/">http://www.w3.org/TR/css3-mediaqueries/</a> 
+</dd><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> 
+</dd><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><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><dt id="bib-TOUCH-EVENTS">[TOUCH-EVENTS]</dt><dd>Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href="http://www.w3.org/TR/touch-events/"><cite>Touch Events version 1</cite></a> URL: <a href="http://www.w3.org/TR/touch-events/">http://www.w3.org/TR/touch-events</a>
+</dd><dt id="bib-WIDGETS">[WIDGETS]</dt><dd>Marcos Cáceres. <a href="http://www.w3.org/TR/widgets/"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/widgets/">http://www.w3.org/TR/widgets/</a> 
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/media-profile/style.css	Tue Mar 13 18:10:08 2012 +0100
@@ -0,0 +1,32 @@
+td.y{
+	background:#dfd;
+}
+
+td.n{
+	background:#fee;
+}
+
+table.profile{
+	 border-spacing: 0;
+   border-collapse:  collapse;
+   margin: 0.5em 0;
+   width:  100%;
+	 border-bottom:  1px solid #90b8de;
+}
+
+.profile th { background: #90b8de; }
+
+.profile td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.profile th:first-child{
+	width: 20%;
+}
+
+.profile th:nth-child(2){
+	width: 5%;
+}
+
--- a/media-profile/tv-20120207.html	Tue Mar 13 17:51:45 2012 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,888 +0,0 @@
-<!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&amp;TV profile (provisional title)</title>
-		<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
-    <!-- 
-      === NOTA BENE ===
-      For the three scripts below, if your spec resides on dev.w3 you can check them
-      out in the same tree and use relative links so that they'll work offline,
-     -->
-		
-		
-  <style type="text/css">
-/*****************************************************************
- * ReSpec CSS
- * Robin Berjon (robin at berjon dot com)
- * v0.05 - 2009-07-31
- *****************************************************************/
-
-
-/* --- INLINES --- */
-em.rfc2119 { 
-    text-transform:     lowercase;
-    font-variant:       small-caps;
-    font-style:         normal;
-    color:              #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
-    border: none;
-}
-
-dfn {
-    font-weight:    bold;
-}
-
-a.internalDFN {
-    color:  inherit;
-    border-bottom:  1px solid #99c;
-    text-decoration:    none;
-}
-
-a.externalDFN {
-    color:  inherit;
-    border-bottom:  1px dotted #ccc;
-    text-decoration:    none;
-}
-
-a.bibref {
-    text-decoration:    none;
-}
-
-code {
-    color:  #ff4500;
-}
-
-
-/* --- WEB IDL --- */
-pre.idl {
-    border-top: 1px solid #90b8de;
-    border-bottom: 1px solid #90b8de;
-    padding:    1em;
-    line-height:    120%;
-}
-
-pre.idl::before {
-    content:    "WebIDL";
-    display:    block;
-    width:      150px;
-    background: #90b8de;
-    color:  #fff;
-    font-family:    initial;
-    padding:    3px;
-    font-weight:    bold;
-    margin: -1em 0 1em -1em;
-}
-
-.idlType {
-    color:  #ff4500;
-    font-weight:    bold;
-    text-decoration:    none;
-}
-
-/*.idlModule*/
-/*.idlModuleID*/
-/*.idlInterface*/
-.idlInterfaceID, .idlDictionaryID {
-    font-weight:    bold;
-    color:  #005a9c;
-}
-
-.idlSuperclass {
-    font-style: italic;
-    color:  #005a9c;
-}
-
-/*.idlAttribute*/
-.idlAttrType, .idlFieldType, .idlMemberType {
-    color:  #005a9c;
-}
-.idlAttrName, .idlFieldName, .idlMemberName {
-    color:  #ff4500;
-}
-.idlAttrName a, .idlFieldName a, .idlMemberName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlMethod*/
-.idlMethType {
-    color:  #005a9c;
-}
-.idlMethName {
-    color:  #ff4500;
-}
-.idlMethName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlParam*/
-.idlParamType {
-    color:  #005a9c;
-}
-.idlParamName {
-    font-style: italic;
-}
-
-.extAttr {
-    color:  #666;
-}
-
-/*.idlConst*/
-.idlConstType {
-    color:  #005a9c;
-}
-.idlConstName {
-    color:  #ff4500;
-}
-.idlConstName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlException*/
-.idlExceptionID {
-    font-weight:    bold;
-    color:  #c00;
-}
-
-.idlTypedefID, .idlTypedefType {
-    color:  #005a9c;
-}
-
-.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
-    color:  #c00;
-    font-weight:    normal;
-}
-
-.excName a {
-    font-family:    monospace;
-}
-
-.idlRaises a.idlType, .excName a.idlType {
-    border-bottom:  1px dotted #c00;
-}
-
-.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
-    width:  45px;
-    text-align: center;
-}
-.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
-.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
-
-.idlImplements a {
-    font-weight:    bold;
-}
-
-dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
-    margin-left:    2em;
-}
-
-.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
-    font-weight:    normal;
-}
-
-.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
-    font-weight:    bold;
-    color:  #000;
-    font-family:    monospace;
-}
-
-.attributes dt code, .fields dt code, .dictionary-members dt code {
-    background:  #ffffd2;
-}
-
-.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
-    color:  #005a9c;
-    background:  transparent;
-    font-family:    inherit;
-    font-weight:    normal;
-    font-style: italic;
-}
-
-.methods dt code {
-    background:  #d9e6f8;
-}
-
-.constants dt code {
-    background:  #ddffd2;
-}
-
-.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
-    margin-bottom:  1em;
-}
-
-table.parameters, table.exceptions {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    margin: 0.5em 0;
-    width:  100%;
-}
-table.parameters { border-bottom:  1px solid #90b8de; }
-table.exceptions { border-bottom:  1px solid #deb890; }
-
-.parameters th, .exceptions th {
-    color:  #fff;
-    padding:    3px 5px;
-    text-align: left;
-    font-family:    initial;
-    font-weight:    normal;
-    text-shadow:    #666 1px 1px 0;
-}
-.parameters th { background: #90b8de; }
-.exceptions th { background: #deb890; }
-
-.parameters td, .exceptions td {
-    padding:    3px 10px;
-    border-top: 1px solid #ddd;
-    vertical-align: top;
-}
-
-.parameters tr:first-child td, .exceptions tr:first-child td {
-    border-top: none;
-}
-
-.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
-    width:  100px;
-}
-
-.parameters td.prmType {
-    width:  120px;
-}
-
-table.exceptions table {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    width:  100%;
-}
-
-/* --- TOC --- */
-.toc a {
-    text-decoration:    none;
-}
-
-a .secno {
-    color:  #000;
-}
-
-/* --- TABLE --- */
-table.simple {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    border-bottom:  3px solid #005a9c;
-}
-
-.simple th {
-    background: #005a9c;
-    color:  #fff;
-    padding:    3px 5px;
-    text-align: left;
-}
-
-.simple th[scope="row"] {
-    background: inherit;
-    color:  inherit;
-    border-top: 1px solid #ddd;
-}
-
-.simple td {
-    padding:    3px 10px;
-    border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
-    background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
-    margin-top: 0;
-}
-
-.section dd > p:last-child {
-    margin-bottom: 0;
-}
-
-.section dd {
-    margin-bottom:  1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
-    margin-bottom:  0;
-}
-
-/* --- EXAMPLES --- */
-pre.example {
-    border-top: 1px solid #ff4500;
-    border-bottom: 1px solid #ff4500;
-    padding:    1em;
-    margin-top: 1em;
-}
-
-pre.example::before {
-    content:    "Example";
-    display:    block;
-    width:      150px;
-    background: #ff4500;
-    color:  #fff;
-    font-family:    initial;
-    padding:    3px;
-    font-weight:    bold;
-    margin: -1em 0 1em -1em;
-}
-
-/* --- EDITORIAL NOTES --- */
-.issue {
-    padding:    1em;
-    margin: 1em 0em 0em;
-    border: 1px solid #f00;
-    background: #ffc;
-}
-
-.issue::before {
-    content:    "Issue";
-    display:    block;
-    width:  150px;
-    margin: -1.5em 0 0.5em 0;
-    font-weight:    bold;
-    border: 1px solid #f00;
-    background: #fff;
-    padding:    3px 1em;
-}
-
-.note {
-    margin: 1em 0em 0em;
-    padding:    1em;
-    border: 2px solid #cff6d9;
-    background: #e2fff0;
-}
-
-.note::before {
-    content:    "Note";
-    display:    block;
-    width:  150px;
-    margin: -1.5em 0 0.5em 0;
-    font-weight:    bold;
-    border: 1px solid #cff6d9;
-    background: #fff;
-    padding:    3px 1em;
-}
-
-/* --- Best Practices --- */
-div.practice {
-    border: solid #bebebe 1px;
-    margin: 2em 1em 1em 2em;
-}
-
-span.practicelab {
-    margin: 1.5em 0.5em 1em 1em;
-    font-weight: bold;
-    font-style: italic;
-}
-
-span.practicelab   { background: #dfffff; }
-
-span.practicelab {
-    position: relative;
-    padding: 0 0.5em;
-    top: -1.5em;
-}
-
-p.practicedesc {
-    margin: 1.5em 0.5em 1em 1em;
-}
-
[email protected] screen {
-    p.practicedesc {
-        position: relative;
-        top: -2em;
-        padding: 0;
-        margin: 1.5em 0.5em -1em 1em;
-    }
-}
-
-/* --- SYNTAX HIGHLIGHTING --- */
-pre.sh_sourceCode {
-  background-color: white;
-  color: black;
-  font-style: normal;
-  font-weight: normal;
-}
-
-pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
-pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
-pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
-pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
-pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
-pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
-pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
-pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
-pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
-pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
-pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
-pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
-pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
-
-/* Predefined variables and functions (for instance glsl) */
-pre.sh_sourceCode .sh_predef_var { color: #00008B; }
-pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
-
-/* for OOP */
-pre.sh_sourceCode .sh_classname { color: teal; }
-
-/* line numbers (not yet implemented) */
-pre.sh_sourceCode .sh_linenum { display: none; }
-
-/* Internet related */
-pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
-
-/* for ChangeLog and Log files */
-pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
-pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
-pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
-
-/* for Prolog, Perl... */
-pre.sh_sourceCode .sh_variable { color: #006400; }
-
-/* for LaTeX */
-pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
-pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
-pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
-pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
-pre.sh_sourceCode .sh_argument { color: #006400; }
-pre.sh_sourceCode .sh_optionalargument { color: purple; }
-pre.sh_sourceCode .sh_math { color: orange; }
-pre.sh_sourceCode .sh_bibtex { color: blue; }
-
-/* for diffs */
-pre.sh_sourceCode .sh_oldfile { color: orange; }
-pre.sh_sourceCode .sh_newfile { color: #006400; }
-pre.sh_sourceCode .sh_difflines { color: blue; }
-
-/* for css */
-pre.sh_sourceCode .sh_selector { color: purple; }
-pre.sh_sourceCode .sh_property { color: blue; }
-pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
-
-/* other */
-pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
-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-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-07-february-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 07 February 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><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="#packaged-applications" class="tocxref"><span class="secno">4.2 </span>Packaged 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><ul class="toc"><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">5.3.5.1 </span>Testing</a></li></ul></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-1" 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 <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">
-	<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 <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 <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">
-		<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 <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">
-		<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.3 </span>Audience</h3>
-	...
-	</div>
-	
-	<div id="scope" class="section">
-	<h3><span class="secno">1.4 </span>Scope</h3>
-		The scope of this document is limited to:
-		<ul>
-			<li>provide references to a set of languages that shall be supported by <a href="#dfn-device" class="internalDFN">device</a>s and can be used by <a title="content provider">content</a> and <a>service provider</a><a>s to author content and services to be presented to the </a><a>end user</a>.</li>
-			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
-		</ul>
-		<p>
-		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
-		</p><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 href="#dfn-tv-service" class="internalDFN">TV service</a>.    
-	</p></div>
-	
-</div>
-
-<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>
-	
-	<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 <a href="#dfn-device" class="internalDFN">device</a> 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>broadband network</a>s or streamed from other devices. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a href="#dfn-tv-service" class="internalDFN">TV service</a>s</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>broadband network</a>s or streamed from other devices.</li>
-			<li><dfn id="dfn-dvb">DVB</dfn>:tbd</li>
-			<li><dfn id="dfn-atsc">ATSC</dfn>:tbd</li>
-			<li><dfn id="dfn-isdb">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></p>
-	</div>
-</div>
-
-<div id="system-overview" class="section">
-	<!--OddPage--><h2><span class="secno">3. </span>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 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 id="dfn-tv-service">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" id="dfn-scheduled-service">scheduled</dfn> or <dfn title="linear service" id="dfn-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" id="dfn-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><p>
-		In order to consume them, users need a <dfn id="dfn-device">device</dfn> that is able to present TV services. Traditionally TV services have been consumed via <a href="#dfn-tv-set" class="internalDFN">TV set</a>s or <a href="#dfn-stb" class="internalDFN">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><p>
-		<a href="#dfn-tv-service" class="internalDFN">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 id="dfn-broadcast-network">broadcast network</dfn>. Different standards have been defined for such purpose, such as <a href="#dfn-dvb" class="internalDFN">DVB</a>, <a href="#dfn-atsc" class="internalDFN">ATSC</a>, <a href="#dfn-isdb" class="internalDFN">ISDB</a>. <a href="#dfn-tv-service" class="internalDFN">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 id="dfn-home-network">home network</dfn>. The term <a href="#dfn-home-network" class="internalDFN">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><p>
-		To provide a level of interactivity, <a href="#dfn-tv-service" class="internalDFN">TV service</a>s may be associated to or delivered as <a href="#dfn-application" class="internalDFN">application</a>s.
-</p></div>
-
-<div id="application-model" class="section">
-<!--OddPage--><h2><span class="secno">4. </span>Application model</h2>
-	
-	For the purposes of this document the term <dfn id="dfn-application">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 href="#dfn-application" class="internalDFN">application</a>s, <a href="#dfn-device" class="internalDFN">device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef">section 5. Application Environment</a>.
-	
-	<div class="informative section" id="launching-applications">
-		<h3><span class="secno">4.1 </span>Launching applications</h3><p><em>This section is non-normative.</em></p>
-	</div>
-	
-	<div id="packaged-applications" class="section">
-	<h3><span class="secno">4.2 </span>Packaged applications</h3>
-	<div class="issue"> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></p></div>
-		While <a href="#dfn-application" class="internalDFN">application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a href="#dfn-browser" class="internalDFN">browser</a> when required, sometimes a single download and installation on a <a href="#dfn-device" class="internalDFN">device</a> is desirable. In order to enable this, <a href="#dfn-device" class="internalDFN">device</a>s <em class="rfc2119" title="shall">shall</em> support the packaging format defined by the [<cite><a class="bibref" rel="biblioentry" href="#bib-WIDGETS">WIDGETS</a></cite>] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a href="#dfn-browser" class="internalDFN">browser</a>.
-	</div>
-</div>
-
-
-<div id="app-environment" class="section">
-<!--OddPage--><h2><span class="secno">5. </span>Application Environment</h2>
- This section lists which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile and that can be used to author <a href="#dfn-application" class="internalDFN">application</a>s. <a href="#dfn-browser" class="internalDFN">Browser</a>s may support more languages than the ones listed in this section.
-
-	<div id="html" class="section">
-	<h3><span class="secno">5.1 </span>HTML</h3>
-		<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><p>The [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification defines conformance requirements for user agents and documents. <a href="#dfn-application" class="internalDFN">Application</a>s and authoring tools <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for documents unless differently specified in this document. <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>].
-		</p><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 href="#dfn-browser" class="internalDFN">browser</a>s in connection with HTML5 are listed in the following sections. 
-	</p></div>
-	<div id="scripting" class="section">
-	<h3><span class="secno">5.2 </span>Scripting</h3>
-		<dfn id="dfn-scripts">Scripts</dfn> are small programs that can be embedded into <a href="#dfn-application" class="internalDFN">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 href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">scripting</a> as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. </li>
-			<li><a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] scripting language</li> 
-		</ul>
-	</div>
-
-	<div id="css" class="section">
-	<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.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. 
-			<p>
-			</p><dt>Properties</dt>
-			<dd>
-			<table class="profile">
-  		<tbody><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>
-			</tbody></table>
-			</dd>
-				
-			<dt>Descriptors</dt>
-			<dd>
-			<table class="profile">
-  		<tbody><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>
-			</tbody></table>
-			</dd>
-			<div id="testing" class="section">
-			<h5><span class="secno">5.3.5.1 </span>Testing</h5>
-			
-			</div>
-		</div>
-			
-		<div id="css3-mq" class="section">
-			<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.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.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.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">
-	<h3><span class="secno">5.4 </span>XML HTTP Request</h3>
-	</div>
-	
-	<div id="dom" class="section">
-	<h3><span class="secno">5.5 </span>Document Object Model (DOM)</h3>
-	</div>
-
-	<div id="x...--add-more-section-for-other-web-standards" class="section">
-	<h3><span class="secno">5.6 </span>... (add more section for other web standards)</h3>
-	</div>
-			
-	<div id="input-methods" class="section">
-		<h3><span class="secno">5.7 </span>Input Methods</h3>
-		<div id="determine-available-input-methods" class="section">
-		<h4><span class="secno">5.7.1 </span>Determine available input methods</h4>
-			<div class="issue">
-				<p>I think we may want to be able to differentiate at least between these 3 set ups:
-				</p><ul>
-					<li>keyboard and mouse</li>
-					<li>touch screen</li>
-					<li>TV Remote</li>
-				</ul>
-				On the other end there are also mixed solutions. So another possible classification for input is:
-				<ul>
-					<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>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>
-					<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)
-			</p></div>
-		</div>
-		<div id="traditional-remote-controls" class="section">
-			<h4><span class="secno">5.7.2 </span>Traditional Remote Controls</h4>
-			<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>
-		</div>
-		<div id="touch-screens" class="section">
-			<h4><span class="secno">5.7.3 </span>Touch screens</h4>
-			[<cite><a class="bibref" rel="biblioentry" href="#bib-TOUCH-EVENTS">TOUCH-EVENTS</a></cite>]
-		</div>
-		<div id="mouse-and-keyboard" class="section">
-			<h4><span class="secno">5.7.4 </span>Mouse and Keyboard</h4>
-		</div>
-		<div id="other-input-devices" class="section">
-			<h4><span class="secno">5.7.5 </span>Other input devices</h4>
-		</div>
-	</div>
-	
-	<div class="informative section" id="content-developers-guidelines">
-		<h3><span class="secno">5.8 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
-	</div>
-	
-</div>
-
-<div id="formats-and-protocols" class="section">
-	<!--OddPage--><h2><span class="secno">6. </span>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&amp;tv IG. Therefore it should describe things like:
-			<ul>
-				<li>adaptive streaming
-				</li><li>parental control
-				</li><li>content protection
-				</li><li>Subtitles (webvtt,TTML etc.)
-				</li><li>discovery and control of home network services
-				</li><li>dynamic insertion of advertising into live broadcast
-				</li><li>...
-			</li></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> 
-
-		<div id="exposing-transport-metadata-to-applications" class="section"><h3><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</h3></div>
-		<div id="discovery-and-communication-with-home-network-services" class="section">
-		<h3><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</h3>
-			<div class="note">
-				No standard available at the moment. Useful references:
-				<ul>
-					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
-					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
-					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
-				</ul>			
-			</div>		
-		</div>
-			
-</div>
-
-<div id="testing-1" class="section">
-<!--OddPage--><h2><span class="secno">7. </span>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/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>
-	
-
-</div>
-
-<div id="performances" class="section">
-	<!--OddPage--><h2><span class="secno">8. </span>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 <em class="rfc2119" title="shall not">shall not</em> support N, B may support N, C <em class="rfc2119" title="shall">shall</em> support N?</li>
-		</ul>
-	</div>
-</div>
-
-<div class="appendix section" id="acknowledgements">
-	<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
-	<p> Thanks to ... for their contributions to this document</p>
-	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
-	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
-</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><dl class="bibliography"><dt id="bib-CSS3-2D-TRANSFORMS">[CSS3-2D-TRANSFORMS]</dt><dd>Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href="http://www.w3.org/TR/css3-2d-transforms/"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-2d-transforms/">http://www.w3.org/TR/css3-2d-transforms/</a> 
-</dd><dt id="bib-CSS3-3D-TRANSFORMS">[CSS3-3D-TRANSFORMS]</dt><dd>Dean Jackson; David Hyatt; Chris Marrin. <a href="http://www.w3.org/TR/css3-3d-transforms/"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-3d-transforms/">http://www.w3.org/TR/css3-3d-transforms</a> 
-</dd><dt id="bib-CSS3-BG">[CSS3-BG]</dt><dd>Elika J. Etemad; Bert Bos; Brad Kemper. <a href="http://www.w3.org/TR/css3-background/"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-background/">http://www.w3.org/TR/css3-background/</a> 
-</dd><dt id="bib-CSS3-FONTS">[CSS3-FONTS]</dt><dd>John Daggett (Mozilla). <a href="http://www.w3.org/TR/css3-fonts"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href="http://www.w3.org/TR/css3-fonts">http://www.w3.org/TR/css3-fonts</a> 
-</dd><dt id="bib-CSS3-MEDIAQUERIES">[CSS3-MEDIAQUERIES]</dt><dd>H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href="http://www.w3.org/TR/css3-mediaqueries/"><cite>Media Queries</cite></a>  URL: <a href="http://www.w3.org/TR/css3-mediaqueries/">http://www.w3.org/TR/css3-mediaqueries/</a> 
-</dd><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> 
-</dd><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><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><dt id="bib-TOUCH-EVENTS">[TOUCH-EVENTS]</dt><dd>Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href="http://www.w3.org/TR/touch-events/"><cite>Touch Events version 1</cite></a> URL: <a href="http://www.w3.org/TR/touch-events/">http://www.w3.org/TR/touch-events</a>
-</dd><dt id="bib-WIDGETS">[WIDGETS]</dt><dd>Marcos Cáceres. <a href="http://www.w3.org/TR/widgets/"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/widgets/">http://www.w3.org/TR/widgets/</a> 
-</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file
--- a/media-profile/tv-src.html	Tue Mar 13 17:51:45 2012 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,465 +0,0 @@
-<!DOCTYPE html>
-<html>
-	<head>
-		<title>Web Media profile</title>
-		<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
-    <!-- 
-      === NOTA BENE ===
-      For the three scripts below, if your spec resides on dev.w3 you can check them
-      out in the same tree and use relative links so that they'll work offline,
-     -->
-		<script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
-		<!--<script src='2009/dap/ReSpec.js/js/respec.js' class='remove'></script> -->
-		<script class='remove'>		
-
-		var respecConfig = {
-					preProcess : [],
-               
-          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "ED",
-          
-          // the specification's short name, as in http://www.w3.org/TR/short-name/
-          shortName:            "webtv-profile",
-
-          // if your specification has a subtitle that goes below the main
-          // formal title, define it here
-          subtitle   :  "Guidelines for integration of interactive media services in a browser-based environment",
-
-          // if you wish the publication date to be other than today, set this
-          // publishDate:  "2009-08-06",
-
-          // if the specification's copyright date is a range of years, specify
-          // the start date here:
-          // copyrightStart: "2005"
-
-          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
-          // and its maturity status
-          // previousPublishDate:  "1977-03-15",
-          // previousMaturity:  "WD",
-
-          // if there a publicly available Editor's Draft, this is the link
-          edDraftURI:           "",
-
-          // if this is a LCWD, uncomment and set the end of its review period
-          // lcEnd: "2009-08-05",
-
-          // if you want to have extra CSS, append them to this list
-          // it is recommended that the respec.css stylesheet be kept
-          extraCSS:	["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css",
-          						//"2009/dap/ReSpec.js/css/respec.css",
-          						"tv.css"],
-
-          // editors, add as many as you like
-          // only "name" is required
-          editors:  [
-              { name: "Giuseppe Pascale", url: "",
-                company: "Opera", companyURL: "http://www.opera.com/" },
-          ],
-          // authors, add as many as you like. 
-          // This is optional, uncomment if you have authors as well as editors.
-          // only "name" is required. Same format as editors.
-
-          //authors:  [
-          //    { name: "Your Name", url: "http://example.org/",
-          //      company: "Your Company", companyURL: "http://example.com/" },
-          //],
-          
-          // name of the WG
-          wg:           "Web and TV IG",
-          
-          // URI of the public WG page
-          wgURI:        "http://www.w3.org/2011/webtv/",
-          
-          // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "public-web-and-tv",
-          
-          // URI of the patent status for this WG, for Rec-track documents
-          // !!!! IMPORTANT !!!!
-          // This is important for Rec-track documents, do not copy a patent URI from a random
-          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
-          // Team Contact.
-          wgPatentURI:  "",
-      };
-      
-		</script>
-  </head>
-	<body>
-<section id='abstract'>
-			
-</section>
-
-<section id="intro" class="informative">
-<h2>Introduction</h2>
-
-	<section>
-	<h2>Background</h2>
-	<p>There is an increasing number of content and service providers worldwide that are deploying interactive video 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>
-	
-	<section>
-	<h2>Design Goals</h2>
-		This sections list the goals that have driven the work on this document.
-
-		<section>
-		<h2>Avoid obsolesce</h2>
-		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.
-	</section>
-	
-		<section>
-		<h2>Improve interoperability</h2>
-			Use of web technologies in different markets and regions to create interactive TV services is increasing. TV services are not relegated anymore to <a>TV set</a>s and <a>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.
-	</section>
-	
-		<section>
-		<h2>Coordinate deployments</h2>
-		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 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 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 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>
-
-	<section>
-	<h2>Audience</h2>
-	...
-	</section>
-	
-	<section>
-	<h2>Scope</h2>
-		The scope of this document is limited to:
-		<ul>
-			<li>provide references to a set of languages that shall be supported by <a>device</a>s and can be used by <a title="content provider">content</a> and <a>service provider<a>s to author content and services to be presented to the <a>end user</a>.</li>
-			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
-		</ul>
-		<p>
-		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
-		<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>
-
-<section id="terminology">
-<h2>Terminology</h2>
-
-	<section id="conformance">
-	
-	</section>
-	
-	<section>				
-	<h3>Definitions</h3>
-	<p>
-		For the purposes of the present document, the following definitions apply:
-		<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. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a>TV service</a>s</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>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>
-	<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 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 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 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.
-</section>
-
-<section>
-<h2>Application model</h2>
-	
-	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 class="informative">
-		<h2>Launching applications</h2>
-	</section>
-	
-	<section>
-	<h2>Packaged applications</h2>
-	<div class=issue> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></div>
-		While <a>application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a>browser</a> when required, sometimes a single download and installation on a <a>device</a> is desirable. In order to enable this, <a>device</a>s MUST support the packaging format defined by the [[!WIDGETS]] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a>browser</a>.
-	</section>
-</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 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 MUST comply with conformance requirements for documents unless differently specified in this document. <a>Browser</a>s MUST comply with conformance requirements for user agents unless differently specified in this document; in particular browsers MUST 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 MUST support <a class="externalDFN">scripting</a> as defined in [[!HTML5]]. </li>
-			<li><a>Browser</a>s MUST support [[!ECMA-262]] scripting language</li> 
-		</ul>
-	</section>
-
-	<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. 
-	
-		<section id="css-properties">
-		<h2>CSS Properties</h2>
-		<a>Browser</a>s MUST support [[!CSS21]].
-		</section>
-		
-		<section id="css-at-rules">
-			<h2>CSS AT-rules</h2>
-			<div class="note">
-				<ul>
-				<li><a href="http://www.w3.org/TR/CSS2/syndata.html#at-rules">http://www.w3.org/TR/CSS2/syndata.html#at-rules</a></li>
-				<li><a href="http://www.w3.org/TR/css3-syntax/#at-rules">http://www.w3.org/TR/css3-syntax/#at-rules</a></li>
-				</ul>
-			</div>
-		</section>
-
-		<section id="css3-box">
-			<h2>CSS3 Basic Box Model</h2>
-			<div class="note"><a href="http://www.w3.org/TR/css3-box/">http://www.w3.org/TR/css3-box/</a></div>
-		</section>
-
-		<section id="css3-ui">
-			<h2>CSS3 Basic User Interface</h2>
-			<div class="note"><a href="http://www.w3.org/TR/css3-ui/">http://www.w3.org/TR/css3-ui/</a></div>
-		</section>
-		
-		<section id="css3-text">
-			<h2>CSS3 Text Module</h2>
-			<div class="note"><a href="http://dev.w3.org/csswg/css3-text/">http://dev.w3.org/csswg/css3-text/</a></div>
-		</section>		
-		
-		<section id="css3-multicol">
-			<h2>CSS3 Multi-column Layout</h2>
-			<div class="note"><a href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412/">http://www.w3.org/TR/2011/CR-css3-multicol-20110412/</a></div>
-		</section>
-		
-		<section id="cssom-view">
-			<h2>CSSOM View</h2>
-			<div class="note"><a href="http://dev.w3.org/csswg/cssom-view/">http://dev.w3.org/csswg/cssom-view/</a></div>
-		</section>
-		
-		
-		<section id="css-viewport">
-		<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 id="css-viewmode">
-		<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>
-		<div class=issue> Industry specifications may define additional mapping between CSS view modes and "system" view modes defined by such specifications</div>
-		</section>
-		
-		<section id="css-selectors">
-		<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.
-		</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> MUST 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 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>
-				
-		<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 id="css3-transitions"> 
-			<h2>CSS3 Transitions</h2>
-			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
-			<div class="note"><a href="http://www.w3.org/TR/css3-transitions/">http://www.w3.org/TR/css3-transitions/</a></div>
-		</section>
-			
-		
-	</section>
-		
-	<section id="xhr">
-	<h2>XML HTTP Request</h2>
-		<div class=note><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></div>	
-	</section>
-	
-	<section id="dom">
-	<h2>Document Object Model (DOM)</h2>
-	<div note="issue">
-		Should be enough to rely on HTML5 here, i.e. on this section
-		<a href="http://dev.w3.org/html5/spec/Overview.html#dependencies">http://dev.w3.org/html5/spec/Overview.html#dependencies</a>
-	</div>
-	</section>
-		
-	<section>
-		<h2>Input Methods</h2>
-		<section>
-		<h2>Determine available input methods</h2>
-			<div class="issue">
-				<p>I think we may want to be able to differentiate at least between these 3 set ups:
-				<ul>
-					<li>keyboard and mouse</li>
-					<li>touch screen</li>
-					<li>TV Remote</li>
-				</ul>
-				On the other end there are also mixed solutions. So another possible classification for input is:
-				<ul>
-					<li>Pointer based:
-					<ul>
-						<li>accurate pointing (mouse, trackball, stylus touch)</li>
-						<li>rough pointing (finger touch, wii)</li>
-						<li>no pointing
-					</ul>
-					</li>
-					<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>
-					<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>
-		</section>
-		<section>
-			<h2>Other input devices</h2>
-		</section>
-	</section>
-	
-	<section class="informative">
-		<h2>Content Developers Guidelines</h2>
-	</section>
-	
-</section>
-
-<section>
-	<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
-				<li>parental control
-				<li>content protection
-				<li>Subtitles (webvtt,TTML etc.)
-				<li>discovery and control of home network services
-				<li>dynamic insertion of advertising into live broadcast
-				<li>...
-			</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 Transport Metadata to Applications</h2></section>
-		<section>
-		<h2>Discovery and Communication with Home Network Services</h2>
-			<div class="note">
-				No standard available at the moment. Useful references:
-				<ul>
-					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
-					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
-					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
-				</ul>			
-			</div>		
-		</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/framework/">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 MUST NOT support N, B may support N, C MUST support N?</li>
-		</ul>
-	</div>
-</section>
-
-<section class='appendix'>
-	<h2>Acknowledgements</h2>
-	<p> Thanks to ... for their contributions to this document</p>
-	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
-	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
-</section>
-
-	</body>
-</html>
\ No newline at end of file
--- a/media-profile/tv.css	Tue Mar 13 17:51:45 2012 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,32 +0,0 @@
-td.y{
-	background:#dfd;
-}
-
-td.n{
-	background:#fee;
-}
-
-table.profile{
-	 border-spacing: 0;
-   border-collapse:  collapse;
-   margin: 0.5em 0;
-   width:  100%;
-	 border-bottom:  1px solid #90b8de;
-}
-
-.profile th { background: #90b8de; }
-
-.profile td {
-    padding:    3px 10px;
-    border-top: 1px solid #ddd;
-    vertical-align: top;
-}
-
-.profile th:first-child{
-	width: 20%;
-}
-
-.profile th:nth-child(2){
-	width: 5%;
-}
-
--- a/media-profile/tv.html	Tue Mar 13 17:51:45 2012 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,873 +0,0 @@
-<!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 Media profile</title>
-		<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
-    <!-- 
-      === NOTA BENE ===
-      For the three scripts below, if your spec resides on dev.w3 you can check them
-      out in the same tree and use relative links so that they'll work offline,
-     -->
-		
-		<!--<script src='2009/dap/ReSpec.js/js/respec.js' class='remove'></script> -->
-		
-  <style type="text/css">
-/*****************************************************************
- * ReSpec CSS
- * Robin Berjon (robin at berjon dot com)
- * v0.05 - 2009-07-31
- *****************************************************************/
-
-
-/* --- INLINES --- */
-em.rfc2119 { 
-    text-transform:     lowercase;
-    font-variant:       small-caps;
-    font-style:         normal;
-    color:              #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
-    border: none;
-}
-
-dfn {
-    font-weight:    bold;
-}
-
-a.internalDFN {
-    color:  inherit;
-    border-bottom:  1px solid #99c;
-    text-decoration:    none;
-}
-
-a.externalDFN {
-    color:  inherit;
-    border-bottom:  1px dotted #ccc;
-    text-decoration:    none;
-}
-
-a.bibref {
-    text-decoration:    none;
-}
-
-code {
-    color:  #ff4500;
-}
-
-
-/* --- WEB IDL --- */
-pre.idl {
-    border-top: 1px solid #90b8de;
-    border-bottom: 1px solid #90b8de;
-    padding:    1em;
-    line-height:    120%;
-}
-
-pre.idl::before {
-    content:    "WebIDL";
-    display:    block;
-    width:      150px;
-    background: #90b8de;
-    color:  #fff;
-    font-family:    initial;
-    padding:    3px;
-    font-weight:    bold;
-    margin: -1em 0 1em -1em;
-}
-
-.idlType {
-    color:  #ff4500;
-    font-weight:    bold;
-    text-decoration:    none;
-}
-
-/*.idlModule*/
-/*.idlModuleID*/
-/*.idlInterface*/
-.idlInterfaceID, .idlDictionaryID {
-    font-weight:    bold;
-    color:  #005a9c;
-}
-
-.idlSuperclass {
-    font-style: italic;
-    color:  #005a9c;
-}
-
-/*.idlAttribute*/
-.idlAttrType, .idlFieldType, .idlMemberType {
-    color:  #005a9c;
-}
-.idlAttrName, .idlFieldName, .idlMemberName {
-    color:  #ff4500;
-}
-.idlAttrName a, .idlFieldName a, .idlMemberName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlMethod*/
-.idlMethType {
-    color:  #005a9c;
-}
-.idlMethName {
-    color:  #ff4500;
-}
-.idlMethName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlParam*/
-.idlParamType {
-    color:  #005a9c;
-}
-.idlParamName {
-    font-style: italic;
-}
-
-.extAttr {
-    color:  #666;
-}
-
-/*.idlConst*/
-.idlConstType {
-    color:  #005a9c;
-}
-.idlConstName {
-    color:  #ff4500;
-}
-.idlConstName a {
-    color:  #ff4500;
-    border-bottom:  1px dotted #ff4500;
-    text-decoration: none;
-}
-
-/*.idlException*/
-.idlExceptionID {
-    font-weight:    bold;
-    color:  #c00;
-}
-
-.idlTypedefID, .idlTypedefType {
-    color:  #005a9c;
-}
-
-.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
-    color:  #c00;
-    font-weight:    normal;
-}
-
-.excName a {
-    font-family:    monospace;
-}
-
-.idlRaises a.idlType, .excName a.idlType {
-    border-bottom:  1px dotted #c00;
-}
-
-.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
-    width:  45px;
-    text-align: center;
-}
-.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
-.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
-
-.idlImplements a {
-    font-weight:    bold;
-}
-
-dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
-    margin-left:    2em;
-}
-
-.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
-    font-weight:    normal;
-}
-
-.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
-    font-weight:    bold;
-    color:  #000;
-    font-family:    monospace;
-}
-
-.attributes dt code, .fields dt code, .dictionary-members dt code {
-    background:  #ffffd2;
-}
-
-.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
-    color:  #005a9c;
-    background:  transparent;
-    font-family:    inherit;
-    font-weight:    normal;
-    font-style: italic;
-}
-
-.methods dt code {
-    background:  #d9e6f8;
-}
-
-.constants dt code {
-    background:  #ddffd2;
-}
-
-.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
-    margin-bottom:  1em;
-}
-
-table.parameters, table.exceptions {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    margin: 0.5em 0;
-    width:  100%;
-}
-table.parameters { border-bottom:  1px solid #90b8de; }
-table.exceptions { border-bottom:  1px solid #deb890; }
-
-.parameters th, .exceptions th {
-    color:  #fff;
-    padding:    3px 5px;
-    text-align: left;
-    font-family:    initial;
-    font-weight:    normal;
-    text-shadow:    #666 1px 1px 0;
-}
-.parameters th { background: #90b8de; }
-.exceptions th { background: #deb890; }
-
-.parameters td, .exceptions td {
-    padding:    3px 10px;
-    border-top: 1px solid #ddd;
-    vertical-align: top;
-}
-
-.parameters tr:first-child td, .exceptions tr:first-child td {
-    border-top: none;
-}
-
-.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
-    width:  100px;
-}
-
-.parameters td.prmType {
-    width:  120px;
-}
-
-table.exceptions table {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    width:  100%;
-}
-
-/* --- TOC --- */
-.toc a {
-    text-decoration:    none;
-}
-
-a .secno {
-    color:  #000;
-}
-
-/* --- TABLE --- */
-table.simple {
-    border-spacing: 0;
-    border-collapse:    collapse;
-    border-bottom:  3px solid #005a9c;
-}
-
-.simple th {
-    background: #005a9c;
-    color:  #fff;
-    padding:    3px 5px;
-    text-align: left;
-}
-
-.simple th[scope="row"] {
-    background: inherit;
-    color:  inherit;
-    border-top: 1px solid #ddd;
-}
-
-.simple td {
-    padding:    3px 10px;
-    border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
-    background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
-    margin-top: 0;
-}
-
-.section dd > p:last-child {
-    margin-bottom: 0;
-}
-
-.section dd {
-    margin-bottom:  1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
-    margin-bottom:  0;
-}
-
-/* --- EXAMPLES --- */
-pre.example {
-    border-top: 1px solid #ff4500;
-    border-bottom: 1px solid #ff4500;
-    padding:    1em;
-    margin-top: 1em;
-}
-
-pre.example::before {
-    content:    "Example";
-    display:    block;
-    width:      150px;
-    background: #ff4500;
-    color:  #fff;
-    font-family:    initial;
-    padding:    3px;
-    font-weight:    bold;
-    margin: -1em 0 1em -1em;
-}
-
-/* --- EDITORIAL NOTES --- */
-.issue {
-    padding:    1em;
-    margin: 1em 0em 0em;
-    border: 1px solid #f00;
-    background: #ffc;
-}
-
-.issue::before {
-    content:    "Issue";
-    display:    block;
-    width:  150px;
-    margin: -1.5em 0 0.5em 0;
-    font-weight:    bold;
-    border: 1px solid #f00;
-    background: #fff;
-    padding:    3px 1em;
-}
-
-.note {
-    margin: 1em 0em 0em;
-    padding:    1em;
-    border: 2px solid #cff6d9;
-    background: #e2fff0;
-}
-
-.note::before {
-    content:    "Note";
-    display:    block;
-    width:  150px;
-    margin: -1.5em 0 0.5em 0;
-    font-weight:    bold;
-    border: 1px solid #cff6d9;
-    background: #fff;
-    padding:    3px 1em;
-}
-
-/* --- Best Practices --- */
-div.practice {
-    border: solid #bebebe 1px;
-    margin: 2em 1em 1em 2em;
-}
-
-span.practicelab {
-    margin: 1.5em 0.5em 1em 1em;
-    font-weight: bold;
-    font-style: italic;
-}
-
-span.practicelab   { background: #dfffff; }
-
-span.practicelab {
-    position: relative;
-    padding: 0 0.5em;
-    top: -1.5em;
-}
-
-p.practicedesc {
-    margin: 1.5em 0.5em 1em 1em;
-}
-
[email protected] screen {
-    p.practicedesc {
-        position: relative;
-        top: -2em;
-        padding: 0;
-        margin: 1.5em 0.5em -1em 1em;
-    }
-}
-
-/* --- SYNTAX HIGHLIGHTING --- */
-pre.sh_sourceCode {
-  background-color: white;
-  color: black;
-  font-style: normal;
-  font-weight: normal;
-}
-
-pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; }           /* language keywords */
-pre.sh_sourceCode .sh_type { color: #666; }                            /* basic types */
-pre.sh_sourceCode .sh_usertype { color: teal; }                             /* user defined types */
-pre.sh_sourceCode .sh_string { color: red; font-family: monospace; }        /* strings and chars */
-pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; }     /* regular expressions */
-pre.sh_sourceCode .sh_specialchar { color: 	#ffc0cb; font-family: monospace; }  /* e.g., \n, \t, \\ */
-pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; }         /* comments */
-pre.sh_sourceCode .sh_number { color: purple; }                             /* literal numbers */
-pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; }       /* e.g., #include, import */
-pre.sh_sourceCode .sh_symbol { color: blue; }                            /* e.g., *, + */
-pre.sh_sourceCode .sh_function { color: black; font-weight: bold; }         /* function calls and declarations */
-pre.sh_sourceCode .sh_cbracket { color: red; }                              /* block brackets (e.g., {, }) */
-pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; }   /* TODO and FIXME */
-
-/* Predefined variables and functions (for instance glsl) */
-pre.sh_sourceCode .sh_predef_var { color: #00008B; }
-pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
-
-/* for OOP */
-pre.sh_sourceCode .sh_classname { color: teal; }
-
-/* line numbers (not yet implemented) */
-pre.sh_sourceCode .sh_linenum { display: none; }
-
-/* Internet related */
-pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
-
-/* for ChangeLog and Log files */
-pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
-pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
-pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
-
-/* for Prolog, Perl... */
-pre.sh_sourceCode .sh_variable { color: #006400; }
-
-/* for LaTeX */
-pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
-pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
-pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
-pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
-pre.sh_sourceCode .sh_argument { color: #006400; }
-pre.sh_sourceCode .sh_optionalargument { color: purple; }
-pre.sh_sourceCode .sh_math { color: orange; }
-pre.sh_sourceCode .sh_bibtex { color: blue; }
-
-/* for diffs */
-pre.sh_sourceCode .sh_oldfile { color: orange; }
-pre.sh_sourceCode .sh_newfile { color: #006400; }
-pre.sh_sourceCode .sh_difflines { color: blue; }
-
-/* for css */
-pre.sh_sourceCode .sh_selector { color: purple; }
-pre.sh_sourceCode .sh_property { color: blue; }
-pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
-
-/* other */
-pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
-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-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 Media profile</h1><h2 id="subtitle">Guidelines for integration of interactive video services in a browser-based environment</h2><h2 id="w3c-editor-s-draft-28-february-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 28 February 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/webtv-profile/">http://www.w3.org/TR/webtv-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><p>
-			
-</p></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="#packaged-applications" class="tocxref"><span class="secno">4.2 </span>Packaged 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-at-rules" class="tocxref"><span class="secno">5.3.2 </span>CSS AT-rules</a></li><li class="tocline"><a href="#css3-box" class="tocxref"><span class="secno">5.3.3 </span>CSS3 Basic Box Model</a></li><li class="tocline"><a href="#css3-ui" class="tocxref"><span class="secno">5.3.4 </span>CSS3 Basic User Interface</a></li><li class="tocline"><a href="#css3-text" class="tocxref"><span class="secno">5.3.5 </span>CSS3 Text Module</a></li><li class="tocline"><a href="#css3-multicol" class="tocxref"><span class="secno">5.3.6 </span>CSS3 Multi-column Layout</a></li><li class="tocline"><a href="#cssom-view" class="tocxref"><span class="secno">5.3.7 </span>CSSOM View</a></li><li class="tocline"><a href="#css-viewport" class="tocxref"><span class="secno">5.3.8 </span>CSS Device Adaptation (viewport)</a></li><li class="tocline"><a href="#css-viewmode" class="tocxref"><span class="secno">5.3.9 </span>CSS 'view-mode' Media Feature</a></li><li class="tocline"><a href="#css-selectors" class="tocxref"><span class="secno">5.3.10 </span>CSS Selectors</a></li><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">5.3.11 </span>CSS3 Fonts</a></li><li class="tocline"><a href="#css3-mq" class="tocxref"><span class="secno">5.3.12 </span>CSS3 Media Queries</a></li><li class="tocline"><a href="#css3-bg" class="tocxref"><span class="secno">5.3.13 </span>CSS3 Backgrounds and Borders</a></li><li class="tocline"><a href="#css3-2d-tf" class="tocxref"><span class="secno">5.3.14 </span>CSS3 2D Transform</a></li><li class="tocline"><a href="#css3-3d-tf" class="tocxref"><span class="secno">5.3.15 </span>CSS3 3D Transform</a></li><li class="tocline"><a href="#css3-transitions" class="tocxref"><span class="secno">5.3.16 </span>CSS3 Transitions</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="#input-methods" class="tocxref"><span class="secno">5.6 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#determine-available-input-methods" class="tocxref"><span class="secno">5.6.1 </span>Determine available input methods</a></li><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">5.6.2 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">5.6.3 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">5.6.4 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">5.6.5 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">5.7 </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 video 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">
-	<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 <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 <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">
-		<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 <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">
-		<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.3 </span>Audience</h3>
-	...
-	</div>
-	
-	<div id="scope" class="section">
-	<h3><span class="secno">1.4 </span>Scope</h3>
-		The scope of this document is limited to:
-		<ul>
-			<li>provide references to a set of languages that shall be supported by <a href="#dfn-device" class="internalDFN">device</a>s and can be used by <a title="content provider">content</a> and <a>service provider</a><a>s to author content and services to be presented to the </a><a>end user</a>.</li>
-			<li>provide references to a set of metrics that can be used to evaluate performances of <a>devices</a></li>
-		</ul>
-		<p>
-		The scope of this document is not to describe an entire operating system. In particular, hardware and software configuration that <a>user</a> would be expected to have on their devices are out of scope.
-		</p><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 href="#dfn-tv-service" class="internalDFN">TV service</a>.    
-	</p></div>
-	
-</div>
-
-<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>
-	
-	<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 <a href="#dfn-device" class="internalDFN">device</a> 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>broadband network</a>s or streamed from other devices. For the purpose of this document this definition also includes storage devices (such as VCR, DVD, Blue Rays discs) that are able to run <a href="#dfn-tv-service" class="internalDFN">TV service</a>s</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>broadband network</a>s or streamed from other devices.</li>
-			<li><dfn id="dfn-dvb">DVB</dfn>:tbd</li>
-			<li><dfn id="dfn-atsc">ATSC</dfn>:tbd</li>
-			<li><dfn id="dfn-isdb">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></p>
-	</div>
-</div>
-
-<div id="system-overview" class="section">
-	<!--OddPage--><h2><span class="secno">3. </span>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 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 id="dfn-tv-service">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" id="dfn-scheduled-service">scheduled</dfn> or <dfn title="linear service" id="dfn-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" id="dfn-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><p>
-		In order to consume them, users need a <dfn id="dfn-device">device</dfn> that is able to present TV services. Traditionally TV services have been consumed via <a href="#dfn-tv-set" class="internalDFN">TV set</a>s or <a href="#dfn-stb" class="internalDFN">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><p>
-		<a href="#dfn-tv-service" class="internalDFN">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 id="dfn-broadcast-network">broadcast network</dfn>. Different standards have been defined for such purpose, such as <a href="#dfn-dvb" class="internalDFN">DVB</a>, <a href="#dfn-atsc" class="internalDFN">ATSC</a>, <a href="#dfn-isdb" class="internalDFN">ISDB</a>. <a href="#dfn-tv-service" class="internalDFN">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 id="dfn-home-network">home network</dfn>. The term <a href="#dfn-home-network" class="internalDFN">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><p>
-		To provide a level of interactivity, <a href="#dfn-tv-service" class="internalDFN">TV service</a>s may be associated to or delivered as <a href="#dfn-application" class="internalDFN">application</a>s.
-</p></div>
-
-<div id="application-model" class="section">
-<!--OddPage--><h2><span class="secno">4. </span>Application model</h2>
-	
-	For the purposes of this document the term <dfn id="dfn-application">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 href="#dfn-application" class="internalDFN">application</a>s, <a href="#dfn-device" class="internalDFN">device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef">section 5. Application Environment</a>.
-	
-	<div class="informative section" id="launching-applications">
-		<h3><span class="secno">4.1 </span>Launching applications</h3><p><em>This section is non-normative.</em></p>
-	</div>
-	
-	<div id="packaged-applications" class="section">
-	<h3><span class="secno">4.2 </span>Packaged applications</h3>
-	<div class="issue"> Should this be mandatory? <p><a href="http://www.w3.org/mid/[email protected]">http://www.w3.org/mid/[email protected]</a></p></div>
-		While <a href="#dfn-application" class="internalDFN">application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a href="#dfn-browser" class="internalDFN">browser</a> when required, sometimes a single download and installation on a <a href="#dfn-device" class="internalDFN">device</a> is desirable. In order to enable this, <a href="#dfn-device" class="internalDFN">device</a>s <em class="rfc2119" title="shall">shall</em> support the packaging format defined by the [<cite><a class="bibref" rel="biblioentry" href="#bib-WIDGETS">WIDGETS</a></cite>] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a href="#dfn-browser" class="internalDFN">browser</a>.
-	</div>
-</div>
-
-
-<div id="app-environment" class="section">
-<!--OddPage--><h2><span class="secno">5. </span>Application Environment</h2>
- This section lists which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile and that can be used to author <a href="#dfn-application" class="internalDFN">application</a>s. <a href="#dfn-browser" class="internalDFN">Browser</a>s may support more languages than the ones listed in this section.
-
-	<div id="html" class="section">
-	<h3><span class="secno">5.1 </span>HTML</h3>
-		<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><p>The [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>] specification defines conformance requirements for user agents and documents. <a href="#dfn-application" class="internalDFN">Application</a>s and authoring tools <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for documents unless differently specified in this document. <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">the HTML syntax</a> and <a class="externalDFN">the XHTML syntax</a> for HTML documents as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>].
-		</p><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 href="#dfn-browser" class="internalDFN">browser</a>s in connection with HTML5 are listed in the following sections. 
-	</p></div>
-	<div id="scripting" class="section">
-	<h3><span class="secno">5.2 </span>Scripting</h3>
-		<dfn id="dfn-scripts">Scripts</dfn> are small programs that can be embedded into <a href="#dfn-application" class="internalDFN">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 href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support <a class="externalDFN">scripting</a> as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. </li>
-			<li><a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="shall">shall</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] scripting language</li> 
-		</ul>
-	</div>
-
-	<div id="css" class="section">
-	<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-at-rules" class="section">
-			<h4><span class="secno">5.3.2 </span>CSS AT-rules</h4>
-			<div class="note">
-				<ul>
-				<li><a href="http://www.w3.org/TR/CSS2/syndata.html#at-rules">http://www.w3.org/TR/CSS2/syndata.html#at-rules</a></li>
-				<li><a href="http://www.w3.org/TR/css3-syntax/#at-rules">http://www.w3.org/TR/css3-syntax/#at-rules</a></li>
-				</ul>
-			</div>
-		</div>
-
-		<div id="css3-box" class="section">
-			<h4><span class="secno">5.3.3 </span>CSS3 Basic Box Model</h4>
-			<div class="note"><a href="http://www.w3.org/TR/css3-box/">http://www.w3.org/TR/css3-box/</a></div>
-		</div>
-
-		<div id="css3-ui" class="section">
-			<h4><span class="secno">5.3.4 </span>CSS3 Basic User Interface</h4>
-			<div class="note"><a href="http://www.w3.org/TR/css3-ui/">http://www.w3.org/TR/css3-ui/</a></div>
-		</div>
-		
-		<div id="css3-text" class="section">
-			<h4><span class="secno">5.3.5 </span>CSS3 Text Module</h4>
-			<div class="note"><a href="http://dev.w3.org/csswg/css3-text/">http://dev.w3.org/csswg/css3-text/</a></div>
-		</div>		
-		
-		<div id="css3-multicol" class="section">
-			<h4><span class="secno">5.3.6 </span>CSS3 Multi-column Layout</h4>
-			<div class="note"><a href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412/">http://www.w3.org/TR/2011/CR-css3-multicol-20110412/</a></div>
-		</div>
-		
-		<div id="cssom-view" class="section">
-			<h4><span class="secno">5.3.7 </span>CSSOM View</h4>
-			<div class="note"><a href="http://dev.w3.org/csswg/cssom-view/">http://dev.w3.org/csswg/cssom-view/</a></div>
-		</div>
-		
-		
-		<div id="css-viewport" class="section">
-		<h4><span class="secno">5.3.8 </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-viewmode" class="section">
-		<h4><span class="secno">5.3.9 </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 class="issue"> Industry specifications may define additional mapping between CSS view modes and "system" view modes defined by such specifications</div>
-		</div>
-		
-		<div id="css-selectors" class="section">
-		<h4><span class="secno">5.3.10 </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.11 </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.
-		</div>
-		
-			
-		<div id="css3-mq" class="section">
-			<h4><span class="secno">5.3.12 </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.13 </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.14 </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.15 </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 id="css3-transitions" class="section"> 
-			<h4><span class="secno">5.3.16 </span>CSS3 Transitions</h4>
-			<div class="issue">This may need multiple subprofiles based on terminal capability</div>
-			<div class="note"><a href="http://www.w3.org/TR/css3-transitions/">http://www.w3.org/TR/css3-transitions/</a></div>
-		</div>
-			
-		
-	</div>
-		
-	<div id="xhr" class="section">
-	<h3><span class="secno">5.4 </span>XML HTTP Request</h3>
-		<div class="note"><a href="http://www.w3.org/TR/XMLHttpRequest/">http://www.w3.org/TR/XMLHttpRequest/</a></div>	
-	</div>
-	
-	<div id="dom" class="section">
-	<h3><span class="secno">5.5 </span>Document Object Model (DOM)</h3>
-	<div note="issue">
-		Is it enough to rely on HTML5 here? I.s. on this section
-		<a href="http://dev.w3.org/html5/spec/Overview.html#dependencies">http://dev.w3.org/html5/spec/Overview.html#dependencies</a>
-	</div>
-	</div>
-		
-	<div id="input-methods" class="section">
-		<h3><span class="secno">5.6 </span>Input Methods</h3>
-		<div id="determine-available-input-methods" class="section">
-		<h4><span class="secno">5.6.1 </span>Determine available input methods</h4>
-			<div class="issue">
-				<p>I think we may want to be able to differentiate at least between these 3 set ups:
-				</p><ul>
-					<li>keyboard and mouse</li>
-					<li>touch screen</li>
-					<li>TV Remote</li>
-				</ul>
-				On the other end there are also mixed solutions. So another possible classification for input is:
-				<ul>
-					<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>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>
-					<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)
-			</p></div>
-		</div>
-		<div id="traditional-remote-controls" class="section">
-			<h4><span class="secno">5.6.2 </span>Traditional Remote Controls</h4>
-			<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>
-		</div>
-		<div id="touch-screens" class="section">
-			<h4><span class="secno">5.6.3 </span>Touch screens</h4>
-			[<cite><a class="bibref" rel="biblioentry" href="#bib-TOUCH-EVENTS">TOUCH-EVENTS</a></cite>]
-		</div>
-		<div id="mouse-and-keyboard" class="section">
-			<h4><span class="secno">5.6.4 </span>Mouse and Keyboard</h4>
-		</div>
-		<div id="other-input-devices" class="section">
-			<h4><span class="secno">5.6.5 </span>Other input devices</h4>
-		</div>
-	</div>
-	
-	<div class="informative section" id="content-developers-guidelines">
-		<h3><span class="secno">5.7 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
-	</div>
-	
-</div>
-
-<div id="formats-and-protocols" class="section">
-	<!--OddPage--><h2><span class="secno">6. </span>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&amp;tv IG. Therefore it should describe things like:
-			<ul>
-				<li>adaptive streaming
-				</li><li>parental control
-				</li><li>content protection
-				</li><li>Subtitles (webvtt,TTML etc.)
-				</li><li>discovery and control of home network services
-				</li><li>dynamic insertion of advertising into live broadcast
-				</li><li>...
-			</li></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> 
-
-		<div id="exposing-transport-metadata-to-applications" class="section"><h3><span class="secno">6.1 </span>Exposing Transport Metadata to Applications</h3></div>
-		<div id="discovery-and-communication-with-home-network-services" class="section">
-		<h3><span class="secno">6.2 </span>Discovery and Communication with Home Network Services</h3>
-			<div class="note">
-				No standard available at the moment. Useful references:
-				<ul>
-					<li><a href="http://www.w3.org/TR/2011/NOTE-hnreq-20111201/">Requirements for Home Networking Scenarios (IG Note)</a></li>
-					<li><a href="http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html">Web Intents</a></li>
-					<li><a href="http://people.opera.com/richt/release/specs/discovery/Overview.html">Networked Service Discovery and Messaging</a></li>
-				</ul>			
-			</div>		
-		</div>
-			
-</div>
-
-<div id="testing" class="section">
-<!--OddPage--><h2><span class="secno">7. </span>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/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>
-	
-
-</div>
-
-<div id="performances" class="section">
-	<!--OddPage--><h2><span class="secno">8. </span>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 <em class="rfc2119" title="shall not">shall not</em> support N, B may support N, C <em class="rfc2119" title="shall">shall</em> support N?</li>
-		</ul>
-	</div>
-</div>
-
-<div class="appendix section" id="acknowledgements">
-	<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
-	<p> Thanks to ... for their contributions to this document</p>
-	<!-- Mark Watson, Mark Vickers, Bob Lund, Clarke Stevens, Jan Lindquist, -->
-	<p> Thanks to participants of the following groups for their feedbacks: Web and TV Interest Group</p>
-</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><dl class="bibliography"><dt id="bib-CSS3-2D-TRANSFORMS">[CSS3-2D-TRANSFORMS]</dt><dd>Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href="http://www.w3.org/TR/css3-2d-transforms/"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-2d-transforms/">http://www.w3.org/TR/css3-2d-transforms/</a> 
-</dd><dt id="bib-CSS3-3D-TRANSFORMS">[CSS3-3D-TRANSFORMS]</dt><dd>Dean Jackson; David Hyatt; Chris Marrin. <a href="http://www.w3.org/TR/css3-3d-transforms/"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-3d-transforms/">http://www.w3.org/TR/css3-3d-transforms</a> 
-</dd><dt id="bib-CSS3-BG">[CSS3-BG]</dt><dd>Elika J. Etemad; Bert Bos; Brad Kemper. <a href="http://www.w3.org/TR/css3-background/"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href="http://www.w3.org/TR/css3-background/">http://www.w3.org/TR/css3-background/</a> 
-</dd><dt id="bib-CSS3-FONTS">[CSS3-FONTS]</dt><dd>John Daggett (Mozilla). <a href="http://www.w3.org/TR/css3-fonts"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href="http://www.w3.org/TR/css3-fonts">http://www.w3.org/TR/css3-fonts</a> 
-</dd><dt id="bib-CSS3-MEDIAQUERIES">[CSS3-MEDIAQUERIES]</dt><dd>H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href="http://www.w3.org/TR/css3-mediaqueries/"><cite>Media Queries</cite></a>  URL: <a href="http://www.w3.org/TR/css3-mediaqueries/">http://www.w3.org/TR/css3-mediaqueries/</a> 
-</dd><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> 
-</dd><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><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><dt id="bib-TOUCH-EVENTS">[TOUCH-EVENTS]</dt><dd>Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href="http://www.w3.org/TR/touch-events/"><cite>Touch Events version 1</cite></a> URL: <a href="http://www.w3.org/TR/touch-events/">http://www.w3.org/TR/touch-events</a>
-</dd><dt id="bib-WIDGETS">[WIDGETS]</dt><dd>Marcos Cáceres. <a href="http://www.w3.org/TR/widgets/"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/widgets/">http://www.w3.org/TR/widgets/</a> 
-</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><p>No informative references.</p></div></div></body></html>
\ No newline at end of file