<div class="gmail_quote">2009/6/30 Silvia Pfeiffer <span dir="ltr"><<a href="mailto:silviapfeiffer1@gmail.com">silviapfeiffer1@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
On Tue, Jun 30, 2009 at 2:50 PM, Ian Hickson<<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>> wrote:<br>
> I considered requiring Ogg Theora support in the spec, since we do have<br>
> three implementations that are willing to implement it, but it wouldn't<br>
> help get us true interoperabiliy, since the people who are willing to<br>
> implement it are willing to do so regardless of the spec, and the people<br>
> who aren't are not going to be swayed by what the spec says.<br>
<br>
</div>Inclusion of a required baseline codec into a standard speaks more<br>
loudly than you may think. It provides confidence - confidence that an<br>
informed choice has been made as to the best solution in a given<br>
situation. Confidence to Web developers, confidence to hosting<br>
providers, confidence also (but less so, since they are gatekeepers in<br>
this situation) to Browser Vendors.<br>
<br>
In my opinion, including a baseline codec requirement into a W3C<br>
specification that is not supported by all Browser Vendors is much<br>
preferable over an unclear situation, where people are forced to<br>
gather their own information about a given situation and make a<br>
decision on what to choose based on potentially very egoistic and<br>
single-sided reasons/recommendations.<br>
<br>
In fact, it is a tradition of HTML to have specifications that are<br>
only supported by a limited set of Browser Vendors and only over time<br>
increasingly supported by all - e.g. how long did it take for all<br>
Browser vendors to accept css2, and many of the smaller features of<br>
html4 such as fixed positioning?</blockquote><div><br>Right. Waiting for all vendors to support the specified codec would be like waiting for them all to be <span>Acid</span>3 compliant. Better to specify how browsers should behave (especially if it's how most of them will behave), and let the stragglers pick up the slack in their own time under consumer pressure.<br>
<br>Sam<br></div></div>