Received: by ns.secondary.com (8.9.3/8.9.3) id AAA15407 for ietf-xml-mime-bks; Wed, 8 Dec 1999 00:04:40 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id AAA15398 for <ietf-xml-mime@imc.org>; Wed, 8 Dec 1999 00:04:38 -0800 (PST)
Received: by mx.fujixerox.co.jp; id RAA17478; Wed, 8 Dec 1999 17:07:42 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma017031; Wed, 8 Dec 99 17:06:37 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id RAA02173; Wed, 8 Dec 1999 17:06:36 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id RAA46980; Wed, 8 Dec 1999 17:07:30 +0900 (JST)
Message-Id: <199912080809.AA03581@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Wed, 08 Dec 1999 17:09:48 +0900
To: James Clark <jjc@jclark.com>
Cc: ietf-xml-mime@imc.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <384B8680.9B02A4A7@jclark.com>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

James Clark wrote:
> 
> The Syntax WG decided that wasn't well-formed. (Fix to E71.)

#I changed the cc field.  Since I am not sure if James is on this ML, 
#I am responding directly.

So, can any external parameter entity be used as an external DTD subset 
and vice versa?

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id AAA15273 for ietf-xml-mime-bks; Tue, 7 Dec 1999 00:12:33 -0800 (PST)
Received: from jclark.com (jclark@jclark.com [192.41.25.183]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id AAA15265 for <ietf-xml-mime@imc.org>; Tue, 7 Dec 1999 00:12:31 -0800 (PST)
Received: from jclark.com (p108-bkkSP13.C.loxinfo.net.th [203.146.65.108]) by jclark.com (8.8.5) id BAA12817; Tue, 7 Dec 1999 01:15:18 -0700 (MST)
X-Authentication-Warning: jclark.com: Host p108-bkkSP13.C.loxinfo.net.th [203.146.65.108] claimed to be jclark.com
Message-ID: <384B8680.9B02A4A7@jclark.com>
Date: Mon, 06 Dec 1999 16:48:48 +0700
From: James Clark <jjc@jclark.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: MURATA Makoto <murata.makoto@fujixerox.co.jp>
CC: ietf-xml-mime@imc.org, Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
References: <199912060905.AA03511@archlute.fujixerox.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> 
> MURATA Makoto wrote:
> > As for external PARAMETER entities, they always parse as external DTD subsets.
> > I now think that we do not need a specialized media type for external parameter
> > entites.
> 
> Having read the XML specification and errara carefully, I withdraw my
> claim.  An external PARAMETER entity does *not* always parse as an external
> DTD subset.
> 
> For example, the following XML document is valid.
> 
> foo.xml
> 
> <?xml version="1.0"?>
> <!DOCTYPE foo SYSTEM "foo.dtd">
> <foo/>
> 
> foo.dtd
> 
> <!ENTITY % foope SYSTEM "foope.mod">
> <!ELEMENT foo %foope;>
> 
> foope.mod
> 
> EMPTY

The Syntax WG decided that wasn't well-formed. (Fix to E71.)

James




Received: by ns.secondary.com (8.9.3/8.9.3) id VAA04574 for ietf-xml-mime-bks; Mon, 6 Dec 1999 21:04:08 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id VAA04568 for <ietf-xml-mime@imc.org>; Mon, 6 Dec 1999 21:04:06 -0800 (PST)
Received: by mx.fujixerox.co.jp; id OAA20472; Tue, 7 Dec 1999 14:06:52 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma020188; Tue, 7 Dec 99 14:06:03 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id OAA09312; Tue, 7 Dec 1999 14:06:03 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id OAA41480; Tue, 7 Dec 1999 14:06:54 +0900 (JST)
Message-Id: <199912070509.AA03545@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Tue, 07 Dec 1999 14:09:14 +0900
To: ietf-xml-mime@imc.org, jjc@jclark.com
Cc: Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <199912060905.AA03511@archlute.fujixerox.co.jp>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> Having read the XML specification and errara carefully, I withdraw my 
> claim.  An external PARAMETER entity does *not* always parse as an external 
> DTD subset.

After reading relevant mail again, I must confess I do not understand.  
Forgive my stupidity.  Parameter entities are just hard ...

I will try to solve this issue in the XML Core WG.

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id BAA08624 for ietf-xml-mime-bks; Mon, 6 Dec 1999 01:00:19 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id BAA08620 for <ietf-xml-mime@imc.org>; Mon, 6 Dec 1999 01:00:17 -0800 (PST)
Received: by mx.fujixerox.co.jp; id SAA11899; Mon, 6 Dec 1999 18:03:01 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma011592; Mon, 6 Dec 99 18:02:09 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id SAA24058; Mon, 6 Dec 1999 18:02:09 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id SAA37770; Mon, 6 Dec 1999 18:02:59 +0900 (JST)
Message-Id: <199912060905.AA03511@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Mon, 06 Dec 1999 18:05:20 +0900
To: ietf-xml-mime@imc.org
Cc: jjc@jclark.com, Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <199912031129.AA03494@archlute.fujixerox.co.jp>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> As for external PARAMETER entities, they always parse as external DTD subsets.  
> I now think that we do not need a specialized media type for external parameter 
> entites.

Having read the XML specification and errara carefully, I withdraw my 
claim.  An external PARAMETER entity does *not* always parse as an external 
DTD subset.


For example, the following XML document is valid.

foo.xml

<?xml version="1.0"?>
<!DOCTYPE foo SYSTEM "foo.dtd">
<foo/>

foo.dtd

<!ENTITY % foope SYSTEM "foope.mod">
<!ELEMENT foo %foope;>

foope.mod

EMPTY

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id RAA12254 for ietf-xml-mime-bks; Sun, 5 Dec 1999 17:24:23 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id RAA12250 for <ietf-xml-mime@imc.org>; Sun, 5 Dec 1999 17:24:21 -0800 (PST)
Received: by mx.fujixerox.co.jp; id KAA17179; Mon, 6 Dec 1999 10:26:37 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma016626; Mon, 6 Dec 99 10:25:31 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id KAA20032; Mon, 6 Dec 1999 10:25:29 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id KAA35564; Mon, 6 Dec 1999 10:26:18 +0900 (JST)
Message-Id: <199912060128.AA03498@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Mon, 06 Dec 1999 10:28:39 +0900
To: ietf-xml-mime@imc.org
Cc: Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <3847D630.301DB09C@w3.org>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

Chris Lilley wrote:
> Instead, they should be labelled as what?

application/xml-dtd

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id GAA03679 for ietf-xml-mime-bks; Fri, 3 Dec 1999 06:37:12 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA03674 for <ietf-xml-mime@imc.org>; Fri, 3 Dec 1999 06:37:10 -0800 (PST)
Received: from w3.org (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id JAA02908; Fri, 3 Dec 1999 09:39:45 -0500
Message-ID: <3847D630.301DB09C@w3.org>
Date: Fri, 03 Dec 1999 15:39:44 +0100
From: Chris Lilley <chris@w3.org>
Organization: W3C
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: MURATA Makoto <murata.makoto@fujixerox.co.jp>
CC: ietf-xml-mime@imc.org, Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
References: <199912031129.AA03494@archlute.fujixerox.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> 
> Chris Lilley wrote:
> > Yes. Even more, though, I care about the converse case; in the case of
> > applications/xml, it should always be the case that it is xml. If it is
> > not, then it is an error, rather than being "a little used case which is
> > actually legal but we dodn't expect people to use it directly".
> 
> We cannot guarantee that the MIME body is really XML since errors will happen.

Sure - but when they hzappen, they should be *errors*. Not, something
that is supposed to happen sometimes.

> But we can elminate the possibility that correctly-labelled data cause
> fatal errors.

Yes, exactly.

> Having heard your argument, I am inclined to introduce a media type
> for external parsed entities. 

Thanks. I am glad that we now agree.

> How do other people feel?
> 
> As for external PARAMETER entities, they always parse as external DTD subsets.
> I now think that we do not need a specialized media type for external parameter
> entites.

Instead, they should be labelled as what?

--
Chris


Received: by ns.secondary.com (8.9.3/8.9.3) id DAA01603 for ietf-xml-mime-bks; Fri, 3 Dec 1999 03:24:21 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id DAA01598 for <ietf-xml-mime@imc.org>; Fri, 3 Dec 1999 03:24:19 -0800 (PST)
Received: by mx.fujixerox.co.jp; id UAA07510; Fri, 3 Dec 1999 20:26:52 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma007466; Fri, 3 Dec 99 20:26:37 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id UAA27994; Fri, 3 Dec 1999 20:26:37 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id UAA27189; Fri, 3 Dec 1999 20:27:20 +0900 (JST)
Message-Id: <199912031129.AA03494@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Fri, 03 Dec 1999 20:29:45 +0900
To: ietf-xml-mime@imc.org
Cc: Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <3847A2AB.C48DC9F1@w3.org>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

Chris Lilley wrote:

> Ok, so even allowing that, if "which program" is an XML parser and you
> feed it a non well formed document, what happens? I would regard
> "mandatory fatal error" as being synonymous with "can't read the
> document"

Right.  But even if the content type is text/xml-external-parsed-entity, 
I cannot read it.  I have no programs that can handle external parsed 
entities directly.  But such programs may be developed tomorrow.

> Yes. Even more, though, I care about the converse case; in the case of
> applications/xml, it should always be the case that it is xml. If it is
> not, then it is an error, rather than being "a little used case which is
> actually legal but we dodn't expect people to use it directly".

We cannot guarantee that the MIME body is really XML since errors will happen.  
But we can elminate the possibility that correctly-labelled data cause 
fatal errors.

> > If some programs that can handle external parsed entities directly (i.e.,
> > without using XML processors for XML documents that reference to them),
> > your point perfectly makes sense. 
> 
> Your point seems to ignore resource discovery, indexing, and other
> routes to finding resources that may not have been intended to be found,
> or found first, or found before other documents in whose context they
> were intended to be used.

I do not ignore such discorvery.  My point is that even if it is lablled as 
an external parsed entity, no existing programs can parse it anyway.  But 
this may change.

Having heard your argument, I am inclined to introduce a media type 
for external parsed entities.  How do other people feel?

As for external PARAMETER entities, they always parse as external DTD subsets.  
I now think that we do not need a specialized media type for external parameter 
entites.

Cheers,

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id CAA28973 for ietf-xml-mime-bks; Fri, 3 Dec 1999 02:57:25 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id CAA28969 for <ietf-xml-mime@imc.org>; Fri, 3 Dec 1999 02:57:23 -0800 (PST)
Received: from w3.org (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id FAA18467; Fri, 3 Dec 1999 05:59:55 -0500
Message-ID: <3847A2AB.C48DC9F1@w3.org>
Date: Fri, 03 Dec 1999 11:59:55 +0100
From: Chris Lilley <chris@w3.org>
Organization: W3C
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: MURATA Makoto <murata.makoto@fujixerox.co.jp>
CC: ietf-xml-mime@imc.org, Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
References: <199912030547.AA03481@archlute.fujixerox.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> 
> Chris Lilley wrote:
> > Yes. My concern is that the question "is this thing, returned as
> > application/xml, actually xml or not" should *not* have multiple
> > answers.
> 
> In general, MIME types can never provide all information about the
> content.  You have to read the MIME body.  The MIME type only tells
> you which program can read the MIME body.

Ok, so even allowing that, if "which program" is an XML parser and you
feed it a non well formed document, what happens? I would regard
"mandatory fatal error" as being synonymous with "can't read the
document"

> In the case of external parsed entities, your point is that application/xml
> or text/xml do not provide enough information, since XML processors cannot
> handle external parsed entities directly.

Sort of.

>  You would lilke the MIME header to
> say "I do not parse as an XML document, but don't throw me away.  I parse as
> an external parsed entity."

Yes. Even more, though, I care about the converse case; in the case of
applications/xml, it should always be the case that it is xml. If it is
not, then it is an error, rather than being "a little used case which is
actually legal but we dodn't expect people to use it directly".

> 
> If some programs that can handle external parsed entities directly (i.e.,
> without using XML processors for XML documents that reference to them),
> your point perfectly makes sense. 

Your point seems to ignore resource discovery, indexing, and other
routes to finding resources that may not have been intended to be found,
or found first, or found before other documents in whose context they
were intended to be used.


> 
> Cheers,
> 
> Makoto
> 
> Fuji Xerox Information Systems
> 
> Tel: +81-44-812-7230   Fax: +81-44-812-7231
> E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id VAA21387 for ietf-xml-mime-bks; Thu, 2 Dec 1999 21:43:05 -0800 (PST)
Received: from mx.fujixerox.co.jp (firewall-user@mx.fujixerox.co.jp [202.32.191.10]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id VAA21383 for <ietf-xml-mime@imc.org>; Thu, 2 Dec 1999 21:43:03 -0800 (PST)
Received: by mx.fujixerox.co.jp; id OAA21865; Fri, 3 Dec 1999 14:45:24 +0900 (JST)
Received: from ns1.fujixerox.co.jp(129.249.118.101) by mx.fujixerox.co.jp via smap (3.2) id xma021708; Fri, 3 Dec 99 14:44:45 +0900
Received: from pumpkin.greens.fxis.fujixerox.co.jp ([131.221.160.133]) by ns1.fujixerox.co.jp (8.9.3/3.7W99040814) with ESMTP id OAA02391; Fri, 3 Dec 1999 14:44:44 +0900 (JST)
Received: from archlute.fujixerox.co.jp (dhcp-1a6-179.greens.fxis.fujixerox.co.jp [131.221.160.179]) by pumpkin.greens.fxis.fujixerox.co.jp (8.9.3/3.7W) with SMTP id OAA25751; Fri, 3 Dec 1999 14:45:27 +0900 (JST)
Message-Id: <199912030547.AA03481@archlute.fujixerox.co.jp>
From: MURATA Makoto <murata.makoto@fujixerox.co.jp>
Date: Fri, 03 Dec 1999 14:47:53 +0900
To: ietf-xml-mime@imc.org
Cc: Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
In-Reply-To: <38455CAD.609F3375@w3.org>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.01
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-xml-mime@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>

Chris Lilley wrote:
> Yes. My concern is that the question "is this thing, returned as
> application/xml, actually xml or not" should *not* have multiple
> answers.

In general, MIME types can never provide all information about the 
content.  You have to read the MIME body.  The MIME type only tells 
you which program can read the MIME body.

In the case of external parsed entities, your point is that application/xml 
or text/xml do not provide enough information, since XML processors cannot 
handle external parsed entities directly.  You would lilke the MIME header to 
say "I do not parse as an XML document, but don't throw me away.  I parse as 
an external parsed entity."

If some programs that can handle external parsed entities directly (i.e., 
without using XML processors for XML documents that reference to them), 
your point perfectly makes sense.  Are there such programs?  
Do people in this ML have such programs?

Cheers,

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata.makoto@fujixerox.co.jp


Received: by ns.secondary.com (8.9.3/8.9.3) id JAA23646 for ietf-xml-mime-bks; Wed, 1 Dec 1999 09:35:04 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA23641 for <ietf-xml-mime@imc.org>; Wed, 1 Dec 1999 09:35:02 -0800 (PST)
Received: from w3.org (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id MAA26124; Wed, 1 Dec 1999 12:36:48 -0500
Message-ID: <38455CAD.609F3375@w3.org>
Date: Wed, 01 Dec 1999 18:36:45 +0100
From: Chris Lilley <chris@w3.org>
Organization: W3C
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Larry Masinter <lmm@acm.org>
CC: MURATA Makoto <murata.makoto@fujixerox.co.jp>, Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, ietf-xml-mime@imc.org, Tsmith@parc.xerox.com, xsl-editors@w3.org
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
References: <NBBBJMDCOOCMJGDGJFJKCEPJIFAA.lmm@acm.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@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>

Larry Masinter wrote:

> The point is that the general question of "this message body, which
> MIME type should I use" can always have multiple answers (since
> application/octet-stream usually applies, for example).

Yes. My concern is that the question "is this thing, returned as
application/xml, actually xml or not" should *not* have multiple
answers.

--
Chris


Received: by ns.secondary.com (8.9.3/8.9.3) id IAA22626 for ietf-xml-mime-bks; Wed, 1 Dec 1999 08:18:59 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by ns.secondary.com (8.9.3/8.9.3) with SMTP id IAA22622 for <ietf-xml-mime@imc.org>; Wed, 1 Dec 1999 08:18:58 -0800 (PST)
Received: from thelma.parc.xerox.com ([13.1.100.28]) by alpha.xerox.com with SMTP id <66026(1)>; Wed, 1 Dec 1999 08:21:24 PST
Received: from mike ([13.0.208.230]) by thelma.parc.xerox.com with SMTP id <97721>; Wed, 1 Dec 1999 08:18:50 PST
From: "Larry Masinter" <lmm@acm.org>
To: "Chris Lilley" <chris@w3.org>, "MURATA Makoto" <murata.makoto@fujixerox.co.jp>
Cc: "Dan Connolly" <connolly@w3.org>, <timbl@w3.org>, <simonstl@simonstl.com>, <ietf-xml-mime@imc.org>, <Tsmith@parc.xerox.com>, <xsl-editors@w3.org>
Subject: RE: External parsed entities (Re: Inconsistency between IETF and W3C...)
Date: Wed, 1 Dec 1999 08:22:14 PST
Message-ID: <NBBBJMDCOOCMJGDGJFJKCEPJIFAA.lmm@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <3844FDB4.1E96DCB9@w3.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-ietf-xml-mime@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>

Chris Lilley wrote:
> > > a) application/xml for xml files. All are required to be well 
> formed,as
> > > per the XML specification, otherwise it is a fatal error.
> > > b) application/xml-epe for external parsed entities which are not
> > > themselves well-formed instances

MURATA Makoto replied:

> > Point of clarification.   I have an external parsed entity.  I use
> > it only as an external parsed entity.  Incidentally, it also parses
> > as an XML document, but this was never intended.  Which one should
> > I use?

Chris Lilley wrote:

> The algorithm is as follows:
> 
> Is it well formed instance
>   Yes: use a)
>   No: use b)

