- From: Monica J. Martin <Monica.Martin@Sun.COM>
- Date: Tue, 27 Jan 2004 11:55:51 -0700
- To: "Burdett, David" <david.burdett@commerceone.com>
- Cc: "WS Choreography (E-mail)" <public-ws-chor@w3.org>
mm2: See below. > Burdett: Thanks for the feedback. I've made some comments in line. > I've also attached an updated use case (it's only 9k) to hopefully > clarify some of the points you made. > > -----Original Message----- > From: Monica J. Martin [mailto:Monica.Martin@Sun.COM] > Sent: Tuesday, January 20, 2004 2:39 PM > To: Burdett, David > Cc: WS Choreography (E-mail) > Subject: Burdett 1/20/2004: Auction Use Case > > .....mm1: * Registration may occur outside of the choreography. > Implies context / policy items. > .....Burdett2: I also agree that it does imply some context/policy > terms since there is a dependency between the registration and auction > choreographies. The question is, how should this be handled from a > choreography persective. > > mm1: Need to differentiate notification messages. They are not the > same, and processing or implications will be different. Differences > may be understood above the choreography [1]. > Burdett2: I agree. However, I think it is quite realistic that a > choreography designer, however misguided, might want to use the same > message for different purposes as they contain the same content even > though the semantics are different because they are being used in a > different part of the choreography. The question is should the CDL > allow this or should we require that each message/interaction in a > choreography definition be different? > > [1] possible business semantics May also impact auction status or search. > mm2: Steve and Martin, I think we have two discussion items here for the reqts document and WS-CDL in general. On notification messages, this is one area where the differentiation is understood at the business, not necessarily in WS-CDL.
Received on Tuesday, 27 January 2004 16:45:36 UTC