It does not matter that SOAP is not committee approved. SOAP is here
already, in use, and here to say. I'd rather use a standard developed,
in-use, and tested by real-world businesses - i.e. I'd rather have the
cart pull the horse than the other way around.
It seems to me that ebXML is just a committee trying to develop a
business utopia. Point me in the right direction: give me websites of
code examples that show how this will fit in with HTTP, DOM, DCOM, COM,
CORBA, Java, etc. Please don't point me to anymore utopian white papers
about ebXML.
-RD
Rachel Foerster wrote:
>
> Furthermore, the ebXML message services specification -- which will be
> approved at the Tokyo ebXML meeting the week of 11/6, offers far more
> fiunctionality and capability than SOAP....which isn't even yet a W3C
> Candidate Recommendation let alone an approved Recommendation.
>
> Rachel
> ----------------------------------------------------------------------
> ---------
>
--
Richard Druckenmiller
[EMAIL PROTECTED]
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
