Semantic Web Services

Tutorial
Michael Stollberg and Armin Haller
DERI – Digital Enterprise Research Institute

3rd International Conference on Web Services (ICWS 2005)

Orlando, Florida, 2005 July 11
 Agenda
Part I: Introduction to Semantic Web Services
– Vision of Next Generation Web Technology

– Semantic Web Service Challenges

Part II: The Web Service Modeling Ontology WSMO

– Aims & Design Principles

– Top Level Element Definitions

BREAK

Part III: A Walkthru Example

– Virtual Travel Agency Example

– Roles, Elements, Semantic Web Service technology usage

Part IV: The Web Service Execution Environment WSMX

– Aims & Design Principles

– Architecture & Components

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 PART I:
Introduction to Semantic Web
Services

• The vision of the Semantic Web

• Ontologies as the basic building block

• Current Web Service Technologies

• Vision and Challenges for Semantic Web Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 The Vision
– 500 million users
– more than 3 billion pages

Static
WWW
URI, HTML, HTTP

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 The Vision
Serious Problems in
• information finding,
• information extracting,
• information representing,
• information interpreting and
• and information maintaining.

Static
WWW Semantic Web
URI, HTML, HTTP RDF, RDF(S), OWL

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 The Vision

Dynamic Web Services

UDDI, WSDL, SOAP Bringing the computer back
as a device for computation

Static
WWW Semantic Web
URI, HTML, HTTP RDF, RDF(S), OWL

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 The Vision
Bringing the web to its full potential

Dynamic Web Services Semantic Web

UDDI, WSDL, SOAP Services

Static
WWW Semantic Web
URI, HTML, HTTP RDF, RDF(S), OWL

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 The Semantic Web
• the next generation of the WWW

• information has machine-processable and

machine-understandable semantics

• not a separate Web but an augmentation of

the current one

• Ontologies as basic building block

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 Ontology Definition

unambiguous conceptual model

terminology definitions of a domain
(ontological theory)

formal, explicit specification of a shared conzeptualization

commonly accepted
machine-readability
understanding
with computational
semantics

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

Ontology Example
name email
Concept
conceptual entity of the Person research
domain matr.-nr.
field
isA – hierarchy (taxonomy)

Property
Student Professor
attribte describing a
concept attends holds

Relation Lecture

relationship between lecture

topic
concepts or properties nr.

holds(Professor, Lecture) =>

Axiom [Link] = [Link]
coherency description
between Concepts /
Properties3rd/Internation
Relations via
Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
logical expressions
 1

Ontology Technology
To make the Semantic Web working we need:
• Ontology Languages:
– expressivity
– reasoning support
– web compliance

• Ontology Reasoning:
– large scale knowledge handling
– fault-tolerant
– stable & scalable inference machines

• Ontology Management Techniques:

– editing and browsing
– storage and retrieval
– versioning and evolution Support

• Ontology Integration Techniques:

– ontology mapping, alignment, merging
– semantic interoperability determination

• and … Applications

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

Web Services
• loosely coupled, reusable components
• encapsulate discrete functionality
• distributed
• programmatically accessible over
standard internet protocols
• add new level of functionality on top of the
current web

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

The Promise of Web Services

web-based SOA as new system design paradigm

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

WSDL
• Web Service Description Language
• W3C effort, WSDL 2 final construction phase

describes interface for

consuming a Web Service:
- Interface: operations (in- & output)
- Access (protocol binding)
- Endpoint (location of service)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

UDDI
• Universal Description, Discovery, and Integration Protocol
• OASIS driven standardization effort

Registry for
Web Services:
- provider
- service information
- technical access

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

SOAP
• Simple Object Access Protocol
• W3C Recommendation

XML data transport:

- sender / receiver
- protocol binding
- communication aspects
- content

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

Deficiencies of WS Technology
• current technologies allow usage of Web Services
• but:
– only syntactical information descriptions
– syntactic support for discovery, composition and execution
=> Web Service usability, usage, and integration needs to be
inspected manually
– no semantically marked up content / services
– no support for the Semantic Web

=> current Web Service Technology Stack failed to

realize the promise of Web Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

Semantic Web Services

Semantic Web Technology
• allow machine supported data interpretation
• ontologies as data model

Web Service Technology

automated discovery, selection, composition,
and web-based execution of services

=> Semantic Web Services as integrated solution for

realizing the vision of the next generation of the Web

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 1

Semantic Web Services

• define exhaustive description frameworks for
describing Web Services and related aspects
(Web Service Description Ontologies)
• support ontologies as underlying data model to
allow machine supported data interpretation
(Semantic Web aspect)
• define semantically driven technologies for
automation of the Web Service usage process
(Web Service aspect)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

Semantic Web Services

Usage Process:
• Publication: Make available the description of the capability
of a service
• Discovery: Locate different services suitable for a given
task
• Selection: Choose the most appropriate services among
the available ones
• Composition: Combine services to achieve a goal
• Mediation: Solve mismatches (data, protocol, process)
among the combined
• Execution: Invoke services following programmatic
conventions
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

Semantic Web Services

Execution support:

• Monitoring: Control the execution process

• Compensation: Provide transactional support and undo or

mitigate unwanted effects

• Replacement: Facilitate the substitution of services by

equivalent ones

• Auditing: Verify that service execution occurred in the

expected way

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

PART II:
The Web Service Modeling
Ontology WSMO
• Aims & Working Groups
• Design Principles
• Top Level Notions
– Ontologies
– Web Services
– Goals
– Mediators
• Comparison to OWL-S

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

WSMO is ..
• a conceptual model for Semantic Web Services:
– ontology of core elements for Semantic Web Services
– a formal description language (WSML)
– execution environment (WSMX)

• derived from and based on the Web Service

Modeling Framework WSMF

• a SDK-Cluster Working Group

