IETF Logo Mail Archive

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

"Anne van Kesteren" <annevk@opera.com> Mon, 21 May 2007 08:49 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 l4L8nFA7060432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 01:49:16 -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 l4L8nFe7060431; Mon, 21 May 2007 01:49:15 -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 sam.opera.com (sam.opera.com [213.236.208.81]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4L8nDH8060390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-xml-mime@imc.org>; Mon, 21 May 2007 01:49:15 -0700 (MST) (envelope-from annevk@opera.com)
Received: from annevk.hotspot.sfr.fr (pat-tdc.opera.com [213.236.208.22]) (authenticated bits=0) by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l4L8mnev011423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 May 2007 08:48:50 GMT
Date: Mon, 21 May 2007 10:48:49 +0200
To: Chris Lilley <chris@w3.org>
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
From: Anne van Kesteren <annevk@opera.com>
Organization: Opera Software
Cc: Larry Masinter <LMM@acm.org>, '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
Content-Type: text/plain; format="flowed"; delsp="yes"; charset="utf-8"
MIME-Version: 1.0
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>
Message-ID: <op.tsn5fnb864w2qv@annevk.hotspot.sfr.fr>
In-Reply-To: <179633441.20070520022411@w3.org>
User-Agent: Opera Mail/9.20 (Win32)
X-Virus-Scanned: ClamAV 0.90.1/3273/Mon May 21 05:31:50 2007 on sam.opera.com
X-Virus-Status: Clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-Printable to 8bit by balder-227.proper.com id l4L8nFH7060423
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 Sun, 20 May 2007 02:24:11 +0200, Chris Lilley <chris@w3.org> 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"

"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...)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

v2.23.0 | Report a Bug | By Email