<!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>An ASP-Based Framework for Solving Problems Related to Declarative Process Specifications</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Isabelle Kuhlmann</string-name>
          <email>isabelle.kuhlmann@fernuni-hagen.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carl Corea</string-name>
          <email>ccorea@uni-koblenz.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>John Grant</string-name>
          <email>grant@cs.umd.edu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Artificial Intelligence Group, University of Hagen</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institute for IS Research, University of Koblenz</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Maryland, College Park</institution>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <fpage>129</fpage>
      <lpage>132</lpage>
      <abstract>
        <p>We present a framework of answer set programming-based solutions for various problems related to declarative process specifications. Specifically, the framework ofers implementations for conformance checking, satisfiability checking, and two diferent inconsistency measures. Since the aforementioned problems are represented in a fragment of linear temporal logic, the framework could also prove useful for a broader range of applications beyond process specifications.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;answer set programming</kwd>
        <kwd>declarative process specifications</kwd>
        <kwd>conformance checking</kwd>
        <kwd>satisfiability checking</kwd>
        <kwd>inconsistency measurement</kwd>
        <kwd>linear temporal logic</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        uct is empty) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Also, our framework is the first to
ofer practical solutions for the actual measurement of
Declarative process specifications are a crucial concept inconsistency in such specifications.
for modeling business processes. Such specifications can In summary, we present a framework based on answer
be expressed by means of linear temporal logic (LTL) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], set programming (ASP) featuring the following qualities:
i.e., a specification can be formulated as a set of LTL
formulas. The intuition behind this is that a business 1. It combines implementations for diferent
probprocess is a (temporal) sequence of actions. Problems lems in the area of declarative process
specificain this area include conformance checking (does a given tions, in particular conformance checking,
satisfisequence of actions conform to a specification?), satisfia- ability checking, and inconsistency measurement
bility checking (is a given specification free of conflicts?), (w.r.t. two distinct inconsistency measures).
as well as inconsistency measurement (if a specification 2. The encodings are based on LTL directly,
meancontains conflicts, how severe are they?) [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. ing no preprocessing, such as the transformation
      </p>
      <p>
        For conformance checking, existing algorithmic ap- to automata [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], is required. It is suficient to
proproaches (see [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] for an overview) are often geared to- vide a set of LTL formulas (and, for conformance
wards a specific modeling language, such as Declare, checking, a set of sequences of actions).
which means that it might not be possible to use them for 3. Since our implementations work directly on LTL
arbitrary LTL formulas. Also, many existing approaches formulas, they can be used in other fields as well.
(also some based on answer set programming [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]) rep- 4. Due to the declarative nature of ASP our
frameresent specifications with finite state automata. As this work delivers interpretable solutions. E.g., in the
transformation and related automata operations may in- case of inconsistency measurement, we can
identroduce a computational burden, in this work, our pre- tify which parts of a set of formulas representing
sented framework encodes the LTL semantics in a native a specification are involved in a conflict.
manner, such that no transformation is needed. We present some preliminaries on LTL and ASP in
      </p>
      <p>Regarding the analysis of inconsistency in declarative Section 2 and present an overview of our framework in
specifications, virtually all existing approaches also rely Section 3.
on the mentioned automata representation (and verify
inconsistency by checking whether the automata
prod</p>
    </sec>
    <sec id="sec-2">
      <title>2. Preliminaries</title>
      <sec id="sec-2-1">
        <title>In the following, we define the specific variant of LTL our work is based on, as well as the problems we address in our framework, and provide a basic overview of ASP.</title>
        <p>
          sequence of temporal states. In this work we consider
CC is actually closer to the definition of the problem of
sequences of finite [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] and fixed length, and refer to the
corresponding fragment of LTL as linear temporal logic
on fixed traces (LTLf ) [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Formulas are closed under the
unary operator X (next) and the binary operator U (until),
in addition to the classical operators ∧ (conjunction), ∨
model checking), and SCLTLf , respectively.
        </p>
        <p>
          In inconsistency measurement (IM) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], the goal is to
quantitatively assess the level of inconsistency in a given
knowledge base. Hence, we aim to map a given
specification  to a numerical value. Although applied in various
(disjunction), and ¬ (negation). We also consider the aux- other domains, it is a relatively new concept in the area of
iliary operators F (eventually) and G (globally), with F
being defined as
⊤U , and G being defined as
        </p>
        <p>¬F¬ .</p>
      </sec>
      <sec id="sec-2-2">
        <title>An LTLf -interpretation ˆ w.r.t. At is a function map</title>
        <p>
          declarative process specifications. In [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], the authors first
introduced two inconsistency measures for LTLf based
on paraconsistent semantics, which are implemented in
ping each state  and proposition  to 1 (true) or 0 (false), the framework.
        </p>
        <p>Problems Related to Declarative Process Specifica- constraint, and if () = ∅,  is called a fact. We further
i.e., ˆ(, ) = 1 if  is assigned 1 at . A formula 
is satisfied</p>
        <p>by an interpretation ˆ, denoted ˆ |=  , if
ˆ, 0 |=  . Further, ˆ,  |=  is inductively defined as
ˆ,  |=  if ˆ(, ) = 1 for  ∈ At
ˆ,  |= ¬ if ˆ,  ̸|= 
ˆ,  |=  1 ∧  2 if ˆ,  |=  1 and ˆ,  |=  2
ˆ,  |=  1 ∨  2 if ˆ,  |=  1 or ˆ,  |=  2
ˆ,  |= X if  &lt;  and ˆ, +1 |= 
ˆ,  |=  1U 2 if ˆ,  |=  2 with  ∈ { + 1, . . . , }
and ˆ,  |=  1 ∀ ∈ {, . . . ,  − 1</p>
        <p>}
interpretation ˆ satisfies a set of formulas
w.r.t. any interpretation ˆ, and  ∈ {0, . . . , }. An
 if
∀</p>
        <p>∈
 : ˆ |=  . We also refer to a satisfiable set of formulas
as consistent, and to an unsatisfiable set of formulas as
inconsistent.
tions</p>
        <p>Conformance checking (CC) is the task of deciding
whether a given trace  = ⟨0, . . . , ⟩, consisting of
a sequence of activities or actions, conforms to a given
specification</p>
        <p>
          . Note that, following the literature in
business process modeling, only the atom indicated by
 ( ∈ {0, . . . , }) is set to 1 in state , while all other
atoms are set to 0 in  [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. We denote the resulting
interpretation as ˆ. Thus, formally, we check whether
ˆ |= . In addition, we allow individual formulas  to
be vacuously satisfied if none of the atoms occurring in
 are contained in .
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>As a generalization of CC, we define the problem of</title>
        <p>formulas can be vacuously satisfied.
satisfiability checking (SC) as the task of deciding whether
there exists a trace  of length , and a corresponding
interpretation ˆ, s.t. ˆ |= , for a given specification
. Again, only atom  is set to true in state , and</p>
      </sec>
      <sec id="sec-2-4">
        <title>To allow for our framework to be used beyond declar</title>
        <p>ative process specifications, we additionally provide
implementations for the “general” problems of CC and SC
in LTLf . To be precise, we lift the restriction that only
atom  is allowed to be true in state , and we prohibit
formulas to be vacuously satisfied. We denote the
correAnswer Set Programming</p>
      </sec>
      <sec id="sec-2-5">
        <title>Answer set program</title>
        <p>
          ming (ASP) [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] is a declarative programming paradigm,
where the objective is to represent a given problem
in a logical format (an extended logic program) s.t.
the models of this representation (the answer sets)
express solutions of the initial problem.
        </p>
        <p>An
extended logic program is comprised of rules of the form
“ = 0:- 1, . . . , , not +1, . . . , not .” with
 (0 ≤
 ≤
 ≤</p>
        <p>
          ) being atoms, and “not”
indicating default negation [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. An atom is a predicate
(1, . . . , ) with  ≥
either a constant or a variable1. Further, “:-” can be
interpreted as “if”, a “,” as “and”, and a “.” marks the end
of a rule. If an atom/rule/program does not contain any
0, with each 1, . . . ,  being
variables, it is referred to as ground.
        </p>
        <p>
          An ASP rule  (as illustrated above) is comprised of
a head () = 0 and a body () = {1, . . . , ,
not +1, . . . , not }. If () is empty,  is called a
 is called an answer set of  .
+() ⊆
divide the elements of () into +() = {1, . . . , }
and − () = {+1, . . . , }. A set  of ground
atoms is a model of a ground logic program  if for
all  ∈  , () ∈  whenever − () ∩  = ∅ and
. The reduct [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] of a program  w.r.t. 
is defined as   = {():- +() | − () ∩  =
∅,  ∈  }. If  is a subset-minimal model of   , then
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Framework</title>
      <p>
        The framework2 we present combines ASP-based
implementations of all problems defined in the preceding
section (namely, CC, MC, SC, SCLTLf , and IM w.r.t. the
two measures defined in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]). The implementations are
done in C++, and the ASP solver we use is Clingo [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        Note that the implementations for CC and SC have been
introduced in a recent work by the authors [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], and
1Following the Clingo [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] syntax, we denote constants by strings
starting with a lowercase letter, and variables by strings starting
with an uppercase letter. Anonymous variables (which do not recur
within a rule) are denoted by “_”.
sponding problems as MC (since the “general” variant of 2https://github.com/aig-hagen/ASP_for_LTL
the implementations for the two inconsistency measures The approach described above can directly be used
have been proposed in a work that is currently under to solve MC as well3—the framework simply requires a
review [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. diferent input format which specifies a set of atoms to be
      </p>
      <p>
        Since due to page limitations, we cannot explain the true per state (instead of a single atom). Furthermore, the
ASP encodings for each problem in detail, we take CC approach can be easily modified to solve SC and SCLTLf .
as an example to demonstrate our overall approach. Our Intuitively, for SCLTLf we merely need to add a rule that
framework takes as input for CC (i) a file containing a “guesses” an interpretation which is then checked to be
specification  (i.e., a set of LTL formulas), and (ii) a file satisfiable, and for SC we additionally need to handle
containing a set of traces . For each trace  ∈ , we vacuous satisfiability directly within ASP.
encode CC in ASP, and if an answer set can be derived, The ASP encodings for the two inconsistency
meathe given problem instance (, ) is satisfiable, otherwise sures from [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] are a bit more intricate, since we need to
it is unsatisfiable. model paraconsistent semantics. E.g., it is not suficient
      </p>
      <p>In order to encode a given problem instance (, ) in to model only the “true” case w.r.t. the diferent
operaASP, we begin by representing each atom  ∈ At() as a tors. Instead, we use truthValue(,  ,  ) to explicitly
fact “atom().”. In the same manner, each formula  ∈ represent a truth value  for a formula  in . However,
 is modeled as kbElement( ). Next, we represent the the overall approach is still the same—we directly model
“type” of each (sub-)formula; e.g., a conjunction  = logical entailment.
 1 ∧  2 is represented as conjunction(,  1,  2).</p>
      <p>The remaining operators (disjunction, negation, next,
until, eventually, and globally) are modeled analogously. 4. Conclusions and Future Work
If a formula  consists of a single atom , it is repre- We introduced a framework that provides ASP-based
sosented by formulaIsAtom(,  ). To represent a trace lutions for multiple problems related to LTL, targeted at
 in ASP, we first define || states, where the final state the field of declarative process specifications. Our
ap = || − 1 is represented as finalState(). The proach does not require any preprocessing (such as the
states {0, . . . , } are then modeled by adding the rule computation of automata), and can be used in other
LTL“state(0..M) :- finalState(M).” to the encoding. related domains as well. In terms of future work, we aim
Further, we model that  ( ∈ {0, . . . , }) is true in to extend our set of implementations, e.g., by
considerstate  by adding “true(, ).”. ing culpability measures (which indicate a level of blame</p>
      <p>An overview of our encoding of logical entailment is for the inconsistency of a knowledge base w.r.t. a given
given in Listing 1. Essentially, we can directly follow the formula or atom). Also, we aim to apply our framework
definition of each operator (see Section 2)—e.g., a formula to more non-monotonic settings, e.g., inconsistency
meaX is true in  if  &lt;  and  is true in +1 (line surement in the presence of superiority relations between
5). Moreover, lines 2–4 describe the classical operators, LTL formulas.
lines 6–8 the remaining LTL-specific ones, and line 1 the
case if a formula is in fact an atom. Finally, we add an
integrity constraint (line 9) which ensures that no answer References
set can be derived if any formula  ∈  evaluates to “not
true” in state 0, i.e., every formula must be satisfied.
3Note that in the case of CC, vacuously satisfied formulas are simply
not encoded in ASP; in the case of MC, every formula is encoded.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Pnueli</surname>
          </string-name>
          ,
          <article-title>The temporal logic of programs</article-title>
          ,
          <source>in: 18th Annual Symposium on Foundations of Computer Science</source>
          (sfcs
          <year>1977</year>
          ), IEEE,
          <year>1977</year>
          , pp.
          <fpage>46</fpage>
          -
          <lpage>57</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Carmona</surname>
          </string-name>
          ,
          <string-name>
            <surname>B. van Dongen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Weidlich</surname>
          </string-name>
          ,
          <article-title>Conformance checking: foundations, milestones and challenges</article-title>
          , in: Process Mining Handbook, Springer,
          <year>2022</year>
          , pp.
          <fpage>155</fpage>
          -
          <lpage>190</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>C.</given-names>
            <surname>Corea</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Grant</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Thimm</surname>
          </string-name>
          ,
          <article-title>Measuring inconsistency in declarative process specifications</article-title>
          ,
          <source>in: 20th International Conference on Business Process Management</source>
          , Springer,
          <year>2022</year>
          , pp.
          <fpage>289</fpage>
          -
          <lpage>306</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>S.</given-names>
            <surname>Dunzer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Stierle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Matzner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Baier</surname>
          </string-name>
          ,
          <article-title>Conformance checking: a state-of-the-art literature review</article-title>
          ,
          <source>in: Proceedings of the 11th international conference on subject-oriented business process management</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>F.</given-names>
            <surname>Chiariello</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Maggi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Patrizi</surname>
          </string-name>
          ,
          <article-title>Asp-based declarative process mining</article-title>
          ,
          <source>in: Proceedings of the AAAI Conference on Artificial Intelligence</source>
          ,
          <year>2022</year>
          , pp.
          <fpage>5539</fpage>
          -
          <lpage>5547</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>F.</given-names>
            <surname>Aguado</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Cabalar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Diéguez</surname>
          </string-name>
          , G. Pérez,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schaub</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Schuhmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Vidal</surname>
          </string-name>
          ,
          <article-title>Linear-time temporal answer set programming</article-title>
          ,
          <source>Theory and Practice of Logic Programming</source>
          <volume>23</volume>
          (
          <year>2023</year>
          )
          <fpage>2</fpage>
          -
          <lpage>56</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>C.</given-names>
            <surname>Di Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Maggi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Montali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <article-title>Resolving inconsistencies and redundancies in decl</article-title>
          .
          <source>process models, Information Systems</source>
          <volume>64</volume>
          (
          <year>2017</year>
          )
          <fpage>425</fpage>
          -
          <lpage>446</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>G. D.</given-names>
            <surname>Giacomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Y.</given-names>
            <surname>Vardi</surname>
          </string-name>
          ,
          <article-title>Linear temporal logic and linear dynamic logic on finite traces</article-title>
          ,
          <source>in: Proceedings of the 23rd IJCAI</source>
          , Beijing, AAAI,
          <year>2013</year>
          , pp.
          <fpage>854</fpage>
          -
          <lpage>860</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Grant</surname>
          </string-name>
          ,
          <article-title>Classifications for inconsistent theories</article-title>
          ,
          <source>Notre Dame Journal of Formal Logic</source>
          <volume>19</volume>
          (
          <year>1978</year>
          )
          <fpage>435</fpage>
          -
          <lpage>444</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gebser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kaminski</surname>
          </string-name>
          , B. Kaufmann, T. Schaub,
          <article-title>Answer set solving in practice</article-title>
          ,
          <source>Synthesis Lectures on AI and Machine Learning</source>
          <volume>6</volume>
          (
          <year>2012</year>
          )
          <fpage>1</fpage>
          -
          <lpage>238</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R.</given-names>
            <surname>Reiter</surname>
          </string-name>
          ,
          <article-title>A logic for default reasoning</article-title>
          ,
          <year>1980</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gebser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kaminski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kaufmann</surname>
          </string-name>
          , M. Ostrowski,
          <string-name>
            <given-names>T.</given-names>
            <surname>Schaub</surname>
          </string-name>
          , P. Wanko,
          <article-title>Theory solving made easy with Clingo 5</article-title>
          , in: Technical Communications of ICLP, OASICS, Schloss Dagstuhl - Leibniz-Zentrum fuer Informatik,
          <year>2016</year>
          , pp.
          <volume>2</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>2</lpage>
          :
          <fpage>15</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gelfond</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Lifschitz</surname>
          </string-name>
          ,
          <article-title>The stable model semantics for logic programming</article-title>
          ,
          <source>in: Proc. ICLP/SLP</source>
          , MIT Press,
          <year>1988</year>
          , pp.
          <fpage>1070</fpage>
          -
          <lpage>1080</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>I.</given-names>
            <surname>Kuhlmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Corea</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Grant</surname>
          </string-name>
          ,
          <article-title>Non-automata based conformance checking of declarative process specifications based on ASP</article-title>
          ,
          <source>in: First International Workshop on Formal Methods for Business Process Management</source>
          ,
          <year>2023</year>
          . In Press.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>C.</given-names>
            <surname>Corea</surname>
          </string-name>
          , I. Kuhlmann,
          <string-name>
            <given-names>M.</given-names>
            <surname>Thimm</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Grant</surname>
          </string-name>
          ,
          <article-title>Paraconsistent reasoning and inconsistency measurement in declarative process specifications, Under review</article-title>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>