<!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>Case-Based Retrieval and Adaptation of Regulatory Documents and their Context</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andreas Korger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Joachim Baumeister</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Angesagt GmbH</institution>
          ,
          <addr-line>Dettelbachergasse 2, D-97070 Wurzburg</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Wurzburg</institution>
          ,
          <addr-line>Am Hubland, D-97074 Wurzburg</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>denkbares GmbH</institution>
          ,
          <addr-line>Friedrich-Bergius-Ring 15, D-97076 Wurzburg</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Regulatory documents are required or provided by authorities in many domains. They commonly point out relevant incidents for speci c scenarios. For those they have to present suitable preventive and reactive measures. We introduce an approach to connect a case-based description of the incidents structure with a case-based description of the according context. This paper shows how to use case-based methods to retrieve, adapt, and reuse incidents descriptions. Subsequently they are used to generate new regulatory documents via case-based reasoning. Case-based reasoning Experience Management Knowledge Management SKOS Semantic Relatedness Natural Language Generation.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        A regulatory document describes incidents that are likely to happen in a
certain situation. Preventive measures are elaborated to avoid the occurrence of
relevant incidents and adequate reactions are proposed. Further, harmful
consequences are to be avoided or mitigated. This underlying structure is
represented in the documents structure. Popular examples of regulatory documents
are public events, for the handling of hazardous material or industrial workplace
safety. For a festival, a regulatory document would describe incidents such as
re and relevant measures like the allocation of re-extinguishers. The overall
goal of this work is to support domain experts in writing regulatory documents.
Fundamental considerations have been presented in preceding works [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ]. For
instance methods for documentary adaptation using a combination of
ontological document description and case-based reasoning. We extend ontologies to
represent these special parts of documents containing regulatory information.
      </p>
      <p>Copyright c 2019 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).</p>
      <p>We use natural language processing to connect graph-based and textual
knowledge representation. Our goal is to retrieve and adapt passages of documents
depicting such regulatory knowledge for usage in another context.</p>
      <p>For generating a new document, we need to answer three questions. Which
incidents are likely to happen? Which preventive and reactive measures are
suitable for each incident under a certain context? How important is each measure?
The last question pays attention to the fact, that a limited budget and time
does not allow for the implementation of all preventive measures. This sums up
to consider a convenient context-based ranking for the incidents and measures.
The presented approach is a general framework and easily adaptable to domains
providing textual as well as ontological information for the context dependent
classi cation, prevention of, and reaction to incidents.</p>
      <p>For reasons of simpli cation and consistency we give examples of the
domain of public events. Our approach is driven by theoretical and case-based
considerations we describe in the rst part of this work. Then we present the
experimental setup we used to install a case-study showing practical capabilities
of our approach. We nish with related work as well as with discussions and
future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Ontology Model for Incident Assessment</title>
      <p>
        We make the assumption that there exists a corpus of regulatory documents
of a certain domain. The documents are sub-classi ed into passages, that are
connected with incidents or the according measures. Those passages of text are
called information units. The work of identifying these passages was done by
domain experts. All information beyond the textual corpus of available documents
is coded into a knowledge base [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This knowledge base consists of entities
(ontological concepts) as logical units and the relations between them. An entity
may be for instance an action, an agent, an event, or a resource. In a textual
context an entity is coded or described as one word (term) or more words up to
some sentences. Entities may be composed of sub parts in an arbitrary manner.
In the following, we introduce the basic concepts of our scenario.
De nition 1. Let KB = (E ; R; D) be a knowledge base. Let E KB be the set of
available entities (ontological concepts). Let I E be the set of known incidents.
Let M E be the set of known measures. Let R E E be the relations
between elements of E . Let D be the set of available documents D = fd1; ::; dj g.
Let U = f(u 2 di)jdi 2 Dg be the set of available information units contained in
D and T the set of terms used to textually build them.
      </p>
      <p>It is very important for the assessment of safety measures to pay respect to
the context under that they are applied. For instance to supply rescue boats on
a festival F1 besides a river makes sense but for a festival F2 in the forest it
is totally senseless. The context are the factual parameters of the environment.
If the parameters change, the relevant incidents, the according measures and
the importances of both change. Respecting the documentary corpus D, the
context is for instance represented by certain parameters whose ful llment is
mentioned in the content of each document or the parameters, all documents
have in common.</p>
      <p>De nition 2. Let KB = (E ; R; D) be the knowledge base. For an entity ei 2 E
let Cei E n feig be the context of ei with Cei = fc1; ::; cj g.</p>
      <p>For instance, for the previous entities F1 and F2 the context CF1 would be
near river and CF2 in the forest. We want to consider relations making
entities a preventive or reactive measure to incidents. This means to focus on the
chronological order of the execution. In some domains measures are classi ed
into before, during and after an incident. We consider the relational classes
during and after as uni ed. A measure that is taken before an expected incident is
a preventive measure, a measure that is taken during or after an incident is a
reactive measure. A measure may be of preventive as well of reactive character.
De nition 3. Let RP M C M I be a relation under a context C, indicating
which measures are taken in this context C before an incident, making them
preventive measures. Let RRM C I M be the analogous relation, indicating
which measures are taken after the occurring of an incident making them reactive
measures.</p>
      <p>Additionally we rely on an importance ranking of incidents and measures
under a given context. The importance is quanti ed by assigning a value between
1 for important and 0 for not important.</p>
      <p>De nition 4. Let IM P (i; C) 2 ]0; 1] be the importance of an element of I under
