- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Sat, 17 Dec 2005 00:35:12 +0100
- To: Chris Lilley <chris@w3.org>
- Cc: ietf-types@iana.org, www-tag@w3.org
* Chris Lilley wrote: >With RFC 3023 as it stands, however, it has all the problems that the >TAG finding notes regarding inconsistency of dual metadata; in >consequence it was felt safer to omit the parameter. As RFC 3066 >carefully describes a consistent handling of +xml media types where a >charset is omitted, this was not felt to be a problem. The idea of RFC 3023's +xml convention is that applications can consider resources labeled with such types XML and process them in a generic way even if the specific media type is not known to the application. This is not guranteed if the rules for detecing the character encoding of image/ svg+xml resources are different from those for application/xml resources or other non-text/* +xml types. If you want to say that the charset parameter is better not used for image/svg+xml resouces that's fine, defining or implying different encoding detection requirements for image/svg+xml resouces than what we have for application/xml is not, as that would make the types incompatible. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 16 December 2005 23:35:01 UTC