--- a/media-profile/Overview-src.html Tue Mar 13 18:10:08 2012 +0100
+++ b/media-profile/Overview-src.html Tue Mar 13 18:16:03 2012 +0100
@@ -47,7 +47,7 @@
// 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"],
+ "style.css"],
// editors, add as many as you like
// only "name" is required
@@ -232,6 +232,7 @@
<section id="css">
<h2>CSS</h2>
+ <div class="note">The list below needs review</div>
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">
--- a/media-profile/Overview.html Tue Mar 13 18:10:08 2012 +0100
+++ b/media-profile/Overview.html Tue Mar 13 18:16:03 2012 +0100
@@ -476,8 +476,8 @@
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>
+</style><link href="style.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 media services in a browser-based environment</h2><h2 id="w3c-editor-s-draft-13-march-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 13 March 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>
@@ -601,7 +601,7 @@
<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/3721A4B2-266C-4C88-ABFD-9DC955EBD87C@gmail.com">http://www.w3.org/mid/3721A4B2-266C-4C88-ABFD-9DC955EBD87C@gmail.com</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>.
+ 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="must">must</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>
@@ -613,7 +613,7 @@
<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><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="must">must</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="must">must</em> comply with conformance requirements for user agents unless differently specified in this document; in particular browsers <em class="rfc2119" title="must">must</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.
@@ -622,19 +622,19 @@
<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>
+ <li><a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="must">must</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="must">must</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>
+ <div class="note">The list below needs review</div>
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>
+ <a href="#dfn-browser" class="internalDFN">Browser</a>s <em class="rfc2119" title="must">must</em> support [<cite><a class="bibref" rel="biblioentry" href="#bib-CSS21">CSS21</a></cite>].
</div>
<div id="css-at-rules" class="section">
@@ -700,7 +700,7 @@
<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>].
+ A conforming <a href="#dfn-browser" class="internalDFN">browser</a> <em class="rfc2119" title="must">must</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>
@@ -739,7 +739,7 @@
<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
+ 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>
</div>
@@ -847,7 +847,7 @@
<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>
+ <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="must not">must not</em> support N, B may support N, C <em class="rfc2119" title="must">must</em> support N?</li>
</ul>
</div>
</div>
@@ -860,7 +860,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-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>
+<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-CSS21">[CSS21]</dt><dd>Bert Bos; et al. <a href="http://www.w3.org/TR/CSS21/"><cite>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a>. W3C Recommendation. URL: <a href="http://www.w3.org/TR/CSS21">http://www.w3.org/TR/CSS21/</a>
+</dd><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>
@@ -870,4 +871,4 @@
</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
+</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>