(joint European research and development initiative)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

WSMO Working Groups

A Conceptual Model
for SWS

A Formal Language for WSMO Execution Environment

for WSMO
A Rule-based Language for SWS

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

WSMO Design Principles

• Web Compliance
• Ontology-Based
• Goal-driven
• Strict Decoupling
• Centrality of Mediation
• Description versus Implementation
• Execution Semantics

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

WSMO Top Level Notions

Objectives that a client wants to
achieve by using Web Services

Provide the Semantic description of

formally specified Web Services:
terminology - Capability (functional)
of the information - Interfaces (usage)
used by all other
components

Connectors between components

with mediation facilities for handling
heterogeneities

WSMO D2, version 1.2, 13 April 2005 (W3C submission)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

Non-Functional Properties
every WSMO elements is described by properties that
contain relevant, non-functional aspects

• Dublin Core Metadata Set:

– complete item description
– used for resource management
• Versioning Information
– evolution support
• Quality of Service Information
– availability, stability
• Other
– Owner, financial

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

Non-Functional Properties List

Dublin Core Metadata Quality of Service
Contributor Accuracy
Coverage NetworkRelatedQoS
Creator Performance
Description Reliability
Format Robustness
Identifier Scalability
Language Security
Publisher Transactional
Relation Trust
Rights Other
Source Financial
Subject Owner
Title TypeOfMatch
Type Version
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 2

WSMO Ontologies
Objectives that a client wants to
achieve by using Web Services

Provide the Semantic description of

formally specified Web Services:
terminology - Capability (functional)
of the information - Interfaces (usage)
used by all other
components

Connectors between components

with mediation facilities for handling
heterogeneities

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Ontology Usage & Principles

• Ontologies are used as the ‘data model’ throughout
WSMO
– all WSMO element descriptions rely on ontologies
– all data interchanged in Web Service usage are ontologies
– Semantic information processing & ontology reasoning

• WSMO Ontology Language WSML

– conceptual syntax for describing WSMO elements
– logical language for axiomatic expressions (WSML Layering)

• WSMO Ontology Design

– Modularization: import / re-using ontologies, modular approach for
ontology design
– De-Coupling: heterogeneity handled by OO Mediators
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Ontology Specification
• Non functional properties (see before)
• Imported Ontologies importing existing ontologies
where no heterogeneities arise
• Used mediators OO Mediators (ontology import with
terminology mismatch handling)

Ontology Elements:
Concepts set of concepts that belong to the ontology, incl.
Attributes set of attributes that belong to a concept
Relations define interrelations between several concepts
Functions special type of relation (unary range = return value)
Instances set of instances that belong to the represented ontology
Axioms axiomatic expressions in ontology (logical statement)
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

WSMO Web Services

Objectives that a client wants to
achieve by using Web Services

Provide the Semantic description of

formally specified Web Services:
terminology - Capability (functional)
of the information - Interfaces (usage)
used by all other
components

Connectors between components

with mediation facilities for handling
heterogeneities

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

WSMO Web Service Description

- complete item description
- quality aspects - Advertising of Web Service
- Web Service Management - Support for WS Discovery

Non-functional Properties Capability

DC + QoS + Version + financial functional description

client-service realization of
interaction interface functionality by
for consuming WS Web Service WS
aggregating
- External Visible Implementation other Web Services
WS
Behavior (not of interest in Web - functional
Service Description) decomposition
- Communication WS
Structure - WS composition
- ‘Grounding’
Choreography --- Service Interfaces --- Orchestration
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Capability Specification
• Non functional properties
• Imported Ontologies
• Used mediators
– OO Mediator: importing ontologies with mismatch resolution
– WG Mediator: link to a Goal wherefore service is not usable a priori
• Pre-conditions
What a web service expects in order to be able to
provide its service. They define conditions over the input.
• Assumptions
Conditions on the state of the world that has to hold before
the Web Service can be executed
• Post-conditions
describes the result of the Web Service in relation to the input,
and conditions on it
• Effects
Conditions on the state of the world that hold after execution of the
Web Service (i.e. changes in the state of the world)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Choreography & Orchestration

• VTA example:
When the service is When the service
requested requests

Date, Time
Date
Hotel
Hotel Service
Time

Error
Flight, Hotel
VTA
Date, Time
Error Service

Confirmation Flight
Flight Service

Error

• Choreography = how to interact with the service to

consume its functionality
• Orchestration = how service functionality is achieved
by aggregating other Web Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Choreography Aspects
Interface for consuming Web Service
• External Visible Behavior
– those aspects of the workflow of a Web Service where Interaction is
required
– described by workflow constructs: sequence, split, loop, parallel
• Communication Structure
– messages sent and received
– their order (communicative behavior for service consumption)
• Grounding
– executable communication technology for interaction
– choreography related errors (e.g. input wrong, message timeout, etc.)
• Formal Model
– reasoning on Web Service interfaces (service interoperability)
– allow mediation support on Web Service interfaces

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Orchestration Aspects
Control Structure for aggregation of other Web Services
Web Service Business Logic

State in Orchestration
Control Flow
1
WS Data Flow
Service Interaction
3

- decomposition of
4 WS service functionality
- all service interaction via
choreographies

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

WSMO Web Service Interfaces

• service interfaces are concerned with service consumption
and interaction
• Choreography and Orchestration as sub-concepts of
Service Interface
• common requirements for service interface description:
1. represent the dynamics of information interchange during service
consumption and interaction
2. support ontologies as the underlying data model
3. appropriate communication technology for information interchange
4. sound formal model / semantics of service interface specifications in
order to allow operations on them.

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 3

Service Interface Description

• Ontologies as data model:
– all data elements interchanged are ontology instances
– service interface = evolving ontology

• Abstract State Machines (ASM) as formal framework:

