<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>CookingCAKE: A Framework for the adaptation of cooking recipes represented as workflows</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gilbert Mu¨ller</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ralph Bergmann</string-name>
          <email>bergmann@uni-trier.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Business Information Systems II University of Trier 54286 Trier</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>221</fpage>
      <lpage>232</lpage>
      <abstract>
        <p>This paper presents CookingCAKE, a framework for the adaptation of cooking recipes represented as workflows. CookingCAKE integrates and combines several workflow adaptation approaches applied in process-oriented case based reasoning (POCBR) in a single adaptation framework, thus providing a capable tool for the adaptation of cooking recipes. The available case base of cooking workflows is analyzed to generate adaptation knowledge which is used to adapt a recipe regarding restrictions and resources, which the user may define for the preparation of a dish.</p>
      </abstract>
      <kwd-group>
        <kwd>recipe adaptation</kwd>
        <kwd>workflow adaptation</kwd>
        <kwd>workflows</kwd>
        <kwd>process-oriented case based reasoning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Even after more than 30 years of research in CBR, adaptation is still a major
challenge. This also applies to the adaptation of cooking recipes. Direct processing of
textual recipes is however almost not feasible. Thus, they are usually transformed to
structured cases, e.g., workflows [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. In Process-Oriented Case-Based Reasoning (POCBR)
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], workflow adaptation is also an important research topic.
      </p>
      <p>
        Existing methods for adaptation in CBR can be roughly classified into
transformational, compositional, and generative adaptation [
        <xref ref-type="bibr" rid="ref21 ref9">21,9</xref>
        ]. While transformational
adaptation relies on adaptations executed in a kind of a rule-based manner, generative
adaptation demands general domain knowledge appropriate for an automated from scratch
problem solver. An approach for transformational adaptation of workflows was
presented by Minor et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Compositional adaptation usually means that several cases
are used during adaptation, incorporating transformational or generative adaptation
methods involving adaptation knowledge. Dufour-Lussier et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], for example,
presented such a compositional adaptation approach. However, the different adaptation
approaches come along with respective advantages and disadvantages. Thus, we expect
that the integration and combination of several adaptation approaches can significantly
improve the overall adaptation capability of a CBR system by overcoming some of the
disadvantages of each individual approach.
      </p>
      <p>Copyright © 2015 for this paper by its authors. Copying permitted for private and
academic purposes. In Proceedings of the ICCBR 2015 Workshops. Frankfurt, Germany.</p>
      <p>In this paper, we present the next evolutionary step of your CookingCAKE system,
which is the integration of three adaptation approaches developed within our
previous research. In particular, we present a novel integration of adaptation by
generalization and specialization, compositional adaptation, and transformational adaptation
in POCBR. To achieve this, CookingCAKE analyzes the case base of cooking
workflows generating an extensive adaptation knowledge base using several adaptation
approaches. This knowledge is then used to adapt workflows according to the
requirements and resources given in a current adaptation scenario. While this paper presents
novel ideas and positions on adaptation, the open challenge is addressed. In addition, we
present our examples as well as a comprehensive use case from the sandwich challenge,
thus this challenge is addressed as well.</p>
      <p>The next section introduces cooking workflows followed by a summary section
sketching the used adaptation approaches from our previous research (see Sect. 3).
Section 4 describes the novel integration of the approaches, including the generation of
adaptation knowledge as well as the integrated adaptation itself. Next, Sect. 5 provides
details on how the Computer Cooking Contest 2015 sandwich challenge is addressed.
Finally, the paper wraps up by discussing potential future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Cooking Workflows</title>
      <p>
        In our approach a cooking recipe is represented as a workflow describing the process
