Keith Moore (moore@cs.utk.edu)
Wed, 04 Aug 1999 21:18:24 -0400
> The problem with "what people think of as WAV files" is that there are a
> variety of implementations of WAV file formatting, and the VPIM spec should
> be as specific as possible.
right. so make the vpim be very specific as to what kind of wav files
are acceptable for the vpim context, and let the audio/wav content-type
correspond more-or-less.to "what people think of as WAV files".
i.e. make vpim-acceptable-content more rigorous than audio/wav.
if you want, define a parameter for audio/wav that indicates the
precise format and codec, define which values of that parameter are
acceptable for vpim, and insist that vpim implementations include that
parameter in mail that they generate. this won't directly help
interoperability, since it's duplicating information already present
in the wav file itself. but it might help call attention to the fact
that only certain formats/codecs of wav are valid for vpim.
think of it as a form of social engineering.
Keith
This archive was generated by hypermail 2.0b3 on Tue Mar 19 2002 - 01:04:14 IDT