<!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>
      <journal-title-group>
        <journal-title>Workshop HCP Human Centered Processes, February</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Making context explicit towards decision support for a flexible scientific workflow system</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Xiaoliang Fan (</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>xiaoliang.fan@gmail.com)</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Patrick Brézillon (</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>patrick.brezillon@lip</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ruisheng Zhang (</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>zhangrs@lzu.edu.cn)</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lian Li (</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>lil@lzu.edu.cn)</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>(1) LIP6</institution>
          ,
          <addr-line>Box 169</addr-line>
          ,
          <institution>Université Pierre et Marie Curie 4 Place Jussieu</institution>
          ,
          <addr-line>Paris 75005</addr-line>
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>(2) School of Information Science and Engineering, Lanzhou University 222</institution>
          <addr-line>South Tianshui Road, Lanzhou 730000</addr-line>
          <country country="CN">P.R.China</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <volume>1</volume>
      <fpage>0</fpage>
      <lpage>11</lpage>
      <abstract>
        <p>Scientific workflow (SWF) system is a specific workflow management system applied to science arena. For years, SWF systems are widely applied to many applications, namely in physics, climate modeling, drug discovery process, etc. However, current SWF systems face the challenge to adapt the flexibility and lack of decision support for scientist. We believe the major reason for the failure is due to do not make context explicit. We propose a solution to introduce contextual graphs (CxG) in the four phases of the SWF lifecycle, each of which is expressed in a standard format, including a case study in virtual screening. Contextual graph allows to model scientists' decision making processes as a uniform representation of knowledge, reasoning, and of contexts, so that scientists are closely involved in each phase of SWF lifecycle to maximize the decision support. Finally, we conclude and highlight that using CxG is the key human-centered process for SWF systems.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Scientific workflow system liberates the computational
scientists from burden of data-centric operations to
concentration on their scientific problems
        <xref ref-type="bibr" rid="ref1 ref16 ref34">(Altintas et al.,
2004; Goble et al., 2007)</xref>
        . However, it is not yet satisfied,
considering that computational science
        <xref ref-type="bibr" rid="ref21">(Roache, 1998)</xref>
        is
always reproduced in a flexible and exploratory pattern.
Consider virtual screening
        <xref ref-type="bibr" rid="ref7">(Chen &amp; Shoichet, 2009)</xref>
        for
example, the choice of one software over others depends
much on contextual information that are highly specific of
the situation at hand, and where, when, how and by whom
the scientific workflow is executed. Thus a strong and
sustainable decision support is urged for scientists to
transfer hypotheses to discovery.
      </p>
      <p>
        Workflow flexibility becomes a critical challenge to deal
with intermittently available resources, execution failures,
and to support human-centric decision-makings. However,
identifying how scientists make decisions to address
workflow flexibility is a very complicated issue. The ways
of scientists make their decision vary from one another: (1)
based on their past experience considering successful or
failed ones; (2) inherited from the best practices within
science communities; (3) from the observed intermediate
results; and (4) just follow their own distinguished way.
Various approaches
        <xref ref-type="bibr" rid="ref18 ref27 ref35 ref9">(Zhang et al., 2008; Courtney, 2001;
Tabak et al., 1985)</xref>
        are proposed to get user involved to
describe their decision making processes. Normally in
such applications, a decision making (e.g., choose
methods, change parameters, re-design the experiment) is
measured by a decision node in workflow design
accompanying with a numerical value (e.g. IF the variable
is greater than 5, THEN execute the activity A, ELSE
execute activity B; WAIT for 2 minutes to execute activity
C). However, scientific discovery is by nature a
knowledge-intensive one
        <xref ref-type="bibr" rid="ref33">(van der Aalst et al., 2005)</xref>
        that
scientists' decisions rely not only on data and information
available, but also on a learning process in which user’s
preference, knowledge, and situation are captured to adapt
the human-centered processes.
      </p>
      <p>
        Such challenges mentioned above become an obstacle
when scientists are making adaptive decisions to deliver
new outcomes with fresh data and its context
        <xref ref-type="bibr" rid="ref13">(Fan et al.,
2010)</xref>
        .
        <xref ref-type="bibr" rid="ref3">Brézillon and Pomerol (1999)</xref>
        define context as
“what constrains the resolution of a problem without
explicit intervention in it”. We believe that the main
reason for this failure is largely due to the lack of context
management in an explicit way. In this paper we propose
four ways of making context explicit in scientific
workflow, by introducing contextual graph to in the four
phases of scientific workflow lifecycle. Representing and
making “context” explicit in SWF system would provide
sustainable decision supports for scientists by formalizing
their research, strategies, and customization information,
where elements of knowledge, reasoning and contexts are
represented in a uniform way.
      </p>
      <p>Hereafter, the paper is organized in the following way.
Section 2 introduces the four phases of the scientific
workflow lifecycle. Section 3 investigates the possibility
of integrating contextual graphs to the four phases of
scientific workflow lifecycle through a case study in
virtual screening. Section 4 discusses previous works on
workflow flexibility in order to point out what is reusable
while problems remain to support decision-makings in a
flexible scientific workflow system. The general
conclusion and future work in Section 5 closes the paper.</p>
    </sec>
    <sec id="sec-2">
      <title>Scientific Workflow Lifecycle</title>
      <p>
        Scientific workflow lifecycle is coming from workflow
lifecycle
        <xref ref-type="bibr" rid="ref11 ref15 ref16 ref31 ref32">(van de Aalst &amp; van Dongen, 2003; Gil et al.,
2007; Deelman &amp; Chervenak, 2008)</xref>
        . It normally starts
from the scientific hypotheses
        <xref ref-type="bibr" rid="ref18 ref2 ref28 ref35 ref8">(Beaulah et al., 2008;
Tadmor &amp; Tidor, 2005; Claus &amp; Johnson, 2008)</xref>
        to reach
a specific experimental goal, which includes four phases
(see Figure 1):

Workflow Searching: before initiating a brand
new workflow designing, scientists get used to
firstly consult a public SWF repository for
searching previously published workflows
        <xref ref-type="bibr" rid="ref16 ref34">(Wroe et al., 2007)</xref>
        . Once found, it would be
easy to reproduce the pre-existing workflow to
constitute a new one. Workflow searching
results of sharing SWF considered with its
context of use. The more shared SWFs are taken
place in the SWF repository, the more accurate
the searching result would be.
      </p>
      <p>
        Workflow Designing is then initiated for
constructing a workflow model
        <xref ref-type="bibr" rid="ref19 ref22">(Ludascher et al.,
2009)</xref>
        . An abstract workflow model will firstly
be designed, in which scientific tasks and their
execution orders, as well as data and its
dependencies will be described. Secondly, the
phase involves the mapping from abstract
workflow to concrete/executable workflow
where the required resources are selected. By
mapping the workflow instance onto the
available execution resources, an executable
workflow is created for the next phase.
      </p>
      <p>
        Workflow Execution is the enactment of
executable workflow by a workflow engine
        <xref ref-type="bibr" rid="ref11">(Deelman &amp; Chervenak, 2008)</xref>
        , in which input
data is consumed and output data is produced
        <xref ref-type="bibr" rid="ref13 ref29">(Tan et al., 2010)</xref>
        . Workflow engine follows the
order of tasks and their dependencies defined in
the workflow model. It is common to re-execute
the workflow iteratively, considering the
evolutionary changes of workflow model (e.g.,
in workflow design, adding or skipping tasks,
and altering task dependencies) or momentary
changes of a running workflow instance (e.g.,
making local decisions in response to a special
situation, alter decision after analysing observed
intermediate result, reporting exceptional cases).
Workflow Publishing is a post-execution phase
for scientists to interpret workflow results
        <xref ref-type="bibr" rid="ref13 ref19 ref22 ref29">(Tan
et al., 2010; Ludascher et al., 2009)</xref>
        and to
publish the SWF in its context of use
        <xref ref-type="bibr" rid="ref12 ref16 ref34">(Wroe et
al., 2007; Deelman &amp; Gil, 2006)</xref>
        . Depending on
the workflow outcomes and analysis results, the
original hypotheses or experimental goals may
be revised or refined, giving rise to another
round of workflow design/execution in an
iterative manner. Furthermore, it must then be
facilitated to publish the workflow on a
repository, so that SWF could be archived for
re-use later.
      </p>
      <p>Figure 1 shows the relationship among each phases
of scientific workflow lifecycle: hypotheses arrive as
keywords to search pre-existing scientific workflow in
SWF repository; then scientist begin to design the
workflow model and maintain the mapping from an
abstract workflow to a concrete one; workflow execution
phase enacts the workflow model on available resources
according to data and control dependencies; if a change is
encountered, there is an iterative process to re-design the
workflow model as well as re-execute the workflow
instance; if executed successful, scientist will publish the
workflow in the SWF repository for the sake of
reproduction in the research communities.</p>
      <p>
        Current studies
        <xref ref-type="bibr" rid="ref11 ref31 ref32">(van de Aalst &amp; van Dongen, 2003;
Deelman &amp; Chervenak, 2008)</xref>
        on SWF lifecycle
generally result in the weakness to manage the workflow
changes and exceptions. We believe that the major failure
is due to do not make context explicit in the SWF systems.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Make Context Explicit in SWF Lifecycle</title>
      <p>Representing and making context explicit in SWF system
is a challenge that could promote a SWF system more
flexible and enhance its intelligence to facilitate effective
decision-makings. In this section, we discuss managing
contexts explicit throughout the four phases of the SWF
lifecycle, each of which is described using a standard
format including: motivation, realization approach,
example, and discussion.</p>
      <p>
        The example is represented in the Contextual graphs
formalism (Brézillon, 2005) through a case study entitled
“Virtual screening research on avian influenza H5N1
virus”, which aims to find dozens of drug candidates for
H5N1 virus
        <xref ref-type="bibr" rid="ref18 ref35">(He et al., 2008)</xref>
        , by docking 7.7 million
small molecules separately on H5N1 protein
        <xref ref-type="bibr" rid="ref7">(Chen &amp;
Shoichet, 2009)</xref>
        . Figure 2 shows a docking example,
which binds a molecule (ZINC12050767) to a virus
protein (H5N1 PAC Polymerase, known as Bird flu)
through the Dock 6.2 software. Virtual screening could be
considered as millions of docking procedures on the PAC
protein.
      </p>
      <p>The application is not only a time-consuming workflow
application in which intensive computing is expected to
be performed by docking software, but also a very flexible
one that there is no unique solution for each computing
because they vary from each other on selecting docking
software. For example, scientists should identify the
context in which the experiment is organized as a
scientific workflow. According to the current focus and
context, they link a specific resource (e.g., software,
database, and instrument) with the workflow to realize a
specific task. The concept of human-centered process is
particularly relevant in such domains.</p>
      <p>Figure 3 provides the definition of the elements in a
contextual graph (actions, contextual elements, sub-graphs,
activities and temporal branching). A more complete
presentation of this formalism and its implementation can
be found in (Brézillon, 2005).</p>
    </sec>
    <sec id="sec-4">
      <title>Workflow Searching</title>
      <p>Motivation: Before the workflow design, context
behaves as an interface to determine which SWF should
be chosen from a library of SWFs, or a SWF repository.
In this case, a scientist plays a role as a context provider
to guide the choice of the right SWF model according to
current focus and context at hand, so as to largely match
what the scientific hypotheses indicate.</p>
      <p>Realization approach:
 Scientist firstly searches a SWF from a SWF
repository, using keywords which could best
describe their hypotheses and are coherent with the
context at hand.
 If the pre-existing SWF is exactly what they want,
the scientist could skip workflow design phase and
just replace with their own parameters for workflow
execution directly.
 Otherwise if it is similar to their needs, slight
modifications will be carried out shortly in the
workflow design.</p>
      <p>Context graph: virtual screening on protein PAc
1: Is the protein rigid or flexible?
Rigid 2: Activity: perform first rigid screening
Flexible 3: Activity: perform second flexible screening
4: analyze the result</p>
      <p>Example: In Figure 4 (Left), CE1 is a contextual element
(blue circle with number 1). The instantiation of the CE1
(Is the protein rigid or flexible?) leads to the generation
of two scientific workflow instances in Figure 4 (Right):
one is SWF_1 (i.e. value of CE2= “Rigid”), and the other
is SWF_2 (i.e. value of CE2=“Flexible”). In the
application, if scientists want to do a rigid virtual
screening, “rigid” will become a keyword when
performing the searching. Thus, SWF_1 will be selected.
Similarly, SWF_2 is chosen when searching for a
“flexible” screening. As a result, CxGs act as an interface
to make decisions to choose SWF from the SWF
repository.</p>
      <p>Discussion: It is normal to expect nothing from the
repository, scientist could move to the next phase to start
workflow design from scratch.</p>
    </sec>
    <sec id="sec-5">
      <title>Workflow Designing</title>
      <p>Motivation: During workflow design, a certain degree of
freedom is given to the user to execute a workflow by
offering multiple alternative execution paths. Classical
workflow systems reduce the degree of flexibility by
offering powerful design constructs (e.g., start, if/else,
repeat until, parallel execution, end), in which
decisionmaking is always measured by a decision node
accompanying with a numerical value. However, human
decision is so complex that a numerical decision is less
descriptive than a simple question. As a result, we
describe execution paths of workflow in contextual graphs
(CxGs) which model contextualized information (CEs)
and their dependencies. In a contextual graph, the most
appropriate execution path could be selected from those
encoded during the execution time to address the context
at hand.</p>
      <p>Realization approach:
 Firstly, it is necessary to know all the current
instances of the CEs at the moment of the
application of the workflow. An instantiation is the
value that a contextual element can take for a
specific instantiation of the focus at hand.
 Then, a group of contextualized information is
generalized as a set of CEs.
 CEs are then formalized in a contextual graph by
their dependencies. The contextual graph is ready
for the workflow execution, when a SWF instance
corresponds to a specific execution path under the
instantiation of context. In CxG, the execution path
is a sequence of actions, connected by the
instantiation of the selected contextual elements.
Example: In Figure 5, a scientist designs the workflow of
protein preparation as a contextual graph with a set of
contextual elements (CE1 and CE4) and their execution
dependencies. The possible execution paths are controlled
by the value of each contextual element. For example, the
instantiation of CE1 (i.e., value of CE1= “Yes”) and CE4
(i.e., value of CE4= “Yes”) leads to the execution path of
“1→2→4→11→5→6→9”.
Contextual graph: protein preparation (old)
1: Can you find the protein by yourself?</p>
      <p>Yes 2: download it from "Protein Data Bank"</p>
      <p>No 3: ask for help until you get the protein
4: Do you need to do "protein preparation"?</p>
      <p>Yes 11: enter parameters during "protein preparation"
5: Activity: remove unrelated molecules
6: Activity: add hydrogen and charge
9: store the protein prepared in the database</p>
      <p>
        No
Discussion: Describing a completely set of all possible
execution paths during workflow design might be either
undesirable or impossible
        <xref ref-type="bibr" rid="ref18 ref23 ref35">(Schonenberg et al., 2008)</xref>
        . For
example, a certain number of possible execution paths are
unknown before execution. As a result, late-modelling
        <xref ref-type="bibr" rid="ref17">(Han et al., 1998)</xref>
        could enable to make sub-model
dynamically defined during execution.
      </p>
    </sec>
    <sec id="sec-6">
      <title>Workflow Execution</title>
      <p>Motivation: Scientists frequently re-execute the scientific
workflow by adding or ignoring portions of workflow
realized at design time. Context should support the
assembling of SWF components, which must be
recompiled each time when a new context arrives (i.e., a
contextual element takes a new instance). As a result, a
new execution path, or even a new contextual graph will
be inserted or removed when SWF evolves along with its
context.</p>
      <p>Realization approach:
 Each time a new instantiation of a CE occurs, the
contextual graph is re-executed, and the SWF is
recompiled for generating a new SWF instance for
execution.
 If the scientist wants to re-design the workflow by
adding or ignoring portion of SWF, they first stop
the current workflow execution.
 Then, a new group of contextualized information,
including the information representing the workflow
changes, should be generalized as a new set of
contextual elements.
 If a CE with the following activities/actions is added
or ignored, a new contextual graph is produced to
address the new focus.</p>
      <p>Example: Figure 6 is inherited from Figure 5. During the
execution phase, the scientist finds something wrong with
the intermediate result, because he doesn't take into
account whether the protein is flexible or rigid. So he
decides to stop the current execution and re-design the
experiment. As a result, a new contextual element CE7 (Is
it a rigid or flexible screening?) is added. When the value
of CE7 is “flexible screening”, Activity13 (Activity:
optimize the protein) is invoked as a new SWF
component. Furthermore, the contextual graph is updated
along with the change of CEs, and it is necessary to record
such update in a knowledge base for the sake of workflow
sharing, which will be discussed in the next section.
Discussion: It would be a risk of incoherence between the
running workflow instance and results. For example,
when you made a decision two minutes ago and the
contextual graph chooses an execution path for the
workflow. But later, right before the workflow execution,
a new context arrives to urge the adaptation of a new
contextual graph.</p>
    </sec>
    <sec id="sec-7">
      <title>Workflow Publishing</title>
      <p>Motivation: If executed successfully, the scientist then try
to analyse the results generalized by workflow execution.
Type of result analysis includes: 1) evaluate data quality
(e.g., does this result make sense?), 2) examine execution
traces and data dependencies (e.g., which results were
“tainted” by this input dataset?), 3) debug runs (e.g., why
did this step fail?), or 4) simply analyse performance (e.g.,
which steps took the longest time?). After the result
analysis process, it is possible to re-design and re-execute
the workflow iteratively until the new context is addressed.
Incremental knowledge acquisition should be proceeded
to make contextual graph growing to be more efficient.
Furthermore, one of the motivations what scientists are
counting on SWF is the sharing, reproduction,
transformation, and evolution of the “old” SWF to be a
brand “new” one. It is expected to enable sharing of SWFs
according to their contexts of use. In this circumstance,
the context defines the status of the knowledge and also
maintains the relationship between different kinds of
knowledge.</p>
      <p>Realization approach:
 A SWF repository is build up to document
