<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Re ning Semantically Annotated Business Process Diagrams</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Hector G. Ceballos</institution>
          ,
          <addr-line>Eduardo Fernandez, Jorge Espinosa</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Tecnologico de Monterrey Av. Eugenio Garza Sada 2501 Monterrey</institution>
          ,
          <addr-line>N.L.</addr-line>
          ,
          <country country="MX">Mexico</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Business Process Diagrams (BPDs) provide a rich graphical expressiveness for modeling not only business processes but also the development of collective human activities. In Multiagent platforms, BPDs has been used for decoupling the modeling of agent behavior from its implementation. Additionally, the annotation of BPD actions and events with conjunctive queries has opened the door for monitoring process development by querying a knowledge base. We study the properties of this annotation scheme for the re nement of activity diagrams through the removal of redundant nodes, the detection of disjoint alternative paths and the merge/split of event nodes.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process Diagrams</kwd>
        <kwd>Semantic Annotation</kwd>
        <kwd>Description Logics</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        BPMN is a standard notation for modeling business processes widely adopted
by industry that provides a rich graphical representation that can be used for
common understanding of processes [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Furthermore, BPMN has been used for
process automation with support of agent technologies given its direct
correspondence with some MAS architectures [
        <xref ref-type="bibr" rid="ref11 ref9">11, 9</xref>
        ]. In these approaches the speci cation
of agent behavior is decoupled from the implementation of agent actions
(denoted as task nodes). BPMN BPDs has been also used for modeling collective
human activities, observable through the e ects of human actions [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        On the other hand, the use of conjunctive queries has been previously
proposed for describing the meaning of events and actions [
        <xref ref-type="bibr" rid="ref3 ref6">6, 3</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], actions are
described by their direct e ects and these annotations are used for determining
the status of a process instance. In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], each possible outcome of a random
variable representing an event or an action is annotated with a conjunctive query in
order to enable process monitoring.
      </p>
      <p>
        Muehlen and Indulska performed a representational analysis of modeling
languages for business processes and business rules, nding that the most complete
combination is BPMN and SWRL [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Rules in the Semantic Web Rule
Language (SWRL) are constituted by conjunctive queries [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>This paper is organized as follows. We introduce basic notions of BPMN
Business Process Diagrams and Conjunctive Queries in section 2. Then, in section 3
we introduce semantic descriptors on a BPD normal form, describe the
properties provided by the use of conjunctive queries and show how these properties
can be used for re ning a BPD by detecting disjoint alternative paths,
deleting redundant nodes, and merging/splitting nodes. We conclude with closing
remarks and future work in section 4.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <p>Next we introduce the formal notions used for introducing conjunctive queries
as semantic descriptors on top of BPMN BPDs.
2.1</p>
      <sec id="sec-2-1">
        <title>Business Process Diagrams</title>
        <p>Business Process Modeling and Notation (BPMN) provides a formal
representation of Business Process Diagrams (BPDs), which basically describe a process
in terms of events and tasks connected through control ows that indicate valid
sequences in the process development. Gateways are special nodes connected
through control ows that indicate whether the process develops in parallel
(AND), alternatively (XOR) or optionally (OR). The beginning of the process is
denoted by an initial event node and its conclusion by a set of end event nodes.</p>
        <p>
          Figure 1 shows a subset of the graphical notation of the BPMN 2.0 speci
cation [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. These graphical elements are used in approaches for software
engineering [
          <xref ref-type="bibr" rid="ref14 ref4">14, 4</xref>
          ] and for modeling human activities [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] through BPDs.
        </p>
        <p>
          Industry has adopted XML le formats for authoring and exchanging BPDs
such as XML Process De nition Language (XPDL)[
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] and BPMN 2.0[
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. In
them, nodes representing tasks, events, gateways and control ows are
represented through unique identi ers along with properties and relationships with
other nodes.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>DL Conjunctive Queries</title>
        <p>
          We use the notation and properties of conjunctive queries given by Description
Logics (DL) [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], which states that the interpretation of a query is not only
given by statements speci ed in the query, but by constraints and de nitions
speci ed in the domain model (T ) as well. This model, known as ontology, is
basically constituted by a set of concepts (used to group/classify objects) and
relations (used to specify entity's attributes or used to relate entities among
them). Ontology languages such as OWL1 allows expressing concepts in terms
of other concepts (de nitions), and specifying constraints between concepts (e.g.
disjointness or subsumption) and properties (e.g. re exivity or transitivity).
        </p>
        <p>A DL conjunctive query (CQ) has the form:</p>
        <p>Q = (s1; :::sn):fT1; :::; Tmg
where si is the set of distinguished variables, denoted Dis(Q), that de ne the
resulting binding sets (the information retrieved), and Ti is a nite set of
either concept clauses (s rdf:type C) or relation clauses (s r s'), where s; s0 2
(NV [ NC ), C is a concept/class and r is a relation/property both de ned in T ,
NV is a nite set of variables denoted V ar(Q), and NC is a nite set of constants.</p>
        <p>
          In SPARQL, the query language for RDF[
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], a conjunctive query is coded as a
SELECT query without lters. Distinguished variables (Dis(Q)) of a conjunctive
query Q are listed in the section SELECT, whereas atoms Ti are speci ed in the
section WHERE as statements or subject-predicate-object triplets.
        </p>
        <p>
          Query containment between conjunctive queries can be decided
automatically observing the constraints and de nitions given in T , as proposed by [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. A
query Q1 is contained in a query Q2 with respect to T (written T j= Q1 v Q2),
if and only if, for every model I of T , Q1(I) v Q2(I). In other words, Q1 v Q2
and K j= Q1 implies that K j= Q2 also, i.e. the answer to Q1 will be included in
the answer to Q2. By de nition, every well-formed query Q is subsumed by &gt;,
i.e. T j= Q v &gt;.
        </p>
        <p>Queries Q1 and Q2 are equivalent if Q1 v Q2 and Q2 v Q1, denoted Q1 Q2.
Q1 and Q2 are considered disjoint if K becomes inconsistent whenever K j=
Q1 u Q2 for any replacement of common variables in both queries, also denoted
by Q1 u Q2 v ?. By de nition, if Q1 v Q2 then Q1 and Q2 are not disjoint.</p>
        <p>Merge of two queries Q1 and Q2 is given by its intersection and it is denoted
by Q1 u Q2, whereas the opposite operation is called split.
1 OWL Web Ontology Language. https://www.w3.org/TR/owl-features/</p>
        <p>Semantic Description of Business Process Diagrams
Now we introduce semantic descriptors for describing the meaning of lanes,
actions and events, provide some basic properties for annotated nodes and show
how these can be used for re ning a BPD.
3.1</p>
      </sec>
      <sec id="sec-2-3">
        <title>Semantic Descriptors</title>
        <p>
          In this paper we use the formalization of BPDs and the normal form proposed
in [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. In this approach, the BPD has the purpose of illustrating alternative
sequences of human actions performed by activity participants, mediated by
intermediate events that the subject or other participants can observe. XOR
gateways are used for representing disjoint alternatives. Activity development has
a triggering condition (initial event) and a set of successful or failure outcomes
(end events).
        </p>
        <p>A Business Process Diagram W is represented by a set of pools (P), lanes
(L), nodes (N) and control ows (F). Nodes (N) allowed in the diagram are: start
events (N S ), intermediate events (N I ), end events (N E ), human tasks (N A) and
gateways (N G). A gateway g 2 N G can be of type Parallel-AND (A),
OptionalOR (O), or Exclusive-XOR (X), denoted respectively type(g; fA; O; Xg).
Unconditional sequence ows are denoted as F (ni; nj ) 2 F, ni ! nj for short, where
ni; nj 2 N . All nodes n 2 N are situated in a lane l 2 L, denoted in(n; l).</p>
        <p>W = fP; L; N; Fg</p>
        <p>N = N S [ N I [ N E [ N A [ N G</p>
      </sec>
      <sec id="sec-2-4">
        <title>De nition 1 (Semantic Descriptor). A semantic descriptor Ann(n; Q) uses</title>
        <p>the conjunctive query Q for representing the meaning of a lane, an observable
event, or human task n 2 (L [ N S [ N I [ N E [ N A) in a BPD W.</p>
        <p>A lane descriptor describes the kind of individual that play a role in the
activity. It has the form Ann(l; Ql), where l 2 L and Ql might represent an absolute or
relative role. An absolute role annotation is given by a Ql = (?role):f?role a RoleClassg
where RoleClass indicates the type of individual, denoted by ?role, associated
to l. A relative role annotation is given by a Ql = (?role):f?role rel ?role2g
where the role associated to the lane (?role) is de ned in terms of its
relationship (rel) with a participant represented by another lane (?role2).</p>
        <p>An event descriptor has the form Ann(z; Qz), where z 2 (N S [ N I [ N E )
and Qz is a conjunctive query describing a condition (constraints between
individuals) that denotes the occurrence of the event.</p>
        <p>A task descriptor has the form Ann(x; Qx), where x 2 N A,</p>
        <p>Qx = (?act):f?act a T askClass : ?act doneBy ?role :</p>
        <p>
          ?act propi ?valueig;
TaskClass indicates the type of task performed or initiated by ?role, and the
task description is expressed by statements such as ?act propi ?valuei. According
to Activity Theory[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], task description might include the participation of other
agents playing a role in the activity, the use of artifacts and the location where
the task occurs. The distinguished variable ?act denotes the task execution (the
action in act).
        </p>
        <p>De nition 2 (Annotated BPD). An annotated BPD WD is a BPD W where
each node n 2 (L [ N S [ N I [ N E [ N A) is annotated with exactly one semantic
descriptor Ann(n; Q) 2 D.
3.2</p>
      </sec>
      <sec id="sec-2-5">
        <title>Properties of Annotated BPDs</title>
        <p>The use of semantic descriptors allows to verify automatically if the meaning of
a BPD node is equivalent to, disjoint with, or subsumed by another BPD node.</p>
      </sec>
      <sec id="sec-2-6">
        <title>De nition 3 (Node Disjointness). The BPD node n1 is disjoint with the</title>
        <p>BPD node n2, denoted n1?n2, if and only if Q1 u Q2 v ? with respect to (w.r.t.)
T , given Ann(n1; Q1) and Ann(n2; Q2).</p>
      </sec>
      <sec id="sec-2-7">
        <title>De nition 4 (Node Subsumption). The BPD node n1 is subsumed by the</title>
        <p>BPD node n2, denoted n1 v n2, if Q1 v Q2 and Q2 6v Q1 w.r.t. T , given
Ann(n1; Q1) and Ann(n2; Q2).</p>
      </sec>
      <sec id="sec-2-8">
        <title>De nition 5 (Node Equivalence). The BPD node n1 is equivalent to the</title>
        <p>BPD node n2, denoted n1 n2, if and only if Q1 Q2 w.r.t. T , given Ann(n1; Q1)
and Ann(n2; Q2).</p>
        <p>These de nitions can be used for detecting redundant nodes, i.e. consecutive
event nodes annotated with equivalent descriptions.</p>
        <p>Theorem 1 (Node Redundancy). Given two consecutive event nodes z1; z2 2
(N S [ N I [ N E), z1 ! z2, such that z2 v z1, z2 will hold whenever z1 holds,
making z2 redundant in the diagram.</p>
        <p>Proof. During process monitoring, the occurrence of the event z2 will be
evaluated right after z1. z2 being subsumed by z1 means that z2 will hold whenever
z1 holds, hence checking the occurrence of z2 becomes unnecessary once z1 has
occurred.</p>
        <p>In the example of Figure 2, the event z7:2 is redundant as long as z7:2 v z5:1,
making unnecessary the observation of z7:2. The following corollary complements
Theorem 1.</p>
        <p>Corollary 1. Given two consecutive event nodes z1; z2 2 (N S [ N I [ N E),
z1 ! z2, such that z2 z1, either z1 or z2 becomes redundant.</p>
        <p>Proof. Given that z1 will hold whenever z2 does and vice versa, either of the
two can be chosen as redundant node.</p>
        <p>Two other properties apply to event nodes preceded by the same gateway.
Two BPD events zi and zj are called siblings, denoted as zijjzj , if both of them
are directly preceded by a gateway g 2 N G, i.e. zi g ! zj .</p>
        <p>Determining that all sibling events following to a gateway g are disjoint
indicates that g must be XOR-Exclusive. Figure 3 shows two alternative scenarios
as result of a medical consultation, denoted by two sibling events, z4:2 and z4:3,
with their corresponding descriptors. Ann(z4:2) and Ann(z4:3) are disjoint as
long as the cardinality of the boolean role followUp is constrained to a single
value in the concept Prescription, stated in T as:</p>
        <p>Prescription v</p>
        <p>1 followUp</p>
        <sec id="sec-2-8-1">
          <title>Theorem 2 (Disjoint sibling events). If every pair of sibling events zijjzj</title>
          <p>immediately preceded by a splitting gateway g 2 N G are disjoint to each other
(zi?zj ), then g must be an event-driven exclusive (XOR) gateway, i.e. type(g; X).
Proof. Once g is reached, process development will continue through g if and
only if some event zi occur after g. Being disjoint every pair of sibling events, only
one of them can occur at a given time, hence the rst that occur will continue
process' monitoring, which is the de nition of an event-driven exclusive (XOR)
gateway. In contrast, g cannot be parallel (AND) as long as once that zi holds
the condition represented by any of its sibling will not hold anymore. For the
same reason g cannot be optional (OR), i.e. more than one sibling cannot hold.</p>
          <p>On the contrary, overlaps between sibling events following to an exclusive
gateway violates process development rules.</p>
        </sec>
        <sec id="sec-2-8-2">
          <title>Theorem 3 (XOR-Equiv overlap). A pair of sibling events zijjzj immedi</title>
          <p>ately preceded by a splitting Exclusive-XOR gateway g 2 N G such that zi zj ,
will provoke a violation of process monitoring after g.</p>
          <p>Proof. Once g is reached, process development must continue through one and
only one path given by the sibling event holding next. zi zj means that both
events will hold, violating the rule imposed by the XOR gateway.
Theorem 4. A pair of sibling events zijjzj immediately preceded by a splitting
Exclusive-XOR gateway g 2 N G such that zi v zj , can potentially provoke a
violation of process monitoring after g.</p>
          <p>Proof. Observing zj means that zi will hold as well, enabling process
development through both branches which constitutes a violation of the splitting XOR
gateway rule. Nevertheless, observing zi does not assure that zj will hold as well,
in which case the violation would not occur.</p>
          <p>Semantic description of sibling events following XOR gateways have similar
or complementary descriptions as long as they represent alternative scenarios.
In these cases, annotations of sibling events have a common sub-expression that
can be captured before the splitting gateway.</p>
        </sec>
      </sec>
      <sec id="sec-2-9">
        <title>De nition 6 (Common Precondition). The conjunctive query Qg is consid</title>
        <p>ered a common precondition for all sibling events zi preceded by g if and only if
Qi Qg u Q0i for every Ann(zi; Qi) 2 D.</p>
        <p>Given that the normal form does not allow to annotate gateways, the common
precondition must be represented through the introduction of an intermediate
event preceding the gateway.</p>
        <p>Theorem 5. The observation of a precondition Qg, included in a set of disjoint
sibling events zi following to the gateway g, can be represented through the
introduction of an event node zg such that: np ! g is replaced by np ! zg ! g,
and D = D [ Ann(zg; Qg) n Ann(zi; Qi) [ Ann(zi; Q0i).</p>
        <p>Proof. Process monitoring requires observing zg before reaching g, and then
evaluating every zi. Assuming world state does not change between the
observation of zg and the observation of zi, the observation of Q0i simultaneously to
Qg is by de nition equivalent to observing Qi.</p>
        <p>In both alternatives shown in Figure 3 the doctor prescribes medication, but
in z4:3 the patient requires follow up whereas in z4:2 he does not. Figure 4 shows
an equivalent representation where the event z4:2 3 represents the common
condition, and original events are replaced by the necessity of a follow up appointment
(z4:3B) or not (z4:2B).</p>
        <p>Properties provided by semantic descriptors also permits to validate if the
work ow can be monitored properly. For instance, Theorem 2 provides a rule
for checking the correspondence between XOR gateways and disjoint events.</p>
        <p>Descriptors of nodes in the structure shown in Figure 4 must be also checked
to prevent monitoring issues. For instance, if doctor's prescription (evaluated
as common precondition) indicates both more medication and a follow-up
appointment, and one of the exclusive alternative paths check for more medication
whereas the other asks for the follow-up appointment, then monitoring could
continue through both paths, but the XOR gateway forces to continue for only
one (chosen arbitrarily).</p>
        <p>Theorem 6. A common precondition zg subsuming at least two alternative events
zi immediately following a XOR gateway g, i.e. zi v zg, will provoke a violation
of process monitoring after g.</p>
        <p>Proof. Assuming that all sibling events zi are evaluated immediately after the
precondition zg, once that zg holds any zi will hold as well. Process monitoring
will follow through the branch of the rst zi evaluated, despite another branch
could be followed (the one indicated by the other zi v zg).</p>
        <p>In the same circumstances but having a Parallel-AND gateway, the
precondition becomes redundant.</p>
        <p>Theorem 7. A common precondition zg is redundant in the diagram if it
subsumes all alternative events zi immediately following a Parallel-AND gateway g,
i.e. zg ! g ! zi and zi v zg.</p>
        <p>Proof. Given that process monitoring continues through all branches of a
splitting Parallel-AND gateway, the evaluation of zg before every zi is unnecessary
as long as zi will necessarily hold once that zg holds.</p>
      </sec>
      <sec id="sec-2-10">
        <title>Re ning and Validating Annotated BPDs</title>
        <p>Theorems 1 and 7, and corollary 1 are used for simplifying the BPD by absorbing
redundant nodes. Theorem 5 is used for introducing common preconditions.
Theorem 2 is used for signaling disjoint alternatives. Finally, theorems 3, 4 and
6 are used for warning about errors on process monitoring.</p>
        <p>The following procedure can be used for validating and automatically re ning
the annotated BPD WD:
1. Identify consecutive events z1 ! z2 such that z1; z2 2 (N I [ N E ),
(a) if z1 v z2 then absorb z2.</p>
        <p>i. if z2 2 N E then N I = N I n z1 and N E = N E [ z1.</p>
        <p>(b) if z1 z2 then absorb z1.
2. For each splitting gateway g immediately followed by sibling events zijjzj ,
(a) If all pairs (zi; zj ) are disjoint (zi?zj ), then set type(g; XOR).
(b) If exists a common precondition Qg such that Qi Qg u Q0i for each
descriptor Ann(zi; Qi) of all sibling events zi, insert an event zg ! g,
D = D [ Ann(zg; Qg) n Ann(zi; Qi) [ Ann(zi; Q0i).
(c) If type(g; XOR) and zi zj , then warn: Monitoring violation after g.
(d) If type(g; XOR) and zi v zj , then warn: Potential monitoring violation
after g.
3. For each splitting gateway g preceded by an event zg and followed by two
or more sibling events zi,
(a) If type(g; AN D) and zi v zg for all zi, then absorb zg.
(b) If type(g; XOR) and zi v zg for at least two zi, then warn: Monitoring
violation after g.</p>
        <p>In this procedure, the absorption of a node ni means that all the arcs nj ! ni
must be replaced by arcs nj ! nk for each nk given by every arc ni ! nk in the
diagram. Then node ni as well as all its incoming and outgoing arcs are removed
from the diagram.</p>
        <p>Given that all re nement strategies are local, the complexity of the previous
procedure is bounded by the computation of query containment between
annotations of sibling event nodes. The identi cation of a common precondition for
a set of sibling events zi requires checking if exists a common subset of triplets
Q0i in every Qi.</p>
        <p>As long as query containment is not a standard reasoning service provided by
state-of-the-art triplestores or DL reasoners it would be necessary to develop a
tool that e ciently decide query containment among a set of CQs. Such a service
would decide Q1 v Q2 by transforming Q2's variables into symbols, asserting the
resulting statements in a graph and asking Q1 to it (using the desired reasoning
level).
4</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusions</title>
      <p>We introduced a taxonomy of semantic descriptors for annotating lanes, events
and tasks in BPMN BPDs. The proposed notation not only provides a formal
description of these elements but it can be also used for mapping the business
process speci cation to its implementation in an agent-based software.</p>
      <p>We demonstrated how using conjunctive queries as semantic descriptors can
help to detect relationships between BPMN BPD events. These relationships
are then used for re ning process speci cations by detecting disjoint alternative
paths, deleting redundant nodes, and merging/splitting nodes.</p>
      <p>We also illustrated why human actions should not only be represented through
their immediate e ects, but breaking them down helps Multiagent System.to
determine whether the activity takes place according to how it was modeled.</p>
      <p>Semantic descriptors can be further used for determining common events
or actions across diagrams, enabling the composition of BPDs. Diagram
composition would enable to introduce the execution of MAS protocols in human
activities, both modeled through BPDs. Semantic descriptors can be also
further used for monitoring process/activity development by inquiring a RDF triple
store representing world state.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvanese</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F</given-names>
          </string-name>
          . (eds.):
          <article-title>The Description Logic Handbook: Theory, Implementation, and Applications</article-title>
          . Cambridge University Press, New York, NY, USA (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ceballos</surname>
            ,
            <given-names>H.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Flores-Solorio</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia</surname>
            ,
            <given-names>J.P.:</given-names>
          </string-name>
          <article-title>A Probabilistic BPMN Normal Form to Model and Advise Human Activities</article-title>
          . In: Baldoni,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Baresi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Dastani</surname>
          </string-name>
          , M. (eds.) Engineering
          <string-name>
            <surname>Multi-Agent</surname>
            <given-names>Systems</given-names>
          </string-name>
          : Third International Workshop, EMAS 2015, Istanbul, Turkey. LNAI
          <volume>9318</volume>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Ceballos</surname>
            ,
            <given-names>H.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia-Vazquez</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brena</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Using activity theory and causal diagrams for designing multiagent systems that assist human activities</article-title>
          .
          <source>In: Proceedings of the 12th Mexican International Conference on Arti cial Intelligence</source>
          ,
          <string-name>
            <surname>MICAI</surname>
          </string-name>
          <year>2013</year>
          . pp.
          <volume>185</volume>
          {
          <fpage>198</fpage>
          .
          <string-name>
            <surname>Mexico City</surname>
          </string-name>
          (
          <year>Nov 2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Endert</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuster</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hirsch</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Albayrak</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Mapping BPMN to agents: An analysis</article-title>
          .
          <source>In: Agent</source>
          ,
          <string-name>
            <given-names>Web</given-names>
            <surname>Services</surname>
          </string-name>
          , and
          <string-name>
            <surname>Ontologies Integrated</surname>
          </string-name>
          Methodologies - International
          <string-name>
            <surname>Workshop</surname>
          </string-name>
          MALLOW-AWESOME
          <year>2007</year>
          . pp.
          <volume>43</volume>
          {
          <issue>58</issue>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. group, W.S.W.:
          <article-title>SPARQL 1.1 Overview (</article-title>
          <year>2013</year>
          ), http://www.w3.org/TR/ sparql11-overview/
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Hinge</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosey</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koliadisz</surname>
          </string-name>
          , G.:
          <article-title>Process seer: A tool for semantic e ect annotation of business process models</article-title>
          .
          <source>In: Proceedings of 13th IEEE International Enterprise Distributed Object Computing Conference</source>
          ,
          <string-name>
            <surname>EDOC</surname>
          </string-name>
          <year>2009</year>
          . pp.
          <volume>54</volume>
          {
          <issue>63</issue>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tabet</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grosof</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>SWRL: A semantic web rule language combining OWL and RuleML</article-title>
          .
          <source>W3C Member Submission 21 May 2004</source>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sattler</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tessaris</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tobies</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>How to decide query containment under constraints using a description logic</article-title>
          .
          <source>In: Logic for Programming and Automated Reasoning</source>
          , 7th International Conference, LPAR 2000,
          <string-name>
            <surname>Reunion</surname>
            <given-names>Island</given-names>
          </string-name>
          , France,
          <source>November 11-12</source>
          ,
          <year>2000</year>
          , Proceedings. pp.
          <volume>326</volume>
          {
          <issue>343</issue>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kuster</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lutzenberger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Albayrak</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A Formal Description of a Mapping from Business Processes to Agents</article-title>
          . In: Baldoni,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Baresi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Dastani</surname>
          </string-name>
          , M. (eds.) Engineering
          <string-name>
            <surname>Multi-Agent</surname>
            <given-names>Systems</given-names>
          </string-name>
          : Third International Workshop, EMAS 2015, Istanbul, Turkey. LNAI
          <volume>9318</volume>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Leont</surname>
          </string-name>
          <article-title>'ev, A.: Activity, Consciousness, and Personality</article-title>
          . Prentice-Hall, Inc. (
          <year>1978</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Mitakides</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delias</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spanoudakis</surname>
          </string-name>
          , N.:
          <article-title>Validating Requirements Using Gaia Analysis Models</article-title>
          . In: Baldoni,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Baresi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Dastani</surname>
          </string-name>
          , M. (eds.) Engineering MultiAgent Systems: Third International Workshop, EMAS 2015, Istanbul, Turkey. LNAI
          <volume>9318</volume>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. zur Muehlen,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Indulska</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Modeling languages for business processes and business rules: A representational analysis</article-title>
          .
          <source>Information Systems</source>
          <volume>35</volume>
          (
          <issue>4</issue>
          ),
          <volume>379</volume>
          {
          <fpage>390</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. OMG:
          <article-title>Business Process Model and Notation (BPMN), Version 2</article-title>
          .0 (
          <year>January 2011</year>
          ), http://www.omg.org/spec/BPMN/2.0
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Ouyang</surname>
          </string-name>
          , C.,
          <string-name>
            <surname>van der Aalst</surname>
          </string-name>
          , W.,
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hofstede</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Translating BPMN to BPEL</article-title>
          .
          <source>BPM Center Report BPM-06-02</source>
          , BPMcenter.org (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Shapiro</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gagne</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <string-name>
            <surname>XML Process De nition Language</surname>
          </string-name>
          (XPDL).
          <source>Tech. Rep. WFMC-TC-025, Work ow Management Coallition (8</source>
          <year>2012</year>
          ), http://www.omg. org/spec/BPMN/2.0/
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>