1 / 20

OWL-S: Ontology Web Language for Services

OWL-S is an ontology and framework for describing the properties and capabilities of web services, allowing for automation of service use and reasoning/planning about services. It integrates with web services such as WSDL and UDDI. Visit http://www.daml.org/services/owl-s for more information.

dflora
Download Presentation

OWL-S: Ontology Web Language for 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. OWL-S:Brief Overview • David Martin • SRI International • Chair, OWL-S Coalition • Co-chair, Semantic Web Services Language Committee DARPA Distribution Statement “A”: Approved for Public Release, Distribution Unlimited

  2. What is OWL-S? • Ontology Web Language for Services • Under development since early 2001 • An OWL ontology for (formally) describing properties and capabilities of Web services • Plus a large body of work about using the ontology: tools, components, algorithms, extensions • An approach that draws on many sources • Description logic, AI planning, Workflow, Formal process modeling, Agents, Web services, … • Ties in with Web services (WSDL, UDDI) • http://www.daml.org/services/owl-s

  3. Contributors to OWL-S(partial list) BBN: Mark Burstein CMU: Katia Sycara, Massimo Paolucci, Naveen Srinivasan De Montfort University: Monika Solanki Maryland / College Park: Bijan Parsia, Evren Sirin NIST: Craig Schlenoff Nokia: Ora Lassila SRI: David Martin Stanford KSL: Deb McGuiness Southampton: Terry Payne Univ. of Toronto: Sheila McIlraith USC-ISI: Jerry Hobbs Yale: Drew McDermott

  4. High-Level Objectives • Automation of service use by software agents • Ideal: full-fledged use of services never before encountered • Enable reasoning/planning about services • e.g., On-the-fly composition • Build on both Semantic Web and Web services Comprehensive framework supporting the entire lifecycle of service management tasks • Discovery, selection, composition, invocation, monitoring, .. • Integrated use with information resources • Ease of use (for users and developers) • Powerful tools

  5. Layered Approach to Language Development OWL-S: an ontology expressed in OWL andrelated languages OWL-S (Services) SWRL (Rules) OWL([DLP], Light, DL, Full) RDFS (RDF Schema) RDF (Resource Description Framework) XML (Extensible Markup Language)

  6. Upper Ontology of Services Ontology images compliments of Terry Payne, University of Southampton

  7. Service Profile:“What does it do?” High-level characterization/summary of a service Used for • Populating service registries • A service can have many profiles • Automated service discovery • Service selection (matchmaking) One can derive: • Service advertisements • Service requests

  8. Service Profile

  9. Service Profile:Styles of use • Class hierarchical yellow pages • Implicit capability characterization • Arrangement of attributes on class hierarchy • Can use multiple inheritance • Relies primarily on “non-functional” properties • Process summaries for planning purposes • More explicit • Inputs, outputs, preconditions, effects • Less reliance on formal hierarchical organization • Summarizes process model specs • Relies primarily on functional description

  10. Upper Ontology of Services

  11. Process Model

  12. Service Model“How does it work?” Process Model: “How does it work?” Process • Interpretable description of service provider’s behavior • Tells service user how and when to interact (read/write messages) & Process control • Ontology of process state; supports status queries • (stubbed out at present) • Used for: • Service invocation, planning/composition, interoperation, monitoring • All processes have • Inputs, outputs, preconditions and effects • Function/dataflow metaphor; action/process metaphor • Composite processes • Control flow • Data flow • “Surface syntax” recently made available

  13. Process of Processes Output & Effects Input & Preconditions www.acmetravel.com book travel service • confirmation no. • ... • customer name • location • car type • dates • credit card no. • ... www.acmecar.com book car service ? • failure notification • … ? • confirmation no. • ... • confirmation no. • dates • room type • credit card no. • ... www.acmehotel.com book hotel service • confirmation no. • ... ? • customer name • flight numbers • dates • credit card no. • ... www.acmeair.com book flight service ? • failure notification • … • failure notification • errror information • …

  14. Upper Ontology of Services Ontology images compliments of Terry Payne, University of Southampton

  15. Service Grounding: “How to access it” • Implementation specific • Message formatting, transport mechanisms, protocols, serializations of types • Service Model + Grounding give everything needed for using the service • Builds upon WSDL

  16. OWL-S / WSDL Grounding OWL-S Resources/Concepts Process Model Inputs / Outputs Atomic Process Message Operation Binding to SOAP, HTTP, etc. WSDL

  17. OWL-S / WSDL Grounding (cont’d)

  18. Some Applications of OWL-S IBM • Provide OWL-S API as part of SNOBASE Semantic Web tool • http://www.alphaworks.ibm.com/tech/snobase • Use OWL-S for enhanced semantic UDDI SAP • Use OWL-S for automatic composition of services to manage border control Toshiba • Use OWL-S in publicly available UDDI at NTT (Main Japanese UDDI) Fujitsu • OWL-S used in Task Computing Project; planned for production in 2005 • http://www.taskcomputing.org/ NIST, DCS, TARDEC • Use OWL-S to describe capabilities of Autonomous Vehicles MyGrid • Use OWL-S to describe Bioinformatics Web services on the Grid • http://www.mygrid.org.uk/ AgentCities • OWL-S used for discovery of new agents • http://www.agentcities.org/

  19. Some Areas of Work Building on OWL-S • Architecture / components • Virtual machine • Libraries • Brokering • Mediation • Ontology management (meta-)services • Algorithms / tools • Development • Editors, WSDL2OWLS, BPEL2OWLS, BPEL augmentations • Discovery & Selection • Composition • UML-based design/generation • Ontology extensions • Security • Policy • Quality of Service • Domain-specific extensions • Semantic Grid applications • Alternate groundings • SWSF

  20. Summary & Status • Describes “what it does”, “how it works”, “how to access it” • Profile, Process, Grounding subontologies • Ties in fairly naturally with WSDL, UDDI • Additional semantics supports • Automation of various Web service tasks • Varied applications • W3C member submission • http://www.w3.org/Submission/2004/07/ • 1.1 release finalized • 1.2 release planned this year • Publications, tools, examples • See http;//www.daml.org/services/owl-s/ • ISWC, WWW, ICSOC conferences (and workshops) • Additional material (including FLOWS, WSMO, WSDL-S) here: • W3C Workshop on Frameworks for Semantics in Web Services • http://www.w3.org/2005/01/ws-swsf-cfp.html

More Related