<?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">Semantic Interactive Ontology Matching: Synergistic Combination of Techniques to Improve the Set of Candidate Correspondences</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jomar</forename><surname>Da Silva</surname></persName>
							<email>jomar.silva@uniriotec.br</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">Graduated Program in Informatics</orgName>
								<orgName type="department" key="dep2">Department of Applied Informatics</orgName>
								<orgName type="institution">Federal University of the State of Rio de Janeiro (UNIRIO)</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Fernanda</forename><surname>Araujo Baião</surname></persName>
							<email>fernanda.baiao@uniriotec.br</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">Graduated Program in Informatics</orgName>
								<orgName type="department" key="dep2">Department of Applied Informatics</orgName>
								<orgName type="institution">Federal University of the State of Rio de Janeiro (UNIRIO)</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Kate</forename><surname>Revoredo</surname></persName>
							<email>katerevoredo@uniriotec.br</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">Graduated Program in Informatics</orgName>
								<orgName type="department" key="dep2">Department of Applied Informatics</orgName>
								<orgName type="institution">Federal University of the State of Rio de Janeiro (UNIRIO)</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jérôme</forename><surname>Euzenat</surname></persName>
							<email>jerome.euzenat@inria.fr</email>
							<affiliation key="aff1">
								<orgName type="institution" key="instit1">Univ. Grenoble Alpes</orgName>
								<orgName type="institution" key="instit2">Inria</orgName>
								<orgName type="institution" key="instit3">CNRS</orgName>
								<orgName type="institution" key="instit4">Grenoble INP</orgName>
								<orgName type="institution" key="instit5">LIG</orgName>
								<address>
									<postCode>F-38000</postCode>
									<settlement>Grenoble</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Semantic Interactive Ontology Matching: Synergistic Combination of Techniques to Improve the Set of Candidate Correspondences</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">EE056E24D0FA210C705D0A81FC9267C8</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T09:46+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 matching</term>
					<term>Wordnet</term>
					<term>interactive ontology matching</term>
					<term>ontology alignment</term>
					<term>interactive ontology alignment</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Ontology Matching is the task of finding a set of entity correspondences between a pair of ontologies, i.e. an alignment. It has been receiving a lot of attention due to its broad applications. Many techniques have been proposed, among which the ones applying interactive strategies. An interactive ontology matching strategy uses expert knowledge towards improving the quality of the final alignment. When these strategies are based on the expert feedback to validate correspondences, it is important to establish criteria for selecting the set of correspondences to be shown to the expert. A bad definition of this set can prevent the algorithm from finding the right alignment or it can delay convergence. In this work we present techniques which, when used simultaneously, improve the set of candidate correspondences. These techniques are incorporated in an interactive ontology matching approach, called ALINSyn. Experiments successfully show the potential of our proposal.</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>Ontology matching seeks to discover correspondences between entities of different ontologies <ref type="bibr" target="#b0">[1]</ref>. Ontology matching can be processed manually, semi-automatically or automatically <ref type="bibr" target="#b0">[1]</ref>. Among the semi-automatic approaches, the ones that follow an interactive strategy stand out, considering the knowledge of domain experts through their participation <ref type="bibr" target="#b1">[2]</ref>. The involvement of a domain expert is not always possible, as it is an expensive, scarce and time-consuming resource. However, when possible, better results have been achieved compared with automatic approaches.</p><p>An expert can be involved by giving his feedback to a correspondence, indicating whether or not it belongs to the alignment. Therefore, defining the set of correspondences to show to the expert is one of the problems of these interactive techniques. If this set is not well defined, the final alignment may be imprecise or incomplete, or convergence to a good alignment can be delayed. Therefore, the scientific problem addressed in this paper is how to improve the set of correspondences to receive expert feedback.</p><p>This paper proposes ALINSyn, an approach that uses two techniques -a semantic and a structural -for the improvement of a given set of candidate correspondences. The semantic technique works by temporarily removing correspondences from the set of candidate correspondences. The structural technique interactively places part of the correspondences taken by the semantic technique back in the set of candidate correspondences. ALINSyn uses techniques used in the ALIN <ref type="bibr" target="#b12">[13]</ref> system, that participated in OAEI 2016.</p><p>To evaluate ALINSyn, we defined ALINBasic, a basic ontology matching algorithm that generates and use a set of candidate correspondences to do the matching. Each of the two ALINSyn techniques was added to ALINBasic in order to modify the set of candidate correspondences generated by it, and the obtained alignments were compared. ALINSyn was also compared to state-of-the-art interactive ontology matching systems, showing the potential of our proposal.</p><p>This paper is structured as follows: Section 2 describes interactive ontology matching, Section 3 describes the ALINBasic algorithm, section 4 describes ALINSyn approach, by explaining its two steps, in section 5 the evaluation of the approach is made and the section 6 is the conclusion.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Interactive Ontology Matching</head><p>An ontology O is represented as a labeled graph G = (V, E, vlabel, elabel). The set of vertices V contains ontology entities such as concepts and properties. Edges in E (E ⊆ V × V ) represent structural relationships between entities. The edge labeling function elabel, which maps an edge (v, v) ∈ E to a subset of the set SL of structural labels, which in turn specify the nature of the structural relationships between entities (e.g., subclassOf). Let LL denote the set of lexical labels associated with entities (e.g., name, documentation). Finally, the vertex labeling function, vlabel : V × LL → String, maps a pair (e, l) ∈ V × LL to a string corresponding to the value of the lexical label l (e.g., name) associated with the entity e <ref type="bibr" target="#b2">[3]</ref>.</p><p>Given two ontologies O and O', an ontology matching is the process that aims to finding a set of correspondences (e, e'), where e and e' are entities in O and O', respectively. Interactive ontology matching takes advantage of user feedback to perform ontology matching.</p><p>Within the set of all possible correspondences between the entities of two ontologies, in the context of the interactive ontology matching, we distinguish two types of correspondences:</p><p>-Candidate correspondences are those possible correspondences that have been selected to be presented to the expert but have not yet received decision, -Classified correspondences are those possible correspondences that have been selected to be presented to the expert and have received decision.</p><p>There are similarity measures, denoted sim, which map the possible correspondence (e, e') ∈ O×O' to a real number in [0, 1].</p><p>According to Meilicke and Stuckenschmidt <ref type="bibr" target="#b3">[4]</ref>, ontology matching algorithms that are based on the analysis of entity names usually have two phases:</p><p>-In the first phase, there is the creation of a set of candidate correspondences.</p><p>To reduce the need to classify all possible correspondences (all pairs of entities) between two ontologies as belonging or not to alignment, the algorithm selects a subset called set of candidate correspondences; -In the second phase, each correspondence in the set of candidate correspondences is classified by the ontology matching algorithm. In an interactive strategy, at least part of these correspondences is classified by the expert, and the other part can be classified by some automatic technique.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">ALINBasic Algorithm</head><p>When the ontology matching is done interactively, we have two quality measures that are conflicting: the number of interactions with the expert and the quality of the generated alignment. It is interesting that a technique to be used in an algorithm of ontology matching can improve one of these qualities without worsening the other in an accentuated way. That is, to decrease the number of interactions without decreasing proportionally the quality of the generated alignment, or to increase the quality of the generated alignment without increasing proportionally the number of interactions with the expert. In this paper two techniques will be presented, which used alone, cannot increase one of the qualities without considerably worsening the other. The first one, the semantic technique, decreases the number of interactions with the expert, but greatly decrease the quality of the generated alignment. The other, structural technique, enhances the quality of the generated alignment, but increasing a lot the number of interactions with the expert. But when used together, they can mitigate the disadvantages of each other, reducing the number of interactions without dramatically decreasing the quality of the generated alignment.</p><p>To evaluate the results of the two proposed techniques, three algorithms will be compared. An algorithm without the inclusion of any of the two techniques, called ALINBasic, a second algorithm, with the inclusion of the semantic technique, called ALINSem, and a third one with the inclusion of both the semantic and structural techniques, called ALINSyn. The two techniques are included in the algorithms as steps of these algorithms, so ALINSem is equivalent to the ALINBasic algorithm plus a semantic step that implements the semantic technique, and the ALINSyn algorithm is equivalent to the ALINSem algorithm plus a structural step that implements the structural technique.</p><p>The ALINBasic algorithm has two phases, as described by Meilicke and Stuckenschmidt <ref type="bibr" target="#b3">[4]</ref>. The first phase selects candidate correspondences to be presented to the user. The second phase presents the selected candidate correspondence to the user and assigns them to the classified correspondences. Hence, in the end there are no candidate correspondences left.</p><p>In the phase of generating the candidate correspondences, only class correspondences, not property correspondences, are chosen, therefore, the ALINBasic algorithm finds only class correspondences.</p><p>The first phase of ALINBasic (Algorithm 1) will use the stable marriage algorithm with size list limited to 1 <ref type="bibr" target="#b4">[5]</ref> <ref type="bibr" target="#b5">[6]</ref>, where the pair will be formed by classes of the two ontologies to be aligned. Correspondences will be ordered by decreased similarity.</p><p>The stable marriage algorithm will be executed six times, each time with a different similarity metric (Jaccard, Jaro-Winkler, n-Gram, Wu-Palmer, Jiang-Conrath and Lin) and the result of the six executions will form a set of correspondences by the union of the six formed sets (Steps 1 to 4 of Algorithm 1). The process of selecting the similarity metrics was based on two criteria: available implementations and the result of these metrics in assessments, such as those carried out in <ref type="bibr" target="#b6">[7]</ref> and <ref type="bibr" target="#b7">[8]</ref>. Wu-Palmer, Jiang-Conrath and Lin are metrics that require a taxonomy to be computed <ref type="bibr" target="#b6">[7]</ref>, this taxonomy being provided, in this algorithm, by Wordnet.</p><p>From the set of correspondences formed by the union of the six sets all correspondence whose classes have exactly the same name will be classified as true (Step 5 of Algorithm 1). The correspondences selected by the running of stable marriage algorithm and not automatically classified will be the candidate correspondences (Step 6 of Algorithm 1).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Algorithm 1 Candidate correspondence generation</head><p>Input: Two ontologies to be aligned Output: Candidate correspondences 1: for Each one of the similarity metrics: Jaccard, Jaro-Winkler, n-Gram, Wu-Palmer, Jiang-Conrath and Lin do</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2:</head><p>Run stable Marriage Algorithm forming the set A sim (being sim the corresponding similarity metric) 3: end for</p><formula xml:id="formula_0">4: Let A = A Jaccard ∪ A Jaro-Winkler ∪ A n-Gram ∪ A Wu-Palmer ∪ A Jiang-Conrath ∪</formula><p>A Lin 5: Let B = Correspondences, from A, automatically classified as true by the fact that their entities have the same name 6: Set of candidate correspondences = A -B Then begins the classification phase of the candidate correspondences of the ALINBasic. At this phase all the candidate correspondences will be presented to the expert to receive his feedback.</p><p>For this, the concept of interaction with the expert will be used. An interaction with the expert corresponds to a question asked about at most three correspondences, as long as they pair-wisely have at least one of the entities in common. This is compliant with the OAEI definition <ref type="bibr" target="#b9">[10]</ref>. For example, if the following correspondences are shown to the expert at the same time (Con-ferenceChair,Chair), (Chairman,Chair) and (Chairman,AssociatedChair), they will be counted as only one interaction since each correspondence has at least one entity of another correspondence. The number of interactions will be used as a comparison criterion between the various executions shown in this paper.</p><p>The ALINBasic algorithm can be seen in Algorithm 2.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Algorithm 2 ALINBasic</head><p>Input: Two ontologies to be aligned Output: Alignment between the two ontologies 1: Run candidate correspondence generation (Algorithm 1) 2: for Each candidate correspondence do 3:</p><p>Receive feedback (the candidate correspondence is transformed to classified correspondence) 4: end for 4 ALINSyn Algorithm</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Improving the Set of Candidate Correspondences</head><p>The objective of the ALINSyn algorithm is to decrease the number of interactions with the expert without decreasing in the same proportion the quality of the generated alignment. To achieve this objective, two steps, one semantic step and one structural step, are added to the ALINBasic algorithm to improve the set of candidate correspondences.</p><p>We first introduce another type of correspondence:</p><p>-Temporarily suspended correspondences are correspondences that are no longer candidate correspondences because of the semantic step. These correspondences can once again be candidate correspondences after the structural step.</p><p>The semantic step transforms some candidate correspondences to temporarily suspended correspondences. The structural step can transform some temporarily suspended correspondences to candidate correspondences again. At the end of the non-interactive phase, by the use of the semantic step, all candidate correspondences that are not semantically equivalent will be transformed to temporarily suspended correspondences. In the interactive phase, by the use of the structural step, after each interaction with the expert, the expert's feedback can transform temporarily suspended correspondences in candidate correspondences if they have a particular structural relationship with a candidate correspondence that received positive feedback.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Semantic Step</head><p>The action of this step is to transform all candidate correspondences with semantically different entity names to temporarily suspended correspondences. The step will be added to the ALINBasic algorithm at the end of the generation phase.</p><p>The semantic step uses Wordnet. Wordnet consists of synonym sets called synsets <ref type="bibr" target="#b8">[9]</ref>. A synset denotes a group of terms with the same meaning. The same term may appear in various synsets, as long as it has several meanings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Comparison of entity names</head><p>A head noun of a phrase is a noun to which all other terms are dependent <ref type="bibr" target="#b10">[11]</ref>. Only correspondences relating entities whose name head nouns are in the same Wordnet synset will remain in the set of candidate correspondences after the semantic step. Before comparing the two entity names, a pre-processing step is necessary in order to extract the correct terms to be compared. An entity name can be atomic or composed. In the latter case, our approach searches for the head noun, and only this head noun will be used to compare the two entities. The rule we used for detection of head noun can be summarized as follows:</p><p>1. If the name contains a preposition (e.g. HeadOfDepartment) then the head noun is the token before the preposition.</p><p>2. Otherwise the head noun is the last token in the name. Choose the head noun of each entity of the name of the correspondence</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3:</head><p>Put the head noun of each name in the canonical form 4:</p><p>if The two head nouns are not in the same wordnet synset then</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>5:</head><p>Transform the candidate correspondence to temporarily suspended correspondence 6: end if 7: end for Example of the semantic step The semantic step can be seen in the Algorithm 3. To illustrate the semantic step we assume that we have the candidate correspondences selected by Algorithm 1 shown in Table <ref type="table" target="#tab_0">1</ref>. The first correspondence to be analyzed will be (Author, Regular Author) (step 1 of Algorithm 3). The head noun of Author is Author, since it has only one word. The head noun for Regular Author is Author, because it does not have a preposition and the last word is Author (step 2). The two head nouns are already in canonical form (step 3) and as they are the same word they are in the same synset, so they are not transformed to temporarily suspended correspondences. The second correspondence in the table is the correspondence (Chairman,Chair) (step 1). Chairman is considered a word because a term is only divided into words if it has hyphen, white space or is in camelcase (step 2). Since the two are in the canonical form (step 3) of the word their synsets are compared in Wordnet, and they are different. It is important to note that the most common meanings of words are searched for in wordnet, so Chair is the object of sitting and not Boss. Therefore this correspondence will be transformed to temporarily suspended correspondences (step 5).</p><p>The result after following these steps for all correspondences is shown in Table <ref type="table" target="#tab_0">1</ref>, in the column 'after the semantic step'.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Algorithm 4 ALINSyn</head><p>Input: Two ontologies to be aligned Output: Alignment between the two ontologies Receive feedback (the candidate correspondence is transformed to classified correspondence)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>5:</head><p>Run structural Step (Algorithm 5 ) 6: end for With the inclusion of the semantic step, the algorithm will be called ALIN-Sem. As an illustration, this algorithm is the same as the algorithm ALINSyn (Algorithm 4) without the inclusion of step 5 (Run structural step). The results of ALINSem will be compared to the results of ALINSyn with the objective of verifying if the combined use of the semantic step and the structural step improves the result achieved by the use of the semantic step alone. Transform the temporarily suspended correspondence to candidate correspondence 4:</p><p>end if 5: end for</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Structural Step</head><p>When only the semantic step is applied, experiments showed that the number of interactions with the expert were reduced, i.e. convergence was reached faster, however the final alignment lost in quality. This is because some true correspondences have been taken from the set of candidate correspondences because of semantic step. The main goal of the structural step is to recover part of the quality lost through the use of the semantic step by transforming some temporarily suspended correspondences again to candidate correspondences.</p><p>At each iteration, all temporarily suspended correspondences that are formed by subclasses of the classes of the correspondences that received positive feedback from the expert are transformed again to candidate correspondences. Tests were performed again using the two techniques, which showed that the use of both techniques makes the number of interactions decrease considerably, but with a much lower quality loss, in relation to the results obtained with the ALINBasic algorithm. The structural step can be seen in Algorithm 5. To illustrate the technique let us assume the situation described in Figure <ref type="figure" target="#fig_2">1</ref>, where Co author is a subclass of Person in the cmt ontology and Regular author is a subclass of Person in the Conference ontology. Let us assume that the correspondence A (Person, Person) is a candidate correspondence and correspondence B (Co author, Regular author) is a temporarily suspended correspondence. If the correspondence A receive positive feedback, the correspondence B by having its classes that are subclasses of the classes of A is transformed to candidate correspondence. The result of the structural step can be seen in Table <ref type="table" target="#tab_0">1</ref> in the column 'after the first run of the structural step'. With the inclusion of the structural step in the interactive phase, the algorithm is called ALINSyn and can be seen in the Algorithm 4.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Evaluation Overview and Designed Analysis</head><p>The goal of the ALINSyn approach is to reduce the number of interactions with the expert without greatly diminishing the quality of the generated alignment. Thus a first research question is: RQ1: Does the semantic step allow the ontology matching strategy to decrease the number of interactions with the expert? This question is answered with the use of the semantic step in the ALINBasic algorithm, as we see in the section "Analysis of the Results", which shows that the number of interactions with the expert has been reduced, but with a great drop in quality. That is why it is important to address other research questions.</p><p>RQ2: Can the expert feedback reduce the quality loss by the use of the semantic step? RQ3: Does the use of both, semantic step and structural step together, generate an alignment with quality and number of interactions compatible with the state of the art proposals?</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1">Conference dataset</head><p>Results obtained in the interactive matching of OAEI 2016 using the conference dataset were used to compare with the state of the art.</p><p>The OAEI interactive track is performed with percentages of expert correctness, from 70% to 100%. This paper has taken into consideration, for the evaluation of the execution of the ALINSyn and of other tools, 100% of correctness by the expert.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2">Analysis of the Results</head><p>After using the semantic step the results presented in Table <ref type="table" target="#tab_2">2</ref> (ALINSem row) were reached, which shows that the use of the semantic step decreases the number of expert interactions, which responds to 'RQ1: Does the semantic step allow the ontology matching strategy to decrease the number of iterations with the expert ?', but there has been a sharp drop in quality, which shows the need to answer the question 'RQ2: Can the expert feedback reduce the quality loss by using the semantic step?'.</p><p>The recovery in the quality of the generated alignment was attempted by the use of structural step. After the inclusion of this new step the results shown in Table <ref type="table" target="#tab_2">2</ref> (ALINSyn row) were reached. That shows that the goal of the ALIN-Syn was achieved using the two techniques. The number of interactions with the expert decreased greatly, from 619 to 219, with the quality decreasing proportionally much less, the f-measure was from 0.79 to 0.75, what responds to RQ2: Can the expert feedback reduce the quality loss by the use of the semantic step ?. The result achieved is due to the combined effect of the joint use of the two techniques.</p><p>If we use only the semantic step we have a good decrease in the number of interactions with the expert, but with a sharp drop in quality. The subsequent use of the structural step, interactively, causes some of the lost quality to be recovered.</p><p>If we use only the structural step, without using the semantic step before, with all possible correspondences, not only the temporarily suspended correspondences, we would have an increase in quality, but a large number of correspondences would be added to the set of candidate correspondences, which would make the number of interactions with the expert too large (Table <ref type="table" target="#tab_2">2</ref>, ALINStr row). The transformation of candidate correspondences into temporarily suspended correspondences, through the semantic step, and the search, by the structural step, only among the temporarily suspended correspondence reduces the search space, which means that the number of interactions with the expert do not go up explosively.</p><p>The combined use of the two techniques results in a more balanced result, with a reduction in the number of interactions without a big loss of quality ( Table <ref type="table" target="#tab_2">2</ref>, ALINSyn row ). OAEI provides a comparison among tool performance in the ontology matching process each year, and one of the ontology groups used is the conference dataset used in this paper <ref type="bibr" target="#b11">[12]</ref>. Table <ref type="table" target="#tab_3">3</ref> shows a comparison of some tools that participated in the OAEI 2016 interactive conference track. NI means number of interactions. In each interaction there can be up to three questions. "%" is the ratio of the number of interactions to the number of possible correspondences among all the alignments of the conference dataset. Table <ref type="table" target="#tab_3">3</ref> compares the performance of ALINSyn with some interactive tools that participated in OAEI 2016, with the expert hitting 100% of the answers in relation to the conference dataset. The use of the techniques shown in this work generates a high quality alignment, in cases where the expert does not make errors, what responds to 'RQ3: Does the use of the two techniques, semantic step and structural step together, generate an alignment with quality and number of interactions compatible with the state of the art ?'. The use of the two techniques combined puts ALINSyn among the best tools in the evaluation of OAEI 2016, when the expert hits 100% of the interactions. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusion</head><p>Progress in information and communication technologies has made a large number of data repositories available, but with a great deal of semantic heterogeneity, which makes it difficult to integrate. A process that has been used to solve this problem is the ontology matching, which tries to discover the existing correspondences between the entities of two distinct ontologies, which in turn structures the concepts that define the data stored in each repository. This work presented an interactive approach for ontology matching, based on manipulation of the set of candidate correspondences with techniques to decrease the number of interactions with the expert, without greatly reducing the quality of the alignment.</p><p>Two techniques were combined, one semantic and the other structural. The goal of the semantic technique was to decrease the number of interactions with the expert. The structural technique came in support of the semantic technique, and its objective was to decrease the quality loss resulting from the decrease in the number of interactions with the expert.</p><p>In order to evaluate if the techniques generated a decrease in the number of interactions without significantly lowering the quality, the executions of a basic algorithm with and without the techniques were compared, which showed that the techniques, when combined, reach their goal.</p><p>In addition, the quality of the alignment provided by the ALINSyn approach was compared to state of the art tools that have participated in the track of interactive ontology matching in OAEI 2016. The results obtained show that ALINSyn generates an alignment with a good quality in comparison to other tools, with regard to precision, recall and f-measure, when the expert never makes mistakes, keeping the number of interactions within the range achieved by the other tools.</p><p>The third author was partially funding by project PQ-UNIRIO N01/2017 (" Aprendendo, adaptando e alinhando ontologias:metodologias e algoritmos.") and CAPES/PROAP.</p><p>The fourth author was partially funding by 'CNPq Special visiting researcher grant (314782/2014-1)'.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Algorithm 3 1 :</head><label>31</label><figDesc>Semantic step Input: Candidate correspondences Output: Temporarily suspended correspondences (ex-candidate correspondences) for Each candidate correspondence do 2:</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Algorithm 5</head><label>5</label><figDesc>Structural Step Input: Temporarily suspended Correspondences, Classified correspondences Output: Candidate Correspondences (ex-temporarily suspended correspondences) 1: for Each temporarily suspended correspondence do 2:if The two classes of the temporarily suspended correspondence are subclasses of classes of a correspondence classified as true then 3:</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Correspondences with classes that are subclasses of other correspondence classes</figDesc><graphic coords="8,250.99,485.26,113.38,88.27" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>Correspondences before and after the semantic step, and after the first run</figDesc><table><row><cell>of structural step</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>e</cell><cell>e'</cell><cell>before semantic step</cell><cell>after semantic step</cell><cell>after the first run of structural step</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 2 .</head><label>2</label><figDesc>Comparison between different matching executions</figDesc><table><row><cell cols="4">NI Precision F-measure Recall</cell></row><row><cell>ALINBasic 619</cell><cell>0.92</cell><cell>0.79</cell><cell>0.70</cell></row><row><cell>ALINSem 152</cell><cell>0.90</cell><cell>0.69</cell><cell>0.57</cell></row><row><cell cols="2">ALINStr 3539 0.93</cell><cell>0.84</cell><cell>0.78</cell></row><row><cell>ALINSyn 219</cell><cell>0.91</cell><cell>0.75</cell><cell>0.65</cell></row><row><cell cols="4">5.3 Comparison among Tools that Participated in the OAEI</cell></row><row><cell cols="2">Interactive Conference Track</cell><cell></cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 3 .</head><label>3</label><figDesc>Comparison between some OAEI 2016 conference dataset interactive tracking tools and ALINSyn</figDesc><table><row><cell></cell><cell cols="4">Number of questions NI % Precision F-measure Recall</cell></row><row><cell>AML</cell><cell>270</cell><cell>271 0.215 0.912</cell><cell>0.799</cell><cell>0.711</cell></row><row><cell>ALINSyn</cell><cell>483</cell><cell>219 0.174 0.915</cell><cell>0.754</cell><cell>0.652</cell></row><row><cell>LogMap</cell><cell>142</cell><cell>142 0.113 0.886</cell><cell>0.723</cell><cell>0.610</cell></row><row><cell>XMap</cell><cell>4</cell><cell>4 0.003 0.837</cell><cell>0.681</cell><cell>0.574</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<title level="m">Ontology Matching -Second Edition</title>
				<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="2013">2013</date>
			<biblScope unit="volume">2</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Towards Evaluating Interactive Ontology Matching Tools</title>
		<author>
			<persName><forename type="first">H</forename><surname>Paulheim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hertling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Ritze</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lect. Notes Comput. Sci</title>
		<imprint>
			<biblScope unit="volume">7882</biblScope>
			<biblScope unit="page" from="31" to="45" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">One Size Does Not Fit All: Customizing Ontology Alignment Using User Feedback</title>
		<author>
			<persName><forename type="first">S</forename><surname>Duan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Fokoue</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Srinivas</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">Lecture Notes in Computer Science (LNCS</title>
		<imprint>
			<biblScope unit="page" from="177" to="192" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">A New Paradigm for Alignment Extraction</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">CEUR Workshop Proc</title>
				<imprint>
			<date type="published" when="2015">2015</date>
			<biblScope unit="volume">1545</biblScope>
			<biblScope unit="page" from="1" to="12" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">College Admissions and the Stability of Marriage</title>
		<author>
			<persName><forename type="first">D</forename><surname>Gale</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">S</forename><surname>Shapley</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Am. Math. Mon</title>
		<imprint>
			<biblScope unit="volume">69</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="9" to="15" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Stable marriage with ties and bounded length preference lists</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">W</forename><surname>Irving</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">F</forename><surname>Manlove</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Omalley</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. Discret. Algorithms</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="213" to="219" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Design and Evaluation of Semantic Similarity Measures for Concepts Stemming from the Same or Different Ontologies object instrumentality</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">G M</forename><surname>Petrakis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Varelas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Hliaoutakis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Raftopoulou</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 4th Work. Multimed. Semant</title>
				<meeting>4th Work. Multimed. Semant</meeting>
		<imprint>
			<date type="published" when="2006">2006</date>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="page" from="233" to="237" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">String similarity metrics for ontology alignment</title>
		<author>
			<persName><forename type="first">M</forename><surname>Cheatham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lect. Notes Comput. Sci</title>
		<imprint>
			<biblScope unit="volume">8219</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="294" to="309" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
	<note>LNCS</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">A survey of exploiting WordNet in ontology matching</title>
		<author>
			<persName><forename type="first">F</forename><surname>Lin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Sandkuhl</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IFIP Int. Fed. Inf. Process</title>
				<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">276</biblScope>
			<biblScope unit="page" from="341" to="350" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Using the SEALS Client s Oracle in Interactive Matching</title>
		<author>
			<persName><forename type="first">D</forename><surname>Faria</surname></persName>
		</author>
		<ptr target="https://github.com/DanFaria/OAEISealsClient/blob/master/OracleTutorial.pdf" />
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Analysing ontological structures through name pattern tracking</title>
		<author>
			<persName><forename type="first">O</forename><surname>Svab-Zamazal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Svatek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lect. Notes Comput. Sci</title>
		<imprint>
			<biblScope unit="volume">5268</biblScope>
			<biblScope unit="page" from="213" to="228" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
	<note>LNAI</note>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Results of the Ontology Alignment Evaluation Initiative</title>
		<author>
			<persName><forename type="first">M</forename><surname>Achichi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cheatham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Dragisic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Faria</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ferrara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Flouris</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Fundulaki</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Harrow</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Ivanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Jimenez-Ruiz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Kuss</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Lambrix</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Leopold</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Meilicke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Montanelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Pesquita</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Saveta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Splendiani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Stuckenschmidt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Todorov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Trojahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Zamazal</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 11th Int. Work. Ontol. Matching co-located with 15th Int. Semant. Web Conf. (ISWC 2016)</title>
				<meeting>11th Int. Work. Ontol. Matching co-located with 15th Int. Semant. Web Conf. (ISWC 2016)<address><addrLine>Kobe, Japan</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2016-10-18">2016. Oct. 18, 2016. 2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">ALIN Results for OAEI</title>
		<author>
			<persName><forename type="first">J</forename><surname>Silva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">A</forename><surname>Baião</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Revoredo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">CEUR Workshop Proc</title>
		<imprint>
			<biblScope unit="volume">1766</biblScope>
			<date type="published" when="2016">2016. 2016</date>
		</imprint>
	</monogr>
</biblStruct>

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