It isn't new functionality at all. It's just that the MSG team refuses to
write down anything about what has to go on between the MSH and the
software above it. Starting and ending conversations is the job of the
software that understands the flow within a conversation. Because the MSH
has undertaken to keep the messages within a conversation in order, it has
to be notified of the beginning and ends of conversation. Some unnamed
persons believe that any reasonable system designer will understand that. I
like to spell things out. In any case, since the MSG team has not spelled
out anything about what goes on between the MSH and the software above it,
notification about conversation beginning and end is just one more thing
that has to exist but isn't spelled out.
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
*************************************************************************************
David Fischer <david@drummondgroup.com> on 12/06/2001 11:15:57 AM
To: Ralph Berwanger <rberwanger@bTrade.com>,
ebxml-msg@lists.oasis-open.org
cc:
Subject: RE: [ebxml-msg] Re: Comments on the 1.09 about ConversationId
I'm sorry, I was not clear enough.
Conversations may not end, from the MSH perspective, because there is no
notification to the MSH that a Conversation has ended -- at least we have
not
identified such a thing. If we would specify such a thing, the
notification
must be made to both ends of the Conversation.
This sounds like new functionality.
Regards,
David.