- From: Yves Lafon <ylafon@w3.org>
- Date: Wed, 18 Oct 2006 14:30:06 +0200 (MEST)
- To: Martin Chapman <martin.chapman@oracle.com>
- cc: "'Gary Brown'" <gary@pi4tech.com>, "'WS-Choreography List'" <public-ws-chor@w3.org>
On Tue, 17 Oct 2006, Martin Chapman wrote: > > I very much agree with the reuse argument to remove the flag; a choreo will > be far more resusable if the flag doesn't exist, or at least add a > don’t'care/maybe option! I concur, In fact, the best, if this distinction is needed would be an initiate element somewhere (like on a description of the root choreo) with a link to the initiating interaction. But not something inside the choreo definition. > > Martin. > >> -----Original Message----- >> From: public-ws-chor-request@w3.org >> [mailto:public-ws-chor-request@w3.org] On Behalf Of Gary Brown >> Sent: Tuesday, October 17, 2006 9:04 PM >> To: 'WS-Choreography List' >> Subject: 'initiate' flag issue >> >> >> >> Hi >> >> Thanks to Yves, I have found Nick's comments on my original >> proposal for >> removing the initiate flag: >> http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0049.html >> >> Nick's argument focused on the declarative flag helping a >> designer when >> composing choreographies. However, I don't see this as being a >> compelling argument - in fact, it is better from a reuse point of view >> that previously standalone choreographies that initiated a >> choreography >> session are able to be composed into more comprehensive choreography >> which now starts the session at a different point. >> >> Regards >> Gary >> >> >> >> > > > -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Wednesday, 18 October 2006 12:30:50 UTC