Reference to WS-CDL and to "If, a peer-style business collaboration in which
visibility into and use of each participating organization’s internal
service-oriented business processes was necessary as part of an end-to-end
business transaction" leads:
a) creation of single centralised conductor, which has no real difference from the orchestrating entity
b) violates SO Principles of Service Abstraction and Loose-Coupling: no internal SO or not-SO business process may be visible through the service interface (used for the collaboration).
The beauty of Choreography in the business meaning is in that there is no such thing as "an end-to-end business transaction": business services get together to resolve common task and everyone of them knows what to do in
response to receiving particular message. However, there is NOBODY personally is responsible for the final result. The WS-CDL violates this fundamental principle of Choreography when it is trying to create a Scenario Contract (end-to-end script).
The SOA RAF should not mistakenly mix technical implementation of Choreography with the Business Choreography or Collaboration.
Regards,
- Michael Poulin