• To: <xml-dev@l...>
• Subject: RE: What does SOAP really add?
• From: "Julian Reschke" <julian.reschke@g...>
• Date: Tue, 23 Apr 2002 08:18:51 +0200
• Importance: Normal
• In-reply-to: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F05649@r...>

> From: Joshua Allen [mailto:joshuaa@m...]
> Sent: Tuesday, April 23, 2002 5:27 AM
> To: Adam Turoff; Dave Winer
> Cc: Edd Dumbill; xml-dev@l...
> Subject: RE:  What does SOAP really add?
>
>
> > The "SOAP brings interop for free" argument is simply a straw man.
> > Especially when it necessarily prevents interop with a whole
> > class of tools (XSLT processors for one).
>
> BTW, this is absolutely and completely wrong.  SOAP messages are XML,
> and therefore are able to be transformed with XSLT just like any other
> XML.  Many people have done this (and yes, I have too).  In fact, it is

But data exposed using SOAP usually cannot retrieved using GET, and
therefore isn't easily accessible using XSLT's document() function.

> only logical that SOAP messages can be more reliably transformed to get
> *some* information than a more generic XML format.  The idea that XSLT
> against SOAP can't be done flies in the face of common sense.  And the
> idea that writing XSLT against Joe's-random-XML is more scalable or
> productive than against SOAP also flies in the face of common sense.

• Follow-Ups:
  • RE: What does SOAP really add?
    • From: Bill de hÓra <dehora@e...>

• References:
  • RE: What does SOAP really add?
    • From: "Joshua Allen" <joshuaa@m...>

• Prev by Date: RE: What does SOAP really add?
• Next by Date: RE: What does SOAP really add?
• Previous by thread: Re: What does SOAP really add?
• Next by thread: RE: What does SOAP really add?
• Index(es):
  • Date
  • Thread