– dynamics representation: high expressiveness & low ontological
commitment
– core principles: state-based, state definition by formal algebra,
guarded transitions for state changes
– overcome the “Frame Problem”

• further characteristics:
– not restricted to any specific communication technology
– ontology reasoning for service interoperability determination
– basis for declarative mediation techniques on service interfaces

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Service Interface Description Model

• Vocabulary Ω:
– ontology schema(s) used in service interface description
– usage for information interchange: in, out, shared, controlled

• States ω(Ω):
– a stable status in the information space
– defined by attribute values of ontology instances

• Guarded Transition GT(ω):

– state transition
– general structure: if (condition) then (action)
– different for Choreography and Orchestration
– additional constructs: add, delete, update

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Service Interface Example

Communication Behavior of a Web Service

Ωin hasValues { Ωout hasValues { Vocabulary:

concept A [ concept B [ - Concept A in Ωin
att1 ofType X att1 ofType W
att2 ofType Z]
- Concept B in Ωout
att2 ofType Y]
…} …}

State ω1 Guarded Transition GT(ω1) State ω2

a memberOf A [ IF (a memberOf A [ a memberOf A [
att1 hasValue x att1 hasValue x ]) att1 hasValue x,
att2 hasValue y] THEN att2 hasValue y]
(b memberOf B [
att2 hasValue m ]) b memberOf B [
att2 hasValue m]

received ontology
sent ontology
instance a
instance b

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Future Directions
Choreography: Orchestration:
- interaction of services / service and client - how the functionality of a Web Service is achieved by
- a „choreography interface“ describes the behavior of a aggregating other Web Services
Web Service for client-service interaction for consuming - extends Choreography descriptions by control & data flow
the service constructs between orchestrating WS and orchestrated WSs.

Conceptual models

User language
- based on UML2 activity diagrams
- graphical Tool for Editing & Browsing Service Interface Description

workflow constructs as basis for describing service interfaces:

- workflow based process models for describing behavior
- on basis of generic workflow constructs (e.g. van der Aalst)

Formal description of service interfaces:

- ASM-based approach
- allows reasoning & mediation

Ontologies as data model: Grounding:

- every resource description based on ontologies - making service interfaces executable
- every data element interchanged is ontology instance - currently grounding to WSDL

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

WSMO Goals
Objectives that a client wants to
achieve by using Web Services

Provide the Semantic description of

formally specified Web Services:
terminology - Capability (functional)
of the information - Interfaces (usage)
used by all other
components

Connectors between components

with mediation facilities for handling
heterogeneities

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Goals
• Ontological De-coupling of Requester and Provider

• Goal-driven Approach, derived from AI rational agent approach

- requester formulates objective independently
- ‘intelligent’ mechanisms detect suitable services for solving the Goal
- allows re-use of Services for different purposes

• Usage of Goals within Semantic Web Services

– A requester (human or machine) defines a Goal to be resolved
– Web Service discovery detects suitable Web Services for solving the
Goal automatically
– Goal resolution management is realized in implementations

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Goal Specification
• Non functional properties
• Imported Ontologies
• Used mediators
– OO Mediators: importing ontologies with heterogeneity resolution
– GG Mediator:
• Goal definition by reusing an already existing goal
• allows definition of Goal Ontologies
• Requested Capability
– describes service functionality expected to resolve the objective
– defined as capability description from the requester perspective
• Requested Interface
– describes communication behaviour supported by the requester for
consuming a Web Service (Choreography)
– Restrictions / preferences on orchestrations of acceptable Web
Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

WSMO Mediators
Objectives that a client wants to
achieve by using Web Services

Provide the Semantic description

formally specified of Web Services:
terminology - Capability
of the information (functional)
used by all other - Interfaces (usage)
components

Connectors between components

with mediation facilities for handling
heterogeneities

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Mediation
• Heterogeneity …
– Mismatches on structural / semantic / conceptual / level
– Occur between different components that shall interoperate
– Especially in distributed & open environments like the Internet
• Concept of Mediation (Wiederhold, 94):
– Mediators as components that resolve mismatches
– Declarative Approach:
• Semantic description of resources
• ‘Intelligent’ mechanisms that resolve mismatches independent of content
– Mediation cannot be fully automated (integration decision)
• Levels of Mediation within Semantic Web Services (WSMF):
– Data Level: mediate heterogeneous Data Sources
– Protocol Level: mediate heterogeneous Communication Patterns
– Process Level: mediate heterogeneous Business Processes

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

WSMO Mediators Overview

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 4

Mediator Structure
Source WSMO Mediator
Component
uses a Mediation Service via 1 Target
1 .. n
Component
Source
Component
- as a Goal
- directly
- optionally incl. Mediation

Mediation
Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

OO Mediator - Example
Merging 2 ontologies

Train Connection OO Mediator

Ontology (s1) Mediation Service
Train Ticket
Purchase Goal: Purchase Ontology
Ontology (s2) “merge s1, s2 and
[Link] subclassof [Link]”

Discovery

Mediation
Services

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

GG Mediators
• Aim:
– Support specification of Goals by re-using existing Goals
– Allow definition of Goal Ontologies (collection of pre-defined Goals)
– Terminology mismatches handled by OO Mediators

• Example: Goal Refinement

Source Goal GG Mediator Target Goal

Mediation Service
“Buy a ticket” “Buy a Train Ticket”

postcondition:
“aTicket memberof trainticket”

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

WG & WW Mediators
• WG Mediators:
– link a Web Service to a Goal and resolve occurring mismatches
– match Web Service and Goals that do not match a priori
– handle terminology mismatches between Web Services and Goals
⇒ broader range of Goals solvable by a Web Service

• WW Mediators:
– enable interoperability of heterogeneous Web Services
⇒ support automated collaboration between Web Services

– OO Mediators for terminology import with data level mediation

