[theora-dev] ogg, mimetypes and containers and rfc4281
giles at xiph.org
Thu Mar 22 10:28:23 PDT 2007
Wow, cool. Sounds good. I think we should also push the disposition
hinting proposal, since that's more meaningful for player determination.
Content-Type: application/ogg; disposition=moving-image; codecs="theora, vorbis"
Content-Type: application/ogg; disposition=sound; codecs="speex"
Gets to be a long line. Is this compatible with RFC 4281?
http://www.advogato.org/article/852.html is the proposal.
A good place might be the RFCs documenting the codec mime-types, which
are being done in connection with the RTP payload formats. We should
also add it to the Ogg-embedding specs for the various codecs.
On Thu, Mar 22, 2007 at 11:32:19AM +0100, j at v2v.cc wrote:
> just found http://www.ietf.org/rfc/rfc4281 and it looks like a good
> way to indicate
> which content ogg streams have,
> to my understanding one would use things like these:
> Content-Type: application/ogg; codecs="theora, vorbis"
> Content-Type: application/ogg; codecs="theora, speex"
> Content-Type: application/ogg; codecs="vorbis"
> what would be a good place to document that so people interested can
> start using it?
> theora-dev mailing list
> theora-dev at xiph.org
More information about the theora-dev