Re: MPEG asks for MIME review for the MPEG21 file format

Graham Klyne <> Mon, 21 May 2007 09:14 UTC

Received: from (localhost []) by (8.13.5/8.13.5) with ESMTP id l4L9EMIL067596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 02:14:22 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.13.5/8.13.5/Submit) id l4L9EMRh067594; Mon, 21 May 2007 02:14:22 -0700 (MST) (envelope-from
X-Authentication-Warning: majordom set sender to using -f
Received: from ( []) by (8.13.5/8.13.5) with ESMTP id l4L9EKBw067580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <>; Mon, 21 May 2007 02:14:21 -0700 (MST) (envelope-from
Received: from [] ( []) by ( with ESMTP id l4L9DwAr005274; Mon, 21 May 2007 02:13:59 -0700
Message-ID: <>
Date: Mon, 21 May 2007 10:13:58 +0100
From: Graham Klyne <>
User-Agent: Thunderbird (Windows/20070221)
MIME-Version: 1.0
To: Chris Lilley <>
CC: Dave Singer <>, Martin Duerst <>, Anne van Kesteren <>, Larry Masinter <>,,, "'Christian Timmerer (ITEC)'" <>,,
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
References: <> <> <> <p06240821c26e59493bca@[]> <> <p0624084bc26f9de750bc@[]> <002901c798b8$0f9ab4f0$2ed01ed0$@org> <> <> <> <p0624083ec273750809d7@[]> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: for more information
X-Songbird: Clean
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

Chris Lilley wrote:
> On Friday, May 18, 2007, 5:27:52 PM, Dave wrote:
> (I'm snipping the parts already covered by Martin)
> DS> Is a ZIP compressed XML file servable under a +xml MIME type? 
> DS> "encoding='zipped Shift_JIS'"?
> I suspect you mean gzip, which is a compression method; zip is an archive format (often compressed internally).
> If you started with foo.xml in Shift_JIS, the encoding declaration would say just that. If you then make foo.xml.gz the encoding declaration (when decompressed) says exactly the same thing. The fact that is been gzipped is conveyed out of band, in the http headers:
> Content-Encoding: gzip
> There is scope for confusion, since XML uses 'encoding' for 'character encoding' (although that's a big advance on calling it 'charset'). HTTP uses content-encoding. The two uses of the concept 'encoding' occur at different levels in the stack.
> In consequence, using gzip content-encoding is compatible with +xml media types.

For clarification: this would be the case only when a suitable MIME
content-transfer-encoding header is applied, n'est pas?  Otherwise such added
encoding/decoding could be applied lower in the stack and not visible at the
level of the MIME object.


Graham Klyne
For email: