daml-s coalition daml pi meeting 10/16/02 daml-s briefing daml-s web services coalition presented...

DAML-S Coalition DAML PI Meeting 10/16/02

DAML-S BriefingDAML-S Web Services Coalition

Presented by:

David Martin (SRI)Sheila McIlraith (Stanford KSL)

Terry Payne (Southampton)

http://www.daml.org/services/


DAML-S Web Services Coalition

BBN: Mark Burstein

CMU: Massimo Paolucci, Katia Sycara

ICSI: Srini Narayanan

Nokia: Ora Lassila

Stanford KSL: Sheila McIlraith

SRI: David Martin

Southampton: Terry Payne

USC-ISI: Jerry Hobbs

Yale: Drew McDermott


OutlineDAML-S technical overview & update

Overview of ontology areasProfile, process model, grounding

Progress to dateChallenges, next stepsDirections for 2002-2003

Key challenges (Sheila McIlraith)Joint committee plans (Katia Sycara)


Convergence on Services• Commercial vendors, media, forecasters, etc.

– Intranets, not just internets

• W3C Web services efforts• Semantic Web community

– DAML-S; WSMF & other EU efforts– ISWC: 10 services-related papers, 7 posters

• Grid computing (OGSA)• Ubiquitous computing (devices)

– Mobile access to services

A remarkable opportunity– Bringing behavioral intelligence to the Web


DAML-S: DAML for web Services

A DAML+OIL ontology/language for (formally) describing properties and capabilities of Web services

DAML-??? (Rules, FOL?)

XML (Extensible Markup Language)

RDF (Resource Description Framework)

RDFS (RDF Schema)

DAML+OIL OWL (Ontology)

DAML-S (Services)


DAML-S ObjectivesAutomation of service use by software agents

Ideal: full-fledged use of services never before encountered:discovery, selection, composition, invocation, monitoring

Useful in the “real world”Compatible with industry standardsIncremental exploitation

Enable reasoning/planning about servicese.g., On-the-fly composition

Integrated use with information resourcesEase of use; powerful tools


Automation Enabled by DAML-S

• Web service discovery Find me a shipping service that transports goods to Dubai.

• Web service invocation Buy me 500 lbs. powdered milk from www.acmemoo.com

• Web service selection & composition

Arrange food for 500 people for 2 weeks in Dubai.

• Web service execution monitoring Has the powdered milk been ordered and paid for yet?


Upper Ontology of Services

Ontology images compliments of Terry Payne, University of Southampton


High-level characterization/summary of a serviceUsed for

• Populating service registries• A service can have many profiles

• Automated service discovery• Service selection (matchmaking)

One can derive:• Service advertisements• Service requests

Service Profile: “What does it do?”


Service ProfileNon Functional Non Functional PropertiesProperties

Functionality Functionality DescriptionDescription


Styles of use

• Class-hierarchical yellow pages– Implicit capability characterization

– Arrangement of attributes on class hierarchy

– Can use multiple inheritance

• Process summaries for planning purposes– More explicit

– Inputs, outputs, preconditions, effects

– Less reliance on formal hierarchical organization

– Summarizes process model specs

Profile: Recent evolution


Exploiting Taxonomies of ServicesServiceProfile

ProductProvidingService

Manufacturing

Transportation

ActionService

InfoService

PhysicalProductService Repair

InformationProduct+

physicalProduct+manufacturer+

deliveryRegion*deliveryProvider*

deliveryType

Physical_Product+

transportationMode+geographicRegion+

physicalProduct+

Tie in with UDDI, UNSPSC, …DL Basis for matchmakingMultiple profiles; multiple taxonomies

nameprovider

role+avgResponseTime?

…

FeeBased feeBasis+paymentMethod+


Service 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

Process Model: “How does it work?”


Service Model / Process Model


AcmeTruckShpng

www.acmeair.com

book flight service

• customer name• flight numbers• dates• credit card no.• • ...

• confirmation no.• ...

