W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

Use case on choreography negotiation

From: Burdett, David <david.burdett@commerceone.com>
Date: Tue, 29 Apr 2003 15:02:25 -0700
Message-ID: <C1E0143CD365A445A4417083BF6F42CC07E6F844@C1plenaexm07.commerceone.com>
To: "WS Choreography (E-mail)" <public-ws-chor@w3.org>
As requested in the conference call, here is the use case that I described.
In this use case, two businesses agree at the business level, that they want
to do business with each other electronically (e.g a buyer wants to place
orders with a seller). Once the business agreement is reached, the
technology to enable the businesses to interoperate and exchange business
documents needs to be set up. This involves agreement on such things as:
1. The business documents and messages that will be used
2. Use of reliable messaging and security technologies
3. The choreographies that will be used (i.e. the sequence in which the
messages will be exchanged)
In order to reach agreement, the businesses conduct an automatic negotiation
with each other that consists of the following steps:
1. Sharing with each other, information about the documents, messages,
reliable messaging, security and choreographies that each supports,
2. Identifying the common set of information that both businesses support
3. Where there are multiple choices of techology, agreeing between them the
optimum set of technologies they will actually use which they then record in
an agreement for future reference
For all the information that is shared (including choreographies) there is a
comment requirement that the information is classified or categorized in a
way which allows the negotiation and agreement to occur.
Director, Product Management, Web Services
Commerce One
4440 Rosewood Drive, Pleasanton, CA 94588, USA
Tel/VMail: +1 (925) 520 4422; Cell: +1 (925) 216 7704
mailto:david.burdett@commerceone.com; Web:  <http://www.commerceone.com/>

Received on Tuesday, 29 April 2003 18:02:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:58 UTC