SOAP and ebXML

I noticed the article on XMLHACK about Jon Bosak's presentation at XML
2000 -- see http://xmlhack.com/read.php?item=935

" the distinction between SOAP, the technology of choice for simple
services, and ebXML, required to perform more mission-critical transactions,
was made clear by Bosak.

The final architecture of Bosak's vision is then:
-XML as a core technology
-UDDI to find the services we need
-SOAP to perform the simple ones
-ebXML for the most complex ones "

I'm wondering if  participants here agree with the notion that SOAP is for
simple services and ebXML for mission critical transactions.  If so, what
about ebXML makes it more suitable for mission critical work?  (Transaction
processing support, maybe?)

What about the objectives of the XML Protocols activity? I don't see
anything in the Activity Statement or Charter one way or the other that
would reflect on this issue.

I realize that this opens up a can of worms, but it's an issue that I'm
sincerely trying to make sense out of.

Received on Wednesday, 6 December 2000 19:14:45 UTC