to prepare a particular dish [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] (see Fig. 1). Cooking workflows consist of a set of
preparation steps (also called tasks) and a set of ingredients (also called data items)
shared between its tasks. Further, control-flow blocks may be used that represent
either sequences, parallel (AND), alternative (XOR), or repeated execution (LOOPs) of
preparation steps. These control-flow blocks may be nested but not interleaved, thus
we consider block-oriented workflows only. This ensures the syntactic correctness of
the workflow following the correctness-by-construction principle [
        <xref ref-type="bibr" rid="ref17 ref3">17,3</xref>
        ], e.g., that the
workflow has one start node and one end node. Such workflows are referred to as
consistent workflows. Tasks and control-flow blocks are linked by control-flow edges defining
italian
mayonaise seasoning mustard
      </p>
      <p>sauce
grate
+
mix
slice
add
open
data- ow edge control- ow edge control- ow node data node task node
Fig. 1. Example of a block-oriented cooking workflow
sandwich</p>
      <p>dish
+ spread
add
layer
sprinkle</p>
      <p>bake
baguette
salami
cucumber
cheese
the execution order. This forms the control-flow. Tasks, data items, and relationships
(represented by data-flow edges) between the two of them form the data flow. An
example block-oriented cooking workflow for a sandwich recipe is illustrated in Fig. 1.
2.1</p>
      <sec id="sec-2-1">
        <title>Semantic Workflows and Semantic Workflow Similarity</title>
        <p>
          To support retrieval and adaptation of workflows, the individual workflow elements are
annotated with ontological information, thus leading to a semantic workflow [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ].
CookingCAKE uses a taxonomy of ingredients to define the semantics of data items and
a taxonomy of preparation steps to define the semantics of tasks. These taxonomies
are employed for the similarity assessment between tasks and data items. An example
ingredient taxonomy is given in Fig. 2. A taxonomy is ordered by terms that are
either a generalization or a specialization of a specific other term within the taxonomy,
i.e., an inner node represents a generalized term that stands for the set of most
specific terms below it. For example, the generalized term vegeterian stands for the set
fpotatoes; rice; noodlesg. Further on in the paper we use inner nodes in generalized
workflows to represent that an arbitrary ingredient from the set of its specializations can
be chosen.
        </p>
        <p>ingre(ψdi)ents0.01
vegeterian0.1</p>
        <p>non vegeterian0.1
potatoes rice noodles
(ψ) (ψ) (ψ)
... side dis0h.5vegetab...le0s.6 liqui...d0s.3 seafoo...d0.7 meat0.6
beef pork chicken turkey
(ψ) (ψ) (ψ) (ψ)</p>
        <p>
          In our previous work, we developed a semantic similarity measure for workflows
that enables the similarity assessment of a case workflow Wc w.r.t. a query workflow
Wq [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], i.e. sim(Wq; Wc). Each query workflow element xq 2 Wq is mapped by the
function m : Wq ! Wc to an element of the case workflow xc 2 Wc, i.e., xc = m(xq).
The mapping is used to estimate the similarity between the two workflow elements
utilizing the taxonomy, i.e., sim(xq; xc). The similarity of preparation steps or ingredients
reflects the closeness in the taxonomy and further regards the level of the taxonomic
elements. In general, the similarity is defined by the attached similarity value of the least
common anchestor, e.g., sim(beef; pork) = 0:6. If a more general query element such
as “meat” is compared with a specific element below it, such as “pork”, the similarity
value is 1. This ensures that if the query asks for a recipe containing meat, any recipe
workflow from the case base containing any kind of meat is considered highly similar.
All the similarity values of the mappings are then aggregated to estimate an overall
workflow similarity.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Querying Semantic Workflows</title>
        <p>
          In order to guide the retrieval and adaptation of workflows a query is defined by the