the context C. Let IM P (m; i; C) 2 ]0; 1] be the importance of a measure m for
the incident i under the context C.</p>
      <p>For a given context and relevant incident induced by the context the
according measures are ordered by importance and classi ed into preventive and
reactive measures. Altogether they build a kind of facilitated process snippet
we call PIRI (Preventive-Incident-Reactive-Interrelation). The presented model
simpli es the real world for facilitation of assessment. Typically there is a cascade
of measures that are executed in a speci c order, e.g. in case of re rst evacuate
all people, then close the doors and windows. A PIRI-snippet is formally de ned
as follows.</p>
      <p>De nition 5. Let KB = (E ; R; D) be the knowledge base. Let i 2 I be an
incident and C E a context. Then, we de ne a PIRI-snippet P IRI(i; C) =
fC; P Gg, where PG = (N,E) is a directed graph. We call PG the PIRI graph
with nodes N = C \ M [ fig all measures mentioned by C and the incident i
and edges E = fRP M C [ RRM C g \ fig all edges containing the node i. The
graph is weighted with node-weights IMP(N,C) and edge weights IMP(E,i,C).</p>
      <p>Influence</p>
      <p>Preventive
Measures</p>
      <p>Incident
0,9</p>
      <p>0,95
0,85
0,7
I
1</p>
      <p>0,8
0,7
0,75</p>
      <p>
        Reactive
Measures
We extend a previously introduced ontology [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] by the de nition of incidents,
measures and the PIRI-snippet. The existent ontology was used for the classi
cation of public events (OECLA) and the structuring of the according regulatory
documents (OSECCO) as depicted in Figure 2. For the ontological description of
incidents we now continued the elaboration of the SECRI ontology (OSECRI ).
The ontology describes the hierarchical context of incidents with a focus on
public events. We use the SKOS ontology [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] and the PROV ontology [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] as upper
ontologies. The SKOS ontology provides knowledge formalization and
structuring capability. The PROV ontology supports the representation of provenance
information to model the multi-agent-character of the scenario which is induced
by the involvement of several authors and addressees. For the ontological
implementation of a PIRI-snippet we introduce the analogous classes and interweave
them with the documentary structure. An information unit is represented as a
secri:InformationUnit. This passage of text semantically targets a secri:Incident
or secri:Measure and is part of a document represented by secco:Document.
Incidents and measures are subsuming classes as the top of a hierarchy. In the case
study we will see an example of this hierarchy in the domain of public events. A
graphical excerpt of the ontology can be seen in the Figure 3.
      </p>
      <p>
        secri:Incident
targets
targets
targets
secco:Document
A convenient case-based representation for the so far described scenario
internalizes the document description of incidents and measures. For each incident
mentioned by the regulatory document the preventive and reactive measures are
combined into a PIRI-snippet. We choose a structural case representation using
attributes and their values [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>De nition 6. A case c1 = (d1; l1) is de ned by the incident and its context as
problem description d1 = fC1; i1g and its solution l1 = f(C1); (m 2 RP M C1 \
i1); (m 2 RRM C1 \ i1)g, the combination of measures targeting the incident i1
under a context C1, separated into preventive and reactive measures.</p>
      <p>The problem descriptions and the solutions are conjunctions of elements of
the knowledge base. The context may be replaced for a unique identi er naming
the context without citing every component. For instance C1 = RegDocument1
then d1 = fRD1; RainStormg and l1 = f(RD1); (W eightT ents^GetF orecast);
(CloseLiquidGas ^ LockDoors ^ GetRainCoat ^ Evacuate)g.</p>
      <p>De nition 7. The case base CB = fc1; :::; cmg is the collection of all cases ci
extracted from available regulatory documents and constructed as described before
as PIRI-snippets. A query q to the case base is a conjunct subset of (negated)
measures and incidents.</p>
      <p>For instance, the query q1 = CloseDoors ^ :LockDoors ^ Evacuation ^
RainStorm retrieves all other PIRI-snippets containing an evacuation and a
closing and not locking of doors.</p>
      <p>To retrieve cases, we search the case base for similar problem descriptions di
for the query q1. To de ne a similarity function, we consider all preventive
measures, reactive measures and the incident as individual sub-parts. Each of these
parts is then compared by a local similarity measure. With an aggregation
function a global similarity measure is composed by weighting with the parameters
(!P ; !I ; !R) and summed up as follows:
SimPIRI(ck; cl) =</p>
      <p>
        !P SimP (Pk; Pl)+!I SimI (ik; il)+!RSimR(Rk; Rl) =3 (1)
The incidents and measures are classi ed by a taxonomy that was derived from
the connected ontology, building the base for the similarity assessment and
adaptation. The local similarities SimP ; SimI ; SimR are calculated via the taxonomic
order of its elements. The incidents I and the measures P,R are hierarchically
structured. Each element of the hierarchy is assigned with a likelihood
symbolizing the similarity of its sub-elements. The similarity of the leaf-elements is set
to 1 and to 0 for the root element. The similarity increases with depth d of the
element according to for instance simd = 1 1=2d [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. If we want to compare two
PIRI-snippets it is desirable to consider the context. For this reason we de ne
the following extended similarity measure under the context C:
SimContext(ck; cl) =
      </p>
      <p>!1SimPIRI(ck; cl)+!2SimC (Contextk; Contextl) =2 (2)
The context may for instance be the ful llment of a classi cation hierarchy
describing the environmental parameters.</p>
      <p>For instance, security measures under a context of high consumption of
alcoholic beverages are to be considered di erent as under a context of low
consumption of alcohol. So SimC is set to the similarity function used in that scenario
weighted by the weights !i 2 [0; 1] working as biases.
2.3</p>
      <sec id="sec-2-1">
        <title>Constrained-based Extension</title>
        <p>The importance ranking can also be used as an order of execution of measures.
The most important measures have to be taken rst. But sometimes less
important measures have to be taken before other, more important measures. This
pays attention to the so called concatenation of circumstances. It is necessary
to introduce a (partial) order of measures additionally to the order induced by
preventive and reactive and the importance ranking.</p>
        <p>De nition 8. For two measures m1 and m2 the constraint m1
m1 should be taken before m2.
m2 states that</p>
        <p>An obvious problem is as follows. To avoid theft or unauthorized access
especially large buildings have to be locked after an evacuation. This can yield people
being locked inside the building. In reality it is often too complex or not possible
to describe for each incident an order of taking the measures. Additionally in a
multi-agent-scenario it is very di cult to execute instructions being too complex
or too numerous. We therefore take a simple strategy of providing only rules for
pairwise measures, as described before (Evacuate LockDoors).</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Case Study</title>
      <p>
        We exemplify the previous approach by a case study in the domain of public
events. We started with 15 regulatory documents in the domain of public events
that were annotated manually by three di erent domain experts. This corpus
is extended as a basis for the present evaluation. For the annotation process
we developed and evaluated several ontologies. These were used for the classi
cation of public events (OECLA) and the structuring of the according security
documents (OSECCO). The following Table 1 shows the number of ontological
concepts covered by each ontology.
For the ontological description of security incidents we continue the elaboration
of the SECRI ontology (OSECRI ). The SECRI ontology describes the
hierarchical context of security incidents for public events. An excerpt of the ontology can
be seen in Figure 4. In this work we extended the existing ontology by the
capacity of modeling preventive and reactive measures for security incidents in the
domain of public events. All ontologies where implemented using the semantic
wiki KnowWE [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Amongst others we introduce the new classes secri:Measure
as well as secri:PreventiveMeasure and secri:ReactiveMeasure as subclasses of
secri:Measure.
      </p>
      <p>broader
broader</p>
      <p>
        For the case-based implementation we made use of myCBR [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The
hierarchically structured incidents and measures represented in the SECRI ontology
were exported to a myCBR model. The case-based attributes were arranged into
taxonomies as local similarity measures. Those were aggregated into a global
similarity measure for the assessment of the according PIRI-snippets. A number of
relevant cases was extracted out of the corpus and installed in myCBR
making up the experimental case base. Table 2 shows the number of di erent cases
contained in the case base.
      </p>
      <p>
        To evaluate the similarity assessment induced by the PIRI-strategy we
constructed a post mortem analysis. This means to take every case of the case base
and use it as a query to the same case base. Our similarity measures are
constructed symmetrically, consequently the query is commutative. As context we
use the event classi cation ontology Oecla. The context of each PIRI-snippet is
represented by the factual parameters classifying the event extracted out of the
according regulatory document. The pairwise similarities of the event classi
cation cases are already available due to a post mortem analysis done in previous
work [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Each document of the corpus mentions about 20 di erent incidents.
We now focus on the incident FireAndExplosion. For this incident we pairwise
calculate the similarity of the according PIRI-snippets. Afterwards we apply the
context and calculate the context dependent similarity. Figure 5 shows for each
pair of documents the similarity of the PIRI-snippet for the incident
FireAndExplosion as well as the PIRI-similarity combined with the context. This
comparison makes clear, where the in uence of the context changes the similarity
ranking of retrieved PIRI-cases.
3.2
      </p>
      <sec id="sec-3-1">
        <title>Generation of Abstracted Information Units</title>
        <p>In the following we present the strategy for the textual construction of
PIRIsnippets and their adaptation for reuse. Figure 6 shows the work ow of breaking
documents into reusable information units. Beginning with selected features it
shows how they can be put together to form a new document. It presents which
methods are used on each level for extraction, retrieval and adaptation. The
relevant textual elements were extracted from the corpus and transferred into the
ontological structures. The next step is to nd the context dependent information
and replace it to make them reusable. We therefore searched for elements of the
domain vocabulary. Everything left we considered normal text or context related
information that can be abstracted. A strategy for abstraction is to replace words
by their class name. For instance a city name is replaced by location data or by
the part-of-speech class. The following exemplary text for the incident storm
shows, how an according passage of a security document would look in reality.
the similarities SimPIRI j SimContext. The value for SimContext was calculated out
of SimPIRI and SimECLA which were weighted with 0.5 each. A signi cant change
of the retrieval by the incorporated context is marked bold.</p>
        <p>Information Units
Corpus RD</p>
        <p>RD
RD</p>
        <p>RD
RD2</p>
        <p>RD</p>
        <p>RD1</p>
        <p>EXTRACT</p>
        <p>SELECT
ADAPT AND GENERATE</p>
        <p>EXTRACT</p>
        <p>SELECT
ADAPT</p>
        <p>Ontological
Concepts
Document Similarity Assessment:</p>
        <p>ECLA, TF-IDF, SECRI
Adaptation: User fills gaps</p>
        <p>Sentence Similarity Assessment:</p>
        <p>PIRI, Sentence Embeddings
Find and adapt similar information units</p>
        <p>Concept Similarity Assessment:
Word embeddings, Ontologies,</p>
        <p>Joint Embeddings
"Storm. Get weather information on a regularly basis from the munich weather
station. Weight all tents with heavy material or x with ropes. In case of
upcoming storm, evacuate the event site using the franz josef avenue and call the re
department."</p>
        <p>The PIRI-snippet with exemplary importance values for this would be:
Preventive(WeightTents(0.9),GetWeatherForecast(0.8))</p>
        <p>Incident(Storm)</p>
        <p>Reactive(CallFireDepartement(0.9),FullEvacuation(0.8)).</p>
        <p>An abstracted information unit for the measure FullEvacuation would be:
"[FullEvacuation][StopWord][EventSite][Verb][StopWord][LocationData]"
This information unit can be adapted for instance to the measure
PartialEvacuation. The ontological concept FullEvacuation is replaced by a retrieved
information unit for the new measure. The concept EventSite is for instance
replaced by the more speci c concept EventSiteComponent. This information can
be retrieved out of other cases because PartialEvacuation is commonly combined
with EventSiteComponent. The concept LocationData has to be replaced by the
contextual location information which is left to the user. The stop words are
inserted and corrected by a natural language generation tool or the user. The
generated textual passage before stop word correction and context correction
looks as follows:</p>
        <p>"[Partial evacuation of the a ected area][the]
[EventSiteComponent][using][the][LocationData]"</p>
        <p>Figure 7 shows the user interaction and the case-based cycle of natural
document extraction and generation. In step (1) a new problem arises. That may
be for instance that a new regulatory document is required or an existing
document has to be improved as shown in step (2). All features are extracted out
of the problem description and the old document at step (3) and queried to the
knowledge base at step (4). The retrieved features, phrases and documents are
returned in step (5) and adapted in step (6) which requires user interaction. The
new regulatory document is used (7) and retained in the corpus enlarging the
case base (8).
3.3</p>
      </sec>
      <sec id="sec-3-2">
        <title>Results and Discussion</title>
        <p>The results of the case study for the retrieval of similar information units are
very promising even without user support. The incorporation of the contextual
paradigm signi cantly improved the simulation of the real world scenario.
Regarding the generation of regulatory documents the results were quite good when
supported by the user. To answer the initial question, which incidents are likely
to happen, the context-based assessment can be used - similar context points to
similar incidents. Same holds for the measures that are suitable for an incident.
The importance of incidents and measures is made accessible by the percentage
of cases covering the incident or measure under a certain context.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Related Work</title>
      <p>
        We started the research for related work to this paper with an overview of state
of the art publications in the domain of natural language generation presented
by Gatt and Krahmer [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Most of the presented work requires a large corpus for
the application of statistical methods. More suitable for our necessities seemed
grammar-based approaches. This lead us to the idea of abstracting text by giving
it a pseudo grammar structure.
      </p>
      <p>
        There exists some work for the assessment of incidents in di erent domains.
A similar approach we want to mention was presented by Sizov et al. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. The
work focuses on the extraction and the (case-based) adaptation of explanations
contained in incident reports in the transportation domain. The work di ers in
that way that we are aiming for a holistic document oriented and ontology-based
approach with user support for generation. A framework for the connection of
ontologies and constraints for the assessment of work ows was presented by
Nguyen et al. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        The structural integration of context into the case-based assessment was
covered by various authors. Di erent approaches for the incorporation of
context into a case-based decision were proposed by Pla et al. [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. We adapted
the method of context stacking for this scenario. A conceptual revision of the
context-based reasoning paradigm was presented by Stensrud et al. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. For the
role of context in case-based reasoning a good work was published by Khan et
al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] as well as by Craw and Aamodt [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] for the use of similar case clusters
for representing context. The ontological side of context representation was for
instance presented in a thoughtful way by Strang et al. [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] and Xu et al. [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>In this paper we presented a data structure called PIRI for the representation of
a regulatory document describing incidents and according measures. After
formally describing it, we transferred the structure into a case-based model. Using
this model an approach was shown for the adaptation of similarity measures to
di erent context. In a case study the approach was applied to a corpus of
regulatory documents of the domain of public events. What we left for future work
are strategies for the identi cation of relevant attributes out of existing cases.
The application of attribute dependent weights would help to individually adjust
the in uence of the context onto the case-based assessment. Additionally, in the
eld of document generation the integration of grammar-based natural language
generation approaches seems to be promising. To adapt abstracted information
units to di erent contexts would help to reduce the needed user support.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bach</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altho</surname>
          </string-name>
          , K.D.:
          <article-title>Developing case-based reasoning applications using myCBR3</article-title>
          . In: Agudo,
          <string-name>
            <given-names>B.D.</given-names>
            ,
            <surname>Watson</surname>
          </string-name>
          , I. (eds.)
          <source>Case-Based Reasoning Research and Development</source>
          . pp.
          <volume>17</volume>
          {
          <fpage>31</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bach</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sauer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altho</surname>
            ,
            <given-names>K.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roth-Berghofer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Knowledge modeling with the open source tool myCBR</article-title>
          .
          <source>In: Proceedings of the 10th International Conference on Knowledge Engineering and Software</source>
          Engineering - Volume
          <volume>1289</volume>
          . pp.
          <volume>84</volume>
          {
          <fpage>94</fpage>
          . KESE'14,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          .org, Aachen, Germany (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Baumeister</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reutelshoefer</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The connectivity of multi-modal knowledge bases</article-title>
          .
          <source>CEUR Workshop Proceedings</source>
          <volume>1226</volume>
          ,
          <issue>287</issue>
          {
          <volume>298</volume>
          (01
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Baumeister</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reutelshoefer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Puppe</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>KnowWE: A semantic wiki for knowledge engineering</article-title>
          .
          <source>Applied Intelligence</source>
          <volume>35</volume>
          (
          <issue>3</issue>
          ),
          <volume>323</volume>
          {
          <fpage>344</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <source>Experience Management</source>
          . Springer, Berlin, Heidelberg (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Craw</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aamodt</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Case-Based Reasoning as a Model for Cognitive Arti cial Intelligence: 26th International Conference</article-title>
          ,
          <string-name>
            <surname>ICCBR</surname>
          </string-name>
          <year>2018</year>
          , Stockholm, Sweden, July 9-
          <issue>12</issue>
          ,
          <year>2018</year>
          , Proceedings, pp.
          <volume>62</volume>
          {
          <issue>77</issue>
          (07
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Gatt</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krahmer</surname>
          </string-name>
          , E.:
          <article-title>Survey of the state of the art in natural language generation: Core tasks, applications and evaluation</article-title>
          .
          <source>CoRR abs/1703</source>
          .09902 (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alegre</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kramer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Augusto</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          :
          <article-title>Is `context-aware reasoning = case-based reasoning'</article-title>
          ? In: Brezillon,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Turner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Penco</surname>
          </string-name>
          , C. (eds.) Modeling and
          <string-name>
            <given-names>Using</given-names>
            <surname>Context</surname>
          </string-name>
          . pp.
          <volume>418</volume>
          {
          <fpage>431</fpage>
          . Springer International Publishing,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Korger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baumeister</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The SECCO ontology for the retrieval and generation of security concepts</article-title>
          .
          <source>In: Cox</source>
          ,
          <string-name>
            <given-names>M.T.</given-names>
            ,
            <surname>Funk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Begum</surname>
          </string-name>
          , S. (eds.)
          <source>ICCBR. Lecture Notes in Computer Science</source>
          , vol.
          <volume>11156</volume>
          , pp.
          <volume>186</volume>
          {
          <fpage>201</fpage>
          . Springer (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Korger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baumeister</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>Textual case-based adaptation using semantic relatedness - a case study in the domain of security documents</article-title>
          .
          <source>In: Wissensmanagement Potsdam</source>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Provenance: An Introduction to PROV</article-title>
          .
          <source>Synthesis Lectures on the Semantic Web: Theory and Technology</source>
          , Morgan and Claypool (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>T.H.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Le-Thanh</surname>
          </string-name>
          , N. (eds.):
          <article-title>Ensuring the Semantic Correctness of Workow Processes: An Ontological Approach</article-title>
          .
          <article-title>KESE 2014 Knowledge Engineering</article-title>
          and Software
          <string-name>
            <surname>Engineering</surname>
          </string-name>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Pla</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coll</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mordvaniuk</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lopez</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Context-aware case-based reasoning</article-title>
          . In: Prasath,
          <string-name>
            <surname>R.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O</given-names>
            <surname>'Reilly</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Kathirvalavakumar</surname>
          </string-name>
          , T. (eds.)
          <source>Mining Intelligence and Knowledge Exploration</source>
          . pp.
          <volume>229</volume>
          {
          <fpage>238</fpage>
          . Springer International Publishing,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Sizov</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ozturk</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marsi</surname>
          </string-name>
          , E.:
          <article-title>Let me explain: Adaptation of explanations extracted from incident reports</article-title>
          .
          <source>AI</source>
          Communications
          <volume>30</volume>
          ,
          <issue>1</issue>
          {
          <fpage>14</fpage>
          (06
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Stensrud</surname>
            ,
            <given-names>B.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barrett</surname>
            ,
            <given-names>G.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trinh</surname>
            ,
            <given-names>V.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gonzalez</surname>
            ,
            <given-names>A.J.</given-names>
          </string-name>
          :
          <article-title>Context-based reasoning: A revised speci cation</article-title>
          .
          <source>In: FLAIRS Conference</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Strang</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , Linnho -Popien,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Frank</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          :
          <article-title>Cool: A context ontology language to enable contextual interoperability</article-title>
          . vol.
          <volume>2893</volume>
          , pp.
          <volume>236</volume>
          {
          <issue>247</issue>
          (01
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <article-title>W3C: SKOS Simple Knowledge Organization System Reference</article-title>
          : http://www.w3.org/TR/skos-reference (
          <year>August 2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Xu</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xing</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          :
          <article-title>Cacont: A ontology-based model for context modeling and reasoning</article-title>
          .
          <source>Applied Mechanics and Materials</source>
          <volume>347</volume>
          -
          <volume>350</volume>
          (03
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>