<!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>On Implementing a SPARQLoid Query Coding Support { Vocabulary Discovery for Queries with Weighted Ontology Mappings</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hiroki Noguchi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Takahisa Fujino</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Naoki Fukuta</string-name>
          <email>fukuta@cs</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Graduate School of Informatics Shizuoka University Hamamatsu</institution>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <fpage>33</fpage>
      <lpage>38</lpage>
      <abstract>
        <p>When writing SPARQL queries that will access to multiple data sources (i.e., a federated querying), one has to know the corresponding vocabulary where one can name the property URIs to be used in the query, and to know the exact URIs for such vocabulary is not easy task since those vocabularies are often separately defined and managed. To avoid such a situation, the techniques to use some ontology mappings in a SPARQL query have been actively developed. In this paper, we present our preliminary implementation of SPARQLoid query coding support system that can utilize familiar vocabularies that may be contained in some ontology mappings by using weighted ontology mappings associated to specified keywords in the query.</p>
      </abstract>
      <kwd-group>
        <kwd>SPARQL</kwd>
        <kwd>ontology mapping</kwd>
        <kwd>Linked Open Data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The use of ontology mapping, alignment, and matching techniques [
        <xref ref-type="bibr" rid="ref14 ref5 ref6">5, 6, 14</xref>
        ] could
be useful for writing queries when it allows us to use any ontologies in the
queries unless those ontologies are not directly used in the endpoint [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. There
are some ontology alignment methods to produce precise and crisp mappings
among their entities. However, in some cases, producing a precise mapping is very
difficult[
        <xref ref-type="bibr" rid="ref14 ref5">5, 14</xref>
        ], especially when the two ontologies have semantic gaps. Alignment
methods generally require much time to produce an alignment when the two
ontologies are huge. Hence, an efficient way to get an alignment has also been
proposed (e.g.,[
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]). To utilize these ontology mappings that have a variety of
confidence values, it is important to explicitly control their effective use in a
query, since without such control a query can produce so much unwanted data
in the process of its execution so that they cannot be processed. Although there
are some approaches that can utilize mappings on querying with SPARQL[
        <xref ref-type="bibr" rid="ref13 ref16">13,
16</xref>
        ], they will not provide a functionality to explicitly control how to process
queries with such ‘somewhat unreliable’ weighted ontology mappings. To solve
this issue, SPARQLoid, a small extension to SPARQL that allows us to utilize
such weighted ontology mappings effectively, has been proposed[
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ].
      </p>
      <p>However, on SPARQLoid, finding a base ontology and understanding their
vocabulary defined in the ontology is still remained as one of the user’s tasks, and
it would be still difficult for various novice users. In this paper, we present our
preliminary implementation of SPARQLoid query coding support system that
can help users to utilize vocabularies that users are familiar with in the query, by
providing a recommendation mechanism for sufficient ontologies and endpoints
in combination with weighted ontology mapping-based querying functionalities
implemented on SPARQLoid engine.
2
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <sec id="sec-2-1">
        <title>Linked Open Data and SPARQL</title>
        <p>The datatype of Linked Open Data (LOD) is basically written by RDF like
Semantic Web. As an example, there is DBpedia that has been converted from
the original Wikipedia content to the form of LOD. Furthermore, to realize
“Open Government”, various countries have been spent much efforts to realize
their open data access site, such as “data.gov”. In 2013, there are at least 447
registered public SPARQL endpoints with over 31 billion RDF triples, which
are interlinked by around 504 million RDF links, and the amount of data are
increasing1.</p>
        <p>
          There are many SPARQL endpoints (e.g., DBpedia[
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]) that allow us to
retrieve and see the data by queries that are written in SPARQL query language.
We can retrieve data not only from one endpoint but also from several endpoints
using federated queries [
          <xref ref-type="bibr" rid="ref11 ref12 ref15">11, 12, 15</xref>
          ]. However, it is not always easy to understand
the ontology used at an endpoint well enough to write a query based on it. The
main reason could be that, often an ontology is constructed with some specific
terms that were not used in others. Furthermore, it often lacks detailed
documentations.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Ontology Mapping</title>
        <p>
          In open systems such as Semantic Web, how to deal with heterogeneity of data
or ontology is becoming an important issue to be solved. To solve the issue, lots
of efforts have been done about developing and evaluating approaches for
ontology mapping[
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Also, some practical software that implemented such ontology
mapping techniques are widely used (e.g. LogMap[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], Alignment API2, etc).
        </p>
        <p>LogMap uses HermiT3 as a reasoner to allow the method to generate higher
quality mappings based on the reasoning results among the ontologies.
Therefore, to fully utilize it, we need to prepare target ontologies that are ready for
reasoning on HermiT. In this way, sometimes we need to utilize various
approaches to generate mappings and their quality would be varied. For example,
1 http://sparqles.okfn.org/availability
2 http://alignapi.gforge.inria.fr/
3 http://hermit-reasoner.com/
AlignmentAPI allows us to generate mappings based on string similarity or other
mapping methods that users have chosen. It generates mappings in short time
but it may produce mappings with lower precision.</p>
        <p>
          In OAEI2012[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], 23 types of mapping generation methods were presented.
We prepared a set of mapping generation and updating mechanism to obtain
results by querying to heterogeneous LODs.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3 SPARQLoid</title>
        <p>
          SPARQLoid enables users to control their utilization of different ontology
mappings as well as confidence values in a query[
          <xref ref-type="bibr" rid="ref7 ref8 ref9">7–9</xref>
          ]. It allows users to choose and
utilize ontology mappings to obtain the data in the target endpoint and specify
the criterion for sorting the results and cutting output data that are far from
accurate.
        </p>
        <p>Here, we show a typical SPARQLoid query in listing 1.1. Notice that the
SPARQLoid query in listing 1.1 obtains the matched instances as ?a, ?b, and
?c using the vocabularies in the conference namespace. However, each target
endpoint to be accessed by a URI (targetEndpoint or federatedQueryEndpoint in
listing 1.1) is expected to be constructed using each different ontologies.
SELECT ?a ?b ?c
WHERE
{
}
?a rdf:type conference:Regular_author
?a conference:has_the_last_name ?b {</p>
        <p>SERVICE &lt; federatedQueryEndpoint &gt; {</p>
        <p>?a conference:has_the_first_name ?c
}
} RANKING &lt; targetEndpoint &gt; {
conference:Regular_author *0.5 +
conference:has_the_last_name *0.2
} THRESHOLD &lt; targetEndpoint &gt; {
conference:Regular_author =0.3 ,
conference:has_the_last_name =0.3
} RANKING &lt; federatedQueryEndpoint &gt; {</p>
        <p>conference:has_the_first_name *0.3
} THRESHOLD &lt; federatedQueryEndpoint &gt; {
conference:has_the_first_name =0.2
}</p>
        <p>Listing 1.1. Example Query in SPARQLoid</p>
        <p>For example, the class conference:Regular author and the property
conference:has the rst name require appropriate mappings to run the queries in
listing 1.1 on the endpoints. In listing 1.1, conference:Regular author was specified
as more important than conference:has the rst name by the ranking clause. In
case of a federated SPARQL querying, the weights of mappings are merged in
the specified ways. In listing 1.1, some threshold values are specified to cut the
irrelevant results that come from lower-weight mappings. For example, the
mappings for conference:Regular author whose confidence values are higher than 0.3
are used to execute the query on the target endpoint.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Proposed System</title>
      <p>
        Our system, SuPARQooL(SUPport system for spARql Query cOding with
Ontology mapping on sparqLoid) realizes a WOM(weighted ontology
mapping)based SPARQL query coding support with vocabulary discovery support
technique. The users can write a query in SPARQL or SPARQLoid[
        <xref ref-type="bibr" rid="ref7 ref8 ref9">7–9</xref>
        ] that includes
some natural language texts as the concepts (i.e., types) or properties to be used
in them, and the system recommends sufficient URIs for them. Although other
systems[
        <xref ref-type="bibr" rid="ref13 ref16 ref17 ref4">4, 13, 16, 17</xref>
        ] are not aware of weighted ontology mappings, SPARQLoid
allows us to utilize weighted ontology mappings effectively. The system
semiautomatically finds candidates of vocabularies or the entire ontologies that can
be mapped to the users’ familiar ontologies. Then, after clicking the “NEXT”
button on the main window (see Figure1), our system calculates the matching
degree to the endpoints that have been registered to the system. The endpoints
in the list are scored and ranked based on the matching degrees. By pressing
the button “more”, the user can see the endpoints to be accessed and test-run
some queries and investigate the endpoint itself to confirm it is sufficient to be
used based on the investigated details of the endpoint. When the user has
successfully coded the queries to be used, the system will prompt the user to select
the endpoints to be accessed from the list. Then, based on the ontologies used
in the endpoints, the SPARQLoid query is translated to a standard SPARQL
0(/1.2(3&amp;42+3!
!"#$%&amp;
:#*#63#/&amp;0(/1.2(3!
query to be run on various SPARQL endpoints. The user can manually rewrite
the generated SPARQL query for fine tunings of performance or adjust detailed
behaviors of the query. The results of the query are also shown in the system,
as well as converting the query that can embed some external applications to
access external SPARQL endpoints.
      </p>
      <p>Figure2 shows the structure of our preliminary implemented system. Query
Analyser analyzes and extracts keywords. Recommender recommends endpoints
by the specified keywords or related endpoint list. Query Translater translates
SPARQLoid queries to standard SPARQL queries that can be run on various
endpoints.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>In this paper, we presented a SPARQL query coding support system with
vocabulary discovery function for queries with weighted ontology mappings, which
can be utilized in SPARQLoid queries. Our system allows users to query
various open endpoints with weighted ontology mappings, as well as finding such
endpoints and user’s familiar base vocabularies to be used in the query.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aguirre</surname>
            ,
            <given-names>J. L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eckert</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrara</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Van Hage</surname>
            ,
            <given-names>W. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hollink</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meilicke</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikolov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ritze</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scharffe</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zamazal</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          <article-title>Sˇv´ab</article-title>
          , Trojahn,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Jim</surname>
          </string-name>
          <article-title>´enez-</article-title>
          <string-name>
            <surname>Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B. C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Zapilko</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <article-title>Preliminary results of the Ontology Alignment Evaluation Initiative 2012</article-title>
          .
          <source>In: Proc. of 7th Ontology Matching Workshop (OM2012)</source>
          ,
          <source>at International Semantic Web Conference (ISWC2012)</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Atencia</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Borgida</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghidini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serafini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A formal semantics for weighted ontology mappings</article-title>
          .
          <source>In: Proc. of the 11th International semantic web conference (ISWC2012)</source>
          . (
          <year>2012</year>
          )
          <fpage>17</fpage>
          -
          <lpage>33</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kobilarov</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cyganiak</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ives</surname>
            ,
            <given-names>Z.G.</given-names>
          </string-name>
          :
          <article-title>DBpedia: A Nucleus for a Web of Open Data</article-title>
          .
          <source>In: Proc. of the 6th International Semantic Web Conference (ISWC2007)</source>
          . (
          <year>2007</year>
          )
          <fpage>722</fpage>
          -
          <lpage>735</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schultz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The R2R Framework: Publishing and Discovering Mappings on the Web</article-title>
          .
          <source>In: Proc. of the 1st International Workshop on Consuming Linked Data (COLD</source>
          <year>2010</year>
          ).
          <article-title>(</article-title>
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Duan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srinivas</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Byrne</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A clustering-based approach to ontology alignment</article-title>
          .
          <source>In: Proc. of the 10th International Semantic Web Conference (ISWC2011)</source>
          . (
          <year>2011</year>
          )
          <fpage>146</fpage>
          -
          <lpage>161</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Euzenat</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Classifications of ontology matching techniques</article-title>
          . In: Ontology matching. (
          <year>2007</year>
          )
          <fpage>61</fpage>
          -
          <lpage>72</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Fujino</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukuta</surname>
          </string-name>
          , N.:
          <string-name>
            <surname>A SPARQL Query</surname>
          </string-name>
          <article-title>Rewriting Approach on Heterogeneous Ontologies with Mapping Reliability</article-title>
          .
          <source>In: Proc. of the IIAI International Conference on Advanced Applied Informatics (IIAI-AAI2012)</source>
          . (
          <year>2012</year>
          )
          <fpage>230</fpage>
          -
          <lpage>235</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Fujino</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukuta</surname>
          </string-name>
          , N.:
          <article-title>SPARQLoid - a querying system using own ontology and ontology mappings with reliability</article-title>
          .
          <source>In: Proc. of the International Semantic Web Conference (Posters &amp; Demos) (ISWC2012)</source>
          . (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Fujino</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukuta</surname>
          </string-name>
          , N.:
          <article-title>Utilizing Weighted Ontology Mappings on Federated SPARQL Querying</article-title>
          .
          <source>In: Proc. of the 3rd Joint International Semantic Technology Conference (JIST2013)</source>
          . (
          <year>2013</year>
          )
          <article-title>(to appear)</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Jim</surname>
          </string-name>
          <article-title>´enez-</article-title>
          <string-name>
            <surname>Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            , B,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>LogMap: Logic-based and Scalable Ontology Matching</article-title>
          .
          <source>In: Proc. of the 11th International Semantic Web Conference (ISWC</source>
          <year>2011</year>
          ),
          <string-name>
            <surname>Part</surname>
            <given-names>I</given-names>
          </string-name>
          , LNCS
          <volume>7031</volume>
          , pp.
          <fpage>273</fpage>
          -
          <lpage>288</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Ladwig</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tran</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked data query processing strategies</article-title>
          .
          <source>In: Proc. of the 9th International semantic web conference (ISWC2010)</source>
          . (
          <year>2010</year>
          )
          <fpage>453</fpage>
          -
          <lpage>469</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Ladwig</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tran</surname>
          </string-name>
          , T.:
          <article-title>SIHJoin: querying remote and local linked data</article-title>
          .
          <source>In: Proc. of the 8th European Semantic Web Conference (ESWC2011)</source>
          . (
          <year>2011</year>
          )
          <fpage>139</fpage>
          -
          <lpage>153</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Makris</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bikakis</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gioldasis</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Christodoulakis</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>SPARQL-RW: Transparent Query Access over Mapped RDF Data Sources</article-title>
          ,
          <source>In: Proc. of the 15th International Conference on Extending Database Technology (EDBT2012)</source>
          , (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N. F.</given-names>
          </string-name>
          :
          <article-title>In: Proc. of the Ontology mapping</article-title>
          . In Steffen, S.,
          <string-name>
            <surname>Rudi</surname>
          </string-name>
          , S., eds.: Handbook on Ontologies. (
          <year>2009</year>
          )
          <fpage>573</fpage>
          -
          <lpage>590</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Quilitz</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leser</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Querying distributed RDF data sources with SPARQL</article-title>
          .
          <source>In: Proc. of the 5th European SemanticWeb Conference (ESWC2008)</source>
          . (
          <year>2008</year>
          )
          <fpage>524</fpage>
          -
          <lpage>538</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Rivero</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hernandez</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruiz</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Corchuelo</surname>
          </string-name>
          , R.:
          <article-title>Mosto: Generating SPARQL Executable Mappings Between Ontologies</article-title>
          .
          <source>In: Proc. of the 30th International Conference on Conceptual Modeling Demos and Posters</source>
          . (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Rivero</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hernandez</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruiz</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Corchuelo</surname>
          </string-name>
          , R.:
          <article-title>Generating SPARQL Executable Mappings to Integrate Ontologies</article-title>
          .
          <source>In: Proc. of the 30th International Conference on Conceptual Modeling</source>
          . (
          <year>2011</year>
          )
          <fpage>118</fpage>
          -
          <lpage>131</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Seddiqui</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aono</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>An efficient and scalable algorithm for segmented alignment of ontologies of arbitrary size</article-title>
          .
          <source>In: Web Semantics</source>
          .
          <volume>7</volume>
          (
          <issue>4</issue>
          ).
          <source>(December</source>
          <year>2009</year>
          )
          <fpage>344</fpage>
          -
          <lpage>356</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>