UT DALLAS Erik Jonsson School of Engineering & Computer Science FEARLESS engineering Semantic Web Services CS - 6V81 University of Texas at Dallas November 23, 2009 Presented by- Rohit Sharma

FEARLESS engineering Agenda!!! 1.Picture? 2.Why? 3.What? 4.Types? 5.Tasks? 6. Structure? 7.Conclusion

FEARLESS engineering Picture ?

FEARLESS engineering Picture ?

FEARLESS engineering Why? Syntactic Interoperability [Before] Semantic Meaning of Messages [After] Great access of Content [Before] Great access of Services [After] OK, 2 points aint sufficient son. *Cough* [ LOL ]  Wait NOOB.

FEARLESS engineering Why? Users & Software Agents –Discover [Web Resources] –Locate [Web Resources] –Invoke [Web Resources] –Compose [Web Resources] –Monitor [Web Resources] –Particular Services –Particular Properties Do all of the above with high degree of automation I am LOST , so what is Semantic Web Services?

FEARLESS engineering What? Component of Semantic Web [It is] Conventional Web Service [Just Like] Server End of Client-Server System [which is] Machine-to-Machine Interaction [for] Via World Wide Web [using] Any Technical Term or Ontology for this? OWL-S: Semantic Markup for Web Services Can I go home I am getting Migraine ………

FEARLESS engineering Types? Atomic *Simple* –Single Computer Program, Sensor, or Device –Invoked by a Request Message –Performs its Task –Produces a Single Response –No Ongoing Interaction Composite *Complex* –Composed of Multiple More Primitive Services –Extended Interaction

FEARLESS engineering Tasks? Automatic Web Service Discovery –Automated Process for Location of Web Services –Provide a Particular Class of Service Capabilities –While Adhering to some Client-Specified Constraints What The Hell? Automatic Web Service Invocation –Automatic Invocation of Web Service by Program/Agent –Given Only a Declarative Description of that Service Explain or Sue !!! Automatic Web Service Composition & Interoperation Involves Automatic Selection, Composition & Interoperation To Perform some Complex Task Given a High-Level Description GRRRRR *Nerd Rage*

FEARLESS engineering Structure? Motivated by the Need to Provide 3 Types of Knowledge *each characterized by the question it answers* 1.What Does the Service Provide for Prospective Clients? --- Service Profile It is used to Advertise the Service The Service Profile tells “What the Service Does“ Helps a Service-Seeking Agent To Determine Whether the Service Meets its Needs

FEARLESS engineering Structure? Motivated by the Need to Provide 3 Types of Knowledge *each characterized by the question it answers* 2. How is it used? --- Service Model Uses the property “describedBy” Tells a Client How to Use the Service, by Detailing the Semantic Content of Requests The Conditions Under which Particular Outcomes will Occur The Step by Step Processes Leading to Those Outcomes

FEARLESS engineering Structure? Motivated by the Need to Provide 3 Types of Knowledge *each characterized by the question it answers* 3. How does one interact with it? --- Service Grounding Provides the Needed Details about Transport protocols Specifies Input, Output & Way of Exchanging Data

FEARLESS engineering Visualization !!

FEARLESS engineering Conclusion: OWL-S is an Ontology for describing Web Services Enable Users and Software Agents to do a LOT (their way) Better place where people can not only find information but also get things done

FEARLESS engineering References: 1. atalogAssetStore/813_81302_1_33145.htm TC D-F.jpg Belhajjame, K., Embury, S.M., Paton, N.W., Stevens, R. and Goble, A.C., (April 2008). "Automatic Annotations of Semantic Web Services Based on Workflow Definitions". ACM Transactions on the Web 2 (2): 1–34

FEARLESS engineering Rohit Sharma Contact:

FEARLESS engineering Thank You: ITS OVER? OMG YAYYYYYYYYYYY