user. CookingCAKE uses POQL (Query Language for Process-Oriented Case-Based
Reasoning) [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] to capture desired and undesired ingredients or preparation steps of a
cooking workflow as a query q. The definition of preparation steps is useful as certain
tools might not be available or their usage is desired (e.g. oven). Let qd = fx1; : : : ; xng
be a set of desired ingredients or preparation steps and qu = fy1; : : : ; yng be a set of
undesired ingredients or preparation steps. A query q is then defined as (x1 ^ : : : ^ x2) ^
:y1^: : :^:yn. POQL also enables to capture generalized terms, i.e., if a vegeterian dish
is desired, this can be defined by :meat. The query q is then used to guide retrieval,
i.e., to search for a workflow which at best does not contain any undesired element
and contains all desired elements. Based on the query q the unmatched elements can
be identified, enabling estimating the elements to be deleted or added to the retrieved
workflow during the subsequent adaptation stage. The similarity between the query
and a workflow W is defined as the similarity between the desired ingredients and the
workflow W and the number of undesired ingredients not contained in W according to
the semantic similarity measure [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] in relation to the size of the query:
sim(q; W ) =
        </p>
        <p>Px2qd sim(x; m(x)) + jfy 2 qujsim(y; m(y)) 6= 1gj
jqdj + jquj
(1)</p>
        <p>Hence, please note that similar desired ingredients or preparation steps increase the
similarity while similar undesired ingredients or preparation steps do not reduce the
similarity between the POQL query and the workflow.</p>
        <p>In general, POQL is even more expressive and can, for example, capture time
restrictions on preparation steps or that a certain ingredient should or should not be
processed in a particular manner (e.g. do or do not bake vegetables). However, for the sake
of simplicity we assume a set of desired and undesired ingredients or preparation steps
only in the following sections.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Adaptation Approaches</title>
      <p>This section summarizes the used adaptation approaches within the CookingCAKE
framework.
3.1</p>
      <sec id="sec-3-1">
        <title>Adaptation by Generalization and Specialization of Workflows</title>
        <p>
          A generalized workflow [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] is a workflow containing generalized terms from a
taxonomy (see Sec. 2.1), each of them representing multiple specialized ingredients or
preparation steps. Thus, the generalized workflow represents a set of specialized workflows.
Figure 3 illustrates an example for a generalization of the example workflow given in
Fig. 1. Here, any preparation step that chops the cheese and any sort of meat could
potentially be used. Such generalized workflows can be learned by comparing
similar workflows from the case base. A workflow is generalized by generalizing terms if
similar workflows from the case base contain several specializations of this generalized
term. It is assumed that if similar workflows contain the terms fbeef; chicken; porkg,
for example, these workflows can be generalized to contain any kind of meat. Likewise
makesmall represents all possible cooking steps reducing ingredients to small pieces.
sauce
mix
slice
add
open
add
layer
        </p>
        <p>bake</p>
        <p>
          Adaptation is supported by specializing a workflow according to the POQL query
