1 / 60

Semantic Web Services

This lecture discusses the motivation and technical solution of Semantically Enabled Service-oriented Architecture (SESA) with a focus on the Web Service Execution Environment (WSMX). It covers topics such as design principles, lifecycle, architecture, execution semantics, and provides an illustration with a larger example.

kinneyjames
Download Presentation

Semantic Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Semantic Web Services Web Service Execution Environment (WSMX) Lecture VIII – 14th May 2009 Srdjan Komazec

  2. Where are we?

  3. Outline • Motivation • Semantically Enabled Service-oriented Architecture (SESA) • Technical solution • Introduction • Relation to the WSMO and WSML • Design principles • Lifecycle • Web Service Execution Environment (WSMX) • Architecture • Components • System entry points • Execution semantics • Illustration by larger example

  4. Motivation

  5. MotivationSemantically Enabled Service-oriented Architecture • Service Orientation • Service-Oriented Computing (SOC) • Services as the fundamental elements for the development of rapid, low-cost, and easily integrable enterprise applications, • Service-Oriented Architecture (SOA) • SOC can be abstractly implemented by SOA, • From function to object to service, • SOA requirements: loose coupling, implementation neutrality, flexible configuration, long lifetime, granularity and teams. • Existing technologies and SOA solutions are… • … difficult to scale without a proper degree of automation, • … partial solution to interoperability. • SESA represents SOA empowered by adding semantics as a means to deal with heterogeneity and mechanization of service usage.

  6. MotivationSemantically Enabled Service-oriented Architecture • Application of SESA offers a scalable integration, more adaptive to changes • service offerings and required capabilities are described by semantically rich and formal service models, • exchanged data is also semantically described, and • reasoning provides total or partial automation of tasks. • A SESA implementation should build a layer on top of the existing technologies (e.g. Web Services). WSMX is an implementation of SESA.

  7. MotivationSESA Architecture Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  8. Motivation • Middleware for Semantic Web Services • Allows service providers to focus on their business, • Reference implementation for WSMO • Eat our own cake, • Environment for goal based discovery and invocation • Run-time binding of service requesters and providers, • Provide a flexible Service Oriented Architecture • Add, update, remove components at run-time as needed, • Keep open-source to encourage participation • Developers are free to use in their own code, and • Define formal execution semantics • Unambiguous model of system behavior.

  9. Technical solution

  10. IntroductionRelation to WSMO and WSML Conceptual Model & Axiomatization for SWS Formal Language for WSMO Semantic Execution Environment Ontology & Rule Language for the Semantic Web

  11. IntroductionWSMX… • … is comprehensive software framework for runtime binding of service requesters and service providers, • … interprets service requester’s goal to • discover matching services, • select (if desired) the service that best fits, • provide data/process mediation (if required), and • make the service invocation, • … is reference implementation for WSMO, • … has a formal execution semantics, and • … is service oriented, event-based and has pluggable architecture • Open source implementation available through Source Forge, • based on microkernel design using technologies such as JMX.

  12. IntroductionDesign principles • Service-oriented principle • Service reusability, loose coupling, abstraction, composability, autonomy, discoverability, • Semantic Principle • Rich and formal description of information and behavioral models enabling automation of certain tasks by means of logical reasoning, • Problem-solving principle • Goal-based discovery and invocation of services, and • Distributed principle • Executing process across a number of components/services over the network, thus promoting scalability and quality of process.

  13. Lifecycle • Discovery - determines usable services for a request, • Composition - combine services to achieve a goal, • Selection - chooses most appropriate service among the available ones, • Mediation- solves mismatches (data, protocol, process) hampering interoperation, • Choreography – interactions and processes between the service providers and clients, • Grounding – lifting and lowering between the semantic and syntactic data representations, and • Invocation -invokes Web service following programmatic conventions.

  14. WSMXCurrent middleware status

  15. WSMX Components

  16. WSMX ComponentsCommunication Manager, Invoker and Grounding • Responsible for interaction with services and entities that are external to WSMX. • Should be open to support as many transport and messaging protocols as possible (transparently to WSMX). • WSMX uses • The SOAP implementation from Apache AXIS, and • The Apache Web Service Invocation Framework (WSIF) . • Both RPC and Document style invocations possible Grounding Invoker SOAP XML WebService MediatedWSML Data ApacheAXIS Network

  17. WSMX ComponentsGrounding • WSMO service descriptions are grounded to WSDL by the means of XSLT lifting and lowering Jacek Kopecký et al. D24.2v0.1. WSMO Grounding, WSMO Working Draft 27 April 2007. http://wsmo.org/TR/d24/d24.2/v0.1

  18. WSMX ComponentsGrounding - Example <xsl:stylesheet version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:p="http://www.wsmo.org/sws-challenge/ShipmentOntologyProcess#" xmlns:muller="http://www.example.org/muller/" exclude-result-prefixes="#all" xmlns:helper="java:ie.deri.wsmx.commons.Helper"> <xsl:output method="xml" omit-xml-declaration="yes"/> <xsl:template match="/muller:invokePriceResponse"> <xsl:variable name="randomId" select="helper:getRandomId()"/> <rdf:RDF> <rdf:Description about="http://example.com/testresponse{$randomId}"> <rdf:type rdf:resource="http://www.wsmo.org/sws-challenge/ShipmentOntologyProcess#PriceQuoteResp"/> <p:price rdf:datatype="http://www.w3.org/2001/XMLSchema#decimal"><xsl:value-of select="number(./muller:price)"/></p:price> </rdf:Description> </rdf:RDF> </xsl:template> </xsl:stylesheet> An example of lifting XML data to RDF

  19. WSMX ComponentsDiscovery • Responsible for finding appropriate Web Services capable of fulfilling a goal • Different techniques available • trade-off: ease-of-provision vs. accuracy • resource descriptions & matchmaking algorithms • Key Word Matching • - match natural language key words in resource descriptions, • Controlled Vocabulary • - ontology-based key word matching, and • Semantic Matchmaking • - what Semantic Web Services aim at. Ease of provision Possible Accuracy

  20. WSMX ComponentsDiscovery – Key Word Matching • Allows for a fast filtering and ranking of the huge number of available services rather quickly. • Nonfunctional properties from the Dublin Core namespace (e.g. dc#description) are candidates for indexing and querying. • Dictionaries of synonyms (WordNet) can be used to discover more services. wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-rule" namespace {_"http://www.wsmo.org/sws-challenge/WSMuller#", dc _"http://purl.org/dc/elements/1.1#"} webService WSMuller nfp dc#title hasValue "Muller Web Service" dc#description hasValue "We ship to Africa, North America, Europe, Asia (all countries)." dc#contributor hasValue "Maciej Zaremba, Matt Moran, Tomas Vitvar, Thomas Haselwanter" endnfp capability WSMullerCapability ...

  21. X WSMX ComponentsDiscovery – Simple Semantic Description = G = WS • Exact Match: • G, WS, O, M ╞ x. (G(x) <=> WS(x) ) • PlugIn Match: • G, WS, O, M ╞ x. (G(x) => WS(x) ) • Subsumption Match: • G, WS, O, M ╞ x. (G(x) <= WS(x) ) • Intersection Match: • G, WS, O, M ╞ x. (G(x) WS(x) ) • Non Match: • G, WS, O, M ╞ ¬x. (G(x) WS(x) ) Keller, U.; Lara, R.; Polleres, A. (Eds): WSMO Web Service Discovery. WSML Working Draft D5.1, 12 Nov 2004.

  22. WSMX ComponentsDiscovery – Simple Semantic Description - Example Generic goals Specific goals Domain knowledge Web services Lara, R., Lausen, H (Eds): WSMO Discovery Engine. WSML Working Draft D5.2, 26 Nov 2004.

  23. WSMX ComponentsDiscovery – Simple Semantic Description - Example • Exact match • Plug-in match • Subsumption match • Intersection match

  24. WSMX ComponentsRanking and Selection • One service which best satisfies the user preferences is selected from the candidate services returned by the service discovery. • Selection • determines best candidate out of discovered WS, • Ranking • determines a priority list of discovered WS. • The process is run after “functional” discovery • Criteria: • Quality of Service (security, robustness, availability), • Context (regional, business / social communities), • Preferences and policies, • Financial criteria, • …

  25. WSMX ComponentsRanking and Selection • Ontologies for specifying QoS. http://www.wsmo.org/ontologies/nfp/ • set of 17 ontologies (i.e. locative, temporal, availability, price, trust, security, etc.)‏ • provide the terminology needed to specify QoS aspects of services

  26. WSMX ComponentsAttaching non-functional properties descriptions to services • Model • Example

  27. WSMX ComponentsRanking and Selection - Example • Extension of SWS Challenge Shipment Scenario • Discounts and obligations modeled for all services in the scenario

  28. WSMX ComponentsData Mediation • Ontology-to-ontology mediation • A set of mapping rules are defined and then executed • Ontology Mapping Language • Initially rules are defined semi-automatic • Create for each source instance the target instance(s) Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  29. WSMX ComponentsData Mediation • Design-time • Inputs • Source Ontology and Target Ontology • Features • Graphical interface • Set of mechanism towards semi-automatic creation of mappings • Capturing the semantic relationships identified in the process • Storing these mappings in a persistent storage • Output • Abstract representation of the mappings • Run-time • Main Mediation Scenario: Instance Transformation • Inputs • Incoming data • Source ontology instances • Features • Completely automatic process • Grounding of the abstract mappings to a concrete language • WSML • Uses reasoner to evaluate the mapping rules • Outputs • Mediated data • Target ontology instances

  30. WSMX ComponentsData Mediation - Example wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight" namespace { _"http://deri.org/iswc2005tutorial/ontologies/travel2#"} ontology travel2 concept travelVoucher type ofType _string bearer ofType name toFrom ofType tripPoints departureDate ofType date arrivalDate ofType date departureTime ofType time arrivalTime ofType time terms ofType payment deliveryDate ofType date ... wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight" namespace { _"http://deri.org/iswc2005tutorial/ontologies/travel1#"} ontology travel1 concept ticket type ofType _string departure_cityofType _string departure_codeofType _string arrival_cityofType _string arrival_codeofType _string departure_dateofType date arrival_dateofType date departure_timeofType time arrival_timeofType time issuing_termsofType terms firstNameofType _string lastNameofType _string ... Source ontology Destination ontology

  31. WSMX ComponentsData Mediation - Example <Alignment> <dc:identifier rdf:resource="m2"/> <onto1> <formalism name="WSML" uri="http://www.wsmo.org/wsml"/><uri>http://deri.org/iswc2005tutorial/ontologies/travel1#travel1</uri> </onto1> <onto2> <formalism name="WSML" uri="http://www.wsmo.org/wsml"/><uri>http://deri.org/iswc2005tutorial/ontologies/travel2#travel2</uri> </onto2> <map> … <Cell id="http://deri.org/iswc2005tutorial/ontologies/travel1#tickethttp://deri.org/iswc2005tutorial/ontologies/travel2#travelVoucher"> <entity1> <Class rdf:about="http://deri.org/iswc2005tutorial/ontologies/travel1#ticket"></Class> </entity1> <entity2> <Class rdf:about="http://deri.org/iswc2005tutorial/ontologies/travel2#travelVoucher"></Class> </entity2> <measure>1.0</measure> <relation>ClassMapping</relation> </Cell> … </map> </Alignment> Mapping between two concepts

  32. WSMX ComponentsData Mediation - Example wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight" namespace { _"http://deri.org/iswc2005tutorial/ontologies/travel2#"} ontology travel2 instance expected_travelVoucher memberOf travelVoucher departureDate hasValue expected_departureDate terms hasValue expected_payment arrivalDate hasValue expected_arrivalDate bearer hasValue expected_name departureTime hasValue expected_departureTime arrivalTime hasValue expected_arrivalTime type hasValue "flight" wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight" namespace { _"http://deri.org/iswc2005tutorial/ontologies/travel1#”} ontology travel1 instance my_ticket_input memberOf ticket type hasValue "flight" firstName hasValue "Adrian" lastName hasValue "Mocan" arrival_date hasValue my_arrival_date departure_date hasValue my_departure_date arrival_time hasValue my_arrival_time departure_time hasValue my_departure_time departure_city hasValue "Innsbruck" departure_code hasValue "INN" arrival_city hasValue "Rome" arrival_code hasValue "RO" issuing_terms hasValue my_terms Source instances Destination instances

  33. WSMX ComponentsProcess Mediation • Requester and provider have their own communication patterns • Only if the two match precisely, a direct communication may take place • At design time equivalences between the choreographies’ conceptual descriptions is determined and stored as set of rules • The Process Mediator provides the means for runtime analyses of two choreography instances and uses mediators to compensate possible mismatches

  34. WSMX ComponentsProcess Mediation Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  35. WSMX ComponentsProcess Mediation - Example • Not a priori compatible behavior interfaces for communication & information interchange • Partially resolvable by “process mediation patterns” ? Figure taken from Emilia Cimpian, D13.7 v0.1 Process Mediation in WSMX, WSMX Working Draft 08 July 2005

  36. WSMX ComponentsProcess Mediation - Example x

  37. WSMX ComponentsChoreography • Requester and provider have their own observable communication patterns • Choreography part of WSMO • Choreography instances are loaded for the requester and provider • Both requester and provider have their own WSMO descriptions • Abstract State Machines (ASM)-based Choreography Engine • Evaluation of transition rules • prepares the available data • Sends data to the Process Mediator • filters, changes or replaces data • Receives data from PM and forwards it to the Communication manager • data to be finally sent to the communication partner

  38. WSMX ComponentsChoreography - Example choreography WSMullerShipmentOrderChoreography stateSignature WSMullerShipmentOrderStateSignature … in sop#ShipmentOrderReq withGrounding { _"http://sws-challenge.org/shipper/v2/muller.wsdl#wsdl.interfaceMessageReference(muller/ShipmentOrder/in0)"} in so#ContactInfo in so#ShipmentDate in so#Package in so#Address out sop#ShipmentOrderResp transitionRules WSMullerShipmentOrderTransitionRules forall {?request} with (?request memberOf sop#ShipmentOrderReq) do add(_#1 memberOf sop#ShipmentOrderResp) delete(?request memberOf sop#ShipmentOrderReq) endForall S1 <shipmentOrderReq(soi#MoonContactInfo, soi#shipmentDate1, package, soi#SzyslakContactInfo), package(1, 7.0, 6.0, 4.0, 1.0), shipmentDate1(“2009-01-21T13:00:00.046Z”, "2009-01-22T13:00:00.046Z")> S2 <shipmentOrderResp(“2009-01-21T15:00:00.046Z”, 65.03), package(1, 7.0, 6.0, 4.0, 1.0), shipmentDate1(“2009-01-21T13:00:00.046Z”, "2009-01-22T13:00:00.046Z")>

  39. WSMX ComponentsResource Manager • Stores internal memory model to a data store • Decouples storage mechanism from the rest of WSMX • Data model is compliant to WSMO API • Independent of any specific data store implementation i.e. database and storage mechanism • Maintains six repositories to store • WSMO top level entities, i.e. • Goals, • Web Service descriptions, • Mediators, and • Ontologies. • Event data and intermediate messages • WSDL descriptions

  40. WSMX ComponentsA Generic Framework for Reasoning with WSML Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  41. Execution Semantics

  42. Execution Semantics • Formal description of the operational behavior of the system in terms of computational steps • Greater flexibility in SESA implementations, • Foundations for model testing, • Executable representation, and • Improved model understanding among humans. • Mandatory execution semantics • Goal-Based Web Service Discovery • Web Service Invocation • Goal-Based Service Execution

  43. Execution SemanticsGoal-Based Web Service Discovery Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  44. Execution SemanticsWeb Service Invocation Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  45. Execution Semantics Goal-Based Service Execution Fensel, D.; Kerrigan, M.; Zaremba, M. (Eds): Implementing Semantic Web Services: The SESA Framework. Springer 2008.

  46. Illustration by larger example

  47. Illustration by larger exampleScenario description • The goal is to discover a suitable solution for the transportation of a package with defined size and weight • Candidate Web Services have different constraints regarding the transportation destinations, package size and weight acceptance, as well as pricing schemas • For more information visit: • http://sws-challenge.org/wiki/index.php/Scenario:_Shipment_Discovery

  48. Illustration by larger exampleGoal description I want to have my package shipped from CA, USA to Tunis, Africa size (7/6/4), weight 1 lbs, the cheaper the better. wsmlVariant _"http://www.wsmo.org/wsml/wsml-syntax/wsml-flight" goal GoalA1 capability GoalA1Capability postcondition definedBy ( ?x[sop#pricehasValue ?price] memberOfsop#PriceQuoteResp and sop#isShipped(shipmentOrderReq) ). interface GoalA1Interface choreography GoalA1Choreography stateSignature GoalA1StateSignature in sop#ShipmentOrderReq out sop#ShipmentOrderResp transitionRules GoalA1TransitionRules forall {?request} with (?request memberOfsop#ShipmentOrderReq) do add(_#1 memberOfsop#ShipmentOrderResp) endForall ontology GoalRequest instance shipmentOrderReqmemberOfsop#ShipmentOrderReq sop#fromhasValuesoi#MoonContactInfo sop#shipmentDatehasValue soi#shipmentDate1 sop#packagehasValue package sop#tohasValuesoi#SzyslakContactInfo instance package memberOfso#Package so#quantityhasValue 1 so#lengthhasValue 7.0 so#widthhasValue 6.0 so#heighthasValue 4.0 so#weighthasValue 1.0 instance shipmentDate1 memberOfso#ShipmentDate so#earliesthasValue "2009-01-21T13:00:00.046Z" so#latesthasValue "2009-01-22T13:00:00.046Z"

  49. Illustration by larger exampleAchieveGoal execution semantics

  50. Illustration by larger exampleAchieveGoal execution semantics Goal expressedin WSML is sent to theWSMX Entry Point

More Related