If we were to support signals of any sort, and I view this is named
message types, then we need to be sure that they have general
applicability in all domains of interest. If we cannot then we would
need to consider an ontological approach in which the ontology of the
domain is loaded and that is what provides the definitions of the
named message types. This approach would obviate the need to define
"built-in" named message types and retain all of the expressiveness
that they provide but rooting it in the applicable domains.


Cheers


Steve T


On 19 Jul 2004, at 20:56, Jean-Jacques Dubray wrote:


<excerpt><fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>David:</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Yes,
I think this is exactly what I am saying, the coupling is at the state
level not at the message level (type of messages, choreography of the
protocol, … all this is “context” specific (not just implementation
specific)).</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>JJ-</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>



<bold><fontfamily><param>Tahoma</param><x-tad-bigger>From:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
david.burdett@commerceone.com [mailto:david.burdett@commerceone.com]</x-tad-bigger></fontfamily>

<fontfamily><param>Tahoma</param><x-tad-bigger>
</x-tad-bigger><bold><x-tad-bigger>Sent:</x-tad-bigger></bold><x-tad-bigger>
Monday, July 19, 2004 12:39 PM</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>To:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Jean-Jacques Dubray; gary@enigmatec.net; tony.fletcher@choreology.com;
public-ws-chor@w3.org</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Cc:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Robin.Milner@cl.cam.ac.uk; kohei@dcs.qmul.ac.uk; yoshida@doc.ic.ac.uk</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Subject:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
RE: State Alignment and Standard Signals</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><x-tad-bigger>JJ</x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><x-tad-bigger>You
said ...</x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><x-tad-bigger>>>></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,FFFF</param><x-tad-bigger>
and leave the protocol detail to the
implementation </x-tad-bigger></color><color><param>0000,0000,8080</param><x-tad-bigger>–</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<JJ>
This is unfortunately not possible, because there is a coupling
between the states of the protocol and the choreography definition,
otherwise it does not make any sense to use a protocol<</JJ></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<<<<< </x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><color><param>0000,0000,FFFF</param><bigger><bigger> </bigger></bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Couldn't
you have different protocols that could result in the same end state?
Also, I think that you could have different messages, with different
representations, binding to transport protocols, etc, that had the
same semantic.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><color><param>0000,0000,FFFF</param><bigger><bigger> </bigger></bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>David</x-tad-bigger></color></fontfamily>


