ebxml-msg — archive

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

From: System
To: [email protected]
Date: Fri, 04 Jan 2002 23:42:00 -0000

Jacques, I agree with you that the MSG spec is NOT tightly coupled to the CPA. The words you quote are exactly the words that eliminate dependence on the CPA. However, information that can be encoded in the CPA is still needed to enable to partners to exchange messages. Without a CPA, that information is entered separately into each partner's system via a GUI tool. That's as loosely coupled as you can ask for. ************************************************************************************* 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 ************************************************************************************* Jacques Durand <[email protected]> on 01/04/2002 07:21:24 PM To: "'David Fischer'" <[email protected]>, Arvola Chan <[email protected]>, ebXML Msg <[email protected]>, "Ian. C. Jones (E-mail)" <[email protected]> cc: Subject: RE: [ebxml-msg] Messaging Spec v1.092 David: No problem with V2.0, agree that�"1.1" is misleading with regard to backward compatibility. The adoption of an (early)�incompatible new version�can still be helped if the upgrade is such that it allows�for an upgraded MSH implementation to handle in parallel the two "incompatible" versions during a transition period, (in case running two different�MSH instances on same site is problematic). That is quite possible using version # in header, if the incompatibility is mostly�in the�packaging format, with no conflicting MSH behavior . This would permit a smooth transition, not needing all trading partners to upgrade at same time. "Tightly" integrated with CPA?�Just reading V1.092 I�did� not have this impression: "...However, the method used by a specific implementation of the MSH does not mandate the existence of a discrete instance of a CPA. ...�This specification does not prescribe how the CPA information is derived, stored, or used: it only states specific information items must be available for the MSH to achieve successful operations." My understanding is that some (actually small) subset of CPA needs be available in some form. That still sounds like loose coupling to me... Regards, jacques Durand