Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ... 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.
4.7. A SIMPLE EXAMPLE OF PROCESS SEMANTIC ANNOTATION 79 Figure 4.6: EEML process model example: purchase process following the mapping rules for meta-model annotation. For example, the EEML Task is one-to-one mapped to the GPO Activity. Based on the meta model annotation, the GPO concepts will take the place of the corresponding process modeling constructs to describe the process. A domain ontology is employed to annotate the model contents which are described in the process annotation model. For instance, the EEML task "purchases" is a GPO activity, and this activity is annotated as a kind of domain ontology concept "buy" in the PSAM model. Figure 4.7 illustrates the annotation results of the purchase model. We exemplify parts of the PSAM instance of annotation results which are represented in OWL. The example here is only a demo of the OWL representation. In the demo the data type of model_fragment is defaulted as URI and the data types of other properties are not specified, which can be compared with the PSAM instances in OWL from exemplars in Appendix H 2 . purchases Purchase 2 The exemplars are introduced in Chapter 7.
- Page 47 and 48: 2.6. PROCESS KNOWLEDGE MANAGEMENT 2
- Page 49 and 50: 2.7. SUMMARY 29 • Creation or imp
- Page 51 and 52: Chapter 3 State of the Art This cha
- Page 53 and 54: 3.1. PROCESS MODELING LANGUAGES 33
- Page 55 and 56: 3.1. PROCESS MODELING LANGUAGES 35
- Page 57 and 58: Table 3.1: Modeling constructs of d
- Page 59 and 60: 3.2. SEMANTIC INTEROPERABILITY AND
- Page 61 and 62: 3.2. SEMANTIC INTEROPERABILITY AND
- Page 63 and 64: 3.2. SEMANTIC INTEROPERABILITY AND
- Page 65 and 66: 3.2. SEMANTIC INTEROPERABILITY AND
- Page 67 and 68: Representation primitives Process P
- Page 69 and 70: 3.3. GOAL MODELING 49 From the surv
- Page 71 and 72: 3.4. SEMANTIC ANNOTATION METHODS AN
- Page 73 and 74: 3.4. SEMANTIC ANNOTATION METHODS AN
- Page 75 and 76: 3.4. SEMANTIC ANNOTATION METHODS AN
- Page 77 and 78: 3.4. SEMANTIC ANNOTATION METHODS AN
- Page 79 and 80: 3.6. SUMMARY 59 In the goal modelin
- Page 81: Part II Design and Application 61
- Page 84 and 85: 64 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 86 and 87: 66 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 88 and 89: 68 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 90 and 91: 70 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 92 and 93: 72 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 94 and 95: 74 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 96 and 97: 76 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 100 and 101: 80 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 102 and 103: 82 CHAPTER 4. SEMANTIC ANNOTATION F
- Page 104 and 105: 84 CHAPTER 5. GOAL ANNOTATION proce
- Page 106 and 107: 86 CHAPTER 5. GOAL ANNOTATION in a
- Page 108 and 109: 88 CHAPTER 5. GOAL ANNOTATION • i
- Page 110 and 111: 90 CHAPTER 5. GOAL ANNOTATION 5.5 G
- Page 112 and 113: 92 CHAPTER 5. GOAL ANNOTATION
- Page 114 and 115: 94 CHAPTER 6. PRO-SEAT (PROCESS SEM
- Page 116 and 117: 96 CHAPTER 6. PRO-SEAT (PROCESS SEM
- Page 118 and 119: 98 CHAPTER 6. PRO-SEAT (PROCESS SEM
- Page 120 and 121: 100 CHAPTER 6. PRO-SEAT (PROCESS SE
- Page 122 and 123: 102 CHAPTER 6. PRO-SEAT (PROCESS SE
- Page 124 and 125: 104 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 126 and 127: 106 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 128 and 129: 108 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 130 and 131: 110 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 132 and 133: 112 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 134 and 135: 114 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 136 and 137: 116 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 138 and 139: 118 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 140 and 141: 120 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 142 and 143: 122 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 144 and 145: 124 CHAPTER 7. EXEMPLAR STUDIES AND
- Page 146 and 147: 126 CHAPTER 7. EXEMPLAR STUDIES AND
4.7. A SIMPLE EXAMPLE OF PROCESS SEMANTIC ANNOTATION 79<br />
Figure 4.6: EEML process model example: purchase process<br />
following the mapping rules <strong>for</strong> meta-model annotation. For example, the EEML Task<br />
is one-to-one mapped to the GPO Activity. Based on the meta model annotation, the<br />
GPO concepts will take the place <strong>of</strong> the corresponding process modeling constructs to<br />
describe the process. A domain ontology is employed to annotate the model contents<br />
which are described in the process annotation model. For instance, the EEML task<br />
"purchases" is a GPO activity, and this activity is annotated as a kind <strong>of</strong> domain ontology<br />
concept "buy" in the PSAM model. Figure 4.7 illustrates the annotation results <strong>of</strong><br />
the purchase model.<br />
We exemplify parts <strong>of</strong> the PSAM instance <strong>of</strong> annotation results which are represented<br />
in OWL. The example here is only a demo <strong>of</strong> the OWL representation. In the<br />
demo the data type <strong>of</strong> model_fragment is defaulted as URI and the data types <strong>of</strong> other<br />
properties are not specified, which can be compared with the PSAM instances in OWL<br />
from exemplars in Appendix H 2 .<br />
<br />
<br />
purchases<br />
Purchase<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
2 The exemplars are introduced in Chapter 7.
Change language