This document is also available in non-normative PDF version.
Copyright © 2004 DERI®,
All Rights
Reserved. DERI liability,
trademark, document use, and software licensing rules apply.
This document exemplifies the usage of the Web Service Modeling Ontology WSMO for modeling possible Web Service driven applications. We first outline general usage of Semantic Web Service in different application fields, identifying the usage scenarios and the arising technical requirements. Then, we provide the WSMO modeling of specific use cases, in order to demonstrate WSMO modeling and for supporting recursive development of WSMO.
For use case modeling, we stick to the latest final working draft of Web Service Modeling Ontology WSMO, Version 0.2 [Roman et al., 2004].
WSMO Standard: D2 v0.2 Web Service Modeling Ontology (WSMO), last version at: http://www.wsmo.org/2004/d2/
WSMO Primer: D3.1 v01. WSMO Primer
WSMO Reasoning: D5.1 v01. Inferencing Support for Semantic Web Services: Proof Obligations.
This document exemplifies the usage of the Web Service Modeling Ontology WSMO for describing Semantic Web Services and related constructs. To this end, we describe two possible use cases of Semantic Web Services in B2C and B2B scenarios and showcase how these can be modeled in WSMO. We briefly replicate the objectives and the approach of WSMO and outline how specific use cases can be modeled in WSMO along with explanations on the modeling decisions. The modeling is exemplified in a human readable syntax for WSMO descriptions. Besides, resources in pure F-Logic generated from these descriptions which aim at solving Web service discovery based on WSMO using an engine such as FLORA-2 are provided in the appendix.
This Deliverable is intended to evolve in accordance to the ongoing development of WSMO itself, serving as input and providing valuable insight for testing and adapting the modeling constructs provided in WSMO in real world scenarios for Web Services. So, besides demonstrating how to model Web Services in WSMO, the use cases also allow us to demonstrate the adequacy of our approach in terms of providing an exhaustive framework for covering all relevant aspects of semantic description of Web Services. In the long run, additional use cases will be added in order to widen possible solutions for Semantic Web Service technologies around WSMO.
This document is organized as follows: the remainder of Section 1 summarizes the objectives and approach of WSMO; Section 2 discusses possible application areas of Semantic Web Services. Section 3 provides the modeling of real world use cases in WSMO. Section 4 concludes the document. The complete WSMO models as computational resources are provided in the Appendices. Besides, we provide facilities for readers to keep track of improvements and discussion related to this document: a Change Tracker in Appendix B explicitly list the major changes between different versions of this document in order to facilitate readers following the improvements, and Appendix C lists the comments given by reviewers as well as the actions undertaking to resolve open issues.
A Web Service is a piece of software accessible via the Internet. Current Web Service technologies allow exchange of messages between Web Services [SOAP], describing the technical interface [WSDL], and advertising a Web Services in a registry [UDDI]. These technologies do not provide any information about the meaning of information used, neither do they explicitly describe the functionality of a services as needed for automated usage and interoperability of Web Services. Enhanced Web Service technologies aim at more sophisticated techniques to describe Web Services, emphasizing the concept of Semantic Web Services. In our understanding, a Semantic Web Service is defined as a “self-contained, self-describing, semantically marked-up software resource that can be published, discovered, composed and executed across the Web in a task driven automatic way” [Arroyo et al., 2004]. In the end, by machine-processable descriptions of the relevant information of Web Services, the following tasks shall be addressed:
The aim of the WSMO project is to define a coherent technology for Semantic Web Services (short: SWS). WSMO defines the modeling elements for describing several aspects of Semantic Web Services. The conceptual basis of WSMO is the Web Service Modeling Framework [WSMF], wherein four main components needed for a full coverage framework for Semantic Web Services are defined (see Figure 1):
Ontologies provide the formal semantics of the information used by all other components.
Goals specify objectives that a client may have when it consults a web service.
Web Services exposed descriptions of the functionality of a Web Service for supporting automated discovery, composition, and execution (called “Capabilities” in WSMO). For supporting automated usage, composition, and execution of Web Services, particular information on the external visible behavior of a Web Service are specified (called “Interface” in WSMO), including information on the technical accessibility and the actual message exchange of Services.
Mediators are used as connectors between particular components and include possibly required mediation facilities needed to make connected components interoperable. WSMO distinguishes different types of Mediators.
Further details on the components of WSMO along with exhaustive explanations are presented in the WSMO Primer [Arroyo and Stollberg, 2004].
 |