<fontfamily><param>Tahoma</param><x-tad-bigger>-----Original
Message-----</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>From:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Jean-Jacques Dubray [mailto:jeanjadu@Attachmate.com]</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Sent:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Monday, July 19, 2004 10:27 AM</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>To:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Gary Brown; Burdett, David; tony.fletcher@choreology.com;
public-ws-chor@w3.org</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Cc:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Robin.Milner@cl.cam.ac.uk; kohei@dcs.qmul.ac.uk; yoshida@doc.ic.ac.uk</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Subject:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
RE: State Alignment and Standard Signals</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Gary:</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>I
don’t think that the “re-use” is in this dimension. For instance,
either a choreography requires state alignment or it does not. The
proposal I made allows for the state alignment protocol to be changed
independently of the choreography definition, therefore allowing it to
be reused in widely different contexts (ebXML, RN, …). A particular
protocol can be used, provided that the protocol you use yield the
same “states” (this is the only level of coupling required between the
protocol and the choreography).</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>From a business
perspective, it would be nice to be able to simply specify the
business protocol as,</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger><<interaction request /></x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>......</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger><<interaction response /></x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>OR</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>
</x-tad-bigger></fontfamily><fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger><<interaction
request-response /> - if synchronous</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><color><param>0000,0000,8080</param><bigger><bigger> </bigger></bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<JJ>
I thought this was precisely the proposal I made, because you can
define an interaction template with an embedded protocol, the
resulting usage of that template looks exactly like the statements
above. It simply means that a few more messages are exchanged as part
of the interaction. Did you take a look at BPSS and the concept of
Business Transaction and Business Transaction Activities (usage of a
business transaction in a collaboration definition)? <</JJ></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>and leave the protocol
detail to the
implementation </x-tad-bigger><color><param>0000,0000,8080</param><x-tad-bigger>–</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<JJ>
This is unfortunately not possible, because there is a coupling
between the states of the protocol and the choreography definition,
otherwise it does not make any sense to use a protocol<</JJ></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger> i.e. this information
would then only be required by an endpoint generation tool, to ensure
that the endpoint used the correct protocol, or an endpoint monitoring
tool to ensure that it interprets the correct set of "on the wire"
messages as an interaction.</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>The problem (you might
reply) is that this does not enable us to do different paths depending
on whether the acknowledgement failed, or the acceptance was negative.
However, if we look at how a BPSS endpoint might react in this
situation, possibly this could be viewed as a exception path in CDL?
This may enable us to define the relevant alternate paths, without
having to make the different stages of the protocol explicit in the
choreography?</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<JJ>The
question is on what basis you take the decision to enter an exception
path? Only a protocol failure can do that, hence the coupling with
protocol states (not protocol message interchanges)<</JJ></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><color><param>0000,0000,8080</param><bigger><bigger>Again,
the proposal I made is for CDL not to define a specific protocol but
rather allow us to define interaction templates that include a
protocol message interchange and resulting states. Such choreography
could then be used, say in a BPSS context, where the protocol specific
messages are the BPSS signals bound to the choreography protocol
states.</bigger></bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Jean-Jacques</x-tad-bigger></color></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>----- Original Message
-----</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>
</x-tad-bigger><bold><x-tad-bigger>From:</x-tad-bigger></bold><x-tad-bigger>
</x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>Jean-Jacques
Dubray</x-tad-bigger></color><x-tad-bigger> </x-tad-bigger></fontfamily>


<bold><fontfamily><param>Arial</param><x-tad-bigger>To:</x-tad-bigger></fontfamily></bold><fontfamily><param>Arial</param><x-tad-bigger>
</x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>Gary
Brown</x-tad-bigger></color><x-tad-bigger> ;
</x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>david.burdett@commerceone.com</x-tad-bigger></color><x-tad-bigger>
; </x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>tony.fletcher@choreology.com</x-tad-bigger></color><x-tad-bigger>
; </x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>public-ws-chor@w3.org</x-tad-bigger></color><x-tad-bigger> </x-tad-bigger></fontfamily>


<bold><fontfamily><param>Arial</param><x-tad-bigger>Cc:</x-tad-bigger></fontfamily></bold><fontfamily><param>Arial</param><x-tad-bigger>
</x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>Robin.Milner@cl.cam.ac.uk</x-tad-bigger></color><x-tad-bigger>
; </x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>kohei@dcs.qmul.ac.uk</x-tad-bigger></color><x-tad-bigger>
; </x-tad-bigger><color><param>0000,0000,FFFF</param><x-tad-bigger>yoshida@doc.ic.ac.uk</x-tad-bigger></color><x-tad-bigger> </x-tad-bigger></fontfamily>


<bold><fontfamily><param>Arial</param><x-tad-bigger>Sent:</x-tad-bigger></fontfamily></bold><fontfamily><param>Arial</param><x-tad-bigger>
Friday, July 16, 2004 5:02 PM</x-tad-bigger></fontfamily>


