- From: Eric Seidel <eseidel@apple.com>
- Date: Wed, 28 Dec 2005 15:44:45 -0600
- To: www-svg@w3.org
== This message seems to have died somewhere in transit, resending. == Greetings, It is my recommendation that section 1.4 when talking about svgz should make reference to Appendix D.4.3 which informs the implementor that svgz content MUST be sent with the correct Content-Encoding headers. In fact, even stronger, I would recommend that either Appendix D.4.3 or Section 1.4 specifically state that sending content w/o the proper headers is in error, and should be ignored by the user agent. FireFox and Safari implementors have already had issues in this regard while implementing svgz support for SVG 1.1. Furthermore, I will state for consideration, that the "svgz" file type, in the local-file case is rather odd. As its existence requires conforming xml user agents to include gzip detection and decompression ability. This same requirement is not made by HTML or any other xml standard (that I am aware of). Other xml file formats I have seen have used .foo.gz instead of .fooz as SVG does. Neither FireFox nor Safari currently support local svgz files, however we both eventually plan to do so as it is required by the 1.1 spec. Thanks, Eric
Received on Wednesday, 28 December 2005 21:44:53 UTC