– Protocol Mediation for establishing valid multi-party collaborations
– Process Mediation for making Business Processes interoperable

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

Comparison to OWL-S

•Capability specification
•General features of the Service
• Quality of Service
• Classification in Service
taxonomies

• Mapping to WSDL
• communication protocol (RPC, HTTP, …)
• Control flow of the service
• marshalling/serialization
•Black/Grey/Glass Box view
• transformation to and from XSD to OWL
• Protocol Specification
• Abstract Messages

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

Perspective
• OWL-S is an ontology and a language to describe Web services
– Strong relation to Web Services standards
• rather than proposing another WS standard, OWL-S aims at enriching
existing standards
• OWL-S is grounded in WSDL and it has been mapped into UDDI
– Based on the Semantic Web
• Ontologies provide conceptual framework to describe the domain of Web
services and an inference engine to reason about the domain
• Ontologies are essential elements of interoperation between Web services
• WSMO is a conceptual model for the core elements of Semantic
Web Services
– core elements: Ontologies, Web Services, Goals, Mediators
• language for semantic element description (WSML)
• reference implementation (WSMX)
– Mediation as a key element
– Ontologies as data model
• every resource description is based on ontologies
• every data element interchanged is an ontology instance

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

OWL-S and WSMO

OWL-S profile ≈ WSMO capability +
goal +
non-functional properties
• OWL-S uses Profiles to express existing capabilities
(advertisements) and desired capabilities (requests)
• WSMO separates provider (capabilities) and requester
points of view (goals)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

OWL-S and WSMO

OWL-S Process Model ≈ WSMO Service Interfaces
• Perspective:
– OWL-S Process Model describes operations performed by Web Service,
including consumption as well as aggregation
– WSMO separates Choreography and Orchestration

• Formal Model:
– OWL-S formal semantics has been developed in very different frameworks
such as Situation Calculus, Petri Nets, Pi-calculus
– WSMO service interface description model with ASM-based formal semantics
– OWL-S Process Model is extended by SWRL / FLOWS

both approaches are not finalized yet

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

OWL-S and WSMO

OWL-S Grounding ≈ current WSMO Grounding

• OWL-S provides default mapping to WSDL
– clear separation between WS description and interface
implementation
– other mappings could be used

• WSMO also defines a mapping to WSDL, but aims at an

ontology-based grounding
– avoid loss of ontological descriptions throughout service usage
process
– ‘Triple-Spaced Computing’ as innovative communication
technology

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

Mediation in OWL-S and WSMO

• OWL-S does not have an explicit notion of mediator
– Mediation is a by-product of the orchestration process
• E.g. protocol mismatches are resolved by constructing a plan that
coordinates the activity of the Web services
– …or it results from translation axioms that are available to the
Web services
• It is not the mission of OWL-S to generate these axioms
• WSMO regards mediators as key conceptual
elements
– Different kinds of mediators:
• OO Mediators for ensuring semantic interoperability
• GG, WG mediators to link Goals and Web Services
• WW Mediators to establish service interoperability
– Reusable mediators
– Mediation techniques under development

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 5

Semantic Representation
• OWL-S and WSMO adopt a similar view on the need
of ontologies and explicit semantics but they rely on
different logics:

– OWL-S is based on OWL / SWRL

• OWL represent taxonomical knowledge
• SWRL provides inference rules
• FLOWS as formal model for process model

– WSMO is based on WSML a family of languages with a

common basis for compatibility and extensions in the
direction of Description Logics and Logic Programming

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

OWL and WSML

OWL Full WSML Full

full RDF(S) support First Order Logic

WSML Rule
OWL DL WSML DL

Description Logics WSML Flight

Description Logics
OWL Lite Logic Programming
subset WSML Core

• WSML aims at overcoming deficiencies of OWL

• Relation between WSML and OWL+SWRL to be completed

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Summary
current Web Service
OWL-S WSMO technologies

Goals and Web

Discovery
Profile Services UDDI API
detection of suitable WS
(capability)

Consumption & Service Interfaces

Interaction
Process Model (Choreography + BPEL4WS / WS-CDL
How to consume &
aggregate
Orchestration)

Grounding
Invocation Grounding+
(WSDL / SOAP, WSDL / SOAP
How to invoke WSDL/SOAP
ontology-based)

Mediation
- Mediators -
Heterogeneity handling

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

PART III:
A Walkthru Example

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Virtual Travel Agency Use Case

• James is employed in DERI Austria and wants to book a flight and a hotel
for the ISWC conference
• the start-up company VTA provides tourism and business travel services
based on Semantic Web Service technology
=> how does the interplay of James, VTA, and other Web Services look like?

Contract

Flight Service
Booking Provider
Customer provides
VTA uses &
aggregates
Customer
Hotel Service
Booking Provider

Contract

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Goal Description
• “book flight and hotel for the ICWS 2005 for James”
• goal capability postcondition: get a trip reservation for this