• failure notification• errror information• …

?

www.acmehotel.com

book hotel service

• confirmation no.• dates• room type• credit card no.• ...


• failure notification• …

?

www.acmecar.com

book car service

• customer name• location• car type• dates• credit card no.• ...


• failure notification• …

?

• • • •

Composite Process

• • • • • • • • • •

• • • •

?

• • • • • • • • • • •

Input &Preconditions

Output &Effects

• • • •

• • • •


• Conditional outputs & effects

• Parameter bindings<rdf:Description rdf:about="#FullCongoBuy">

<sameValues rdf:parseType="daml:collection"> <ValueOf atClass="#FullCongoBuy“ theProperty="#fullCongoBuyBookISBN"/> <ValueOf atClass="#LocatedBookOutput“ theProperty="outInCatalogBookISBN"/> <ValueOf atClass="#CongoBuyBook“ theProperty="#congoBuyBookISBN"/></sameValues>

Pushing the limits of DAML+OIL expressiveness

Process Model: Recent evolution


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

• Examples: HTTP forms, SOAP, KQML, CORBA IDL, OAA ICL, Java RMI


DAML-S / WSDL Grounding

• Web Services Description Language– Authored by IBM, Ariba, Microsoft– Focus of W3C Web Services Description WG– Commercial momentum– Specifies message syntax accepted/generated

by communication ports– Bindings to popular message/transport

standards (SOAP, HTTP, MIME)– Abstract “types”; extensibility elements

• Complementary with DAML-S


DL-based Types

WSDL

DAML-S

Process Model

Atomic Process

Operation Message

Inputs / Outputs

Binding to SOAP, HTTP, etc.


DAML-S / WSDL Grounding (cont’d)


Review: Upper Ontology of Services


Path of EvolutionRelease 0.5 (May 2001)

Initial Profile & Process ontologies

Release 0.6 (December 2001)Refinements to Profile & ProcessResources ontology

Two approaches to formal semanticsSycara/Ankolekar, McIlraith/Narayanan

Release 0.7 (October 2002)DAML-S/WSDL GroundingProfile, Process Model refinementsMore complete examples

Towards 1.0Expressiveness issues; process modeling; industry tie-in


Related ActivitiesWeb site & mailing lists

http://www.daml.org/services/[email protected]

UsersUMCP (Hendler/Parsia), UMBC (Finin), Manchester (Goble), CMU (Sadeh), Lockheed-

Martin, Ultralog, beta-reviewers, …

ToolsDAML-S publications

WWW10 SW Workshop (2), SWWS, WWW11, Coordination 2002, AAMAS, ICSW (4), IEEE Computer, IEEE Intel. Systems…

W3C Web services activitiesDesignated liaison for WS Arch. WG; Katia Sycara

ExperimentUse cases


Challenges• Finding the “80/20” line• Profiles: relationship with processes• Process modeling: many issues

– Variability of public/private aspects of Processes– Extending to offline (sub)processes– Generalizing to multiple roles– Failure, transactions

• Where and how to go beyond DAML+OIL?– Interface between DL ontology, logical expressions, algorithm/workflow

representation

• Connecting with Industry– Showing compelling value– Not promising too much– Providing an incremental path


Next steps / prioritiesFocus on use cases architectureJoint committee forming …Move to OWLModel information servicesProfile: More substantial illustrative taxonomies

Tie in with existing taxonomies where possible (e.g. UNSPSC)

Process ModelEvaluate potential tie-in with an existing effort (WSFL?)

Support real-world useDescribing and using public WSDL servicesPossible collaborations with other SemWeb projectsDemos directed towards Web services community

Tools DAML-S API


What’s Next for DAML-S:2 Key Challenge Areas

Presenter: Sheila McIlraith

Stanford

Knowledge Systems Laboratory


• Expressiveness of DAML+OIL

• DAML-S Industry Trends complementary compatible influential

Current Challenges


Expressiveness & Semantics

