[widgets] Content-Type Processing Model

Hi Adam, Ian,
The Web Apps Working group recently became aware that the relevant
section on content sniffing from HTML5 has moved to its own internet
draft [1] (Content-Type Processing Model).  As our Widget packaging
spec [2] has some dependency on content sniffing, we would like to
contribute to this specification where possible. Particularly, we
would like to make sure that sniffing and appropriate MIME mappings
are made when resources are read from local storage.

At the moment, [1] reads:

" For resources fetched from the file system, user agents should use
  platform-specific conventions, e.g. operating system extension/type
  mappings."

We are concerned that operating system extension/type mappings might
cause issues for widget engines because those mapping could be
incorrect, or come from arbitrary sources etc. So we are looking to
collaborate to resolve this issue and wondering if that can be
standardized as part of [1]. Our current approach in [2] has been to
provide a table with a bunch of file extension to MIME mappings.

Kind regards,
Marcos

[1] http://tools.ietf.org/html/draft-abarth-mime-sniff-00
[2] http://dev.w3.org/2006/waf/widgets/


-- 
Marcos Caceres
http://datadriven.com.au

Received on Friday, 30 January 2009 16:18:07 UTC