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

Re: SVG12: Transfer-Encoding

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Thu, 29 Dec 2005 01:25:04 +0100
To: Chris Lilley <chris@w3.org>
Cc: www-svg@w3.org
Message-ID: <91b6r1lcqirdrmk95mum2dfpjj17i88n7a@hive.bjoern.hoehrmann.de>

* Chris Lilley wrote:
>BH>   From http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/conform.html
>BH> appendix D.4.3
>
>BH> [...]
>BH>   Also, if the SVG is compressed with gzip or deflate, Conforming
>BH>   SVG Servers must indicate this with the "Content-Encoding: gzip"
>BH>   or "Content-Encoding: deflate" headers, as appropriate.
>BH> [...]
>
>BH> The draft is unclear whether it is appropriate for a "SVG Server" to
>BH> indicate this compression through the Transfer-Encoding header, please
>BH> change the draft such that this is clarified.
>
>Bjoern, looking at 3.6 Transfer Codings in the HTTP/1.1 specification
>http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6
>
>We think you may be confusing Transfer-Coding with Content-Encoding,
>described in section 14.11 Content-Encoding
>http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.11
>or possibly even the Content-Transfer-Encoding values of MIME.

I don't, and I could not work out of the thread what the Working Groups
response to my issue is, the latest draft still has weird language like
"i.e.an svgz file"; could you please point out the actual response to my
issue?
-- 
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 Thursday, 29 December 2005 00:24:42 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:32 GMT