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 10:08:01 +0200 (CEST)
To: Mark Baker <distobj@acm.org>
cc: Henrik Frystyk Nielsen <henrikn@microsoft.com>, Mark Nottingham <mnot@mnot.net>, christopher ferris <chris.ferris@Sun.COM>, <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.33.0109190958030.30336-100000@mail.idoox.com>
 I don't see this stop-gap as necessary, see my argument with
dispatching on access URLs and not on content-type or even
 I see dispatching as very tied with addressing - and which of
the three [access URL, content-type, XML namespace] is the thing
we use for addressing?
 I can't envision a situation where you would have a bunch of XML
documents along with their MIME content-type information but
without any addressing information. And if somebody designs
precisely such an application - well, we aren't able to keep
people from shooting themselves in the foot.
 So I'd give people two options - either give your SOAP
application its access URL or make your general XML processor
know XML namespaces.
 I don't see why we should change MIME dispatchers for special
handling of XML.

                            Jacek Kopecky


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

On Tue, 18 Sep 2001, Mark Baker wrote:

 > > Right, but then why isn't application/xml sufficient?
 > I'd be perfectly happy with application/xml, if we could
 > guarantee that practically all XML processors at the other
 > end of the pipe grokked (and dispatched on) namespaces.
 > I don't think we're there yet, but I'd like to be proven
 > wrong.  I've said all along that application/soap+xml is
 > only a stop-gap until application/xml can be used.
 > MB
Received on Wednesday, 19 September 2001 04:08:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:15 UTC