RE: [ebxml-msg] Can an MSH send a sync ack and then an async resp onse?

David,

The words you quoted make the coupling as loose as can be.  I really don't
know what your concern is.  In addition, the CPPA and MSG teams have been
working very hard since the work resumed under OASIS to ensure that the two
specifications are consistent on all details.

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" <> on 01/20/2002 07:05:07 PM
To:
Martin W Sachs/Watson/IBM@IBMUS
cc:

Subject:
RE: [ebxml-msg] Can an MSH send a sync ack and then an async

resp
onse?

Marti

I was responding to the comment made originally made by Cliff Collins at
[1]
and confirmed by David Fischer at [2] that changes to the CPP/A spec were
implicity changing the behavior of the MSH spec.

I have gone on record many times before that this tight coupling between
the
specs is wrong and should have been avoided but accept that it is too late
to do anything about it for this version. However if there is a tight
coupling between the two specs we should make it explicit and update the
introduction to reflect this in the way that David Fischer suggests at [3].

Finally Marty, please remember that I an NOT anti-CPA I just want the
relationship between the CPA and the MSH specs to be "right" with less
coupling than currently exists.

No doubt there will be debate around this when we plan what goes into the
next version.

David

================

[1] http://lists.oasis-open.org/archives/ebxml-msg/200201/msg00154.html
[2] http://lists.oasis-open.org/archives/ebxml-msg/200201/msg00158.html
[3] http://lists.oasis-open.org/archives/ebxml-msg/200201/msg00161.html