Using WSDL/UDDI and DAML-S in Web Service Discovery

1
Using WSDL/UDDI and DAML-S in Web Service
Discovery

• Aphrodite Tsalgatidou
• National and Kapodistrian University of Athens
• Email afrodite_at_di.uoa.gr
• http//www.di.uoa.gr/afrodite

2
WS Discovery The problem
(1) Service Description
Service Provider
(2) Publishing
(3) Description of Req. needs
Invocation/Binding
Service Requestor
Service Broker
(4) Matchmaking
3
WS Discovery Requirements
Description Publishing Description of Req. Needs Matchmaking
HOW DAML-S, XML, keywords, Scalable, Secure, Available, DAML-S, XML, keywords, Scalable, Secure, Available, By composition, keywords, inference
WHO Program, Developer, Business user Program, Developer, Business user Developer, Business user Program, Developer, Business user
WHEN/HOW LONG N/A Persistent, With lease N/A Design-time, run-time, persistent query, volatile query
WHAT See next slide See next slide See next slide See next slide
WHERE N/A Local, Corporate, Global N/A Local, Corporate, Global
4
WHAT reqs more specifically
W3C Stack Layer Attributes
Business level agreements
Service level agreements
Composition Conversations, Transactions
Orchestration Conversations, Transactions
Presentation Type of output (e.g. WAP)
Policy Preconditions, Effects, Domain(s), Cost, Security, Constraints (geographical, time or based on other attributes), Performance, Reliability, Information about the service provider
Implementation Description Network address
Interface Description service Name, Short service description, input/output messages, Operations, bindings, interaction pattern, synchronicity, exceptions
XML Schema
5
WSDL/UDDI
Description Publishing Description of Requestor Needs Matchmaking
HOW DAML-S, XML, keywords, Scalable, Secure, Available, DAML-S, XML, keywords, Scalable, Secure, Available, By composition, keywords, inference
WHO Program, Developer, Business user Program, Developer, Business user Developer, Business user Program, Developer, Business user
WHEN/HOW LONG N/A Persistent, With lease N/A Design-time, run-time, persistent query, volatile query
WHAT See next slide See next slide See next slide See next slide
WHERE N/A Local, Corporate, Global N/A Local, Corporate, Global
6
WSDL/UDDI and WHAT reqs
W3C Stack Layer Attributes
Business level agreements
Service level agreements
Composition Conversations, Transactions
Orchestration Conversations, Transactions
Presentation Type of output (e.g. WAP)
Policy Preconditions, Effects, Domain(s), Cost, Security, Constraints (geographical, time or based on other attributes), Performance, Reliability, Information about the service provider
Implementation Description Network address
Interface Description service Name, Short service description, input/output messages, Operations, bindings, interaction pattern, synchronicity, exceptions
XML Schema
7
The DAML-S approach
Description Publishing Description of Req. Needs Matchmaking
HOW DAML-S, XML, keywords, Scalable, Secure, Available, DAML-S, XML, keywords, Scalable, Secure, Available, By composition, keywords, inference
WHO Developer, Business user Program, Developer, Business user Developer, Business user Program, Developer, Business user
WHEN/HOW LONG N/A Persistent, With lease N/A Design-time, run-time, persistent query, volatile query
WHAT See next slide See next slide See next slide See next slide
WHERE N/A Local, Corporate, Global N/A Local, Corporate, Global
8
DAML-S and WHAT reqs
W3C stack Layer Attributes
Business level agreements
Service level agreements
Composition Conversations, Transactions
Orchestration Conversations, Transactions
Presentation Type of output (e.g. WAP)
Policy Preconditions, Effects, Domain(s), Cost, Security, Constraints (geographical, time or based on other attributes), Performance, Reliability, Information about the service provider
Implementation Description Network address
Interface Description service Name, Short service description, input/output messages, Operations, bindings, interaction pattern, synchronicity, exceptions
XML Schema
9
Evaluation of DAML-S (1/2)

• Issues related to the language specification
• Issues inherited from the Semantic Web

10
Evaluation of DAML-S (2/2)

• Generality of descriptions
• Possible inconsistency between the ServiceProfile
  and the ServiceModel
• Lack of tools that enable the definition of all
  three aspects of a Daml-s description
• Lawlessness in ontologies
• Inability to compare preconditions and effects
• Tricky comparison on the non-functional
  attributes
• Maturity issue

11
Future Work

• Expand the survey by examining composition and
  standards (such as BPEL4WS, WSCL, WSRP, ) and
  see how they can be combined with other standards
  in order to meet the specified requirements
• Examine DAML-S 0.9, OWL
• Investigate the merging of UDDI/WSDL and DAML-S
  activities
• Extend our discovery mechanism prototype to
  address as many requirements as possible and
  evaluate the standards