- From: Monica J. Martin <Monica.Martin@Sun.COM>
- Date: Mon, 25 Oct 2004 18:02:27 -0700
- To: Tony Fletcher <tony.fletcher@choreology.com>, "'Nickolas Kavantzas'" <nickolas.kavantzas@oracle.com>
- Cc: "'Furniss, Peter'" <Peter.Furniss@choreology.com>, "'Steve Ross-Talbot'" <steve@enigmatec.net>, "'WS-Choreography List'" <public-ws-chor@w3.org>
Tony Fletcher wrote: >Dear Nick, Peter and others, > >Firstly the text for the parallel construct (2.5.1.2 Parallel) currently >mentions nothing about when it completes. I think it should explicitly >state that the parallel activity is not finished until all the activities in >the parallel or finished. > > mm1: +1 to Tony's question. Also a point to clarify, you indicate a parallel enables 'concurrently' one or more Activity-Notations. Concurrent typically implies there is an intersection at some point. Parallel can be independent. Can you clarify what applies here as I think concurrency applies not necesarily parallel. >Secondly, I do not quite understand the Choreography Life-line proposal. >Does it mean that the Boolean expression of the complete attribute is >'continuously' evaluated and if / as soon as it evaluates to true the >choreography is terminated. I think we should spell out whether it is >evaluated continuously or at what points it is evaluated and what happens to >the choreography when it does turn true - I presume that messages 'in >flight' do not suddenly vaporise, for instance. > >
Received on Tuesday, 26 October 2004 01:02:30 UTC