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

Re: comments on draft-barth-mime-sniffing

From: Jamie Lokier <jamie@shareable.org>
Date: Tue, 16 Jun 2009 16:25:43 +0100
To: Simon Pieters <simonp@opera.com>
Cc: Ian Hickson <ian@hixie.ch>, Robert O'Callahan <robert@ocallahan.org>, Adam Barth <w3c@adambarth.com>, Larry Masinter <masinter@adobe.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, public-html@w3.org
Message-ID: <20090616152543.GI29040@shareable.org>
Simon Pieters wrote:
> On Fri, 12 Jun 2009 20:55:29 +0200, Ian Hickson <ian@hixie.ch> wrote:
> 
> >I've updated HTML5 to require that Content-Types of types that are not
> >supported cause the resource to be ignored (even if it would otherwise be
> >supported).
> 
> If a UA does not know what is not supported, is it reasonable to consider  
> anything that is not video/* or audio/* to be not supported?

For video, content negotiation is probably going to end up being done
in Javascript rather than HTTP, or by User-Agent recognition.

The Content-Type of video/* simply doesn't provide enough information,
in practice to tell if the file can be played or not by a particular
browser / video player.  The file itself must be read, to determine
the codecs used.  Of course the client must understand the file
format, but the tough part is understanding the codec format inside
the file format, which is just a container.

Although there is an RFC specifying MIME sub-types to video/*
describing the codecs, I don't see any way to sensibly fit that into
HTTP's Accept: content-negotiation.

-- Jamie
Received on Tuesday, 16 June 2009 15:26:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:04 UTC