Properties defined in the Abstract classes cannot contain instances but, thanks to
the class-subclass the relationship property will be inherited by subclasses until the
subclasses will be concrete.
At this point the main concepts of BPMN are represented as ontological classes.
In order to link together the main concepts we define the Object Property in the
proper classes.
The use of Object Property in the BPMN ontology is a little different from the
traditional Semantic Web. An example is useful in understanding this interesting
aspect. Each process may be composed by different GenericBusinessProcessObject,
and it is not a must to define in each process all the GenericBusinessProcessObject
defined in the BPMN specification. If each GenericBusinessProcessObject is
defined only by its name a solution may be to define in the class Process several
properties (datatype properties) each of one of the generic business process. The
generic business process is a more complicated concept: It has several subclasses
and each of them has its own properties. To solve this problem in the metamodel that
we developed, we adopt an Object Property ???hasGenericBusinessProcessObject,???
which has the class Process as domain and the class GenericBusinessProcessObject
as range.
Pages:
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232