goal _"[Link]
importsOntology {_"[Link] …}
capability
postcondition
definedBy
?tripReservation memberOf tr#reservation[
customer hasValue fof#james,
origin hasValue loc#innsbruck,
destination hasValue loc#orlando,
travel hasValue ?flight,
accommodation hasValue ?conferenceHotel
payment hasValue tr#creditcard
] and
?flight[airline hasValue tr#staralliance] memberOf tr#flight and
?hotel[name hasValue “Sheraton Safari Hotel”] memberOf tr#hotel .
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

VTA Service Description

• book tickets, hotels, amenities, etc.
• capability description (pre-state)
capability VTAcapability
sharedVariables {?creditCard, ?initialBalance, ?item, ?passenger}
precondition
definedBy
?reservationRequest[
reservationItem hasValue ?item,
passenger hasValue ?passenger,
payment hasValue ?creditcard,
] memberOf tr#reservationRequest and
((?item memberOf tr#trip) or (?item memberOf tr#ticket)) and
?creditCard[balance hasValue ?initialBalance] memberOf po#creditCard.

assumption
definedBy
po#validCreditCard(?creditCard) and
(?creditCard[type hasValue po#visa] or ?creditCard[type hasValue po#mastercard]).
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

VTA Service Description

• capability description (post-state)
postcondition
definedBy
?reservation[
reservationItem hasValue ?item,
customer hasValue ?passenger,
payment hasValue ?creditcard
] memberOf tr#reservation .

assumption
definedBy
reservationPrice(?reservation, "euro", ?tripPrice) and
?finalBalance= (?initialBalance - ?ticketPrice) and
?creditCard[po#balance hasValue ?finalBalance] .

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Web Service Discovery

has Objective: „book a flight and a

James
hotel for me for the ICWS 2005.“

Goal definition

searches result set includes

Service Registry WS Discoverer VTA

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Semantic Web Service Discovery

find appropriate Web Service for automatically
resolving a goal as the objective of a requester

• Aims:
– high precision discovery
– maximal automation
– effective discoverer architectures
• Requirements:
– infrastructure that allows storage and retrieval of
information about Web services
– description of Web services functionality
– description of requests or goals
– algorithms for matching requesters for capabilities with the
corresponding providers

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 6

Discovery Techniques
• different techniques available
– trade-off: ease-of-provision <-> accuracy
– resource descriptions & matchmaking algorithms

Key Word Matching

match natural language key words in resource descriptions
Possible Accuracy
Ease of provision

Controlled Vocabulary
ontology-based key word matching

Semantic Matchmaking
… what Semantic Web Services aim at

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Matchmaking Notions & Intentions

=G = WS
Exact Match:
G, WS, O, M ╞ ∀x. (G(x) <=> WS(x) )

PlugIn Match:
G, WS, O, M ╞ ∀x. (G(x) => WS(x) )

Subsumption Match:
G, WS, O, M ╞ ∀x. (G(x) <= WS(x) )

Intersection Match: X

G, WS, O, M ╞ ∃x. (G(x) ∧ WS(x) )

Non Match:
G, WS, O, M ╞ ¬∃x. (G(x) ∧ WS(x) )
Keller, U.; Lara, R.; Polleres, A. (Eds): WSMO Web Service Discovery. WSML Working Draft D5.1, 12 Nov 2004.

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Discovery Approach
• Matchmaking Notion to be used defined for each goal
capability element
• Basic Procedure:
Goal Capability Web Service Capability
Plug-In
Precondition Precondition
valid pre-state?
Exact
no Assumption Assumption
yes

abort Intersection
Postconditio Postconditio
n n
valid post-state?
Exact
no Effect Effect
yes

abort
Match
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Discoverer Architecture
• Discovery as central Semantic Web Services technology

• Integrated Discoverer Architectures admired:

Keyword-/ Classification-based
Filtering
retrieve Service
Descriptions efficient narrowing
Controlled Vocabulary of search space
Filtering (relevant services
Resource Repository to be inspected)
(UDDI or other)
Semantic
Matchmaking

invoke Web Service

usable Web Service

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Service Interfaces
VTA Capability

Interface (Chor.) Orch.

defines provides 2) get request ..
Flight WS
3) provide offer
Goal Capability 4) receive selection
5) send confirmation
Requested Capability Interface (Chor.) Interface (Orch.)
2) get request 2) flight request
book flight & hotel VTA WS
3) provide offer 3) hotel request
Requested Interface 4) receive selection ‘Trip Booking’ 4) book flight Capability
2) send request 5) send confirmation 5) book hotel
3) select from offer Interface (Chor.) Orch.
4) receive confirmation 2) get request Hotel WS ..
3) provide offer
4) receive selection
5) send confirmation

Behavior Interface: how entity can interact

Choreography: interaction between entities
Orchestration: service aggregation for
realizing functionality

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

VTA Service Description

• Behavior Interface
• Transition “get request” to “provide offer”
choreography VTABehaviorInterface
importsOntology {_"[Link] …}
vocabularyIn {reservationRequest, …}
vocabularyOut {reservation, …}
guardedTransitions VTABehaviorInterfaceTransitionRules
if (reservationRequest memberOf tr#reservationRequest[
reservationItem hasValue tr#trip,
origin hasValue loc#city,
destination hasValue loc#city,
passenger hasValue tr#passenger]
then reservationOffer memberOf tr#reservation[
reservationItem hasValue tr#trip,
reservationHolder hasValue ?reservationHolder] .

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Choreography Discovery
VTA Capability

Interface (Chor.) Orch.

defines provides 2) get request ..
Flight WS
3) provide offer
Goal Capability 4) receive selection
5) send confirmation
Requested Capability Interface (Chor.) Interface (Orch.)
2) get request 2) flight request
book flight & hotel VTA WS
3) provide offer 3) hotel request
Requested Interface 4) receive selection ‘Trip Booking’ 4) book flight Capability
2) send request 5) send confirmation 5) book hotel
3) select from offer Interface (Chor.) Orch.
4) receive confirmation 2) get request Hotel WS ..
3) provide offer
4) receive selection
5) send confirmation

- both behavior interfaces given (“static”) - VTA Orchestration & Behavior Interfaces of
- correct & complete consumption of VTA aggregated WS given
=> existence of a valid choreography? => existence of a valid choreography between
VTA and each aggregated WS?

- Choreography Discovery as a central reasoning task in Service Interfaces

- ‘choreographies’ do not have to be described, only existence determination
=> choreography discovery algorithm & support from WSMO model
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

WSMO Service Interface Description Model

