Transcript Use case

WSMO D3.2:
Use Case and Testing
Part 1: Overview & Achievements
2nd F2F meeting SDK cluster working group on Semantic Web Services
Lausanne, Switzerland, 14-06-2004
Michael Stollberg
Digital Enterprise Research Institute
[email protected]
Session Structure
• Part 1: Overview & Achievements
– recall of aims & structure of deliverable
– overview of achievements since last f2f meeting
• Part 2: Discovery in WSMO & Discussion
– presentation of discovery
• General Approach
• Implementations in FLORA
– discussion & feedback (open round)
WSMO D3.2 – Use Case and Testing
Michael Stollberg
2
- Recall -
Overview WSMO D3.2
• Objectives
– Showcase use case modeling in WSMO
– “playground” for recursive development of WSMO
• Content
– “use-case oriented” use case description
– WSMO use case modeling with explanations
– Complete WSMO models for computation
WSMO D3.2 – Use Case and Testing
Michael Stollberg
3
- Recall -
Use Cases
1.
Virtual Travel Agency (VTA)
–
–
–
a VTA provides end-user eTourism services
these are aggregations of eTourism Web Services of several
Providers
is a SWS-enabled B2C application that provides an end-user
service following a C/S Model
2. B2B Integration with Semantic Web Services
–
–
Business document exchange between heterogeneous backend systems
“3rd party” P2P architecture
WSMO D3.2 – Use Case and Testing
Michael Stollberg
4
- Achievements -
Overview
WSMO Use Case Modeling (section 3.1.2)
1. WSML
2.
Ontology Development
3.
Mediators
4.
Goals and Web Service Capability Modeling
5.
Goal-Capability Marching (heart of Discovery)
WSMO D3.2 – Use Case and Testing
Michael Stollberg
5
- Achievements -
1) WSML
Modeling Language for WSMO
• human usability:
–
–
–
human readable
frame-based syntax (definitely improves readability)
language to easily define ontologies, web services, goals and mediators
• web support:
–
–
everything is a URI (or a literal)
namespace support
• expressivity:
–
–
–
logic programming
matchmaking computable
logical expressions based on F-Logic
WSMO D3.2 – Use Case and Testing
Michael Stollberg
6
- Achievements -
2) Ontology Development
2.1) International Train Ticket Ontology (Listing 1)
General comment: nearly finished
• usedMediators:
–
–
OWL Factbook and Address as reference ontologies
uses Date and Time Ontology & Location Ontology
• Concepts:
station, itinerary, trip, trainTrip, distance, class, service, meal
• Axioms:
-
transitivity of location concept
constraint: departure before arrival
distance constraints and measure transformation
WSMO D3.2 – Use Case and Testing
Michael Stollberg
7
- Achievements -
2) Ontology Development
2.2) Date and Time (Listing 2)
General comment: final version
• Concepts:
-
Applause for
Holger !!
general notions: dateandtime, instant, interval
Date: year, monthOfYear, dayof Month
Time: hourOfDay, minuteOfHour, secondOfMinute
• Relations:
general structure of axioms / integrity constraints
• Axioms:
-
Integrity Constraints for all notions
“Date and Time Algebra”: equal, before, after
Instant / Interval containment
WSMO D3.2 – Use Case and Testing
Michael Stollberg
8
- Achievements -
2) Ontology Development
2.3) Purchase Ontology (Listing 3)
General comment: initial version
• usedMediators:
–
–
uses OWL Currency ontology
uses Location & Date and Time Ontology
• Concepts:
buyer, seller, tradeItem, product, product, price,
paymentMethod (credit card, cash), trade, delivery
• Axioms:
-
Price must be positive
=> Does anybody know / have a decent purchase ontology?
WSMO D3.2 – Use Case and Testing
Michael Stollberg
9
- Achievements -
2) Ontology Development
2.4) Location Ontology (Listing 4)
General comment: nearly finished
• usedMediators:
uses OWL Factbook & Address ontology
• Concepts:
location, country, city, state
address
• Instances:
- some test instances
link to knowledge base with large set of instances is missing
WSMO D3.2 – Use Case and Testing
Michael Stollberg
10
- Achievements -
3) Mediators
General Remark: Mediators with empty Mediation Service / Reduction are omitted
•
OO Mediator (see Listings 7 – 10):
–
–
•
GG Mediator:
–
–
•
Re-use of Goals via Refinement (in Reduction) + terminology mismatches
not in use case
WG Mediator:
–
–
–
•
reusable ontology mappings, i.e. “Schema Adapter”
Modeling of Mediation Service still open
Handling of partial matches in WS Discovery (differences in Reduction)
terminology mismatches
not in use case
WW Mediator:
–
–
–
connecting Web Services for global Choreography / Orchestration
mediation on data level, process level, protocol level
not in use case
WSMO D3.2 – Use Case and Testing
Michael Stollberg
11
- Achievements -
4) Goal & Capability Description
Aims:
- Conceptually correct modeling
- Support for Discovery Mechanism
•
Goal:
– describes a desire that a user wants to be resolved when using a Web Service
– De-coupling of request and service
•
Web Service Capability:
– Functional description
– specifies:
•
•
•
•
•
Input & conditions over this (pre-condition)
arbitrary states of the world that have to hold before service can be executed (assumption)
Output in relation to the input, and conditions over this (postcondition)
Changes in the world that result from service execution (effects)
Web Service Interface: not completely specified yet (next big issue)
WSMO D3.2 – Use Case and Testing
Michael Stollberg
12
- Achievements -
4) Goal Modeling
Use Case Goal (Listing 5)
Desire:
Buy a train itinerary from Innsbruck to Frankfurt on July, 17th 2004, for Tim
Berners-Lee
Postcondition:
get the description of the itinerary bought
Effect:
have a trade with the seller for the itinerary, paying by credit card and the bill
and ticket have to be delivered to Tim Berners-Lee’s address
WSMO D3.2 – Use Case and Testing
Michael Stollberg
13
- Achievements -
4) Capability Modeling
Use Case Web Service Capability (Listing 6)
Web Service Functionality:
sells train itineraries for a date after the current date, with start and end in Austria or
Germany, and paid by credit card
Precondition:
buyer information, his purchase intention has to be a train itinerary (after the current
date, with start and end in Austria or Germany). Payment method of the buyer has to be
a non-expired credit card
Assumption:
buyer credit card account has to have “enough money” (not modeled yet)
Postcondition:
information about the itinerary bought, for which the start and end locations, departure
date, and passenger are the same as provided in the input
Effect:
A trade with the buyer in the precondition for the itinerary in the postcondition, using
the credit card of the buyer given in the precondition
WSMO D3.2 – Use Case and Testing
Michael Stollberg
14
- Achievements -
5) Web Service Discovery in WSMO
•
Understanding of Discovery – 3 aspects:
1) Goal-Capability Matching (Core)
2) Handling of Partial Matches (WG Mediator)
3) Heuristics and Filters for different “Discoverers”
•
Realization of Goal-Capability-Matching:
prove that Capability logically entails Goal
•
Implementation in FLORA:
in Part 2 ….
WSMO D3.2 – Use Case and Testing
Michael Stollberg
15
</ WSMO D3.2
Use Case and Testing >
<discovery & discussion after break>