Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
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 41<br />
• Bundles. A group <strong>of</strong> related specializations. In general, they are grouped based<br />
on questions <strong>of</strong> an activity: how? what? who? when? where? and why? For most<br />
activities in the handbook, some subset <strong>of</strong> these questions provides a systematic<br />
and logical way <strong>of</strong> grouping the different specializations that appear.<br />
• Uses. A list <strong>of</strong> activities where the given activity is used as a part.<br />
• Generalizations. The set <strong>of</strong> activities are type processes <strong>of</strong> the given activity.<br />
Other kinds <strong>of</strong> entries are also used in the process handbook, such as Dependencies<br />
(flow, sharing and fit), Resources (inputs, outputs, actors and locations), and Exceptions<br />
(exception types and ways <strong>of</strong> exception detection, anticipation, avoidance and<br />
solution).<br />
For the process perspectives, the operational/functional perspective <strong>of</strong> a process<br />
is elaborated through the entries <strong>of</strong> an activity. Parts and Uses provide a structural<br />
view <strong>of</strong> activities. Resources and Bundles can specify resources and organizational<br />
perspectives. The control perspective is represented through Dependencies. The data<br />
transaction perspective is not specified explicitly through those entries.<br />
The MIT process handbook contains generic models <strong>of</strong> typical business activities<br />
(e.g. buying, making, and selling) and specific case examples <strong>of</strong> business practices.<br />
They are classified and represented through the entries. In such a way, process knowledge<br />
in the repository looks like business process taxonomy and patterns. The semantics<br />
<strong>of</strong> entries are not <strong>for</strong>mally defined <strong>for</strong> the repository but they can be represented in<br />
PIF [85] to share the process descriptions.<br />
3.2.3 TOVE (Toronto Virtual Enterprise) ontologies<br />
TOVE ontologies are stated as a common sense enterprise model covering a set <strong>of</strong> integrated<br />
ontologies <strong>for</strong> the modeling <strong>of</strong> both commercial and public enterprises. The<br />
TOVE consists <strong>of</strong> a set <strong>of</strong> generic core ontologies, including an activity ontology that<br />
spans activity, state, time and causality, a generic resource ontology describing the<br />
properties <strong>of</strong> the enterprise resources such as machines, electricity or raw materials,<br />
capital, human skill and in<strong>for</strong>mation, an organization ontology spanning structure,<br />
roles, and communication, and a product ontology which includes features, parameters,<br />
assemblies, versions, and revisions. It also includes a set <strong>of</strong> extensions to these<br />
generic ontologies to cover concepts such as cost and quality. However, the primary<br />
component <strong>of</strong> the ontology is the terminology <strong>for</strong> classes <strong>of</strong> processes and relations <strong>for</strong><br />
processes and resources, along with definitions <strong>of</strong> the classes and relations [44]. The<br />
KIF (Knowledge Interchange Format) [29] is the language providing the logical lexicon<br />
<strong>for</strong> the TOVE ontologies. The non-logical part <strong>of</strong> the lexicon consists <strong>of</strong> expressions<br />
(constants, functions, relations) that refer to concepts in some domain.<br />
At the heart <strong>of</strong> the TOVE enterprise model lies the representation <strong>of</strong> an activity<br />
and its corresponding enabling and caused states. Activities and states specify trans<strong>for</strong>mations<br />
by fluent and actions. Axioms <strong>of</strong> temporal projection represent how the<br />
actions change the status <strong>of</strong> a state. A set <strong>of</strong> constants are defined <strong>for</strong> status (<strong>of</strong> state<br />
and <strong>of</strong> activities), and a set <strong>of</strong> actions are defined by functions with parameters <strong>of</strong><br />
the state and the associated activity [101]. Evidently, the data transaction perspective<br />
can be supported by activity ontology. The states related to classes <strong>of</strong> resources