1. Web Service Semantics - WSDL-S Meenakshi Nagarajan for the WSDL-SWSDL-S team R. Akkiraju *, J. Farrell *, J.Miller, M. Nagarajan, M. Schmidt *, A. Sheth, K. Verma "Web Service Semantics - WSDL-S" A joint UGA-IBM * Technical Note, version 1.0, April 18, 2005. http://lsdis.cs.uga.edu/projects/METEOR-S/WSDL-Shttp://lsdis.cs.uga.edu/projects/METEOR-S/WSDL-S http://www.alphaworks.ibm.com/g/g.nsf/img/semanticsdocs/$file/wssemantic_annotation.pdf

2. 2 WSDL-S Service Template Operation: buyTicket Input1: TravelDetails Output1: Confirmation Annotations Publish Search Semantic UDDI Operation: cancelTicket Input1: TravelDetails Output1: Confirmation WSDL-S : scope, proposal and the bigger picture Sivashanmugam, K., Verma, K., Sheth, A., Miller, J., Adding Semantics to Web Services Standards, ICWS 2003 Web service 1 Web service 2 Composition

3. 3 Adding semantics to WSDL – guiding principles Build on existing Web Services standards Mechanism independent of the semantic representation language Mechanism should allow the association of multiple annotations written in different semantic representation languages

4. 4 Guiding principles... Support semantic annotation of Web Services whose data types are described in XML schema Provide support for rich mapping mechanisms between Web Service schema types and ontologies

5. 5 WSDL-S Offer an evolutionary and compatible upgrade of existing Web services standards Externalize the semantic domain models –agnostic to ontology representation languages. –reuse of existing domain models –allows annotation using multiple ontologies (same or different domain) updating tools around WSDL is relatively easier

6. 6 Semantic annotations on WSDL elements Annotating message types (XSD complex types and elements) –extension attribute : modelReference (semantic association) –extension attribute : schemaMapping (schema/data mapping) Annotating operations –extension elements : precondition and effect (child elements of the operation element) –extension attribute : category (on the interface element) –extension attribute : modelreference (action) (on operation element)

7. 7 ………… <xs:element name= "processPurchaseOrderResponse" type="xs:string wssem:modelReference="POOntology#OrderConfirmation"/> http://www.naics.com/ <input messageLabel = ”processPurchaseOrderRequest" element="tns:processPurchaseOrderRequest"/> <output messageLabel ="processPurchaseOrderResponse" element="processPurchaseOrderResponse"/> <wssem:precondition name="ExistingAcctPrecond" wssem:modelReference="POOntology#AccountExists"> <wssem:effect name="ItemReservedEffect" wssem:modelReference="POOntology#ItemReserved"/> PurchaseOrder.wsdls

8. 8 Annotating operations extension element : Precondition –A set of assertions that must be satisfied before a Web service operation can be invoked “must have an existing account with this company” “only US customers can be served” extension element : Effect –Defines the state of the world/information model after invoking an operation. “item shipped to mailing address” “the credit card account will be debited” extension attribute : Category –Models a service category on a WSDL interface element. category = “Electronics” Code = “naics:443112” extension element : Action –Annotated with a functional ontology concept. action = “Rosetta:RequestQuote”

9. 9 Annotating message types - simple correspondences (...) <xs:element name= "processPurchaseOrderResponse" type="xs:string (...) Billing Account OrderConfirmation xsd:string OWL ontology has_account has_accountID WSDL message element 1:1 Correspondences results_in semantic match

10. 10 Annotating message types - complex correspondences (...)........... (...) Address StreetAddress xsd:string OWL ontology hasCity hasStreetAddress hasZip WSDL complex type element 1.modelReference to establish a semantic association 2.schemaMapping to resolve structural heterogeneities beyond a semantic match semantic match

