I like Frank's observation. Cheers
Steve T On 20 Jul 2006, at 17:31, Frank Leymann wrote: > From my perspective, there is in fact a distinction between > orchestration and composition: Orchestration is one of many different > methods to compose services. E.g. you can define compositions at the > type level and instantiate it afterwards (that what BPEL does, e.g.); > composition at the instance level is possible too (e.g. when an > agreement protocol is run between a collection of services); and so > on. > > ----- Ursprüngliche Mail ---- > Von: Ashley at Metamaxim <[EMAIL PROTECTED]> > An: [email protected] > Gesendet: Mittwoch, den 19. Juli 2006, 16:10:01 Uhr > Betreff: Re: [service-orientated-architecture] Orchestration, > Choreography, and Composition > > > Todd wrote: > > > I thought I'd turn this into a group exercise and see how all of you > > define it. (i.e., Orchestration, Choreography, and Composition) > > Excellent. This should be fun! > > In my view, Choreography defines a behavioural protocol to which > multiple parties must (or should) adhere when engaged in a service > based collaboration. I am sure that Steve R-T will give us the > definitive definition of Choreography! > > Like you, Todd, I am not clear whether there is any real difference > between Orchestration and Composition. Perhaps Orchestration is the > means by which Composition is achieved? > > Rgds > Ashley > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
