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

Martin Duerst <duerst@it.aoyama.ac.jp> Mon, 21 May 2007 11:03 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 l4LB3vPB099340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 04:03:58 -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 l4LB3vUw099339; Mon, 21 May 2007 04:03:57 -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 scmailgw1.scop.aoyama.ac.jp (scmailgw1.scop.aoyama.ac.jp [133.2.251.194]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4LB3r4e099312 for <ietf-xml-mime@imc.org>; Mon, 21 May 2007 04:03:55 -0700 (MST) (envelope-from duerst@it.aoyama.ac.jp)
Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id l4LB3qIB020845 for <ietf-xml-mime@imc.org>; Mon, 21 May 2007 20:03:52 +0900 (JST)
Received: from (133.2.206.133) by scmse2.scbb.aoyama.ac.jp via smtp id 0bd8_f5e6bb02_078a_11dc_85f4_0014221f2a2d; Mon, 21 May 2007 20:03:52 +0900
X-AuthUser: duerst@it.aoyama.ac.jp
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:41772) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <SA707B> for <ietf-xml-mime@imc.org> from <duerst@it.aoyama.ac.jp>; Mon, 21 May 2007 20:02:18 +0900
Message-Id: <6.0.0.20.2.20070521192805.04ef2100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Mon, 21 May 2007 19:30:23 +0900
To: "Anne van Kesteren" <annevk@opera.com>, "Chris Lilley" <chris@w3.org>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
Cc: Larry Masinter <LMM@acm.org>, "'Graham Klyne'" <GK@ninebynine.org>, ietf-types@alvestrand.no, ietf-xml-mime@imc.org, ietf-liaisons@ietf.org, "'Christian Timmerer (ITEC)'" <christian.timmerer@itec.uni-klu.ac.at>, "'Dave Singer'" <singer@apple.com>
In-Reply-To: <op.tsn5fnb864w2qv@annevk.hotspot.sfr.fr>
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> <179633441.20070520022411@w3.org> <op.tsn5fnb864w2qv@annevk.hotspot.sfr.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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>

At 17:48 07/05/21, Anne van Kesteren wrote:

>"Efficient XML" seems to be more on the content encoding level than the  
>character encoding level to me. (Assuming you meant charset="blah" as  
>opposed to encoding="blah" above given your examples of UTF-8 and  
>UTF-16...)

That's not only you. It seems so to virtually everybody.
That's no surprise, because it IS at that level.
The trick is that it can be handled as if it were a character
encoding. That's where the language lawyers come in.

Regards,   Martin.


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp