Re: The role of media types for XML content

Liam Quin <liam@w3.org> Tue, 14 June 2005 23:59 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5ENxrlK077921; Tue, 14 Jun 2005 16:59:53 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j5ENxpgl077920; Tue, 14 Jun 2005 16:59:51 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from homer.w3.org ([128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5ENxoIv077913 for <ietf-xml-mime@imc.org>; Tue, 14 Jun 2005 16:59:50 -0700 (PDT) (envelope-from liam@w3.org)
Received: by homer.w3.org (Postfix, from userid 16040) id B168D4EFA7; Tue, 14 Jun 2005 19:59:47 -0400 (EDT)
Date: Tue, 14 Jun 2005 19:59:47 -0400
From: Liam Quin <liam@w3.org>
To: MURATA Makoto <murata@hokkaido.email.ne.jp>
Cc: ietf-xml-mime@imc.org
Subject: Re: The role of media types for XML content
Message-ID: <20050614235947.GL1742@w3.org>
References: <20050614232431.C56F.MURATA@hokkaido.email.ne.jp> <187486099.20050614174033@w3.org> <20050615075541.6960.MURATA@hokkaido.email.ne.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <20050615075541.6960.MURATA@hokkaido.email.ne.jp>
X-Feet: bare, comfortable. happy and free!
User-Agent: Mutt/1.5.9i
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 Wed, Jun 15, 2005 at 08:06:36AM +0900, MURATA Makoto wrote:
[...]
> I have said that specialized media types for XML-based vocabularies are 
> ad-hoc solutions which do not work for multi-namespace documents
Here I agree with you.  The architectures clearly don't match at all:
Internet media types simply don't work for this sort of document today.
Mozilla Firefox is making this clear -- it supports XHTML with
embedded MathML and SVG for example, in either order, and perhaps
with XHTML and SVG and mathML inside the SVG...

> and that proliferation of specialized media types blocks future use 
> of multi-namespace documents.
I don't think it's blocking future use.  I think in the long term we
have to rethink how multi-namespace XML documents are handled.

But that should not stop us from using the existing infrastructure as
best and as helpfully as we can in the meantime.

I'd like to see a registration for the XML syntax simply because
it's useful today, despite the limitations.

Best,

Liam

-- 
Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/
http://www.holoweb.net/~liam/