Re: Registration of media typeimage/svg+xml

Julian Reschke <> Fri, 19 November 2010 09:42 UTC

Received: from (localhost []) by (8.14.4/8.14.3) with ESMTP id oAJ9gRqt021854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Nov 2010 02:42:27 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.14.4/8.13.5/Submit) id oAJ9gRmq021853; Fri, 19 Nov 2010 02:42:27 -0700 (MST) (envelope-from
X-Authentication-Warning: majordom set sender to using -f
Received: from ( []) by (8.14.4/8.14.3) with SMTP id oAJ9gPvo021848 for <>; Fri, 19 Nov 2010 02:42:26 -0700 (MST) (envelope-from
Received: (qmail invoked by alias); 19 Nov 2010 09:42:23 -0000
Received: from (EHLO []) [] by (mp009) with SMTP; 19 Nov 2010 10:42:23 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+cVQxMqkOcDXmkFebiTN05qwKabaDt3GCfbeu+ze HRirKq+pyr/Mb5
Message-ID: <>
Date: Fri, 19 Nov 2010 10:42:14 +0100
From: Julian Reschke <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Lilley <>
CC: Ned Freed <>,,, Alexey Melnikov <>, Maciej Stachowiak <>
Subject: Re: Registration of media typeimage/svg+xml
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

On 18.11.2010 23:22, Chris Lilley wrote:
> ...
> In that case I can remove the section.
> ...

Thanks for that!

> ...
> Julian, does that satisfy your concern as well?
> ...

Partly. As Björn already said, the svgz file extension still is 
mentioned in a way that could be understood to say that the gzipped 
variant *is* the same mime type.

I think we have now agree that it is not, right?

One way to address this would be to mention it elsewhere, stating this 
is just a convention, and how it needs to be handled. I do believe that 
the registration template is not the best place for it, though (maybe a 
WG Note that establishes the filename convention and shows how to serve 
that stuff over HTTP?).

Of course an alternative is to make it a *separate* media type. I 
believe that Maciej Stachowiak said at the Lyon TPAC that Safari on 
MacOS internally uses media types, and that they actually had to add a 
workaround so that they could map both *.svg and *.svgz to the same 
(hopefully I got that right; cc'ing him). That's exactly the kind of 
problem I'm hoping to avoid.

Best regards, Julian