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

78 CHAPTER 4. SEMANTIC ANNOTATION FRAMEWORK
Where the cardinalities of both has_inActivity and has_outActivity are 1.
Definition 6. Input and output are defined as parameters of an activity, which include
value and data type. They are usually related to artifacts participating in the activity.
I i = (id, model_f ragment, name, alternative_name, data_type, related_arti f act)
O i = (id, model_f ragment, name, alternative_name, data_type, related_arti f act)
If the same artifact related with both input and output parameters of an activity,
the state of the artifact must change through this activity. We call it transformation.
Definition 7. Precondition and postcondition are presented by expressions to constrain
input and output. The constraints are usually used as contract in services or process
composition.
Θ pre = (id, model_f ragment, name, alternative_name, related_input)
Θ post = (id, model_f ragment, name, alternative_name, related_output)
Definition 8. Exception happens in an activity and it can be handled by an activity.
E i = (id, model_f ragment, name, alternative_name, handler_Activity, same_as,
di f f erent_f rom, kind_o f , superConcept_o f , partialE f f ect_o f ,
compositionConcept_o f , instance_o f )
Exception will be annotated using predefined exception types in a domain ontology.
The activity handling the exception is pointed out by handler_activity.
PSAM is modeled in OWL when it is implemented for annotation applications.
Appendix G.1 presents the OWL representation of a complete PSAM 1 .
4.7 A Simple Example of Process Semantic Annotation
There is a business process model to describe a very simple process of buying merchandise.
It can be reused in any specialized and complicated purchase process. We
assume it is originally built in EEML [77]. This purchase process contains only a task
"purchase". There are two person roles in this task named "Client" and "Seller". The
process starts with a milestone "agreed deal" and ends with a milestone "deal finishes".
One flow links from "agreed deal" to the input port of the task "purchase" and another
flow links from the output port of "purchase" to "deal finishes". A resource role "Order"
coming to the input port is and another resource role "Receipt" is out of the output
port. The EEML process model of a purchase process is illustrated in Figure 4.6.
We applied the semantic annotation approach to annotate the purchase model.
The EEML modeling constructs are annotated with GPO concepts in meta-model annotation.
In this case, EEML modeling constructs are mapped to the GPO concepts
1 A complete PSAM contains the part of PSAM presented in this chapter and the extension part of
PSAM in Chapter 5.