W3C home > Mailing lists > Public > public-ws-chor@w3.org > July 2003

Re: The degenerate pi-calc use case

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Sun, 13 Jul 2003 21:03:32 +0100
Cc: public-ws-chor@w3.org
To: Jeff Lansing <jeff@polexis.com>
Message-Id: <14713164-B56D-11D7-90BD-000393AD2AA6@enigmatec.net>

Jeff,

I agree with your comments. The reason for the use case and the reason 
for using the pi-calculus is that it is such a simple use case with no 
real business interest to it. The aim was to flush out fairly basic 
requirements by using an example that was easy to specify in an 
unambiguous way (hence the use of the pi-calculus). I don't think that 
anyone who is familiar with the pi-calculus would suggest using it as a 
one-to-one mapping to a language for choreography. Rather it has 
interesting properties that one can exploit. In the same way lambda 
calculus, upon which most imperative programming languages are based, 
is not evident. Syntactic sugar can be used to hide the formalism and 
help the intuitive appear and at the same time enable us to ask 
questions of a language with a formal base (even if not proven) that we 
perhaps could or would not otherwise be able to ask.


Cheres

Steve T

On Sunday, July 13, 2003, at 03:20  pm, Jeff Lansing wrote:

>
> This example is interesting, but it seems like a lot of machinery to
> describe what is essentially just connecting to something like a
> GetStockQuote service.
>
> What if you try to do something just a little harder, such as pulling
> (or pushing) the results of a StockQuote service through a
> CurrencyConverter service?
>
> Does the amount of pi-calculus machinery then become so cumbersome, in
> that case, that it starts to loose its intuitive appeal?
>
> Jeff
>
> This email is confidential and may be protected by legal privilege. If 
> you are not the intended recipient,  please do not copy or disclose 
> its content but  delete the email and contact the sender immediately. 
> Whilst we run antivirus software on all internet emails we are not 
> liable for any loss or damage. The recipient is advised to run their 
> own antivirus software.
>

This email is confidential and may be protected by legal privilege. If you are not the intended recipient,  please do not copy or disclose its content but  delete the email and contact the sender immediately. Whilst we run antivirus software on all internet emails we are not liable for any loss or damage. The recipient is advised to run their own antivirus software.
Received on Sunday, 13 July 2003 16:03:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:24 GMT