Choreography in IRS-III – Coping with Heterogeneous Interaction Patterns in Web Services

Abstract

Abstract. In this paper we describe how we handle heterogeneity in web service interaction through a choreography mechanism that we have developed for IRS-III. IRS-III is a framework and platform for developing semantic web services which utilizes the WSMO ontology. The overall design of our choreography framework is based on: the use of ontologies and state, IRS-III playing the role of a broker, differentiating between communication direction and which actor has the initiative, having representations which can be executed, a formal semantics, and the ability to suspend communication. Our framework has a full implementation which we illustrate through an example application.

An Improved Abstract State Machine Based Choreography Specification and Execution Algorithm for Semantic Web Services

“…Authors of [2] demonstrate the data granularity mismatch issue with an example: one web service requires credit card details to be sent one at a time, whereas another requires that all details are sent in single message. Frame structures in Flora-2 intrinsically solve this type of granularity issue.…”

“…Service choreography however (as pointed out in [1][2][3] as well) does not have a unique understanding among researchers. In the Business Process Modeling (BPM) community, choreography is known as a general predefined collaboration scenario that should be agreed upon and adhered to by two or more web services in order to accomplish a business goal, without the presence of a central coordinator (unlike orchestration).…”

“…In fact, our literature search has failed to reveal any choreography engine that implements it exactly as specified. For example, current implementations (such as WSMX [17] and IRS-III [2]) do not fully adhere to the ASM theory. Our own investigation into the algorithm has revealed certain important shortcomings which make it unsuitable for driving the correct interaction between goal and web service choreographies, and helps explain its lack of proper adaptation in existing choreography engine implementations.…”

Process Mediation of OWL-S Web Services

“…OWL-S broker [29] also assumes that the requester formulates its request as query which is used to find appropriate providers and to translate between the requester and providers. The work in [32] and [33] describe the IRS-III broker system based on the WSMO methodology. IRS-III requesters formulate their requests as goal instances and the broker mediates only with providers given their choreographies (explicit mediation services are used for mediation).…”

3-Level Service Composition and Cashew: A Model for Orchestration and Choreography in Semantic Web Services

“…The DIP project 2 has proposed [15] that the distinction that the IRS [4], one of two DIP implementations of the WSMO model, makes between service-and client-choreographies [5] should be formalised in WSMO. The first difference between the two is the viewpoint: in a service choreography, the service documents which communications are offered to clients; in a client choreography, the client documents which communications they offer and accept in return.…”