11. 11 Using modelReference and schemaMapping Address xsd:string OWL ontology has_City has_StreetAddress has_Zip WSDL complex type element modelReference at the complex type level –Typically used when specifying complex associations at leaf level is not possible –Allows for specification of a mapping function semantic match

12. 12 modelReference at the leaf levels –assumes a 1:1 correspondence between leaf elements and domain model concepts Item dueDate ItemDesc Quantity OWL ontology hasIemDesc hasDueDate hasQuantity WSDL complex type element Using modelReference and schemaMapping

13. 13 Representing mappings Address xsd:string OWL ontology has_City has_StreetAddress has_Zip WSDL complex type element........ Mapping using XSLT

14. 14 WSDL-S in perspective

15. 15 WSDL-S evolution Action Attribute for Functional Annotation Pre and Post Conditions Can use XML, OWL or UML types Extension Adaptation schemaMapping

16. 16... <input messageLabel = ”processPurchaseOrderRequest" element="tns:processPurchaseOrderRequest"/> <output messageLabel ="processPurchaseOrderResponse" element="processPurchaseOrderResponse"/>... WSDL... <xs:complexType name="processPurchaseOrderRequest“ wssem:modelReference="POOntology#OrderDetails” > <input messageLabel = ”processPurchaseOrderRequest" element="tns:processPurchaseOrderRequest"/> <output messageLabel ="processPurchaseOrderResponse" element="processPurchaseOrderResponse"/>... WSDL - S Annotating a service UDDI Semantic Layer Publishing a service WSDL-S in the life cycle of a Web service Sivashanmugam, K., Verma, K., Sheth, A., Miller, J., Adding Semantics to Web Services Standards, ICWS 2003

17. 17 WSDL-S in the life cycle of a Web process Web Service Discovery Service 2 Template An abstract Web process WSDL-S Service 1 Template Web service 1 Web service 2 WSDL-S modelReference schemaMapping Transformation WSDL-S modelReference schemaMapping Process execution Sivashanmugam, K., Verma, K., Sheth, A., Miller, J., Adding Semantics to Web Services Standards, ICWS 2003

18. 18 WSDL-S in action ProPreO - Experimental Proteomics Process Ontology (CCRC / LSDIS) data sequence peptide_sequence Excerpt: ProPreO – process ontology <wsdl:definitions targetNamespace="urn:ngp" …… xmlns:wssem="http://www.ibm.com/xmlns/WebServices/WSSemantics" xmlns:ProPreO="http://lsdis.cs.uga.edu/ontologies/ProPreO.owl" > <schema targetNamespace="urn:ngp" xmlns="http://www.w3.org/2001/XMLSchema"> ……...... Excerpt: Bio-informatics Web service WSDLS CCRC – Complex Carbohydrate Research Center www.ccrc.uga.edu ProPreO - http://lsdis.cs.uga.edu/projects/glycomics/propreo/www.ccrc.uga.edu

19. 19 WSDL-S collaborations Meteor-S collaboration with WSMOMeteor-S –Using WSDL-S for grounding Web services annotated with WSML ontologies Influencing OASIS / W3C Requestor’s goal Service capability WSDL-S WSML Kunal Verma, Adrian Mochan, Michal Zaremba, Amit Sheth, John Miller, Christoph Bussler, Linking Semantics Web service Efforts - Integrating WSMX and METEOR-S, Second International Workshop on Semantic and Dynamic Web Processes, July 2005Linking Semantics Web service Efforts - Integrating WSMX and METEOR-S, Second International Workshop on Semantic and Dynamic Web Processes, July 2005

20. 20 WSDL-S annotatorWSDL-S annotator - Radiant

21. 21 Why WSDL-S ? Approach simple, light-weight, upwardly compatible with the existing WSDL standard –practical for adoption Approach agnostic to semantic representation language –reuse of domain models –flexibility in choice of modeling language –annotation with multiple ontologies Ease in tool upgrades –e.g. wsif / axis invocation More on METEOR-S Web site