<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Combining Lexical and Semantic Similarity Measures with Machine Learning Approach for Ontology and Schema Matching Problem</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Proceedings of the XX International Conference “Data Analytics and Management in Data Intensive Domains” (DAMDID/RCDL'2018)</institution>
          ,
          <addr-line>Moscow</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Lev Bulygin Lomonosov Moscow State University</institution>
          ,
          <addr-line>Moscow</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <fpage>245</fpage>
      <lpage>249</lpage>
      <abstract>
        <p>Ontology and schema matching is one of the most important tasks for data integration. We suggest to combine the different matchers with machine learning approach. The features are the outputs of lexical and semantic similarity functions. Naive Bayesian classifier, logistic regression and gradient tree boosting have been trained on these features. The proposed approach is tested on the OAEI 2017 benchmark “conference” with the various splits of the data on train and test sets. Experiments show that final combined model in element-level matching outperformed the single matchers. Results are compared with EditDistance matcher and WordNet matcher.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>Data integration is now a very important problem, as the
amount of data is growing very much. One of the most
important steps in automatic data integration is the
comparison of ontologies or schemas. This problem is
traditionally solved manually or semi-automatically.
Manual ontology or schema matching is very
laborintensive, long in time and prone to errors. Therefore
now the task is to maximally automate the process of
comparing the circuit with the greatest accuracy.</p>
      <p>For schema matching and ontology matching
element-level and structure-level matchers are used.
Element-level matchers use information of elements of
schema (name of columns, description). Structure-level
matchers use information of structure (type similarity,
key properties, hierarchy of elements).</p>
      <p>Recently, element-level matchers have been widely
used lexical and semantic information. For getting
semantic information WordNet and Word2vec are used.
Word2vec allow us to get a meaning of the word and we
can use this for improving ontology and schema
matching. So we can combine many lexical and semantic
information into one similarity matrix and train a
machine learning model for trying to solve ontology and
schema matching problems.</p>
      <p>This work is performed as Master thesis. The main
goal of this work is to propose a approach for solving
ontology and schema matching problem with the greatest
accuracy. To achieve this goal we need to perform the
following tasks: review related work, create the
architecture of solution, select of information for
matching and create experiments. We compared our
approach on OAEI 2017 “conference” ontologies with
single matchers: edit distance and WordNet.</p>
      <p>In Section 2 we reviewed related work and it's
evolution. Section 3 describes the setup of the paper. In
Section 4 presents our matching algorithm in detail.
Section 5 shows the experiments and the analysis. We
conclude this paper in Section 6.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Related Work</title>
      <p>
        Schema matching and ontology matching are very
similar. In this article, there is no difference for schema
matching and ontology matching because we only work
with the names of the entities. So we considered the
works about schema matching and ontology matching
together. In [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] a review of approaches for automatic
schema matching are conducted. They introduced the
classification of matchers and concluded that it is
impossible to create a fully automatic matching system,
universal for all subject areas. One of the most important
conclusions is that hybrid matching system is better than
single system. Intuitively, this is obvious, since a hybrid
matcher uses more information to make a decision.
      </p>
      <p>
        In [2] the ready-made solutions for automatic schema
matching are compared and the concept of pre-match
effort and post-match effort introduced. Pre-match effort
is learning of the matcher, configuration of thresholds
and weights. Post-match effort is correction and
improvement of the match output. In the same year, in
[3] the authors described their COMA system. The
authors introduced new methods of post-match effort:
reuse of matchings, aggregation of individual matchers.
In [4] the Target-based Integration Query System (TIQS)
are described. In [5] a new classification on matching
dimensions are presented. A natural issue is uncertainty,
In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] uncertainty are considered, monotonicity and
statistical monotonicity are introduced . All the above
articles don't use machine learning for aggregation
results of matchers.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] Bayesian Networks are used for combining
ontology matching. As the features lexical information
(N-gram, Levenshtein, Dice Coefficient etc) were used.
The best accuracy is 88%.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] the outputs from several single matchers are
used and the authors trained on this data a multi-layer
neural network.The authors used lexical information and
the WordNet similarity.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] ontology matching problem in detail are
described: applications, classifications of ontology
matching techniques, evaluations and alignment. They
suggest three dimensions of building correspondences:
conceptual, extensional and semantic.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] Multiple Concept Similarity for ontology
mapping are described. The author reduced the ontology
mapping problem to the machine learning problem. They
used lexical information (prefix, suffix, Edit distance,
ngram), semantic information (WordNet) and special
types of similarity called Word List similarity (a
similarity for sentences).
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] a machine-learning approach to ontology
alignment problem are described. The authors used
lexical information, semantic information (WordNet)
and structural information for training Support Vector
Machine, K-Nearest Neighbours, Decision Tree,
AdaBoost models. The authors improves F-measure
criterion up to 99%.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] Bayeasian Networks are used for composition
of matchers. The resulting model achieved 81%
accuracy. The authors used the outputs of the lexical
matchers, structure-level matchers, synonym matchers
and instance-level matchers.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] all stages of ontology matching problem in
detail are described: feature selection, methods of
combining matchers and experiments.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] word2vec embeddings for ontology matching
problem are used. Authors proposed the new algorithm of
matching and sentence2vec algorithm. The results matcher
are compared with various types of WordNet, EditDistance
matchers. In [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] the combination of word2vec features and
a neural network are used. One of the most important
problems is that articles using machine learning can not be
compared with each other because of the lack of a unified
benchmark. The OAEI is not intended to use machine
learning, so the training dataset is chosen by the author of
the article.
      </p>
      <p>At the moment, the most promising option is the
