Hello,<br><br>Sorry if this too has been discussed many times already, but....<br><br>(Assuming there is one....) What's the argument against also registering MIME types like "video/ogg" and "audio/ogg" (instead of just giving everything a "application/ogg" extension)?
<br><br><br>See ya<br><br><div><span class="gmail_quote">On 10/24/06, <b class="gmail_sendername">Ralph Giles</b> <<a href="mailto:giles@xiph.org">giles@xiph.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Oct 24, 2006 at 10:32:12AM +0100, Ivo Emanuel Gonçalves wrote:<br><br>> Oh, and sorry for having brought this up. Was just trying to help,<br>> but yeah, it wasn't needed or well planned. I'll be shutting up now.
<br><br>'S ok, it's an easy mistake to make if you haven't lived through past<br>incarnations of the argument. We really do appreciate your help.<br><br>If it helps, the issues go something of like this:<br><br>Some people want to use different applications for audio and video
<br>playback. On windows in particular, this decision is by default<br>made based on the file extension, rather than a more reliable<br>file magic check or the internet media type when it's from a remote<br>server. So they want different extensions to mark audio and video files.
<br><br>Coming from a unix background, the core xiph developers believe that<br>while file extensions are a nice shorthand, but you should be able<br>to name your files whatever you want and have things still work. So<br>
we want to encourage applications to be more sophisticated about file<br>identification of container formats like Ogg.<br><br>Implicit in this is that we'd be fine with an optional extension. But if<br>the goal of having a separate extension is so files and streams coming
<br>from the network go to the correct player, then the extension really<br>isn't optional. If most people don't use it, it won't reliably serve to<br>distinguish between the desired players.<br><br>So while we're fine with an optional extension, the choice is between
<br>recomending one, or recomending two or more distinct extensions. In<br>this we're guided by one of Xiph's design principles: don't make it<br>harder to make good software. If the extension can be wrong, you have<br>to look in the file anyway, so making the extension match the file
<br>contents is just another thing that has to be implemented properly on<br>top of what's already required.<br><br>That why, when people ask, we recommend just .ogg as a file extension.<br><br>FWIW,<br> -r<br><br></blockquote>
</div><br><br clear="all"><br>-- <br> Charles Iliya Krempeaux, B.Sc.<br><br> charles @ <a href="http://reptile.ca">reptile.ca</a><br> supercanadian @ <a href="http://gmail.com">gmail.com</a><br><br> developer weblog:
<a href="http://ChangeLog.ca/">http://ChangeLog.ca/</a><br><br>