W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: MIME type for WAVE with PCM?

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 17 Jun 2009 14:03:34 +1200
Message-ID: <11e306600906161903n46ac602aod934564a0971f78b@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: David Singer <singer@apple.com>, Simon Pieters <simonp@opera.com>, public-html@w3.org
On Wed, Jun 17, 2009 at 1:59 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Wed, Jun 17, 2009 at 7:21 AM, Anne van Kesteren <annevk@opera.com>wrote:
>
>> On Tue, 16 Jun 2009 20:30:45 +0200, David Singer <singer@apple.com>
>> wrote:
>> > well, not exactly.  There should be documentation of the codecs
>> > parameter for WAV files before we know what to put in there.  RFC
>> > 4281 doesn't say (because we didn't 'own' wav, I think).
>>
>> I sort of get the feeling that defining our own magic list of codec
>> keywords that map to existing formats would have been easier :/ (Also for
>> authors.)
>>
>
> You mean easier than using a number? Possibly, although there are at least
> 104 Wave codecs (!).
>
> But we can still do that, and support both names and numbers in the future,
> if someone's motivated enough to make up a keyword list.
>

Actually I guess an easy way to do it would be to strip WAVE_FORMAT_ off the
symbolic identifier and lowercase the rest. So we'd get
audio/wave; codecs=pcm
audio/wave; codecs=gsm610
audio/wave; codecs=dolby_ac3_spdif

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
Received on Wednesday, 17 June 2009 02:04:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:38 GMT