W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2001

Re: text/xml for SOAP is incorrect

From: Jacek Kopecky <jacek@idoox.com>
Date: Wed, 19 Sep 2001 16:10:20 +0200 (CEST)
To: Rich Salz <rsalz@zolera.com>
cc: <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.33.0109191557220.30336-100000@mail.idoox.com>
 Rich,
 as somebody wrote before, transforming content on its way based
solely on its content-type is not very nice. But I agree such
transformations might be harmful as SOAP does indeed forbid some
XML.
 But OTOH SOAP messages are XML so they should be allowed to be
handled as XML when they reach an address with a generic XML
processor.
 I don't think dispatch is a misuse of MIME Content-type
information. I think that creating specific content types for the
purpose of dispatching when better or at least equal other means
of dispatch exist is misuse of the content-type mechanism.

                            Jacek Kopecky

                            Idoox
                            http://www.idoox.com/


P.S: 21st century started on Sep 11, 2001



On Wed, 19 Sep 2001, Rich Salz wrote:

 > >  To explain my position: I am wary of application/soap and
 > > application/soap+xml because it won't usually allow generic
 > > processing as if it were XML.
 >
 > This might be the crux of the matter.  Larry Masinter, e.g., explains
 > why having a separate content type is useful to *avoid* generic
 > processing that might do things (e.g., add a DTD?) that SOAP doesn't
 > like.  SOAP isn't XML; it's a *subset.*
 >
 > I am curious why you think dispatch is misuse.
 > 	/r$
 >
Received on Wednesday, 19 September 2001 10:10:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:03 GMT