audio/x-riff mime type

[Jerome Leclanche]

The audio/x-riff mime type is causing me trouble currently. Namely, it
is conflicting with image/webp as webp images are based on RIFF
containers (this hasn't come up since only kde ships a webp mime type
for now).

Why is there an audio/x-riff mime type at all? The only riff-based
audio is wav, which has its own mime type (audio/x-wav) and gets
correctly detected.

Unless someone has a strong reason not to, I suggest immediately
dropping the audio/x-riff mime type from the fdo database, as the only
matches it will get are on generic riff-based files.
If the mime type is necessary, i suggest creating a new one,
application/x-riff: "RIFF data" which would be a parent of audio/wav,
image/webp etc.

J. Leclanche

[Thiago Macieira]

Post by Jerome Leclanche
Why is there an audio/x-riff mime type at all? The only riff-based
audio is wav, which has its own mime type (audio/x-wav) and gets
correctly detected.
Unless someone has a strong reason not to, I suggest immediately
dropping the audio/x-riff mime type from the fdo database, as the only
matches it will get are on generic riff-based files.
If the mime type is necessary, i suggest creating a new one,
application/x-riff: "RIFF data" which would be a parent of audio/wav,
image/webp etc.

Right, that makes sense.

RIFF can embed other types of media. It's just that so far it's basically been
used only for audio files, and WAV at that. If there's now a good use of it
with non-audio data, it should be in the application/ hierarchy.