q. Lets assume the generalized workflow contains the term meat and the query defines
that beef is desired, the generalized element can be specialized according to beef . Thus,
specialization enables adapting a workflow according to the POQL query.
The idea of compositional adaptation by workflow streams [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] is that each workflow
can be decomposed into meaningful sub-components or snippets [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. A sandwich
workflow, for example, prepares the sauce and the toppings in order to produce the entire
sandwich dish. These sub-components represented as partial workflows are referred to
as workflow streams. Workflow streams can be identified by collecting all data-flow
connected tasks1 until a new data item such as sandwich sauce is created. An
example for a workflow stream for the example workflow (see Fig. 1) is given in Figure 4
describing how to place toppings on the sandwich. To compute the adaptation
knowledge, all workflow streams that can be found in the workflows within the case base are
extracted.
        </p>
        <p>The basic idea for compositional adaptation is, to adapt a workflow by using the
workflow streams of other workflows that produce the same data item in a different
manner, e.g., with other tasks or data. In the sandwich domain, for example, toppings,
sauces, or preparation steps can be replaced. However, only workflow streams are
substitutable if they produce the same data and consume identical data nodes. This ensures
that replacing an arbitrary stream does not violate the semantic correctness of the
workflow.
1 If a task consumes a data item produced by another one, both tasks are dataflow-connected.
grate
slice
add
layer</p>
        <p>
          bake
salami cucumber cheese
The workflow adaptation operators [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] are specified by two workflow sub-graphs
called streamlets, one representing a workflow fraction to be deleted and one
representing a workflow fraction to be added. Such operators can be learned from the case base
by comparing two workflows and employ the difference between the two workflows in
order to generate workflow adaptation operators. The example adaptation operator in
Fig. 5 describes that mayonnaise can be replaced by tomatoes. This also enforces that
tasks have to be changed as well, because the combine task also has to be exchanged
for a chop task.
        </p>
        <p>italian
seasoning
combine</p>
        <p>add
deletion streamlet oD
mayonnaise
mustard
sauce
tomatos</p>
        <p>italian
seasoning</p>
        <p>sauce
chop</p>
        <p>mix
insertion streamlet oI</p>
        <p>The basic idea for operational adaptation is that chains of adaptation operators are
applied W !o1 W1 !o2 : : : !on Wn to the retrieved workflow W , thereby transforming
the workflow W to an adapted workflow Wn. This process can be considered a search
process towards an optimal solution w.r.t. the query. Hence, streamlets are removed,
inserted, or replaced to transform the workflow according to the query.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>CookingCAKE Framework</title>
      <p>We now present the CookingCAKE framework which automatically generates
adaptation knowledge using various adaptation approaches applied in POCBR (see Sect. 4.1).
Based on this knowledge workflow adaptation is supported regarding a POQL query
defining the requirements and resources on the workflow adaptation (see Sect. 4.2).
4.1</p>
      <sec id="sec-4-1">
        <title>Generation of adaptation knowledge</title>
        <p>
          As the acquisition of adaptation knowledge is an instance of the traditional knowledge
acquisition bottleneck [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], CookingCAKE automatically generates adaptation
knowledge based on the workflows contained in the case base (see Fig. 6). First, the case base
and thus each workflow is generalized applying the method described in section 3.1.
From this generalized case base further adaptation knowledge, i.e., workflow streams
and adaptation rules (see Sect. 3), is automatically generated. As the adaptation
knowledge is acquired based on the generalized case base, the adaptation knowledge itself is
also generalized. This increases the adaptability for the entire adaptation procedure.
        </p>
        <p>generalization
casebase
generalized
casebase
work ow adaptation
streams operators
adaptationknowledge</p>
        <p>The generated adaptation knowledge can then be used to adapt a workflow whenever
a query occurs. Further details on this procedure are explained in the next section.
Whenever a POQL query occurs CookingCAKE searches for the workflow that best
matches the given query within the generalized case base (see Fig. 7). However, it may
happen that not all resources or requirements defined in the query are fulfilled by this
workflow. Thus, workflow adaptation is required. For this purpose the workflow
adaptation approaches presented in Sect. 3 are subsequently applied, still regarding the defined
query. After this procedure, the adapted workflow still has to be specialized according
to the query if it contains generalized elements. Therefore, CookingCAKE uses the
specialization method presented in Sect. 3.1.</p>
        <p>
          In order to ensure scalability of the presented approach for large case bases or large
sets of adaptation knowledge, CookingCAKE supports a cluster-based retrieval [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] for
workflows as well as for adaptation knowledge.
5
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>CCC Sandwich Challenge</title>
      <p>In order to address the sandwich challenge a case base of 61 sandwich recipe
workflows was created. The workflows were manually modelled based on sandwich recipes
found on WikiTaaable2 and further Internet sources. To enable similarity computations
between the workflows, a modified version of the ingredient and cooking step ontology
provided by WikiTaaable was employed. More precisely, multiple inheritance was
resolved as CookingCAKE so far is only able to handle taxonomies (single inheritance).
Further, the generalized terms of the taxonomies have been manually annotated with
similarity values (see Sect. 2.1).</p>
      <p>A running demo of CookingCAKE for the sandwich challenge is available under
http://cookingCAKE.wi2.uni-trier.de3 (see Fig. 8). The query of CookingCAKE
contains desired and undesired ingredients as well as desired and undesired preparation
2 http://wikitaaable.loria.fr
3 Please note that CookingCAKE is still under improvement until the CCC’15
steps. An example query ( http://cookingCAKE.wi2.uni-trier.de?d=cherry%20tomato|salmon&amp;u=
cheese), generates a salmon and cherry tomato recipe without using any kind of cheese.
Please note, that CookingCAKE does not necessarily fulfill the given query, it rather
tries to fulfill the query as much as possible but does not execute any adaptations if no
adaptation knowledge is present in order to remain the quality of the sandwich recipe.
Consequently, if e.g. edam cheese is desired among other ingredients possibly a recipe
with gouda cheese is returned if that is more suitable concerning the other desired
desired ingredients. Further, undesired ingredients might be contained or a desired
ingredient might not be contained, if that seems to be inappropriate according to the
remaining ingredients given in the query. In general, cooking steps are adapted, if particular
changed ingredients may require a different preparation of the particular dish.</p>
      <p>After the definition of a query, CookingCAKE searches for the workflow in the
case base that already best matches the given query based on the similarity value (see
Sect. 2.2). If the query can not be fulfilled, adaptation is required. In this case, the
entire adaptation procedure presented in Sect. 4.2 is used to adapt the sandwich recipe
according to a query.</p>
      <p>As a result, CookingCAKE can also print a detailed XML-File describing the used
original case based recipe as well as the adapted recipe according to the query.
Further, information is provided on which ingredients are removed from and added to the
original workflow during adaptation.</p>
      <p>Additionally, CookingCAKE also provides a textual view of the solution (see Fig.
9). For this purpose, the workflows are translated into a textual representation. Hence,
the block-oriented workflow structure is reduced to a single sequence. Based on this, the
required ingredients and the sequence of preparation steps (including the information
on which ingredients are required in every preparation step) are generated. Further, the
workflow itself is also illustrated in the process view.</p>
      <p>CookingCAKE also features a name generator for the generated recipes. It accesses
the taxonomy of ingredients and combines several terms of sub-taxonomies contained
as ingredients in the workflow to assign a name to a recipe.</p>
      <p>Based on the 61 recipes stored in CookingCAKE, generalization and specialization
enable to generate more than 9 1021 recipes. Further adaptations are supported by 197
workflow streams found and 7870 operators (1306 replace, 3903 insert, 2661 delete)
generated. As the streams and operators are also generalized (see Sect. 4.2) adaptability
is further increased. Hence, CookingCAKE provides a capable tool for the adaptation
of sandwich recipes.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusions and Future Work</title>
      <p>We presented CookingCAKE, a framework for the adaptation of cooking recipes
represented as workflows integrating and combining various adaptation approaches applied
in Process-Oriented Case-Based Reasoning (POCBR). The available case base of
cooking workflows is analyzed to generate adaptation knowledge which is used to adapt a
recipe regarding a given query for the preparation of a dish.</p>
      <p>
        In future work, we will investigate and integrate additional adaptation approaches
for workflows such as the abstraction of workflows containing abstract tasks (e.g.,
prepare sauce, place toppings on sandwich). Further, we will integrate the case-based
adaptation approach of Minor et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] in our framework. Moreover, CookingCAKE will
be extended to be able to handle more knowledge-intensive ontologies, e.g., ontologies
with multiple inheritance. Future work will also comprise the retrieval of adaptable
cases [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], i.e., we will investigate the adaptability of the workflows within the case
base as the workflow that best matches the given query is not necessarily the workflow
that can be at best adapted to the resources and requirements given. Consequently, a
better workflow as starting point for the adaptation can be chosen. Moreover, the
retainment of adaptation knowledge[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] will be addressed by gathering user feedback on
the adapted cooking recipes. This is important, as the quality of automatically learned
adaptation knowledge can not always be ensured. Thus, the quality of workflow
adaptation is improved and the growth of adaptation knowledge can be controlled. Finally,
CookingCAKE will be extended by interactive adaptation [
        <xref ref-type="bibr" rid="ref1 ref20 ref8">1,8,20</xref>
        ]. This supports the
