OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [ebxml-dev] ConversationId Ambiguity


The following appears in your posting, which I believe is quoted from the
MSG spec: "The ConversationId... remains constant for all messages within a

The conversationId must NOT change for each messageId.  It must remain
constant for all messages within a conversation.

Sequence number is important if you believe that there is a use case in
which more than one message sent by a given party within the conversation
may be outstanding at the same time. In other words, in this use case a
receiving MSH may have two or more messages for the same conversation to
process at the same time.



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

kumar <kumar@SAMSUNGSDSINDIA.com> on 01/10/2002 06:06:51 AM

To:    ebxml-dev@lists.ebxml.org
cc:    Visweswaraiah <Visweswaraiah@SAMSUNGSDSINDIA.com>, 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?


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>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC