wsmx logo

D13.6v0.2 WSMX Use Cases

WSMX Working Draft 21 September 2005

This version:
http://www.wsmo.org/TR/d13/d13.6/v0.2/20050907/
Latest version:
http://www.wsmo.org/TR/d13/d13.6/
Previous version:
http://www.wsmo.org/TR/d13/d13.6/v0.1/20041205/
Editor:
douglas foxvog
Author:
douglas foxvog, Armin Haller


Table of contents

1. Introduction
1.1. Overview
1.2. Purpose of this document
1.3. Document Overview
2. WSMX architecture components
3. WSMX Architecture Components
4. Conclusions and Further Directions
References
Acknowledgement

1. Introduction

1.1 Overview

The Web Services Execution Environment (WSMX) [Cimpian et al., 2005] is an execution environment for dynamic discovery, selection, mediation and invocation of semantic Web Services. WSMX is based on the Web Services Modeling Ontology (WSMO) [Roman et al., 2005] which describes all aspects related to this discovery, mediation, selection and invocation.

WSMX is a reference implementation for WSMO. The goal is to provide both a test bed for WSMO and to demonstrate the viability of using WSMO as a means to achieve dynamic inter-operation of semantic Web Services.

1.2. Purpose of this document

This document introduces several usage scenarios of WSMX, described in different documents. The first document, D13.6v0.1 (renumbered D13.6.1) [Haller, 2004] identifies three WSMX use cases: a Business-to-Consumer (B2C), a Business-to-Business (B2B), and an Application-to-Application (A2A) scenario. The process steps within these scenarios are only presented at a conceptual level, a more detailed description of implemented parts of the execution semantics of WSMX is given in [Oren, 2004].

The second document, WSMX X12 Use Case (D13.6.2) [Foxvog, 2005] details an expanded use case using WSMX to send and receive ANSI X12 EDI messages.

The documents briefly describe the architecture and the scope of WSMX at the time of their writing and review the knowledge necessary for exemplifying the specific use cases.

The first version of WSMX provided a complete architecture for dynamic discovery, mediation, selection and invocation and a simple but complete implementation of these components. In this implementation it was not able to fulfill all aspects of the execution requirements described in the initial use cases.

The second use case [Foxvog, 2005] uses a more complete version of WSMX with a far larger and more complex ontology.

Subsequent versions of WSMX and corresponding use cases will incorporate ongoing research of the WSMO and WMSL working group and will lead WSMX to a status where it fulfills all the Semantic Web Services support described in this document.

Hence the use cases are intended to serve as an input for further improvements and providing valuable insight for adapting or including components to deal with real world scenarios for Web Services. Further use cases will evolve in accordance to the ongoing development of WSMX itself and references to them will be included in this documment in the future as necessary.

2. Use Cases

The initial set of use cases [Haller, 2004] was divided into two business domains. The Business to Consumer and Business to Business use cases describe the purchase of a bike, firstly in a B2C and secondly in a B2B collaboration. Both scenarios are first described in general; the actors, roles, and goals are defined; the overall system architecture is depicted; and finally the execution flow of WSMX for the cases is outlined. The final use case in the set describes an Application Integration scenario by illustrating an A2A use case. It depicts an automatically invoked stock purchase by an application running in a banks divison and processed and executed by another division within the same bank.

The second use case [Foxvog, 2005] uses a large electronic data interchange (EDI) ontology for converting a few types of messages (initially) from ANSI X12 EDI to WSML.

3. WSMX architecture components

The individual use cases present very brief description of WSMX's components. This is solely indented to give the reader the chance to follow the process steps in the use cases without knowledge of other WSMX deliverables. Given the fact that some components are very specific and cover some technical requirements, they are not exemplified in the use cases and therefore not specified in detail in the the use case documents. For further information on all components we point the interested reader to the WSMX Architecture document [Zaremba/Moran, 2005].

4. Conclusions and Further Directions

The initial use cases described the execution flow of different invocation scenarios and showed how different entities could benefit from using WSMX as their means for executing Semantic Web Services. WSMX makes optimal use of the semantic descriptions offered by WSMO to address the requirements from the B2C, B2B and A2A domain. WSMX could be used as the centerpiece of a robust and flexible Web Service architecture: customers could use the client side editor to search and invoke web services, service requesters could use it to achieve their business tasks and it could be used to interconnect applications.

In the first release of WSMX not every component could perform all the tasks described in the use cases. A client-side editor had not yet been implemented for designing and sending goals. The functionality of the Choreography Engine was based on a simple match without any Mediation Service if the communication pattern of the requester and provider were different. Hence communication could only be performed if the two communication patterns are perfectly symmetrical.

The composition of Web Services was omitted in these use cases so far. A composition component would be responsible for executing complex compositions of services in order to achieve a certain goal.

Work is just beginning on the EDI use case.

References

[Oren, 2004] E. Oren: WSMX Execution Semantics. WSMX Working Draft v01, 2004. Available from http://www.wsmo.org/2004/d13/d13.2/v0.1/.

[Cimpian et al., 2005] E. Cimpian, T. Vivtar, M. Zaremba: Overview and Scope of WSMX. WSMX Working Draft v0.2, 2005. Available from http://www.wsmo.org/TR/d13/d13.0/v0.1/20050223/.

[Foxvog, 2005] D. Foxvog: WSMX X12 Use Case. WSMX Working Draft v0.1, 2005. Available from http://www.wsmo.org/TR/d13/d13.6/d13.6.2/v0.1/.

[Haller, 2004] A. Haller: WSMX Use Cases. WSMX Working Draft v0.1, 2004. Available from http://www.wsmo.org/TR/d13/d13.6/v0.1/20041205/.

[Roman et al., 2005] D. Roman, H. Lausen, and U. Keller: Web Service Modeling Ontology (WSMO). WSMO Final Draft v1.2, 2005. Available from http://www.wsmo.org/TR/d2/v1.2/20050413/.

[Zaremba/Moran, 2005] M. Zaremba, M. Moran: WSMX Architecture. WSMX Working Draft v0.2, 2005. Available from http://www.wsmo.org/TR/d13/d13.4/v0.1/20050613/.

Acknowledgement

The work is funded by the European Commission under the projects DIP, Knowledge Web, Ontoweb, SEKT, SWWS, Esperonto, and h-TechSight; by Science Foundation Ireland under the DERI-Lion project; and by the Vienna city government under the CoOperate program.

The editors would like to thank to all the members of the WSMX working group for their advice and input into this document.


Valid XHTML 1.1!

webmaster