• common formal model for Service Interface description
– ontologies as data model
– based on ASMs
– not restricted to any executable communication technology
• general structure:
– Vocabulary Ω:
• ontology schema(s) used in service interface description
• usage for information interchange: in, out, shared, controlled
– States ω(Ω):
• a stable status in the information space
• defined by attribute values of ontology instances
– Guarded Transition GT(ω):
• state transition
• general structure: if (condition) then (action)
• different for Choreography and Orchestration
• additional constructs: add, delete, update

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Service Interface Example

Behavior Interface of a Web Service
Ωin hasValues { Ωout hasValues { Vocabulary:
defined concept A [ concept B [ - Concept A in Ωin
att1 ofType X att1 ofType W
att2 ofType Z]
- Concept B in Ωout
att2 ofType Y]
…} …}

State ω1 Guarded Transition GT(ω1) State ω2

a memberOf A [ IF (a memberOf A [ a memberOf A [
att1 hasValue x att1 hasValue x ]) att1 hasValue x,
att2 hasValue y] THEN att2 hasValue y]
(b memberOf B [
att2 hasValue m ]) b memberOf B [
att2 hasValue m]

received ontology
sent ontology
instance a
instance b
evolving ontology instance store
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Choreography Discovery
internal internal
business logic of business logic of
Web Service Web Service
(not of interest in Service (not of interest in Service
Interface Description) Interface Description)

• a valid choreography exists if:

– 1) Information Compatibility
• compatible vocabulary
• homogeneous ontologies
– 2) Communication Compatibility
• start state for interaction
• a termination state can be reached without any additional input

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 7

Information Compatibility
If choreography participants have compatible
vocabulary definitions:
– Ωin(S1) and Ωshared(S1) = Ωout(S2) and Ωshared(S2)
– determinable by Intersection Match from Discovery
SIS1, SIS2, O, M ╞ ∃x. (ΩS1(in U shared)(x) ∧ ΩS2(out U shared)(x))
– more complex for multi-party choreographies

Prerequisite: choreography participants use

homogeneous ontologies:
– semanticInteroperability(S1, S2, …, Sn)
– same ontologies in Service Interfaces, or usage of
respective OO Mediators

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Communication Compatibility
• Definitions (for “binary choreography” (only 2 services), more complex for multi-party choreographies)

Valid Choreography State:

ωx(C(S1, S2)) if informationCompatibility (ΩS1(ωx), ΩS2(ωx))
– means: action in GT of S1 for reaching state ωx(S1) satisfies condition in GT of S2 for
reaching state ωx(S2), or vice versa
Start State:
ωØ(C(S1, S2)) if ΩS1(ωØ)=Ø and ΩS2(ωØ)=Ø and ∃ ω1(C(S1, S2))
– means: if initial states for choreography participants given (empty ontology, i.e. no
information interchange has happened), and there is a valid choreography state for
commencing the interaction
Termination State:
ωT(C(S1, S2)) if ΩS1(ωT)=noAction and ΩS2(ωT)=noAction and ∃ ωT(C(S1, S2))
– means: there exist termination states for choreography participants (no action for
transition to next state), and this is reachable by a sequence of valid choreography
states

• Communication Compatibility given if there exists a start state and a termination

state is reachable without additional input by a sequence of valid choreography
states 3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Communication Compatibility Example

James’ Goal Behavior Interface VTA Behavior Interface
ΩS1(ωØ) = {Ø}
ΩS2(ωØ) = {Ø}
if Ø then request Start
if request then offer
ΩS1(ω1) = {request(out)}
ΩS2(ω1) =
if cnd1(offer) then changeReq ω1(C) {request(in), offer(out)}
ΩS1(ω2a) = if changeReq then offer
ω2(C)
{offer(in), changeReq(out)} ΩS2(ω2a) =
if cnd2(offer) then order ω3(C) {changeReq(in),offer(out)}
ΩS1(ω2b) = if order then conf
ω4(C)
{offer(in), order(out)} ΩS2(ω2b) =
if conf then Ø Termination {order(in), conf(out)}
ΩS1(ω3) = {offer(in), conf(in)}

existence of a valid Choreography

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

WW Mediators in Choreography

Choreography WW Mediator
internal internal
business logic of business logic of
Web Service Web Service
(not of interest in Service (not of interest in Service
Interface Description) Interface Description)

• if a choreography does not exist, then find an

appropriate WW Mediator that
– resolves possible mismatches to establish Information
Compatibility (OO Mediator usage)
– resolves process / protocol level mismatches in to
establish Communication Compatibility
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Orchestration
Control Structure for aggregation of other Web Services
Web Service Business Logic

State in Orchestration
Control Flow
1
WS Data Flow
Web Service Usage
3
- formally described service
2
functionality decomposition
- only those aspects of WS
4 WS
realization wherefore other
WS are aggregated
- aggregated WS used via
their behavior interface

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Orchestration Description & Validation

• Orchestration Description:
– interaction behavior of “Orchestrator” with “orchestrated Web
Services”
– WSMO Service Interface description model, extension of Guarded
Transitions general structure:
if condition then operation
Operation = (Orchestrator, Web Service, Action)
– Orchestrator serves as client for aggregated Web Services

• Orchestration Validation:
– need to ensure that interactions with aggregated Web
Service can be executed successfully
=> Choreography Discovery for all interaction of
Orchestrator with each aggregated Web Service

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Orchestration Validation Example

VTA Web Service Orchestration Flight WS Behavior Interface

if Ø then (FWS, flightRequest) Start if request then offer

(VTA, FWS)
if order then confirmation
if flightOffer
then (HWS, hotelRequest) Termination
(VTA, FWS)

Hotel WS Behavior Interface

if selection Start
(VTA, HWS)
then (FWS, flightBookingOrder) if request then offer
Termination if order then confirmation
if selection, flightBookingConf (VTA, HWS)
then (HWS, hotelBookingOrder)

Orchestration is valid if valid choreography exists for interactions between

Orchestrator and each aggregated Web Service, done by choreography
discovery
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Service Composition and Orchestration

