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

Chris Lilley <> Sun, 20 May 2007 23:02 UTC

Received: from (localhost []) by (8.13.5/8.13.5) with ESMTP id l4KN2bHW042843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 May 2007 16:02:37 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.13.5/8.13.5/Submit) id l4KN2bMP042842; Sun, 20 May 2007 16:02:37 -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 l4KN2U2B042680 for <>; Sun, 20 May 2007 16:02:30 -0700 (MST) (envelope-from
Received: from [] (localhost []) by (Postfix) with ESMTP id DB1F94F016; Sun, 20 May 2007 19:02:12 -0400 (EDT)
Date: Sun, 20 May 2007 02:24:11 +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 Friday, May 18, 2007, 7:54:32 AM, Anne wrote:

AvK> On Fri, 18 May 2007 03:12:09 +0200, Chris Lilley <>; wrote:
>> The successor to RFC 3023 needs to indicate that binary XML which is  
>> presented as a new encoding (in the xml sense) can use +xml, while other  
>> binary forms cannot.

AvK> You wouldn't be able to still parse the retrieved resource in that case
AvK> with a generic XML parser. Wasn't that the whole idea of +xml?

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


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