I'm not saying that the MPEG codecs meet the <a href="http://3.12.7.1">3.12.7.1</a> requirements. I'm saying that ISO/IEC MPEG standards are vastly preferable to the nonstandard, single-company junk that web developers are saddled with now. The W3C need not abandon its ideals to declare that MPEG standards are better than the status quo of MS, Adobe and Real "standards." From my perspective, and for what it's worth, I doubt that the ideals of the W3C as expressed in <a href="http://3.12.7.1">3.12.7.1</a> would result in a situation that would be superior to simply letting the international standards body for audio and video codecs deal with these technological areas. IF <a href="http://3.12.7.1">3.12.7.1</a> were satisfied by Ogg or some other effort, we would still at best end up with a bifurcated digital world, where the web went with the free/open "standard," while every other digital representation of video and audio was encoded in the MPEG set of standards. I just think idealism shouldn't have to trump pragmatism in this instance.<div>
<br></div><div>Who wins and who loses? Web and new media developers win by having a streamlined workflow and one expectation for video and audio standards support in browsers. Users win by not having to worry about whether or not they have the right plug-in for Site A or Site B. The W3C wins by having a video tag that's reliable and complete, and not just a sort-of-better EMBED.</div>
<div><br></div><div>The issue of a small licensing fee didn't stop MPEG 1 Part 3 from becoming the ubiquitous world standard for audio. It isn't going to stop MPEG-4 AAC from supplanting it, and it hasn't stopped MPEG-2 and AVC from being the standard for HD codecs. Insisting on purity in these matters while the world moves on strikes me as just a bit quixotic.</div>
<div><div><br><br><div class="gmail_quote">On Mon, Mar 31, 2008 at 12:10 PM, Gervase Markham <<a href="mailto:gerv@mozilla.org">gerv@mozilla.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Robert J Crisler wrote:<br>
> The text under <a href="http://3.12.7.1" target="_blank">3.12.7.1</a> could have been written ten years ago:<br>
><br>
> "It would be helpful for interoperability if all browsers could support<br>
> the same codecs. However, there are no known codecs that satisfy all the<br>
> current players: we need a codec that is known to not require per-unit<br>
> or per-distributor licensing, that is compatible with the open source<br>
> development model, that is of sufficient quality as to be usable, and<br>
> that is not an additional submarine patent risk for large companies.<br>
> This is an ongoing issue and this section will be updated once more<br>
> information is available."<br>
<br>
...<br>
<br>
> You may have a digital cable or satellite service (that's<br>
> MPEG-2 or MPEG-4). You may have a DVD player (MPEG-2), or a Blu-Ray<br>
> player (MPEG-4). You may have an iPod (MPEG-4). And you may have heard<br>
> of MP3.<br>
<br>
So you believe that these codecs meet the requirements in <a href="http://3.12.7.1" target="_blank">3.12.7.1</a>? Or<br>
are you saying that the requirements need to change? If you are saying<br>
they need to change, who wins and who loses from the change? And how do<br>
you justify that?<br>
<br>
Gerv<br>
</blockquote></div><br></div></div>