--- a/tvprofile/tv.html Mon Jan 16 20:17:00 2012 +0100
+++ b/tvprofile/tv.html Mon Jan 16 20:18:38 2012 +0100
@@ -476,18 +476,18 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="tv.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/w3c-unofficial" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><div class="head"><p></p><h1 class="title" id="title">Web&TV profile (provisional title)</h1><h2 id="subtitle">Guidelines for integration of interactive TV services in a Browser-based environment</h2><h2 id="unofficial-draft-13-january-2012">Unofficial Draft 13 January 2012</h2><dl><dt>Editor:</dt><dd><span>Giuseppe Pascale</span>, <a href="http://www.opera.com/">Opera</a></dd>
+ <body style="display: inherit; "><div class="head"><p></p><h1 class="title" id="title">Web&TV profile (provisional title)</h1><h2 id="subtitle">Guidelines for integration of interactive TV services in a Browser-based environment</h2><h2 id="unofficial-draft-16-january-2012">Unofficial Draft 16 January 2012</h2><dl><dt>Editor:</dt><dd><span>Giuseppe Pascale</span>, <a href="http://www.opera.com/">Opera</a></dd>
</dl><p class="copyright">This document is licensed under a <a class="subfoot" href="http://creativecommons.org/licenses/by/3.0/" rel="license">Creative Commons Attribution 3.0 License</a>.</p><hr></div>
<div id="abstract" class="introductory section"><h2>Abstract</h2>
-</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p>This document is merely a public working draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organisation.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#background" class="tocxref"><span class="secno">1.1 </span>Background</a></li><li class="tocline"><a href="#design-goals" class="tocxref"><span class="secno">1.2 </span>Design Goals</a><ul class="toc"><li class="tocline"><a href="#avoid-obsolesce" class="tocxref"><span class="secno">1.2.1 </span>Avoid obsolesce</a></li><li class="tocline"><a href="#improve-interoperability" class="tocxref"><span class="secno">1.2.2 </span>Improve interoperability</a></li><li class="tocline"><a href="#coordinate-deployments" class="tocxref"><span class="secno">1.2.3 </span>Coordinate deployments</a></li><li class="tocline"><a href="#provide-a-complete-application-environment" class="tocxref"><span class="secno">1.2.4 </span>Provide a complete application environment</a></li><li class="tocline"><a href="#do-not-reinvent-the-wheel" class="tocxref"><span class="secno">1.2.5 </span>Do not reinvent the wheel</a></li><li class="tocline"><a href="#a-tunable-meta-profile" class="tocxref"><span class="secno">1.2.6 </span>A tunable meta-profile</a></li></ul></li><li class="tocline"><a href="#audience" class="tocxref"><span class="secno">1.3 </span>Audience</a></li><li class="tocline"><a href="#scope" class="tocxref"><span class="secno">1.4 </span>Scope</a></li></ul></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">2. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2.1 </span>Conformance</a></li><li class="tocline"><a href="#definitions" class="tocxref"><span class="secno">2.2 </span>Definitions</a></li></ul></li><li class="tocline"><a href="#overview" class="tocxref"><span class="secno">3. </span>Overview</a><ul class="toc"><li class="tocline"><a href="#system-architecture" class="tocxref"><span class="secno">3.1 </span>System Architecture</a></li><li class="tocline"><a href="#application-model" class="tocxref"><span class="secno">3.2 </span>Application Model</a></li></ul></li><li class="tocline"><a href="#browser-environment" class="tocxref"><span class="secno">4. </span>Browser Application Environment</a><ul class="toc"><li class="tocline"><a href="#html" class="tocxref"><span class="secno">4.1 </span>HTML</a><ul class="toc"><li class="tocline"><a href="#scripting" class="tocxref"><span class="secno">4.1.1 </span>Scripting</a></li><li class="tocline"><a href="#css" class="tocxref"><span class="secno">4.1.2 </span>CSS</a><ul class="toc"><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">4.1.2.1 </span>CSS3 Fonts</a></li></ul></li><li class="tocline"><a href="#document-object-model--dom" class="tocxref"><span class="secno">4.1.3 </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">4.1.4 </span>... (add more section for other web standards)</a></li></ul></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">4.2 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">4.2.1 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">4.2.2 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">4.2.3 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">4.2.4 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">4.3 </span>Content Developers Guidelines</a></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">5. </span>Formats and Protocols</a></li><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">6. </span>Testing</a></li><li class="tocline"><a href="#performances" class="tocxref"><span class="secno">7. </span>Performances</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
+</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p>This document is merely a public working draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organisation.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#background" class="tocxref"><span class="secno">1.1 </span>Background</a></li><li class="tocline"><a href="#design-goals" class="tocxref"><span class="secno">1.2 </span>Design Goals</a><ul class="toc"><li class="tocline"><a href="#avoid-obsolesce" class="tocxref"><span class="secno">1.2.1 </span>Avoid obsolesce</a></li><li class="tocline"><a href="#improve-interoperability" class="tocxref"><span class="secno">1.2.2 </span>Improve interoperability</a></li><li class="tocline"><a href="#coordinate-deployments" class="tocxref"><span class="secno">1.2.3 </span>Coordinate deployments</a></li><li class="tocline"><a href="#provide-a-complete-application-environment" class="tocxref"><span class="secno">1.2.4 </span>Provide a complete application environment</a></li><li class="tocline"><a href="#do-not-reinvent-the-wheel" class="tocxref"><span class="secno">1.2.5 </span>Do not reinvent the wheel</a></li><li class="tocline"><a href="#a-tunable-meta-profile" class="tocxref"><span class="secno">1.2.6 </span>A tunable meta-profile</a></li></ul></li><li class="tocline"><a href="#audience" class="tocxref"><span class="secno">1.3 </span>Audience</a></li><li class="tocline"><a href="#scope" class="tocxref"><span class="secno">1.4 </span>Scope</a></li><li class="tocline"><a href="#system-overview" class="tocxref"><span class="secno">1.5 </span>System Overview</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="#browser-environment" class="tocxref"><span class="secno">3. </span>Browser Application Environment</a><ul class="toc"><li class="tocline"><a href="#html" class="tocxref"><span class="secno">3.1 </span>HTML</a><ul class="toc"><li class="tocline"><a href="#scripting" class="tocxref"><span class="secno">3.1.1 </span>Scripting</a></li><li class="tocline"><a href="#css" class="tocxref"><span class="secno">3.1.2 </span>CSS</a><ul class="toc"><li class="tocline"><a href="#css3-fonts" class="tocxref"><span class="secno">3.1.2.1 </span>CSS3 Fonts</a></li></ul></li><li class="tocline"><a href="#document-object-model--dom" class="tocxref"><span class="secno">3.1.3 </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">3.1.4 </span>... (add more section for other web standards)</a></li></ul></li><li class="tocline"><a href="#input-methods" class="tocxref"><span class="secno">3.2 </span>Input Methods</a><ul class="toc"><li class="tocline"><a href="#traditional-remote-controls" class="tocxref"><span class="secno">3.2.1 </span>Traditional Remote Controls</a></li><li class="tocline"><a href="#touch-screens" class="tocxref"><span class="secno">3.2.2 </span>Touch screens</a></li><li class="tocline"><a href="#mouse-and-keyboard" class="tocxref"><span class="secno">3.2.3 </span>Mouse and Keyboard</a></li><li class="tocline"><a href="#other-input-devices" class="tocxref"><span class="secno">3.2.4 </span>Other input devices</a></li></ul></li><li class="tocline"><a href="#content-developers-guidelines" class="tocxref"><span class="secno">3.3 </span>Content Developers Guidelines</a></li></ul></li><li class="tocline"><a href="#formats-and-protocols" class="tocxref"><span class="secno">4. </span>Formats and Protocols</a></li><li class="tocline"><a href="#testing" class="tocxref"><span class="secno">5. </span>Testing</a></li><li class="tocline"><a href="#performances" class="tocxref"><span class="secno">6. </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 class="informative section" id="introduction">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
<div id="background" class="section">
<h3><span class="secno">1.1 </span>Background</h3>
- <p>There is an increasing number of content providers worldwide that are deploying interactive TV services based on web technologies. In order to achieve that, many organizations and companies have created profiles of web technologies suitable for use in a specific market and/or region. These profiles are supersets, subsets or both of several W3C specifications. Often these documents have been written without a direct involvement of relevant W3C working groups. Furthermore not always these different groups were aware of each other, leading to different profiles in different regions and markets. In some cases also extensions to web standards have been designed, leading to multiple incompatible solutions addressing the same use case.</p>
+ <p>There is an increasing number of content and service providers worldwide that are deploying interactive TV services based on web technologies. In order to achieve that, many organizations and companies have created profiles of web technologies suitable for use in a specific market and/or region. These profiles are supersets, subsets or both of several W3C specifications. Often these documents have been written without a direct involvement of relevant W3C working groups. Furthermore not always these different groups were aware of each other, leading to different profiles in different regions and markets. In some cases also extensions to web standards have been designed, leading to multiple incompatible solutions addressing the same use case.</p>
<p>The goal of this document is to reduce fragmentation and eliminate the needs for extensions, by providing a common meta-profile that allows external organizations to align with W3C and with each other. While is not possible to provide a profile that cover all needs of different organizations and stakeholders, this meta-profile tries to keep at a minimum the variables involved in defining new profiles, providing a common reference framework that different organization can reuse.</p>
</div>
@@ -529,20 +529,34 @@
<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" href="#dfn-content-provider" class="internalDFN">content</a> and <a href="#dfn-service-provider" class="internalDFN">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 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 href="#dfn-user" class="internalDFN">user</a> would be expected to have on their devices are out of scope.
+ 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 id="system-overview" class="section">
+ <h3><span class="secno">1.5 </span>System Overview</h3>
+ <div class="note">This section gives and overview of the typical architecture of an interactive TV services delivery system. The level of detail of this section is general and abstract: there is no attempt to provide an in-depth technical explanation of each component and of the interaction between them. Also in practice some logical component may be combined into one, and some component may be missing in some deployments and/or regions.</div>
+ <p>
+ The main goal of this profile is to simplify and harmonize the production and delivery of <a>TV Services</a> to web enabled devices. For the purposes of this document a <dfn 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 mainly 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 may range from a single legacy IPv4 subnet to multiple IPv4 subnets and dual stack or IPv6 environments and will typically (but not always) be connected to the Internet.
+ </p><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. 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 that are expected to be supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this specification are listed in <a href="#browser-environment" class="sectionRef">section 3. Browser Application Environment</a>.
+ </p></div>
</div>
@@ -560,49 +574,35 @@
<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 href="#dfn-broadband-network" class="internalDFN">broadband network</a>s or streamed from other devices.</li>
- <li><dfn id="dfn-tv-set">TV set</dfn>: A display device that can presents content from a variety of sources - such as received via <a href="#dfn-broadcast-network" class="internalDFN">broadcast network</a>s,<a href="#dfn-broadband-network" class="internalDFN">broadband network</a>s or streamed from other devices.</li>
- <li><dfn id="dfn-tv-service">TV service</dfn>: A providing commercial video service that may include elements of interactivity and provides a coherent user experience. TV services are usually divided into two main groups: <dfn title="schedule service" id="dfn-schedule-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).</li>
- <li><dfn id="dfn-device">device</dfn>: for the purposes of this document, a device is any piece of equipment owned by the user that is able to presentat <a href="#dfn-tv-service" class="internalDFN">TV service</a>s to the end user. Note that this is a generic term that also includes the <a href="#dfn-tv-set" class="internalDFN">TV set</a> and <a href="#dfn-stb" class="internalDFN">STB</a> terms defined in this document.</li>
- <li><dfn id="dfn-broadband-network">broadband network</dfn>: bi-directional IP connection</li>
- <li><dfn id="dfn-broadcast-network">broadcast network</dfn>: classical uni-directional TV broadcast networks such as DVB, ATSC, ISDB.
- </li><li><dfn id="dfn-user">user</dfn>: is the consumer of <a href="#dfn-tv-service" class="internalDFN">TV service</a>s. Traditionally TV services have been consumed only 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 end users have a wide range of devices (e.g. PC, laptops,smartphones, tablets) available both in their home and outside and expect to be able to access to services from any device.</li>
- <li><dfn id="dfn-service-provider">service provider</dfn>: aggregates content from one or more <a href="#dfn-content-provider" class="internalDFN">content provider</a>s and offer them to the end user for consumption.</li>
- <li><dfn id="dfn-content-provider">content provider</dfn>: the author of a piece of content that is later sold or licensed to <a href="#dfn-service-provider" class="internalDFN">service provider</a>s and consumed by the <a href="#dfn-user" class="internalDFN">user</a>s.</li>
+ <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.</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 class="informative section" id="overview">
-<!--OddPage--><h2><span class="secno">3. </span>Overview</h2><p><em>This section is non-normative.</em></p>
-
- <div id="system-architecture" class="section">
- <h3><span class="secno">3.1 </span>System Architecture</h3>
- <div class="note"> TODO: briefly describe the system architecture, just to explain how content is delivered to devices via a multitude of networks and which components of the overall architecture are in scope for this document. This section is just informative and should help the reader to understand which parts of the system architecture are covered by this spec but should not try to be an encyclopedic explanation of TV systems </div>
- </div>
- <div id="application-model" class="section">
- <h3><span class="secno">3.2 </span>Application Model</h3>
- The term <dfn id="dfn-application">application</dfn> is used to refer to a collection of documents and associated resources that can be used to provide a <a href="#dfn-tv-service" class="internalDFN">TV service</a> and are authored using a set of languages commonly referred to as "web technologies" or "web standards". In order to be able to run <a href="#dfn-application" class="internalDFN">application</a>s, devices implement an interactive user-agent commonly referred to as <dfn id="dfn-browser">browser</dfn>. The set of languages that are expected to be supported by the browser running on a <a href="#dfn-device" class="internalDFN">device</a> are listed in <a href="#browser-environment" class="sectionRef">section 4. Browser Application Environment</a>.
- </div>
-
-</div>
<div id="browser-environment" class="section">
-<!--OddPage--><h2><span class="secno">4. </span>Browser Application Environment</h2>
+<!--OddPage--><h2><span class="secno">3. </span>Browser Application Environment</h2>
This section list which languages are supported by <a href="#dfn-browser" class="internalDFN">browser</a>s conforming to this profile. <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">4.1 </span>HTML</h3>
+ <h3><span class="secno">3.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><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 id="scripting" class="section">
- <h4><span class="secno">4.1.1 </span>Scripting</h4>
+ <h4><span class="secno">3.1.1 </span>Scripting</h4>
<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>
@@ -611,35 +611,35 @@
</div>
<div id="css" class="section">
- <h4><span class="secno">4.1.2 </span>CSS</h4>
- Support for CSS as a whole is not required by HTML5, even though some features are defined in terms of specific CSS requirements.
+ <h4><span class="secno">3.1.2 </span>CSS</h4>
+ 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="css3-fonts" class="section">
- <h5><span class="secno">4.1.2.1 </span>CSS3 Fonts</h5>
- The [!CSS3-fonts] 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 user-agent.
+ <h5><span class="secno">3.1.2.1 </span>CSS3 Fonts</h5>
+ The [<cite><a class="bibref" rel="biblioentry" href="#bib-CSS3-FONTS">CSS3-FONTS</a></cite>] module describes how font properties are specified and how font resources are loaded dynamically.
+ The features marked as included below <em class="rfc2119" title="shall">shall</em> be supported by conforming <a href="#dfn-browser" class="internalDFN">browser</a>s.
<dt>Properties</dt>
<dd>
- <table class="parameters">
+ <table class="profile">
<tbody><tr>
- <th>Name</th>
- <th>Notes</th>
- <th>Included</th>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
</tr>
<tr>
- <td>font</td><td></td>
+ <td>font</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-size</td><td></td>
+ <td>font-size</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-size-adjust</td><td></td>
+ <td>font-size-adjust</td>
<td class="n">no</td>
</tr>
<tr>
- <td>font-variant</td><td></td>
+ <td>font-variant</td>
<td class="y">yes</td>
</tr>
</tbody></table>
@@ -647,26 +647,26 @@
<dt>Descriptors</dt>
<dd>
- <table class="parameters">
+ <table class="profile">
<tbody><tr>
- <th>Name</th>
- <th>Notes</th>
- <th>Included</th>
+ <th scope="col">Name</th>
+ <th scope="col">Included</th>
+ <th scope="col">Notes</th>
</tr>
<tr>
- <td>font-family</td><td></td>
+ <td>font-family</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-stretch</td><td></td>
+ <td>font-stretch</td>
<td class="n">no</td>
</tr>
<tr>
- <td>font-style</td><td></td>
+ <td>font-style</td>
<td class="y">yes</td>
</tr>
<tr>
- <td>font-weight</td><td></td>
+ <td>font-weight</td>
<td class="y">yes</td>
</tr>
</tbody></table>
@@ -675,38 +675,38 @@
</div>
<div id="document-object-model--dom" class="section">
- <h4><span class="secno">4.1.3 </span>Document Object Model (DOM)</h4>
+ <h4><span class="secno">3.1.3 </span>Document Object Model (DOM)</h4>
</div>
<div id="x...--add-more-section-for-other-web-standards" class="section">
- <h4><span class="secno">4.1.4 </span>... (add more section for other web standards)</h4>
+ <h4><span class="secno">3.1.4 </span>... (add more section for other web standards)</h4>
</div>
</div>
<div id="input-methods" class="section">
- <h3><span class="secno">4.2 </span>Input Methods</h3>
+ <h3><span class="secno">3.2 </span>Input Methods</h3>
<div id="traditional-remote-controls" class="section">
- <h4><span class="secno">4.2.1 </span>Traditional Remote Controls</h4>
+ <h4><span class="secno">3.2.1 </span>Traditional Remote Controls</h4>
</div>
<div id="touch-screens" class="section">
- <h4><span class="secno">4.2.2 </span>Touch screens</h4>
+ <h4><span class="secno">3.2.2 </span>Touch screens</h4>
</div>
<div id="mouse-and-keyboard" class="section">
- <h4><span class="secno">4.2.3 </span>Mouse and Keyboard</h4>
+ <h4><span class="secno">3.2.3 </span>Mouse and Keyboard</h4>
</div>
<div id="other-input-devices" class="section">
- <h4><span class="secno">4.2.4 </span>Other input devices</h4>
+ <h4><span class="secno">3.2.4 </span>Other input devices</h4>
</div>
</div>
<div class="informative section" id="content-developers-guidelines">
- <h3><span class="secno">4.3 </span>Content Developers Guidelines</h3><p><em>This section is non-normative.</em></p>
+ <h3><span class="secno">3.3 </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">5. </span>Formats and Protocols</h2>
+ <!--OddPage--><h2><span class="secno">4. </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&tv IG. Therefore it should describe things like:
<ul>
<li>adaptive streaming
@@ -722,11 +722,11 @@
</div>
<div id="testing" class="section">
-<!--OddPage--><h2><span class="secno">6. </span>Testing</h2>
+<!--OddPage--><h2><span class="secno">5. </span>Testing</h2>
</div>
<div id="performances" class="section">
- <!--OddPage--><h2><span class="secno">7. </span>Performances</h2>
+ <!--OddPage--><h2><span class="secno">6. </span>Performances</h2>
</div>
<div class="appendix section" id="acknowledgements">
@@ -737,7 +737,8 @@
</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-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>
+<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-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-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></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