| Figure 1. WSMO Components |
Semantic Web Services can be used in manifold application fields. In accordance to the use cases defined in Web Services Architecture Usage Scenarios by the W3C Web Services Architecture Working Group (see [He et al., 2004]), we discuss two of the most commonly used scenarios to exemplify the usage of SWS technologies in this document:
For describing the use cases, we slightly modify the methodology of the W3C Use Case descriptions and extend them by the requirements arising for Semantic Web Services technologies. The aspects considered for our use case definitions are as follows:
In [He et al., 2004], the travel agency use case is separated into two use cases - one with static discovery and one with automated discovery. With Semantic Web Services we clearly want to support automated discovery. Thus, in the first WSMO use case we will describe a Virtual Travel Agency example that involves automated discovery of Web Services.
Imagine a “Virtual Traveling Agency”, called VTA for short, which is an end user platform providing eTourism services to customers. These services can cover all kinds of information services concerned with tourism information - from information about events and sights in an area to services that support booking of flights, hotels, rental cars, etc. online. Such VTAs are already existent, but at this point mostly comprise simple information portals along with some web-based customer services (see for example an eTourism service provider in Austria at: http://www.etourism.at/). By applying Semantic Web Services, a VTA will invoke Web Services provided by several eTourism suppliers and aggregate them into new customer services in a (semi-)automatic fashion. Such VTAs providing automated eTourism services to end users thus tremendously enhance the functionality of currently existing VTAs.
Our VTA use case that aggregates Web Services of different tourism service providers in a nutshell shall provide the following functionality: A customer uses the VTA service as the entry point for his requests. These requests must fit to end-user services that the VTA provides. These end-user services are aggregated by the VTA by invoking and combining Web Services offered by several tourism service providers. Therefore, there must be some kind of contract between the service providers and the VTA for regulating usage and allowance of the Web Services. Figure 2 gives an overview (modified and extended from W3C Travel Agent Use Case overview, as defined in [He et al., 2004]).
 |
| Figure 2. Use Case Overview: Virtual Travel Agency based on Semantic Web Services |
The scenario outlines a general structure for VTAs that can be extended to more complex scenarios wherein the customer can be a Web Service itself, thus creating a network of composed services that offer complex tourism services. For example, one VTA can provide flight booking services for an airline union, another VTA aggregates booking service for a worldwide hotel chain, and a third VTA provides booking services for rental cars by combining the services of several worldwide operating car rental agencies. Then, another VTA uses these services for providing an end-user service for booking complete holiday trips worldwide.
We provide the modeling of one such VTA use case in Section 3.1.VTA for International Online Train Ticket.
In the general use case there are 3 actors. The following defines why they participate in this use case (goal) and the particular interactions they are involved in (roles).
We identify the following usage scenarios
In this use case, the VTA is the central point of interaction between the Customer and other Web Services. Regarding the technological requirements, it is obvious from the usage scenario descriptions that (1) the Web Services offered by the Service Providers have to carry sufficient descriptive information to support automated Web Service usage, and (2) that the VTA has to provide all mechanisms to handle Semantic Web Services. The basic architecture of such a VTA as a central entity for Semantic Web Services handling is shown in Figure 3. The essential functionalities of Semantic Web Service enabled VTAs – with special regard to the requirements for Semantic Web Service technologies – are:
 |
| Figure 3. General Architecture of a SWS-enabled VTA |
Summarizing, the VTA is a SWS-enabled B2C application that provides an end-user service following a client/server model. In order to support coherent functionality of the VTA and to ensure that the descriptions of Web Services are compatible to this, an overall framework for SWS technologies is needed. This is provided by WSMO.
The second use case is concerned with the integration of possible heterogeneous resources in B2B settings which is considered as one of the most important application fields of the Web Service technology.
In the B2B use case, two enterprises called E1 and E2 want
electronically exchange business documents across the network. Assuming
that partners may not know each other before, contract negotiation and
contract agreement are essential aspects of this use case. The contract
agreement defines roles of enterprises in the conversation, for
instance, one of the enterprise E1 becomes the seller and the second
enterprise E2 becomes the buyer. An agreement also predefines the order
of the messages interchanged between the parties, e.g.the buyer first
sends purchase order (PO) and after that it receives purchase order
acknowledgement (POA). In constrats to the previous B2C use case, where
the client/server model of interactions has been adopted, here partners
are equal in the interaction, i.e. a peer-to-peer model is assumed in
this use case. Each of the companies has an own set of web services for
exchanging business documents electronically. The infrastructure
provided by SWS takes care for any necessary mediation between web
services (links web services), ontologies (resolves possible
representation mismatches between ontologies used by these two
enterprises), goals (links goals), as well as linking web services and
goals. The infrastructure also supports the execution of the contract
to fulfill approved agreement.
 |
| Figure 4. B2B Integration with Semantic Web Services |
In this use case an ultimate goal of an enterprise E1 is to integrate its own back-end system with the back-end system of an enterprise E2. Once integrated, SWS software enables back-end systems of both companies to interact and to preserve the message, process and protocol semantic. The information systems used by enterprises E1 and E2 are autonomous, heterogonous and distributed. Semantic Web Services address each of these three properties and the software based on SWS enables companies to cooperate.
The use case assumes peer-to-peer relationships between two business partners carrying conversation about purchasing/selling of goods. The B2B use case focuses on the technical infrastructure based on the SWS technology, which enable any business company to automatically discover web services which are capable to fulfill its goals, compose simple web services into complex web services to achieve a given goal and to automatically execute given services in a particular order. This use case assumes that there may be no prior business relationships between two enterprises before the discovery. Enterprise E1 must find enterprise E2 and they must agree and enforce the contract in their companies. Agreement should define roles of each of them in the agreed business process – e.g. one of them would become a buyer and one of them would become a seller. The agreement can lead to only one time execution of the agreed business process (e.g. request purchase order) or to long time relationships based on the multiply execution of the agreed contract. Payments are sent through financial institutions and at this stage they are out of the scope of this use case. The same situation concerns the shipment of the goods. This use case consider sending documents as for example purchase orders or invoices, but the physical shipment of goods is out of the scope of this use case.
There are two actors in the B2B use case – actors, which represent two business entities. The size and the importance of companies are not predefined in this use case. They might differ in size but from the perspective of this use case it should not matter which one of them is a more dominant partner. Both of the enterprises undertake a predefined role in the use case. These are:
In this use case the following usage scenarios have been identified:
The Web Services Modeling Execution (WSMX) is the infrastructure is a WSMO-reference implementation that addresses this use case, see WSMX hompage at: http://www.wsmo.org/wsmx/. Therein, a WSMX-platform is hosted by each of the enterprises to support services following a peer-to-peer model. WSMX is software implementation of a web service execution environment supporting the development, management and execution of Semantic Web enabled Web Services. WSMX platform does not differentiate between calls coming from the back-end application systems (intra-company information systems) and from the information systems of other enterprises. WSMX can also communicate directly with other WSMX platforms hosted by other enterprises as shown on figure 5.
 |
| Figure 5. B2B Use Case System Architecture |
The following exemplifies the usage of WSMO for describing Semantic Web Services for some specific aspects of the use cases decribed above. In the following we will:
The provided listings use the conceptual model presented in WSMO Standard, V0.2 as the latest stable version of WSMO. During the elaboration of this use, several conceptual refinements have been undertaken which we explicitly describe in the text. For modeling, we apply the syntax defined in in D16.1 v02 BNF Grammar for WSML language. Currently, we support FLORA-2 as an F-Logic reasoner (see documentation and download of the latest distributions at the FLORA-2 homepage http://flora.sourceforge.net/). We provide the models as executable resources for FLORA-2 in Appendix A of this document.
According to the general VTA use case described in Section 2.1 B2C - Virtual Travel Agency we define a specific use case for booking international train tickets online. We describe a hypothetical Web Service, combining the functionality provided by the Austrian national train operator (ÖBB) and the German Railways (DB), which offer end-user services for searching and buying train tickets for itineraries in Austria and in Germany. This Web Service is composed out of other Web Services, namely one for searching existing train connections, and one for purchasing train tickets online. The services of ÖBB and DB are currently not provided in a machine-processable manner but only via simple end-user web interfaces - Figure 6 shows the currently available portal for ÖBB where the user has to manually select the desired train connection and is lead through the purchase process.
As a user request we assume that the user wants to purchase an
international train ticket. The course of the use case shall be the
following:
- the customer creates a goal for an international train connection
from Innsbruck to Frankfurt on 17th May 2004, at 16.00 local time
- the VTA returns a set of possible connections
- the user selects one of these connections and poses a request for
booking the ticket online
- the VTA combines the online train ticket booking services from
ÖBB and DB, executes the booking and payment process, and sends an
online ticket per email to the Customer.
 |
| Figure 6. ÖBB Train Connection Itinerary Service |
The rationale for choosing this first use case is that it allows to showcase and test describing all WSMO components identified in WSMO Standard. The setting is kept simple on purpose. More complex cases to be added at a later stage of this deliverable can build upon this, providing models of more involved scenarios.
The following properties have to be covered in our use case modeling. For each of the WSMO top-level components, a separate table describes informally which parts of the use case are concerned.
| O1 |
Ontological information are needed on international train itineraries, on notions of date and time, on the purchasing process, as well as on persons, locations, and addresses. This information should be kept in separate re-usable ontologies, following the modularity principle of ontology design. |
| O2 | An itinerary is described by its start and end locations, date and time of departure and arrival, stations which the train passes (particularly, the station where the border is crossed) and is done by some passenger. |
| O3 | An itinerary describes a valid international train connection. |
| O4 | There has to be traveller / customer that does the itinerar/buys a train ticket |
| O5 | There exists a concept that defines whether a location is located at the border between 2 countries |
| O6 | A ticket is valid for exactly 1 itinerary and has a price |
| O7 | A ticket is valid for exactly 1 customer |
| O9 | The purchase ontology has to identify the buyer and seller roles, a product with a price, and valid payment methods |
| O10 | We need to be able to express valid payment methods. The only valid payment method for online tickets is credit card payment |
| O11 | Information on Date and Time should allow axiomatic expressions on dependencies of specific dates and times , i.e. expression that define relationships like 'after' or 'before ' |
| G1 | Booking an Online Train Ticket |
| G1.1 | From Innsbruck to Frankfurt |
| G1.2 | Start time: 17th July 2004, at 18.00 local time. |
| W1 | A National Train Operator, here the Austrian ÖBB, provides an end-user Web Service that offers a search facility for international train connections and a facility for buying international train tickets online. |
| W2 | The search facility takes a start location, an end location, and a departure date as input and returns a set of itineraries. |
| W3 | The facility for buying train tickets online takes a specfic itinerary with start location and end location in countries of its coverage, the information of the customer and the number of his (not expired) credit card number as input, and it returns a ticket for this itinerary as the result. |
| W4 | The user interacts with the end-user Web Service which aggregates the search and purchasing Web Services from possibly different providers like ÖBB, DB, etc. |
| M1 | There need to be OO Mediators that integrate the distinct ontologies used as terminology definitions. |
| M2 | If there are terminological mismatches between the ontologies used in the Goal or the Web Service description, OO Mediators have to be defined to resolve these. |
| M3 | If there are differences between the Goal and the ÖBB-Web Service, a WG Mediator is needed to resolve these. |
| M4 | if there are mismatches between the search facility Web Service and purchase Web Service (which are composed into the end-user Web Service), then a WW Mediator has to be defined which resolves the mismatches. |
The following provides the modeling of the use case in WSMO with respect to the requirements determined above. The modeling in this document relies on the Web Service Modeling Ontology WSMO, Version 0.2 [Roman et al., 2004]. Some elements of WSMO at not completely specified at the current version of the ontology. This version of the use case modeling is restricted to the WSMO components wherefore a stable specification is existing at this point in time.
With regard to modularized ontologies as a basic design principle of WSMO, we define four separate domain ontologies as the the terminology definitions for the use case:
The ontologies specified in the following are intended to be "real ontologies" in the sense that they describe the specific domain as a shared conceptualization in a sufficient manner. This allows to reuse this ontologies in different settings and use cases - for example, notions or date and time or a general purchase ontology are needed in a lot of other possible scenarios. However, we do not claim the defined below to be such generic ontologies, but they will be enhanced and completed within cooperations with other use cases, projects, and initiatives.
As extensions to WSMO Standard as defined in [Roman et al., 2004], we apply the following conventions in the Listings:
The "International Train Ticket" Ontology defines a train trip and the surrounding concepts as defined the WSML definition of the ontology shown in Listing 1.
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/tc.wsml
namespace
default=http:://www.wsmo.org/ontologies/trainConnection#,
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418#,
dt=http:://www.wsmo.org/ontologies/dateTime#,
prs=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlPersonMediator.wsml,
loc=http:://www.wsmo.org/ontologies/location#,
xsd=http://www.w3.org/2001/XMLSchema#
non-functional-properties
dc:title "International Train Connections Ontology"
dc:creator "DERI International"
dc:subject "Train", "Itinerary", "Train Connection", "Ticket"
dc:description "International Train Itineraries"
dc:publisher "DERI International"
dc:contributor "Michael Stollberg", "Ruben Lara", "Holger Lausen", "Axel Polleres"
dc:date "2004-06-28"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#ontos
dc:format "text/plain"
dc:language "en-US"
dc:relation
http://www.daml.org/2001/06/itinerary/itinerary-ont,
http://daml.umbc.edu/ontologies/ittalks/person,
http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/location,
http://opencyc.sourceforge.net/daml/cyc-transportation.daml
dc:coverage "ID:7029392 Name:World"
dc:rights http://www.deri.org/privacy.html
version "$Revision: 1.7 $"
usedMediators
ooMediator
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlPersonMediator.wsml,
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlFactBookMediator.wsml,
http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/location
comment: conceptDefinitions
concept station subconceptOf loc:location
non-functional-properties
dc:description "Train station"
code oftype xsd:string
non-functional-properties
dc:description "Code of the station"
locatedIn oftype set loc:location
borderToCountry oftype loc:border
non-functional-properties
dc:description "For stations located at the border"
concept itinerary
non-functional-properties
dc:description "An itinerary between two locations"
passenger oftype prs:person
non-functional-properties
dc:description "prs:person is a subset of vCard (http://www.ietf.org/rfc/rfc2425.txt)"
recordLocatorNumber oftype xsd:string
trip oftype trip
concept trip
start oftype loc:location
end oftype loc:location
via oftype set loc:location
departure oftype dt:dateAndTime
arrival oftype dt:dateAndTime
duration oftype dt:interval
distance oftype loc:distance
concept trainTrip subconceptOf trip
non-functional-properties
dc:description "A train trip"
start oftype station
end oftype station
via oftype set station
seat oftype xsd:string
train oftype xsd:string
class oftype xsd:string
comment: variableDefinitions
variable S memberOf station
variable L, Start, End memberOf loc:location
variable C memberOf loc:country
variable T memberOf trip
variable D, A memberOf dt:dateAndTime
comment: axiomDefinitions
axiom stationCountry
non-functional-properties
dc:description "Integrity constraint: if a station is located in a place
which is located in a given country, the country of the station is the
same"
logical-expression
"<-
S[
locatedIn hasvalue L,
country hasvalue C]
and not L[
country hasvalue C]."
axiom departureBeforeArrival
non-functional-properties
dc:description "Integrity Constraint: departure has to be before arrival"
logical-expression
"<-
T[
departure hasvalue D,
arrival hasvalue A]
and A <= D."
axiom startNotEqualEnd
non-functional-properties
dc:description "Integrity Constraint: the start and end of a trip have to be different"
logical-expression
"<-
T[
start hasvalue Start,
end hasvalue End]
and Start = End."
comment: instanceDefinitions
comment: A link to large set of instances is missing in WSMO.
Therefore, in this version of the ontology we only include
some example instances. The inclusion of links to large
set of instances will be considered in future versions of
WSMO
instance innsbruckHbf memberOf station
name hasvalue "Innsbruck Hbf"
code hasvalue "INN"
locatedIn hasvalues {loc:innsbruck}
instance frankfurtHbf memberOf station
name hasvalue "Frankfurt Hbf"
code hasvalue "FKF"
locatedIn hasvalues {loc:frankfurt}
|
Please notice that the link to large set of instances is missing in WSMO. Therefore, in this version of the ontology we only include some example instances, which holds for the other ontologies defined in this use case as well. The inclusion of links to large set of instances will be considered in future versions of WSMO.
The "Date and Time Ontology" in Listing 2 defines models for dates (i.e. certain days) and time (i.e. definition of certain points in time). Further, it defines axioms that represent conventional aspects of date and time, like ´before´ and ´after´, etc. In the use case, this is needed to determine validity of train connections, e.g for ensuring that a ticket is not for an itinerary that is in the past. It also can be used generally for expressing dates and time and relationships between them.
The main ontology taken into consideration for developing this conceptual model of Date and Time is an entry sub-ontology of time, available at http://www.isi.edu/~pan/damltime/time-entry.owl. This ontology uses abstract temporal concepts like instant, interval and event and uses the Gregorian calendar as representation (partly using own encoding and partly using XSD encoding). Axioms are defined in first order logic in the accompanying paper [Pan and Hobbs]; there also is a LISP version of these axioms available at http://www.cs.rochester.edu/~ferguson/daml/daml-time-20030728.lisp. Other ontologies like COBRA calenderclock ontology (http://daml.umbc.edu/ontologies/cobra/0.4/calendarclock) are only a straight forward representation of the Gregorian calendar, without any abstraction of concepts and description of axioms. Widely used concrete representations for date and time are defined in ISO 8601 (Numeric representation of Dates and Time) and in the XML Schema Definition (http://www.w3.org/TR/xmlschema-2/), which is based on ISO 8601.
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/dt.wsml
namespace
default=http://www.wsmo.org/ontologies/dateTime#,
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418#
non-functional-properties
dc:title "Date and Time Ontology"
dc:creator "DERI International"
dc:subject "Date", "Time", "Date and Time Algebra"
dc:description "generic representation of data and time including basic algebra"
dc:publisher "DERI International"
dc:contributor "Holger Lausen", "Axel Polleres", "Ruben Lara"
dc:date "2004-06-28"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#ontos
dc:format "text/plain"
dc:language "en-US"
dc:relation http://www.isi.edu/~pan/damltime/time-entry.owl,
http://www.w3.org/TR/xmlschema-2/
dc:coverage "World"
dc:rights http://www.deri.org/privacy.html
version "$Revision: 1.12 $"
comment: conceptDefinitions
concept instant
non-functional-properties
dc:description "An instant represents a particular point in time and is the superconcept
of all concrete representations such as the Gregorian calendar"
concept interval
non-functional-properties
dc:description "An interval represents a duration between 2 points in time"
start oftype instant
end oftype instant
concept date
non-functional-properties
dc:description "concept date and its representation according to the Gregorian Calendar"
subconcept-of instant
dayOfMonth oftype dayOfMonth
monthOfYear oftype monthOfYear
year oftype year
concept dayOfMonth
non-functional-properties
dc:description "day of a month is represented by an integer"
subconcept-of xsd:integer
concept year
non-functional-properties
dc:description "year is represented by an integer"
subconcept-of xsd:integer
concept monthOfYear
non-functional-properties
dc:description "monthOfYear is represented by an integer"
subconcept-of xsd:integer
concept time
hourOfDay oftype hourOfDay
minuteOfHour oftype minuteOfHour
secondOfMinute oftype secondOfMinute
concept secondOfMinute
non-functional-properties
dc:description "a secondOfMinute is represented by an integer"
subconcept-of xsd:integer
concept minuteOfHour
non-functional-properties
dc:description "a minuteOfHour is represented by an integer"
subconcept-of xsd:integer
concept hourOfDay
non-functional-properties
dc:description "a hourOfDay is represented by an integer"
subconcept-of xsd:integer
concept dateAndTime
non-functional-properties
dc:description "concept date and time and representing together a specific point of time (instant)"
subconcept-of instant
date oftype date
time oftype time
comment: variableDefinitions
variable X, Y, Z, D1, D2 memberOf topConcept
variable A, B, C, D, E, F, JDN, JDN_D1, JDN_D2, SFM_T1, SFM_T2 memberOf xsd:integer
variable T, T1, T2 memberOf time
comment: functionDefintions
function julianDayNumber
non-functional-properties
dc:description "The Julian Day Count is a uniform count of days from a remote epoch
in the past (about 4712 BC). At this instant, the Julian Day Number is 0. Once
you have the Julian Day Number of a particular date in history, it is easy to
calculate time elapsed between it and any other Julian Day Number"
dc:source http://quasar.as.utexas.edu/BillInfo/JulianDatesG.html
parameter instant oftype instant
non-functional-properties
dc:descripion "For each instant there should exist a corresponding Julian Day
Number, however it may not be always defined only by this binary predicate,
e.g. if the instant is represented as Gregorian Date and it is a date between
1582 and 1924. A country must be given as third parameter (since e.g. Greece
changed no earlier then 9th of March 1924 from the Julian to the Gregorian Calendar)"
comment: The following dc:source indicates which country changed in which year
comment: from the Julian to the Gregorian Calendar
dc:source http://members.brabant.chello.nl/~h.reints/cal/whenjul2greg.htm
range oftype xsd:integer
function daysBetween
non-functional-properties
dc:description "(Instant1, Instant2, Difference) is a triple of the ternary relation
corresponding to this function iff Instant1 and Instant2 are members of the concept
'instant' (particular point in time) and Instant2 is 'Difference' days after Instant1."
parameter instant1 oftype instant
parameter instant2 oftype instant
range oftype xsd:integer
function secondsBetween
non-functional-properties
dc:description "(Instant1, Instant2, Difference) is a triple of the ternary relation
corresponding to this function iff Instant1 and Instant2 are members of the concept
'instant' (particular point in time) and Instant2 is 'Differnce' seconds after Instant1."
parameter instant1 oftype instant
parameter instant2 oftype instant
range oftype xsd:integer
function secondsFromMidnight
non-functional-properties
dc:description "(Time, SecondsFromMidnight) is a tuple of the binary relation
corresponding to this function iff SecondsFromMidnight are the seconds elapsed from
00:00:00 of the same day.
This simplifies the axiomatization of the difference between two given times"
parameter time oftype time
range oftype xsd:integer
comment: relationDefintions
relation contains
non-functional-properties
dc:description "(Interval, X) is a tuple of the binary relation
corresponding to this function iff Interval contains X and X is an instant or an
interval"
parameter interval oftype interval
parameter intervalOrInstant oftype (instant or interval)
comment: axiomDefinitions
axiom invalidMonthOfYear
non-functional-properties
dc:description "integrity constraint for valid monthOfYear"
logical-expression
"<-
X memberOf monthOfYear and
(X < 1 or X > 12)."
axiom invalidDayOfMonth
non-functional-properties
dc:description "integrity constraint for valid dayOfMonths"
logical-expression
"<-
X memberOf dayOfMonth and
(X < 1 or X > 31)."
axiom validDate
non-functional-properties
dc:description "Integrity Constraints for date.
The dayOfMonth is valid in dependency of the actual monthOfYear, in a leap
year the month 2 of the Year has 29 days otherwise 28. For leap years holds
the following: Every year divisible by 4 is a leap year.
However, every year divisible by 100 is not a leap year; and every year divisible by
400 is a leap year after all.
Note: This axiomatization is still imprecise, since the country plays a role
when defining a valid day of the month: E.g. 1712 was a double leap year
in Sweden, i.e. February 1712 had 30 days in Sweden.
The mathematical function symbol modulo is assumed to be defined elsewhere
as that it returns the remainder after an integer division of its
first argument by its second"
dc:source http://www.tondering.dk/claus/cal/node3.html
logical-expression
"<-
X memberOf date and (
(X.dayOfMonth > 28 and X.monthOfYear = 2,
not ((modulo(X.year ,4) = 0 and not modulo(X.year ,100) = 0)
or modulo(X.year ,400) = 0))
or (X.dayOfMonth > 29 , X.monthOfYear = 2)
or (X.dayOfMonth > 30 , X.monthOfYear = 4)
or (X.dayOfMonth > 30 , X.monthOfYear = 6)
or (X.dayOfMonth > 30 , X.monthOfYear = 9)
or (X.dayOfMonth > 30 , X.monthOfYear = 11)
)."
axiom invalidHourOfDay
non-functional-properties
dc:description "integrity constraint for valid hourOfDay:"
logical-expression
"<-
X memberOf hourOfDay and
(X < 0 or X >= 24)."
axiom invalidMinuteOfHour
non-functional-properties
dc:description "integrity constraint for valid minuteOfHour:"
logical-expression
"<-
X memberOf minuteOfHour and
(X < 0 or X >= 60)."
axiom invalidSecondOfMinute
non-functional-properties
dc:description "integrity constraint for valid secondOfMinute:"
logical-expression
"<-
X memberOf secondOfMinute and
(X < 0 or X >= 60)."
axiom invalidInterval
non-functional-properties
dc:description "computes if a interval X contains a second interval Y"
logical-expression
"<-
X memberOf interval and X.start >= X.end."
axiom equalityDate
non-functional-properties
dc:description "computes equality of a date"
logical-expression
"X = Y <-
Y memberOf date and X memberOf date and
X.dayOfMonth = Y.dayOfMonth and
X.monthOfYear = Y.monthOfYear and
X.year = Y.year."
axiom beforeDate
non-functional-properties
dc:description "computes if a given date X is before another date Y"
logical-expression
"X < Y <-
Y memberOf date and X memberOf date and
((X.dayOfMonth = Y.dayOfMonth and X.monthOfYear = Y.monthOfYear and X.year = Y.year) or
(X.monthOfYear < Y.monthOfYear and X.year = Y.year) or
(X.year < Y.year))."
axiom afterDate
non-functional-properties
dc:description "defined as inverse of beforeDate"
logical-expression
"X > Y <- Y < X"
axiom julianDayNumber
non-functional-properties
dc:description "This axiom describes how the correct Julian Day Number
can be computed for a given Gregorian Calendar Date. Note
that the Gregorian Calendar was introduced in 15.October 1582.
however until 1919 this axiomatization is not unambiguous since the country
should be taken into to account as 3rd parameter (e.g. Greece
changed at the 9 Mar 1924 from the Julian to the Gregorian calendar).
Details to the axiomatization
If the month is January or February we subtract 1 from the year to get a new Year
and add 12 to the month to get a new Month. (Thus, we are thinking of January and
February as being the 13th and 14th month of the previous year and March is the
start of the year, this simplifies the calculation considering the leap year)
Within the calculation the fractional part of all results has to be dropped,
here we use the function symbol floor() [it can be rewritten as predicate,
however it gets less readable]
A more lengthy description of this axiomatization can be found at
http://quasar.as.utexas.edu/BillInfo/JulianDatesG.html"
dc:source http://quasar.as.utexas.edu/BillInfo/JulianDatesG.html,
http://members.brabant.chello.nl/~h.reints/cal/whenjul2greg.htm
logical-expression
"julianDayNumber(X) = JDN <-
X memberOf date and
((
X.monthOfYear < 3 and
Y = X.year -1 and
M = X.monthOfYear + 12
)
or
(
X.monthOfYear > 2 and
Y = X.year and
M = X.monthOfYear
))
and
D = X.dayOfMonth and
A = floor(Y / 100) and
B = floor(A / 4) and
C = 2 - A + B and
E = floor(365.25 * (Y + 4716)) and
F = floor(30.6001 * (M + 1)) and
JDN = C + D + E + F - 1524."
axiom daysBetweenDates
non-functional-properties
dc:description "the difference in days between 2 dates"
logical-expression
"daysBetween(D1, D2) hasvalue X <-
D1 memberOf date and D2 memberOf date and
X = julianDayNumber(D1) - julianDayNumber(D2)."
axiom equalityTime
non-functional-properties
dc:description "computes if two given times are the same"
logical-expression
"X = Y <-
X memberOf time and Y memberOf time and
X.secondOfMinute = Y.secondOfMinute and
X.minuteOfHour = Y.minuteOfHour and
X.hourOfDay = Y.hourOfDay."
axiom beforeTime
non-functional-properties
dc:description "computes if a given time X is before another time Y"
logical-expression
"X < Y <-
X memberOf time and Y memberOf time and
((X.secondOfMinute < Y.secondOfMinute and X.minuteOfHour = Y.minuteOfHour and X.hourOfDay = Y.hourOfDay) or
(X.minuteOfHour < Y.minuteOfHour and X.hourOfDay = Y.hourOfDay) or
(X.hourOfDay < Y.hourOfDay))."
axiom afterTime
non-functional-properties
dc:description "defined as inverse of beforeTime"
logical-expression
"X > Y <- Y < X."
axiom secondsFromMidnight
non-functional-properties
dc:description "computes the amount of seconds from midnight"
logical-expression
"secondsFromMidnight(T) hasvalue X <-
T memberOf time and
X = T.secondOfMinute + (T.minuteOfHour*60) + (T.hourOfDay*60*60)."
axiom secondsBetweenTimes
non-functional-properties
dc:description "the difference in seconds between 2 times"
logical-expression
"secondsBetween(T1, T2) hasvalue X <-
T1 memberOf time and T2 memberOf time and
X = secondsFromMidnight(T1) - secondsFromMidnight(T2)."
axiom equalityDateAndTime
non-functional-properties
dc:description "computes if Date and Time are equal"
logical-expression
"X = Y <-
X memberOf dateAndTime and Y memberOf dateAndTime and
X.date = Y.date and
X.time = Y.time."
axiom beforeDateAndTime
non-functional-properties
dc:description "computes if a given date and time X is before another date and time Y"
logical-expression
"X < Y <-
X memberOf dateAndTime and Y memberOf dateAndTime and
((X.date = Y.date and X.time < Y.time) or
X.date < Y.date)."
axiom afterDateAndTime
non-functional-properties
dc:description "defined as inverse of beforeDateAndTime"
logical-expression
"X > Y <- X
memberOf dateAndTime and Y memberOf dateAndTime and
Y < X."
axiom secondsBetweenDateAndTime
non-functional-properties
dc:description "computes the difference in seconds between two different DateAndTime"
logical-expression
"secondsBetween(D1, D2) = X <-
D1 memberOf dateAndTime and D2 memberOf dateAndTime and
X = secondsFromMidnight(D1.time) + julianDayNumber(D1.date) * 24 * 60 * 60 -
(secondsFromMidnight(D2.time) + julianDayNumber(D2.date) * 24 * 60 * 60)."
axiom daysBetweenDateAndTime
non-functional-properties
dc:description "the difference in days between two different DateAndTime"
logical-expression
"daysBetween(D1, D2) hasValue X <-
D1 memberOf dateAndTime and D2 memberOf dateAndTime and
X = daysBetween(D1.date, D2.date)."
axiom intervalContainment
non-functional-properties
dc:description "computes if a interval X contains a second interval Y"
logical-expression
"contains(X, Y) <-
X memberOf interval and Y memberOf interval and
(X.start < Y.start or X.start = Y.start) and
(X.end > Y.end or X.end = Y.end)."
axiom instantContainment
non-functional-properties
dc:description "computes if a interval X contains a instant Y"
logical-expression
"contains(X, Y) <-
X memberOf interval and Y memberOf instant and
(X.start < Y or X.start = Y) and
(X.end > Y or X.end = Y)."
|
The "Purchase" ontology defines general concepts for purchasing a product (there is a buyer, a seller, a product with a price, a payment method, and delivery). At the current state this is a preliminary domain ontology for products, purchases, and payment methods. This ontology will be re-designed and enhanced in future versions. In order to provide a general purchase ontology, several existing conceptualizations are considered as a starting point, inter alia:
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/po.wsml
namespace
default=http:://www.wsmo.org/ontologies/purchase#,
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418#,
loc=http:://www.wsmo.org/ontologies/location#,
cu=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlCurrencyMediator.wsml#,
dt=http:://www.wsmo.org/ontologies/dateTime#
non-functional-properties
dc:title "Purchase Ontology"
dc:creator "DERI International"
dc:subject "Buyer", "Seller", "Product", "Price",
"Payment method", "Delivery"
dc:description "general purchase ontology"
dc:publisher "DERI International"
dc:contributor "Michael Stollberg", "Axel Polleres", "Ruben lara", "Holger Lausen"
dc:date "2004-06-28"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#ontos
dc:format "text/plain"
dc:language "en-US"
dc:relation
http://www.daml.ecs.soton.ac.uk/ont/currency.daml,
http:://www.wsmo.org/ontologies/location,
http:://www.wsmo.org/ontologies/dateTime
dc:coverage "ID:7029392 Name:World"
dc:rights http://www.deri.org/privacy.html
version "$Revision: 1.16 $"
usedMediators
ooMediators
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlCurrencyMediator.wsml,
http:://www.wsmo.org/ontologies/location,
http:://www.wsmo.org/ontologies/dateTime
comment: conceptDefinitions
concept buyer
non-functional-properties
dc:description "Buyer of some items"
shipTo oftype loc:address
billTo oftype loc:address
purchaseIntention oftype set tradeItem
hasPayment oftype set paymentMethod
concept seller
non-functional-properties
dc:description "Seller of some items"
address oftype loc:address
saleIntention oftype set tradeItem
acceptsPayment oftype set paymentMethod
concept tradeItem
non-functional-properties
dc:description "A trade item"
product oftype product
pricelimit oftype price
concept product
non-functional-properties
dc:description "Generic product"
name oftype xsd:string
concept price
non-functional-properties
dc:description "Generic price"
amount oftype xsd:float
currency oftype cu:currency
concept paymentMethod
non-functional-properties
dc:description "Payment method for a trade"
name oftype xsd:string
concept trade
non-functional-properties
dc:description "A trade is an actual agreement on trading items between two trading partners"
items oftype set tradeItem
buyer oftype buyer
seller oftype seller
payment oftype paymentMethod
concept delivery
non-functional-properties
dc:description "Delivery of a good as an effect of a purchase"
products oftype set product
receiver oftype buyer
sender oftype seller
concept creditCard subconceptOf paymentMethod
non-functional-properties
dc:description "A credit card"
holder oftype xsd:string
expMonth oftype dt:monthOfYear
expYear oftype dt:year
type oftype xsd:string
concept cash subconceptOf paymentMethod
non-functional-properties
dc:description "Cash payment method"
currency oftype cu:currency
comment: variableDefinitions
variable T memberOf tradeItem
variable P memberOf price
comment: instanceDefinitions
comment: A link to large set of instances is missing in WSMO.
The inclusion of links to large set of instances will be considered
in future versions of WSMO.
A complete list of currencies can be found at
http://www.daml.ecs.soton.ac.uk/ont/currency.daml
|
The "Locations Ontology" defines an concepts for locations, including cities and states, as well as postal addresses. This general ontology builds upon the OWL-Factbook and Address ontology, and it can be re-used in different settings.
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/loc.wsml
namespace
default=http:://www.wsmo.org/ontologies/location#,
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418#,
cnt=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlFactbookMediator.wsml#,
ad=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlAddressMediator.wsml#,
xsd=http://www.w3.org/2001/XMLSchema#
non-functional-properties
dc:title "Locations Ontology"
dc:creator "DERI International"
dc:subject "Location", "Country", "State", "City", "Address"
dc:description "Ontology for representing ontologies in the current political/social system"
dc:publisher "DERI International"
dc:contributor "Ruben Lara", "Axel Polleres"
dc:date "2004-06-28"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#ontos
dc:format "text/plain"
dc:language "en-US"
dc:relation
http://www.daml.org/2001/09/countries/fips-10-4-ont,
http://www.daml.org/2001/09/countries/iso-3166-ont,
http://www.daml.org/2003/09/factbook/factbook-ont,
http://daml.umbc.edu/ontologies/ittalks/address
dc:coverage "ID:7029392 Name:World"
dc:rights http://www.deri.org/privacy.html
version "$Revision: 1.7 $"
usedMediators
ooMediator
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlFactbookMediator.wsml,
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/owlAddressMediator.wsml
comment: conceptDefinitions
concept location
non-functional-properties
dc:description "General notion of location"
name oftype xsd:string
country oftype set country
concept country subconcept cnt:country
non-functional-properties
dc:description "Add the codes to the CIA country properties"
comment: FIPS 10-4 Country Code
fipsCode oftype xsd:string
comment: ISO 3166 Country Code
isoCode oftype xsd:string
concept address subconceptOf ad:address
non-functional-properties
dc:description "Extended address, adding more details to
city, state and country"
city oftype city
state oftype state
country oftype country
concept city subconceptOf location
non-functional-properties
dc:description "City"
state oftype state
population oftype xsd:integer
extension oftype xsd:integer
non-functional-properties
dc:description "Extension of the city in square kilometers"
zipcodes oftype set xsd:string
concept state subconceptOf location
non-functional-properties
dc:description "State"
cities oftype set city
population oftype xsd:integer
extension oftype xsd:integer
concept border subconceptOf location
non-functional-properties
dc:description "Border between two countries. Notice that it
would be more natural to model this as a location with a cardinality
constraint = 2 for the country property. However, it is not clear
how to do this in F-Logic"
countryA oftype country
countryB oftype country
concept distance
non-functional-properties
dc:description "Distance between two points"
amount oftype xsd:float
units oftype xsd:string
kilometers oftype xsd:float
miles oftype xsd:float
comment: variableDefinitions
variable D, D1, D2 memberOf distance
variable U memberOf xsd:string
variable A memberOf xsd:float
comment: axiomDefinitions
axiom validDistance
non-functional-properties
dc:description "The amount in a distance cannot be less than 0.
We only accept kilometers and miles."
logical-expression
"<-
D[
amount hasvalue A,
units hasvalue U]
and A < 0
and not (U="Kilometers" or U="Miles")."
axiom kilometers
non-functional-properties
dc:description "Calculation for the kilometers property of distance"
logical-expression
"D[
amount hasvalue A,
units hasvalue U] and
( (U="Kilometers" and kilometers=A) or
(U="Miles" and kilometers=A*1.609344))."
axiom miles
non-functional-properties
dc:description "Calculation for the miles property of distance"
logical-expression
"D memberOf distance[
amount hasvalue A,
units hasvalue U] and
( (U="Miles" and miles=A) or
(U="Kilometers" and miles=A/1.609344)."
axiom equalityDistance
non-functional-properties
dc:description "Computes equality of a distance"
logical-expression
"D1 = D2 <-
D1.kilometers = D2.kilometers."
axiom lessThanDistance
non-functional-properties
dc:description "Computes -less than- for a distance"
logical-expression
"D1 < D2 <-
D1.kilometers < D2.kilometers."
axiom moreThanDistance
non-functional-properties
dc:description "Computes -more than- for a distance"
logical-expression
"D1 > D2 <-
D1.kilometers > D2.kilometers."
comment: instanceDefinitions
comment: "A link to large set of instances is missing in WSMO.
Therefore, in this version of the ontology we only include
some example instances. The inclusion of links to large
set of instances will be considered in future versions of
WSMO"
instance austria memberOf country
fipsCode hasvalue "AU"
isoCode hasvalue "AT"
instance germany memberOf country
fipsCode hasvalue "GM"
isoCode hasvalue "DE"
instance usa memberOf country
fipsCode hasvalue "US"
isoCode hasvalue "US"
instance innsbruck memberOf city
name hasvalue "Innsbruck"
country hasvalue austria
instance frankfurt memberOf city
name hasvalue "Frankfurt"
country hasvalue germany
instance boston memberOf city
name hasvalue "Boston"
country hasvalue usa
instance massachusetts memberOf state
name hasvalue "Massachusetts"
country hasvalue usa
|
Goals denote what a user wants as the result of the Web Service. For modeling the goal, we describe the information elements that the user wants to get from the service (the postcondition) together with the state of the world desired after the service execution (the effect).
In our use case, we have one Goal: a user wants to buy a train itinerary from Innsbruck to Frankfurt on a certain date. The Goal states that the desire is to get the description of the itinerary bought, and that the effect of the Web Service has to be a trade between the train company and the requester for the desired itinerary. Listing 5 shows this Goal with the following elements:
goal http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/goal.wsml
namespace
default=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040628/resources/goal#,
dc=http://purl.org/dc/elements/1.1#,
dt=http:://www.wsmo.org/ontologies/dateTime#,
tc=http:://www.wsmo.org/ontologies/trainConnection#,
po=http:://www.wsmo.org/ontologies/purchase#,
loc=http:://www.wsmo.org/ontologies/location#,
wsml=http://www.wsmo.org/2004/d2/#
non-functional-properties
dc:title "Buying a ticket for a train trip"
dc:creator "DERI International"
dc:subject "Train Tickets", "Online Ticket Booking", "Train trip"
dc:description "Express the goal of buying a ticket for a train trip"
dc:publisher "DERI International"
dc:contributor "Michael Stollberg", "Ruben Lara", "Holger Lausen", "Axel Polleres"
dc:date "2004-06-07"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#L3958
comment: MIME type according to [RFC2646,RFC2046]
dc:format "text/plain"
comment: langugae definition according [RFC3066, ISO639]
dc:language "en-us"
dc:relation
http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/trainConnection,
http:://www.wsmo.org/ontologies/purchase,
http:://www.wsmo.org/ontologies/location
dc:coverage "ID:7029392 Name:World"
dc:rights http://deri.at/privacy.html
version "$Revision: 1.8 $"
usedMediators
http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/trainConnection,
http:://www.wsmo.org/ontologies/purchase,
http:://www.wsmo.org/ontologies/location
postcondition
axiom buyATicketForItinerary
non-functional-properties
dc:description "The goal postcondition is represented as a fact, in this case the fact is
only specified partly, e.g. for the time of departure the minute and seconds
are not specified.
It represents that 'Tim Berners-Lee' wants to go from innsbruckHbf to frankfurtHbf departing
from innsbruckHbf at 17.07.2004 18h"
logical-expression
"someItinerary memberOf tc:itinerary[
trip hasValue someTrip memberOf tc:trainTrip[
start hasValue innsbruckHbf,
end hasValue frankfurtHbf,
departure hasValue _# memberOf dt:dateAndTime[
date hasValue _# memberOf dt:date[
dayOfMonth hasValue 17,
monthOfYear hasValue 7,
year hasValue 2004
],
time hasValue _# memberOf dt:time[
hourOfDay hasValue 18
]
]
],
passenger hasValue _# memberOf loc:person[
firstName hasValue "Tim",
lastName hasValue "Bernsers-Lee",
email hasValue "timbl@w3.org"
]
]."
effect
axiom havingTradeForTrip
non-functional-properties
dc:description "The goal effect is represented as a fact
It represents that 'Tim Berners-Lee' wants to have a trade
with a provider (not specified) for the itinerary given;
the ticket should be delivered to his address and he wants
to pay by credit card"
logical-expression
"sometrade memberOf po:trade[
items hasValues someTrip,
buyer hasValue _# memberOf po: buyer[
shipTo hasValue timsAddress memberOf loc:address[
roomNumber hasValue 3,
streetAddress hasValue 'Tims street',
city hasValue boston,
state hasValue massachusetts,
zip hasValue 02103
],
billTo hasValue timsAddress
],
payment hasValue _# memberOf po:creditCard[
holder hasValue 'Tim Berners-Lee',
expMonth hasValue 9,
expYear hasValue 2007,
type hasValue 'MasterCard'
]
]."
|
Notice that an instance of the concept 'Itinerary' is used as the value of the property 'Items' of the concept 'Trade'. In the ontologies defined above, Itinerary is not defined in tc.wsml as a subconcept of po:product. This subclassing should be done by an OO-mediator that imports the terminology required for the goal and takes care of this operation. Such a mediator will be included in the next version of this deliverable.
As explained above, we define one (imaginary) Web Service in this use case: an end-user service (means that the user interacts with this service) for purchasing international train tickets offered by the Austrian national train operator ÖBB, which is composed of other Web Services, each for the search and buying facility of international train tickets. This setting allows modeling all notions of a WSMO Web Service description: A Capability of the end-user service and its Choreography for user-service interaction, as well as the orchestration which incorporates the aggregated Web Services. The current version of WSMO Standard does only provide a stable specification for describing Capabilities, the model below is restricted to the overall Web Service description and the Capability definition. The modeling for the WSMO Web Service Interface will be added in a later version.
A Web Service Capability in WSMO is described by pre- and postconditions, assumptions and effects, as defined in [Roman et al., 2004]. More detailed discussion of the Discovery mechanism of WSMO Goals and Capabilities is provided in section 3.1.3.
webservice http://www.wsmo.org/2004/d3/d3.2/v0.1/20040526/resources/ws.wsml
namespace
default=http://www.wsmo.org/2004/d3/d3.2/v0.1/20040526/resources/ws#
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d2/#
dt=http:://www.wsmo.org/ontologies/dateTime#,
tc=http:://www.wsmo.org/ontologies/trainConnection#,
po=http:://www.wsmo.org/ontologies/purchase#,
loc=http:://www.wsmo.org/ontologies/location#,
non-functional-properties
dc:title "ÖBB Online Ticket Booking Web Service"
dc:creator "DERI International"
dc:subject
dc:description "web service for booking online train tickets for Austria and Germany"
dc:publisher "DERI International"
dc:contributor "Michael Stollberg", "Ruben Lara", "Holger Lausen"
dc:date "2004-06-03"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/##L3966
comment: MIME type according to [RFC2646,RFC2046]
dc:format "text/plain"
comment: language definition according [RFC3066, ISO639]
dc:language "en-us"
dc:relation http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/trainConnection,
http:://www.wsmo.org/ontologies/purchase,
http:://www.wsmo.org/ontologies/location
dc:coverage tc:austria, tc:germany
dc:rights http://deri.at/privacy.html
version "$Revision: 1.1 $"
usedMediators
http:://www.wsmo.org/ontologies/dateTime,
http:://www.wsmo.org/ontologies/trainConnection,
http:://www.wsmo.org/ontologies/purchase,
http:://www.wsmo.org/ontologies/location
capability
preCondition
non-functional-properties
dc:description "the input has to be a buyer with a purchase intention for
an itinerary wherefore the start- and endlocation have to be in Austria
or in Germany, and the departure date has to be later than the current Date.
Also, a not-expired credit card for payment is expected."
logical-expression
" inputBuyer memberOf po:buyer[
shipTo hasValue BuyerAddress memberOf loc:address,
billTo hasValue BuyerAddress memberOf loc:address,
hasPayment hasValue Payment memberOf po:creditCard,
purchaseIntention hasValue Trip
] and
Trip memberOf tc:trainTrip[
start hasValue Start,
end hasValue End,
departure hasValue Departure
]and
(Start.locatedIn = austria or Start.locatedIn = germany) and
(End.locatedIn = austria or End.locatedIn = germany) and
dt:after(Departure,currentDate) and
(currentDate.date.year < Payment.expYear or
(currentDate.date.monthOfYear =< Payment.expMonth and currentDate.date.year = Payment.expYear))."
assumption
non-functional-properties
dc:description "the account of the credit card has to hold a sufficient amount of money
to pay the ticket."
logical-expression
comment: not specified as the ontological terminology is missing
postCondition
non-functional-properties
dc:description "the output of the service is a train trip wherefore
the start- and endlocation have to be in Austria or in Germany and
the departure date has to be later than the current Date."
logical-expression
"outputTrip memberOf tc:trainTrip[
start hasValue Start,
end hasValue End,
departure hasValue Departure
] and
(Start.locatedIn = austria or Start.locatedIn = germany) and
(End.locatedIn = austria or End.locatedIn = germany) and
dt:after(Departure,currentDate)."
effect
non-functional-properties
dc:description "there shall be a trade for the train trip of the postcondition"
logical-expression
" someTrade memberOf po:trade[
items hasValues outputTrip,
payment hasValue AcceptedPayment memberOf po:creditCard
]."
interface
non-functional-properties
dc:description "describes the Interface of Web Service"
comment: not specified yet.
|
As in the modeling in the Goal, here an instance of the concept 'Itinerary' is used as the value of the property 'Items' of the concept 'Trade', while Itinerary is not defined in tc.wsml as a subconcept of po:product. The OO-mediator that imports the terminology required for the capability and performs this operation willbe included in the next version of this deliverable.
OO-Mediators
OO Mediators "connect" ontologies with other ontologies or OO Mediators for refining ontologies, as well as for importing ontologies as the terminology definitions into other WSMO components. As the Goal and the Web Service specified above have homogeneous information spaces, we only have to specify OO Mediators for the existing ontologies used for the domain ontologies defined in this use case. Here, we have to define the following OO Mediators, specified in the Listings below:
ooMediator
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/owlAddressMediator.wsml
namespace
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418/#
non-functional-properties
dc:title "OO Mediator importing the OWL Factbook ontology to WSML"
dc:creator "DERI International"
dc:publisher "DERI International"
dc:contributor "Axel Polleres"
dc:date "2004-06-07"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#L3962
dc:format "text/plain"
dc:language "en-us"
dc:rights http://deri.at/privacy.html
version "$Revision: 1.3 $"
sourceComponent
ontology http://daml.umbc.edu/ontologies/ittalks/address/
targetComponent
ontology
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/loc.wsml
mediationService
comment: not yet implemented.
comment: should have a full wsml-webservice description, here we only
comment: give the intended endpoint of the future service
comment: http://138.232.65.151:8080/TranslatorService/OWL2WSML/
comment: This source ontology might overlap with the owl person ontology.
comment: Not yet checked. In case, we should have one mediator importing both
comment: and resolving possible overlaps/conflicts.
|
ooMediator http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/owlCurrencyMediator.wsml
namespace
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418/#
non-functional-properties
dc:title "OO Mediator importing the OWL Currency ontology to WSML"
dc:creator "DERI International"
dc:publisher "DERI International"
dc:contributor "Holger Lausen"
dc:date "2004-06-07"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#L3962
dc:format "text/plain"
dc:language "en-us"
dc:rights http://deri.at/privacy.html
version "$Revision: 1.3 $"
sourceComponent
ontology http://www.daml.ecs.soton.ac.uk/ont/currency.daml
targetComponent
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/po.wsml
mediationService
comment: not yet implemented.
comment: should have a full wsml-webservice description, here we only
comment: give the intended endpoint of the future service
comment: http://138.232.65.151:8080/TranslatorService/OWL2WSML/
|
ooMediator
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/owlFactbookMediator.wsml
namespace
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418/#
non-functional-properties
dc:title "OO Mediator importing the OWL Factbook ontology to WSML"
dc:creator "DERI International"
dc:publisher "DERI International"
dc:contributor "Axel Polleres"
dc:date "2004-06-07"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#L3962
dc:format "text/plain"
dc:language "en-us"
dc:rights http://deri.at/privacy.html
version "$Revision: 1.4 $"
sourceComponent
ontology http://www.daml.org/2003/09/factbook/factbook-ont/
targetComponent
ontology
http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/loc.wsml
mediationService
comment: not yet implemented.
comment: should have a full wsml-webservice description, here we only
comment: give the intended endpoint of the future service
comment: http://138.232.65.151:8080/TranslatorService/OWL2WSML/
|
ooMediator http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/owlPersonMediator.wsml
namespace
dc=http://purl.org/dc/elements/1.1#,
wsml=http://www.wsmo.org/2004/d16/d16.1/v0.2/20040418/#
non-functional-properties
dc:title "OO Mediator importing the OWL Person ontology to WSML"
dc:creator "DERI International"
dc:publisher "DERI International"
dc:contributor "Axel Polleres"
dc:date "2004-06-07"
dc:type http://www.wsmo.org/2004/d2/v0.3/20040329/#L3962
dc:format "text/plain"
dc:language "en-us"
dc:rights http://deri.at/privacy.html
version "$Revision: 1.3 $"
sourceComponent
ontology http://daml.umbc.edu/ontologies/ittalks/person/
targetComponent
ontology http://www.wsmo.org/2004/d3/d3.2/v0.1/20040607/resources/tc.wsml
mediationService
comment: not yet implemented.
comment: should have a full wsml-webservice description, here we only
comment: give the intended endpoint of the future service
comment: http://138.232.65.151:8080/TranslatorService/OWL2WSML/
comment: This source ontology might overlap with the owl address ontology.
comment: Not yet checked. In case, we should have one mediator importing both
comment: and resolving possible overlaps/conflicts.
|
Notice that the mediation services are not specified. For importing an OWL ontology into a WSML ontology, it is obvious that such mediation services are required. The terminology to express the capability of mediation services as well as the requester goals is not defined at the moment. This terminology, modeling the ontology mediation domain, has to be included in future versions of the deliverable and the necessary goals and capabilities have to be defined using such terminology.
WG-Mediators
A WG Mediator links a Web Service to a Goal, resolves terminological
mismatches, and states the functional difference (if any) between both.
The main application of WG Mediators is handling of partial matches
within Web Service discovery. For resolving terminological mismatches,
OO Mediators are applied, similar to the ones specified above. The
functional difference is stated in the reduction which restricts the
set of valid ontology objects to be passed between the Web Service and
the Goal.
In our use case, we do not need an WG Mediator, because the Goal and the Web Service Description use the same domain ontologies (i.e. there are not terminology mismatches), and there is no functional differences between the Goal and the Capability. An WG Mediator with a reduction would be needed if the Web Service Capability specifies that train tickets as well as plane tickets are sold: Therefore, the reduction would restrict the valid set of information to train tickets, as requested by the Goal.
GG-Mediators
A GG Mediator connects Goals, specifying the possible functionality
reduction. For example, a GG Mediator would connect a Goal "buy a
ticket" with another Goal "buy a train ticket" by stating the
ontological correspondance between the Goals as a reduction. If 'train
ticket' is a subclass of 'ticket', than the reduction in the GG
Mediator would specify that valid instances for the second Goal have to
be 'train ticket subclassof ticket'.