[pardon me if this retreads some ground, but I'm just getting up to speed on
this issue]
so am I to understand --
application/ogg is for downloading, and will invoke an app that supposedly can
parse *any* ogg file --
audio/vorbis is for streaming -- but this is narrowly defined as vorbis audio
only. Presumably the thinking is that a streaming application is likely to be
less general-purpose?
So when we get Theora working, we'll need to go back to the IETF and get
video/theora, video/theora-vorbis, or something like that. And then again with
Tarkin? What if someone compresses Tarkin with a Speex audio stream? Or
metadata? etc.
ISTM there is a logical inconsistency here: the download MIME type is at the OGG
(wrapper) level, whereas streaming is one level down at the content level.
The *logical* thing to do (which of course may not be an option here) would be
to have a streaming/ogg type for the *general* case that one is streaming OGG
files without regard to exactly what is in them.
-dbm
<p><p>> -----Original Message-----> From: Linus Walleij [mailto:triad@df.lth.se]
> Sent: Wednesday, January 08, 2003 5:27 AM
> To: vorbis-dev@xiph.org
> Subject: [vorbis-dev] [Fwd: Re: Regarding non-streaming Ogg]
>
>
> This is my previous conversation with Colin Perkins at IETF regarding
> audio/vorbis. For interested parties. Last two paragraphs are the most
> interesting ones.
>
> Linus
>
> -----Vidarebefordrat meddelande-----
>
> From: Colin Perkins <csp@isi.edu>
> To: Linus Walleij <triad@df.lth.se>
> Subject: Re: Regarding non-streaming Ogg
> Date: 20 Jun 2001 16:17:34 -0400
>
> --> Linus Walleij writes:
> >Colin,
> >
> >regarding application/ogg,
> draft-walleij-ogg-mediatype-02.txt which is not
> >subject to streaming issues like the audio/vorbis, could
> this draft be
> >advanced to be a proposed standard on the standards track?
> This would be
> >good since it provides a fallback MIME type for downloading
> .ogg files off
> >webservers for example.
>
> Provided that it explains that it is not for streaming, and
> that another
> format is in development, then I don't see why not.
>
> >Regarding the audio/vorbis type, is it correct that from now
> on, the same
> >MIME type is to be used for sockets and streaming, so that
> audio/vorbis is
> >the MIME type in both cases? I was confused when reading through the
> >drafts and seeing that the content usually denoted as
> audio/mpeg becomes
> >audio/MPA under RTP for example.
>
> Yes. The audio/mpa vs. audio/mpeg thing is the result of combining two
> previously separate namespaces, and not something we should emulate in
> new formats.
>
> Colin
>
>
> --- >8 ----
> List archives: http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to
> 'vorbis-dev-request@xiph.org'
> containing only the word 'unsubscribe' in the body. No
> subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.