workflows with their contexts of use.
 When workflow is re-executed, the contextual graph
is adapted incrementally to trace the workflow
flexibility. Once a new contextual graph is
generated, add it as a new scenario to SWF
repository.
 Conscientious users might partition the workflow
into coherent fragments and publish them.</p>
      <p>Example: Once a contextual element is modified, a new
CxG is created to address the new focus and its context.
Drawn from Figure 6, Figure 7 shows a new contextual
graph to be added in a SWF repository for future sharing
with other scientists.</p>
      <sec id="sec-7-1">
        <title>Contextual graph: protein preparation (new)</title>
        <p>1: Can you find the protein by yourself?</p>
        <p>Yes 2: Download it from "Protein Data Bank"</p>
        <p>No 3: Ask for help until you get the protein
4: Do you need to do "protein preparation"?</p>
        <p>Yes 11: Enter parameters during "protein preparation"
5: Activity: remove unrelated molecules
6: Activity: add hydrogen and charge
7: Is it a rigid or flexible screening?</p>
        <p>Rigid</p>
        <p>Flexible 13: Activity: optimize the protein
9: store the protein prepared in the database</p>
        <p>No
Discussion: Encourage sharing of scientific workflow
with its context, would make it as a complementary of
paper-based publications. In such a case, scientific
workflow would be archived along with paper-based
publications. However, the quality of sharing data and
workflow becomes a new question.</p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>Summary</title>
      <p>Contextual graphs are a formalism of representation
