<!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>Reuse with Domain and Process Ontologies</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bahar AAMERI</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael GRUNINGER</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Toronto</institution>
          ,
          <country country="CA">Canada</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Mechanical and Industrial Eng,University of Toronto</institution>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Although several generic process ontologies have been proposed in the past, the design of process ontologies for specific domains remains a challenge. Earlier work by Aameri that provided a methodology for specifying a domain process ontology requires a characterization of the partial automorphisms of the models of an underlying static domain ontology. In this paper, we exploit the modularization of domain ontologies as a means for reusing the existing domain process ontologies through ontology combination and merging. The metatheoretic relationships among ontologies within a repository play a key role in the characterization of how a domain process ontology for a given static domain is related to the domain process ontologies based on the different modules of the static domain ontology.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>process ontology</kwd>
        <kwd>domain ontology</kwd>
        <kwd>reuse</kwd>
        <kwd>reducibility</kwd>
        <kwd>ontology design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The design of ontologies which axiomatize classes of processes specific to a particular
domain remains an important challenge in ontological engineering. A domain process
ontology axiomatizes possible classes of change within the underlying domain,
without enumerating the definable classes of activities. This distinguishes a process ontology
from process descriptions and action theories, which axiomatize properties of specific
activities. The focus is on domain process ontologies that only classify the atomic
activities within a domain, those that characterize complex activities in the domain are more
closely related to AI planning problems.</p>
      <p>
        Aameri [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] proposes a four step methodology for designing domain process
ontologies. The verification of the process ontology requires the identification of the partial
automorphisms of the models that represent the underlying domain, and consequently
needs a characterization of all models of the underlying domain ontology. Unfortunately,
both of these tasks can be quite difficult. In fact, for most real-world ontologies it is
currently unknown which classes of mathematical structures are isomorphic to their models;
the identification of the partial automorphisms of their models is thus neither trivial nor
available in the literature.
      </p>
      <p>
        Suppose we need an ontology which axiomatizes sheet metal manufacturing
processes, and we utilize the CardWorld and BoxWorld ontologies, presented in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], for
representing 2D and 3D shapes. The characterization of the models of both ontologies is not
a straightforward task, since neither ontology is synonymous with a single known
mathematical theory. Even if we did characterize the models of these ontologies, we would
most probably get lost trying to identify the partial automorphisms. To make this
problem easier, it should be possible to decompose the ontologies into modules, identify the
partial automorphisms of the models of these modules, and then use this information in
building the process ontology.
      </p>
      <p>
        As another example, suppose we want to axiomatize abstract data types and their
operations. Intuitively, we should be able to reuse the chains process ontology [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] for
representing lists, since the ontology of lists is synonymous with the ontology of
linear orderings, and the linear ordering ontology is an non-conservative extension of the
ontology of chains (which are sets of linear orderings).
      </p>
      <p>The focus of this paper is the presentation of formal techniques which address the
idea of reusability and modularization in design and verification of domain process
ontologies; in particular, we discuss how relationships between domain ontologies within
an ontology repository can assist us in identifying the properties of ontologies’ models
which are required in developing new domain process ontologies.</p>
      <p>
        The concepts of reusability and modularization in the characterization of the models
of ontologies have been explored in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Metatheoretical relationships (such as relative
interpretation, definability, conservative and non-conservative extension) between
firstorder theories are exploited to construct models of a given ontology based on models of
the related ontologies. At the base level of such techniques are ontologies that
axiomatize general mathematical structures like graphs and lattices. However, these techniques
cannot always be used in designing domain process ontologies, as the relationships
between domain ontologies are not always preserved between the corresponding process
ontologies. Our proposed solution is to exploit the same logical relationships between the
domain ontologies, but in a weaker form of reuse; instead of directly importing the
modules of ontologies that are related to a given domain ontology, we only employ certain
properties of those modules in designing the new domain process ontology.
      </p>
      <p>We start by describing the general properties of domain process ontologies, and
reviewing the methodology that Aameri proposed for designing such ontologies. In
Section 3, we review the relationships between domain ontologies within a repository, and
show how existing domain process ontologies can be reused in designing new domain
process ontologies.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Properties of Domain Process Ontologies</title>
      <p>
        As we explained in the introduction, the objective in designing domain process
ontologies is to have a complete classification of activities based on their effects, without
enumerating all definable activity classes. By following the design methodology proposed in
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], one can develop domain process ontologies that satisfy these requirements. We first
briefly review the design methodology, and then prove this claim.
      </p>
      <p>
        The key idea behind the methodology is that all changes within a domain can be
described based on a fixed set of (primitive or defined) relations. If we identify those
relations and axiomatize activity classes that affect them, we can be sure that we have a
complete classification. For a given domain, the methodology designs a first-order process
ontology with three main modules – one is the ontology of the Process Specification
Language (PSL) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and the other two are constructed based on the properties of the domain.
      </p>
      <p>The PSL ontology1 is a generic process ontology that axiomatizes fundamental
concepts for describing processes. Within the PSL ontology, states are represented by the</p>
      <sec id="sec-2-1">
        <title>1http://colore.oor.net/process%5Fspecification%5Flanguage/psl%5Foutercore.clif</title>
        <p>Predicate