This is not an appropriate algorithm. The choice of the MIME type
to use for a communication depends on the intent of the communication
as well as the nature of the body of the communication. It might
be appropriate to use text/plain, for example, if you intend for
the recipient to read the actual XML rather than interpret it,
and it might be appropriate to use application/octet-stream if you
want no interpretation at all.

The point is that the general question of "this message body, which
MIME type should I use" can always have multiple answers (since
application/octet-stream usually applies, for example).

The XHTML group got caught up in this, since there are some XHTML
bodies for which 'text/html' are appropriate and others that are not.
Don't try to construct a functional one-to-one mapping from 
message body content to MIME type, because you can and will get
multiple values.




Received: by ns.secondary.com (8.9.3/8.9.3) id CAA15467 for ietf-xml-mime-bks; Wed, 1 Dec 1999 02:49:17 -0800 (PST)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id CAA15463 for <ietf-xml-mime@imc.org>; Wed, 1 Dec 1999 02:49:16 -0800 (PST)
Received: from w3.org (IDENT:root@localhost [127.0.0.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id FAA19314; Wed, 1 Dec 1999 05:51:33 -0500
Message-ID: <3844FDB4.1E96DCB9@w3.org>
Date: Wed, 01 Dec 1999 11:51:32 +0100
From: Chris Lilley <chris@w3.org>
Organization: W3C
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: MURATA Makoto <murata.makoto@fujixerox.co.jp>
CC: Dan Connolly <connolly@w3.org>, timbl@w3.org, simonstl@simonstl.com, ietf-xml-mime@imc.org, Tsmith@parc.xerox.com, xsl-editors@w3.org, masinter@parc.xerox.com
Subject: Re: External parsed entities (Re: Inconsistency between IETF and W3C...)
References: <199912010159.AA03439@archlute.fujixerox.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@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>

MURATA Makoto wrote:
> 
> Chris Lilley wrote:
> > a) application/xml for xml files. All are required to be well formed,as
> > per the XML specification, otherwise it is a fatal error.
> > b) application/xml-epe for external parsed entities which are not
> > themselves well-formed instances
> 
> Point of clarification.   I have an external parsed entity.  I use
> it only as an external parsed entity.  Incidentally, it also parses
> as an XML document, but this was never intended.  Which one should
> I use?

The algorithm is as follows:

Is it well formed instance
  Yes: use a)
  No: use b)

This does not strike me as being especially difficult or complex.

--
Chris