Vorbis dev - Aug 2007 - Clarification on MIME types

Just an important detail that I must be sure of before I continue to
draft the RFC I'm working on, as well as going to IANA later.

What makes more sense?

audio/ogg for Ogg FLAC, Speex, Vorbis, Ghost with a disposition type
thrown in in the mix?

Or audio/ogg+flac, audio/ogg+speex, audio/ogg+vorbis, etc?

Let's call the latter the XHTML approach.  It would force us to
register a new MIME type for every project using Ogg.  It would
probably help application developers, though.

The former approach is more akin I think to MPEG's audio/mpeg, which
puts any audio on a MPEG container with that MIME.  See: MP3.  Also,
not a large list of MIME types to register.  However, it may become
harder for developers to support everything out there under audio/ogg.

This concern applies as well to video/ogg, but not to application/ogg,
because it would be impossible to track all possible mixes that might
go in .ogx

-Ivo

On Tue, Aug 28, 2007 at 07:45:02PM +0100, Ivo Emanuel Gon?alves wrote:
> audio/ogg for Ogg FLAC, Speex, Vorbis, Ghost with a disposition type
> thrown in in the mix?
I thought we had decided on this, without the disposition type? 
Basically copying the mpeg scheme.
> Or audio/ogg+flac, audio/ogg+speex, audio/ogg+vorbis, etc?
I think this is silly. video/ogg+dirac+vorbis+cmml? There is a published 
RFC for codec hinting, btw. You could reference that on this point, but 
I don't think it should be required.
> This concern applies as well to video/ogg, but not to application/ogg,
> because it would be impossible to track all possible mixes that might
> go in .ogx
I also thought we'd agreed to drop .ogx?

 -r