activity(a)
occurrence o f (o; a)
prior(f; o)
holds(f; o)
changes(o; f)</p>
        <p>Interpretation
a is an activity.
o is an occurrence of activity a.</p>
        <p>Fluent f holds before activity occurrence o.</p>
        <p>Fluent f holds after activity occurrence o.
(:prior(f; o) ^ holds(f; o)) _ (prior(f; o) ^ :holds(f; o)).</p>
        <p>Table 1. PSL Predicates
set of fluents that hold before or after activity occurrences, and only activity occurrences
can cause state transitions. A model of the PSL ontology includes partially ordered sets
of activity occurrences, called occurrence trees. The root of an occurrence tree is
associated with an initial state, and the branches are all sequences of occurrences of the atomic
activities. Table 1 briefly describes PSL predicates that we use in this paper.</p>
        <p>The methodology begins by identifying the appropriate domain ontology that
axiomatizes the concepts of the underlying domain and their relationships independent of
the notion of change. To enable reasoning about change, the axioms of the domain
ontology are translated into a set of state constraints which extend the PSL ontology.
Translation definitions map each relation symbol in the signature of the domain ontology into
a fluent symbol in the signature of the state constraints. If the domain ontology is not
sorted, the set of state constraints must contain an axiom which indicates sorts of the
elements in the models of the domain ontology. The set of state constraints together with
the PSL ontology is called domain state ontology.</p>
        <p>
          The results in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] show that in a model of a domain state ontology, each activity
occurrence o is associated with two models of the corresponding domain ontology; one
that represents the state before the activity occurrence (and is denoted by m (o)) and the
other that represents the state after the activity occurrence (and is denoted by h (o)). In
the other words, an activity occurrence is a transition between two models of the domain
ontology. In that sense, classifying activities is equivalent to identifying different ways
of changing models of the underlying domain ontology. Instead of considering fluents
that are changed, the methodology characterizes an activity occurrence o by fluents that
are preserved. This means that we need a representation for invariant (or equivalently
common) substructures of m (o) and h (o). Since we want to characterize changes to a
particular set of fluents, we use a special type of structure-preserving maps:
        </p>
        <sec id="sec-2-1-1">
          <title>Definition 1 Let M1; M2 be structures with signature L.</title>
          <p>An injective mapping j : M1 ! M2 is a partial isomorphism loosed to a non-empty set
L L iff for all relations R 2 L , hx1; : : : ; xni 2 RM1 iff hj (x1); : : : ; j (xn)i 2 RM2 :</p>
          <p>A mapping j : M ! M is a loosed partial automorphism iff it is a loosed
isomorphism between substructures of M .2</p>
          <p>
            In general, a structure N can be represented by the set of all its partial
automorphisms denoted by PAut(N ). Note that PAut(N ) forms a monoid [
            <xref ref-type="bibr" rid="ref5">5</xref>
            ]. Since m (o) and
h (o) are models of the same theory with the same universe3 their invariant substructures
2We denote structures by calligraphic font: M ; N ; :::; the extension of a relation R in a structure M by
ha1; :::; ani 2 RM ; the domain of a mapping j by dom(j); and the signature of a first-order theory T by S(T ).
          </p>
          <p>
            3We assume that for all o, the universes of m(o) and h(o) are equal; when an element is destroyed, it is
not annihilated from the universe. Rather, its sort will change from something that is indicated by the state
constraints to ob ject. Conversely, when an element is created a new sort is assigned to an ob ject of the universe.
can be represented by subsets of PAut(m(o)). Moreover, the results in [
            <xref ref-type="bibr" rid="ref5">5</xref>
            ] and [
            <xref ref-type="bibr" rid="ref6">6</xref>
            ] show
that the lattice of the substructures of N is isomorphic to the lattice of the partial
identities in PAut(N ). Consequently, if S is an invariant substructure of m(o) and h(o) (i.e.
S m(o) and S h(o)), then the submonoid of PAut(m(o)) that represents S can be
extracted by the partial identity in PAut(m(o)) which its domain is equal to the universe
of S . The scaffold GoL is then the set of sets of partial automorphisms, loosed to L, that
correspond to all invariant substructures (with respect to L) of m(o) and h(o).
          </p>
        </sec>
        <sec id="sec-2-1-2">
          <title>Definition 2 (from [1]) Let M be a model of a domain state ontology.</title>
          <p>A scaffold GoL of an activity occurrence o in M is a set consisting of all sets Gi such that
