Re: The role of media types for XML content

MURATA Makoto <murata@hokkaido.email.ne.jp> Tue, 14 June 2005 14:47 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 j5EElgCE031389; Tue, 14 Jun 2005 07:47:42 -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 j5EElgs3031388; Tue, 14 Jun 2005 07:47:42 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from mail.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5EElfwF031380 for <ietf-xml-mime@imc.org>; Tue, 14 Jun 2005 07:47:41 -0700 (PDT) (envelope-from murata@hokkaido.email.ne.jp)
Received: from [127.0.0.1] (r113229.ppp.asahi-net.or.jp [210.167.113.229]) by mail.asahi-net.or.jp (Postfix) with ESMTP id 043BB1609B; Tue, 14 Jun 2005 23:47:40 +0900 (JST)
Date: Tue, 14 Jun 2005 23:47:40 +0900
From: MURATA Makoto <murata@hokkaido.email.ne.jp>
To: Mark Baker <distobj@acm.org>
Subject: Re: The role of media types for XML content
Cc: ietf-xml-mime@imc.org
In-Reply-To: <20050613152513.GF20401@markbaker.ca>
References: <20050611154009.266D.MURATA@hokkaido.email.ne.jp> <20050613152513.GF20401@markbaker.ca>
X-Mailer-Plugin: BkASPil for Becky!2 Ver.2.046
Message-Id: <20050614232431.C56F.MURATA@hokkaido.email.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.20.04 [ja]
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>

Mark> >And do you want to specify a 
Mark> > specialized media type when you reference the embedded RNG?
Mark> 
Mark> Ideally, yes, I think that would be valuable for the reasons I gave
Mark> before concerning layering and security.
Mark> 
Mark>  [1] http://www.w3.org/2004/CDF/
Mark>  [2] http://www.markbaker.ca/2004/01/XmlDispatchTest/

You propose to use a specialized media type for a fragment and 
to use a different media type for the entire resource.  It is a very 
interesting idea.  It might help the marriage between media types and 
multi-namespace XML documents.  But I do not think that MIME RFCs or
URI/IRI RFCs bless it (at least now).  Media types have been intended 
as values of the content-type field of MIME.  

You might want to raise this issue in the W3C CDF WG or W3C TAG, and 
you might even want to write an RFC that updates MIME RFCs or URI/IRI
RFCs.

However, unless such significant changes are endorsed, I continue 
to be very reluctant to register a specialized media type for 
the RELAX NG XML syntax.

After all, it is ISO/IEC JTC1/SC34 that is requesting the registartion
of a media type for the RELAX NG compact syntax.  In its last meeting, 
SC34 decided to request this media type, but did not consider a specialized 
media type for the RELAX NG XML syntax.  Since we are talking about 
media types in the standard tree, the media type for the RNG compact
syntax can go to the IESG but that for the RNG XML syntax cannot.

Cheers,

-- 
MURATA Makoto <murata@hokkaido.email.ne.jp>