<?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">ALIN Results for OAEI 2017</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>
						<title level="a" type="main">ALIN Results for OAEI 2017</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">198A6FCA79D855CB22C5D29597B9C3B0</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>ALIN is an ontology alignment system specialized in the interactive alignment of ontologies. Its main characteristic is the selection of correspondences to be shown to the expert, depending on the previous feedbacks given by the expert. This selection is based on semantic and structural characteristics. ALIN has obtained the alignment with the highest quality in the interactive tracking for Conference data set. This paper describes its configuration for the OAEI 2017 competition and discusses its results.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Presentation of the system</head><p>A large amount of data repositories became available due to the advances in information and communication technologies. Those repositories, however, are highly semantically heterogeneous, which hinders their integration. Ontology alignment has been successfully applied to solve this problem, by discovering correspondences between two distinct ontologies which, in turn, conceptually define the data stored in each repository. Among the various ontology alignment approaches that exist in the literature, interactive ontology alignment includes the participation of experts of the domain to improve the quality of the final alignment. This approach has proven more effective than non-interactive ontology alignment <ref type="bibr" target="#b0">[1]</ref>. ALIN is an ontology alignment system specialized in interactive alignment.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.1">State, purpose, general statement</head><p>ALIN is an ontology alignment system, specialized in the ontology interactive alignment, based primarily on linguistic matching techniques, using the Wordnet as external resource. After generating an initial set of correspondences ( called set of candidate correspondences, which are the correspondences selected to receive the feedback from the expert ), interactions are made with the expert, and to each interaction, the set of candidate correspondences is modified. The modification of the set of candidate correspondences is through the use of the structural analysis of ontologies and use of correspondence anti-patterns. The interactions continue until there are no more candidate correspondences left. ALIN was built with a special focus on the interactive matching track of OAEI 2017.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.2">Specific techniques used</head><p>The ALIN algorithm is shown in algorithm 1.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Algorithm 1 ALIN algorithm</head><p>Input: Two ontologies to be aligned Output: Alignment between the two ontologies 1: Loading of ontologies Choose correspondences to show to the expert</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>7:</head><p>Receive expert feedback to chosen correspondences and remove them of the set of candidate correspondences</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>8:</head><p>Remove correspondences in an correspondence anti-pattern from set of candidate correspondences</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>9:</head><p>Insert some data property and object property correspondences into set of candidate correspondences 10:</p><p>Insert some correspondences from the backup set into set of candidate correspondences 11: end while The steps of ALIN algorithm are the following: 1. Load of the ontologies with load of classes, object properties and data properties through the Align API <ref type="foot" target="#foot_0">1</ref> . For each entity some data are stored such as name and label. In the case of classes, their superclasses and disjunctions are saved. In the case of object properties the properties that are their hypernyms and their associated classes are saved. The classes of data properties are saved, too. ALIN does not use instances. The ALIN can only work with ontologies whose entity names are in English.</p><p>2. As an initial set of candidate correspondences a stable marriage algorithm with incomplete preference lists with maximum size of the list equals to 1, using linguistic metrics to sort the priority list was used <ref type="bibr" target="#b1">[2]</ref>. The list is sorted in decreasing order. For this algorithm only the correspondence whose first entity is in the list of second entity and vice-versa is selected. The linguist metrics used are Jaccard, Jaro-Winkler and n-Gram <ref type="bibr" target="#b2">[3]</ref> provided by Simmetrics API 2 and Resnick, Jiang-Conrath and Lin <ref type="bibr" target="#b2">[3]</ref> provide by HESML API<ref type="foot" target="#foot_2">3</ref> that use Wordnet. To use Wordnet the canonical form of the entity names is needed, therefore Stanford CoreNLP API<ref type="foot" target="#foot_3">4</ref> was used. The most frequent synsets of words are used to calculate semantic similarities. To find this synset is used the WS4J API <ref type="foot" target="#foot_4">5</ref> . The algorithm is run six times, once by each metric, and the result set is the union of results of each metric.</p><p>3. The value of the similarity metrics ( Resnick, Jiang-Conrath, Lin, Jaccard, Jaro-Winkler and n-Gram ) vary from 0 to 1 ( 1 is the maximum value ). When a correspondence in the set of candidate correspondences has all the six metrics with the maximum value, it is added to the final alignment and removed from the set of candidate correspondences. There are exceptions to this rule, some correspondences that fall into some structural patterns are not put on the final alignment and are not removed from the set of candidate correspondences.</p><p>4. The correspondences whose entities has one of its linguistic metrics less than a given threshold are removed from the set of candidate correspondences. These correspondences are put into a backup set, and can return to the set of candidate correspondences using structural analysis. The use of this technique can best be seen in <ref type="bibr" target="#b3">[4]</ref>, with the difference that, in <ref type="bibr" target="#b3">[4]</ref>, instead of applying a threshold, it was removed the classes of correspondences that were not in the same Wordnet synset.</p><p>5-11. At this point the interactions with the expert begin. The correspondences in the set of candidate correspondences are sorted by the sum of similarity metric values, with the greatest sum first. The correspondences are showed to the expert. The set of candidate correspondences has, at first, only correspondences of classes. When the expert answer one question, the set of candidate correspondences is modified. Correspondences ( besides the correspondence answered by expert ) can be removed and correspondences can be included into the set of candidate correspondences, depending on the answer of the expert. If the expert does not accept the correspondence it is removed from the set of candidate correspondences. But if the expert accepts the correspondence it is removed from the set of candidate correspondences and put in the final alignment.</p><p>At each interaction with the expert: -We remove from the set of candidate correspondences and disregard all the correspondences that are in correspondence anti-pattern <ref type="bibr" target="#b4">[5]</ref> with the correspondences accepted by the expert;</p><p>-We insert into the set of candidate correspondences, data property and object property correspondences related to the class correspondences accepted by the expert.</p><p>-We insert into the set of candidate correspondences, correspondences of the backup set ( step 4 ) whose both entities are subclasses of the classes of a correspondence accepted by expert.</p><p>This step continues until the set of candidate correspondences is empty. Detailed information about the ALIN system can be seen in the master thesis of Jomar da Silva 6 .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.3">Link to the system and parameters file</head><p>ALIN is available through Google drive ( https://drive.google.com/open?id=1myVtcRoKKdUDHQTKNKsomna8AFbukanf) as a package for running through the SEALS client.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Results</head><p>The system ALIN has been developed with its focus on interactive ontology alignment. The approach performs better when the number of data and object properties is proportionately large. ALIN considers properties associated to correspondent classes when selecting entities for user feedback, thus allowing for increased recall. When the number of properties in the ontologies is small, the system still generates a very precise alignment, but its recall tends to decrease.</p><p>Another characteristic of ALIN is its reliance on an interactive phase. The non-interactive phase of the system is quite simple, mainly based on maximum string similarity, specializing in maintaining a high precision without worrying about recall, generating initially a low f-measure. The recall increases in the interactive phase. Finally, ALIN is also not robust to users errors. The system uses a number of techniques that take advantage of the expert feedback to reach other conclusions. When the expert gives a wrong answer it is propagated generating other errors, thereby decreasing the f-measure.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Comments on the participation of the ALIN in non-interactive tracks</head><p>As expected the participation of ALIN in non-interactive alignment processes showed the following results: high precision and not so high recall, as can be seen in Anatomy track 7 shown in Table <ref type="table" target="#tab_2">1</ref>, where recall+ field refers to nontrivial correspondences found and Coherent field filled by + indicates that the generated alignment is consistent.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">INTERACTIVE ONTOLOGY ALIGNMENT: AN APPROACH BASED ON THE INTERACTIVE MODIFICATION OF THE SET OF CANDIDATE CORRESPONDENCES</head><p>. Available at http://www2.uniriotec.br/ppgi/bancode-dissertacoes-ppgi-unirio/ano-2017/interactive-ontology-alignment-an-approachbased-on-the-interactive-modification-of-the-set-of-candidate-correspondences/view Last accessed on Nov, 12, 2017. Regarding the Conference track<ref type="foot" target="#foot_5">8</ref> , as ALIN evaluates only the properties associated with classes already evaluated as belonging to the alignment, the alignment of the M2 type (which take into account only the properties of ontologies) were with the f-measure = 0, as can be seen in Table <ref type="table" target="#tab_0">2</ref>. As properties are evaluated only in the interactive phase in the ALIN, alignments of type M1 (only classes) remained with a higher recall than M3 (classes and properties), as can be seen in Table <ref type="table" target="#tab_0">2</ref>, because the reference alignments of type M3 contain properties besides classes. Anatomy track In this track the program ALIN showed the highest precision among the four evaluated tools when the error rate is zero, as can be seen in Table <ref type="table" target="#tab_4">3</ref>. When the error rate increases both the precision as the recall falls, reducing the f-measure, as can be seen in Table <ref type="table" target="#tab_5">4</ref>. This is expected and explained earlier.</p><p>As ontologies of the Anatomy Track contains almost no properties, some interactive techniques used in ALIN can not be utilized, like the selection of properties associated with classes with positive feedback. This has limited the increase in recall, which influenced the f-measure.</p><p>Conference Track In this track ALIN stood out, showing the greatest fmeasure among the four tools when the error rate is zero, as can be seen in 5, as with a loss of f-measure when the error rate increases, as can be seen in Table <ref type="table" target="#tab_7">6</ref>.</p><p>Other results, including results with other error rates can be seen on the OAEI 2017 9 page. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Comparison of the participation to ALIN in OAEI 2017 with his participation in OAEI 2016</head><p>The difference between the participation of ALIN in OAEI 2016 and his participation in OAEI 2017 was the use of the HESML API in 2017 instead of the WS4J API in calculating semantic similarities, which greatly increased the efficiency in these calculations. In ALIN's participation in OAEI 2016 <ref type="bibr" target="#b5">[6]</ref>, three semantic similarity metrics were used: Wu-Palmer, Jiang-Conrath and Lin. In ALIN's participation in OAEI 2017 the metrics Resnick, Jiang-Conrath and Lin were used. Resnick's exchange of Wu-Palmer is due to the fact that the Wu-Palmer metric in the HESML API took longer to execute than the same metric in the WS4J API. The Resnick metric proved to be much faster than the Wu-Palmer metric in the HESML API and according to <ref type="bibr" target="#b6">[7]</ref> as good as, so the Resnick metric was chosen to take Wu-Palmer's place in the implementation of ALIN at OAEI 2017. More information about the HESML API can be found in <ref type="bibr" target="#b7">[8]</ref>. In table <ref type="table" target="#tab_9">7</ref>. it can be seen that the ALIN runtime has decreased considerably with the use of the HESML API instead of the WS4J API. In the Anatomy interactive track of OAEI 2016, ALIN did not use the semantic metrics, only the string metrics, since the semantic metrics were taking a long time, making it impossible to execute it. In OAEI 2017, using the HESML API, it was possible to use semantic metrics, which led to an increase in the quality of the alignment generated, but with an increase in the expert's participation. The execution time also increased with the inclusion of semantic metrics, as we can see in table <ref type="table" target="#tab_10">8</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">General Comments</head><p>Evaluating the results it can be seen that the system can be improved towards:</p><p>(a) handling user error rate; (b) generating a higher quality (especially w.r.t. recall) initial alignment in its non-interactive phase;</p><p>(c) reducing the number of interactions with the expert; and (d) optimize the process to reduce its execution time, especially in alignments with large numbers of correspondences, such as Anatomy.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Conclusions</head><p>Within certain characteristics, the ALIN system stands out in ontology alignment process in interactive application scenarios, especially when the amount of data and object properties are relatively large and when the expert does not make mistakes. With these features there is an alignment generated with relatively high precision and recall.</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></div><figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>2 :</head><label>2</label><figDesc>Generation of the initial set of candidate correspondences 3: Automatic classification of correspondences 4: Removal of correspondences by the low value of semantic similarity</figDesc><table /><note>5: while Set of candidate correspondences is not empty do 6:</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 1 .</head><label>1</label><figDesc>Participation of ALIN in Anatomy non-interactive track</figDesc><table><row><cell cols="6">Runtime Size Precision F-Measure Recall Recall+ Coherent</cell></row><row><cell>836</cell><cell>516 0.996</cell><cell>0.506</cell><cell>0.339</cell><cell>0.0</cell><cell>+</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 2 .</head><label>2</label><figDesc>Participation of ALIN in Conference non-interactive track</figDesc><table><row><cell cols="7">Threshold Precision Recall F1-Measure F2-Measure F.5-Measure</cell></row><row><cell>ra1+m1</cell><cell>0.0</cell><cell>0.89</cell><cell>0.32</cell><cell>0.47</cell><cell>0.37</cell><cell>0.66</cell></row><row><cell>ra1+m2</cell><cell>0.0</cell><cell>0.0</cell><cell>0.0</cell><cell>0.0</cell><cell>0.0</cell><cell>0.0</cell></row><row><cell>ra1+m3</cell><cell>0.0</cell><cell>0.89</cell><cell>0.27</cell><cell>0.41</cell><cell>0.31</cell><cell>0.61</cell></row><row><cell cols="7">2.2 Comments on the participation of the ALIN in interactive</cell></row><row><cell>tracks</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_4"><head>Table 3 .</head><label>3</label><figDesc>Participation of ALIN in Anatomy interactive track -Error rate 0.0</figDesc><table><row><cell cols="6">Tool Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>ALIN</cell><cell>1074</cell><cell>0.993 0.794</cell><cell>0.882</cell><cell>939</cell><cell>1472</cell></row><row><cell>AML</cell><cell>45</cell><cell>0.968 0.948</cell><cell>0.958</cell><cell>241</cell><cell>240</cell></row><row><cell>LogMap</cell><cell>23</cell><cell>0.982 0.846</cell><cell>0.909</cell><cell>388</cell><cell>1164</cell></row><row><cell>XMap</cell><cell>43</cell><cell>0.927 0.865</cell><cell>0.895</cell><cell>35</cell><cell>35</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_5"><head>Table 4 .</head><label>4</label><figDesc>Participation of ALIN in Anatomy interactive track -Error rate 0.1</figDesc><table><row><cell cols="7">Tool Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>ALIN</cell><cell>1000</cell><cell>0.94</cell><cell>0.745</cell><cell>0.831</cell><cell>905</cell><cell>1352</cell></row><row><cell>AML</cell><cell>45</cell><cell cols="2">0.956 0.946</cell><cell>0.95</cell><cell>266</cell><cell>264</cell></row><row><cell>LogMap</cell><cell>23</cell><cell>0.962</cell><cell>0.83</cell><cell>0.891</cell><cell>388</cell><cell>1164</cell></row><row><cell>XMap</cell><cell>44</cell><cell cols="2">0.927 0.865</cell><cell>0.895</cell><cell>35</cell><cell>35</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_6"><head>Table 5 .</head><label>5</label><figDesc>Participation of ALIN in Conference interactive track -Error rate 0.0</figDesc><table><row><cell cols="7">Tool Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>ALIN</cell><cell>35</cell><cell cols="2">0.957 0.731</cell><cell>0.829</cell><cell>329</cell><cell>571</cell></row><row><cell>AML</cell><cell>30</cell><cell cols="2">0.912 0.711</cell><cell>0.799</cell><cell>271</cell><cell>270</cell></row><row><cell>LogMap</cell><cell>35</cell><cell>0.886</cell><cell>0.61</cell><cell>0.723</cell><cell>82</cell><cell>246</cell></row><row><cell>XMap</cell><cell>21</cell><cell>0.837</cell><cell>0.57</cell><cell>0.678</cell><cell>4</cell><cell>4</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_7"><head>Table 6 .</head><label>6</label><figDesc>Participation of ALIN in Conference interactive track -Error rate 0.1</figDesc><table><row><cell cols="7">Tool Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>ALIN</cell><cell>35</cell><cell cols="2">0.804 0.669</cell><cell>0.73</cell><cell>321</cell><cell>549</cell></row><row><cell>AML</cell><cell>30</cell><cell cols="2">0.841 0.701</cell><cell>0.765</cell><cell>282</cell><cell>275</cell></row><row><cell>LogMap</cell><cell>35</cell><cell cols="2">0.851 0.598</cell><cell>0.702</cell><cell>82</cell><cell>246</cell></row><row><cell>XMap</cell><cell>21</cell><cell>0.837</cell><cell>0.57</cell><cell>0.678</cell><cell>4</cell><cell>4</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_9"><head>Table 7 .</head><label>7</label><figDesc>Participation of ALIN in Conference interactive track -OAEI 2016/2017-Error rate 0.0</figDesc><table><row><cell cols="6">Year Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>2016</cell><cell>101</cell><cell>0.957 0.735</cell><cell>0.831</cell><cell>326</cell><cell>574</cell></row><row><cell>2017</cell><cell>35</cell><cell>0.957 0.731</cell><cell>0.829</cell><cell>329</cell><cell>571</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_10"><head>Table 8 .</head><label>8</label><figDesc>Participation of ALIN in Anatomy interactive track -OAEI 2016/2017-Error rate 0.0</figDesc><table><row><cell cols="6">Year Run Time (sec) Precision Recall F-measure Total Requests Distinct Mappings</cell></row><row><cell>2016</cell><cell>505</cell><cell>0.993 0.749</cell><cell>0.854</cell><cell>803</cell><cell>1221</cell></row><row><cell>2017</cell><cell>1074</cell><cell>0.993 0.794</cell><cell>0.882</cell><cell>939</cell><cell>1472</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Alignment API . Available at http://alignapi.gforge.inria.fr/ Last accessed on Oct, 10,</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2017" xml:id="foot_1">.<ref type="bibr" target="#b1">2</ref> String Similarity Metrics for Information Integration . Available on http://www.coli.uni-saarland.de/courses/LT1/2011/slides/stringmetrics.pdf. Last accessed on Oct, 10, 2017.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">HESML. Available at https://www.researchgate.net/publication/313881253 HESML A scalable ontologybased semantic similarity measures library with a set of reproducible experiments and a replication dataset Last accessed on Oct, 10, 2017.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">Stanford CoreNLP . Available at http://stanfordnlp.github.io/CoreNLP/ Last accessed on Oct, 10, 2017.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4"><ref type="bibr" target="#b4">5</ref> WS4J . Available at https://github.com/Sciss/ws4j Last accessed on Nov, 08, 2017.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_5">"Results of Evaluation for the Conference track within OAEI 2017 . Available at http://oaei.ontologymatching.org/2017/conference/eval.html Last accessed on Nov, 12, 2017.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<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="b1">
	<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="b2">
	<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="b3">
	<monogr>
		<title level="m" type="main">Semantic Interactive Ontology Matching : Synergistic Combination of Techniques to Improve the Set of Candidate Correspondences</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>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><surname>(n.D</surname></persName>
		</author>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Digging Ontology Correspondence Antipatterns</title>
		<author>
			<persName><forename type="first">A</forename><surname>Guedes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Baião</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Revoredo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceeding WOP14 Proc. 5th Int. Conf. Ontol. Semant. Web Patterns</title>
				<meeting>eeding WOP14 . 5th Int. Conf. Ontol. Semant. Web Patterns</meeting>
		<imprint>
			<date type="published" when="2014">2014</date>
			<biblScope unit="volume">1302</biblScope>
			<biblScope unit="page">3848</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<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>

<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">HESML: A scalable ontology-based semantic similarity measures library with a set of reproducible experiments and a replication dataset</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">J</forename><surname>Lastra-Díaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>García-Serrano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Batet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Fernández</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Chirigati</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.is.2017.02.002</idno>
		<ptr target="http://doi.org/10.1016/j.is.2017.02.002" />
	</analytic>
	<monogr>
		<title level="j">Information Systems</title>
		<imprint>
			<biblScope unit="volume">66</biblScope>
			<biblScope unit="page">97118</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

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