This is in reply both to Stefano's posting and to Jamie Clark's posting
that it references (see below).
The CPA should specify whether messages are sequence-numbered. The CPA
specification has to be in sync with the messaging specification. I am not
sure that the definition of sequence numbers is complete in the messaging
spec. at this time.
Whether the sequence counts find their way up to the business application
is a messaging service and other middleware matter.
As to messages referencing each other, the message header includes a
RefToMessageId element, which is for that purpose.
As Stefano reminds us, the whole question of ebXML middleware (BSI)
interoperability and a conceptual upper interface to the messaging service
have thus far been ignored by ebXML.
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
*************************************************************************************
Stefano POGLIANI <[email protected]> on 03/06/2001 04:15:58 AM
Please respond to [email protected]
To: James Bryce Clark <[email protected]>, "Welsh, David"
<[email protected]>
cc: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: RE: more on collaborations, contracts and 2-27 minutes
Hope not to miss the point completely.... in which case I apologize.
The verification of the correct sequencing should be done by the
middleware (the infamous BSI) which should be configured out of the
content of the CPA (which, in turn, references the Collaboration
choreography specified by the BP).
/stefano
-----Original Message-----
From: James Bryce Clark [mailto:[email protected]]
Sent: 05 March 2001 22:05
To: Welsh, David
Cc: 'James Bryce Clark'; [email protected];
[email protected]; [email protected]; [email protected];
[email protected]; [email protected]
Subject: RE: more on collaborations, contracts and 2-27 minutes
Dave asks for confirmation that something in ebXML can tag and count
messages sequentially, so as to enable crossreferencing, detection of
blips arriving out of sequence, and the like:
�"I can understand that at a lower level TRP service, there's something
dealing with 'message counting' but I'm not aware that something like this
info finds it's way up the stack so the business app's can also do their
counting; which does sound like redundant but it is the way of the world
and as such it's not going to stop. "
In our "simple negotiation pattern" test, we also noted that messages need
to be able to cross reference each other, and sought confirmation of some
kind of unique message ID.
Good questions.� I don't know the answer.�� Can we do that?�� Goes on my
list for tomorrow's metamodel meeting.�� Jamie
James Bryce Clark
Spolin Silverman & Cohen LLP
310 586 2404��� [email protected]
James Bryce Clark
Spolin Silverman & Cohen LLP
310 586 2404��� [email protected]
