<!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>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Riichiro MIZOGUCHIA</string-name>
          <email>mizo@jaist.ac.jp</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Japan Advanced Institute for Science and Technology (JAIST)</institution>
          ,
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Laboratory for Applied Ontology (LOA), ISTC-CNR</institution>
          ,
          <addr-line>Trento</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>From the standpoint of applied ontology, the problem of understanding and modeling causation has been recently challenged on the premise that causation is real. As a consequence, the following three results were obtained: (1) causation can be understood via the notion of systemic function; (2) any cause can be decomposed using only four subfunctions, namely Achieves, Prevents, Allows and Disallows; and (3) all these subfunctions can be defined in terms of Achieves alone. It follows that the essence of causation lies in a single function, namely Achieves. It remains to elucidate the nature of the Achieves function, which has been elaborated only partially in the previous work. In this paper, we first discuss a couple of fundamental policies in the above mentioned causation theory since these are useful in the discussion, then summarize the results obtained in the former paper, and finally reveal the nature of Achieves giving a complete solution to the problem of what causation is.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Causation</kwd>
        <kwd>systemic function</kwd>
        <kwd>device ontology</kwd>
        <kwd>direct causation</kwd>
        <kwd>state-mediation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Although what causation is has been discussed for many years, it has been considered an
unsolved problem to date. Assuming causation is real, this paper discusses causation as an
occurrent (causing) and aims to demonstrate that it is essentially achieving. This view has
been presented in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] where the authors obtained the following results: (1) causation can be
understood as a case of systemic function, and hence it is possible to talk about causation in
terms of function, (2) Causing can be decomposed along two dimensions, direct/indirect and
positive/negative, into the four subfunctions Achieves, Prevents, Allows and Disallows, and
(3) Prevents, Allows and Disallows can be defined in terms of the Achieves function. It
follows that causation is essentially understood in terms of Achieves.
      </p>
      <p>
        The main goal of this paper is to uncover what Achieves is. This issue has been only
partially tackled in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Before addressing the main topic, the paper reviews how an occurrent
causes another. This review leads to fruitful discussions of causation which relies on three
policies adopted in the theory: (1) the state-centric approach, (2) the distinction between
direct and indirect causations, and (3) the impossibility of direct causation between events.
On the basis of these discussions and policies, we see why the conventional attempts to
explain causality have not been successful. Then, after summarizing the results obtained in
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], we will turn to our main goal, the elucidation of the Achieves function. More precisely,
we will reveal the nature of Achieves for all possible relata giving in this way a solution to
the question of what causation is.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Presuppositions, Negative causation, and Fundamental claims</title>
      <sec id="sec-2-1">
        <title>2.1 Typical existing theories</title>
        <sec id="sec-2-1-1">
          <title>The main questions driving this research can be articulated as follows:</title>
          <p>
            (i) What is causation?
(ii) Does a theory of causation explain (exclude) the known positive (negative) examples?
Typical attempts to define the causation C→E are listed below [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ]:
(1) E-type events regularly follow C-type events.
(2) E is counterfactually dependent on C.
(3) There is a spatiotemporally continuous transfer of energy or momentum from C to E.
(4) C raises the probability of E.
(5) By manipulating C, we could bring about changes in E.
(6) Dispositional account of causation [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ][
            <xref ref-type="bibr" rid="ref4">4</xref>
            ].
          </p>
          <p>
            Unfortunately, it has been shown that none of these successfully answers the above
questions[
            <xref ref-type="bibr" rid="ref2">2</xref>
            ][
            <xref ref-type="bibr" rid="ref5">5</xref>
            ].
          </p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 Presuppositions</title>
        <p>
          The view in this paper embraces the following five views and restrictions which were
introduced and motivated in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. Note here that they are introduced for scoping the research.
        </p>
        <p>Presupposition 1: Causation is real and not a mere cognitive artifact necessary for human
understanding of phenomena.</p>
        <p>Presupposition 2: We do not discuss epistemological causation. That is, identification of
the cause of a given effect and prediction of the effects of a given cause are out of scope.
Presupposition 3: Human factors are out of scope. For example, we do not discuss
causations such as “The cause of the accident is carelessness of the driver”.
Presupposition 4: We only deal with phenomena in classical physics, and we assume
causal relation is asymmetric, that is, if C1→E1, (read: C and E are events and C causes
E), then E1→C1 does not hold.</p>
        <p>Presupposition 5: We only discuss token-level causations. That is, we do not discuss
causation like “Smoking causes cancer” but discuss what the “cause” is in “Tom’s
smoking caused him to contract cancer”.</p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3 Negative causation</title>
        <p>
          Generally speaking, negative causation is considered particularly challenging. It is known