search of a suitable query by involving user interaction during adaptation which assist
the user to create more individual cooking recipes.
      </p>
      <p>Acknowledgements. This work was funded by the German Research Foundation (DFG),
project number BE 1373/3-1.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aha</surname>
            ,
            <given-names>D.W.</given-names>
          </string-name>
          ,
          <article-title>Mun˜oz-</article-title>
          <string-name>
            <surname>Avila</surname>
          </string-name>
          , H.:
          <article-title>Introduction: Interactive case-based reasoning</article-title>
          .
          <source>Applied Intelligence</source>
          <volume>14</volume>
          (
          <issue>1</issue>
          ),
          <fpage>7</fpage>
          -
          <lpage>8</lpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bergmann</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gil</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Similarity assessment and efficient retrieval of semantic workflows</article-title>
          .
          <source>Inf. Syst</source>
          .
          <volume>40</volume>
          ,
          <fpage>115</fpage>
          -
          <lpage>127</lpage>
          (
          <year>Mar 2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Dadam</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rinderle-Ma</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Go¨ser,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Kreher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            ,
            <surname>Jurisch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            :
            <surname>Von ADEPT zur AristaFlow BPM Suite-Eine Vision</surname>
          </string-name>
          wird Realita¨t:”
          <article-title>Correctness by Construction” und flexible, robuste Ausfu¨hrung von Unternehmensprozessen (</article-title>
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dufour-Lussier</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lieber</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nauer</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toussaint</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Text adaptation using formal concept analysis</article-title>
          .
          <source>In: Bichindaritz</source>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Montani</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          <source>(eds.) Case-Based Reasoning. Research and Development, LNCS</source>
          , vol.
          <volume>6176</volume>
          , pp.
          <fpage>96</fpage>
          -
          <lpage>110</lpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Hanney</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keane</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The adaptation knowledge bottleneck: How to ease it by learning from cases</article-title>
          . In: David Leake,
          <string-name>
            <surname>E.P.</surname>
          </string-name>
          (ed.)
          <source>Case-Based Reasoning Research and Development</source>
          <year>1997</year>
          , pp.
          <fpage>179</fpage>
          -
          <lpage>192</lpage>
          . LNAI 1266, Springer (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Jalali</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leake</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>On retention of adaptation rules</article-title>
          . In: Lamontagne,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Plaza</surname>
          </string-name>
          , E. (eds.)
          <source>Case-Based Reasoning Research and Development, Lecture Notes in Computer Science</source>
          , vol.
          <volume>8765</volume>
          , pp.
          <fpage>200</fpage>
          -
          <lpage>214</lpage>
          . Springer International Publishing (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. Kolodner, J.L. (ed.)
          <source>: Proceedings Case-Based Reasoning Workshop</source>
          . Morgan Kaufmann Publishers, San Mateo, California (
          <year>1988</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Leake</surname>
            ,
            <given-names>D.B.</given-names>
          </string-name>
          , Wilson, D.C.
          <article-title>: Combining CBR with interactive knowledge acquisition, manipulation and reuse</article-title>
          .
          <source>In: Case-Based Reasoning Research and Development</source>
          , pp.
          <fpage>203</fpage>
          -
          <lpage>217</lpage>
          . Springer (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lopez</surname>
            <given-names>Mantaras</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>McSherry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Bridge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Leake</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Smyth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Craw</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Faltings</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Maher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.L.</given-names>
            ,
            <surname>Cox</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.T.</given-names>
            ,
            <surname>Forbus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Keane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Aamodt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Watson</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.</surname>
          </string-name>
          :
          <article-title>Retrieval, reuse, revision and retention in case-based reasoning</article-title>
          .
          <source>The Knowledge Engineering Review</source>
          <volume>20</volume>
          (
          <issue>03</issue>
          ),
          <fpage>215</fpage>
          -
          <lpage>240</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Minor</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergmann</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , Go¨rg,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Walter</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          :
          <article-title>Towards case-based adaptation of workflows</article-title>
          .
          <source>In: Case-Based Reasoning. Research and Development</source>
          , pp.
          <fpage>421</fpage>
          -
          <lpage>435</lpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Minor</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montani</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recio-Garca</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          :
          <article-title>Process-oriented case-based reasoning</article-title>
          .
          <source>Information Systems</source>
          <volume>40</volume>
          (
          <issue>0</issue>
          ),
          <fpage>103</fpage>
          -
          <lpage>105</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. Mu¨ller, G.,
          <string-name>
            <surname>Bergmann</surname>
            ,
            <given-names>R.:</given-names>
          </string-name>
          <article-title>A cluster-based approach to improve similarity-based retrieval for Process-Oriented Case-Based Reasoning</article-title>
          .
          <source>In: 20th European Conference on Artificial Intelligence (ECAI</source>
          <year>2014</year>
          ), IOS Press (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. Mu¨ller, G.,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>Workflow Streams: A Means for Compositional Adaptation in Process-Oriented Case-Based Reasoning</article-title>
          .
          <source>In: Proceedings of ICCBR 2014</source>
          . Cork,
          <string-name>
            <surname>Ireland</surname>
          </string-name>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. Mu¨ller, G.,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>Generalization of Workflows in Process-Oriented Case-Based Reasoning</article-title>
          . In: 28th International FLAIRS Conference. AAAI,
          <string-name>
            <surname>Hollywood</surname>
          </string-name>
          (Florida),
          <source>USA</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. Mu¨ller, G.,
          <string-name>
            <surname>Bergmann</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Learning and Applying Adaptation Operators in Process-Oriented Case-Based Reasoning</article-title>
          .
          <source>In: Proceedings of ICCBR 2015</source>
          . Frankfurt,
          <string-name>
            <surname>Germany</surname>
          </string-name>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. Mu¨ller, G.,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>POQL: A New Query Language for Process-Oriented Case-Based Reasoning</article-title>
          .
          <source>In: Proceedings of the LWA</source>
          <year>2015</year>
          <article-title>Workshops: KDML, FGWM, IR, and FGDB</article-title>
          . COER Workshop Proceedings, to appear (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Dynamische Ablaufa¨nderungen in Workflow-Management-</article-title>
          <string-name>
            <surname>Systemen</surname>
          </string-name>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Minor</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Walter</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>Extraction of procedural knowledge from the web</article-title>
          .
          <source>In: Workshop Proceedings: WWW'12</source>
          .
          <string-name>
            <surname>Lyon</surname>
          </string-name>
          , France (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Smyth</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keane</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Retrieving adaptable cases</article-title>
          . In: Wess,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Althoff</surname>
          </string-name>
          , K.D.,
          <string-name>
            <surname>Richter</surname>
          </string-name>
          , M. (eds.)
          <source>Topics in Case-Based Reasoning, Lecture Notes in Computer Science</source>
          , vol.
          <volume>837</volume>
          , pp.
          <fpage>209</fpage>
          -
          <lpage>220</lpage>
          . Springer Berlin Heidelberg (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breu</surname>
          </string-name>
          , R.: CBRFlow:
          <article-title>Enabling adaptive workflow management through conversational case-based reasoning</article-title>
          .
          <source>In: Advances in Case-Based Reasoning</source>
          , pp.
          <fpage>434</fpage>
          -
          <lpage>448</lpage>
          . Springer (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Wilke</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>Techniques and knowledge used for adaptation during case-based problem solving</article-title>
          .
          <source>In: Tasks and Methods in Applied Artificial Intelligence</source>
          , pp.
          <fpage>497</fpage>
          -
          <lpage>506</lpage>
          . Springer (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>