xml-dev - RE: SOAP, plague, love

["John D. Gwinner" <JGwinner@dazsi.com>]

> -----Original Message-----
> From: owner-xml-dev@xml.org [mailto:owner-xml-dev@xml.org]On Behalf Of
> Dick Brooks (E)
> Sent: Sunday, May 07, 2000 2:35 PM
> To: Jonathan Borden; xml-dev@xml.org
> Subject: RE: SOAP, plague, love
>
>
> Jonathan,
>
> I agree with your assessment. It points out that SOAP by itself is
> inadequate for E-Commerce applications and must be augmented by another
> technology (XMTP is a great example and it's a fine peice of work). You
> really should consider sending XMTP to W3C as a working draft. FYI - I
> referenced XMTP in the ebXML packaging spec as a possible solution to create
> a pure XML packaging solution.

Dick, I'm glad that it is "Inadequate" by your measure, because if it was,
some of the E-Commerce that we are doing would be much more difficult.  SOAP
is just a way to get understandable messages back and forth (from
*anything*) - what you do with the message that we craft is up to each of us.
If everything that you consider important was built into SOAP from the
beginning, it would make implementation of somethings harder, which in our
E-Commerce case we do not want.  It wouldn't be "Simple".

It's like saying that ethernet cards are inadequate for your E-Commerce
because they don't have encryption built in.  They shouldn't - that piece goes
somewhere else.  If you want authentication, encryption, and non-repudiation,
can't you just build this into a payload?  (Maybe you can't, this is an honest
question).

Why are we discussing this here instead of on the SOAP list?

		== John ==


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************