https://xml.coverpages.org/WS-BPEL-CS01.pdf

Web Services Business Process Execution Language Version 2.0

The potential to achieve dynamic, scalable and cost-effective marketplaces and eCommerce solutions has driven recent research efforts towards so-called Semantic Web Services that are enriching Web services with machine-processable semantics. To this end, the Web Service Modeling Ontology (WSMO) provides the conceptual underpinning and a formal language for semantically describing all relevant aspects of Web services in order to facilitate the automatization of discovering, combining and invoking electronic services over the Web.

In this paper we describe the overall structure of WSMO by its four main elements: ontologies, which provide the terminology used by other WSMO elements, Web services, which provide access to services that, in turn, provide some value in some domain, goals that represent user desires, and mediators, which deal with interoperability problems between different WSMO elements. Along with introducing the main elements of WSMO, we provide a logical language for defining formal statements in WSMO together with some motivating examples from practical use cases which shall demonstrate the benefits of Semantic Web Services.

/pdf/web-service-modeling-ontology-2at408gd3c.pdf

Web Service Modeling Ontology

Service-Oriented Architecture (SOA) provides a flexible framework for service composition Using standard-based protocols (such as SOAP and WSDL), composite services can be constructed by integrating atomic services developed independently Algorithms are needed to select service components with various QoS levels according to some application-dependent performance requirements We design a broker-based architecture to facilitate the selection of QoS-based services The objective of service selection is to maximize an application-specific utility function under the end-to-end QoS constraints The problem is modeled in two ways: the combinatorial model and the graph model The combinatorial model defines the problem as a multidimension multichoice 0-1 knapsack problem (MMKP) The graph model defines the problem as a multiconstraint optimal path (MCOP) problem Efficient heuristic algorithms for service processes of different composition structures are presented in this article and their performances are studied by simulations We also compare the pros and cons between the two models

Efficient algorithms for Web services selection with end-to-end QoS constraints

Workflows and e-Science: An overview of workflow system features and capabilities

Service interface description languages such as WSDL, and related standards, are evolving rapidly to provide a foundation for interoperation between Web services. At the same time, Semantic Web service technologies, such as the Ontology Web Language for Services (OWL-S), are developing the means by which services can be given richer semantic specifications. Richer semantics can enable fuller, more flexible automation of service provision and use, and support the construction of more powerful tools and methodologies. Both sets of technologies can benefit from complementary uses and cross-fertilization of ideas. This paper shows how to use OWL-S in conjunction with Web service standards, and explains and illustrates the value added by the semantics expressed in OWL-S.

https://eprints.soton.ac.uk/263000/1/OWL-S-SWSWPC2004-final.pdf

Bringing semantics to web services: the OWL-S approach

This document defines a notation for specifying business process behavior based on Web Services. This notation is called Business Process Execution Language for Web Services (abbreviated to BPEL4WS in the rest of this document). Processes in BPEL4WS export and import functionality by using Web Service interfaces exclusively. Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Business protocols, in contrast, use process descriptions that specify the mutually visible message exchange behavior of each of the parties involved in the protocol, without revealing their internal behavior. The process descriptions for business protocols are called abstract processes. BPEL4WS is meant to be used to model the behavior of both executable and abstract processes. BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intracorporate and the business-to-business spaces. Status of this Document This is an initial public draft release of the BPEL4WS specification. We anticipate a number of extensions to the feature set of BPEL4WS that are discussed briefly at the end of the document. BPEL4WS represents a convergence of the ideas in the XLANG and WSFL specifications. Both XLANG and WSFL are superseded by the BPEL4WS specification. BPEL4WS and related specifications are provided as-is and for review and evaluation only. BEA, IBM and Microsoft hope to solicit your contributions and suggestions in the near future. BEA, IBM and Microsoft make no warrantees or representations regarding the specifications in any manner whatsoever.

Tony Andrews

Papers

Business Process Execution Language for Web Services Version 1.1