- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Fri, 06 Jan 2012 22:54:18 +0100
- To: Jarred Nicholls <jarred@sencha.com>
- Cc: public-webapps@w3.org
* Jarred Nicholls wrote: >This is an editor's draft of a spec, it's not a recommendation, so it's >hardly a violation of anything. This is a 2-way street, and often times >it's the spec that needs to change, not the implementation. The point is, >there needs to be a very compelling reason to breach the contract of a >media type's existing spec that would yield inconsistent results from the >rest of the web platform layers, and involve taking away functionality that >is working perfectly fine and can handle all the legit content that's >already out there (as rare as it might be). You have yet to explain how you propose Webkit should behave, and it is rather unclear to me whether the proposed behavior is in line with the existing HTTP, MIME, and JSON specifications. A HTTP response with Content-Type: application/json;charset=iso-8859-15 for instance must not be treated as ISO-8859-15 encoded as there is no charset parameter for the application/json media type, and there is no other reason to treat it as ISO-8859-15, so it's either an error, or you silently ignore the unrecognized parameter. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 6 January 2012 21:54:41 UTC