1. All Gi j 2 Gi are submonoids of PAutL(m(o)), such that their identity elements ei j
are partial identities associated with invariant substructures (with respect to L)
of m(o) and h(o);
2. The identity element ei j of each Gi j 2 Gi has a maximal domain; that is, there is
no other identity mapping e0 that satisfies property 1 and dom(ei j) dom(e0);
3. If Gi = fGi1; : : : ; Gimg, then dom(ei1) [ [ dom(eim) dom(m(o)), and
dom(ei1) \ \ dom(eim) = ?.</p>
        </sec>
        <sec id="sec-2-1-3">
          <title>The trivial scaffold Io is the set of set of all partial automorphisms of m(o).</title>
          <p>Activities can be categorized based on which fluents they change. However, since
the objective is not to enumerate all activity classes, the methodology distinguishes the
invariant substructures up to isomorphism, and more importantly, does not consider the
number of fluents that activity occurrences change. The key question is how to identify
a set of fluents that can describe all possible changes within the domain ontology?
Suppose for two activity occurrences o1; o2, we have m(o1) = m(o2), but h(o1) 6= h(o2).
Then, there is at least one fluent, denoted by the fluent symbol F, that o1 changes it, and
o2 preserves it, and so GoF1 is not isomorphic to GoF2 . Therefore, the answer to the above
question is equivalent to find the set CT defined in the following:
Definition 3 Suppose a theory Tpsl [ Tst is the domain state ontology for a domain
ontology T , and let L be the set of all primitive and definable symbols in the language of
Tpsl [ Tst that correspond to the symbols in the language of T .</p>
          <p>CT = fL1; :::; Lng, is the minimal set such that
1. L1 L; :::; Ln L;
2. for all activity occurrences o1; o2 in models of Tpsl [ Tst</p>
          <p>m(o1) = m(o2); GoL11 = GoL21 ; :::; GoL1n = GoL2n implies h(o1) = h(o2).</p>
          <p>
            For the chains ontology Tchains, we have CTchains = ffpointg; fltg; fcomparablegg
since a theorem in [
            <xref ref-type="bibr" rid="ref1">1</xref>
            ] shows that for all activity occurrences o1; o2 in models of the
chains state ontology, if m(o1) = m(o2) and the scaffolds of o1 and o2 that correspond to
fluent symbols point, lt (stands for “less than”), and comparable are isomorphic, then
h(o1) = h(o2).
          </p>
          <p>Definition 4 summarizes the properties of domain process ontologies that are
designed with respect to the methodology. Considering property 2 in Definition 3, a
complete classification includes an activity class for each element Li of CT such that the
members of the class change fluents in Li. Thus, for each activity class the domain process
ontology includes a definition that specifies which fluents are changed and which fluents
are preserved by the members of the class. Since these definitions are in the signature
(8a) change point(a) ((8o) occurrence o f (o; a) (9x) changes(o; point(x))):
(8a) change lt(a) ((8o) occurrence o f (o; a) (9x; y) changes(o; lt(x; y))):</p>
          <p>(8a) new chain(a) (change lt(a)^
(8o; x; y) (occurrence o f (o; a) ^ changes(o; lt(x; y))) changes(o; comparable(x; y))):</p>
          <p>(8a) rearrange(a) (change lt(a)^
(8o; x; y) (occurrence o f (o; a) ^ changes(o; lt(x; y)))
:changes(o; comparable(x; y))):
(1)
(2)
(3)
(4)
of the underlying domain state ontology, the domain process ontology is a definitional
extension of the domain state ontology. This is captured by property 1 in Definition 4.</p>
          <p>Note that GoLi represents all changes that o makes to the fluents specified by symbols
in Li. Therefore, if an activity class ci is associated with Li, the scaffolds that correspond
to Li and the occurrences of the members of ci are nontrivial. On the other hand, when
an activity is not a member of ci, its occurrences do not change fluents in Li, and so the
corresponding scaffold is trivial. This is captured by property 2a in Definition 4.</p>
          <p>Notice however that there might be constraints in the domain that enforce changing
fluents in a set L j 2 CT whenever the fluents in Li 2 CT are changed. In that case, ci is a
subclass of c j. Moreover, there are activities that change fluents in L j without changing
the fluents in Li. An additional class is therefore required to distinguish these types of
activities from activities in ci. For example, the fluent symbol comparable in Tchains is
defined based on lt, and so any activity that changes comparable will also change lt. The
activity class ccomparable is therefore a subclass of clt , and the chains process ontology
(see Figure 1) includes a class of activities that change a fluent lt(a; b), but preserve
comparable(a; b). Property 2b addresses this requirement.</p>
          <p>Definition 4 Let Tpsl [ Tst be a domain state ontology for a domain ontology T .</p>
          <p>Let l (Tprocess) = S(Tprocess) n S(Tpsl [ Tst ).</p>
          <p>Tpsl [ Tst [ Tprocess is a domain process ontology for T iff
1. Tpsl [ Tst [ Tprocess is a definitional extension of Tpsl [ Tst such that for each ci 2
l (Tprocess) there is an axiom in Tprocess of the following form,
(8a)ci(a)
((8o) occurrence o f (o; a)</p>
          <p>Yi(o);
where Yi(o) is a formula in the language of Tpsl [ Tst with a unique free variable o
2. Let Act(ci) = fa : hai 2 ciM g, where M 2 Mod(Tpsl [ Tst [ Tprocess), and
SubClass(ci) = fAct(c j) : Act(c j) Act(ci)g.</p>
          <p>There is an injective mapping j : CT ! l (Tprocess) such that
(a) if ci = j (Li), then hai 2 ciM iff for all occurrences o of a, GoLi 6= Io.
(b) if there is no Li 2 CT such that ci = j (Li), then exists c j = j (L j), such that</p>
          <p>SubClass(c j) 6= ?, and Act(c j) n S SubClass(c j) Act(ci).</p>
        </sec>
        <sec id="sec-2-1-4">
          <title>We call Tprocess the domain process schemata for T .</title>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>4http://colore.oor.net/chains%5Fprocess/definitions/chains%5Fprocess.clif</title>
        <p>From this point forward, we will be using the phrase “domain process ontology”
exclusively when referring to process ontologies that satisfy the properties specified by
Definition 4.</p>
        <p>Let o be an occurrence of an activity a which satisfies property 2 in Definition 3,
but a is not a member of any activity class defined by the domain process ontology.
According to the above definition, all scaffolds of o are trivial, and since o satisfies property
2, a has no effects in the underlying domain. In the other words, all nontrivial activities
within a domain are members of at least one activity class defined by the respective
domain process ontology. This implies that the classifications specified by domain process
ontologies are complete.</p>
        <p>A domain process ontology classifies activities and defines the corresponding
hierarchy in such a way that classes in the leaves of the hierarchy tree includes activities that
have same effects on isomorphic substructures of the respective domain. This ensures
that the classification is neither enumerative, nor too general.</p>
        <p>Theorem 1 proves these two important properties of domain process ontologies.
Theorem 1 5 Let Tpsl [ Tst [ Tprocess be the domain process ontology for T , and c1; :::; cn
be the activity classes defined in Tprocess.</p>
        <p>1. Tpsl [ Tst [ Tprocess j= (8a)activity(a) c1(a) _ ::: _ cn(a);
2. Let a1; a2 be activities in a model M of Tpsl [ Tst [ Tprocess such that the effects of
a1 and a2 on the isomorphic substructures of a model of T are not isomorphic.
Then, either exists a leaf activity class ci in Tprocess such that ha1i 2 ciM and
ha2i 62 ciM , or a1 and a2 are members of more than one leaf activity class.</p>
        <p>The chains process ontology, for example, specifies a complete classification of
possible activities, but does not enumerate all definable sets of activities. In the meantime, it
is not too general as the members of each leaf activity class have same effects. To make
this more clear, consider this example: let M 2 Mod(Tchains), where M = fx; yg, and
hx; yi 2 ltM . Suppose a1 changes M to M1, where hy; xi 2 ltM1 , and a2 changes M to
M2, where M2 = fx; yg, but hx; yi 62 ltM2 and hy; xi 62 ltM2 . Clearly, both a1 and a2 are
members of change lt, however, this class is too general since a1 and a2 change
isomorphic substructures of M , but have different effects. The chains process ontology resolves
this problem by defining two subclasses, new chain and rearrange, for change lt.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Designing Process Ontologies Using Repositories</title>
      <p>In designing domain process ontologies we face two main challenges. First, we need to
find the smallest set of fluent symbols C , that satisfies property 2 in Definition 3. Second,
we have to identify the set of partial automorphisms for the relations that correspond to
those fluents. For domains with more complex structures this is even harder, since the
number of combinations that have to be examined with respect to property 2 increases
exponentially. Fortunately, in practice we have found that elements (Li) of the fluents set
C usually includes at most three fluent symbols. Therefore, in most cases we can find
mathematical structures, with well-studied sets of partial automorphisms, that represent
axioms that correspond to elements in Li. This would address the second challenge.</p>
      <p>For the first challenge, one solution is to decompose the domain ontology into
modules, determine the fluent set for each module, and then find the fluent set for the original
5Proofs of the theorems can be found at http://stl.mie.utoronto.ca/publications/reuseprocess.pdf
ontology with respect to the fluent sets of its modules. In the following, we explore this
idea further. We investigate three types of relationships among domain ontologies in a
repository, namely extensions, synonymy and reducibility, and show how these
relationships can help us in developing domain process ontologies.</p>
      <sec id="sec-3-1">
        <title>3.1. Extensions in Hierarchies</title>
        <p>We start by the simplest relationship between first-order ontologies.</p>
      </sec>
      <sec id="sec-3-2">
        <title>Definition 5 Let T1; T2 be two first-order ontologies such that S(T1) S(T2). T2 is an</title>
        <p>extension of T1 iff for any sentence F in the language of T1, T1 j= F implies T2 j= F.
T2 is a conservative extension of T1 iff T1 6j= F implies T2 6j= F.</p>
        <p>
          Unfortunately, extension (or reduction) between domain ontologies is not preserved
between the corresponding domain process ontologies. The reason is that in classifying
activities, we consider partial symmetries between the models of the domain ontology
(partial symmetries are captured by partial automorphisms), while an arbitrary extension
might both increase or decrease partial symmetries among the models. However, we can
take advantage of extensions within the hierarchies of an ontology repository.
Definition 6 (from [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]) A hierarchy H = hH ; i is a partially ordered finite set of
ontologies H = T1; :::; Tn such that S(Ti) = S(Tj), for all i; j, and T1 &lt; T2 iff T2 is a
nonconservative extension of T1.
        </p>
        <p>We know that T 0 T implies Mod(T ) Mod(T 0). That means that there might be
axioms in the extension which excludes transitions to models that are related to a specific
type of change, and so eliminates some of the activity classes of T 0. The extension might
also change the definitions of the activity classes.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Theorem 2 Let T 0</title>
      <sec id="sec-4-1">
        <title>T . Then CT</title>
        <p>CT 0 .</p>
        <p>Consider the ontology Tchains , and the ontology Tlinorder of linear orderings. Tlinorder
is an extension of Tchains, and they are in the same hierarchy. As we described earlier, the
chains process ontology includes three leaf activity classes, where the first class includes
activities that create or destroy elements in the orderings, the second one includes
activities which reorder elements in a single chain, and the third one is the set of activities that
break a chain into a group of chains, or join a group of chains to make a single chain.
However, the domain process ontology for Tlinorder only includes the first two classes
since there is an axiom in Tlinorder which states that models of Tlinorder are single chains.</p>
      </sec>
      <sec id="sec-4-2">
        <title>3.2. Definitional Extensions and Synonymous Ontologies</title>
        <p>Recall that every constant, function, and relation in a model of a definitional extension
of an ontology is definable in a model of the ontology. Consequently, every model of
the ontology can be expanded to a unique model of its definitional extension, and two
models of the ontology are isomorphic iff their expansions are isomorphic. This leads us
to conclude that a domain ontology and all its definitional extensions share one single
domain process ontology.</p>
      </sec>
      <sec id="sec-4-3">
        <title>Theorem 3 Let P1 be the domain process schemata corresponds to T1, and T2 be a definitional extension of T1. Then P1 is the domain process schemata for T2.</title>
      </sec>
      <sec id="sec-4-4">
        <title>Definition 7 Two ontologies T1 and T2 are synonymous iff there exists an ontology T3</title>
        <p>with the signature S(T1) [ S(T2) that is a definitional extension of T1 and T2.</p>
        <p>Translation definitions are sentences that interpret non-logical symbols of an
ontology, in the language of another ontology. It can be easily proved that for two synonymous
ontologies T1 and T2, there exists a set of translation definitions D21 from T2 into T1 and a
set of translation definitions D12 from T1 into T2 such that T1 [ D21 is logically equivalent
to T2 [ D12. The other direction is true as well.</p>
        <p>Definition 8 Let T0 and T1 be two ontologies such that S(T0) \ S(T1) = ?.
Translation definitions for T0 into T1 are sentences in S(T0) [ S(T1) of the form
8x pi(x)</p>
        <p>F(x);
where pi(x) is a symbol in S(T0) and F(x) is a formula in the language of T1.</p>
        <p>By definition, every pair of synonymous ontologies have a common definitional
extension. Thus, the following theorem is an immediate consequence of Theorem 3.</p>
      </sec>
      <sec id="sec-4-5">
        <title>Theorem 4 Let P1 be the domain process schemata corresponds to T1, and T2 be synonymous with T1. P1 is synonymous with the domain process schemata for T2.</title>
        <p>Suppose two ontologies T1; T2 are synonymous, and the process ontology P1 for T1
already exists in the repository. We can translate the axioms of P1 into the language of
T2, using D12, and the result is the process ontology for T2.</p>
        <p>
          Consider the DOLCE direct quality ontology Tdir qual 6 (discussed in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ])
(8x; y1; y2) dqt(x; y1) ^ dqt(x; y2)
y1 = y2
(8x1; x2; y) T Q(x1) ^ T Q(x2) ^ PD(y) ^ dqt(x1; y) ^ dqt(x2; y)
x1 = x2
(8x) T Q(x)
        </p>
        <p>(9y) PD(y) ^ dqt(x; y)
Using an automated theorem prover, it can be shown that Tdir qual is synonymous with
the ontology of injection bipartite incidence structures Tin j bipartite7 under the following
translation definitions
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
P :
D :
(8x; y) dqt(x; y)</p>
        <p>in(x; y) ^ point(x) ^ line(y)
(8x) T Q(x)
(8x) PD(x)</p>
        <p>dqt(x; y) _ dqt(y; x) _ x = y
Therefore, the process ontology for Tdir qual can be achieved by translating Tin jbipart proc8,
which is the process ontology for Tin j bipartite, into the language of Tdir qual using D. The
result is depicted in Figure 2.9
6http://colore.oor.net/quality/direct%5Fquality.clif
7http://colore.oor.net/bipartite%5Fincidence/injection%5Fbipartite.clif
8http://colore.oor.net/injection%5Fbipartite%5Fprocess/definitions/injection%5Fbipartite%5Fprocess.clif
9http://colore.oor.net/direct%5Fquality%5Fprocess/definitions/direct%5Fquality%5Fprocess.clif
(8a) change PD(a) ((8o) occurrence o f (o; a) (9x) changes(o; PD(x))):
(8a) change quality(a) ((8o) occurrence o f (o; a) (9x; y) changes(o; dqt(x; y))):
(15)</p>
      </sec>
      <sec id="sec-4-6">
        <title>3.3. Reducible Ontologies</title>
        <p>
          So far we have considered relationships between two ontologies. In the remaining of this
section, we investigate reusing domain process ontologies of theories that are
synonymous with the constructing modules of a domain ontology. We exploit the the notion
of faithful interpretation [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], which is the generalization of the notion of conservative
extension to ontologies with distinct signatures.
        </p>
      </sec>
      <sec id="sec-4-7">
        <title>Definition 9 The mapping p is an interpretation of an ontology T1 into an ontology T2</title>
        <p>iff for all sentence F in the language of T1, T1 j= F implies T2 j= p (F).
p is a faithful interpretation of T1 into T2 iff T1 6j= F implies T2 6j= p (F).</p>
        <p>
          Synonymy is a relation between two ontologies. The notion of reducibility (from
[
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]) extends it to a relationship among a set of ontologies.
        </p>
      </sec>
      <sec id="sec-4-8">
        <title>Definition 10 An ontology T is reducible to a set of ontologies T1; :::; Tn iff</title>
      </sec>
      <sec id="sec-4-9">
        <title>1. T faithfully interprets each ontology Ti;</title>
        <p>2. T1 [ ::: [ Tn faithfully interprets T ;
3. T is synonymous with T1 [ ::: [ Tn.</p>
        <p>The following lemma shows the construction of a domain process ontology from the
domain process ontologies of the modules of the underlying domain ontology.
Lemma 1 Suppose T = T1 [ ::: [ Tn is a consistent theory, and P; P1; :::; Pn are domain
process schemata correspond to T; T1; :::; Tn respectively.</p>
        <p>If S(Ti) \ S(Tj) = ?, for all 1 i; j n, then P = P1 [ ::: [ Pn.</p>
        <p>Suppose in a reduction T1; :::; Tn for T , all modules except T1 and T2 have disjoint
signatures. We can construct a new reduction T10; T3; :::; Tn for T , where T10 = T1 [ T2, so
that the signatures of theories in the new reduction is disjoint. The following theorem,
which is a consequence of Definition 10 and Theorem 4, shows the construction of the
domain process ontology for T using the domain process ontologies of its disjoint
reductive modules. Note that the domain process ontologies for T1 and T2 can be reused in
constructing the domain process ontology for T1 [ T2.</p>
        <p>Theorem 5 Suppose T is reducible to a set of ontologies T1; :::; Tn such that S(Ti) \
S(Tj) = ?, for 1 i; j n. Suppose P; P1; :::; Pn are domain process schemata correspond
to T; T1; :::; Tn respectively.</p>
        <p>Then P is synonymous with P1 [ ::: [ Pn.</p>
        <p>
          Consider a version of the Blocks World problem, in which at most one block can be
placed on another, and each block has one unique color [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. It is easy to verify that the
colored blocks world ontology is reducible to the bounded chains ontology Tbounded chains10
and Tdir qual under the following translation definitions
10http://colore.oor.net/orderings/bounded%5Fchains.clif
        </p>
        <p>
          (8x; y; z)C(x; y; z) ((9l)line(l) ^ in(x; l) ^ in(y; l) ^ in(z; l)):
(8x; y; z; l) line(l) ^ in(x; l) ^ in(y; l) ^ in(z; l) ^ (x 6= y) ^ (x 6= z) ^ (y 6= z) (C(x; y; z) _C(z; y; x)):
(21)
(16)
(17)
(18)
(19)
For the bounded chains ontology, we reuse the verified chains process ontology from
[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] (Figure 1). Considering Theorem 5, the colored blocks process ontology11 can be
obtained by translating the axioms in Figure 1 and Figure 2 using axioms 16-19.
        </p>
      </sec>
      <sec id="sec-4-10">
        <title>3.4. Weakly Reducible Ontologies</title>
        <p>Many ontologies are not reducible to standard mathematical ontologies, however, they
have subtheories that are. These cases can be captured by the notion of weak reducibility.</p>
      </sec>
      <sec id="sec-4-11">
        <title>Definition 11 An ontology T is weakly reducible to ontologies T1; :::; Tn iff</title>
      </sec>
      <sec id="sec-4-12">
        <title>1. T faithfully interprets each ontology Ti;</title>
        <p>2. T1 [ ::: [ Tn faithfully interprets a subtheory T 0
3. T 0 is synonymous with T1 [ ::: [ Tn.</p>
        <p>T ;</p>
        <p>The domain process ontologies of the reductive modules of a weakly reducible
ontology T can be reused in designing the domain process ontology for the subtheory T 0
of T which is synonymous with the weak reduction. The new domain process ontology
would be helpful in constructing the domain process ontology for T , as T and T 0 are in
the same hierarchy and T is an extension of T 0.</p>
      </sec>
      <sec id="sec-4-13">
        <title>Theorem 6 Let T be weakly reducible to T1; :::; Tn.</title>
        <p>Then CT CT 0 , where T 0 T and T 0 is synonymous with T1 [ ::: [ Tn.</p>
        <p>Consider the ontology Tmcg12 of Megiddo cyclic geometries. Tmcg is weakly
reducible to the ontology Tcyclic13 of cyclic orderings and the ontology Tweak bipart 14 of
weak bipartite incidence geometries. Figure 3 shows the axioms of Tmcg that are not in
Tcyclic and Tw bipart . The domain process ontologies for Tcyclic15 and Tw bipart 16 already
exist in the repository, and so we know that CTcyclic = ffpointg; fCg; fcmpgg (where
cmp(x; y; z) holds iff C(x; y; z) or C(z; y; x) hold) and CTw bipart = ffpointg; flineg; fingg.
Consequently, we have CTmcg ff pointg; flineg; fing; fCg; fcmpgg. However, Axioms
11http://colore.oor.net/colored%5Fblocks%5Fprocess/definitions/colored%5Fblocks%5Fprocess.clif
12http://colore.oor.net/cyclic%5Fgeometry/mcg.clif
13http://colore.oor.net/cyclic%5Fordering/cyclic.clif
14http://colore.oor.net/bipartite%5Fincidence/weak%5Fbipartite.clif
15http://colore.oor.net/cyclic%5Fprocess/definitions/cyclic%5Fprocess.clif
16http://colore.oor.net/weak%5Fbipartite%5Fprocess/definitions/weak%5Fbipartite%5Fprocess.clif
20 and 21 prevent any changes in the fluent cmp without changing the fluent in, and
therefore CTmcg = ffpointg; flineg; fing; fCgg. Theorem 7 formally proves this claim.17
Theorem 7 (MCG Classification Theorem) Suppose Tpsl [ Tstmcg is the domain state
ontology for Tmcg, and M 2 Mod(Tpsl [ Tstmcg).</p>
        <p>For any activity occurrences o1; o2 in M with m(o1) = m(o2), if Gop1oint = Gop2oint , Gloi1ne =
Gloi2ne, Gion1 = Gion2 , GCo1 = GCo2 , then Gcom1p = Gcom2p, and consequently h(o1) = h(o2).</p>
      </sec>
      <sec id="sec-4-14">
        <title>3.5. Decomposable Ontologies</title>
        <p>Decomposability is the weakest relation among the ontologies in a repository, but it can
still assist us in developing domain process ontologies.</p>
      </sec>
      <sec id="sec-4-15">
        <title>Definition 12 An ontology T is decomposable into ontologies T1; :::; Tn iff</title>
      </sec>
      <sec id="sec-4-16">
        <title>1. T interprets each ontology Ti;</title>
        <p>2. T1 [ ::: [ Tn faithfully interprets a subtheory T 0
3. T 0 is synonymous with T1 [ ::: [ Tn.</p>
        <p>We can reuse the domain process ontologies of the reductive modules of a
decomposable ontology in the same way as they are used for weakly reducible ontologies.</p>
      </sec>
      <sec id="sec-4-17">
        <title>Theorem 8 Let T be decomposable to T1; :::; Tn.</title>
        <p>Then CT CT 0 , where T 0 T and T 0 is synonymous with T1 [ ::: [ Tn.</p>
        <p>
          Consider the theory Trcc18 which axiomatizes the mereotopology Region Connection
Calculus (RCC) [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. The results in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] shows that Trcc is decomposable to the theory
TBA19, which is a first-order axiomatization of the Boolean algebras, and a connection
theory Tconnection.20
        </p>
        <p>We know that CTBA = ffelementgg and CTconnection = ffCgg. Considering the
translation definitions between Trcc and TBA, we can rename element to region, and therefore
CTrcc ffregiong; fCgg. By the following theorem we have CTrcc = ffregiong; fCgg. 21
Theorem 9 (RCC Classification Theorem) Suppose Tpsl [ Tstrcc is the domain state
ontology for Trcc, and M 2 Mod(Tpsl [ Tstrcc).</p>
        <p>For any activity occurrences o1; o2 in M with m(o1) = m(o2), if Groe1gion = Groe2gion,
GCo1 = GCo2 , then h(o1) = h(o2).</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusion and Future Work</title>
      <p>By designing a domain process ontology based on its underlying static domain ontology,
we lay the foundations for the verification of the domain process ontology with respect
to its intended models. Nevertheless, there is more to the evaluation of a domain process
ontology than a characterization of its models. One of the challenges in designing process
ontologies is to avoid the pitfall of enumerating all definable classes of activities while
still showing that the classes in the ontology capture all of the necessary distinctions. To
this end, we have provided a formal definition of a domain process ontology and have
17MCG process ontology: http://colore.oor.net/mcg%5Fprocess/definitions/mcg%5Fprocess.clif
18http://colore.oor.net/mereotopology/rcc.clif
19http://colore.oor.net/lattices/boolean%5Flattice.clif
20http://colore.oor.net/connections/connection.clif
21RCC process ontology: http://colore.oor.net/rcc%5Fcontinuous%5Fprocess/definitions/rcc%5Fprocess.clif
shown that this enables us to prove the completeness of the classification specified by the
ontology with respect to all possible changes within the domain.</p>
      <p>A second challenge is that the methodology for designing process ontologies also
requires a characterization of the partial automorphisms of the models that represent the
underlying domain, and such a characterization is not known in many cases. To
overcome this difficulty, we have proposed techniques for using the decomposition of the
ontologies into modules, identifying the partial automorphisms of the models of these
modules, and then using this information to build the process ontology. Furthermore, we
applied these techniques to design three new domain process ontologies to demonstrate
the feasibility of the approach.</p>
      <p>
        In developing formal ontologies, reusability is exploited in different forms; existing
ontologies can be imported, extended, specialized, combined [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], or translated [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] to
build new ontologies. Likewise, reusability has been explored for the purpose of ontology
verification [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and in the context of ontology design patterns [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. The type of reuse
that we apply for designing domain process ontologies (except for the case of synonymy
and reducibility) is not similar to the forms that are mentioned above. It is weaker, in the
sense that we do not directly use the existing domain or process ontologies, but is still
effective since it simplifies the design challenges and saves us from redoing a complex
and error-prone task.
      </p>
      <p>All of these process ontologies have been designed by starting with some existing
domain ontology (such as orderings, geometries, or mereotopology). In practice, there
also exist taxonomies of process classes that are part of upper ontologies or ontologies for
areas such as chemical pathways and manufacturing. In these cases, there is no explicit
static domain ontology which was used in the design of the taxonomies. Future work
will need for evaluating such process taxonomies through the identification of the correct
static domain ontology.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>B.</given-names>
            <surname>Aameri</surname>
          </string-name>
          .
          <article-title>Using Partial Automorphisms to Design Process Ontologies</article-title>
          .
          <source>In Proceedings of the 7th International Conference on Formal Ontology in Information Systems</source>
          , pages
          <fpage>309</fpage>
          -
          <lpage>322</lpage>
          . IOS Press,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruninger</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Bouafoud</surname>
          </string-name>
          .
          <article-title>Thinking Outside (and Inside) the Box</article-title>
          .
          <source>In SHAPES 1.0</source>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruninger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Hahmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hashemi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Ong</surname>
          </string-name>
          .
          <article-title>Ontology Verification with Repositories</article-title>
          .
          <source>In Proc. of the 6th FOIS Int. Conference</source>
          , pages
          <fpage>317</fpage>
          -
          <lpage>330</lpage>
          , Toronto,Canada,
          <year>2010</year>
          . IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruninger</surname>
          </string-name>
          .
          <article-title>Ontology of the Process Specification Language</article-title>
          .
          <source>In Handbook on Ontologies in Information Systems</source>
          . Springer-Verlag,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.V.</given-names>
            <surname>Lawson</surname>
          </string-name>
          .
          <source>Inverse Semigroups: The Theory of Partial Symmetries. World Scientific</source>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>D.A.</given-names>
            <surname>Bredikhin</surname>
          </string-name>
          .
          <article-title>Inverse semigroups of local automorphisms of universal algebras</article-title>
          .
          <source>Siberian Mathematical Journal</source>
          ,
          <volume>17</volume>
          (
          <issue>3</issue>
          ):
          <fpage>386</fpage>
          -
          <lpage>393</lpage>
          ,
          <year>1976</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gru</surname>
          </string-name>
          ¨ninger, T. Hahmann,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hashemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ong</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Ozgovde</surname>
          </string-name>
          .
          <article-title>Modular First-order ontologies via repositories</article-title>
          .
          <source>Applied Ontology</source>
          ,
          <volume>7</volume>
          (
          <issue>2</issue>
          ):
          <fpage>169</fpage>
          -
          <lpage>209</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>C.</given-names>
            <surname>Masolo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Borgo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Oltramari. WonderWeb Deliverable D18- Ontology Library</surname>
          </string-name>
          (final).
          <source>Technical Report</source>
          , Laboratory for Applied Ontology, ISTC-CNR, Trento, Italy.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>F.</given-names>
            <surname>Lin</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Reiter</surname>
          </string-name>
          .
          <article-title>State Constraints Revisited</article-title>
          .
          <source>Journal of logic and computation</source>
          ,
          <volume>4</volume>
          (
          <issue>5</issue>
          ):
          <fpage>655</fpage>
          -
          <lpage>677</lpage>
          ,
          <year>1994</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Randell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Cui</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Cohn</surname>
          </string-name>
          .
          <article-title>A spatial logic based on regions and connection</article-title>
          .
          <source>In Proceedings of the Third Int. Conference on Principles of KR</source>
          , pages
          <fpage>165</fpage>
          -
          <lpage>176</lpage>
          . San Mateo, California,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>H.S.</given-names>
            <surname>Pinto</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.P.</given-names>
            <surname>Martins</surname>
          </string-name>
          . Reusing Ontologies.
          <source>In AAAI 2000 Spring Symposium on Bringing Knowledge to Business Processes</source>
          , pages
          <fpage>77</fpage>
          -
          <lpage>84</lpage>
          . AAAI Press,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          and
          <string-name>
            <given-names>V.</given-names>
            <surname>Presutti</surname>
          </string-name>
          .
          <article-title>Ontology Design Patterns</article-title>
          . In Handbook on Ontologies. Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>