Problem: DAML+OIL has a well-defined semantics, butit is not sufficiently expressive to characterize all and onlythe intended interpretations of DAML-S.




Solution 1:A. Distributed operational semantics via Petri Nets.





B. Interleaving function-based operational semantics w/ subtype polymorphism.






C. Semantics via translation to first-order logic.






C. Semantics via translation to first-order logic.

Solution 2: DAML Rules?


Wire Protocols

Description Discovery

TCP/IP

HTTP/SMTP/BEEP

XML

SOAP/XMLP

SOAP Blocks

XML

WSDL

WSDL Extensions

Process

Agreements

Inspection

Registry (UDDI)

Modification of slide by James Snell (IBM)

Industry Trends: The Web Services Stack


Wire Protocols


TCP/IP

HTTP/SMTP/BEEP

XML

SOAP/XMLP

SOAP Blocks

XML

WSDL

WSDL Extensions

Inspection

Registry (UDDI)

Modification of slide by James Snell (IBM)

Process

AgreementsD

A

M

L

S

InvocationInteroperationCompositionMonitoringVerification

Automated

Industry Trends: The Web Services Stack


Wire Protocols


TCP/IP

HTTP/SMTP/BEEP

XML

SOAP/XMLP

SOAP Blocks

XML

WSDL

WSDL Extensions

Agreements

Inspection

Registry (UDDI)

D

A

M

L

S

InvocationInteroperationCompositionMonitoringVerification

Automated

Industry Trends: The Web Services StackModification of slide by James Snell (IBM)

Process

W3C WS Choreograph GroupBPEL4WS (Microsoft, IBM, BEA)WSCL (HP)BPML (Most but Microsoft)WSCI (Sun, BEA, Yahoo, …)XLANG (Microsoft), WSFL (IBM), …


• “Services/Rules” (Web Services: Expressiveness Issues & Industry Trends)

Breakout Sessions

• “Service Use Cases”


Joint US Europe Semantic Web Services Committee

Presenter: Katia Sycara

Carnegie Mellon University


Objectives

• Bring together US and European Semantic Web Services researchers

• Engage in collaborative standardization efforts– DAML-S language– Semantic Web Services Architecture

• Possible outcome is a W3C Note


Overall Structure

• Language Technical Committee – Co-chairs: David Martin and TBD

• Architecture Technical Committee– Co-chairs: Mark Burstein and Christoph Bussler

• Industrial Advisory Board• Advisory Committee

– Murray Burke, Hans-Georg Stork, Jim Hendler

• Coordinating Committee– Co-chairs: Dieter Fensel and Katia Sycara


ISWC2003

• http://iswc2003.semanticweb.org

• Location: Sundial Resort, Sanibel Island, Fla, USA

• Dates:: 20-23 October 2003

• Paper Submission Date: April 15, 2003

• Workshop Proposals Submission Date: December 16, 2002

• Tutorial Proposal Submission Date: Feburary 28, 2003

• Demo Proposal Submission Date: July 13, 2003


ISWC2003Organizing Committee

• General Chair: Dieter Fensel

• Program Chair: Katia Sycara

• Program Co-Chair: John Mylopoulos

• Tutorial Chair: Asun Gomez-Perez

• Workshop Chairs: Sheila McIlraith and Dimitris Plexousakis

• Industrial Track Chair: Christoph Bussler

• Poster Chair: Raphael Malyankar

• Finance Chair: Jerome Euzenat

• Publicity Chair: Mike Dean

• Local Arrangements Chair: Jeff Bradshaw

• Sponsor Chairs: Ying Ding and Massimo Paolucci

• Registration Chair: Atanas Kyriakov

• Demo Chair: Jeff Heflin

daml-s coalition daml pi meeting 10/16/02 daml-s briefing daml-s web services coalition presented...

Documents

damls web service discovery

daml oil ontologylanguage

web slide

web service invocation

shipping service

fullfledged use of services

populating service registries

katia sycara slide