Well, at least they spelled ebXML correctly....

["William J. Kammerer" <wkammerer@foresightcorp.com>]

Check out 'Let's See If "Coopetition" Works For Web Services,' By Jason
Levitt (April 2, 2001) in InformationWeek, at
http://www.informationweek.com/author/internet.htm.

"SOAP, UDDI, WSDL, ... aren't open standards. They're draft
specifications of technologies that are owned by IBM, Microsoft, and
others."

"The problem here is that ebXML overlaps quite a bit with Web Services
functionality. EbXML has its own registry and other infrastructure
components that parallel Web Services, but are different. The only
bright spot in the ebXML evolution, which will culminate when the ebXML
1.0 specification is released in May, is that the ebXML standards
organization has agreed to support a version of SOAP, the Web Services
messaging protocol. (Actually, a World Wide Web Consortium draft
specification called "SOAP with attachments," which adds the capability
of attaching binary, non-XML documents to a SOAP message, was needed to
replace the messaging transport in ebXML). This will allow basic
interoperability between Web Services and ebXML, should both of them
become successful, but doesn't resolve the fact that they're trying to
achieve similar goals in different ways."

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"accelerating time-to-trade"