allowing the description of decision making in which
context influences the line of reasoning (e.g. choice of a
method for accomplishing a task). The advantage of
contextual graphs relies on that: (i) CxGs provide
naturally learning and explanation capabilities in the
system; and (ii) CxGs allow a learning process for
integrating new situations by assimilation and
accommodation. In short, the notion of context is made
explicit during the four phases of scientific workflow
lifecycle by contextual graphs. Contextual Graphs
formalism has been already used in different domains
such as medicine, incident management on a subway line,
road sign interpretation by a driver, computer security,
psychology, cognitive ergonomics, etc.</p>
    </sec>
    <sec id="sec-9">
      <title>Related Works</title>
      <p>
        Various approaches, such as BPEL
        <xref ref-type="bibr" rid="ref18 ref35">(Zhang et al., 2008)</xref>
        ,
UML
        <xref ref-type="bibr" rid="ref9">(Courtney, 2001)</xref>
        , Petri-net
        <xref ref-type="bibr" rid="ref27">(Tabak et al., 1985)</xref>
        , are
proposed to address the issue of workflow flexibility by
getting user involved in representing decision-making.
Applications
        <xref ref-type="bibr" rid="ref22 ref30">(Yu et al., 2005; Hey et al., 2009)</xref>
        have
proven the significance of current systems to handle
numerical decision-making as control-flow functions,
such as “wait 30 second, and then proceed the next task”,
“if the value is greater than 5 then execute the task_A, else
execute the task_B”. However, it becomes an obstacle to
manage the common but important decisions, such as “are
you satisfied with the result?” and “do you need to do the
protein preparation again”, which is more comprehensive
for scientists.
      </p>
      <sec id="sec-9-1">
        <title>Approach</title>
      </sec>
      <sec id="sec-9-2">
        <title>BPEL (Zhang 2008)</title>
      </sec>
      <sec id="sec-9-3">
        <title>Petri-net (Tabak 1985) et</title>
        <p>et</p>
        <p>
          Context has been considered as a key element to support
