<?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">Compatible and Incompatible Ontology Mappings</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Muhammad</forename><forename type="middle">Aun</forename><surname>Abbas</surname></persName>
							<email>muhammad-aun.abbas@univ-ubs.fr</email>
							<affiliation key="aff0">
								<orgName type="department">LabSTICC</orgName>
								<orgName type="institution">University of South Brittany</orgName>
								<address>
									<postCode>56000</postCode>
									<settlement>Vannes</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giuseppe</forename><surname>Berio</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">LabSTICC</orgName>
								<orgName type="institution">University of South Brittany</orgName>
								<address>
									<postCode>56000</postCode>
									<settlement>Vannes</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Compatible and Incompatible Ontology Mappings</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">5D6D9BF1C1369B96DD52DEF53F44767C</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T05:04+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>
			<textClass>
				<keywords>
					<term>Upper ontologies</term>
					<term>Ontology mappings</term>
					<term>Galois connection</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Upper ontologies are interesting because describing and representing concepts that can be used across various domains (as opposed to domain ontologies). This feature may enable increased correctness of mappings between domain ontologies, conceptual schema and languages. Unfortunately, there exist various upper ontologies and it is quite difficult to decide or to assess which of them should be used in one application: the main reason is that upper ontologies are complex artifacts possibly specified in specific logics providing formalization of highly abstract concepts. Researchers have been therefore interested in understanding the similarities between upper ontologies by establishing mappings between key ontology concepts. In this paper, we review mappings proposed in literature and we establish a notion of compatibility between these mappings by introducing a method based on Galois connections. We then conclude with a synthesis of the results obtained by using the proposed method.</p><p>The key findings put in evidence some key differences leading to incompatibility among proposed mappings. These differences are worth to be further investigated.</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>In literature, what can be referred to as mappings between ontologies has been studied in various contexts, especially in the case of domain ontologies. Mappings are usually abstract or concrete functions or relations between ontology artifacts (often concepts); mappings correspond to, precise or approximate, similarities, equality, subsumption <ref type="bibr" target="#b0">[1]</ref>. Mappings have been discussed and formalized in domain ontology matching, alignment and merging; distinct approaches have been then proposed based on logics <ref type="bibr" target="#b1">[2]</ref>, categories <ref type="bibr" target="#b2">[3]</ref>, argumentations , <ref type="bibr" target="#b3">[4]</ref>, and practice <ref type="bibr" target="#b4">[5]</ref>. All these approaches require to use a specific formalization and not really usable for upper ontologies because mainly requiring description logics and/or, not very generic, easily understandable, concepts belonging to ontologies). Some of those approaches are focusing on the mapping correctness, trying to understand if a mapping is not logically contradictory when combined with the whole set of ontology axioms while some other approaches focuses on what we name mapping acceptability, i.e. looking for mappings that, according to formulated arguments, are more suitable than others.</p><p>We undertake an intermediate approach base on the key notion of mapping compatibility and incompatibility. Mappings are incompatible if they cannot be used consistently together in one single application. However, it is quite important to note that two incompatible mappings may be both correct (w.r.t. the whole set of ontology axioms). Compatible and incompatible mappings are relevant at both run-time and design time. At run-time, compatible and incompatible mappings are especially relevant in peer to peer applications, distributed applications and agent based applications and finally open interoperability focused applications. Indeed, all of such applications often comprise several autonomous entities without any central point of control and even without any common management procedure: each of these entities may use its own vocabulary, reference schema, ontology and so on to map each message, flow, variables and so on coming from other entities. At design-time, compatible and incompatible mappings can be used to understand distinct perspectives underlying interpretations of ontological artifacts. For instance, to accomplish alignment, one concept can be mapped on to another concept belonging to another ontology due to label based similarities (and therefore the mapping is quite loose) while another mapping can map one concept on to another one because their logical equivalence (within some theoretical frameworks) can be established. Within the former mapping, the various ontological artifacts (as concepts) are interesting because of their labels; within the second mapping, the various ontological artifacts are interesting as logical artifacts (to perform for instance, reasoning).</p><p>Throughout the paper, we therefore provide a complete method for checking mapping incompatibility, especially in the case of upper ontologies. We consider this notion very useful whenever there ontologies are formalized in distinct logics and whenever the key point is not to evaluate if a mapping is correct but just if distinct mappings can be used together (because they are not contradictory). Therefore, mapping compatibility and incompatibility will be formalized by using mechanisms which are logic-independent (as for instance, the case of e-connections <ref type="bibr" target="#b5">[6]</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1">Motivating Example</head><p>We have two agents and , they are using ontologies as their knowledge base. First agent is based on DOLCE ontology and the second agent is based on GFO ontology and they have ontology mappings for others agent's ontology. These ontology mappings are independent to each other, i.e., these mappings may have different ontology correspondences for any concept. . Agent sends two messages to Agent : a) msg(Particular) b) msg(Event). We have to check whether the ontology artifacts used in these messages are interpreted by the receiving agent are compatible with the sent messages. For this we have to check whether the ontology correspondences for these ontology artifacts are compatible in mappings and . For msg(Particular) both alignments have compatible mappings for this message because they are same, while for msg(Event) both alignments have incompatible mappings for this message because the mapped concepts are disjoint and nothing common between them.</p><p>This paper is structured as follows. In the next section we describe about Galois connections and Ontology mapping compatibility and incompatibility and we present a table about available upper ontology mappings. We present our proposed method in Section 3. A synthesis of our work is presented in Section 4. We then present Related Work in 5. Finally we conclude in Section 6.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Preliminaries</head><p>In this section we will describe about Galois connections and Ontology mapping compatibility and incompatibility.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Galois connections</head><p>In the literature, two definitions of Galois connections are reported. Definition 1: Given ordered structures A, B with partial order relationship and antitone mappings and , we say that the pair ( ) establishes an order reversing Galois connection between and if ( ) and ( ) , . Definition 2: Given ordered structures with partial order relationship and isotone mappings and , we say that the pair ( ) establishes an order preserving Galois connection between and if ( ) and ( ), .</p><p>The first definition can be seen as symmetric where the two mappings γ and α cannot be differentiated; if order relationships are information orders then if a ≽ A b this means that a is less informed than b (the same as for instance in subsumption); γ and α can be interpreted abstraction mappings, because applying one mapping result in some information loss. The second definition is not symmetric because γ and α can be differentiated; under the same interpretation of order relationships, α is an abstraction mapping while γ is a concretization mapping because resulting in information enrichment.</p><p>Galois connections are interesting whenever dealing with mappings between ontologies because at least:</p><p>1. Independent of the kind of formalization (such as the kind of logics) used to represent ontologies, ontologies comprise at least one taxonomy to organize artifacts, which corresponds to an information order as well; 2.</p><p>Can be applied to concepts but also to relationships/properties <ref type="bibr" target="#b6">[7]</ref> and to their taxonomies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Ontology mapping incompatibility and compatibility</head><p>Except approximated mappings, precise mappings between ontologies are basically represented as functions or relationships between ontology artifacts. Representing mappings as relationships enables to map one artifact on to several artifacts, which is the position we are undertaking in the remainder. Let now suppose that , are two ontologies and , are the sets of their concepts, ordered according to concept taxonomies. Starting from two concept mappings ( ) , (</p><p>), being used to complete the two ontology mappings f and g whenever they are undefined. The same can be done for relationships/properties defined in the ontologies. Starting from mappings, for building functions on ordered sets as required by Galois connection, lets now define orders in power sets and in the same way as follows:</p><p>where represents the concept taxonomies in . Two functions can then be easily defined as: with ( ) ( ) and ( ) ( ) . Functions α, γ may or may not respect conditions required in definitions 1 and 2. Figures <ref type="figure" target="#fig_1">1(a</ref>) to 1(d) show the relevant situations depending on the conditions required for Galois connections. Each situation depicted in the figures can be associated with a logical meaning (according to <ref type="bibr" target="#b7">[8]</ref> as better explained in the remainder), which is based on the fact that the ontology source of one mapping may be re-interpreted in the ontology target of the same mapping. (a function is said to be an interpretation of into iff is satisfied in all models of , by interpreting each symbol 's' of as models of ( ). This means that allows to infer at least the same formulas then when substituting symbols A, C with B and D (for instance, it is possible to infer because ). Because and are symmetric, also leads to necessary conditions for being interpreted into . According to the discussion above, the notion of "mapping incompatibility" can now be introduced by the following definition.</p><p>Definition 3. Two mappings f and g between two ontologies are "compatible" iff the corresponding functions α and γ are either an order preserving Galois connection or an order reversing Galois connection. Two mappings that are not compatible are said to be "incompatible".</p><p>It should be noted that "mapping incompatibility" and "mapping compatibility" are distinct notions that "mapping correctness" mentioned in the Introduction. Indeed, compatible or incompatible mappings can be either correct or incorrect when combined with additional ontology axioms.</p><p>Compatibilities and incompatibilities can also be stated at the level of ontology artifacts according to the following definition.</p><p>Definition 4. Given mappings f and g, functions α and γ built as above, an ontology artifact A is compatible with ontology artifacts ( ) iff Galois connections conditions are respected between A and ( ). Symmetrically, an ontology artifact B is compatible with ontology artifacts ( ) iff Galois connections conditions are respected between B and ( ). Otherwise involved artifacts are incompatible.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Existing upper Ontology Mappings</head><p>Comparing upper ontologies is usually performed by establishing (explicitly or implicitly) some mappings between concepts belonging to distinct ontologies. We have defined a methodology for collecting existing mappings (Table <ref type="table" target="#tab_1">1</ref>), then for analyzing them according to Galois connections. </p><formula xml:id="formula_0">Source WordNet DOLCE GFO SUMO SOWA Cyc BFO UFO BWW UEMO PDL Chisholm PROTON PSI [9] × × [9] × × [10] × × [11] × × × × × [12] × × [13] × × × × [14] × × [15] × × [16] × × × [17] × × [18] × × [19] × × × ×</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Proposed method</head><p>We propose a method to find compatibilities and incompatibilies between ontology mappings (see Fig. <ref type="figure">2</ref>). It has two main steps. (a) Collecting existing upper ontology mappings, (b) Analyzing collected mappings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Collecting existing upper ontology mappings</head><p>In most of the cases found in the literature, relationships between mapped concepts are not qualified i.e. it remains unclear if the authors consider them as equivalence, subsumption, similarity and so on. Our proposal based on Galois connections does not require any information about the type of mapping such as equivalence, similarity and so on. In some cases, the authors do not specify any mapping for some concepts. In our proposal, we consider that the authors have tried to map all concepts, except if otherwise stated.</p><p>In our proposal, we have also taken care of the "format"' that the authors use for representing mappings. For mappings implicitly explained in the text, we have explicitly built a two column table for each couple of ontologies. For mappings directly provided as two column tables, we have just considered the same tables.</p><p>When dealing with a multicolumn table involving more than two ontologies, we have applied transitivity by assuming that, without specific assumptions provided by authors, the authors have used the same types of mapping for all ontologies.</p><p>To arrange the collected mappings, we have used several four column tables providing one mapping from some authors and an inverse mapping from some other authors. Extract of those tables is shown in Fig. <ref type="figure">3</ref>. Each of these four column tables possibly provides distinct mappings between distinct ontologies, and can be used for the further analysis step.</p><p>DOLCE mapping by <ref type="bibr" target="#b14">[15]</ref> BWW mapping by <ref type="bibr" target="#b14">[15]</ref> DOLCE mapping by <ref type="bibr" target="#b12">[13]</ref> BWW mapping by <ref type="bibr" target="#b12">[13]</ref> </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Entity</head><p>Thing Entity Thing System Endurant Fig. <ref type="figure">3</ref>. Arrangement of ontology mappings in four column table</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Analyzing collected upper ontology mappings</head><p>The objective of this step is to verify if the couples of collected mappings respect Galois connection conditions. Compatible mappings have been further distinguished in weak compatible mappings and compatible mappings. The former rises whenever Galois connection conditions are trivially respected because some concepts are mapped to ⊥.</p><p>Hereinafter, the reader can find in several situations, how compatibilities and incompatibilities have been established. According to definition 4, compatibilities and incompatibilities are stated per ontology artifacts. .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Trivial compatibility case</head><p>α ({Category}) GFO = ({Abstract}) Sowa γ({Abstract}) Sowa =({Category}) GFO α ᵒ γ ({Abstract}) Sowa =α ({Category}) GFO = ({Abstract}) Sowa γ ᵒ α({Category}) GFO =γ({Abstract}) Sowa =({Category}) GFO The situation above corresponds to (one type of) Galois connection for specific concepts.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Weak compatibility case α({MaterialStructure}</head><formula xml:id="formula_1">) GFO = ( ) DOLCE γ({PhysicalEndurant}) DOLCE = ({Materi- alStructure}) GFO α ᵒ γ({PhysicalEndurant}) DOLCE =α({MaterialStructure}) GFO = ( ) DOLCE ⊑ (Physi- calEndurant) DOLCE γ ᵒ α({MaterialStructure}) GFO = γ( ) DOLCE = ( ) GFO ⊑ ({MaterialStructure}) GFO</formula><p>This means that the two mappings are compatible. It should be noted that the situation does not much change if instead of the o tology root ⊤ woul h ve bee use . </p><formula xml:id="formula_2">Indeed: α({MaterialStructure}) GFO = (⊤) DOLCE γ({MaterialStructure}) GFO = ({PhysicalEndurant}) DOLCE α ᵒ γ ({PhysicalEndurant}) DOLCE =α(MaterialStructure}) GFO = (⊤) DOLCE γ ᵒ α({MaterialStructure}) GFO = γ (⊤) DOLCE = ⊤ ⊒({PhysicalEndurant}) DOLCE 3. Compatibility case A concept X in</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Synthesis</head><p>The methodology presented in section 3 has been applied to available mappings (shown in table <ref type="table" target="#tab_1">1</ref>) whenever the two required mappings α and γ are established by distinct authors (however, it is possible to apply the methodology to mappings supplied by same authors). Compatibilities due to mapping to are provided in italic (because they are "weak compatibilities" due to our interpretation of partial mappings). Table <ref type="table" target="#tab_3">2</ref> is interpreted as a compatible ontology mapping couples and incompatible ontology mapping couples. A compatible mapping couple observes the properties of Galois connection and Incompatible mapping couples does not respect the properties of Galois connection. We have also applied our approach on GFO and Sowa's ontology; DOLCE and SUMO; DOLCE and WordNET; DOLCE and BWW. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Related Work</head><p>As said in the Introduction, several approaches to mappings between ontologies have been proposed in the literature. These approaches are not intended for any kind of ontology even if some rely on the specific formalization in which the ontology is represented. Hereinafter, we are going to review approaches that in our opinion are representative.</p><p>In <ref type="bibr" target="#b20">[20]</ref> it is suggested to use Category theory approach for Ontology merging. In <ref type="bibr" target="#b2">[3]</ref>, an algebraic approach i.e. categorical approach is used to formally describe ontology merging, ontology alignment composition, union and intersection. They focus on defining suitable categorical representation of ontology alignments. However they define composition, union and intersection operation operations for ontology alignments without considering whether ontology alignments involve in these operations may generate inconsistencies.</p><p>In <ref type="bibr" target="#b3">[4]</ref> it is suggested to use Argumentation to argue about acceptability of mappings issued by distinct agents. The disadvantage is that in addition to mappings there is the need to provide justification of such mappings, which in most cases are not available. Our approach does not consider justifications of mappings, so it can handle this kind of mappings. So However, our approach can be seen within the context of arguments. Indeed, if it is possible to say that if two functions are incompatible, couples ( ) or ( ) can be redefined as attacks. We do not define successful attack, but conflict free set can contain either or , not both.</p><p>Researchers work on debugging and repairing of ontology alignment. <ref type="bibr" target="#b21">[21]</ref> and <ref type="bibr" target="#b22">[22]</ref> consider that ontologies are correct but if there is some inconsistency it is caused only by ontology mappings. <ref type="bibr" target="#b21">[21]</ref> find the minimal conflict set that causes incoherent alignment, and then removes the correspondences causing inconsistencies by minimizing its impact. <ref type="bibr" target="#b22">[22]</ref> uses the notion of minimal conflict sets and provides a mapping revision operator that modify alignment so that the result be consistent. Our incompatible mappings can be considered as minimal conflict set and can be first evaluated by these approaches for possible incoherence.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusion</head><p>This paper has presented an approach of comparing mappings proposed by different authors. These mappings are usually stated for showing underlying similarities between upper ontologies, even when these ontologies have been designed by using fundamentally distinct design options. The methodology is based on Galois connections and on the definition of "mapping compatibility and incompatibility". We applied the methodology to available mappings (shown in Table <ref type="table" target="#tab_1">1</ref>) and in the paper we have provided a synthesis of the results concerning relevant couples of upper ontologies. These results show that all the mappings established between upper ontologies are weakly compatible or incompatible. We believe our work is useful in the context of upper ontologies. As upper ontologies are based on different design options, so they are very difficult to establish mappings between upper ontologies. So our work of classifying upper ontologies correspondence into compatible and incompatible mappings helps the user of upper ontologies when they used these ontologies in their applications.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Bibliography</head></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 Fig. 1 .</head><label>11</label><figDesc>Fig. 1.a</figDesc><graphic coords="5,136.05,303.40,151.20,144.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 1 .</head><label>1</label><figDesc>Fig.1.a provides the situation of an order preserving the Galois connection. It can be shown that A,B,C,D (for instance, concepts) are interpreted as first order logics symbols, (and f mapping by definition) leads to necessary conditions for being interpreted into (a function is said to be an interpretation of into iff is satisfied in all models of , by interpreting each symbol 's' of as models of ( ). This means that allows to infer at least the same formulas then when substituting symbols A, C with B and D (for instance, it is possible to infer because ). Because and are symmetric, also leads to necessary conditions for being interpreted into . Fig.1.b corresponds to the situation of an order reversing Galois connection. By interpreting A,B,C,D as first order logic symbols, it is possible to define an interpretation of into such that ( ) and ( ) ( is a negation connective). In practice, it is a negative interpretation saying what is not instead of what is. Fig.1.c depicts one acceptable situation in which Galois connection conditions are not satisfied. In this case, is an interpretation of into , but cannot be interpreted in by therefore, f and g mappings (on which and are built) are fundamentally distinct. Finally, Fig.1.d depicts another acceptable situation in which Galois connection conditions are not satisfied. In this case, and bound concepts in completely distinct and independent</figDesc><graphic coords="5,287.55,303.40,151.20,144.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="7,136.05,189.40,331.39,172.45" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1 .</head><label>1</label><figDesc>Existing</figDesc><table /><note>Comparison of Upper ontologies conceptsFig. 2. Steps for finding compatibilities and incompatibilities in ontology mappings</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head></head><label></label><figDesc>GFO = γ({Space Region}) DOLCE = ( ) GFO = Spatial Location and Space Region are subsumed by Physical Quality and Abstract Region respectively that are not ordered. This situation therefore does correspond to neither order reversing not order preserving Galois connection, rising in incompatibility.</figDesc><table><row><cell>one ontology is mapped to some concept Y in other ontology, but in</cell></row><row><cell>another mapping performed by some other author(s), X is mapped to Z which is sub-</cell></row><row><cell>sumed by Y. i.e. Z Y. For instance</cell></row><row><cell>α({Process}) GFO = ({Stative}) DOLCE</cell></row><row><cell>γ({Process}) DOLCE =({Process}) GFO</cell></row><row><cell>α ᵒ γ ({Process}) DOLCE = α({Process}) GFO = ({Stative}) DOLCE ({Process}) DOLCE</cell></row><row><cell>Stative is more general than Process, and Process is an immediate descendant of</cell></row><row><cell>Stative.</cell></row><row><cell>γ ᵒ α({Process}) GFO = γ({Stative}) DOLCE = ({Process}) GFO</cell></row><row><cell>which corresponds to a reverse ordering Galois connection.</cell></row><row><cell>4. Incompatibility case</cell></row><row><cell>A concept X in one ontology is mapped to some concept Y in another ontology, but X</cell></row><row><cell>is mapped to Z, while Y and Z are not ordered.</cell></row><row><cell>α({Region}) GFO = ({Space Region}) DOLCE</cell></row><row><cell>γ({Spatial Location}) DOLCE =({Region}) GFO</cell></row><row><cell>α ᵒ γ ({Spatial Location}) DOLCE = α(Region) GFO = ({Space Region}) DOLCE</cell></row><row><cell>γ ᵒ α({Region})</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 2 .</head><label>2</label><figDesc>Compatibilities and Incompatibilities of DOLCE and GFO</figDesc><table><row><cell></cell><cell cols="2">Mappings couple α [9], γ [11]</cell><cell></cell></row><row><cell></cell><cell>Compatibilities</cell><cell cols="2">InCompatibilities</cell></row><row><cell>DOLCE</cell><cell>GFO</cell><cell>DOLCE</cell><cell>GFO</cell></row><row><cell>Particular</cell><cell>Individual</cell><cell>Event</cell><cell>{Change},</cell></row><row><cell></cell><cell></cell><cell></cell><cell>{Discrete Pro-</cell></row><row><cell></cell><cell></cell><cell></cell><cell>cess}</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Ontology mapping</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">F</forename><surname>Noy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Handbook on ontologies</title>
				<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="573" to="590" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Using C-OWL for the alignment and merging of medical ontologies</title>
		<author>
			<persName><forename type="first">H</forename><surname>Stuckenschmidt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Van Harmelen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Serafini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Bouquet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the First Int. WS. on Formal Biomedical K. R. (KRMed)</title>
				<meeting>of the First Int. WS. on Formal Biomedical K. R. (KRMed)</meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="volume">102</biblScope>
			<biblScope unit="page" from="88" to="101" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Formalizing ontology alignment and its operations with category theory</title>
		<author>
			<persName><forename type="first">A</forename><surname>Zimmermann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Krotzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Frontiers in Artificial Intelligence and Applications</title>
		<imprint>
			<biblScope unit="volume">150</biblScope>
			<biblScope unit="page">277</biblScope>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Argumentation for reconciling agent ontologies</title>
		<author>
			<persName><forename type="first">C</forename><surname>Trojahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Tamma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Payne</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Semantic Agent Systems</title>
				<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="89" to="111" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Debugging ontology mappings: A static approach</title>
		<author>
			<persName><forename type="first">P</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Baowen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computing and Informatics</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="21" to="36" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Working with multiple ontologies on the semantic web</title>
		<author>
			<persName><forename type="first">B</forename><surname>Grau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Parsia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sirin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web-ISWC 2004</title>
				<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="620" to="634" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Relational Galois Connections</title>
		<author>
			<persName><forename type="first">B</forename><surname>Ganter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Formal Concept Analysis 4390</title>
				<editor>
			<persName><forename type="first">S</forename><surname>Kuznetsov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Schmidt</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin / Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="1" to="17" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">A Mathematical Introduction to Logic</title>
		<author>
			<persName><forename type="first">H</forename><surname>Enderton</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2001">2001</date>
			<publisher>Harcourt Academic Press</publisher>
		</imprint>
	</monogr>
	<note>2nd edn</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">General Formal Ontology (GFO): A Foundational Ontology Integrating Objects and Processes</title>
		<author>
			<persName><forename type="first">H</forename><surname>Herre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Heller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Burek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hoehndorf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Loebe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Michalek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Onto-Med Report, Research Group Ontologies in Medicine (Onto-Med)</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
		<respStmt>
			<orgName>University of Leipzig</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Borgo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gangemi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Oltramari</surname></persName>
		</author>
		<title level="m">IST Project 2001-33052 WonderWeb: Ontology Infrastructure for the Semantic Web</title>
				<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
	<note>WonderWeb Deliverable D18 Ontology Library</note>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">H</forename><surname>Bens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Ontology4.us</title>
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Aligning the UEML Ontology with SUMO</title>
		<author>
			<persName><forename type="first">A</forename><surname>Opdahl</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Enterprise Interoperability IV</title>
				<meeting><address><addrLine>London</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2010">2010</date>
			<biblScope unit="page" from="409" to="418" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">A Unified Foundational Ontology and some Applications of it in Business Modeling</title>
		<author>
			<persName><forename type="first">G</forename><surname>Guizzardi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Wagner</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="129" to="143" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">BFO in a Nutshell: A Bi-categorial Axiomatization of BFO and Comparison with DOLCE</title>
		<author>
			<persName><forename type="first">P</forename><surname>Grenon</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
		<respStmt>
			<orgName>IFOMIS, University of Leipzig</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">Use of upper ontologies for interoperation of information systems: a tutorial</title>
		<author>
			<persName><forename type="first">R</forename><surname>Colomb</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2002">2002</date>
			<publisher>ISIB-CNR</publisher>
			<pubPlace>Padua (Italy</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">Semantic Annotation for Process Models : Facilitating Process Knowledge Management via Semantic Interoperability</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Lin</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
	<note type="report_type">Master&apos;s Thesis</note>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Using meta models for the comparison of ontologies</title>
		<author>
			<persName><forename type="first">I</forename><surname>Davies</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Green</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Milton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rosemann</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<monogr>
		<author>
			<persName><forename type="first">I</forename><surname>Terziev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kiryakov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Manov</surname></persName>
		</author>
		<title level="m">Base Upper-level Ontology (BULO)</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">Guidance. Deliverable</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">8</biblScope>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
	<note>SEKT project</note>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Evaluating PSI Ontologies by mapping to the Common Sense</title>
		<author>
			<persName><forename type="first">N</forename><surname>Keberle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Ermolayev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W.-E</forename><surname>Matzke</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="volume">107</biblScope>
			<biblScope unit="page" from="91" to="104" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">What Is Ontology Merging?</title>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Krötzsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ehrig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Sure</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">American Association for Artificial Intelligence</title>
				<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">An efficient method for computing alignment diagnoses</title>
		<author>
			<persName><forename type="first">C</forename><surname>Meilicke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Stuckenschmidt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Web Reasoning and Rule Systems</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="182" to="196" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">A conflict-based operator for mapping revision</title>
		<author>
			<persName><forename type="first">G</forename><surname>Qi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Q</forename><surname>Ji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Haase</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web-ISWC 2009</title>
				<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="521" to="536" />
		</imprint>
	</monogr>
</biblStruct>

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