using of machine learning to create a hybrid model with
lexical, semantic and structure information. In this
article, we want to connect many different single
matchers to one hybrid matcher using machine learning.
One of the newest features we used is Word2vec. So far
we only used the single element-level matchers.</p>
      <p>All reviewed papers use widely the lexical
information and WordNet distances. In this paper we
used 29 similarity metrics from 17 various single
element-level matchers.</p>
    </sec>
    <sec id="sec-3">
      <title>3 Problem Statement, Evaluation Metrics and Similarity Measures</title>
      <sec id="sec-3-1">
        <title>3.1 Problem Statement</title>
        <p>An ontology O is by a 3-tuple (C, P, I). C is the classes,
denoting the concepts. P is the relations within the
ontology. I is the instances of classes. The task of
ontology matching is to find the alignment between
entities in a source ontology  1 and a target ontology  2.</p>
        <p>An alignment is a set {( 1,  2,   )| 1 ∈  1,  2 ∈
 2}, where  1 is an entity in  1,  2 is an entity in  2, and
  is the confidence of the correspondence.</p>
        <p>Our algorithm works only with names of entities
without the structure information. The input of our
algorithm is the two ontologies: source and target. The
output of our algorithm is the alignment.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 Evaluation Metrics</title>
        <p>The effectiveness of ontology matching could
measured by precision, recall and F-measure.
 = |∩| | |, (1)</p>
        <p>= |∩| | |, (2)
 −  
= 2⋅  
⋅   , (3)
+  
where A is a predict alignment and B is a true
alignment.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3 Used Similarity Measures</title>
        <p>As features for machine learning we used the similarity
measures. We extract from ontology the names of
entities. Further we need to create sets of words from
names for computing some similarity measures.</p>
        <p>Example. We have two names of entities:
“early_paid_applicant” and
“early-registeredparticipant”. The sets are [“early”, “paid”, “applicant”]
and [“early”, “registered”, “participant”].</p>
        <p>
          Metrics based on lexical information from names of
