1. Towards Semantic Interoperability: In-depth Comparison of Two Approaches to Solving Semantic Web Service Challenge Mediation Tasks Tomas Vitvar, Marco Brambilla tomas.vitvar@deri.org, marco.brambilla@polimi.it The 9th International Conference on Enterprise Information Systems Madeira, Portugal, 2007 Maciej Zaremba, Tomas Vitvar, Matthew Moran, Marco Brambilla, Stefano Ceri, Dario Cerizza, Emanuele della Valle, Federico Facca, Christina Tziviskou

2. 2 Overview SWS Challenge Scenario DERI Solution – WSMO, WSML, WSMX Politecnico di Milano + CEFRIEL Solution – WebML, Glue Comparision and Conclusion

3. 3 Scenario Moon company wants to build B2B integration with Blue company Blue – RosettaNet to be integrated with Moon back-end CRM and OMS

4. 4 Scenario: Blue RosettaNet Blue sends purchase order (customer id, and items to be ordered) and expects order confirmation with confirmation id Blue uses RosettaNet Standard PIP3A4 for Purchase Orders POC[confirmationID PO[id, item1, item2, item3]

5. 5 Scenario: Moon Back-end Systems Internal customer id must be obtained from CRM system based on provided ID by Blue Order must be opened in OMS system Individual items are placed in OMS Order is closed in OMS id cid openOrder addItem* closeOrder

6. 6 Scenario: Interoperability Problems Interoperability Problems: –Incompatible XML schemas for Blue’s and Moon’s messages –Incompatible processes of Blue’s and Moon’s systems Id’ cid openOrder addItem* closeOrder POC[confirmationID PO[id, item1, item2, item3] Data Interoperability Process Interoperability

7. 7 Overview Mediation Scenario DERI Solution – WSMO, WSML, WSMX Politecnico di Milano + CEFRIEL Solution – WebML, Glue Comparision and Conclusion

8. 8 SWS: WSMO, WSML, WSMX Semantic Web Services in DERI –SWS: WSMO, WSML, WSML community Effort driven by DERI EU FP6 and national funding Web Service Modelling… … Ontology -> WSMO –Conceptual model for SWS: goal, ontologies, mediators, services … Language -> WSML –Ontology Language for SWS –WSML Variants: WSML Core, WSML DL, WSML Rule, WSML Full … Execution Environment and Architecture -> WSMX –Middleware platform for SWS –Now in OASIS SEE TC

9. 9 Scenario: WSMX to Facilitate Integration Modelling of information and behaviour of standard RosettaNet definitions Modelling of information and behaviour of proprietary back-end systems

10. 10 Scenario: What to model WSMO Ontology WSMO Service WSMO Ontology WSMO Service RosettaNet PIP 3A4 CRM, OMS systems Grounding

11. 11 Scenario: Deploy Models and Ontology Mappings WSMO Ontology WSMO Service WSMO Ontology WSMO Service RosettaNet PIP 3A4 CRM, OMS systems mapping rules Grounding

12. 12 RosettaNet PIP 3A4 WSMO Ontology: Modelling of Information Web Service XML Schema WSMO Ontology Lifting Schema Mapping Lowering Schema Mapping Lifting Rules in XSLT

13. 13 RosettaNet PIP 3A4 WSMO Service: Modelling of Choreography, Grounding Web Service WSMO Choreography and Grounding Definition WSDL Web Service Operations, Input and output messages a b stateSignature in a → wsdl.interfaceMessageReference … out b → wsdl.interfaceMessageReference … … transitionRules If a then add(b) … Abstract State Machine Rules If message A is in the memory, then add message B to the memory from invocation of related operation.

14. Conversation: Process and Data Mediation Mapping Rules WSMO Ontology (Moon-CRM/OMS) WSMO Ontology (Blue-PIP3A4) a ↔ o, b ↔ p, c ↔ q, d ↔ r Data Mediator Process Mediator Choreography Engine blue Send PO Receive POC GetCustomer OpenOrder AddItem CloseOrder 14 moon

15. 15 Overview Mediation Scenario DERI Solution – WSMO, WSML, WSMX Politecnico di Milano + CEFRIEL Solution – WebML, Glue Comparision and Conclusion

16. The WebML-SWEET framework SWSWebML S emantic W eb S ervice Application 16

17. Model-driven design for WSMO WSML Goal WSML WS Choreography WSML WS Capability WSML Ontology Ontology importing and/or semantic annotation Automatic code generation Business process modeling WF-driven WebML generator Web application modeling BPMN model WebML skeleton Running application WebML Data model WebML hypertext model WSML Ontology Generator WSML WS Capabilty Generator WSML WS Chor. Generator WSML Goal Cap. Generator The SWE-ET is a top-down approach to the development of applications employing Semantic Web Services, that combines semantic methods and tools with Software Engineering ones. 17

18. Semantics-enabled data models @ participants (enriched E-R models vs. ontologies) Lowering and lifting implemented through XSLT transformations: –Participant model  XML messages 18 WebML Data Mediation

19. WebML-WSMO Choreography Choreography interface of the service can be extracted from the description and registered in a Semantic Execution Environment (i.e. WSMX) 19

20. WebML – WSMO capabilities 20

21. 21 Overview Mediation Scenario DERI Solution – WSMO, WSML, WSMX Politecnico di Milano + CEFRIEL Solution – WebML, Glue Comparision and Conclusion

22. IssueWebML/ WebRatioWSMO/ WSMX Data modelingEnriched EROntologies Data mediationXSLT-based mapping and lifting/ lowering Design-time onto-onto mapping. Bidirectional XML-WSML lifting/lowering. Process modelingBPMN/WebML of services and a mediator Ontologized ASM of each service’s choreography Process mediation Execution of WebML mediator Execution of service’s choreographies Web services publishing and invocation Generic units for publishing and invocation. AXIS Services published on WSMX, invocation according to the grounding Comparison 22

23. Two different approaches to semantic mediation –WebML: starting from a software engineering background. Focus on design time –WSMO: starting from semantic web experience. Focus on runtime dynamic integration Most explicit evidence –WebML: design-time process mediation model, based on BPMN –WSMO: no design-time process mediation model; runtime dynamic process mediation 23 Conclusions

24. 24 Thanks!