decision making in human centered processes for a long
time (
          <xref ref-type="bibr" rid="ref4">Brézillon, 2003</xref>
          ;
          <xref ref-type="bibr" rid="ref6">Brézillon, 2010</xref>
          ). To address a
coherent formalism of context,
          <xref ref-type="bibr" rid="ref25">Sowa (1984)</xref>
          proposes
conceptual graphs with their mechanisms of aggregation
and expansion. Then,
          <xref ref-type="bibr" rid="ref26">Sowa (2000)</xref>
          introduces a way to
manage the context in conceptual graphs.
          <xref ref-type="bibr" rid="ref5">Brézillon (2005)</xref>
          presents a simpler formalism of Contextual Graphs (CxGs)
for representing context. Compared with other approaches,
CxGs formalism is good at describing decision making in
which context influences the line of reasoning.
        </p>
        <p>
          In the implementation level, a number of applications
exist for preparing formal representation of context.
          <xref ref-type="bibr" rid="ref20">McCarthy (1993)</xref>
          formalizes contexts as formal objects,
and the basic relation is ist(c,p). It asserts that the
proposition p is true in the context c, where c is meant to
capture all that is not explicit in p that is required to make
p a meaningful statement representing what it is intended
to state. Formulas ist(c,p) are always asserted within a
context, i.e., something like ist(c', ist(c,p)): c': ist (c, p).
          <xref ref-type="bibr" rid="ref24">Sharma (1995)</xref>
          gives a list of desirable properties for
contexts in a formal language and distinguishes four
approaches for formalizing contexts: (1) incrementing
arity; (2) variation on implication; (3) modal operator
forms; and (4) syntactic treatment. Based on McCarthy's
work on context logic,
          <xref ref-type="bibr" rid="ref14">Farquhar et al. (1995)</xref>
          present an
approach to integrating disparate heterogeneous
information sources.
        </p>
        <p>
          In Table 1, we compare various approaches to model
decision making in workflow, as implementation of
“Exclusive Choice workflow pattern”
          <xref ref-type="bibr" rid="ref31 ref32">(van de Aalst &amp;
Hofstede, 2003)</xref>
          .
        </p>
        <p>By comparison, Contextual Graphs plays an equivalent
role to other approaches for representing decision making.
Furthermore, the advantage of contextual graphs embraces:
(1) multiple representations of decision making, not only
with a numerical value, but also with any kind of answers
to questions to get scientists involved in a local
decisionmaking process; (2) it is directly readable (e.g. generally
something as “If the contextual element C has the value
V1, thus use method M1, and with the value V2 use
method M2”); and (3) it is very easy to have an
incremental growth of a contextual graph by addition of
contextual elements and branches for representing
practices developed by users and not yet known by the
system.</p>
      </sec>
    </sec>
    <sec id="sec-10">
      <title>Conclusion</title>
      <p>The human-centered processes must be considered at a
global level to deal with the user, the task at hand, and the
context in which the task is accomplished. Take a flexible
scientific workflow for example, scientists could not
handle the transferring from hypotheses to discovery in
the SWF system without taking into account the context.</p>
      <p>We propose a solution to introduce contextual graphs in
the four phases of SWF lifecycle, each of which is
expressed in a standard format, including a concrete
example in the area of virtual screening. In our application
on virtual screening, we use contextual graphs to model
the decision making processes of scientists as a uniform
representation of knowledge, reasoning, and contexts. As
a result, scientists are closely involved in each phase of
SWF lifecycle to maximize the decision support received
from the system.</p>
      <p>We believe that all of data, information and knowledge
should be invoked, assembled, organized, structured and
situated according to the given focus, and finally be
formulated as the chunk of professional knowledge for
scientists to maintain their research sustainability.</p>
      <p>The extension of our work includes the development of
a prototype interface between scientific workflow system
and contextual graphs. Representing and making
“context” explicit in SWF system by contextual graph
would enhance workflow flexibility by formalizing
scientists' research, strategies, and customization
information, where elements of knowledge, reasoning and
contexts are represented in a uniform way.</p>
    </sec>
    <sec id="sec-11">
      <title>Acknowledgments</title>
      <p>This work is supported by grants from National Natural
Science Foundation of China (90912003, 60773108,
90812001, 61011130212), Centre national de la
recherche scientifique (Researcher exchange project with
NSFC 2010), and Région Ile-de-France (CP10-201), and
by scholarships from China Scholarship Council
(2008618047), and Égide (690544G).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Altintas</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , et al. (
          <year>2004</year>
          ),
          <article-title>Kepler: an extensible system for design and execution of scientific workflows</article-title>
          .
          <source>Proceedings of 16th International Conference on Scientific and Statistical Database Management</source>
          (pp.
          <fpage>423</fpage>
          -
          <lpage>424</lpage>
          ). Danvers, MA: IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Beaulah</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Correll</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Munro</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheldon</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Addressing informatics challenges in Translational Research with workflow technology</article-title>
          .
          <source>Drug discovery today</source>
          ,
          <volume>13</volume>
          (
          <fpage>17</fpage>
          -
          <lpage>18</lpage>
          ),
          <fpage>771</fpage>
          -
          <lpage>777</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>Brézillon P.</given-names>
            , and
            <surname>Pomerol</surname>
          </string-name>
          <string-name>
            <surname>J.C.</surname>
          </string-name>
          (
          <year>1999</year>
          ).
          <article-title>Contextual knowledge sharing and cooperation in intelligent assistant systems</article-title>
          ,
          <source>Le Travail Humain</source>
          ,
          <volume>62</volume>
          (
          <issue>3</issue>
          ),
          <fpage>223</fpage>
          -
          <lpage>246</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Brézillon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          (
          <year>2003</year>
          ).
          <article-title>Focusing on Context in HumanCentered Computing</article-title>
          .
          <source>IEEE Intelligent Systems</source>
          ,
          <volume>3</volume>
          (
          <issue>18</issue>
          ),
          <fpage>62</fpage>
          -
          <lpage>66</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Brézillon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>Task-realization models in contextual graphs</article-title>
          . In Dey,
          <string-name>
            <given-names>A.K.</given-names>
            ,
            <surname>Kokinov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Leake</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            , and
            <surname>Turner</surname>
          </string-name>
          , R. (Eds),
          <source>Proceedings of Modeling and Using Context: 5th International and Interdisciplinary Conference</source>
          (pp.
          <fpage>55</fpage>
          -
          <lpage>68</lpage>
          ). Berlin :Springer Verlag.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Brézillon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Pomerol</surname>
          </string-name>
          , J.-Ch. (
          <year>2010</year>
          ).
          <article-title>Framing decision making at two levels</article-title>
          . In Respicio, A.,
          <string-name>
            <given-names>F.</given-names>
            <surname>Adam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Phillips-Wren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Teixeira</surname>
          </string-name>
          &amp; J.
          <string-name>
            <surname>Telhada</surname>
          </string-name>
          (Eds.),
          <article-title>Bridging the Socio-Technica Gap in Decision Support Systems- Challenges for the next Decade</article-title>
          . Amsterdam: IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Shoichet</surname>
            ,
            <given-names>BK.</given-names>
          </string-name>
          (
          <year>2009</year>
          ).
          <article-title>Molecular docking and ligand specificity in fragment-based inhibitor discovery</article-title>
          ,
          <source>Nature Chemical Biology</source>
          ,
          <volume>5</volume>
          (
          <issue>5</issue>
          ),
          <fpage>358</fpage>
          -
          <lpage>364</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>Claus</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , and Johnson,
          <string-name>
            <surname>S.</surname>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Grid computing in large pharmaceutical molecular modeling</article-title>
          ,
          <source>Drug discovery today</source>
          ,
          <volume>13</volume>
          (
          <fpage>13</fpage>
          -
          <lpage>14</lpage>
          ),
          <fpage>578</fpage>
          -
          <lpage>583</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>Courtney</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          (
          <year>2001</year>
          ).
          <article-title>Decision making and knowledge management in inquiring organizations: toward a new decision-making paradigm for DSS</article-title>
          . Decision Support
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <string-name>
            <surname>Systems</surname>
          </string-name>
          ,
          <volume>31</volume>
          (
          <issue>1</issue>
          ),
          <fpage>17</fpage>
          -
          <lpage>38</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>Deelman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Chervenak</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Data Management Challenges of Data-Intensive Scientific Workflows</article-title>
          .
          <source>Proceedings of the 8th IEEE International Symposium on Cluster Computing and the Grid</source>
          (pp.
          <fpage>687</fpage>
          -
          <lpage>692</lpage>
          ), Lyon: IEEE CS Press.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <surname>Deelman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gil</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          (
          <year>2006</year>
          ).
          <article-title>Managing large-scale scientific workflows in distributed environments: Experiences and challenges</article-title>
          .
          <source>Proceedings of the Second IEEE International Conference on e-Science and Grid Computing</source>
          (pp.
          <fpage>144</fpage>
          ), Washington: IEEE Computer Society.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>Fan</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          et al. (
          <year>2010</year>
          ).
          <article-title>Context-oriented scientific workflow system and its application in virtual screening</article-title>
          . In Respicio,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Adam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Phillips-Wren</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Teixeira</surname>
          </string-name>
          <string-name>
            <given-names>C.</given-names>
            , and
            <surname>Telhada</surname>
          </string-name>
          <string-name>
            <surname>J</surname>
          </string-name>
          . (Eds.).
          <article-title>Bridging the SocioTechnical Gap in Decision Support SystemsChallenges for the next Decade (pp</article-title>
          .
          <fpage>335</fpage>
          -
          <lpage>345</lpage>
          ). Amsterdam: IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Farquhar</surname>
            ,
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dappert</surname>
            ,
            <given-names>J</given-names>
          </string-name>
          , Fikes,
          <string-name>
            <surname>R</surname>
          </string-name>
          and Pratt,
          <string-name>
            <surname>W.</surname>
          </string-name>
          (
          <year>1995</year>
          ).
          <article-title>Integrating information sources using context logic (Tech. Rep</article-title>
          . KSL-
          <volume>95</volume>
          -12). Palo Alto, California: Stanford University, Knowledge Systems Laboratories.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <string-name>
            <surname>Gil</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Deelman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ellisman</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fahringer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fox</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gannon</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Livny</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Myers</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2007</year>
          ).
          <article-title>Examining the Challenges of Scientific Workflows</article-title>
          . Computer,
          <volume>12</volume>
          (
          <issue>40</issue>
          ),
          <fpage>24</fpage>
          -
          <lpage>32</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <string-name>
            <surname>Goble</surname>
          </string-name>
          , CA., et al. (
          <year>2007</year>
          ).
          <article-title>myExperiment: social networking for workflow-using e-scientists</article-title>
          .
          <source>Proceedings of 2nd workshop on Workflows in support of large-scale science</source>
          (pp.
          <fpage>1</fpage>
          -
          <lpage>2</lpage>
          ). NY: ACM.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <surname>Han</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bussler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>1998</year>
          ).
          <article-title>A Taxonomy of Adaptive Workflow Management</article-title>
          .
          <source>In Workshop of the 1998 ACM Conference on Computer Supported Cooperative Work</source>
          . Seattle, Washington, USA.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <string-name>
            <surname>He</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          , et al. (
          <year>2008</year>
          ).
          <article-title>Crystal structure of the polymerase PA(C)-PB1(N) complex from an avian influenza H5N1 virus</article-title>
          .
          <source>Nature</source>
          ,
          <volume>454</volume>
          ,
          <fpage>1123</fpage>
          -
          <lpage>1126</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <surname>Ludascher</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altintas</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bowaers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cummings</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Critchlow</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Deelman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De</surname>
          </string-name>
          , R.D.,
          <string-name>
            <surname>Freire</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klasky</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McPhillips</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Podhorszki</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taylor</surname>
          </string-name>
          , I., and
          <string-name>
            <surname>Vouk</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2009</year>
          ).
          <article-title>Scientific process automation and workflow management</article-title>
          . In Shoshani, A., and Rotem D. (Eds),
          <source>Scientific Data Management: Challenges</source>
          ,
          <string-name>
            <given-names>Existing</given-names>
            <surname>Technology</surname>
          </string-name>
          , and
          <string-name>
            <surname>Deployment</surname>
          </string-name>
          , Computational Science Series, chapter
          <volume>13</volume>
          .
          <string-name>
            <surname>Chapman</surname>
          </string-name>
          &amp; Hall/CRC.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <surname>McCarthy</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>1993</year>
          ).
          <article-title>Notes on formalizing context</article-title>
          . In Bajcsy, R. (Ed.),
          <source>Proceedings of the Thirteenth International Joint Conference on Artificial Intelligence</source>
          (pp.
          <fpage>555</fpage>
          -
          <lpage>560</lpage>
          ). San Mateo, California: Morgan Kaufmann.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <string-name>
            <surname>Roache</surname>
            ,
            <given-names>P.J.</given-names>
          </string-name>
          (
          <year>1998</year>
          ).
          <article-title>Verification and validation in computational science and engineering</article-title>
          . Albuquerque, NM: Hermosa Publishers.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <string-name>
            <surname>Hey</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , et al. (
          <year>2009</year>
          ).
          <article-title>The Fourth Paradigm: DataIntensive Scientific Discovery</article-title>
          . Redmond, Washington: Microsoft research.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          <string-name>
            <surname>Schonenberg</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mans</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Russell</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mulyar</surname>
          </string-name>
          , N.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Process flexibility: A survey of contemporary approaches</article-title>
          . In: Dietz J.,
          <string-name>
            <surname>Albani</surname>
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Barjis</surname>
            <given-names>J</given-names>
          </string-name>
          . (Eds),
          <source>Advances in enterprise engineering I</source>
          . Berlin: Springer-Verlag.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          <string-name>
            <surname>Sharma</surname>
            ,
            <given-names>N</given-names>
          </string-name>
          (
          <year>1995</year>
          ).
          <article-title>On formalising and reasoning with contexts</article-title>
          (
          <source>Tech. Rep. 352)</source>
          . Brisbane, Queensland: University of Queensland, Department of Computer Science.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          <string-name>
            <surname>Sowa</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          (
          <year>1984</year>
          ).
          <source>Conceptual Structures: Information Processing in Mind and Machine</source>
          . Reading, MA: Addison Wesley Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          <string-name>
            <surname>Sowa</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          (
          <year>2000</year>
          ).
          <article-title>Knowledge Representation: Logical, Philosophical, and Computational Foundations</article-title>
          . Pacific Grove, CA: Brooks Cole Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <string-name>
            <surname>Tabak</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Levis</surname>
            ,
            <given-names>A.H.</given-names>
          </string-name>
          (
          <year>1985</year>
          ).
          <article-title>Petri Net Representation of Decision Models</article-title>
          .
          <source>IEEE Transactions on Systems- Man and Cybernetics</source>
          ,
          <volume>15</volume>
          (
          <issue>6</issue>
          ),
          <fpage>812</fpage>
          -
          <lpage>818</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          <string-name>
            <surname>Tadmor</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Tidor</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>Interdisciplinary research and education at the biology-engineeringcomputer science interface: a perspective (reprinted article)</article-title>
          ,
          <source>Drug discovery today</source>
          ,
          <volume>10</volume>
          (
          <fpage>23</fpage>
          -
          <lpage>24</lpage>
          ),
          <fpage>1706</fpage>
          -
          <lpage>1712</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          <string-name>
            <surname>Tan</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Missier</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Foster</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Madduri</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Roure</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2010</year>
          ).
          <article-title>A comparison of using Taverna and BPEL in building scientific workflows: the case of caGrid, Concurrency</article-title>
          and
          <source>Computation: Practice and Experience</source>
          ,
          <volume>22</volume>
          (
          <issue>9</issue>
          ),
          <fpage>1098</fpage>
          -
          <lpage>1117</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Buyya</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>A Taxonomy of Scientific Workflow Systems for Grid Computing</article-title>
          . In special issue on Scientific Workflows,
          <source>SIGMOD Record</source>
          ,
          <volume>34</volume>
          (
          <issue>3</issue>
          ),
          <fpage>44</fpage>
          -
          <lpage>49</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          <string-name>
            <surname>van de Aalst</surname>
          </string-name>
          , W.M.P.,
          <string-name>
            <surname>van Dongen</surname>
            ,
            <given-names>B.F.</given-names>
          </string-name>
          , et al. (
          <year>2003</year>
          ).
          <article-title>Workflow Mining: A Survey of Issues and Approaches</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          ,
          <volume>47</volume>
          ,
          <fpage>237</fpage>
          -
          <lpage>267</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          <string-name>
            <surname>van de Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hofstede</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , et al. (
          <year>2003</year>
          ).
          <source>Workflow Patterns. Distributed and Parallel Databases</source>
          .
          <volume>14</volume>
          (
          <issue>3</issue>
          ),
          <fpage>5</fpage>
          -
          <lpage>51</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Grunbauer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>Case Handling: A New Paradigm for Business Process Support</article-title>
          .
          <source>Data and Knowledge Engineering</source>
          <volume>53</volume>
          (
          <issue>2</issue>
          ),
          <fpage>129</fpage>
          -
          <lpage>162</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          <string-name>
            <surname>Wroe</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goble</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goderis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          et al. (
          <year>2007</year>
          ).
          <article-title>Recycling workflows and services through discovery and reuse</article-title>
          .
          <source>Concurrency and Computation: Practice and Experience</source>
          ,
          <volume>19</volume>
          (
          <issue>2</issue>
          ),
          <fpage>181</fpage>
          -
          <lpage>194</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          <string-name>
            <surname>Zhang</surname>
          </string-name>
          , H., et al. (
          <year>2008</year>
          ).
          <source>Extending BPEL2</source>
          .
          <article-title>0 for GridBased Scientific Workflow Systems</article-title>
          ,
          <source>Proceedings of IEEE Asia-Pacific Services Computing Conference</source>
          (pp.
          <fpage>757</fpage>
          -
          <lpage>762</lpage>
          ), Yilan: IEEE CS press.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>