RE: Conversation Id

[David Burdett <david.burdett@commerceone.com>]

I like ConversationId better than MessageSet Id as I think it is more
descriptive. However I don't like the tie in to a business process as it
would suggest that the TRP protocol can *only* be used for eCommerce when
that is not the case.

Therefore how about the following variation on your definitions as an
alternative ...

=========
ConversationId - A unique identifier that links together the messages in a
Conversation

Convesation - The exchange of a series of related messages between two
parties.

A ConversationId is designed to enable the sender or receiver of a message
to identify the instance of a service that it is executing. Frequently a
service is synonymous with the execution of a Business Process
=========

David


-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com]
Sent: Friday, August 18, 2000 5:22 AM
To: ebxml-transport@lists.ebxml.org
Subject: Conversation Id


All,

	As promised this is the definition of ConversationId that John 
Ibbotson and I came up with;

John's definition.
ConversationId	The instance of the business protocol.

My refinement in discussion with John was
ConversationId	A unique identifier assigned by the initiator of 
			the conversation used to relate all messages in a 
			single conversation.

Conversation	A single instance of a unit of business (IBM TPAML)
Alternate definition
Conversation	A single instantiation of a TPA between parties.


	I agree that the definition in the messaging service specification
at line 475 is incorrect and needs amendment.  Looking back it appears 
to have got confused after Burlington when we renamed some of the 
elements as the definition for MessageSetId in the header spec v0.5 is 
what we should have had for ConversationId.  From that version:
Message Set Id 	This is a globally unique identifier for the Message
			Set. It is a string.
			<EdNote> Guidelines on how to specify globally
unique
			identifiers will be provided.
			</EdNote>
Which was why John and I called it conversation ID as we felt the IBM 
term conversation was very close to Message Set and hopefully a little 
easier to explain.

	This was of course compounded when we did the merge and removed 
some of the extra words.  Sorry for the confusion.


Ian Jones