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

Martin Duerst <duerst@it.aoyama.ac.jp> Fri, 18 May 2007 10:28 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 l4IASUUK008956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 May 2007 03:28:30 -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 l4IASUAi008955; Fri, 18 May 2007 03:28:30 -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 l4IASRMe008947 for <ietf-xml-mime@imc.org>; Fri, 18 May 2007 03:28:28 -0700 (MST) (envelope-from duerst@it.aoyama.ac.jp)
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id l4IASQNd029493 for <ietf-xml-mime@imc.org>; Fri, 18 May 2007 19:28:26 +0900 (JST)
Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp id 41b1_83501a46_052a_11dc_9330_0014221fa3c9; Fri, 18 May 2007 19:28:25 +0900
X-AuthUser: duerst@it.aoyama.ac.jp
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:55149) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <SA4B38> for <ietf-xml-mime@imc.org> from <duerst@it.aoyama.ac.jp>; Fri, 18 May 2007 19:26:54 +0900
Message-Id: <6.0.0.20.2.20070518152931.08d71da0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Fri, 18 May 2007 15:31:02 +0900
To: "Larry Masinter" <LMM@acm.org>, "'Dave Singer'" <singer@apple.com>, "'Graham Klyne'" <GK@ninebynine.org>
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: RE: MPEG asks for MIME review for the MPEG21 file format
Cc: ietf-xml-mime@imc.org, ietf-liaisons@ietf.org, "'Christian Timmerer (ITEC)'" <christian.timmerer@itec.uni-klu.ac.at>, ietf-types@alvestrand.no
In-Reply-To: <002901c798b8$0f9ab4f0$2ed01ed0$@org>
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>
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>

I fully agree with Larry's interpretation of RFC 3023 and his
comment on this proposal. "is XML" and "contains XML" are
two different things, and the "+xml" suffix is only for
the "is XML" case.

Regards,    Martin.

At 04:17 07/05/18, Larry Masinter wrote:
>I believe the +xml suffix should be reserved for media types whose content
>can be
>parsed without any preprocessing by a generic XML parser. A reply
>from David Singer indicated that the proposed MPEG 21file format is "binary
>and contains within it either XML text or BiM-encoded XML (like a ZIP
>archive
>with an XML document as the main document.)"
>
>In that case, the use of +xml would (IMO) be inappropriate.
>
>I thought this was clear form RFC 3023, but perhaps not.
>
>Larry


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