RE: Grounding Choreographies (the atoms) - WAS Simple Choreography composition suggestion

Dear Colleagues,

Clearly this is one approach,. But perhaps not the most useful one.

Another approach is to allow hierarchal (or layered) composition within
the language as David (Burdett) has been suggesting, such that we can
build an MEP from a set of messages and then a (higher level) MEP from
MEPs and so on.  And I agree we could use the term an 'interaction' to
mean a single message or a single MEP.  So I think that the distinction
that Steve mentioned in another email between a business message and a
protocol message is not helpful - it is just a question of the 'layer'
you are focused on (consider which is the real business message in SOAP
embedded in HTTP embedded in TCP embedded in IP until eventually you do
ground in photons or electrons!!)

Best Regards     Tony
A M Fletcher
 
Cohesions  (TM)
 
Business transaction management software for application coordination
www.choreology.com
 
Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK
Tel: +44 (0) 20 76701787   Fax: +44 (0) 20 7670 1785  Mobile: +44 (0)
7801 948219
tony.fletcher@choreology.com     (Home: amfletcher@iee.org)


-----Original Message-----
From: public-ws-chor-request@w3.org
[mailto:public-ws-chor-request@w3.org] On Behalf Of Steve Ross-Talbot
Sent: 18 July 2003 09:27
To: Champion, Mike
Cc: public-ws-chor@w3.org
Subject: Re: Grounding Choreographies (the atoms) - WAS Simple
Choreograph y composition suggestion



+1

On Thursday, July 17, 2003, at 07:25  pm, Champion, Mike wrote:

>
>
>
>> -----Original Message-----
>> From: Cummins, Fred A [mailto:fred.cummins@eds.com]
>> Sent: Thursday, July 17, 2003 1:59 PM
>> To: Martin Chapman; Steve Ross-Talbot; Champion, Mike
>> Cc: public-ws-chor@w3.org
>> Subject: RE: Grounding Choreographies (the atoms) - WAS Simple 
>> Choreograph y composition suggestion
>>
>
>
>> While I agree that it should be possible to define a MEP with the 
>> choreography langauge, I would not like a reliable messaging 
>> choreography to be merged with a purchasing choreography. I want the 
>> purchasing choreography to be expressed with the reliable messaging 
>> protocol implied, i.e., abstracted out.
>>
>> The MEP will have implications to the design of the business 
>> choreography.  Consequently, it may be necessary to incorporate a 
>> reference so that the assumptions are clear, but I don't see a single

>> choreography incorporating both levels of abstraction in any more 
>> complex way.
>
> Maybe we could agree that ...
>
> -- The underlying formalism we use or devise must be rich enough to
> describe
> all known MEPs, and RM protocols, etc.
>
> -- The actual WS-Choreography language must be rich enough to describe
> the
> interaction at the "logical" level, with RM, Security interactions, 
> etc.
> abstracted away.
>
> -- Our objective is that business choreography *languages* can be
> built as a
> layer on top of WS-Choreography, not that it should be directly 
> useable by
> non-technical business analysts  .
>
> 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 Friday, 18 July 2003 06:43:42 UTC