RE: [soa-rm-ra] SOA-Pro & Core Concepts

["Danny Thornton" <danny.thornton@scalablearchitectures.com>]

The PR1 Release of the OASIS SOA RA shows choreography as an attribute
of the Service Description Process Model, line 1163.  Choreography is
defined in two places:
 
Line 897
Process Choreography
The description of the possible interactions that may take place between
two or more participants to fulfil an objective.
 
Line 2104
Choreograpy
A technique used to characterize and to compose service-oriented
business collaborations based on ordered message exchnges between peer
entities in order to achieve a common business goal.
 
The OMG Pro states:
The Choreography is a aspecification of what is transmitted and when it
is transmitted between parties to enact a service exchange. The
choreography specifies exchanges between the parties - the data, assets
and obligations that go between the service participants and any other
service interface. The choreography defines what happens between the
provider and consumer participants without imposing on their internal
processes - but their internal processes do have to be compatible with
their external contracts.

My statements are in agreement with all definitions referenced above.  

I do agree with Michael that choreography is not a part of Service
Contract, but in the context which the OMG Pro uses Service Contract
their intention is similar to the use of choreography in the OASIS SOA
RA.

In other words, the different usages of choreography is not something
that would give me heartburn.

Danny Thornton


-------- Original Message --------
Subject: Re: [soa-rm-ra] SOA-Pro & Core Concepts
From: "Jeffrey A. Estefan" <jeffrey.a.estefan@jpl.nasa.gov>
Date: Thu, July 31, 2008 3:43 pm
To: <soa-rm-ra@lists.oasis-open.org>

 Folks,
 
Whose definition of Choreography are we using?  Ours (in Sect 4.3.3 of
RA), or somebody else's?