2 CONCEPTUAL MODELLING
OF A COMPOSITION
According to (Payne, 2004) the Semantic Web
technologies use knowledge representation methods
in a distributed environment. Semantic Web
Services, as the new research paradigm, are usually
defined as a improvement of Web Services with
semantic annotations. But these services are based
on different ontologies. The requester agent has to
translate the description of every service from its
own ontology into the Web Service's one to produce
a valid requests.
Our approach proposes to solve this problematic.
We propose a model in three levels: global, local
and physical.
The global level sees a Service as an application
from a set of data E in itself.
At the local level, a Service is an application
which associates a data set equivalent to E
D
, to a
data set equivalent to E
R
.
At the physical level, a Service consists in the
sequence of pages on which we submit or retrieve
data semantically equivalent to those in the union of
E
D
and E
R
.
We will now present these three levels with more
details, then we will explain how we can translate
data or transactions from a level to another.
2.1 Global Level
Let E be the set of concepts expressed when
processing a given Web Service Abstracted, WSA.
We build an ontology for this service, that we name
global data model (GO), and which could be
described in OWL. We name it Abstracted since it is
not related to a concrete implementation of the
Service.
We use a simplified ontology based on two
relationships: generalization and aggregation.
2.2 Local Level
On every web site registered as addressing a service
WSA, we have a local ontology (LO). It is a
specialization of the OWL model described at the
global level.
A site processes a service if there is a morphism
between the global service WSA and (GO) and a
Local Web Service WSL and (LO).
2.3 Physical Level
Concretely, a Web site without SOAP/WSDL
automation completes a Service by browsing a
sequence of pages. On each of these pages, forms
(the most often) allow to express some concepts, the
actual subset of the local ontology.
We browse a sequence pages so that the
aggregation of the concepts expressed is equal to the
input data set of the transaction, then another
sequence whose concepts aggregation contains the
output data subset. We name this sequence a path.
2.4 Formalizing the Three
Abstraction Levels
We associate a table such as Table 1 to every WSA.
We identify the ontology of the service, and the
transactions needed to complete this service. This
global level is completed by local and physical
vision of each service.
For instance, for Service WS
2
, booking a plane
seat, each flight company may, from the concepts of
"departure city", "arrival city" and "departure date"
return the information of availability.
Depending on the concrete architecture of the
flight company site, the path allowing the realisation
of this service won't be the same. The table below
expresses two different sites performing the same
service, one through a simple request, the other
through a composite request.
3 DETECTION OF WEB
SERVICES, CONSTRAINTS,
PHYSICAL COMPOSITION
Constraints between Services are the translation,
from an event standpoint, of user constraints, i.e. the
translation of a constraint in precedence, validation
and triggering between different services. These
constraints are formalized as guards (Singh, 1996).
We propose a methodology to build the physical
resolition map, Algorithm 1:
• Step 1: Identify services to operate to
complete the composition
• Step 2: Identify constraints between these
services
• Step 3: Formalize the resolution of each
Service
WEBIST 2006 - WEB INTERFACES AND APPLICATIONS
462