<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Case-Based Retrieval and Adaptation of Regulatory Documents and their Context</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Andreas</forename><surname>Korger</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Angesagt GmbH</orgName>
								<address>
									<addrLine>Dettelbachergasse 2</addrLine>
									<postCode>D-97070</postCode>
									<settlement>Würzburg</settlement>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Joachim</forename><surname>Baumeister</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">denkbares GmbH</orgName>
								<address>
									<addrLine>Friedrich-Bergius-Ring 15</addrLine>
									<postCode>D-97076</postCode>
									<settlement>Würzburg</settlement>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="institution">University of Würzburg</orgName>
								<address>
									<addrLine>Am Hubland</addrLine>
									<postCode>D-97074</postCode>
									<settlement>Würzburg</settlement>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Case-Based Retrieval and Adaptation of Regulatory Documents and their Context</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">51BA4FD597B4EF8DD3A99931F3471367</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T18:28+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Regulatory documents are required or provided by authorities in many domains. They commonly point out relevant incidents for specific 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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><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 fire and relevant measures like the allocation of fire-extinguishers. The overall goal of this work is to support domain experts in writing regulatory documents. Fundamental considerations have been presented in preceding works <ref type="bibr" target="#b8">[9,</ref><ref type="bibr" target="#b9">10]</ref>. 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>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 classification, prevention of, and reaction to incidents.</p><p>For reasons of simplification 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 first part of this work. Then we present the experimental setup we used to install a case-study showing practical capabilities of our approach. We finish with related work as well as with discussions and future work.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Ontology Model for Incident Assessment</head><p>We make the assumption that there exists a corpus of regulatory documents of a certain domain. The documents are sub-classified 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 <ref type="bibr" target="#b2">[3]</ref>. 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. Definition 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 = {d 1 , .., d j }. Let U = {(u ∈ d i )|d i ∈ D} 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 F 1 besides a river makes sense but for a festival F 2 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 fulfillment is mentioned in the content of each document or the parameters, all documents have in common. Definition 2. Let KB = (E, R, D) be the knowledge base. For an entity e i ∈ E let C ei ⊆ E \ {e i } be the context of e i with C ei = {c 1 , .., c j }.</p><p>For instance, for the previous entities F 1 and F 2 the context C F1 would be near river and C F2 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 classified into before, during and after an incident. We consider the relational classes during and after as unified. 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. Additionally we rely on an importance ranking of incidents and measures under a given context. The importance is quantified by assigning a value between 1 for important and 0 for not important. Definition 4. Let IM P (i, C) ∈ ]0, 1] be the importance of an element of I under the context C. Let IM P (m, i, C) ∈ ]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 classified into preventive and reactive measures. Altogether they build a kind of facilitated process snippet we call PIRI (Preventive-Incident-Reactive-Interrelation). The presented model simplifies the real world for facilitation of assessment. Typically there is a cascade of measures that are executed in a specific order, e.g. in case of fire first evacuate all people, then close the doors and windows. A PIRI-snippet is formally defined as follows.</p><p>Definition 5. Let KB = (E, R, D) be the knowledge base. Let i ∈ I be an incident and C ⊆ E a context. Then, we define a PIRI-snippet P IRI(i, C) = {C, P G}, where PG = (N,E) is a directed graph. We call PG the PIRI graph with nodes N = C ∩ M ∪ {i} all measures mentioned by C and the incident i and edges E = {R P M −C ∪ R RM −C } ∩ {i} all edges containing the node i. The graph is weighted with node-weights IMP(N,C) and edge weights IMP(E,i,C).  We extend a previously introduced ontology <ref type="bibr" target="#b8">[9]</ref> by the definition of incidents, measures and the PIRI-snippet. The existent ontology was used for the classification of public events (O ECLA ) and the structuring of the according regulatory documents (O SECCO ) as depicted in Figure <ref type="figure">2</ref>. For the ontological description of incidents we now continued the elaboration of the SECRI ontology (O SECRI ).</p><p>The ontology describes the hierarchical context of incidents with a focus on public events. We use the SKOS ontology <ref type="bibr" target="#b16">[17]</ref> and the PROV ontology <ref type="bibr" target="#b10">[11]</ref> 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 <ref type="figure" target="#fig_0">3</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Case-Based Representation of the PIRI-Structure</head><p>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 <ref type="bibr" target="#b4">[5]</ref>. Definition 6. A case c 1 = (d 1 , l 1 ) is defined by the incident and its context as problem description d 1 = {C 1 , i 1 } and its solution l 1 = {(C 1 ), (m ∈ R P M −C1 ∩ i 1 ), (m ∈ R RM −C1 ∩ i 1 )}, the combination of measures targeting the incident i 1 under a context C 1 , 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 identifier naming the context without citing every component. For instance</p><formula xml:id="formula_0">C 1 = RegDocument1 then d 1 = {RD 1 , RainStorm} and l 1 = {(RD1), (W eightT ents∧GetF orecast), (CloseLiquidGas ∧ LockDoors ∧ GetRainCoat ∧ Evacuate)}.</formula><p>Definition 7. The case base CB = {c 1 , ..., c m } is the collection of all cases c i 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 q 1 = 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 d i for the query q 1 . To define 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:</p><formula xml:id="formula_1">Sim PIRI (c k , c l ) = ω P Sim P (P k , P l )+ω I Sim I (i k , i l )+ω R Sim R (R k , R l ) /3 (1)</formula><p>The incidents and measures are classified by a taxonomy that was derived from the connected ontology, building the base for the similarity assessment and adaptation. The local similarities Sim P , Sim I , Sim R 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 sim d = 1−1/2 d <ref type="bibr" target="#b0">[1]</ref>. If we want to compare two PIRI-snippets it is desirable to consider the context. For this reason we define the following extended similarity measure under the context C:</p><formula xml:id="formula_2">Sim Context (c k , c l ) = ω 1 Sim PIRI (c k , c l )+ω 2 Sim C (Context k , Context l ) /2 (2)</formula><p>The context may for instance be the fulfillment of a classification hierarchy describing the environmental parameters.</p><p>For instance, security measures under a context of high consumption of alcoholic beverages are to be considered different as under a context of low consumption of alcohol. So Sim C is set to the similarity function used in that scenario weighted by the weights ω i ∈ [0, 1] working as biases.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Constrained-based Extension</head><p>The importance ranking can also be used as an order of execution of measures. The most important measures have to be taken first. 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. Definition 8. For two measures m 1 and m 2 the constraint m 1 ≺ m 2 states that m 1 should be taken before m 2 .</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 difficult 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><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 different 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 classification of public events (O ECLA ) and the structuring of the according security documents (O SECCO ). The following Table <ref type="table" target="#tab_0">1</ref> shows the number of ontological concepts covered by each ontology. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Retrieval of Similar PIRI-Snippets</head><p>For the ontological description of security incidents we continue the elaboration of the SECRI ontology (O SECRI ). The SECRI ontology describes the hierarchical context of security incidents for public events. An excerpt of the ontology can be seen in Figure <ref type="figure" target="#fig_4">4</ref>. 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 <ref type="bibr" target="#b3">[4]</ref>. Amongst others we introduce the new classes secri:Measure as well as secri:PreventiveMeasure and secri:ReactiveMeasure as subclasses of secri:Measure. For the case-based implementation we made use of myCBR <ref type="bibr" target="#b1">[2]</ref>. 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 <ref type="table" target="#tab_1">2</ref> shows the number of different cases contained in the case base. 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 classification ontology O ecla . 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 classification cases are already available due to a post mortem analysis done in previous work <ref type="bibr" target="#b8">[9]</ref>. Each document of the corpus mentions about 20 different 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 <ref type="figure">5</ref> shows for each pair of documents the similarity of the PIRI-snippet for the incident FireAnd-Explosion as well as the PIRI-similarity combined with the context. This comparison makes clear, where the influence of the context changes the similarity ranking of retrieved PIRI-cases.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Generation of Abstracted Information Units</head><p>In the following we present the strategy for the textual construction of PIRIsnippets and their adaptation for reuse. Figure <ref type="figure">6</ref> shows the workflow 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 find 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. PIRI0 x x 0,5 0,6 0,6 0,6 0,5 0,5 0,6 0,6 0,5 0,5 0,3 0,5 0,3 0,5 0,4 0,5 0,3 0,5 0,3 0,5 0,3 0,3 0,3 0,3 0,4 0,5 0,0 0,2 PIRI1 0,5 0,7</p><p>x x 0,9 0,8 0,4 0,5 0,3 0,4 0,4 0,5 0,6 0,7 0,3 0,3 0,6 0,5 0,4 0,5 0,4 0,5 0,5 0,4 0,3 0,3 0,4 0,4 0,3 0,3 PIRI2 0,5 0,5 0,9 0,8 x x 0,5 0,5 0,4 0,4 0,5 0,4 0,6 0,6 0,3 0,3 0,5 0,5 0,4 0,6 0,4 0,5 0,4 0,4 0,3 0,4 0,4 0,4 0,2 0,3 PIRI3 0,5 0,5 0,4 0,5 0,5 0,5 x x 0,5 0,6 1,0 0,8 0,4 0,5 0,3 0,5 0,2 0,5 0,4 0,5 0,4 0,4 0,2 0,3 0,2 0,3 0,6 0,6 0,1 0,2 PIRI4 0,6 0,6 0,3 0,4 0,4 0,4 0,5 0,6</p><p>x x 0,5 0,6 0,3 0,4 0,2 0,5 0,1 0,4 0,1 0,3 0,1 0,2 0,2 0,3 0,1 0,2 0,7 0,6 0,0 0,1 PIRI5 0,5 0,5 0,4 0,5 0,5 0,4 1,0 0,8 0,5 0,6</p><p>x x 0,4 0,5 0,3 0,5 0,2 0,5 0,4 0,5 0,4 0,5 0,2 0,3 0,2 0,2 0,6 0,5 0,1 0,2 PIRI6 0,3 0,5 0,6 0,7 0,6 0,6 0,4 0,5 0,3 0,4 0,4 0,5</p><p>x x 0,3 0,4 0,3 0,5 0,5 0,5 0,3 0,4 0,3 0,3 0,3 0,3 0,4 0,5 0,1 0,3 PIRI7 0,3 0,5 0,3 0,3 0,3 0,3 0,3 0,5 0,2 0,5 0,3 0,5 0,3 0,4</p><p>x x 0,3 0,5 0,3 0,2 0,3 0,3 0,1 0,3 0,3 0,3 0,3 0,4 0,0 0,1 PIRI8 0,4 0,5 0,7 0,6 0,6 0,5 0,2 0,5 0,8 0,8 0,2 0,5 0,3 0,5 0,3 0,5</p><p>x x 0,5 0,5 0,5 0,5 0,6 0,5 0,4 0,4 0,2 0,3 0,1 0,1 PIRI9 0,3 0,5 0,4 0,5 0,4 0,6 0,4 0,5 0,1 0,3 0,4 0,5 0,5 0,6 0,3 0,2 0,5 0,5</p><p>x x 0,9 0,8 0,2 0,3 0,3 0,3 0,2 0,3 0,2 0,3 PIRI10 0,3 0,5 0,4 0,5 0,4 0,5 0,5 0,5 0,1 0,2 0,5 0,5 0,3 0,4 0,3 0,3 0,5 0,5 0,9 0,8</p><p>x x 0,2 0,3 0,3 0,3 0,2 0,3 0,2 0,3 PIRI11 0,3 0,3 0,5 0,4 0,5 0,4 0,2 0,3 0,2 0,3 0,2 0,3 0,3 0,3 0,1 0,3 0,6 0,5 0,2 0,3 0,2 0,3 x x 0,3 0,3 0,3 0,4 0,3 0,3 PIRI12 0,3 0,3 0,3 0,3 0,3 0,4 0,2 0,3 0,1 0,2 0,2 0,2 0,3 0,3 0,3 0,3 0,4 0,4 0,3 0,3 0,3 0,3 0,3 0,3</p><p>x x 0,1 0,2 0,0 0,3 PIRI13 0,4 0,5 0,4 0,4 0,4 0,4 0,6 0,6 0,7 0,6 0,6 0,5 0,4 0,5 0,3 0,4 0,2 0,3 0,2 0,3 0,2 0,3 0,3 0,4 0,1 0,2 x x 0,2 0,3 PIRI14 0,0 0,2 0,3 0,3 0,2 0,3 0,1 0,2 0,0 0,1 0,1 0,2 0,1 0,3 0,0 0,1 0,3 0,3 0,2 0,3 0,2 0,3 0,3 0,3 0,0 0,3 0,2 0,3 </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Information Units</head><p>Fig. <ref type="figure">6</ref>: Workflow of decomposing and recomposing security documents.</p><p>"Storm. Get weather information on a regularly basis from the munich weather station. Weight all tents with heavy material or fix with ropes. In case of upcoming storm, evacuate the event site using the franz josef avenue and call the fire department."</p><p>The PIRI-snippet with exemplary importance values for this would be: Preventive(WeightTents(0.9),GetWeatherForecast(0.8)) Incident(Storm) Reactive(CallFireDepartement(0.9),FullEvacuation(0.8)). An abstracted information unit for the measure FullEvacuation would be:</p><formula xml:id="formula_3">"[FullEvacuation][StopWord][EventSite][Verb][StopWord][LocationData]"</formula><p>This information unit can be adapted for instance to the measure Partial-Evacuation. The ontological concept FullEvacuation is replaced by a retrieved information unit for the new measure. The concept EventSite is for instance re-placed by the more specific 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>" Figure <ref type="figure" target="#fig_5">7</ref> 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 <ref type="bibr" target="#b1">(2)</ref>. 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 <ref type="bibr" target="#b4">(5)</ref> and adapted in step (6) which requires user interaction. The new regulatory document is used <ref type="bibr" target="#b6">(7)</ref> and retained in the corpus enlarging the case base (8).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3">Results and Discussion</head><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 significantly 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.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Related Work</head><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 <ref type="bibr" target="#b6">[7]</ref>. 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 different domains. A similar approach we want to mention was presented by Sizov et al. <ref type="bibr" target="#b13">[14]</ref>. The work focuses on the extraction and the (case-based) adaptation of explanations contained in incident reports in the transportation domain. The work differs 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 workflows was presented by Nguyen et al. <ref type="bibr" target="#b11">[12]</ref>.</p><p>The structural integration of context into the case-based assessment was covered by various authors. Different approaches for the incorporation of context into a case-based decision were proposed by Pla et al. <ref type="bibr" target="#b12">[13]</ref>. 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. <ref type="bibr" target="#b14">[15]</ref>. For the role of context in case-based reasoning a good work was published by Khan et al. <ref type="bibr" target="#b7">[8]</ref> as well as by Craw and Aamodt <ref type="bibr" target="#b5">[6]</ref> 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. <ref type="bibr" target="#b15">[16]</ref> and Xu et al. <ref type="bibr" target="#b17">[18]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions</head><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 different 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 identification of relevant attributes out of existing cases. The application of attribute dependent weights would help to individually adjust the influence of the context onto the case-based assessment. Additionally, in the field of document generation the integration of grammar-based natural language generation approaches seems to be promising. To adapt abstracted information units to different contexts would help to reduce the needed user support.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Definition 3 .</head><label>3</label><figDesc>Let R P 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 R RM −C ⊆ I × M be the analogous relation, indicating which measures are taken after the occurring of an incident making them reactive measures.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 1</head><label>1</label><figDesc>Figure 1 shows a PIRI-diagram for the incident I 1 under the context C consisting of several contextual elements (c 1 , c 2 , c 3 , ..).</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 1 :Fig. 2 :</head><label>12</label><figDesc>Fig. 1: PIRI-diagram under a context C = (C 1 , ..., C j ) showing the ranked preventive and reactive measures with the according importance weight.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Fig. 3 :</head><label>3</label><figDesc>Fig. 3: Class representation of a PIRI-snippet.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 4 :</head><label>4</label><figDesc>Fig. 4: Excerpt of the SECRI Ontology showing 7 of 72 measures.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>[Fig. 7 :</head><label>7</label><figDesc>Fig. 7: Case-based cycle of regulatory document assessment.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>Number of ontological concepts for each ontology used.</figDesc><table><row><cell cols="4">OSECCO Structuring OECLA Classification OSECRI Incidents OSECRI Measures</cell></row><row><cell>278</cell><cell>136</cell><cell>115</cell><cell>72</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2 .</head><label>2</label><figDesc>Overview of different cases.</figDesc><table><row><cell cols="4">Different Contexts PIRI-Cases (Measures under Context)-Cases Information Units</cell></row><row><cell>15</cell><cell>300</cell><cell>1500</cell><cell>500</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head></head><label></label><figDesc>Post mortem analysis of the PIRI-snippets for the measure FireAndExplosion without and with the context of the event classification. The values show the similarities Sim PIRI | Sim Context . The value for Sim Context was calculated out of Sim PIRI and Sim ECLA which were weighted with 0.5 each. A significant change of the retrieval by the incorporated context is marked bold.</figDesc><table><row><cell>christm</cell><cell cols="3">wine</cell><cell cols="3">wine</cell><cell cols="3">folk</cell><cell>city</cell><cell>carne</cell><cell>folk</cell><cell>music</cell><cell>carne</cell><cell>fair</cell><cell>fair</cell><cell cols="7">running camp</cell><cell cols="6">arena campus</cell></row><row><cell>PIRI0</cell><cell>P</cell><cell>R I</cell><cell>1 I</cell><cell>P</cell><cell>R I</cell><cell>2 I</cell><cell>P</cell><cell>I R I</cell><cell>3</cell><cell>PIRI4</cell><cell>PIRI5</cell><cell>PIRI6</cell><cell>PIRI7</cell><cell>PIRI8</cell><cell cols="2">PIRI9 PIRI10</cell><cell>P</cell><cell>R I</cell><cell>1 1 I</cell><cell>P</cell><cell>R I</cell><cell>1 I</cell><cell>2</cell><cell>P</cell><cell>R I</cell><cell>3 1 I</cell><cell>P</cell><cell>R I</cell><cell>4 1 I</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">x x</cell></row><row><cell cols="2">Fig. 5: RD Corpus</cell><cell cols="2">RD</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>RD</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">RD</cell><cell></cell><cell>RD1</cell><cell></cell><cell></cell><cell cols="5">EXTRACT</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">EXTRACT</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>RD</cell><cell>RD2</cell><cell></cell><cell cols="8">ADAPT AND GENERATE SELECT</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">SELECT ADAPT</cell><cell></cell><cell></cell><cell></cell><cell cols="7">Ontological Concepts</cell><cell></cell><cell></cell></row><row><cell cols="10">Document Similarity Assessment:</cell><cell></cell><cell cols="5">Sentence Similarity Assessment:</cell><cell cols="14">Concept Similarity Assessment:</cell></row><row><cell cols="7">ECLA, TF-IDF, SECRI</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="4">PIRI, Sentence Embeddings</cell><cell></cell><cell cols="14">Word embeddings, Ontologies,</cell></row><row><cell cols="8">Adaptation: User fills gaps</cell><cell></cell><cell></cell><cell cols="6">Find and adapt similar information units</cell><cell></cell><cell></cell><cell></cell><cell cols="8">Joint Embeddings</cell><cell></cell><cell></cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Developing case-based reasoning applications using my-CBR3</title>
		<author>
			<persName><forename type="first">K</forename><surname>Bach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">D</forename><surname>Althoff</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Case-Based Reasoning Research and Development</title>
				<editor>
			<persName><forename type="first">B</forename><forename type="middle">D</forename><surname>Agudo</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">I</forename><surname>Watson</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin Heidelberg; Berlin, Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="17" to="31" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Knowledge modeling with the open source tool myCBR</title>
		<author>
			<persName><forename type="first">K</forename><surname>Bach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Sauer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">D</forename><surname>Althoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Roth-Berghofer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 10th International Conference on Knowledge Engineering and Software Engineering</title>
				<meeting>the 10th International Conference on Knowledge Engineering and Software Engineering<address><addrLine>Aachen, Germany</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1289">1289. 2014</date>
			<biblScope unit="page" from="84" to="94" />
		</imprint>
	</monogr>
	<note>KESE&apos;14. CEUR-WS.org</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The connectivity of multi-modal knowledge bases</title>
		<author>
			<persName><forename type="first">J</forename><surname>Baumeister</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Reutelshoefer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2014-01">01 2014</date>
			<biblScope unit="volume">1226</biblScope>
			<biblScope unit="page" from="287" to="298" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">KnowWE: A semantic wiki for knowledge engineering</title>
		<author>
			<persName><forename type="first">J</forename><surname>Baumeister</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Reutelshoefer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Puppe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Applied Intelligence</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="323" to="344" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Experience Management</title>
		<author>
			<persName><forename type="first">R</forename><surname>Bergmann</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2002">2002</date>
			<publisher>Springer</publisher>
			<pubPlace>Berlin, Heidelberg</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Case-Based Reasoning as a Model for Cognitive Artificial Intelligence</title>
		<author>
			<persName><forename type="first">S</forename><surname>Craw</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Aamodt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">26th International Conference, ICCBR 2018</title>
				<meeting><address><addrLine>Stockholm, Sweden</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018-07-12">July 9-12, 2018. 07 2018</date>
			<biblScope unit="page" from="62" to="77" />
		</imprint>
	</monogr>
	<note>Proceedings</note>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Survey of the state of the art in natural language generation: Core tasks, applications and evaluation</title>
		<author>
			<persName><forename type="first">A</forename><surname>Gatt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Krahmer</surname></persName>
		</author>
		<idno>CoRR abs/1703.09902</idno>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Is &apos;context-aware reasoning = case-based reasoning&apos; ?</title>
		<author>
			<persName><forename type="first">N</forename><surname>Khan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Alegre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kramer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">C</forename><surname>Augusto</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Modeling and Using Context</title>
				<editor>
			<persName><forename type="first">P</forename><surname>Brézillon</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">R</forename><surname>Turner</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Penco</surname></persName>
		</editor>
		<meeting><address><addrLine>Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer International Publishing</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="418" to="431" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">The SECCO ontology for the retrieval and generation of security concepts</title>
		<author>
			<persName><forename type="first">A</forename><surname>Korger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Baumeister</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">ICCBR. Lecture Notes in Computer Science</title>
		<editor>Cox, M.T., Funk, P., Begum, S.</editor>
		<imprint>
			<biblScope unit="volume">11156</biblScope>
			<biblScope unit="page" from="186" to="201" />
			<date type="published" when="2018">2018</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Textual case-based adaptation using semantic relatedness -a case study in the domain of security documents</title>
		<author>
			<persName><forename type="first">A</forename><surname>Korger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Baumeister</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Wissensmanagement Potsdam</title>
				<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Provenance: An Introduction to PROV</title>
		<author>
			<persName><forename type="first">L</forename><surname>Moreau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Groth</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Synthesis Lectures on the Semantic Web: Theory and Technology</title>
				<imprint>
			<publisher>Morgan and Claypool</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Ensuring the Semantic Correctness of Workflow Processes: An Ontological Approach</title>
	</analytic>
	<monogr>
		<title level="j">Knowledge Engineering and Software Engineering</title>
		<editor>Nguyen, T.H.H., Le-Thanh, N.</editor>
		<imprint>
			<date type="published" when="2014">2014. 2014</date>
		</imprint>
	</monogr>
	<note type="report_type">KESE</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Context-aware case-based reasoning</title>
		<author>
			<persName><forename type="first">A</forename><surname>Pla</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Coll</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Mordvaniuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>López</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Mining Intelligence and Knowledge Exploration</title>
				<editor>
			<persName><forename type="first">R</forename><surname>Prasath</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><surname>O'reilly</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">T</forename><surname>Kathirvalavakumar</surname></persName>
		</editor>
		<meeting><address><addrLine>Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer International Publishing</publisher>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="229" to="238" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Let me explain: Adaptation of explanations extracted from incident reports</title>
		<author>
			<persName><forename type="first">G</forename><surname>Sizov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Ozturk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Marsi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">AI Communications</title>
		<imprint>
			<biblScope unit="volume">30</biblScope>
			<biblScope unit="page" from="1" to="14" />
			<date type="published" when="2017-06">06 2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Context-based reasoning: A revised specification</title>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">S</forename><surname>Stensrud</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">C</forename><surname>Barrett</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">C</forename><surname>Trinh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">J</forename><surname>Gonzalez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">FLAIRS Conference</title>
				<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">Cool: A context ontology language to enable contextual interoperability</title>
		<author>
			<persName><forename type="first">T</forename><surname>Strang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Linnhoff-Popien</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Frank</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2004-01">01 2004</date>
			<biblScope unit="volume">2893</biblScope>
			<biblScope unit="page" from="236" to="247" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<ptr target="http://www.w3.org/TR/skos-reference" />
		<title level="m">W3C: SKOS Simple Knowledge Organization System Reference</title>
				<imprint>
			<date type="published" when="2009-08">August 2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Cacont: A ontology-based model for context modeling and reasoning</title>
		<author>
			<persName><forename type="first">N</forename><surname>Xu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Yang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Xing</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Applied Mechanics and Materials</title>
		<imprint>
			<biblScope unit="volume">347</biblScope>
			<biblScope unit="page">350</biblScope>
			<date type="published" when="2013">03. 2013</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
