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

"C. M. Sperberg-McQueen" <cmsmcq@acm.org> Fri, 18 May 2007 13:27 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4IDRECi067225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 May 2007 06:27:14 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l4IDREZH067224; Fri, 18 May 2007 06:27:14 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4IDRCpP067217 for <ietf-xml-mime@imc.org>; Fri, 18 May 2007 06:27:12 -0700 (MST) (envelope-from cmsmcq@acm.org)
Received: from [IPv6???1] (homer.w3.org [128.30.52.30]) by homer.w3.org (Postfix) with ESMTP id 6E2144EEFD; Fri, 18 May 2007 09:26:58 -0400 (EDT)
In-Reply-To: <6.0.0.20.2.20070518194309.08d1ee50@localhost>
References: <E94B6002-BAE6-4D08-98A3-89E8D46504F3@stewe.org> <AE61ED01-9B91-4D5D-8654-AF8DD1B86EA2@stewe.org> <464814BE.4090208@ninebynine.org> <p06240821c26e59493bca@[17.202.35.52]> <4649B0BA.4040002@ninebynine.org> <p0624084bc26f9de750bc@[17.202.35.52]> <002901c798b8$0f9ab4f0$2ed01ed0$@org> <892351513.20070518031209@w3.org> <op.tsidc6yf64w2qv@annevk.hotspot.sfr.fr> <6.0.0.20.2.20070518194309.08d1ee50@localhost>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <755A58D4-90BE-4337-981F-9739B58FB8D6@acm.org>
Cc: "C. M. Sperberg-McQueen" <cmsmcq@acm.org>, "Anne van Kesteren" <annevk@opera.com>, "Chris Lilley" <chris@w3.org>, "Larry Masinter" <LMM@acm.org>, ned.freed@mrochek.com, "'Dave Singer'" <singer@apple.com>, "'Graham Klyne'" <GK@ninebynine.org>, ietf-liaisons@ietf.org, "'Christian Timmerer (ITEC)'" <christian.timmerer@itec.uni-klu.ac.at>, ietf-types@alvestrand.no, ietf-xml-mime@imc.org
From: "C. M. Sperberg-McQueen" <cmsmcq@acm.org>
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
Date: Fri, 18 May 2007 15:27:05 +0200
To: Martin Duerst <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.752.2)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l4IDRDpP067219
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On 18 May 2007, at 13:07 , Martin Duerst wrote:
>
> At 14:54 07/05/18, Anne van Kesteren wrote:
>> ...
>> You wouldn't be able to still parse the retrieved resource in that  
>> case
>> with a generic XML parser. Wasn't that the whole idea of +xml?
>
> Well, yes, but the language lawyers argue as follows:
>
> Except for UTF-8 and UTF-16, there is absolutely no guarantee
> that an XML parser accepts any encoding whatsoever. There is
> a lot of XML out there with e.g.
>    <?xml version='1.0' encoding='Shift_JIS'?>
> but no XML parser is required to grok that (although many do).
> So you can view binary XML just as an extremely weird and special
> character encoding. I personally wish it wouldn't be necessary,
> but there are people who claim that it is, for whatever it's worth.

First, I agree with Martin's analysis, or rather with his
resumé of the language lawyers' view.

Second, I wonder: Martin, can you clarify something?  When you
say "I personally wish it wouldn't be necessary", do you mean
"I personally wish that it were proven and accepted that the
socalled 'binary XML' format(s) were unnecessary"?  or do you
mean "I personally wish that the language lawyers would not be
such idiots, and that it were generally accepted that this
particular view of "character encoding", and this particular
use of the XML encoding declaration, is unnecessary, and that
binary XML formats should not need to pretend to be
"character encodings" in the sense of the XML specification?

Michael