W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

Fwd: [widgets] Content-type sniffing and file extension to MIME mapping

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Wed, 3 Dec 2008 22:03:28 +0000
Message-ID: <b21a10670812031403y316c28c0wc6a55287029b1f12@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>

I've added the following requirement to the Req doc:

R12. Derive the MIME types of Resources
In the case that the packaging format does not support labeling
resources with a MIME Type, a conforming specification MUST either
specify or recommend a means of deriving the MIME type of resources
for the purposes of rendering. A conforming specification MAY define a
means to override how a widget user agent derives the MIME type of a
resource (e.g., treat resources with the file extension .php as
text/html), but MUST NOT force a widget user agent to process
resources of one MIME type as that of another type (e.g. treating a
jpeg image at text/html).

Web and offline distribution, device independence, and current
development practice or industry best-practice.

To allow appropriate rendering of resources by the widget user agent.
For instance, for the sake of interoperability, all widget user agents
should treat resources with a .html file extension as text/html (and
not as application/xhtml+xml).

Here is the list of file extensions and what they should map to (added
to the packaging spec):

.html,.htm -> text/html
.css          -> text/css
.gif            -> image/gif
.jpeg, jpg  -> image/jpeg
.js             -> application/javascript
.xml          -> application/xml
.wav,wave -> audio/x-wav
.ico           -> image/vnd.microsoft.icon
.png          -> image/png

A widget user agent would be expected to support the above types. All
other types are optional. All proprietary types, apart from ico, are

Kind regards,
Received on Wednesday, 3 December 2008 22:04:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 13:55:23 UTC