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

148 CHAPTER 9. VALIDATION OF APPLICABILITY
Table 9.2: SWRL queries and rules for RE2
RE2 Rule Name SWRL formulation
QRule-Activity-sameas Activity(?x) ∧ same_as(?x, ?y) → query : select?x, ?y ∧ query :
RE2.1
orderBy(?y)
QRule-Activity-kindof Activity(?x) ∧ kind_o f(?x, ?y) → query : select(?x, ?y) ∧ query :
orderBy(?x)
QRule-Activity-phaseof Activity(?x) ∧ phase_o f(?x, ?y) → qurey : select(?x, ?y) ∧ query :
orderBy(?x)
QRule-Activity-Inputmappedto
Activity(?x) ∧ has_ Input(?x, ?y) ∧ mapped_to(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
RE2.2 QRule-Activity-Outputmappedto
Activity(?x) ∧ has_Output(?x, ?y) ∧ mapped_to(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasArtifact-sameas
Activity(?x) ∧ has_ Artif act(?x, ?y) ∧ same_as(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasArtifact-kindof
Activity(?x) ∧ has_ Arti f act(?x, ?y) ∧ kind_o f(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasArtifact-partof
Activity(?x) ∧ has_Arti f act(?x, ?y) ∧ part_o f(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasActor-sameas
Activity(?x) ∧ has_ Actor − role(?x, ?y) ∧ same_as(?y, ?z) → query :
RE2.3
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasActor-kindof
Activity(?x) ∧ has_ Actor − role(?x, ?y) ∧ kind_o f(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
QRule-ActivityhasActor-memberof
Activity(?x) ∧ has_Actor − role(?x, ?y) ∧ member_o f(?y, ?z) → query :
select(?x, ?y, ?z) ∧ query : orderBy(?z)
RE2.4
QRule-ActivityachievesHardGoal
orderBy(?y)
Activity(?x) ∧ achieves(?x, ?y) → query : select(?x, ?y) ∧ query :
QRule-ActivitypositivelysatisfiesSoftGoal
Activity(?x) ∧ positively_satis f ies(?x, ?y) → query : select(?x, ?y) ∧
query : orderBy(?y)
QRule-ActivitynegativelysatisfiesSoftGoal
Activity(?x) ∧ negatively_satis f ies(?x, ?y) → query : select(?x, ?y) ∧
query :
orderBy(?y)
Activity-subActivity-hasArtifact and IRule-Activity-subActivity-hasActor
are used to introduce the implicit annotation of has_Artifact and has_hasActor-role
for the super-Activity. The effects of goals from the sub-Activities could be transferred
to the super-Activities but it is not necessary for all cases. RE3.5 is therefore formalized
as SWRL queries not inference rules by only listing the possible goal annotations
transferred from the sub-Activities.
RE3.6 (Check the Precondition/Postcondition of Activities) is formalized
into QRule-Activity-hassamePrecondition and QRule-ActivityhassamePostcondition.
It attempts to find out the redundant Activities with
the same conditions or the workflow patterns with the branches divided from the
conditions. Besides, for RE3.7 (Check the information flow from the Output to the
Input) the information flow (/output-input flow) can be identified through comparing
the annotated Input and Output in QRule-Activity-hasOuput-mappedtosameonto-Activity-hasInput.
If an output has an ontology reference which is also
referenced by an input, there might be an information flow between the output and
the input.
9.2.4 Formalizing RE4 - Knowledge discovery requirements
RE4 is related to G4 (The annotation should be helpful in the semantic reconciliation of
models to facilitate reuse and integration of models.). This requirement is for analyzing
the potential semantic relations between different models. However, SWRL rules can
only be applied in one ontology file, such as the SWRL formulations of RE1, RE2 and