1 / 73

Designing Semantic Web Process: The WSDL-S Approach

Designing Semantic Web Process: The WSDL-S Approach. Presented by Ke Li LSDIS Lab, University of Georgia (Under the Direction of John A. Miller). Acknowledgment. Dr. John A. Miller Dr. Amit P. Sheth Dr. Eileen T. Kraemer Kunal, Meena Doug, Zixin Cary, Scott. Outline. Introduction

chiku
Download Presentation

Designing Semantic Web Process: The WSDL-S Approach

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. Designing Semantic Web Process: The WSDL-S Approach Presented by Ke Li LSDIS Lab, University of Georgia (Under the Direction of John A. Miller)

  2. Acknowledgment • Dr. John A. Miller • Dr. Amit P. Sheth • Dr. Eileen T. Kraemer • Kunal, Meena • Doug, Zixin • Cary, Scott

  3. Outline • Introduction • Background • Contribution • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  4. Outline • Introduction • Background • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  5. Introduction • Web Service • Concept • Web Services are self-contained modular business applications that have open, internet-oriented and standards-based interface. • Web Service Standards • SOAP (Simple Object Access Protocol) • WSDL (Web Service Description Language) • UDDI (Universal Description, Discovery and Integration) • WS-BPEL (Web Service Business Process Execution Language)

  6. Introduction • Web Process • Combine individual services to achieve a more complex goal • Advantage • enables modular design • Implements the control and data flow between services • For example, Service A, B and C. B is dependent on A’s output message. A and C can be invoked at the same time

  7. Introduction • Semantic Web Service • Adding semantics to Web service standards • Bring “meaning” to the services • Removes ambiguity in the description of Web service elements. • Enables automation of tasks like discovery, invocation, composition

  8. Introduction • WSDL-S Based Tool Suite for Designing Semantic Web Process • Radiant – Web Service Semantic Annotation and Semantic Publish • Lumina – Semantic Web Service Discovery • Saros – Web Services Composition

  9. Outline • Introduction • Background • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  10. Background • Problems with current Web Service publishing, discovery and composition • No unified WSDL to UDDI mapping structure • Syntactic search mechanism for service discovery

  11. Background • Mapping Structure from WSDL to UDDI

  12. Background • Modified Mapping Structure from WSDL-S to UDDI

  13. Background • Four Semantic Web Service Standard Proposals (Brief Overview) • OWL-S • WSMO (Web Service Modeling Ontology) • SWSO (Semantic Web Service Ontology) • WSDL-S

  14. Background (OWL-S and WSMO) • OWL-S • WSMO

  15. Background (WSDL-S) • WSDL-S • Built on existing Web Service standard - WSDL • Enables semantic annotation of Web Services by using extensibility elements and attributes • Annotation on message types: modelReference, and schemaMapping • Annotation on operation: modelReference, category, precondition and effect • Uses external domain models to provide the semantics

  16. Outline • Introduction • Background • Contribution • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  17. Contribution • Design and develop the WSDL-S based semantic discovery tool called Lumina. • Develop the API for publishing WSDL / WSDL-S files to our enhanced UDDI registry. • Design the Semantic Template generator which can be used within Saros.

  18. Outline • Introduction • Background • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  19. The METEOR-S Semantic Discovery Tool - Lumina • Motivation • Support semantic discovery (WSDL-S approach) • Enable semi-automatic design of Web Processes (using Saros) • Supply a unified discovery style to discover from different Universal Business Registries

  20. The METEOR-S Semantic Discovery Tool - Lumina • Setting Environment • Web Server: Tomcat 5.0.30 • UDDI Registry Implementation: JUDDI 0.9 • Registry Database: MySQL-4.1.12-win32 • JDK 1.5 • Model Dependency • METEOR-S Discovery API • WSDLS4J • UDDI4J

  21. The METEOR-S Semantic Discovery Tool - Lumina • Discovery Modes – UDDI structure based discovery 1.General UDDI Discovery (Basic UDDI Discovery Panel) • Unified search style for all the UBRs • Provide discovery of “Business Entity”, “Business Service” and “Technical Model” • Business Entity: Business Name, Discovery URL, Categories, TModel Keys • Business Service: Service Name, Categories, Business Key, TModel Keys • TModel: TModel Name

  22. The METEOR-S Semantic Discovery Tool – Lumina – UDDI Structure Based Discovery

  23. The METEOR-S Semantic Discovery Tool – Lumina –UDDI Structure Based Discovery

  24. The METEOR-S Semantic Discovery Tool - Lumina • Discovery Modes – WSDL-S based Semantic Discovery 2. WSDL-S Discovery (WSDL-S Discovery Panel & Semantic Template View) • Input to the discovery module • Ontology URL • Operation functional concepts, semantic inputs and semantic outputs Input modes • Typed in by the user • Dragged and dropped from the Ontology Navigator in Radiant • Output from the discovery module • Service information (service name, WSDL location) • Service provider information (link to the business entity) • Detailed discovered operation information (operation name, input / output variables, ontological concepts about these parameters, input / output types, portType)

  25. The METEOR-S Semantic Discovery Tool – Lumina:Semantic Discovery Panel + Partner Service Viewer

  26. The METEOR-S Semantic Discovery Tool – Lumina:Semantic Template View

  27. The METEOR-S Semantic Discovery Tool - Lumina • Discovery Modes – WSDL based Syntactic discovery 3. WSDL Discovery (WSDL Discovery Panel) • Input to discovery module: • Exact operation name, input and output variables • Same as WSDL-S Discovery except the semantic information

  28. The METEOR-S Semantic Discovery Tool – Lumina – METEOR-S Discovery Class Diagram

  29. The METEOR-S Semantic Discovery Tool - Lumina • Architecture of Lumina • Adopts Eclipse Plugin Techniques: • Action: Lumina start button in tool bar • Editor: UDDI Editor (Basic UDDI Discovery, WSDL-S Discovery and WSDL Discovery) • View: (Semantic Template Viewer and Partner Service Viewer) • Perspective: Lumina Perspective

  30. The METEOR-S Semantic Discovery Tool – Lumina Model Class diagram

  31. The METEOR-S Semantic Discovery Tool – Lumina View Class diagram

  32. Outline • Introduction • Background • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  33. Design Semantic Web Process Using WSDL-S • Semantic Annotation and Publish – Radiant • WSDL-S to UDDI Mapping Structure

  34. Design Semantic Web Process Using WSDL-S: WSDL-S to UDDI Mapping Structure

  35. Design Semantic Web Process Using WSDL-S – Annotating a Web service using Radiant

  36. Design Semantic Web Process Using WSDL-S • Semantic Discovery – Lumina • WSDL-S Discovery Panel (UDDI Editor) and Partner Service Viewer • Store the candidate partner services to partner service viewer (convenient) • Semantic Template Viewer • Save the semantic template to files • Load a exist semantic file • Enable discovery of multiple operations • Dependence • Economic • Efficient

  37. Design Semantic Web Process Using WSDL-S: WSDL-S Discovery Panel

  38. Design Semantic Web Process Using WSDL-S: Semantic Template View

  39. Design Semantic Web Process Using WSDL-S • Semantic Web Process Design - Saros • Dynamic partner selection using the Semantic Templates that describe virtual partners • Two phase design • Generate new semantic template(s) or load the exist semantic template(s) using Semantic Template Viewer (Lumina) • Discover the partner services using the semantic templates and bind the discovered services to the process

  40. WSDL-S Semantic Template BPEL Process Process Designer Search Results Semantic Publication and Discovery UDDI Registry Design Semantic Web Process Using WSDL-S • Semantic Web Process Design - Saros

  41. Design Semantic Web Process Using WSDL-S: Saros Design Panel

  42. Outline • Introduction • Background • The METEOR-S Semantic Discovery Tool – Lumina • Design Semantic Web Process Using WSDL-S • Sample Use Case • Evaluation • Related Work • Conclusion • Future Work

  43. Sample Use Case • Sample Scenario • Goal: investment strategy for buying stock • Input: stock ticker, possible investment amount • Output: value analysis for proceeding with the investment

  44. Sample Use Case • Analyze the business requirement and build a UML diagram

  45. Sample Use Case • Fill in the process skeleton

  46. Sample Use Case 3. Fill in the nested constructs / structured activities

  47. Sample Use Case 4. Identify partners • Binding the real partners: using concrete service information • Binding the virtual partners: filling a semantic template • Discovery based on: • Operation • Input and output

  48. Sample Use Case: Search for “investment” service

  49. Sample Use Case: Search for the other two services

  50. Sample Use Case: Add virtual partner

More Related