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

Chris Lilley <> Mon, 21 May 2007 15:24 UTC

Received: from (localhost []) by (8.13.5/8.13.5) with ESMTP id l4LFOw5U076163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 08:24:58 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.13.5/8.13.5/Submit) id l4LFOwDq076162; Mon, 21 May 2007 08:24:58 -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 l4LFOujt076156 for <>; Mon, 21 May 2007 08:24:57 -0700 (MST) (envelope-from
Received: from [] (localhost []) by (Postfix) with ESMTP id BED204F056; Mon, 21 May 2007 11:24:52 -0400 (EDT)
Date: Mon, 21 May 2007 17:24:33 +0200
From: Chris Lilley <>
X-Mailer: The Bat! (v3.95.6) Home
Reply-To: Chris Lilley <>
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <>
To: "Anne van Kesteren" <>
Cc: "Larry Masinter" <>, "'Dave Singer'" <>, "'Graham Klyne'" <>, <>, "'Christian Timmerer (ITEC)'" <>, <>, <>
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
In-Reply-To: <>
References: <> <> <> <p06240821c26e59493bca@[]> <> <p0624084bc26f9de750bc@[]> <002901c798b8$0f9ab4f0$2ed01ed0$@org> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

On Monday, May 21, 2007, 10:48:49 AM, Anne wrote:

AvK> On Sun, 20 May 2007 02:24:11 +0200, Chris Lilley <>; wrote:
>> Swapping your sentences around: yes, the whole idea of +xml is that you  
>> know you can use a generic XML parser.

>> Something that might or might not be xml, therefore should not use +xml.

>> An XML parser must understand UTF-8 and UTF-16 and may understand other  
>> encodings. I gather that the Efficient XML folks will declare a new  
>> encoding, and parsers which don't know it will not parse it. Same is if  
>> I said the encoding was

>> encoding="i-bet-you-never-heard-of-this-one"

AvK> "Efficient XML" seems to be more on the content encoding level than the
AvK> character encoding level to me.

I would have thought so too, but Liam Quin tells me this is not the current thinking in the EXI WG.

AvK (Assuming you meant charset="blah" as
AvK> opposed to encoding="blah" above given your examples of UTF-8 and  
AvK> UTF-16...)

No, I meant exactly what I typed.

 Chris Lilley          
 Interaction Domain Leader
 Co-Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG