Permalink
Browse files

[e] (0) Lift the cat who was amongst the pigeons up and put him back …

…on his pedestal for now. (remove requirement on ogg for now)

git-svn-id: http://svn.whatwg.org/webapps@1143 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Dec 11, 2007
1 parent 80b66ee commit 78cb4e133f332599b73ce6945b425f3c30e093fa
Showing with 38 additions and 27 deletions.
  1. +18 −13 index
  2. +20 −14 source
31 index
@@ -2212,13 +2212,16 @@
</dl>
<p>This specification does not require support of any particular network
transport protocols, image formats, audio formats, video formats, style
sheet language, scripting language, or any of the DOM and WebAPI
specifications beyond those described above. However, the language
described by this specification is biased towards CSS as the styling
language, ECMAScript as the scripting language, and HTTP as the network
protocol, and several features assume that those languages and protocols
are in use.
transport protocols, style sheet language, scripting language, or any of
the DOM and WebAPI specifications beyond those described above. However,
the language described by this specification is biased towards CSS as the
styling language, ECMAScript as the scripting language, and HTTP as the
network protocol, and several features assume that those languages and
protocols are in use.
<p class=note>This specification might have certain additional requirements
on character encodings, image formats, audio formats, and video formats in
the respective sections.
<h4 id=features><span class=secno>1.3.3. </span>Features defined in other
specifications</h4>
@@ -13440,12 +13443,14 @@ The island of Shalott.&lt;/p></pre>
<p>User agents may support any video and audio codecs and container
formats.
<p>User agents should support Ogg Theora video and Ogg Vorbis audio, as
well as the Ogg container format. <a href="#refsOggTheora">[THEORA]</a> <a
href="#refsOggVorbis">[VORBIS]</a> <a href="#refsOgg">[OGG]</a></p>
<!-- (it's not a MUST because some vendors may have legal reasons
why they can't or won't support it, and there's no point making them
non-conforming when they have no choice in the matter) -->
<p class=big-issue>It would be helpful for interoperability if all browsers
could support the same codecs. However, there are no known codecs that
satisfy all the current players: we need a codec that is known to not
require per-unit or per-distributor licensing, that is compatible with the
open source development model, that is of sufficient quality as to be
usable, and that is not an additional submarine patent risk for large
companies. This is an ongoing issue and this section will be updated once
more information is available.</p>
<!-- XXX mention that this spec doesn't require native support or
plugin support, either is fine -->
34 source
@@ -614,13 +614,17 @@
</dl>
<p>This specification does not require support of any particular
network transport protocols, image formats, audio formats, video
formats, style sheet language, scripting language, or any of the DOM
and WebAPI specifications beyond those described above. However, the
language described by this specification is biased towards CSS as
the styling language, ECMAScript as the scripting language, and HTTP
as the network protocol, and several features assume that those
languages and protocols are in use.</p>
network transport protocols, style sheet language, scripting
language, or any of the DOM and WebAPI specifications beyond those
described above. However, the language described by this
specification is biased towards CSS as the styling language,
ECMAScript as the scripting language, and HTTP as the network
protocol, and several features assume that those languages and
protocols are in use.</p>
<p class="note">This specification might have certain additional
requirements on character encodings, image formats, audio formats,
and video formats in the respective sections.</p>
<h4>Features defined in other specifications</h4>
@@ -11331,13 +11335,15 @@ The island of Shalott.&lt;/p></pre>
<p>User agents may support any video and audio codecs and container
formats.</p>
<p>User agents should support Ogg Theora video and Ogg Vorbis audio,
as well as the Ogg container format. <a
href="#refsOggTheora">[THEORA]</a> <a
href="#refsOggVorbis">[VORBIS]</a> <a href="#refsOgg">[OGG]</a></p>
<!-- (it's not a MUST because some vendors may have legal reasons
why they can't or won't support it, and there's no point making them
non-conforming when they have no choice in the matter) -->
<p class="big-issue">It would be helpful for interoperability if all
browsers could support the same codecs. However, there are no known
codecs that satisfy all the current players: we need a codec that is
known to not require per-unit or per-distributor licensing, that is
compatible with the open source development model, that is of
sufficient quality as to be usable, and that is not an additional
submarine patent risk for large companies. This is an ongoing issue
and this section will be updated once more information is
available.</p>
<!-- XXX mention that this spec doesn't require native support or
plugin support, either is fine -->

0 comments on commit 78cb4e1

Please sign in to comment.