ebxml-msg — archive

RE: [ebxml-msg] Messaging Spec v1.092

From: System
To: [email protected]
Date: Mon, 07 Jan 2002 12:14:00 -0000

Sorry to repeat myself: There is already a simple protocol that requires no prenegotiation. It's called Simple Object Access Protocol. All the MSG team has to do is throw out all the ebXML add-ons and you have SOAP and we can all go home. Similarly, if what you want is for some Web service to dictate the IT terms and conditions to anyone who wants to do business with it, all you need is WSDL. If that's the world you want, again, no re-inventing is needed. In other words, there already exists what is needed for SMEs. We could subset ebXML down to the equivalent of SOAP/WSDL or we could decide that our space is really B2B. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com ************************************************************************************* "Burdett, David" <[email protected]> on 01/07/2002 11:39:38 AM To: Martin W Sachs/Watson/IBM@IBMUS, David Fischer <[email protected]> cc: Jacques Durand <[email protected]>, Arvola Chan <[email protected]>, ebXML Msg <[email protected]>, "Ian. C. Jones (E-mail)" <[email protected]> Subject: RE: [ebxml-msg] Messaging Spec v1.092 Marty You said ... >>>MWS:� See my first comment above.� You cannot avoid the runtime database unless you think that you can legislate a single software and middleware configuration that everyone is required to use on pain of ...<<< I agree you cannot legislate, but you should be able to define default parameters for sending a message reliably, for example, which does not require prior negotiation. What we need to do, is make a decision early-on in the development of the next spec on whether we are going to develop: 1. A Negotiation Protocol, which leads to the agreement of a CPA, which then results in the exchange of messages according to the ebMS spec (which is what I think you are suggesting Marty), or 2. A lighter weight spec which allows messages to be sent without prior negotiation but which can reference a negotiated agreement if it exists (which is what I am suggesting). Currently I think there are some who think the first approach is overkill and won't be used by SMEs or the Web Services community, and some who think the second approach won't work. Either a way decision on the way forward has to be made. David