A Logic-based Approach to Web Services Composition and Verification using OWL-S

Bouvanesswary Alibert.S,Niranjannya.G, Reka.P Sri Manakula Vinayagar Engineering College, Madagadipet, Puducherry bouvanaa@gmail.com, niranjannya.4@gmail.com,rekap1213@gmail.com Abstract Service consumers would have different degrees of satisfaction on a service and a collection of these impressions over a period of time within a network give service reputation. The Semantic Web should enable greater access not only to content but also to services on the Web. In this project, we will focus on OWL-S as underlying language for annotating Web Services. OWL-S provides an ontological framework based on which an abstract description of a service can be created. It is an upper ontology whose root class is the Service class that directly corresponds to the actual service that is described semantically (every service that is described maps onto an instance of this concept).Each OWL-S process is based on an IOPR model. Key Words:
Web Services; Ontology; IOPR; Semantic Web;

It also states that we can identify two major classes of web services, REST-compliant web services, in which the primary purpose of the service is to manipulate XML representations of web resources using a uniform set of stateless operations, and arbitrary web services, in which the service may expose an arbitrary set of operations. The term Web services describes a standardized way of integrating web-based applications using the XML, SOAP, WSDL and UDDI open standards over an internet protocol backbone. XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available and UDDI is used for listing what services are available. Used primarily as a means for businesses to communicate with each other and with clients, web services allow organizations to communicate data without intimate knowledge of each other's IT systems behind the firewall. 2. OWL-S Automatic Web service discovery: with the development of the Semantic Web, many Web Services will be available on the Web, performing the most various tasks. OWL-S will help software agents to discover the Web Service that would fulfill a specific need within some quality constraints, without the need for human intervention. Automatic Web service invocation: generally, it is necessary to write a specific program to invoke a Web Service, using its WSDL description. OWL-S will open the possibility for a software agent to automatically 1

