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

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

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Wed, 10 Dec 2008 11:26:38 +0100
Message-ID: <493F995E.8010809@students.cs.uu.nl>
To: Marcos Caceres <marcosscaceres@gmail.com>
CC: Jonas Sicking <jonas@sicking.cc>, Simon Pieters <simonp@opera.com>, public-webapps <public-webapps@w3.org>
Marcos Caceres schreef:
> Seems that there is still too much incompatibility to suggest
> "application/xml" support across Widget user agents. I think we should
> just stick with text/html. If authors want to use "application/xml",
> then they can use <content src="somefile" type="application/xml" />
> and hope for the best :)

XHTML is a W3C standard that’s been Recommended status for many years 
and has plenty of implementations (except for Internet Explorer, at this 
time). This should be more than enough to warrant inclusion in the list 
of MIME type mappings.

I’m against using the application/xml type for XHTML by the way. A more 
specific MIME type is available and it has its use in certain occasions 
(e.g. for content negotiation, to determine whether the UA is requesting 
a human-readable XHTML  version or a site-specific machine-readable XML 
version). XML is a transmission format that a lot of different formats 
make use of, however each format using XML is still a format on its own 
and should have its own MIME type. E.g. application/xhtml+xml should not 
be confused with application/rdf+xml, even though both could be served 
as application/xml.


Note: New email address! Please update your address book.

~~ Ushiko-san! Kimi wa doushite, Ushiko-san nan da!! ~~
Laurens Holst, student, university of Utrecht, the Netherlands
Website: www.grauw.nl. Backbase employee; www.backbase.com

Received on Wednesday, 10 December 2008 10:27:09 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:13 UTC