<?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">Ontology Integration Approaches: A Systematic Mapping</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jordana</forename><forename type="middle">S</forename><surname>Salamon</surname></persName>
							<email>jssalamon@inf.ufes.br</email>
							<affiliation key="aff0">
								<orgName type="department">Computer Science Department</orgName>
								<orgName type="laboratory">Ontology &amp; Conceptual Modeling Research Group (NEMO)</orgName>
								<orgName type="institution">Federal University of Espírito Santo-Vitória -ES</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Cássio</forename><forename type="middle">C</forename><surname>Reginato</surname></persName>
							<email>cassio.reginato@inf.ufes.br</email>
							<affiliation key="aff0">
								<orgName type="department">Computer Science Department</orgName>
								<orgName type="laboratory">Ontology &amp; Conceptual Modeling Research Group (NEMO)</orgName>
								<orgName type="institution">Federal University of Espírito Santo-Vitória -ES</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Monalessa</forename><forename type="middle">P</forename><surname>Barcellos</surname></persName>
							<email>monalessa@inf.ufes.br</email>
							<affiliation key="aff0">
								<orgName type="department">Computer Science Department</orgName>
								<orgName type="laboratory">Ontology &amp; Conceptual Modeling Research Group (NEMO)</orgName>
								<orgName type="institution">Federal University of Espírito Santo-Vitória -ES</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Ontology Integration Approaches: A Systematic Mapping</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">602C58F52A5BBD4AB67237297CD62910</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T03:48+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>Ontology Integration</term>
					<term>Systematic Mapping</term>
					<term>Mapping Study</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ontology integration is an important topic of interest in Ontology</head><p>Engineering. Integrating ontologies is a complex process that involves finding suitable ontologies, interpreting them and integrating them into a new integrated ontology. This paper presents a systematic mapping that investigated ontology integration approaches and provides a panorama of this topic. The results revealed a limited use of semantic relationships to map ontologies and a lack of concern with the integration scope, the goals the integrated ontology must achieve, search and selection of the ontologies to be integrated, and integration-based development processes.</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>Nowadays, ontology engineers are supported by a wide range of ontology engineering methods and tools. However, building ontologies is still a difficult task. Integrating existing ontologies to develop a new one can be a useful approach. Ontology reuse allows speeding up the ontology development process, saving time and money, and promoting the application of good practices <ref type="bibr" target="#b20">(Poveda Villalon et al., 2010)</ref>. However, ontology reuse is a complex research issue and one of the most challenging areas of Ontology. Ontology engineers still face problems to select the right ontologies for reuse and integrate several ontologies into a new ontology <ref type="bibr" target="#b16">(Park et al., 2011)</ref>. Ontology integration involves merging, consolidating, analyzing, and modifying two or more ontologies into a new (integrated) ontology <ref type="bibr" target="#b19">(Pinto and Martins, 2001)</ref>. It depends on finding and reusing ontologies able to meet the requirements of the new ontology.</p><p>Ontology integration is related to knowledge sharing and reuse. Therefore, it is crucial in Ontology Engineering and has been a recurrent research topic <ref type="bibr" target="#b0">(Blomqvist and Öhgren, 2008)</ref> . In some cases, ontology integration is approached in an isolated form (i.e., self-contained) and, in others, it is approached as part of the ontology development process. Due to the high number of ontology models available, ontology development has demanded efficient methods of reuse and integration <ref type="bibr" target="#b2">(Caldarola et al., 2015)</ref>.</p><p>Given the importance of ontology integration, we carried out a mapping study to investigate ontology integration approaches recorded in the literature. A mapping study is a secondary study designed to give an overview of a research area through classification and counting contributions in relation to the categories of that classification. It makes a broad study in a topic of a specific theme and aims to identify available evidence about that topic <ref type="bibr" target="#b12">(Kitchenham and Charters, 2007)</ref>. Moreover, the panorama provided by a mapping study allows identifying issues in the researched topic that should be addressed in future research.</p><p>In this study we are particularly interested in ontology integration approaches addressing the conceptual level. By "ontology integration approaches" we mean approaches (i.e., methods, techniques, processes) that integrate (by merging, consolidating, and, when necessary, modifying) two or more ontologies with the purpose of building a new integrated ontology <ref type="bibr" target="#b19">(Pinto and Martins, 2001)</ref>. In this sense, approaches that are limited to address ontology mapping, without producing a new integrated ontology, are out of the study scope. By "conceptual level" we mean that we are interested in approaches concerned with the meanings behind the concepts to perform the integration. No matter if they are exclusively conceptual or associated to operational concerns. Hence, approaches limited to propose operational solutions (i.e., focused on computational aspects) are out of the study scope.</p><p>This paper presents the mapping study and its main results. It is organized as follows: Section 2 provides the background for the paper, talking briefly about ontology integration; Section 3 presents the research protocol used in the study; Section 4 presents the obtained results; Section 5 discusses the findings that emerge from the results; Section 6 addresses the study limitations; and, finally, Section 7 presents our final considerations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Ontology Integration</head><p>In the context of computer and information sciences, an ontology is an artifact that describes a certain reality with some purpose. As any artefact, ontologies have a lifecycle. They are designed, implemented, evaluated, modified, reused, etc. <ref type="bibr" target="#b6">(Gangemi and Presutti, 2009)</ref>. Ontology development is a complex task and even specialists face difficulties. Ontology reuse is a practice that can help in this matter, since existent ontologies can be reused to build new ones <ref type="bibr" target="#b8">(Guizzardi et al., 2013)</ref>. Despite that, ontology engineers still face problems to select the most suitable ontologies and integrate them <ref type="bibr" target="#b16">(Park et al., 2011)</ref>.</p><p>In the literature there are several definitions for ontology integration. In short, ontology integration can be defined as the process of integrating two or more source ontologies to build a new (integrated) ontology <ref type="bibr" target="#b21">(Vergara et al., 2003)</ref>. During the integration process, it may be necessary to refine the source ontologies before integrating them. In addition, new concepts and relationships can be added to the integrated ontology, so that its requirements can be met. Given the strong relation between merging and integration, and the possible confusion this may cause, we explain them bellow.</p><p>According to <ref type="bibr" target="#b18">Pinto et al. (1999)</ref>, there are three different situations involving ontology integration: (i) development of a new ontology reusing other ontologies; (ii) merging of different ontologies that deal with the same subject, resulting in a single ontology unifying them; (iii) integration of ontologies into applications. In the first case, a new ontology has to be developed and there are available ontologies that meet the new ontology requirements; then these ontologies are reused to build a new one. In the second case, the new ontology joins ideas, concepts, distinctions, axioms, etc. (i.e., knowledge) of ontologies in the same domain. When ontologies are merged, a new ontology is created and it unifies concepts, terminologies, definitions, constraints, etc. In the third case, different ontologies are introduced into one application to specify or implement a knowledge-based system.</p><p>In both, integration and merging, there are, on one hand, source ontologies and, on the other, the resulting ontology, obtained by reusing the source ontologies. In the integration process, after the integration it is possible to identify in the resulting ontology regions from the source ontologies. The domains of the source ontologies are different from the domain of the resulting ontology, although there may be a relation between them. The concepts from the source ontologies can be reused in the integrated ontology as they are, they can be adapted (or modified), specialized or added to new concepts. In merging, the goal is to build a more comprehensive ontology about a subject, gathering, in a coherent way, knowledge from other ontologies in the same subject. Thus, the subject of the merged ontologies and the resulting ontology is the same. After merging, it may be difficult to identify regions from the source ontologies in the resulting ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">The Research Protocol</head><p>The study was performed following the approach defined in <ref type="bibr" target="#b12">(Kitchenham and Charters, 2007)</ref>, which involves: planning, when the research protocol is defined; conducting, when the protocol is executed and data are extracted, analyzed, and recorded; and reporting, when the results are recorded and made available to potential interested parties. In this section we present the main parts of the research protocol used in the study.</p><p>The study goal was to investigate ontology integration approaches addressing the conceptual level. For achieving this goal, we defined thirteen research questions (RQ) that are shown in Table <ref type="table">1</ref>.</p><p>The search string adopted in the study is composed of terms related to ontology integration and approach. The following search string was used: (("ontology interoperability") OR ("ontology integration") OR ("ontology merging")) AND (("approach") OR ("method") OR ("framework") OR ("strategy") OR ("process")). As discussed, we are interested in approaches that integrate (by merging, consolidating, and, when necessary, modifying) two or more ontologies with the purpose of building a new ontology. Therefore, in the search string we included merging among the terms related to integration. For establishing the string, we performed some tests using different terms, logical connectors, and combinations among them. More restrictive strings excluded some important publications identified during the informal literature review that preceded the study. These publications were used as control publications, meaning that the search string should be able to retrieve them. We decided to use a comprehensive string that provided better results in terms of number and relevance of the selected publications, even thought it had selected many publications eliminated in subsequent steps.</p><p>The search was performed in the following six sources: IEEE Xplore, ACM Digital Library, Scopus, Science Direct, Engineering Village and Web of Science.</p><p>Publications selection was performed in four steps. In Preliminary Selection and Cataloging (S1), the search string was applied in the search mechanism of each digital library (we limited the search scope to title, abstract and keywords metadata fields). After that, in Duplications Removal (S2), publications indexed in more than one digital library were identified and duplications were removed. In Selection of Relevant Publications -1st filter (S3), the abstracts of the selected publications were analyzed considering the following inclusion (IC) and exclusion (EC) criteria: (IC1) the publication presents an approach for ontology integration addressing the conceptual level; (EC1) the publication is not written in English; (EC2) the publication does not have an abstract; (EC3) the publication is a copy or an older version of an already selected publication; (EC4) the publication is a secondary study, a tertiary study, a summary or an editorial; (EC5) the publication was published as an abstract. In Selection of Relevant Publications -2nd filter (S4), the full text of the publications selected in S3 were read and analyzed considering the cited inclusion and exclusion criteria plus (EC6) The full text of the publication is not available. Publication selection was performed by the first and second authors. For each publication, an identifier was defined and the following information was recorded: title, authors, year, reference and source. Publication selection was reviewed by the third author, who performed the publication selection procedure and reviewed the all the results obtained by the other authors in each step. Discordances were discussed and resolved in meetings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1 -Research Questions</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>ID</head><p>Research Question Rationale</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ01</head><p>Which ontology integration approaches addressing the conceptual level have been presented in the literature?</p><p>Identify ontology integration approaches addressing the conceptual level recorded in the literature</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ02</head><p>When and in which type of vehicle (journal/conference/workshop) have the publications been published?</p><p>Provide an overview about when and where the publications have been published as a way of analyzing the maturity of the research topic. Moreover, verify the distribution of publications per time and per publication vehicle.</p><p>RQ03 Which type of research has been done?</p><p>Identify the type of research using the classification defined in <ref type="bibr" target="#b22">(Wieringa et al., 2006)</ref>. A panorama about the research types can indicate the maturity level of the research topic.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ04</head><p>What is the basic principle of the ontology integration approach?</p><p>Identify the main characteristics of the ontology integration approaches and verify if there is a predominance of some of them.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ05</head><p>Which are the steps of the ontology integration approach? Are they explicitly defined?</p><p>Investigate if there has been concern with defining systematic processes for ontology integration and which steps have been proposed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ06</head><p>Does the approach refer to ontology integration, ontology merging or both?</p><p>Identify the type of approach according to the classification defined in <ref type="bibr" target="#b19">(Pinto and Martins, 2001)</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ07</head><p>Is the ontology integration approach related to some ontology engineering method? If it is the case, which is the method and how does the approach relate to it?</p><p>Investigate whether integration approaches have been proposed in the context of broader ontology engineering methods and how the approach relates to the method.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ08</head><p>Is the ontology integration approach guided by goals?</p><p>Investigate whether goals have been used to support ontology integration.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ09</head><p>Does the ontology integration approach use competence questions?</p><p>Investigate whether competence questions have been used to support ontology integration.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ10</head><p>Does the ontology integration approach use pre-selected ontologies, or does it aid in the selection of the ontologies to be integrated?</p><p>Investigate whether the integration approaches provide mechanisms to support the selection of the ontologies to be integrated.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ11</head><p>Does the ontology integration approach address only the conceptual level or also the operational level?</p><p>Investigate whether ontology integration approaches addressing the conceptual level have also addressed the operational level.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ12</head><p>Is the ontology integration approach automatic, semiautomatic or nonautomatic?</p><p>Investigate whether computational assistance have been used to support the ontology integration approaches.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ13</head><p>Which types of semantic relationships between concepts are addressed in the ontology integration approach?</p><p>Identify the types of semantic relationships between concepts (e.g., equivalence, specialization, generalization, etc.) have been addressed in the ontology integration approaches.</p><p>After selecting the publications, data were extracted and recorded. Data extraction and recording consisted of extracting data from the publications for each research question and recording them in a form designed as a spreadsheet. Data extraction was performed by the first author and reviewed by the third author. Once data were validated, data interpretation and analysis were carried out. Quantitative data were tabulated and used in graphs and statistical analysis. Qualitative analysis was performed considering the findings, their relation to the research questions and the systematic mapping purpose. Data interpretation and analysis were performed by the first author and reviewed by the third author. Discordances were discussed and resolved in meetings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Data Synthesis</head><p>The systematic mapping considered studies published until November of 2017. In the first step (S1) 1816 publications were obtained (229 from IEEE Xplore, 616 from Scopus, 49 from ACM, 57 from Science Direct, 512 from Engineering Village and 353 from Web of Science). In the second step (S2) duplications were removed, remaining 591 publications. In the third step (S3), 232 publications were selected (a reduction of about 61%). In the fourth step (S4) 15 publications were selected (a reduction of about 93%). The expressive reduction in S4 was due to the fact that most analyzed approaches addressed only the operational level. Next, we present the main results for each research questions (RQ). <ref type="table" target="#tab_0">2</ref> presents a summary of the ontology integration approaches found in the study. RQ02. When and in which type of vehicle (journal/conference/workshop) have the studies been published? -The publications selected were published between 2001 and 2017, as shown in Figure <ref type="figure" target="#fig_0">1</ref>. Regarding the publication vehicle, four studies (27%) were published in journals, ten studies (66%) in conferences and one (7%) in workshops. RQ04. What is the basic principle of the ontology integration approach? -The main principles identified were: similarity calculation, semantic mappings and integration operations. The former is about using heuristics to calculate proximity between names, structures and concepts in order to find equivalences. The second is used to find semantic relationships between concepts and indicate the proximity level between them in a   <ref type="bibr" target="#b19">(Pinto and Martins, 2001)</ref> Proposes an ontology integration process that can be used in combination with other methods to build ontologies when the ontologies to be integrated are not pre-selected.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ01. Which approaches of ontology integration addressing the conceptual level have been presented in the literature? -Table</head><p>[P02] <ref type="bibr" target="#b15">(Miyoung et al., 2006)</ref> Ontology merging approach that considers vertical and horizontal integration and uses WordNet.</p><p>[P03] <ref type="bibr" target="#b0">(Blomqvist and Öhgren, 2008)</ref> Method proposed to the automotive suppliers domain. It considers the development of an ontology from the integration of two others, one manually developed and the other automatically developed. [P04] <ref type="bibr" target="#b7">(Geum et al., 2008)</ref> Aims to generate new concepts related to services from ontology integration. It includes three steps: service ontologies development, ontology integration and generation of new service concepts. [P05] <ref type="bibr" target="#b3">(Châabane et al., 2009)</ref> Geographic ontology merging method consisting of three phases: determine the n-ary correspondences between the ontologies; identify mappings between the concepts of the candidate ontologies; rule-based merging to produce a global ontology. [P06] <ref type="bibr" target="#b4">(Chen et al., 2009)</ref> Framework based on web services for knowledge integration from ontology integration. [P07] <ref type="bibr" target="#b9">(Heer et al., 2009)</ref> Approach in which several ontologies can be merged into one using semantic correspondences. It is based on the assumption that all ontologies use a common top-level ontology.</p><p>[P08] <ref type="bibr" target="#b10">(Hu and Wang, 2010)</ref> Presents merging heuristics/algorithms based on category theory for geology ontologies. [P09] <ref type="bibr" target="#b11">(Juárez et al., 2011)</ref> Method that receives a set of source ontologies and a merging parameter and produces a domain ontology unifying knowledge from the source ontologies that meet the merging parameter. [P10] <ref type="bibr" target="#b13">(Leung et al., 2011)</ref> Ontology development method that integrates methods of reuse and a system to support integration. [P11] <ref type="bibr" target="#b14">(Lv, 2011)</ref> Approach combining integration heuristics/algorithms and similarity measures to integrate ontologies. [P12] <ref type="bibr" target="#b17">(Petrov et al., 2012)</ref> Intelligent system that supports merging of anatomical ontologies. It is based on directed acyclic graph models and three integration heuristics/algorithms. [P13] <ref type="bibr" target="#b1">(Bova et al., 2015)</ref> Approach to integrate ontologies to support data interoperability and knowledge representation in intelligent information systems. [P14] <ref type="bibr" target="#b5">(Cuenca et al., 2017)</ref> It deals with integration within the OEMA (Ontology for Energy Management Applications) ontology network, which is composed of eight interconnected domain ontologies. [P15] <ref type="bibr" target="#b1">(Bova et al., 2015)</ref> Method that considers three processes and semantic mappings to integrate two ontologies.</p><p>RQ05. Which are the steps of the ontology integration approach? Are they explicitly defined? -Only the approach addressed in [P02] does not present steps explicitly defined. Table <ref type="table" target="#tab_1">3</ref> presents the steps of each approach.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ06. Does the approach refer to ontology integration, ontology merging or both? -Five approaches (33%) ([P01], [P06], [P11], [P13], [P15]</head><p>) refer to ontology integration, while nine</p><formula xml:id="formula_0">(60%) P02], [P03], [P04], [P05], [P07], [P08], [P09], [P12], [<label>P14</label></formula><p>]) refer to ontology merging. The approach reported in [P10] refer to both, integration and merging. RQ07. Is the ontology integration approach related to some ontology engineering method? If it is the case, which is the method and how does the approach relate to it? -12 publications (80%) propose approaches addressing ontology integration in isolation (i.e., given two or more pre-selected ontologies, how to integrate them). Only three publications (20%) propose ontology integration approaches as part of a broader ontology engineering processes. In [P03], the integration approach refers to the ontology merging phase of SEMCO, an ontology engineering method that involves ontology development, ontology evaluation and ontology merging. In [P10], the integration approach is performed in the context of the analysis, design and implementation phases of the Method for Integration-Oriented Ontology Development, which includes preparation, analysis, design, implementation and maintenance. In [P14], the approach is performed in the context of the first, second and fourth phases of an ontology development method that includes requirements definition, ontology selection for reuse, implementation, ontology integration and evaluation.</p><p>RQ08. Is the approach guided by goals? -None of the approaches uses goals to support ontology integration.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>RQ09. Does ontology integration use competence questions? -Only one approach ([P10]</head><p>) uses competence questions to support ontology integration.</p><p>RQ10. Does the ontology integration approach use pre-selected ontologies, or does it aid in the selection of the ontologies to be integrated? -12 approaches (80%) consider preselected ontologies for integration, that is, they assume that there are two or more selected ontologies that need to be integrated and focus on more specific issues of the integration problem (e.g., how to integrate concepts). Only three approaches (20%) ([P01], [P10],</p><p>[P14]) define ontology selection as a step of the ontology integration approach.</p><p>RQ11. Does the ontology integration approach address only the conceptual level or also the operational level? -Only the approach presented in [P01] does not address the operational level. All others (93%) address both levels.</p><p>RQ12. Is the ontology integration approach automatic semiautomatic or non-automatic? -Six approaches (40%) [P06] (13%) it was not possible to conclude if there is or is not computational assistance.</p><formula xml:id="formula_1">([P08], [P09], [P11], [P12], [P13], [<label>P15</label></formula><p>RQ13. Which types of semantic relationships between concepts are addressed in the approach? -Table <ref type="table">4</ref> presents the identified semantic relationships and the approaches that address each of them. In the table, semantically equivalent relationships are listed separated by "/".</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 4 -Semantic relationships addressed in the integration approaches</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Semantic Relationship Publications</head><p>Equivalence/Synonyms/Identity Semantic</p><formula xml:id="formula_2">[P02], [P04], [P05], [P07], [P08], [P09], [P11], [P12], [P13], [P15] Specialization/hyponym/Subsumption [P02], [P06], [P08], [P11], [P13], [P14] Generalization/Hypernym [P06], [P07], [P08], [P13], [P14] Part Of/Part-Whole [P04], [P08], [P12] Overlap/Partial Equivalence [P02], [P06], [P07], [P13], Disjoint [P02], [P07], Dependency [P08], Spatial Identity [P05] Undefined [P01], [P03], [P10]</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Discussion</head><p>By analysing the publications distribution over the years (RQ02), it is possible to notice that although there has been research about the topic since 2001, it has not been regular. Moreover, considering the publication vehicles (RQ02) (there is a predominance of conferences instead of journals) and the types of research (RQ03), we can conclude that the topic has been explored but it is not mature yet. The lack of studies classified as Evaluation Research indicates that the approaches have not reached the practice.</p><p>With respect to the basic principle of the approaches (RQ04), the majority of them concern finding similarities or semantic relationships between concepts. These results show that integration approaches have been concerned with establishing relations between the ontologies concepts, which is very important to integration.</p><p>There have been concern with defining systematic processes for ontology integration (RQ05). Some steps are cited in several approaches, such as identification of mappings between concepts and merging/integration of concepts. Since these are core activities to integrate ontologies, it is not surprising that they are in most of the approaches. Besides these activities, integration approaches related to broader ontology engineering methods also include activities related to ontologies search and selection. Nevertheless, only three approaches ([1], <ref type="bibr">[11]</ref>, <ref type="bibr">[14]</ref>) address ontology evaluation, even though this is an important activity in of ontology development. Only two approaches ([1] and [10]) address ontology modularization, an important aspect to manage complexity of ontologies. In the view of the above, we can notice that most of the integration approaches have been focused only on integration activities. In fact, most approaches are not concerned with the entire ontology development process (RQ07). As a consequence, these approaches ignore important steps in ontology development such as requirements elicitation, modularization, testing and evaluation.</p><p>There is a predominance of merging approaches (RQ06). This is probably due to two main reasons: (i) approaches focusing on more specific integration problems (e.g., how to integrate similar concepts) can deal with them by merging ontologies (i.e., there is no need to add new concepts to the integrated ontology); and (ii) merging can be seen as part of the integration process, i.e., ontology integration involves merging, since after merging ontologies, new concepts can be added to the resulting ontology.</p><p>Integration approaches have not been concerned with defining the goals the integrated ontology should achieve (RQ08). Most of the analyzed approaches were defined to be used in a specific situation (e.g., given two pre-selected ontologies, how to integrate them). Thus, a big picture of the goals the integrated ontology should achieve is not explored. Goals can be used to express the design rationale behind an ontology and can be helpful in the search for the ontologies to be integrated. Since most of the approaches (80%) use pre-selected ontologies (RQ10), they have not addressed issues that could help ontology search and selection. Moreover, since most approaches do not include steps to identify the integration goals, it is natural that they also are not concerned with defining the integration scope by means of competency questions (RQ09), which has to be made prior to carry out the integration itself.</p><p>Only one of the analyzed approaches does not address the operational level (RQ11). Most of the analyzed approaches were defined to deal with a specific situation, often related to computational applications. Thus, it is not surprising that most of the approaches address not only the conceptual but also the operational level. This can also be influenced by the fact that most of the ontologies available on the Web and used to form the Semantic Web are available only in their operational form. With the growth of the Semantic Web, there is also a growing need to integrate these ontologies. This also can explain the predominance of approaches with automatic or semiautomatic solutions (RQ12). As ontology integration can be a hard process when the ontologies to be integrated are large or heavy, the approaches have automated the process in order to request less intervention from the users.</p><p>Finally, the approaches have addressed few types of semantic relations (RQ13). Some approaches use only the equivalence relation, which limits the integration approach. Addressing only the equivalence relation leads to miss important mappings when the overlap of definitions and properties from different concepts is not complete. One of the reasons for some approaches to consider only the equivalence relation is their focus on operational solutions. Implementing heuristics to find equivalence mappings is easier than heuristics to find other types of semantic relations. However, ideally, the integration approaches should deal with a diversity of semantic relations, to enable proper identification of mappings between the ontologies to be integrated.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Limitations of the Study</head><p>Usually, when conducting secondary studies, researchers need to make a lot of decisions and exercise a lot of judgement. The decisions taken by researchers and the judgments influence the outcome both in terms of which publications are selected and what the researchers conclude from their secondary studies <ref type="bibr" target="#b23">(Wohlin et al., 2012)</ref>. Thus, as in any study, the study presented in this paper has some limitations. Some of the challenges researchers may face during a systematic mapping are: (i) how to select a comprehensive and relevant source of publications; (ii) how to consistently apply the inclusion/exclusion criteria; (iii) how to classify and interpret data. In this study, we experienced these challenges and we take some actions aiming at minimizing the influence on the results.</p><p>With respect to (i), the study considered six digital libraries as source of publications. They were selected based on other secondary studies recorded in the literature, as well as on other secondary studies carried out in the research group in which this work was carried out (NEMO). While this set of digital libraries represents a comprehensive source of publications, the exclusion of other sources and the fact that we did not perform snowballing may have left some valuable publications out of the analysis.</p><p>As for (ii), publications selection and data extraction were initially performed by two of the authors and some subjectivity may have been incorporated, especially regarding the level addressed by the approach (conceptual or operational). Information contained in the publications could lead to a misunderstanding about this aspect. In order to reduce this subjectivity, the third author reviewed publications selection and data extraction and, in case of discordance or possible bias, discussions were held until a consensus was reached. With regard to the selection made from the search string, terminological problems may have led to not select some publications. In order to minimize this possibility, simulations were performed with variations of the string until obtaining the one that was used.</p><p>With respect to (iii), a classification scheme was defined for each research question. Some categories were based on classifications previously proposed in the literature (for example, for type of research we used the classification defined in <ref type="bibr" target="#b22">(Wieringa et al., 2006)</ref>). Other categories were established during data extraction, based on data provided by the analyzed publications (e.g., types of semantic relations and categories of the approaches basic principle). Determining the categories and how the publications fit into them involves a lot of judgment. Data extraction and classification were performed by the first author and reviewed by the third. Even so, it is possible that other researchers would obtain different results.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Final Considerations</head><p>This paper presented a systematic mapping that investigated ontology integration approaches addressing the conceptual level. 591 publications were analyzed and 15 approaches were identified. Before performing the systematic mapping, we investigated the literature searching for secondary studies on ontology integration. Since no secondary study was found on the research topic, we decided to perform the systematic mapping.</p><p>The mapping results provide an overview of the research related to the investigated topic. In short, integration approaches, even when addressing the conceptual level, have also addressed (and, many times, focused on) the operational level. Most of the approaches have been proposed to address specific situations or specific integration problems. There has been concern with defining a systematic process to guide integration. However, in most cases, the integration process is not embedded in a broader ontology development process and considers the integration of pre-selected ontologies, without addressing search and selection of ontologies. Goals and competence questions have not been used to support ontology integration. Finally, approaches have considered few types of semantic relations, which tends to limit the mapping and integration of ontologies.</p><p>These results point to some gaps in the context of integrating ontologies at conceptual level: (i) lack of concern with defining the scope for the integrated ontology prior to the integration process; (ii) lack of concern with the goals that the integrated ontology must achieve; (iii) lack of concern with search and selection of ontologies to be integrated; (iv) limited use of semantic relations to map ontologies; and (v) lack of integration-based development processes that address the development of an integrated ontology considering the main phases of ontology engineering. These gaps provide a roadmap of issues to be explored in future researches.</p><p>As future work, we plan to investigate ontology integration approaches addressing only the operational level and verify if the concerns at this level are different than the ones we identified in this study. Moreover, considering the gaps we perceived from this study, we have proposed a goal-oriented systematic approach to develop ontologies based on integration and a framework to support our approach.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 -</head><label>1</label><figDesc>Figure 1 -Year and Publication VehicleRQ03.Which type of research has been done?-According to the classification presented in<ref type="bibr" target="#b22">(Wieringa et al., 2006)</ref> and considering that a publication can be classified in more than one type, all the analyzed publications were classified as Proposal of Solution. Eight of them ([P03], [P04], [P07], [P08], [P09], [P11], [P12], [P15]) (53%) are also Validation Research, because they use proof of concept, experiment, prototype or something similar to evaluate the proposal. No publication was classified as Evaluation Research, which means that none of the proposals have been applied in a real environment.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>The last refers to operations involving terminology, definition and documentation of concepts to make the integrated ontology consistent. Five approaches(33%) ([P06], [P10], [P11], [P13], [P15]) use similarity calculation, seven (47%) ([P04], [P05], [P07], [P08], [P09], [P12], [P14]) use semantic mappings and two ([P01], [P03]) (13%) apply integration operations. [P02] is the only approach combining different principles. It uses similarity calculation and semantic mappings.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>]) provide automatic solutions, four (27%) propose semiautomatic solutions ([P02], [P07], [P10], [P14]) three (20%) do not provide any computational assistance ([P01], [P03], [P05]). In ([P04],</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 2 Integration approaches.</head><label>2</label><figDesc></figDesc><table><row><cell>ID</cell><cell>Reference</cell><cell>Description</cell></row><row><cell>[P01]</cell><cell></cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 3 -Steps of the ontology integration approaches</head><label>3</label><figDesc>Establish the semantic relations between two geological ontologies, Merge synonyms in the overlapping set as a new concept, Add other concepts from source ontologies that do not belong to the semantic overlapping set, Add semantic relation (hyponym) in the semantic overlapping set, Add new semantic relations to the resulting ontology [P09] Source ontologies evaluation, Merging parameters definition, Equivalence mapping, Mapping filtering, Ontology merging using filtering results. [P10] Candidate ontologies identification, Concepts evaluation, Source ontologies identification and categorization, Knowledge modules modification, Connection points identification, Basic ontology building, Knowledge modules integration [P11] Identify alignment between entities, Find ontologies portions that overlap and integrate the ontologies, Perform the pruning of the integrated ontology through redundancy detection, Check the integrated ontology consistence [P12] Mapp the two input ontologies, Merge input ontologies in a super ontology [P13] Ontologies comparison, Concepts integration, Result checking, Interpretation,</figDesc><table><row><cell>ID</cell><cell>Title</cell></row><row><cell cols="2">[P01] Identify integration possibility, Identify modules, Identify ontological commitments and</cell></row><row><cell></cell><cell>assumptions, Identify knowledge to be represented, Identify candidate ontologies, Obtain</cell></row><row><cell></cell><cell>candidate ontologies, Study candidate ontologies, Select candidate ontologies, Apply</cell></row><row><cell></cell><cell>integration operations, Analyze the resulting ontology</cell></row><row><cell cols="2">[P03] Add top level concepts to both ontologies, Add intermediate concepts, Add more specific</cell></row><row><cell></cell><cell>concepts, Include attributes and relationships</cell></row><row><cell cols="2">[P04] Find ontology concepts and service descriptions to be integrated, Create new relationships</cell></row><row><cell></cell><cell>with the descriptions and related concepts</cell></row><row><cell cols="2">[P05] Find correspondences, Mapping, Merging</cell></row><row><cell cols="2">[P06] Receive ontologies to be integrated, Perform similarity calculation of the ontology concepts,</cell></row><row><cell></cell><cell>Merge the ontologies top-level concepts, Merge the subsequent concepts</cell></row><row><cell cols="2">[P07] Ontology alignment, Ontology merging</cell></row><row><cell cols="2">[P08] Ontology</cell></row><row><cell></cell><cell>matching</cell></row><row><cell cols="2">[P14] Ontology structure definition, Ontology selection for reuse, Addition of new information to the</cell></row><row><cell></cell><cell>ontology, Ontology integration</cell></row><row><cell cols="2">[P15] Semantic similarity calculation, Merging of concepts, Knowledge model building based on</cell></row><row><cell></cell><cell>network, Model decomposition in blocks, Blocks rebuilding using semantic mappings between</cell></row><row><cell></cell><cell>the concepts, Integrated ontology generation</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 Workshop Conference Journal</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgment</head><p>This research is funded by the Brazilian Research Funding Agency CNPq (461777/2014-2 and 407235/2017-5), CAPES (23038.028816/2016-41), and FAPES (69382549/2014).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Constructing an enterprise ontology for an automotive supplier</title>
		<author>
			<persName><forename type="first">E</forename><surname>Blomqvist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Öhgren</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Eng. Appl. Artif. Intell</title>
		<imprint>
			<biblScope unit="volume">21</biblScope>
			<biblScope unit="page" from="386" to="397" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Integration of ontologies in scope of model and conceptual semantics: Modified approach</title>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">V</forename><surname>Bova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">V</forename><surname>Kureichik</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Lezhebokov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">9th Int. Conf. on Application of Information and Communication Technologies, AICT</title>
				<imprint>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="156" to="160" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">An approach to ontology integration for ontology reuse in knowledge based digital ecosystems</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">G</forename><surname>Caldarola</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Picariello</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">M</forename><surname>Rinaldi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Management of Computational and Collective intElligence in Digital EcoSystems</title>
				<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="1" to="8" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">A proposal for a geographic ontology merging methodology</title>
		<author>
			<persName><forename type="first">S</forename><surname>Châabane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Jaziri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Gargouri</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the 2009 Int. Conf. on the Curr. Trends in Inf. Tech., CTIT</title>
				<meeting>of the 2009 Int. Conf. on the Curr. Trends in Inf. Tech., CTIT</meeting>
		<imprint>
			<date type="published" when="2009">2009. 2009</date>
			<biblScope unit="page" from="202" to="207" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Ontology-Based Knowledge Integration for Distributed Product Knowledge Service</title>
		<author>
			<persName><forename type="first">Y.-M</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y.-J</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C.-C</forename><surname>Wen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H.-C</forename><surname>Chu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">World Congress on Engineering ans Computer Science, WCECS, vols I and II</title>
				<imprint>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="1197" to="1202" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">A unified semantic ontology for energy management applications</title>
		<author>
			<persName><forename type="first">J</forename><surname>Cuenca</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Larrinaga</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Curry</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="86" to="97" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Ontology design patterns</title>
		<author>
			<persName><forename type="first">A</forename><surname>Gangemi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Presutti</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Handbook on Ontologies</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="221" to="243" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Generating new service concepts based on ontology integration</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Geum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Suh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Oh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the 4th IEEE Int. Conf. Conference on Management of Innovation and Technology, ICMIT</title>
				<meeting>of the 4th IEEE Int. Conf. Conference on Management of Innovation and Technology, ICMIT</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="878" to="883" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Towards ontological foundations for the conceptual modeling of events</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>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">A</forename><surname>Falbo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">S S</forename><surname>Guizzardi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P A</forename><surname>Almeida</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">LNCS</title>
		<imprint>
			<biblScope unit="page" from="327" to="341" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Tool support for the integration of light-weight ontologies</title>
		<author>
			<persName><forename type="first">T</forename><surname>Heer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Retkowitz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Kraft</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lect. Notes Bus. Inf. Process</title>
		<imprint>
			<biblScope unit="page" from="175" to="187" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Geo-ontology integration based on category theory</title>
		<author>
			<persName><forename type="first">L</forename><surname>Hu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">2010 International Conference on Computer Design and Applications</title>
				<meeting><address><addrLine>ICCDA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2010">2010. 2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">CreaDO -A methodology to create domain ontologies using parameter-based ontology merging techniques</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">P</forename><surname>Juárez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">E</forename><surname>Esquivel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">M</forename><surname>Rebollar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 10th Mexican Int. Conf. on Artifical Intelligence and Applications, MICAI -Proceedings of Special Session</title>
				<meeting>10th Mexican Int. Conf. on Artifical Intelligence and Applications, MICAI -eedings of Special Session</meeting>
		<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="23" to="28" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Guidelines for performing Systematic Literature Reviews in Software Engineering</title>
		<author>
			<persName><forename type="first">B</forename><surname>Kitchenham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Charters</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Engineering</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<date type="published" when="1051">2007. 1051</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">An integration-oriented ontology development methodology to reuse existing ontologies in an ontology development process</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">K</forename><surname>Leung</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">K</forename><surname>Lau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Fan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Tsang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 13th Int. Confrence Inf. Integr. Web-Based Appl. Serv</title>
				<meeting>13th Int. Confrence Inf. Integr. Web-Based Appl. Serv</meeting>
		<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="174" to="181" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">An approach to ontologies integration</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Lv</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 8th Int. Conf. n Fuzzy Systems and Knowledge Discovery</title>
				<meeting>8th Int. Conf. n Fuzzy Systems and Knowledge Discovery</meeting>
		<imprint>
			<date type="published" when="2011">2011. 2011</date>
			<biblScope unit="page" from="1262" to="1266" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">A New Method for Ontology Merging based on Concept using WordNet</title>
		<author>
			<persName><forename type="first">C</forename><surname>Miyoung</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Kim</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">8th Int. Conf. Adv. Commun. Technol</title>
				<meeting><address><addrLine>ICACT</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2006">2006. 2006. 2006</date>
			<biblScope unit="page" from="1573" to="1576" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Ontology selection ranking model for knowledge reuse</title>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Oh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Ahn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Expert System Applications</title>
		<imprint>
			<biblScope unit="volume">38</biblScope>
			<biblScope unit="page" from="5133" to="5144" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">An intelligent system approach for integrating anatomical ontologies</title>
		<author>
			<persName><forename type="first">P</forename><surname>Petrov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Krachunov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Todorovska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Vassilev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Biotechnol. Equip</title>
		<imprint>
			<biblScope unit="volume">26</biblScope>
			<biblScope unit="page" from="3173" to="3181" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Some Issues on Ontology Integration</title>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">S</forename><surname>Pinto</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P</forename><surname>Martins</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Praxis</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="page" from="1" to="12" />
			<date type="published" when="1994">1999. 1994</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">A methodology for ontology integration</title>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">S</forename><surname>Pinto</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P</forename><surname>Martins</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. Int. Conf. on Knowledge Capture KCAP 2001</title>
				<meeting>Int. Conf. on Knowledge Capture KCAP 2001</meeting>
		<imprint>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page">131</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Reusing ontology design patterns in a context ontology network</title>
		<author>
			<persName><forename type="first">M</forename><surname>Poveda Villalon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2010">2010. 2010</date>
			<biblScope unit="volume">671</biblScope>
			<biblScope unit="page" from="35" to="49" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Semantic Management: Application of Ontologies for the Integration of Management Information Models</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E L</forename><surname>Vergara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">A</forename><surname>Villagrá</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Berrocal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">I</forename><surname>Asensiot</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Pignaton</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Integ. Net. Manag. VIII</title>
				<meeting><address><addrLine>Boston, MA</addrLine></address></meeting>
		<imprint>
			<publisher>Springer US</publisher>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="131" to="134" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Requirements engineering paper classification and evaluation criteria: a proposal and a discussion</title>
		<author>
			<persName><forename type="first">R</forename><surname>Wieringa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Mead</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Rolland</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Requirements Engineering</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="102" to="107" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<monogr>
		<author>
			<persName><forename type="first">C</forename><surname>Wohlin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Runeson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Höst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Ohlsson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Regnell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Wesslén</surname></persName>
		</author>
		<title level="m">Experimentation in software engineering</title>
				<meeting><address><addrLine>Berlin Heidelberg, Germany</addrLine></address></meeting>
		<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
	<note>Experimentation in Software Engineering</note>
</biblStruct>

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