• Web Service Composition:
– the realization of a Web Service by dynamically composing the
functionalities of other Web Services
• The new service is the composite service
• The invoked services are the component services
– a composite service can provide the skeleton for a Web Service (e.g. the
VTA Web Service)

• Current Composition techniques only cover aspects for valid

orchestrations partially
– functional Web Service composition (on capability descriptions)
– dynamic control and data flow construction for composite Web Service
– delegation of client / goal behavior to component services

=> Orchestration Validation needed to ensure executable Web Service

aggregations

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Composition System Overview

client
(from Berardi, ESWC 2005 Semantic Web Services Tutorial) target
service
invocation
non-functional
requirements
functional of the target
requirements service Orchestration
of the
target
service specification of
the process of Monitoring
Synthesis the composite
service

additional
requirements for
orchestration

service service
descriptions descriptions
available
service
functional functional invocation
features features
available available
non- service 1 ……… non- service n
functional functional
features features

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

Conclusions
• Semantic Web Service descriptions require
– expertise in ontology & logical modeling
=> tool support for users & developers under development
– understanding of Semantic Web Service technologies
• what it does, and how it works
• which are the related descriptive information

• Semantic Web Service technologies aim at automation of the Web

Service usage process
– users only define goal with tool support
– ‘intelligent’ SWS middleware for automated Web Service usage

• state of the art in technology & tool development

– theoretical approaches are converging; standardization efforts
– prototypical SWS technologies existent
– industrial strength SWS technology suites aspired in upcoming efforts

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 8

PART IV:
The Web Service Execution
Environment WSMX
• Aims & Design Principles
• WSMX Development Process and Releases
• Components and System Architecture
– Components
– Event-based Implementation
– System Entry Points
– Execution Semantics

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

WSMX Introduction
• Software framework for runtime binding of service
requesters and service providers
• WSMX interprets service requester’s goal to
– discover matching services
– select (if desired) the service that best fits
– provide data mediation (if required)
– make the service invocation
• is based on the conceptual model provided by WSMO
• has formal execution semantics
• SO and event-based architecture based on microkernel
design using technologies as J2EE, Hibernate, Spring,
JMX, etc.

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Design Principles
Strong Decoupling & Strong Mediation
autonomous components with mediators for interoperability

Interface vs. Implementation

distinguish interface (= description) from implementation (=program)

Peer to Peer
interaction between equal partners (in terms of control)

WSMO Design Principles == WSMX Design Principles

== SOA Design Principles

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

WSMX Usage Scenario

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Development Process & Releases

• The development process for WSMX includes:
– Establishing its conceptual model
– Defining its execution semantics
– Develop the architecture
– Design the software
– Building a working implementation
• Planned releases:
November 2005 (WSMX 0.4)

June 2005 (WSMX 0.3)

January 2005 (WSMX 0.2)

November 2004 (WSMX 0.1.5)

current status of components

2005 2006
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Components & System Architecture

WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Selected Components
• Adapters
• Parser
• Invoker
• Choreography & Process Mediator
• Matchmaker
• Data Mediator
• Resource Manager

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Adapters
• to overcome data representation
mismatches on the communication layer
• transforms the format of a received
message into WSML compliant format
• based on mapping rules

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Parser
• WSML 1.0 compliant parser
– Code handed over to wsmo4j initiative
• Validates WSML description files
• Compiles WSML description into internal
memory model
• Stores WSML description persistently
(using Resource Manager)

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Invoker
• WSMX V0.1 used the SOAP implementation from
Apache AXIS
• Web Service interfaces were provided to WSMX as
WSDL
• Both RPC and Document style invocations possible
• Input parameters for the Web Services were translated
from WSML to XML using an additional XML Converter
component.
Network

SOAP
XML XML Web
Mediated Invoker
Apache
AXIS Service
WSML Data Converter

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 9

Choreography & Process Mediator

• requester and provider have their own
communication patterns
• only if the two match precisely, a direct
communication may take place
• at design time equivalences between the
choreographies’ conceptual descriptions is
determined and stored as set of rules
• Choreography Engine & Process Mediator
provides the means for runtime analyses of two
choreography instances and uses mediators to
compensate possible mismatches
3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Matchmaker
• responsible for finding appropriate Web
Services to achieve a goal (discovery)
• currently the built-in matchmaking is
performed by simple string-based
matching; advanced semantic
discoverers in prototypical stage

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

OOMediator
• Ontology-to-ontology mediation
• A set of mapping rules are defined and then executed
• Initially rules are defined semi-automatic
• Create for each source instance the target instance(s)
Source Target
Ontology Ontology

Source Execution Target

Instance Instance
Environment

Mapping Rules
Mapping Rules
Creator

Mappings
Mappings

Data Base

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Resource Manager
• Stores internal memory model to a data
store
• Decouples storage mechanism from the
rest of WSMX
• Data model is compliant to WSMO API
• Independent of any specific data store
implementation i.e. database and
storage mechanism

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Event-based Implementation
Core – Manager

“Business” Process – Internal Workflow

Event and Notification Distribution /Delivery Mechanism

events notifications
events notifications events notifications events notifications
Discovery
Wrapper
Choreography implements Data Mediator Communication
Wr apper Mediator Wr apper Manager Wrapper
Interface

Communication
Choreography Discovery Mediator
Manager

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

System entry points

• storeEntity(WSMOEntity):Confirmation
– provides an administration interface for storing any WSMO-related
entities (Web Services, Goals, Ontologies)
• realizeGoal(Goal, OntologyInstance):Confirmation
– service requester expects WSMX to discover and invoke Web Service
without exchanging additional messages
• receiveGoal(Goal, OntologyInstance, Preferences):WebService[]
– list of Web Services is created for given Goal
– requester can specify the number of Web Services to be returned
• receiveMessage(OntologyInstance,WebServiceID,
ChoreographyID):ChoreographyID
– back-and-forth conversation to provide all necessary data for
invocation
– involves execution of choreographies and process mediation between
service interfaces

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