1. Introduction The web service as a software system designed to support interoperable machine-tomachine interaction over a network. It has an interface described in a machine-process able format (specifically Web Services Description Language WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Webrelated standards.

read the description of the Web Service's inputs and outputs and invoke the service. Automatic Web service composition and interoperation: in a Web where many services are available, it should be possible to perform a complex task, involving the coordinated invocation of various Web Services, based solely on the high-level description of the objective. OWL-S will help in the composition and interoperation of the Services in a way that will enable the automatic execution of this task. OWL-S is such ontology of service concepts. OWL-S organizes a service description into four conceptual areas: the service, the profile, the process model, and the grounding. The service simply binds the other parts together into a unit that can be published and invoked. The profile provides a general description of the Web Service, intended to be published and shared to facilitate service discovery. Profiles can include both functional properties (inputs, outputs, preconditions, and results) and non-functional properties (service name, text description, contact information, service category and additional service parameters). The functional properties are derived from the process model. The process model describes how the service performs its tasks and it includes information about the service's inputs, outputs (including a specification of the conditions under which various outputs will occur), preconditions (circumstances that must hold before the service can be used) and results (changes brought about by the service). For a complex, composed service, the process model shows how it breaks down into simpler component processes, and the flow of control and data between them. The grounding specifies how the service is invoked, by detailing how the atomic processes in the process model map onto WSDL representations. 3. Designing the user interface framework

In this module Design the interface for the user to interact with the application. Each and every software application needs fine steps to interact with end users of the application. In this application the interaction with end users are made under jsp concepts. Our approach is to provide a simple user interface for invoking Web services. We have designed a general interface, as opposed to the use of forms specific to each domain as is currently implemented by many Web services invocation systems 4. Description of Web Services In this module, the ontology files are used to describe the concepts and relationships that can exist for an agent or a community of agents. This definition is consistent with the usage of ontology as set-of-concept definitions, but more general. In this scenario, it is fundamental to connect ontology concepts the database, each one of them being connected to one/several items. We consider three types of concepts: leaf-concepts, generalized concepts and restriction concepts proposed only by ontologies. 4.1 Leaf-Concept The leaf-concepts are defined as connected in the easiest way to database each concept is associated to one item in the database. 4.2 Generalized Concept Generalized concepts are described as the concepts that subsume other concepts in the ontology. A generalized concept is connected to the database through its subsumed concepts. This means that, recursively, only the leafconcepts subsumed by the generalized concept contribute to its database connection 4.3 Restriction Concept

Restriction concepts are described using logical expressions defined over items and are organized in the subset. In a first attempt, we base the description of the concepts on restrictions over properties available in description logics. Thus, the restriction concept defined could be connected to a disjunction of items. 5. Web service composition This task involves the automatic composition, and interoperation of Web services to perform some complex task, given a highlevel description of an objective. For example, the user may want to make all the travel arrangements for a trip to a conference. Currently, the user must select the Web services, specify the composition manually, and make sure that any software needed for the interoperation of services that must share information is custom-created. With OWL-S markup of Web services, the information necessary to select and compose services will be encoded at the service Web sites. 6. Implementation of Output match algorithm In our system, depending on the results of the output matching algorithms, relevant Web services are invoked and executed without further involvement of the user in the overall process. 7. Implementation Output match algorithm (see Figure 2), which traverses all the elements in output and output S. To find the most matching services, the maximum time complexity has to be O(n2), n is dimension of service outputs. OutputMatch(outputQ,outputS){ CurrentMatchDegree=Exact; /*first assign the match degree as max*/ For all outQ in outputQ{ Find the outS in outputS which has the most 3

match degree with output, marked as MatchDegree; If(matchdegree==Level5) return fail; Elseif(MatchDegree< CurrentMatchDegree) CurrentMatchDegree= MatchDegree } } Figure 1 Output match algorithm

Figure 2 Getting the keyword and concept

Figure 3 Web Service Compositions

Figure 4 Ranking Display

Figure 5 Service Display 8. Related Work There are many approaches which dont adopt established specification languages, like BPEL, they usually propose different modifications, thus imposing more difficulties to implement the system. Instead, [4] presents a policy-driven approach for enabling Web services adaptability through a semantic modification in the invocation primitive of BPEL4WS, whilst maintains its syntax unaffected. For the requirements of the composition solution, such as real-time, automatic, reliable, [6] proposes a service composition approach based on Petri nets modeling technique. It facilitates automatic and goal-driven creation of composite Web services. However, the scale of the reachable set of Petri net is growing exponentially, which means the low scalability of Petri net. 4

Discovery of services only by IO isnt a precise way, and [9] presents a precise and decidable matching Method based on the description logic reasoning, targeting merely the informationproviding type of Web services. It is a nice exploration, but signature and specification matching is to dive deeper into detail of IO. [12] Presents an approach that integrates service composition into service discovery and matchmaking, discusses general issue involved in describing and matching such services and presents an efficient algorithm implementing the idea. [10] Presents an approach to automatically generate data processing workflows. It defines a methodology for assigning formal semantics to data and operations according to a domain ontology, which allows sharing and reusing. But these two methods dont mention verification of the composition; its a key problem before invoking services practically. Based on many solutions proposed, [5] presents an analysis that includes formalization of the WSCE process, a classification of existing solutions into four distinct categories and an in-depth evaluation of these approaches after systematically analyzing the strengths and weaknesses of the solutions. Also it presents an application of this analysis to three different scenarios.
10. Conclusion and Future enhancement

This paper proposes a complete approach to compose and verify Web services, involving description, composition, selection and verification. OWL-S is such ontology of service concepts based on IOPR model. Since an OWLS process may have several results with corresponding outputs, the Result entity of the IOPR model provides a means to specify this situation. Each result can be associated to a result condition, called inCondition that specifies when that particular result can occur. Therefore, an inCondition binds inputs to the corresponding outputs. As the problem is divided into two sub problems, the efficiency and effect are improved. This paper involves the

composition of different services and also selected service is matched with candidate services using output match algorithm. The future enhancement includes the same concept can be achieved with increasing speed and also frequently visited links can be stored in the database for future references. The approach is regarded as a meaningful research. References [1]Raman Kazhamiakin, Marco Pistore, Static Verification of Control and Data in Web Service Compositions, International Conference on Web Services, 2006, pp.83-90. [2]Hai Huang and Rick A. Mason, Model Checking Technologies for Web Services, Proceedings of the the Fourth IEEE Workshop on Software Technologies for Future Embedded and Ubiquitous Systems, and the Second International Workshop on Collaborative Computing, Integration, and Assurance (SEUSWCCIA' 06), 2006, pp. 217-224. [3]Melliti Tarek, Celine Boutrous-Saab, Sylvain Rampacek, Verifying correctness of Web services choreography, Proceedings of the European Conference on Web Services, 2006, pp.306-318. [4]Fernando Antonio Aires Lins, Jose Carlos dos Santos Junior, PNelson Souto Rosa, Adaptive Web Service Composition, ACM SIGSOFT Software Engineering Notes, vol.32, no.4, 2007, pp.6-13. [5] Vikas Agarwal, Girish Chafle, Sumit Mittal, Biplav Srivastava, Understanding Approaches for Web Service Composition and Execution, Proceedings of the 1st Bangalore annual computer conference, 2008, pp.1-8. [6]Dmytro Zhovtobryukh, A Petri Net-based Approach for Automated Goal-Driven Web Service Composition, Simulation, vol. 83, no.1, 2007, pp.33-63. [7]Berardi D, Calvanese D, Giacomo GD, etc. Automatic Composition of Services That Export Their Behavior, Proc. 1st Intl Conf. 5

Service-Oriented Computing (ICSOC 03), LNCS 2910, Springer-Verlag,2003, pp. 4358. [8]Amy Moormann Zaremski, Jeannette M, Specification Matching of Software Components, ACM Transactions on Software Engineering and Methodology (TOSEM), vol.6, no. 4, 1997. Pp.333 -369 [9]Wen-feng Zhao and Jun-liang Chen, Toward Automatic Discovery and Invocation of Information- Providing Web Services, The Semantic Web-ASWC 2006, pp. 474-480. [12]Ulrich Kuster, Birgitta KonigRies, Mirco Stern and Michael Klein, DIANE An Integrated Approach to Automated Service Discovery, Matchmaking and Composition, Proceedings of the 16th international conference on World Wide Web, May. 2007, pp. 10331042. [10]Jose Luis Ambite, PDipsy Kapoor, Automatic generation of data processing workflows for transportation modeling, Proceedings of the 8th annual international conference on Digital government research, May.2007. Pp.82-91 [11]Lamport L, Specifying Systems: The TLA+ Language and Tools for Hardware and Software Engineers, Addision-Wesley, Boston, July 2002. [12]MIT,Larch Prover,http://nms.lcs.mit.edu/larch/LP/overview .html. [13]W3C, OWL-S, http://www.w3.org/Submission/2004/SUBMOWL-S-20041122/. [20]OASIS, BPEL, http://docs.oasisopen. org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html. [14]W3C, WS-CDL, http://www.w3.org/TR/2005/CRws-cdl-1020051109/