[1] The idea underlying the notion of service choreography can be summarised as follows: "Dancers dance following a global scenario without a single point of control" That is, at run-time each participant in a service choreography executes its part according to the behavior of the other participants.
[3] Choreography describes the sequence and conditions in which the data is exchanged between two or more participants in order to meet some useful purpose.
On one hand, in service choreographies the logic of the message-based interactions among the participants is specified from a global perspective.
"Many presentations at the W3C Workshop on Web services of 11–12 April 2001 pointed to the need for a common interface and composition language to help address choreography.
Moreover, complementary efforts were launched:[25] "In June 2002, Intalio, Sun, BEA and SAP released a joint specification named Web Services Choreography Interface (WSCI).
The WSCI specification is one of the primary inputs into the Web Services Choreography Working Group which published a Candidate Recommendation on WS-CDL version 1.0 on November 9th, 2005"[3].
The upcoming Business Process Modeling Notation version 2.0 will introduce diagrams for specifying service choreographies.
[9] The academic field has put forward other service choreography languages, for example Let's Dance,[10] BPEL4Chor[11] and MAP.