Re: [soa-rm-ra] revised section 4.3

["Mike Poulin" <mpoulin@usa.com>]

1.
I beg you pardon for missing an issue with the diagram "Figure 2726- Interaction dependencies" in 4.3.1. This diagram has the same problem with Service INterface and Behavior/Information Models as the diagram in "Figure 1413- Service Description": Behavior/Information Models drive and contribute into the definition of the Service Interface, not another way around.

I propose (to Peter? :-) ) to correct both diagrams in sync (or I can send corrected picture w/o the source).

2. 
Propose a change for:

Services can be composed in a variety of ways, including direct consumer-to-service interaction, by using programming techniques, or using an intermediary, such as an orchestration engine  leveraging higher level orchestration languages.they can be aggregated by means of an aggregation engine approach that leverages a service composition scripting language.  Such approaches are further elaborated in the following sub-sections on service-oriented business processes and collaborations.

as

Services can be composed in a variety of ways, including direct consumer-to-service interaction or using an intermediary Actor. In technology, interactions may be realised , by using programming techniques, or using an intermediary, such as an orchestration engine  leveraging higher level orchestration languages.they can be aggregated by means of an aggregation engine approach that leverages a service composition scripting language.  Such approaches are further elaborated in the following sub-sections on service-oriented business processes and collaborations.

3.
Propose a change for 

 

 

Business Collaboration

Business collaboration is a set of interactions among business participants where each participant agrees to perform activities that in aggregate will produce a required business outcome.

 

as 

 

Business collaboration is a set of interactions among  form of joint work of business participants where each participant agrees to perform interactions and activities that in aggregate will produce a required business outcome.

 

Reasons: business collaboration is not about interactions but about individual work in encemble with others, which may include interactions.


4.
Propose a change for 
Whereas orchestration requires a central controller to execute a predefined business process, service composition can also be accomplished as a simultaneous cooperation between actors without the presence of a central control.

as 

Whereas orchestration requires a central controller to execute a predefined business process, service composition can also be accomplished as a simultaneous cooperation between joint work of actors without the presence of a central control.  
 

Reason: cooperation != collaboration; cooperation preserves the rule that participants work "as is" only and coopration task is an additional task to them; collaboration assumes dedication and potential chnages inside the participants. Thus, business_collaboration_ may include service _cooperation_ but not service collaboration (which defeats the purpose of services).
Also, a low popularity of Choreography in services (not in business) is attributed to "business services into collaborative efforts in order to achieve a common business outcome based on collective agreements between participants and with no one in charge over the entire collaboration", i.e. it assumes possible change thap participants try to avoid. 

5.
Suggestion:
now it is written: "These ports do not explicitly show service interfaces in order to emphasize that in the example these are not intended to be generally available to any actor in the SOA ecosystem;however, the interfaces should adhere to the principles involved in the composition of services. " (2307-2308)

I understand that this example demonstrate internal dedication o participants to collaborate via syncronising (changing) internal processes. I am OK with this as well with the explanation about "ports". However, the statement "interfaces should adhere to the principles involved in the composition of services"  needs a bit more or different wording. We can say that to be used in the SOA Ecosystem, the interactions between commpanies must use services and service interfaces rahter than ports in accordance with the principles involved in the composition of services 

Thanks,
- Michael


P.S. I will not be bale to partiicpate in today meeting, sorry.



 

----- Original Message -----

From: Ken Laskey

Sent: 01/17/12 12:18 AM

To: soa-rm-ra@lists.oasis-open.org

Subject: [soa-rm-ra] revised section 4.3

I’ve incorporated all adjudicated changes to section 4.3 and attempted to capture consensus in some original material appearing in section 4.3.4 to the end.  I am hoping for a continuation of the agreeability over the past few days and everyone will be happy with the changes; at the least, I am hoping for an acceptable balance among everyone’s remaining unhappiness.

 

 

 

 

 

Take a look and start the discussion.  I’d like nothing better than to have this resolved before Wednesday’s call.

 

 

 

 

 

Ken

 

 

 

 

 

---------------------------------------------------------------------------

 

 

Dr. Kenneth Laskey

 

 

MITRE Corporation, M/S H305              phone: 703-983-7934

 

 

7515 Colshire Drive                                    fax:        703-983-1379

 

 

McLean VA 22102-7508