RE: [ebxml-dev] ConversationId Ambiguity

[Dick Brooks <dick@tech-comm.com>]

Kumar,

>Now the question wether the ConversationId is Unique within From and To
>Party pair?

I think of the ConversationId as a "session id". All messages exchanged over
the same "session" would have the same ConversationId.

>wether the ConversationId remains same for the set of messageIds?

That's correct, different messageId's can be exchanged over the same
ConversationId.

>If ConversationId is unique and changes with each messageId then what is
>the essence of sequence number?

ConversationId is not required to change with each messageId. If it did then
your question would be valid.

All of the cases I'm aware of use ConversationId for "session context" and
all messages exchanged over a session may require ordered delivery (e.g.
sequenceNumber).

Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>
Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714

-----Original Message-----
From: kumar [mailto:kumar@SAMSUNGSDSINDIA.com]
Sent: Thursday, January 10, 2002 5:07 AM
To: ebxml-dev@lists.ebxml.org
Cc: Visweswaraiah; Pradeep N
Subject: [ebxml-dev] ConversationId Ambiguity


Hi! ebXML folks,

Specification says the ConversationId Must be unique between From and To
Party pair.

------------------------------------------------------------------------
------------------------------------------------------------------------
-
The REQUIRED ConversationId element is a string identifying the set of
related messages that make up a conversation between two Parties. It
MUST be unique within the From and To party pair.  The Party initiating
a conversation determines the value of the ConversationId element that
SHALL be reflected in all messages pertaining to that conversation.
The ConversationId enables the recipient of a message to identify the
instance of an application or process that generated or handled earlier
messages within a conversation. It remains constant for all messages
within a conversation.


All messages sent within the same conversation, as identified by the
ConversationId element, that have a deliverySemantics attribute with a
value of OnceandOnlyOnce SHALL each have the same value
messageOrderSemantics (either Guaranteed or NotGuaranteed).

SequenceNumber element
The SequenceNumber element indicates the sequence in which messages MUST
be processed by a Receiving MSH. The SequenceNumber is unique within the
ConversationId and MSH.  The From Party MSH and the To Party MSH each
set an independent SequenceNumber as the Sending MSH within the
ConversationID.  It is set to zero on the first message from that MSH
for a conversation and then incremented by one for each subsequent
message sent.
------------------------------------------------------------------------
------------------------------------------------------------------------
-
When you carefully scan the specification, Initially it says that
ConversationId Must be unique within From and To Party pair. Again it
says that it remains constant within in
within a conversation.And again it says that Sequence Number is unique
within the conversationId and MSH.
Now the question wether the ConversationId is Unique within From and To
Party pair?
wether the ConversationId remains same for the set of messageIds?
If ConversationId is unique and changes with each messageId then what is
the essence of sequence number?


Regards
kumar








----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>