<bold><fontfamily><param>Arial</param><x-tad-bigger>Subject:</x-tad-bigger></fontfamily></bold><fontfamily><param>Arial</param><x-tad-bigger>
RE: State Alignment and Standard Signals</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>This
is how I would approach the problem.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>I
would create a construct called Protocol. A protocol is itself a
choreography, and more precisely a choreography template. This
choreography is of course performed between abstract roles (let’s call
them initiating role and responding role).</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Initiating                                   
Responding</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
--- Request --->                                      Abstract message</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<<---- Receipt ---                                      (concrete)
signal</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<<---- Acceptance---                                 (concrete) signal</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<<---- Response ---                                   Abstract message</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
--- Receipt --->                                       (concrete)
signal</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
--- Acceptance--->                                  (concrete) signal</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>When
this template is used, every abstract message must be associated to a
concrete message.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>In
addition I should be able to associate “states” to this choreography,
e.g.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>
-</x-tad-bigger></color></fontfamily></excerpt><excerpt><fontfamily><param>Times New Roman</param><color><param>0000,0000,8080</param><smaller><x-tad-smaller>   
</x-tad-smaller></smaller></color></fontfamily></excerpt><excerpt><fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>RequestAccepted
= positive request Acceptance signal received,</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>
-</x-tad-bigger></color></fontfamily></excerpt><excerpt><fontfamily><param>Times New Roman</param><color><param>0000,0000,8080</param><smaller><x-tad-smaller>   
</x-tad-smaller></smaller></color></fontfamily></excerpt><excerpt><fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>ResponseAccepted
= positive Response Acceptance signal received.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>
“Positive” acceptance/response represents an XPath expression on a
message.</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>In
a choreography, I should be able to specify (apologies, I don’t know
the syntax by heart):</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><<choreography
… ></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<<interaction type=”procotol”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
<<protocol ref=”myProtocol”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<<message name=”Request” type=”ProcessPO”/></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<<message name=”Response” type=”AckPO”/></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<<state name=”OrderProcessed” boundTo=”RequestAccepted”/></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<<state name=”OrderAccepted” boundTo=”ResponseAccepted”
conditionExpression=”//PO/@accepted=”true”/></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
<</protocol></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<</interaction></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>           
<<choice></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
<<switch value=”OrderAccepted”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
   <<case value=”true”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<<interaction type=”Request/Response”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                               
… process payment …</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
<</interaction></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
   <</case></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
   <<case value=”false”></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                                   
… choreography ends …</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
   <</case></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>                       
<</switch></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><</choice></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger><</choregraphy></x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>I
promised David that I will make a formal proposal, I hope within the
next couple of weeks. Is this kind of approach acceptable?</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger> </x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>Jean-Jacques</x-tad-bigger></color></fontfamily>


<fontfamily><param>Arial</param><color><param>0000,0000,8080</param><x-tad-bigger>  </x-tad-bigger></color></fontfamily>



<bold><fontfamily><param>Tahoma</param><x-tad-bigger>From:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Gary Brown [mailto:gary@enigmatec.net]</x-tad-bigger></fontfamily>

<fontfamily><param>Tahoma</param><x-tad-bigger>
</x-tad-bigger><bold><x-tad-bigger>Sent:</x-tad-bigger></bold><x-tad-bigger>
Friday, July 16, 2004 8:25 AM</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>To:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Jean-Jacques Dubray; david.burdett@commerceone.com;
tony.fletcher@choreology.com; public-ws-chor@w3.org</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Cc:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Robin.Milner@cl.cam.ac.uk; kohei@dcs.qmul.ac.uk; yoshida@doc.ic.ac.uk</x-tad-bigger></fontfamily>

<bold><fontfamily><param>Tahoma</param><x-tad-bigger>Subject:</x-tad-bigger></fontfamily></bold><fontfamily><param>Tahoma</param><x-tad-bigger>
Re: State Alignment and Standard Signals</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>Hi</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>Do you have an example
of how the CDL would look in order to represent this state alignment
(e.g. as you have described in your article), in such a manner that
the interactions are protocol independent? Would you see a "state
aligned" interaction only completing after the second (acceptance)
signal in the BPSS case?</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>For example,</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>
</x-tad-bigger></fontfamily><fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>    <<interaction A->B /></x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>would only be deemed to
have completed once B had sent the acceptance message to A?</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>Curious to know how such
a state alignment protocol could be modelled in CDL in an abstract
manner that is decoupled from a particular binding........</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>Regards</x-tad-bigger></fontfamily>


<fontfamily><param>Arial</param><x-tad-bigger>Gary</x-tad-bigger></fontfamily>


<fontfamily><param>Times New Roman</param><bigger><bigger> </bigger></bigger></fontfamily>

</excerpt>