System Entry Points

storeEntity receiveGoal receiveMessage

Service Service Service

Provider Requester Requester

any Data any Data

format format

Editor Adapter Adapter

WSML WSML WSML

Communication Communication Communication

Manager Manager Manager
(Requester Side (Requester Side (Requester Side)

Service Choreography Parser

Parser Parser
Repository Engine

Communication Data
Data Manager
Legend Service Matchmaker
Mediator (Provider Side)
Mediator
Repository
WSMX components
SOAP
External entities
Selector
Execution Flow
Service
Usage Provider

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Execution Semantics
WSMT – Web Services Modelling Toolkit

Request to discover WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor
Web services.
Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Execution Semantics
WSMT – Web Services Modelling Toolkit

Goal expressed
WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor
in WSML is sent to
WSMX System
Service InterfaceWSMX Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Com. M. implements
Service WSMX
the interface to Administration Framework Interface
Service
Requesters receive WSML goals Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 10

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Com. M. informs Service 1
Core that Goal
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

has been received Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Chor. wrapper Service
Requesters picks up event for Providers
WSMX Manager Chor. component
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters New choreography Providers
WSMX Manager Instance is created
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Core is
Wrapper notified
Wrapper Wrapper
Web
that choreography Service 1
instance has been
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on created. Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface
acting on
WSML Interface
goal is Interface Interface Interface Interface Interface Interface
Web
parsedResource
to Service 2
behalf of Communication Data Process
Parser Discovery Selector Choreography
service internal
Manager format.
Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

acting on
Discovery is Web
invoked Data Service 2
behalf of Communication Resource Process
Parser Discovery Selector Choreography
service Manager Manager for parsed goal.
Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Discovery may
Mediator Mediator ...
requester Invoker Receiver
requires ontology Web
mediation. Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource After data mediation,
Data Process
Parser DiscoveryDiscovery
Selector Choreography
service Manager Manager iterates,
Mediator Mediator ...
if needed through
requester Invoker Receiver Web
last steps until
Service p
... Adapter n

Grounding result set is finished.

Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Selection is invoked
Mediator Mediator ...
to relax result set to
requester Invoker Receiver Web
finally one service.
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
Choreography
service Manager Manager Mediator Mediator
instance for goal
...
requester Invoker Receiver requester is checked Web
for next steps. Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 11

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor

Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Result is returned Web
acting on Service 2
behalf of Communication
to Com. [Link]
to be Data Process
Parser Discovery Selector Choreography
service forwarded to Manager
Manager the Mediator Mediator ...
requester service requester.
Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Execution Semantics
WSMT – Web Services Modelling Toolkit

WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor
Set of Web Service
descriptions
Service WSMX
expressed in WSML Administration Framework Interface
Service
Requesters sent to adapter. Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Execution Semantics
Set of Web Service
WSMT – Web Services Modelling Toolkit
descriptions expressed
in requester’s own
WSMX Managment WSMX Monitor WSML Editor Choreography Editor Mediator Editor
format returned to
goal requester.
Service WSMX
Administration Framework Interface
Service
Requesters Providers
WSMX Manager
Data and Communication Protocols Adapters
Adapter 1

System Interface

WSMX Manager Core

Back-End CM RM Parser Discovery Selector DM PM Choreography
Application Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper
Web
Service 1
Adapter 2

Agent Interface Interface Interface Interface Interface Interface Interface Interface

Web
acting on Service 2
behalf of Communication Resource Data Process
Parser Discovery Selector Choreography
service Manager Manager Mediator Mediator ...
requester Invoker Receiver Web
Service p
... Adapter n

Grounding
Component
Wrapper
Resource Manager Interface Reasoner Interface

WSMO Objects Non WSMO Reasoner

Interface
Objects
New
Component

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Conclusions
• Conceptual model is WSMO (with some add-
ons)
• End to end functionality for executing SWS
• Has a formal execution semantics
• Real implementation
• Open source code base at SourceForge
• Event-driven component architecture
• Developers welcome

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

WSMX @ [Link]

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Closing, Outlook,
Acknowledgements

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Tutorial Wrap-up
• The targets of the presented tutorial were to:
– understand aims & challenges within Semantic Web Services
– understand Semantic Web Service Frameworks:
• aims, design principles, and paradigms
• ontology elements & description

• an overview of Semantic Web Service techniques:

– element description
– discovery
– choreography and service interoperability determination
– orchestration and composition

• present WSMX a future Web Service based IT middleware

– design and architecture
– components design

=> you should now be able to correctly assess emerging technologies &
products for Semantic Web Services and utilize these for your future work

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Beyond WSMO
• Although WSMO (and OWL-S) are the main initiatives on
Semantic Web services, they are not the only ones:
• Semantic Web Services Interest Group
– Interest group founded at W3C to discuss issues related to
Semantic Web Services ([Link]
– Standardization Working Group in starting phase
• SWSI: International initiative to push toward a
standardization of SWS ([Link]
• Semantic Web services are entering the main stream
– UDDI is adopting OWL for semantic search
– WSDL 2 will contain a mapping to RDF
– The use of semantics is also discussed in the context of
standards for WS Policies

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005
 12

Acknowledgements
The WSMO work is funded by the European
Commission under the projects DIP, Knowledge
Web, SEKT, SWWS, AKT and Esperonto; by
Science Foundation Ireland under the DERI-
Lion project; and by the Vienna city government
under the CoOperate program.

We would like to thank to all the members of the

WSMO, WSML, and WSMX working groups for
their advice and input into this tutorial.

3rd Internation Conference on Web Services (ISWC 2005), Orlando, Florida (USA), July 2005