04.11.2014 Views

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

180 Selected Studies on Software and Information Systems<br />

WSMO corresponds to the meta-model layer of the architecture. A WSMO description<br />

of a concrete web service is related to the model layer. The concrete web service is placed in<br />

the information layer.<br />

MOF<br />

metametamodel<br />

M3 Layer<br />

metamodel<br />

M2 Layer<br />

WSMO<br />

model<br />

information<br />

M1 Layer<br />

M0 Layer<br />

WSMO descriptions<br />

Concrete Web Services, Domains<br />

and Data to be described<br />

Figure 6-10. The relation between WSMO and MOF (retrieved from [70]).<br />

WSMO identifies four top-level elements which define the semantics of the web service:<br />

– Ontologies: provide a vocabulary to describe different aspects of web services.<br />

– Web services: represent computational entities able to provide access to services. Web<br />

service is in WSMO described from three points of view: non-functional, functional<br />

and behavioral. The functionality is described by one and only one capability. The<br />

behavior may be described by multiple interfaces.<br />

– Goals: describe aspects related to user desires with respect to the requested functionality.<br />

It is characterized in dual way. The goal’s description includes the requested<br />

capability and requested interface.<br />

– Mediators: describe elements that handle interoperability problems between different<br />

WSMO elements. They describe elements aiming at overcoming structural, semantic<br />

and conceptual mismatches between them.<br />

To express the WSMO model, WSMO uses the WSML language [30].<br />

6.3 Semantic Web Service Coordination<br />

Semantic web service coordination aims at satisfying the users’ goals using Semantic web<br />

service discovery, composition and execution [45]. Figure 6-11 presents an overview of the<br />

utilization of web service composition by a user. The user can be a human, an agent or an<br />

application invoking the service. The first step of this process is gathering the information<br />

about the goal. For this goal, taking the input data and considering preconditions, the<br />

composition process starts including web services discovery. The discovery is responsible<br />

for searching for the web services in the available registries. During composition the domain<br />

knowledge is exploited to enhance the used methods. The domain knowledge is stored<br />

in ontologies linked to the Semantic web services’ descriptions. When the composition is<br />

constructed, it is executed. This results in output data and effects in which the user is<br />

interested in.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!