that there are two types of negative causation: causation of absence and causation by absence.
An example of the former is
“No robbery occurred because John locked the door”, and an example of the latter is
“A thief broke into Tom’s house because he did not lock the door.”
Causations related to absent occurrences are common in daily life, and hence causal theories
that cannot explain them fail at least at the practical level. That said, it is difficult to talk about
non-existing entities even in applied ontological systems, in particular those developed
within a realist approach. Resolving this problem is a challenging task. The theory discussed
in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] can explain negative causation and overcome other disadvantages introduced in
traditional approaches like, for instance, counterfactual theory [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4 Fundamental claims</title>
        <p>Let us consider two examples: (a) Traffic accident and (b) Blood clot growth (See Fig. 3).
a1. A car hit a person. b1. A blood clot grew.
a2. A witness informed a fires station b2. The blood vessel narrowed.</p>
        <p>(EMS) of the accident. b3. The flow rate of the blood reduced.
a3. An ambulance came and transferred the b4. An organ downstream was lacking
victim to a hospital. oxygen.
a4. The victim arrived at the hospital. b5. It contracted an ischemic disease
a5. A doctor examined the victim. b6. etc.
a6. etc.</p>
        <p>In spite of the difference of the domain, these two are often considered similar in terms of
causation because, so the argument goes, the causal chains they manifest are similar.
However a closer investigation reveals that they are very different from each other. What
exists in the traffic accident is a sequence of completed processes (events). Each event
happens after the former event has completed. On the other hand, at least the first three
occurrents in the blood clot case happen concurrently, that is, it is wrong to say that the
effective cross section of the blood vessel starts to decrease after the completion of the growth
of the blood clot. This is a continuous and concurrent process with the decreasing in flow rate
happening together with the clot growing. The occurrents in the case of the traffic accident
have no direct interaction between them but interact with each other indirectly with the
mediation of states, while there is no state-mediation in the case of blood clot and all the
processes are ongoing after the organism downstream has contracted an ischemic disease.</p>
        <p>The issue here is whether the causal interaction between two processes is done by
mediation of state or not. Therefore, the fact that these processes are constituted of states is
irrelevant here. In fact, direct interaction between two processes are mainly done by
equationbased parameter propagation where no state-mediation exists between them (See 5.1).</p>
        <p>Note here that such ischemic disease will not be cured even if the growth of the clot has
terminated, since it has been caused by the state of the smaller cross section of the blood
vessel rather than the growth process itself. This fact tells us a very important message which
is summarized as:
Claim 1: States play crucial roles in causation. So, states necessarily appear in the relata of
causation.</p>
        <p>
          Although all the interactions between the occurrents in the traffic accident happen with the
mediation of states, those between b1, b2 and b3 in the blood clot case happen directly on
each other, and hence they do not need any state in between the causal interaction to occur.
This fact suggests a new distinction among causation kinds:
Claim 2: There are two types of causation: direct causation and indirect causation. The latter
happens with the mediation of states, while the former needs no state-mediation in between.
Imagine two occurrents causally connected to each other. In the terminology of [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], if they
overlap, then the interaction between them must be of the type holding between processes
rather than between events. Remember that any event, a completed process in [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], must be
dealt with as a whole. This inherent property of an event prohibits direct interaction between
events. This is obvious from no completed occurrents can directly influence another one after
the completion. These observations lead to our third claim:
Claim 3: There is no direct causation between events (understood as completed processes).
These three claims challenge the traditional view of causation as found in the literature. The
state-based approach to causation is the basis for the theory of causation discussed in this
paper as we are going to see in the next section.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Fundamental issues for fruitful discussion on causation</title>
      <p>In this section, we discuss two fundamental issues derived from the above three claims for
better discussion on causation.</p>
      <sec id="sec-3-1">
        <title>3.1 How an occurrent causes another</title>
        <p>Suppose that two causally connected events/processes C and E occurred consecutively (in
turn) in which C has influenced E in some way. Such an influence must be a kind of
interaction between C and E. As to the question of when/where it happens, only the following
four sequences are logically possible:
(a) C; the interaction; E
(b) C(including the interaction); E
(c) C; (including the interaction)E
(d) C(including the interaction); (including the interaction)E
The first case seems not possible because the interaction between C and E cannot happen at
the time in which C had completed and E has not happened yet. Therefore, an answer can be
provided only by the other three cases. The essence of these three is that the interaction
between C and E are included in either C or E. Considering that any interaction requires the
participation of the interacting entities, here C and E, it turns out that only (d) where C and
E are overlapped is valid. This conclusion coincides with our claims discussed earlier. That
is, the fact that the case (a) does not hold corresponds to Claim 3: “There is no direct causation
between events”,. Case (d) corresponds the Claim 5 which will be introduced in section 5
and corresponds to: “Causal efficacy inheres in an event”. Up to here, by interaction, we
mean direct causation between processes or events. However, the case (a) turns out to be
possible if we expand it to accept indirect interactions via states suggested by Claim 2. Some
people might think an interaction, call it F, between C and E can be an ordinary process/event
that mediates the influence of C on E. However, such thought fails under a regression
argument because the same problem arises between C and F. Now let us consider the case
where C and E meet (share the end and beginning instants). Direct causation is positive so
that a substantial interaction like energy or momentum transfer should happen for C to
influence E. However, such transfer cannot happen in an instant time because there is no
instant occurrent in reality. Therefore, (d) is valid only for overlapping cases.</p>
        <p>In summary, (a) is possible only in the case of indirect causation mediated by states
created by C, while only (d) is possible if we confine the discussion to direct causation. In
other words, the secret of how an occurrent causes another is hidden in the case (d) which we
are going to discuss in section 5.2. As far as the author knows, none of the existing theories
on causation including the six theories presented in 2.1 cares about the directedness of
causation.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 Granularity and Adjacency</title>
        <p>In the discussion on causation in the literature, not enough attention has been paid to the
granularity of the occurrents and of the causal chain. In “John contracted cancer (E) because
of smoking (C)”, for example, a long causal chain is hidden between C and E, and hence
these two events are not adjacent to each other in the causal chain. Special attention must be
paid on the adjacency between the cause and its effect when discussing causation. Imagine,
for example, a case where a discussion on the nature of C → E is made in a causal sequence
which, when better detailed, turns out to be C→C1→C2→C3→E. The discussion would be
problematic because it is not clear which causation is actually discussed. Is it the causation
C→C1 or C1→C2, or else? Indeed, it is unclear what one means by the causation C → E
where C and E are not adjacent in the first place. Some might express objections by saying
that it is theoretically difficult to talk about adjacency of causal occurrents because
finergrained causal sequences could exist between any causal pairs of events. Although the worry
makes sense in many cases, it is not always true in reality. For example, “John kicked a ball
(C) and it traveled away (E)” is a case where the cause and its effect are adjacent
independently of the granularity. A kicking which is an impact-giving occurrent on an object
by swinging one’s leg is a complex of multiple micro motions, so it has a long causal
sequence in it, but a kicking is a macro occurrent and refers to the entire sequence and hence
the adjacency between the kicking and traveling occurrents remains unchanged. Concretely
put, assume that a kicking (C) is composed of three finer causal units (say, C0→C1→C2→C3).
Then the whole causal sequence becomes C0→C1→C2→C3→E in which the last event before
E (the ball’s traveling) is C3, i.e., the collision between the foot and the ball. There is no
finergrained causal chains between C and E because C includes all events just before E happens.
As described above, the kicking is thus a macro occurrent C that starts at C0 and ends at C3.
The reason why the adjacency is not influenced in this example is because what can be
decomposed by introducing finer-granular causation is only the causal occurrent itself rather
than the causal link (→). The boundary between the cause and its effect under consideration
remains unchanged in the case of decomposition of occurrents.</p>
        <p>Another popular example: “John struck a match (C) and the match fired (E)”, is also
inappropriate for fruitful discussion of the nature of causation. There are several important
causal occurrents between C and E, for example: “John struck a match (C) → frictional heat
was generated → the gunpowder ignited → the match bar temperature rose → the match bar
fired (E)”. Because of the existence of such a finer causal chain in between, it is not
appropriate to argue about the causal relation between C and E without a theory of
composition of a causal chain.</p>
        <p>The important issues about adjacency can be summarized as follows:
(1) Discussion of the nature of causing (denoted by →) using examples (C→E) must be
done in the situation where the causal link being discussed is uniquely identified.
(2) In order to uncover the nature of causation, we should first tackle the adjacent causation
before the nature of causal chains.
(3) Our new finding on directedness of causation is of importance because it is compliant
with (1). Any direct causation has its unique “causing(→)” in C→E and problematic
issues appear only in indirect causations.
(4) Direct causations are unaffected by additive/subtractive interventions because, in the
case of &lt;Event → State&gt; pattern, when the happening of the effect (E) is under
consideration, the causal event (C) has completed already which guarantees E has
happened, and in the case of &lt;Process → Process&gt;, as is discussed in 5.2.2, both C and
E are happening concurrently and hence at the time E exists C is necessarily happening.
That is, there is no way to separate them. Needless to say, if C does not happen, there is
no need to talk about E’s occurrence. (In the case of indirect causation and/or a long
causal chain, however, an intervention could occur at any time after C has completed)
None of the six existing theories shown in 2.1 cares about the adjacency of causation.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Summary of the theory of causation</title>
      <p>
        This section summarizes the achievements obtained in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which will be extended in section
5 to complete a presentation of the entire theory. First of all, we present informal definitions
of state, process and event.
      </p>
      <p>A process is an ongoing/progressive occurrent which exists at any instant as a whole while it
is activated. It constitutes an event when completion.</p>
      <p>An event is a completed occurrent and is dealt with as a whole spreading over the entire
interval. It has temporal parts. While it cannot change, a process can. A sequence of events
forms a process.</p>
      <p>A state is a time-indexed quality and its consecutive change constitutes a process. While the
quality inheres in the bearer, it (the bearer) participates in the state when viewed from
temporal perspective.</p>
      <sec id="sec-4-1">
        <title>4.1 Causation and function</title>
        <p>
          Given a causation C→E, an entity A composed of all entities participating in C can be said
to perform a systemic function (see [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]) that achieves E by behaving in a certain way in C.
Indeed, considering E as a systemic goal for C, we obtain the following claim:
        </p>
        <sec id="sec-4-1-1">
          <title>Claim 4: Any causation can be mapped to a systemic function.</title>
          <p>
            Technically, the validity of Claim 4 relies on a series of results that led to the introduction of
notions like systemic context and systemic function [
            <xref ref-type="bibr" rid="ref8">8</xref>
            ], and theories like the device ontology
[
            <xref ref-type="bibr" rid="ref9">9</xref>
            ]. The device ontology is a system of roles that generalizes an entity that acts as a device
in the propagation of other entities (e.g., the heart as a device in a human body), and enables
us to talk about behaviors of an entity in a system and of externally detectable input/output
characteristics. The modeling is granularity-independent thanks to the recursive application
to behavioral analysis of the components where necessary. Although we will briefly explain
it in 5.1, readers can find the details of the device ontology in [
            <xref ref-type="bibr" rid="ref1">1</xref>
            ] and [
            <xref ref-type="bibr" rid="ref9">9</xref>
            ].
          </p>
        </sec>
      </sec>
      <sec id="sec-4-2">
        <title>4.2 Essentials of causation</title>
        <p>Note first that Claim 4 does not have a revisionist goal, it does not attempt to free the world
from causation. The mapping instead aims to shed light on causation by studying it in terms
of functions. In other words, while causation is assumed to be a truly ontological notion
(Presupposition 1), its rewriting in terms of function helps to deepening its understanding. Of
course, there is an obvious circularity in the causation-function mapping due to the fact that
causation inheres in function. However, this circularity does not raise a problem here since
there is no attempt to reduce the former to the latter. On the contrary, since the circularity
makes evident the strict dependence of function over causation and since we already have a
well-developed theory of function, it is interesting to see what we can learn by analyzing
causality in terms of functions. The core of a function is the achievement of a goal by a
behavior, which suggests that the most generic function is the Achieve function as we are
going to show.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3 The functional square</title>
        <p>
          As stated earlier, there are two distinctions about causation: direct/indirect and
positive/negative. Achieves is direct and positive. According to these two dimensions, there
are four types of functions, see Table 1, with Achieves being classified as direct and positive.
Achieves is investigated in section 5, here we
define the other three.
Prevents is defined as follows (for details see
[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ])
        </p>
        <sec id="sec-4-3-1">
          <title>Definition 1 (Prevents): In context C, an occurrent X prevents an occurrent Y if and only if there exists an occurrent Z in C such that (i) X Achieves Z in C, and (ii) Y and Z are incompatible in C by which we mean either Y or Z is true but not both in C.</title>
          <p>Some readers may find it uncomfortable to bring up context when discussing causation,
but this is by no means a relativization of causation to context, rather the opposite. It is by
selecting a causation that automatically one also determines a context in which the causation
holds. Imagine, for example, that “John could not enter the room because the door was
locked”. In order to make this causation valid, a context is required to ensure that there is no
other way to enter the room (e.g., there is no other unlocked door or window) and he is not
allowed to break in. Causal talks in the literature implicitly assume the existence of such
contexts.</p>
        </sec>
      </sec>
      <sec id="sec-4-4">
        <title>4.4 Indirect causation and preconditions</title>
        <p>Many of the examples discussed thus far in the literature are examples of indirect causation
as shown below.</p>
        <sec id="sec-4-4-1">
          <title>Example 1: No robbery occurred because John locked the door. Example 2: A thief broke into Tom’s house because he did not lock the door.</title>
          <p>Example 3: Emily’s dog was bitten by an insect, contracting an eye disease as a result.</p>
          <p>
            Ignoring this, she did not take the dog to any animal hospital. Later the dog lost its sight.
(extracted from [
            <xref ref-type="bibr" rid="ref10">10</xref>
            ]).
          </p>
          <p>
            Example 4: A father pushing his child out of the way of a speeding car saved the child’s life
(i.e. causes it not to die). [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ].
          </p>
          <p>
            Example 5: The failure of delivering a piece of machinery in time caused a machine to break
down.[
            <xref ref-type="bibr" rid="ref12">12</xref>
            ]
Nevertheless, the discussion of causation in the literature has been based on one type of
causation “An occurrent C caused an occurrent E” without distinguishing between direct and
indirect causation [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ][
            <xref ref-type="bibr" rid="ref5">5</xref>
            ]. The proposal of the author is to adopt a state-centered view and to
conceptualize indirect causation as state-mediated causation. From [
            <xref ref-type="bibr" rid="ref1">1</xref>
            ] we know that the
result is significant. Taking this approach in combination with the functional view, one can
show that many examples discussed in the literature are not about the Achieve function, but
they are about the Allow and Disallow functions.
          </p>
        </sec>
      </sec>
      <sec id="sec-4-5">
        <title>4.4.1 Preconditions</title>
        <p>A precondition for an occurrent is a condition whose truth value influences the activation of
the associated occurrent. Before defining the latter two functions, we note that there are two
types of preconditions for an occurrent. We call one the facilitative precondition and the other
the preventive precondition. Either one can be stated as follows:</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Facilitative precondition for X:</title>
      <p>If occurrent X occurs in context C, the facilitative precondition of X is true in C.</p>
    </sec>
    <sec id="sec-6">
      <title>Preventive precondition for X:</title>
      <p>If occurrent X occurs in context C, the preventive precondition of X is false in C.</p>
      <sec id="sec-6-1">
        <title>4.4.2 Allows and Disallows</title>
        <sec id="sec-6-1-1">
          <title>We can now define the functions Allows and Disallows.</title>
          <p>Definition 2 (Allows): Occurrent X Allows occurrent Y in context C if and only if there is a
state Z that satisfies one of the following conditions: In C, (i) X Achieves Z and Z is a
facilitative precondition for Y, (ii) X Prevents Z and Z is a preventive precondition for Y,
and (iii) X maintains Z and Z is a facilitative precondition for Y.</p>
          <p>Definition 3 (Disallows): Occurrent X Disallows occurrent Y in context C if and only if there
is a state Z that satisfies one of the following conditions: In C, (i) X Achieves Z and Z is
a preventive precondition for Y, (ii) X Prevents Z and Z is a facilitative precondition for
Y, and (iii) X maintains Z and Z is a preventive precondition for Y.</p>
          <p>Note that the last two definitions use the function Maintain which originally refers to the
function of outputting the incoming operand without changing it. The prototypical example
is a conduit that outputs exactly what is fed into it: a water pipe has an output flow rate that
is equal to the input flow rate. The general Maintain function performs similarly by keeping
the current state unchanged. In terms of Maintain, “John did not lock the door” is paraphrased
as he Maintained the lock in the unlocked state. In other words, the omission of an event that
should have occurred Maintains the current state (by doing nothing). The introduction of
Maintain thus overcomes the theoretical difficulty of mentioning an occurrent which does
not happen.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>On the Achieve function</title>
      <p>The discussion we have done thus far enables us to confine the study of the meaning of
causation to that of Achieves, and hence we need to investigate this function to shed light on
what causing is. This section is devoted for this purpose.</p>
      <sec id="sec-7-1">
        <title>5.1 Rule of how to apply the device ontology</title>
        <p>
          The device ontology [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] is a system of roles such as device (actor), conduit, operand and
medium for capturing dynamic systems in a consistent manner. A device receives operand
carried by medium and processes it to output. It has a nested structure for finer-granular
phenomena. It is used to define function in a systemic context in which its input-output
behavior realized by the internal processing plays the functional role under consideration in
the given systemic context [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Assume a causation C → E is given. Considering E is a
systemic goal achieved by the occurrent C, an entity composed of all objects participating in
C can be said that it performs a systemic function that achieves E using C in that context.
This conceptual framework is elaborated in terms of “what to achieve” and “how to achieve”
defined in function decomposition proposed in [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Then, we have the following: “what to
achieve” corresponds to E and “how to achieve” to C, which shows a causal sequence of
C→E is equivalent to Achieves function performed by the device identified by the above way.
The implication of this device ontology-based modeling is significant. The key idea is to
consider C in C→E an internal phenomena (occurrent) happening in a device which performs
Achieves function. It contrasts the ordinary notion of a causal chain which is conceptualized
Norm al state of
the w indow
        </p>
        <p>Stone being
on the ground</p>
        <p>Effect Effect Effect
[CAarums]e (hVInasin.adVt)ehlios.[CCoanudseu it] (awSttinothdneoew )(twSoiuttohcnhVeins)g
(Sw ing) (toAltlroawvienlg）</p>
        <p>Ca u se (Throw )</p>
        <p>Ca u s e (Collision )</p>
        <p>E ffe ct
[Ston e] (Break ag e
Ca u se of th e
(Stone w in d ow )
im
pactgiving)
as a sequence of causally connected occurrents at the same level. On the other hand, our
modeling is nested in multiple devices of different granularity in such a way that a cause is
one-level deeper than the corresponding effect as is depicted in Fig. 1. Thanks to the
granularity-free characteristic, the above way of application of device ontology to modeling
of causation works for any causal pair of occurrents.</p>
        <p>For example, suppose a situation where Tom threw a stone to the window of a house and
it was broken because the stone hit it. Before the stone-throwing event, it seems there is no
system which has a systemic function there. Tom, the stone and the window seem to exist
independently of each other without forming any system and such a system does not have to
be there. However, a system emerges when he has thrown a stone to the window. That is,
whenever and wherever C→E exists a system is there because of the identification of a
causation which reveals a certain connection between participants of the related occurrents.
At the time when Tom held a stone and started to throw it to the window, his arm/hand, the
stone and the window virtually form a system (device) in which three behaviors (occurrents)
happen in turn: throwing motion, stone traveling and the stone hitting the window. Whether
or not Tom has an intention to break the window does not matter here. Once a causation “Tom
threw a stone to the window of a house and it was broken” is picked out, we can talk about a
window breaking system composed of Tom’s arm/hand and the stone together with a window
as a target object. There would be three-level granularity. The coarsest granularity suggests
to model the phenomena as a system (device) composed of the stone and his arm whose input
is the normal state of the window and output is the breakage of the window caused by the
collision, in which all the three occurrents are included (See Fig. 1). What happened in this
system is analyzed in the second coarsest granularity. That is, two subsystems are identified:
(1) the stone as a window-hitting subsystem and (2) his arm and a virtual conduit (the 3D
region occupied by the trajectory of the stone) with the stone as a stone-travelling subsystem.
In the first subsystem, the stone touching (hitting) the window with velocity Vs corresponds
to the cause and the breakage of the window to the resultant occurrent (effect). The second
subsystem models how the stone touches the window with Vs with input of the initial location
(ground) of the stone and output of the final location (at the window) with Vs. The resulting
configuration of system/subsystems is shown in Fig. 1. We now obtain a rule for the
application of the device ontology in causation as occurrent:
[Rule] Identify a device by assigning E as output (what to achieve) and C as the internal
behavior (how to achieve). If necessary, apply this rule to C recursively (e.g., in the case
where C is a causal chain made of finer-granular occurrents).</p>
      </sec>
      <sec id="sec-7-2">
        <title>5.2 The essentials of Achieves</title>
        <p>Finally, it is time to investigate the Achieves function in all cases of relata in terms of the
possible types such as event, process and state.
5.2.1</p>
      </sec>
      <sec id="sec-7-3">
        <title>Event → Process</title>
        <p>
          A typical example is a collision of two balls in a billiard game. Imagine that a rolling white
ball collides with a red ball at rest with velocity Va, and the red ball rolls afterwards. At first
glance, it seems that the collision event causes the red ball rolling, but this is not accurate.
There is no instant event in reality and any collision is a quick push process with a large
acceleration. Because it is incorrect to say that the red ball starts rolling after collision, this
should be &lt;Process → Process&gt; causation rather than &lt;Event → Process&gt;. In addition, what
is activated by the collision is not an event but a process. Although some people might think
the red ball rolling must begin by a starting event, but such a starting event is essentially a
sub-event associated with all occurrents, it cannot be a relata of causation, since any relata
must be an entity as a whole rather than a part. Another seemingly problematic example
which seems to belong to the &lt;Event → Process&gt; pattern would be &lt;A switch was turned on
→ the machine worked&gt;. However, because what caused the machine to work is not the
switch-turning behavior but the resulting “on” state of the switch, this is not a direct but an
indirect causation. The above observation suggests that there is no &lt;Event → Process&gt;
pattern in the real world. This is due to the nature of an event which must be dealt with as a
whole at any time [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] and once it has terminated there is no way to influence others except
via resultant intermediate states. However, such state-mediated causation is an indirect
causation. If the causal influence happens before the termination, then it is not an event but
a process which performs the influence as discussed in the next sub-section.
5.2.2
        </p>
      </sec>
      <sec id="sec-7-4">
        <title>Process → Process</title>
        <p>A typical example of this pattern is a pair of a piston and
a crank (see Fig. 2). The piston and the crank are
connected to each other by a joint so that their behaviors
(piston’s downward and crank’s rotation) are interlocked
and are necessarily synchronized. In other words, the two
processes happen concurrently which is the common
interaction of this pattern. A remarkable feature of the
P→P pattern is that its effect is generated via laws such as
f=ma or law-like formula such as x=y which is free from
causation. In the case of the push process of the piston &amp;
crank, for example, it seems that the piston exerts force f
on the crank and the crank moves with acceleration a (=
f/m). Although it would be correct in terms of Newtonian
mechanics, we try to avoid application of physical laws
as much as possible because they are hypotheses in
nature and they might unconsciously introduce hidden
causation. Therefore, we concentrate on the fact that
there exists a shared individual in any pushing/pulling
phenomena caused by contact force. That is, we identify
an equation x=y in which x and y are
positions/speeds/accelerations of the bottom edge of the
piston rod and the edge of the crank, respectively. We talk
of these two behaviors (motions) without using formula
f=ma. (The equation x=y is not a law but a causation-free Fig. 3 Blood clot.
formula which holds a priori and hence we can accept it
as given truth.) This is why we introduce equation-based
parameter propagation. A similar equation is found in the blood clot case shown in Fig. 3 in
which x=y+z holds where x is the cross section of the blood vessel, y is the area of the vertical
cross section of the clot and z the cross section of the effective channel of the blood vessel.
This is also such a formula that we can accept as given truth rather than an equation derived
from a physical law. A typical example of Achieves of this type is throwing (an object) as a
process in which the position and velocity is shared by the hand and the object (x=y) and
Allows, by releasing, the object to travel with the initial position and velocity at the time of
the release. Other examples include push, pull, warm, cool, etc.
(a) Equation-based parameter propagation
The issue we need to discuss as to the causation in the pattern of P→P is whether the
propagation through such formula is causal or not. Although y increases if x increases in the
case of x=y, it happens not because of the relation between x and y is causal, since the reason
why x=y holds in the case of the piston &amp; crank is because both objects share the same entity
(the joint) and there is only one motion of the same entity with two different perspectives.
So, it seems there is no causation in the propagation made through x=y. However, there exist
two phenomena in which the piston pushes down the crank and the crank pulls down the
piston. These two phenomena are causally different, though the observable behaviors are the
same. We need a more careful investigation into this.</p>
        <p>We have neglected &lt;Process → State&gt; as a pattern in the discussion because it is
understood to be included in the pattern of &lt;Process → Process&gt; because a process is a
continuous/ consecutive change of states. Nevertheless, if we try to understand what is
happening at each time instance during the interval when the process is ongoing, it is useful
to investigate the &lt;Process → State&gt; case. Similar to the discussion in the case of &lt;Event →
State&gt; discussed in 5.2.4 in which the state is obtained as the result of the completed event,
the state on the right-hand side of &lt;Process → State&gt; seems to be also the result of the process
on the left-hand side. To support this conclusion we need to understand the state in the process
and the propagation from the state on the left-hand side to that on the right-hand side. Note
here that a process is a sequence of state change. In other words, a state or a set of states form
a process when they change as time goes, and as a result, a new state keeps being created at
any time while the process is ongoing. All processes can be said that they have causation in
their state change. Let us examine this claim for the possible two cases:
[Case 1] In the case that the process under consideration has an operand (target object), the
state change of the operand is the result of some operation done by the action/occurrent
intrinsically specified in it. So, the state change of the object is causal.
[Case 2] In the case of no operand, that is, occurrents denoted by intransitive verbs, on the
other hand, we need more neat consideration.</p>
        <p>Let us take “growing” as an example. Growth of an organism is made thanks to a lot of
internal biological activities of its parts. The result of the growth is of variety according to
attributes/states we pay attention. When we concentrate on its size, we observe enlarging
process of its size and it is a sequence of state change in terms of the size. Apparently, it is
caused by those internal activities in the growth. Although walking is an action denoted by
an intransitive verb walk, &lt;John walking → John’s location changing&gt; is causal because
walking has a couple of complex internal causal occurrents inside which enables John to walk
and his location change is its effect.
5.2.3</p>
      </sec>
      <sec id="sec-7-5">
        <title>State → State</title>
        <p>We have discussed &lt;Event → Process&gt;, &lt;Process → Process&gt; and &lt;Process → State&gt;
patterns. The next is the pattern &lt;State → State&gt;. The blood clot case shown in Fig. 3 is a
typical example of this pattern which is analogous to a flow-control valve in fluid dynamics
in which &lt;The half-closed state of a valve → The half flow rate&gt; holds. In general, such a
case where a state can be a cause of some occurrent is limited to the case where it is an
internal state of a device. Needless to say, the growth of a blood clot is equivalent to dynamic
generation of a flow-control valve (with closing behavior) in the blood vessel.</p>
        <p>Causation we have discussed thus far is based on change which is characterized as the
non-zero derivative and on its propagation. In particular, device ontology works mainly for
such changes. Note here that there is another kind of change in the talk of causation. It is the
deviation from the standard and examples are found in flow-control valve and the blood clot
cases discussed above. We do not have a causal theory for such change yet. The causation &lt;
the half-closed state of a valve (S1)1 → the half flow rate (S2) &gt; is not based on the non-zero
derivative changes and is a complex causal phenomena based on finer-grained causal
occurrents. Although it seems difficult to tackle it at first glance, it is fairly easy to model it
in terms of the combination of &lt;Process → State&gt; together with the recursive application of
device ontology based on the rule discussed in 5.1.</p>
        <p>
          Let us take a flow-control valve as an example. Assume the valve has started to close and
stopped at an intermediate state between full open and full closed. Let S1 be the valve opening
state after the deviation from the full open state. The phenomena as a whole is an closing
event E1 but &lt;E1 → S1&gt; is not valid because it is not causation but a description of a
phenomenon from two different perspectives. Nevertheless, there are several internal
phenomena which causes to increase the resistance against the smooth flow of the fluid and
hence the flow rate is smaller than the standard (S2). To see what happens in terms of changes
with non-zero derivative, we investigate it according to two cases: (i) valve’s closing process
P1 is ongoing and (ii) P1 has terminated to become valve’s closing event E1. Following the
theory in [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], E1 is constituted of P1. While P1 is ongoing, the valve closing process P1
causes increase of the resistance against the smooth flow of the fluid so that the
flow-ratedecreasing process P2 is ongoing. Therefore, &lt;P1 → P2&gt; holds and at any time instance
during the process is ongoing &lt;P1 → S2&gt; holds. On the other hand, when P1 has terminated,
then &lt;E1 → S2&gt; is established and S2 is output. Considering S1 is also the state when E1
has terminated, the above observations suggest that the pattern &lt;S1 → S2&gt; does not mean
propagation of changes but rather continuation of causal phenomena caused by an occurrent
1 Hereafter, S1 and S2 denote not only the state “half-xyz” but also any state deviated from the standard value (state).
of other patterns, say, &lt;P1 → P2&gt;. We do not have functions of this type other than Cause.
        </p>
        <p>It would be worth to note the fact that both &lt;E1 → S2&gt; and &lt;P1 → S2&gt; hold in the case
of flow-control valve is neither usual nor trivial. The continuity of the output state between
an event and its constituent process does not always happen. Imagine a cutting process and
the corresponding event. At any time the cutting process is ongoing, the object has not been
separated yet. It has been separated only after the completion of the cutting event.
5.2.4</p>
      </sec>
      <sec id="sec-7-6">
        <title>Event → State</title>
        <p>
          The last pattern is &lt;Event → State&gt;. Whenever an event has completed, a resulting state is
generated and it lasts for a while. When you cut an object, it becomes separated. When you
buy a good of 10 USD, then your pocket money decreases by that amount and you obtain the
ownership of the good. When you finish your daily walk to the park, then you are back to
your home again. In all cases, the corresponding resultant states are successfully realized or
achieved when any event has completed. Note here that in such cases, no intervention would
occur before getting the resulting state. This is because if the event has not completed, there
is no need to talk about its effect. As we see thus far, this pattern nicely demonstrates that the
essential of causation is generating a new resultant state which would eventually causes
(Allows or Disallows) succeeding occurrents. Considering &lt;Process → Process&gt; and &lt;State
→ State&gt; patterns tend to work as continuation or maintaining of existing states and/or their
change [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], &lt;Event → State&gt; pattern plays the key role in causation by creating a new state.
As we have already seen thus far, there are many example functions of this type and cut is
one of the most typical ones. Considering that most processes will have eventually terminated
to constitute an event with resultant states, many of the concrete functions belong to this type
such as kill, produce, inform, delete, transfer, etc.
        </p>
      </sec>
      <sec id="sec-7-7">
        <title>5.3 How to terminate the recursive application of device ontology</title>
        <p>In the above discussion, especially in the case of &lt;P → P&gt;, analysis of the internal causal
phenomena is deferred to recursive application of device ontology to cope with finer-granular
phenomena as indicated by the rule presented in 5.1 (See Fig. 1). Completion of our
discussion on causation requires us to guarantee the recursive application will terminate
without leaving any ambiguity of what Achieves is. This problem is resolved as follows.</p>
        <p>Recursive application of the device ontology definitely terminates when it reaches the
minimal granularity. So, we have the following two cases:
(a) The change under consideration cannot be attributed to the inner causal phenomena of
the device, and hence it is because of proactive phenomena such as Alpha collapse which
are not reduced to more fundamental phenomena.
(b) Except (a) there are only two cases: either &lt;E1→S2&gt; or &lt;P1 → P2/S2&gt;. In either case,</p>
        <p>S2 has been obtained using a certain propagation of S1 causally obtained by E1 or P1.
The latter is apparently what we have discussed thus far so that we can identify causal source.
Only the case (a) remains to be discussed. The issue is how many such principles that are
irreducible to finer causal phenomena, exist and how much they influence our theory of
causation. Although we cannot provide a proof, there seems to exist only a few such
principles, which we introduce as primitives into our theory. We can summarize what we
have discussed in the following three claims:
Claim 5: Causal efficacy inheres in each event as the pattern of &lt;Event → State&gt; rather than
between events. It is production of a new resultant state when an event has completed.
Claim 6: Achieves, which is the core subfunction of causation, is characterized by the three
patterns: &lt;Event → State&gt;, &lt;Process → Process&gt; and &lt;State → State&gt;.</p>
        <p>Claim 7: Any causation in reality is a sequence of occurrents connected by either one of the
four subfunctions: Achieves, Prevents, Allows or Disallows.</p>
        <p>We need to elaborate the role of Allows in causal chains. Informally put, it makes one of the
facilitative preconditions of an occurrent true so that it literally allows the occurrent to happen,
that is, the occurrent does not necessarily happen then and when it happens is undetermined.
What is interesting, however, is in the case of no preventive preconditions, when an Allows
happens to make the last false facilitative precondition true, the occurrent happens at the very
time when Allows has happened. A typical example is a switch-turning event which is
understood as an Allows for a machine to work by Achieve-ing the “on state” of the switch
which must have been in the last false facilitative precondition of the machine to work.</p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>Concluding remarks</title>
      <p>
        We have discussed causation not as a relation but as an occurrent at the token level and
claimed that causing corresponds to achieving. After presenting three main claims we
discussed how an occurrent causes another together with the role of the notion of directedness
of causation. Then, we gave a brief summary of the achievements obtained in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. We finally
investigated the nature of the direct function Achieves, and showed that the source of
causation inheres in an event and that the &lt;Event → State&gt; and &lt;Process→ Process&gt; patterns
play the key role in causation.
      </p>
      <p>
        We have outlined a proposed theory of causation. The future work includes formalization
of our theory and proper positioning of the theory in the rich history of causal theories
including a closely related work [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] as well as a theory of causal chains. Apparently, such a
causal chain that is composed only of Achieves would be equivalent with Achieves as a whole.
However, many of the real causal chains would be composed of the four subfunctions:
Achieves, Prevents, Allows and Disallows. We need a theory for explaining what causation a
causal chain is as a whole in terms of these for subfunctions.
      </p>
      <p>Finally, some implications of our findings are worth noting. Our theory is free from the
simultaneity issues because it does not assume precedence of a cause to its effect. Thanks to
its sole assumption of asymmetry, it can cope with it and arrange causal ordering consistently
with the time flow from cause to effect. Another implication is the necessity of causation. It
is apparent from the proposed four subfunctions that direct causation is necessary and the
Allow function is not. Because most of real causations are causal chains which would include
Allows subfunction, we can conclude they cannot be necessary. A rigorous definition of
system and state, on which the theory relies, is still lacking. These are a genuine philosophical
issues and hence go beyond the scope of this paper.</p>
      <p>Acknowledgement
The author is grateful for Ludger Jansen and Stefano Borgo for their comments on the draft of the paper.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Toyoshima</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mizoguchi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ikeda</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          : Causation: functional perspective,
          <source>Applied Ontology</source>
          <volume>14</volume>
          (
          <issue>1</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>36</lpage>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Losee</surname>
          </string-name>
          , John: Theories of causality, Publishers, New Brunswick, New Jersey,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Röhl</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Jansen</surname>
            ,
            <given-names>L</given-names>
          </string-name>
          :
          <article-title>Representing dispositions</article-title>
          .
          <source>Journal of Biomedical Semantics</source>
          ,
          <volume>2</volume>
          (
          <issue>Suppl 4</issue>
          ),
          <fpage>S4</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Mumford</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Anjum</surname>
            ,
            <given-names>R. L.</given-names>
          </string-name>
          :
          <article-title>Getting causes from powers</article-title>
          . Oxford University Press,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Mumford</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anjum</surname>
            ,
            <given-names>R. L.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Causation</surname>
            :
            <given-names>A Very</given-names>
          </string-name>
          <string-name>
            <surname>Short</surname>
            <given-names>Introduction</given-names>
          </string-name>
          , Oxford University Press,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>[6] https://plato.stanford.edu/entries/causation-counterfactual/.</mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Galton</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Mizoguchi</surname>
          </string-name>
          , R.:
          <article-title>The water falls but the waterfall does not fall: New perspectives on objects, processes and events</article-title>
          .
          <source>Applied Ontology</source>
          <volume>4</volume>
          (
          <issue>2</issue>
          ):
          <fpage>71</fpage>
          -
          <lpage>107</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Mizoguchi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kitamura</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Borgo</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A unifying definition for artifact and biological functions</article-title>
          .
          <source>Applied Ontology</source>
          <volume>11</volume>
          (
          <issue>2</issue>
          ):
          <fpage>129</fpage>
          -
          <lpage>154</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Mizoguchi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , et al.:
          <article-title>A functional ontology of artifacts</article-title>
          ,
          <source>The Monist</source>
          <volume>92</volume>
          (
          <issue>3</issue>
          ),
          <fpage>387</fpage>
          -
          <lpage>402</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Beebe</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          :
          <article-title>Causing and nothingness</article-title>
          . In J. Collins,
          <string-name>
            <surname>N</surname>
          </string-name>
          , Hall and
          <string-name>
            <surname>L. A.</surname>
          </string-name>
          Paul (eds.),
          <source>Causation and Counterfactuals</source>
          ,
          <volume>291</volume>
          -
          <fpage>308</fpage>
          . MIT Press,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>The debate between causal realism and causal constructivism: Metaphilosophical reflections</article-title>
          .
          <source>Philosophia</source>
          ,
          <volume>81</volume>
          :
          <fpage>59</fpage>
          -
          <lpage>71</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Schaffer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Causes need not be physically connected to their effects: The case for negative causation</article-title>
          . In C. Hitchcock (ed.),
          <source>Contemporary Debates in Philosophy of Science</source>
          (pp.
          <fpage>197</fpage>
          -
          <lpage>216</lpage>
          ).
          <source>Basil Blackwell</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Kitamura</surname>
            ,
            <given-names>Y</given-names>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Kashiwase</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fuse</surname>
          </string-name>
          , R. Mizoguchi:
          <article-title>Deployment of an ontological framework of functional design knowledge</article-title>
          ,
          <source>Advanced Engineering Informatics</source>
          <volume>18</volume>
          (
          <issue>2</issue>
          ),
          <fpage>115</fpage>
          -
          <lpage>127</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Galton</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>States, processes and events, and the ontology of causal relations</article-title>
          . In M. Donnelly and G. Guizzardi (Eds.),
          <source>Proceedings of the 7th International Conference of Formal Ontology in Information Systems (FOIS</source>
          <year>2012</year>
          ), pp.
          <fpage>279</fpage>
          -
          <lpage>292</lpage>
          , IOS Press,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Dowe</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Wesley Salmon's process theory of causality and the conserved quantity theory</article-title>
          .
          <source>Philosophy of Science</source>
          ,
          <volume>59</volume>
          ,
          <fpage>195</fpage>
          -
          <lpage>216</lpage>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>