21.01.2014 Views

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.2. SEMANTIC INTEROPERABILITY AND PROCESS ONTOLOGIES 45<br />

linking the parameters to a resource class which is defined separately from the process<br />

ontology.<br />

The Intelligent S<strong>of</strong>tware Agents Lab at Carnegie Mellon University has played a<br />

critical role in the development <strong>of</strong> OWL-S from its very conception. In addition, the<br />

S<strong>of</strong>tagent Group has also developed the most complete and integrated set <strong>of</strong> OWL-S<br />

development tools, the OWL-S IDE. However, OWL-S is criticized to suffer conceptual<br />

ambiguity, lack concise axiomatization, be designed too loosely and <strong>of</strong>fer an overly<br />

narrow view on Web services [106].<br />

3.2.7 WSMO (Web Service Modeling Ontology)<br />

WSMO is a conceptual model <strong>for</strong> describing various aspects related to <strong>Semantic</strong> Web<br />

services. The objective <strong>of</strong> WSMO and its accompanying ef<strong>for</strong>ts is to solve the application<br />

integration problem <strong>for</strong> Web services by defining a coherent technology <strong>for</strong><br />

<strong>Semantic</strong> Web services [210].<br />

WSMO provides ontological specifications <strong>for</strong> the core elements <strong>of</strong> <strong>Semantic</strong> Web<br />

services. The representation <strong>of</strong> WSMO follows the MOF (Meta-Object Facility) [124]<br />

specification, and the MOF constructs Class, sub-Class, Attributes and type are<br />

used in the definition <strong>of</strong> WSMO. Every construct <strong>of</strong> WSMO is called a WSMO element.<br />

There are five top-level elements: annotations, ontologies, Web services, goals<br />

and mediators. WSMO does not contain the constructs to represent any <strong>of</strong> the process<br />

perspectives, but only provide interface to describe the functionality <strong>of</strong> the Web<br />

service. A tw<strong>of</strong>old view on the operational competence <strong>of</strong> the Web service is provided:<br />

choreography decomposes a capability in terms <strong>of</strong> interaction within the Web service;<br />

orchestration decomposes a capability in terms <strong>of</strong> functionality required <strong>for</strong>m other Web<br />

services. The process <strong>of</strong> Web services composition is excluded from WSMO. Another<br />

important feature <strong>of</strong> WSMO is that it introduces the elements Goal and Mediator.<br />

Goal can represent an objective <strong>of</strong> the execution <strong>of</strong> a Web service. Mediator is exploited<br />

to overcome interoperability problems between different WSMO elements. For example,<br />

a wgMediator (Web service to goal Mediator) links Web services to goals, indicating<br />

that the Web service (totally or partially) fulfills the goal to which it is linked. Such a<br />

mediator may explicitly state the difference between the two entities and map different<br />

vocabularies through the use <strong>of</strong> ooMediators (ontology to ontology Mediators) [209].<br />

3.2.8 POP* (<strong>Process</strong>, Organization, Product and others)<br />

POP* methodology is one <strong>of</strong> the research contributions <strong>of</strong> the EU project ATHENA<br />

[139]. The overall objective <strong>of</strong> ATHENA is to enable enterprise to seamlessly interoperate<br />

with others. The POP* methodology aims to develop a set <strong>of</strong> core modeling<br />

methodology elements <strong>for</strong> capturing collaborative enterprises design and management.<br />

It <strong>of</strong>fers a model exchange device by providing a common <strong>for</strong>mat along with a mapping<br />

methodology to define the mappings from the various enterprise modeling languages<br />

to the common <strong>for</strong>mat. The POP* methodology includes a common <strong>for</strong>mat as the exchange<br />

<strong>for</strong>mat — the POP* meta-model containing a set <strong>of</strong> basic modeling constructs.<br />

There are five dimensions included in POP*, namely the <strong>Process</strong>, Organization, Product,<br />

Decision and Infrastructure dimensions [138].

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

Saved successfully!

Ooh no, something went wrong!