Re: Microsoft Refuses to support ebXML
Jim Murphy <[email protected]> Mon, 17 Feb 2003 13:49:21 -0500
| Newsgroups | gmane.comp.windows.devel.soap.general |
|---|---|
| Organization | Ironring Software |
| Message-ID | <000201c2d6b5$4cb462b0$bb2aa8c0@Manta> |
> -----Original Message----- > From: Discussion of implementing SOAP applications today > [mailto:[email protected]] On Behalf Of Anne Thomas Manes > Sent: Monday, February 17, 2003 10:42 AM > To: [email protected] > Subject: Re: [SOAP] Microsoft Refuses to support ebXML > I'm not sure that I understand your comment regarding OASIS. Perhaps you > view OASIS as the primary backer of ebXML and hence they don't back > SOAP/WSDL/UDDI? That's clearly a misperception -- especially since UDDI is > at OASIS. > In general, the protocol-level and basic XML technologies get standardized > at W3C, and the application-level and extended services level stuff gets > standardized at OASIS. There are a few exceptions: I'd have expected > Choreography to happen at OASIS rather than W3C. That is exactly the (mis)perception I have. Delineating the protocol specs vs. application is helpful but with your noted exceptions I wouldn't have come to that conclusion on my own. It seems like a more significant philosophical rift to me: 1. ebXML: all-or-nothing vs. GXA: layered 2. ebXML: top down GXA: bottom up Clearly OASIS is "the primary backer of ebXML" - other than UN/CEFACT who else does - the industry adoption list looks somewhat limited [1]? [1] - http://www.ebxml.org/endorsements.htm Kind Regards, Jim You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other DevelopMentor lists at http://discuss.develop.com.