- From: Jon Dart <jdart@tibco.com>
- Date: Thu, 27 Feb 2003 13:03:30 -0800
- To: Assaf Arkin <arkin@intalio.com>
- Cc: bhaugen <linkage@interaccess.com>, public-ws-chor@w3.org
I am curious why you'd regard these as requirements. The use case of, for example, bargaining over the terms of a transaction before completing it, has been contemplated and there is standardization work going on in that area in the context of ebXML. However, this is probably beyond what most people now deploying B2B are doing. Real B2B in my experience currently tends to involve parties that have pre-existing relationships (established non-electronically) and pre-negotiated terms. If we want to enable people to move beyond that model and make the process more dynamic, that may be desirable, but let's be sure that there is a real business use case for it. Also I think the problem set that something like the ebXML CPA addresses may be a different problem than what this group is chartered to do. --Jon Assaf Arkin wrote: > I definitely agree and would like to add to further requirements: > > * A conversation may involve more than one participant > * Conversation rules usually allow participants to join and leave > * A conversation may range over multiple participants but involve only a > subset at any sub-conversation > * A participation in one conversation could be identical to a participation > in another conversation > * Negotiating a script is also a conversation, so a conversation that leads > to a conversation needs to be described > > arkin > > >>-Bob Haugen > > > >
Received on Thursday, 27 February 2003 16:06:54 UTC