entities:
• N-gram [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. Let ngram(S, N) be the set of
substrings of string S of length N. The n-gram
similarity for two strings S and T:
•
•
        </p>
        <p>
          ( ,  ) = |     ( (,| |),∩| |)−+1 ( , )| (4)
Dice coefficient [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The Dice similarity score is
defined as twice the shared information
(intersection) divided by sum of cardinalities. For
two sets X and Y, the Dice similarity score is:
   ( ,  ) = 2|∗||∩+ | || (5)
Jaccard similarity [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. For two sets X and Y, the
Jaccard similarity score is:
        </p>
        <p>
          ( ,  ) = ||∩∪ || (6)
Jaro measure [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The Jaro measure is a type of edit
distance, developed mainly to compare short strings,
such as first and last names.
(8)
•
where T is the total number of characters in both
strings, and M is the number of matches in the two
strings X and Y.
        </p>
        <p>
          Soundex [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Phonetic measure such as soundex
match string based on their sound. These measures
have been especially effective in matching names,
since names are often spelled in different ways that
sound the same.
        </p>
        <p>Token Sort. Fuzzy Wuzzy token sort ratio raw
raw_score is a measure of the strings similarity as an
int in the range [0, 100]. For two strings X and Y,
the score is obtained by splitting the two strings into
tokens and then sorting the tokens. The score is then
the fuzzy wuzzy ratio raw score of the transformed
strings.</p>
        <sec id="sec-3-3-1">
          <title>Tversky Index. For sets X and Y:</title>
          <p>( ,  ) =
|∩ |
|∩ |+ |− |+ |− |
, (11)
where  ,  &gt; 0.</p>
        </sec>
        <sec id="sec-3-3-2">
          <title>Overlap coefficient. For sets X and Y:</title>
          <p>( ,  ) =</p>
          <p>
            |∩ |
  (| |,| |)
(12)
Metrics based on semantic information from names
WordNet similarity. Best score of similarity between
synonyms of one word with synonyms of other
word. We use a sentence similarity algorithm from
[
            <xref ref-type="bibr" rid="ref14">14</xref>
            ].
          </p>
          <p>Word2vec and Sentence2vec similarity. Word2vec
is a
model that are
used to
produce
word
embeddings. We used word2vec model trained by
the texts of Google News. The dimensionality of
these
vectors is</p>
          <p>
            300. We used sentence2vec
algorithm from [
            <xref ref-type="bibr" rid="ref14">14</xref>
            ].
          </p>
          <p>of entities:</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 Proposed Matching Algorithm</title>
      <p>The input of the matching system is the two
ontologies. For each ontology the system extracts the
names of the entities. Further it generate all possible pairs
of the names of the ontology with the names of the other
ontology. For all pairs system computes the all similarity
measures. All outputs of the similarity measures are
concatenated
into
the
one
similarity
matrix.</p>
      <p>The
computed features are used as input to a machine
learning model.</p>
      <p>Program 1 Element-level matching algorithm
Input: Ontology1, Ontology2 - input ontologies
or schemas, THRESHOLD - threshold for create
matching between elements
Output: alignment - output alignment for
Ontology1 and Ontology2
for Entity1 ∈ Ontology1 do
for Entity2 ∈ Ontology2 do</p>
      <p>Name1 ← get_name(Entity1)
Name2 ← get_name(Entity2)
Features ← get_features(Name1, Name2)
Match ← predict_match(Features)
if Match &gt; THRESHOLD then</p>
      <p>alignment.append((Name1,Name2))
end if
end for
end for
return alignment
Program 2 Creating dataset and training a machine
learning model
Input: TrueAlignments - set of true alignments,
TrainAlignments - set of train pairs
Output: Model - trained model for predict
matching
for Ontology1, Ontology2 in TrueAlignments do
for Entity1 ∈ Ontology1 do
for Entity2 ∈ Ontology2 do
if (Entity1, Entity2) ∈ TrainAlignments
then</p>
      <p>add_to_train(Entity1, Entity2, 1)
else</p>
      <p>add_to_train(Entity1, Entity2, 0)
end if
end for
end for
end for
Model.train()
return Model</p>
      <p>For training a machine learning model we need the
ontologies and the alignments. We split the alignments
on the training alignments and testing alignments.
Further we train a machine learning model on the
features from train alignments. Then we can evaluate
Fmeasure on testing alignment.</p>
    </sec>
    <sec id="sec-5">
      <title>5 Preliminaries and Results</title>
      <sec id="sec-5-1">
        <title>5.1 Collection of Data</title>
        <p>The experiments were conducted at the dataset
“conference” from OAEI 2017. The dataset consists 16
ontologies from the same domain (conference
organisation) and 21 true ontology matchings. This
dataset is convenient for machine learning because all
ontologies are from the same domain and this dataset has
the several true matchings between ontologies.</p>
        <p>We get entities from ontologies with parsing code on
Python and get array of tuples: (entity1, entity2, match),
where entity1, entity2 - string names of entities, match
bool variable, 1 means that the entities are matched, 0
means that the entities are not matched. We generated 29
similarity measures from 3.3 with Python packages:
py_stringmatching24, fuzzycomp25, gensim26.</p>
        <p>The final dataset is very unbalanced: 391 572
negative samples and 305 positive samples. After
generating features we split data randomly on train and
test datasets in equal proportions. In Table 1 are
described our split.
24 https://github.com/kvpradap/py_stringmatching
25 https://github.com/fuzzycode/fuzzycomp
26 https://github.com/RaRe-Technologies/gensim
27
http://scikitlearn.org/stable/modules/generated/sklearn.naive_bayes</p>
        <p>We can see on Table 2 that XGBoost is the model
with best F-measure 55.01%. The worst model is Naive
Bayes Classifiers with F-measure 4.15%. EditDistance is
better than WordNet by 27%. For getting more stable
results we splitted the datasets randomly on training and
testing pairs 20 times and averaged the results. The
results are show on Table 3. We can see that XGBoost
are remained the best model.
.GaussianNB.html
28
http://scikitlearn.org/stable/modules/generated/sklearn.linear_mode
l.LogisticRegression.html
29 https://github.com/dmlc/xgboost</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6 Conclusions</title>
      <p>In this paper, we combined the lexical and semantic
similarity measures into one hybrid model. The
experiments show that hybrid model is better than single
matchers.</p>
      <p>In future work we want to run our solution on other
benchmarks. We must add the structure-level and
instance-level features because in our dataset there are
examples in which the names of entities are exactly the
same but they are not matched.</p>
      <p>Acknowledgments. This work is supervised by Sergey
Stupnikov, Institute of Informatics Problems, Federal
Research Center “Computer Science and Control“ of the
Russian Academy of Sciences”.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <source>[1] [2] [3] [4]</source>
          [5]
          <string-name>
            <surname>Rahm</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bernstein</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A survey of approaches to automatic schema matching</article-title>
          .
          <source>In: The International Journal on Very Large Data Bases</source>
          , vol.
          <volume>10</volume>
          , issue 4, pp.
          <fpage>334</fpage>
          -
          <lpage>350</lpage>
          (
          <year>2001</year>
          ). doi:
          <volume>10</volume>
          .1007/s007780100057
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Do</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melnik</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rahm</surname>
          </string-name>
          , E.:
          <article-title>Comparison of Schema Matching Evaluations</article-title>
          .
          <source>In: Revised Papers from the NODe 2002 Web and DatabaseRelated Workshops on Web, Web-Services, and Database Systems</source>
          , pp.
          <fpage>221</fpage>
          -
          <lpage>237</lpage>
          (
          <year>2002</year>
          ). doi:
          <volume>10</volume>
          .1007/3-540-36560-5_
          <fpage>17</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Do</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rahm</surname>
          </string-name>
          , E.:
          <article-title>COMA: a system for flexible combination of schema matching approaches</article-title>
          .
          <source>In: VLDB '02 Proceedings of the 28th international conference on Very Large Data Bases</source>
          , pp.
          <fpage>610</fpage>
          -
          <lpage>621</lpage>
          (
          <year>2002</year>
          ). doi:
          <volume>10</volume>
          .1016/B978-155860869- 6/
          <fpage>50060</fpage>
          -
          <lpage>3</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <given-names>L.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Embley</surname>
          </string-name>
          .:
          <article-title>Automating Schema Mapping for Data Integration</article-title>
          . (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Survey of SchemaBased Matching Approaches</article-title>
          .
          <source>In: Journal on Data Semantics IV</source>
          , pp.
          <fpage>146</fpage>
          -
          <lpage>171</lpage>
          (
          <year>2005</year>
          ). doi:
          <volume>10</volume>
          .1007/11603412_
          <fpage>5</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Gal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Why is Schema Matching Tough and What Can We Do About It? In: ACM SIGMOD Record</article-title>
          , vol.
          <volume>35</volume>
          , issue 4, pp.
          <fpage>2</fpage>
          -
          <lpage>5</lpage>
          (
          <year>2006</year>
          ). doi:
          <volume>10</volume>
          .1145/1228268.1228269
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Svab</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Svatek</surname>
          </string-name>
          , V.:
          <article-title>Combining Ontology Mapping Methods Using Bayesian Networks</article-title>
          .
          <source>In: OM'06 Proceedings of the 1st International Conference on Ontology Matching</source>
          , vol.
          <volume>225</volume>
          , pp.
          <fpage>206</fpage>
          -
          <lpage>210</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Hariri</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abolhassani</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sayyadi</surname>
          </string-name>
          , H.:
          <article-title>A Neural-Networks-Based Approach for Ontology Alignment</article-title>
          . (
          <year>2006</year>
          ). https://www.jstage.jst.go.jp/article/softscis/2006/ 0/2006_0_1248/_article
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Ontology Matching. Springer-Verlag Berlin Heidelberg, Berlin (
          <year>2007</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -38721-0
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Ichise</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <article-title>: Machine Learning Approach for Ontology Mapping Using Multiple Concept Similarity Measures</article-title>
          . In: Seventh IEEE/ACIS International Conference on Computer and Information Science, (
          <year>2008</year>
          ). doi:
          <volume>10</volume>
          .1109/ICIS.
          <year>2008</year>
          .51
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Nezhadi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shadgar</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Osareh</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Ontology Alignment Using Machine Learning Techniques</article-title>
          .
          <source>In: International Journal of Computer Science &amp; Information Technology</source>
          , vol.
          <volume>3</volume>
          , pp.
          <fpage>139</fpage>
          -
          <lpage>150</lpage>
          (
          <year>2011</year>
          ). doi:
          <volume>10</volume>
          .5121/ijcsit.
          <year>2011</year>
          .3210
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Nikovsi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esenther</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ye</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shiba</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Takayama</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Bayesian Networks for Matcher Composition in Automatic Schema Matching</article-title>
          . In: Mitsubishi Electric Research Laboratories (
          <year>2011</year>
          ).
          <source>doi: 10.1.1.644.2168</source>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Ngo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Enhancing Ontology Matching by Using Machine Learning, Graph Matching and Information Retrieval Techniques</article-title>
          . In: University Montpellier II -
          <source>Sciences et Techniques du Languedoc</source>
          (
          <year>2012</year>
          ).
          <source>doi: 10.1.1.302.587</source>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lai</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>He</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lv</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          :
          <article-title>Ontology Matching with Word Embeddings</article-title>
          .
          <source>In: Chinese Computational Linguistics and Natural Language Processing Based on Naturally Annotated Big Data</source>
          , pp
          <fpage>34</fpage>
          -
          <lpage>45</lpage>
          (
          <year>2014</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -12277-
          <issue>9</issue>
          _
          <fpage>4</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Jayawardana</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lakmal</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perera</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sugathadasa</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ayesha</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Deriving a Representative Vefctor for Ontology Classes with Instance Word Vector Embeddings</article-title>
          .
          <source>In: 2017 Seventh International Conference on Innovative Computing Technology (INTECH)</source>
          , (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .1109/INTECH.
          <year>2017</year>
          .8102426
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>