W3C home > Mailing lists > Public > www-svg@w3.org > December 2004

Re: SVG12: image/svg+xml gzip requirements

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 08 Dec 2004 18:38:43 +0100
To: Thomas DeWeese <Thomas.DeWeese@Kodak.com>
Cc: www-svg@w3.org, ietf-types@iana.org
Message-ID: <41b92f4f.453469968@smtp.bjoern.hoehrmann.de>

* Thomas DeWeese wrote:
>   Please don't rewrite the TAG finding.  The TAG indicates that
>User agents should 'notify' the user of the problem.  It does not say
>that these documents must be rejected.

Appendix F.1 of the SVG 1.1 Recommendation requires that rendering must
stop after a fatal error as defined in the XML 1.0 Recommendation has
been encountered, which in case of the relevant documents means after
reading the very first octet of the binary resource. The TAG finding,
even if it disagrees with the SVG 1.1 Recommendation, has no authority
to override this conformance requirement.

>   I might also point out 4.2 where the last paragraph says:
>     Representation providers SHOULD NOT in general specify the
>     character encoding for XML data in protocol headers since the data
>     is self-describing.
>   Which would seem to support not including the character encoding
>in the SVG mime type.

It does not. It says you should not use the charset parameter, it
does not say XML MIME Type registrations should define inconsistent
processing rules for XML resources that use the charset parameter.
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 Wednesday, 8 December 2004 17:39:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:04 UTC