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

Re: SVG 1.2 Comment: image/svg+xml;charset=""

From: Chris Lilley <chris@w3.org>
Date: Wed, 24 Nov 2004 16:00:27 +0100
Message-ID: <16087233.20041124160027@w3.org>
To: Anne van Kesteren <fora@annevankesteren.nl>
Cc: Robin Berjon <robin.berjon@expway.fr>, Bjoern Hoehrmann <derhoermi@gmx.net>, <www-svg@w3.org>

On Wednesday, November 24, 2004, 3:53:36 PM, Anne wrote:


AvK> Robin Berjon wrote:
>> 
>> Bjoern Hoehrmann wrote:
>> 
>>> * Robin Berjon wrote:
>>>
>>>> Those are the precise people we do *not* want to put the burden of 
>>>> resolving this on. They will have to deal with uncooperative server
>>>> administrators that'll refuse to let them control the character 
>>>> encoding because all they (think they) know about character encodings
>>>> is that you have to provide one to avoid certain XSS attacks.
>>>
>>> Are you saying that the proposed registration would avoid that, i.e.,
>>> that http://www.bjoernsworld.de/temp/utf8-or-iso-8859-1.svg must be
>>> considered UTF-8 encoded by all implementations?
>> 
>> Ideally yes. It is, after all, what the XML document says.

AvK> However, that's not how HTTP works.

Could you expand on that? How does it work, in your opinion, that is
germane to this discussion?

HTTP works by doing what the media type registration says, which is what
is under discussion here.


-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Wednesday, 24 November 2004 15:00:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:52 UTC