YASA-M: a Semantic Web Service Matchmaker

YASA-M: a Semantic Web Service Matchmaker

YASA-M : a semantic Web service matchmaker Yassin Chabeb, Samir Tata, Alain Ozanne To cite this version: Yassin Chabeb, Samir Tata, Alain Ozanne. YASA-M : a semantic Web service matchmaker. 24th IEEE International Conference on Advanced Information Networking and Applications (AINA 2010):, Apr 2010, Perth, Australia. pp.966 - 973, 10.1109/AINA.2010.122. hal-01356801 HAL Id: hal-01356801 https://hal.archives-ouvertes.fr/hal-01356801 Submitted on 26 Aug 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. YASA-M: A Semantic Web Service Matchmaker Yassin Chabeb, Samir Tata, and Alain Ozanne TELECOM SudParis, CNRS UMR Samovar, Evry, France Email: fyassin.chabeb, samir.tata, [email protected] Abstract—In this paper, we present new algorithms for match- This paper is organized as follows. Section II presents a state ing Web services described in YASA4WSDL (YASA for short). of the art of semantic matching approaches. In Section III, We have already defined YASA that overcomes some issues we give an overview of our service description language then missing in WSDL or SAWSDL. In this paper, we continue on our contribution and show how YASA Web services are we detail our service matching algorithm. Section IV presents matched based on the specificities of YASA descriptions. Our the implementation and the experiments of the proposed matching algorithm consists of three variants based on three algorithms for service matching. Finally, we conclude this different semantic matching degree aggregations. This algorithm paper and present our future work. was implemented in YASA-M, a new Web service matchmaker. YASA-M is evaluated and compared to well known approaches II. STATE OF THE ART for service matching. Experiments show that YASA-M provides better results, in terms of precision, response time, and scalability, Research efforts in matching of semantic Web services try than a well known matchmaker. to identify matching degrees for relationships between the semantic concepts that describe the elements of services and I. INTRODUCTION requests (e.g. input, output). In this section, we present a state of the art of the elementary matching. It focuses on Web services are running through the Web and based matching at one time only one and same part of both the on standards such as SOAP for message transport, WSDL requested and the offered sides (e.g. one requested input for service description, and UDDI for service advertisement and one offered input). Global matching is computed from and discovery. It is now obvious that the lack of seman- all matching results. Therefore, elementary matching degrees tic descriptions in WSDL prevents automatic discovery and are aggregated to compute global matching degree between hence automatic invocation and composition [1], [2]. To deal requested and offered services. Related works are classified with these issues several approaches were developed. They according to their elementary matching principle, especially, use semantic models (ontologies, etc.) for the description of their matching degrees categories. semantic Web services. We can cite among others, OWL-S The matching approaches depend on the parts of the service [3], SAWSDL [4] and WSMO [5]. description to match; some approaches focuses on service pro- In our works, we are interested in the description of semantic cess, some others are interested in service profile (functional, Web services which is based on the de-facto standard to non-functional, etc.) or both of them. The matching can be describe Web services, namely WSDL. In a previous work, performed in various ways. It can be logic-based or not. When we have presented YASA4WSDL [6] (YASA for short), an ex- it is based on text similarity measurement, on structured graph tension of SAWSDL for semantic description of Web services. matching, or path-length-based similarity of concepts, then it is YASA requires no other changes to existing WSDL or XML called non logic-based matching. Whereas when it is based on Schema documents, or to the way in which they had been deductive approach, it is called logic-based matching. Match- used previously. YASA uses two types of ontologies. The first ing approaches that use a combination of logical and non- one, called Technical Ontology Type, concerns ontologies that logical mechanisms are called hybrid matching approaches. describe service concepts (e.g. interface, input and output) and In the following, we present the most recent contribution to ontologies that describe non functional concepts of services logic-based, non-logic-based, and hybrid matching. (e.g. QoS and context information). The second ontology A. Logic-based Matching type, called Domain Ontology Type, concerns ontologies that define the semantics of the service business domain (e.g. This category uses concepts from ontologies and logical tourism, health, trade...). YASA was motivated mainly by rules. Matching degrees are defined differently depending on our opinion that such a language will provide facilities for semantics of matched description elements. There are mainly automatic service discovery, composition and enactment. In three matching approaches: this paper, we continue on our contribution and show how • IO-matching: so called ”service profile IO-matching”. Web services described in YASA are discovered. We present in It concerns data semantics of input (I) and output (O) detail our semantic matching algorithm which consists of three service parameters. This type of matching is adopted in variants based on three different semantic matching degree [7], [8], and [9]. aggregations. Implementations were evaluated and compared • PE-matching: this category concerns the matching of ser- to well known approaches for Web service matching. vice/request preconditions (P) and effects (E). This type of matching is adopted in PCEM [10] with preconditions ones are hybrid and includes additional computation of syn- and effects are specified in Prolog. tactic similarity values: subsumed-by and nearest-neighbor. In • IOPE-matching: this category of approaches makes use of WSMO-MX [18], the matchmaker accepts as inputs services preconditions and effects as well as inputs and outputs. specified in WSML-MX [19]. The matching is based on This category of matching is adopted in [11], [12], [13], the ”Intentional matching of services” in [12], the Object- and [14]. oriented graph matching of the matchmaker DSD-MM [15], In [9], the authors propose four matching degrees. Let A and OWLS-MX hybrid semantic matching [17]. The match- be an advertised service and R a requested service, then ing degrees are computed by aggregated valuations of four in addition to the common degrees ”Exact” and ”Fail”, the matching elements: ontology-based type, logical constraint, re- authors propose the ”Plug-in” degree if Output(A) subsumes lation name, and syntactic similarity. The degrees of semantic Output(R), i.e. Output(A) is a set that includes Output(R), and matching of WSMO service and goal (requested service) types the ”Subsumes” degree if Output(R) subsumes Output(A), i.e. are: ”equivalence”, ”plugin”, ”inverse-plugin”, ”intersection”, the provider does not completely fulfill the request but it likely ”fuzzy similarity”, ”neutral” and, ”disjunction” (fail) [19]. needs to modify its plan or perform other requests to complete The SAWSDL-MX [20] matchmaker is inspired by OWLS- its task [9]. The algorithm of matching compares the request MX [17] and WSMO-MX [18]. It is based on logic-based to the advertised services. It matches one by one their inputs matching (subsumption reasoning: ”Exact”, ”Subsumes”, and and outputs and records those which matched maximally but ”Subsumed-by”) as well as IR-based (text retrieval) match- it is not obvious that, allowing requester to (1) constraining ing. The syntactic similarity between offered operation and the minimal acceptable degree and (2) restricting concepts of requested operation is an average of the similarity between search will always offer efficient matching process. This may the input vectors and the output vectors. The syntactic-based leads to matching fails either by not choosing the favorable degrees ”Subsumed-by” and ”Nearest-neighbor” depend on degree or the right concepts, and then it would be necessary selected text similarity measure: Loss-of-Information (LOI), to execute one or more times again the request. Extended Jaccard (ExtJacc), Cosine (Cos), or Jensen-Shannon In [11], for each input, output, and service category, there (JS) [20]. is a different interpretation for different degrees: in addition In SAWSDL, as there is no explicit mention of precondition to ”Equivalent” and ”Fail” degrees, the authors propose ”Un- and effects, SAWSDL Matchmakers still match in the same known” and ”Subsumes” degrees. The first is used when the way, for example, semantic annotation on service precondition result of matching could not be known. The second denotes and semantic annotation on service results. Same problems all other matching cases. Consequently, this approach does persist for

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    10 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us