<!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>DORIS: Discovering Ontological Relations In Services</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Maria Koutraki</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dan Vodislav</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicoleta Preda</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ETIS CNRS, University of Cergy-Pontoise</institution>
          ,
          <addr-line>Cergy-Pontoise</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>PRiSM CNRS, University of Versailles</institution>
          ,
          <addr-line>Versailles</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We propose to demonstrate DORIS, a system that maps the schema of a Web Service automatically to the schema of a knowledge base. Given only the input type and the URL of the Web Service, DORIS executes a few probing calls, and deduces an intensional description of the Web service. In addition, she computes an XSLT transformation function that can transform a Web Service call result in XML to RDF facts in the target schema. Users will be able to play with DORIS, and to see how real-world Web Services can be mapped to large knowledge bases of the Semantic Web.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>http://isbndb.com/api/author?q=
Parameter q (required): The author name
http://isbndb.com/api/authors?q=Dario Fo
a Transformation</p>
      <p>Function
f
i
y
rdfs:label</p>
      <p>date
won
created
z2
\1997"
\BMuistoe"ro \1969" \1974P"a\yPC?aWayn!o"'tn't \PNriozbee"l \1997" rd\fBMs:uliasbtoee"rlo \19d6a9t"e rPdfas\yP:Cl?aaWaybn!eo"'ltn't \1d9a7t4e"</p>
      <p>Fig. 2: A call result (left), and its mapping to the KB (right).</p>
      <p>If this URL is accessed, the WS will respond with the result of the query,
typically with an XML document. In the example, if we call the service with
the input value \Dario Fo", we may receive as answer the XML tree depicted in
Figure 2 (left).</p>
      <p>In this way the providers can keep control of their data, while users and
applications can receive answers to their knowledge requests. This partial openness
may be the reason for the success of WSs. If a user issues too many requests,
she is blocked. One consequence of this design is that it is impossible to crawl
the data of the WS exhaustively.</p>
      <p>Challenges. The main challenge when dealing with WSs is that the data that
the service returns is not necessarily in the schema of the KB. In fact, even
di erent WSs typically use di erent schemas. The goal is, therefore, to map the
output of a WS call (Figure 2 (left)) into facts in the schema of the KB (Figure 2
(right)). This involves not just an alignment of the schema of the WS with the
schema of the KB, but also a transformation function, which translates an XML
tree into an RDF graph.</p>
      <p>This is di cult for several reasons: First, labels of intermediary nodes in
the call results are usually vacuous and do not give away any semantics. In the
example, they are just labeled \a", \b", and \c". Second, it is not clear which
nodes in the call result correspond to entities in the KB schema. In the example,
one can guess that the nodes labeled with \b" correspond to entities. However,
the nodes labeled with \f" correspond to nothing in particular. Third, call results
usually contain data for several types of entities. The key challenge is to detect
which node corresponds to which entity. Finally, the edges of the XML tree have
to be mapped to relation names in the schema of the KB. This is particularly
di cult because sometimes entire paths in the XML tree correspond to one single
relation in the schema of the KB.</p>
      <p>
        Contribution. In this paper, we demonstrate DORIS [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], an approach that,
given a KB and a WS, deduces both the schema mapping and the transformation
function automatically. As input, DORIS requires only the KB, the WS URL,
and the input type. The central idea is to probe the WS with a few sample
inputs from the KB, and to analyze the overlap of the XML call result with the
KB in order to deduce the alignments. Technically speaking, DORIS describes
the WS as a view with binding patterns over a global database schema [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The
particular contribution of this demo proposal is the graphical interface that lets
users play with the system, and map real-world WSs automatically to some of
the largest KBs of the Semantic Web.
      </p>
      <p>
        Related Work. Schema alignment approaches such as [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] could be considered
to map WSs to KBs. However, they fail because the XML result tree of the WS
does not give away which nodes correspond to entities in the KB and which don't.
Worse, our scenario requires aligning multi-hop relations with single-hop
relations, which is out of the scope of current schema alignment approaches. Closest
to our work, [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] derives intensional descriptions for WSs. However, the approach
is semi-automatic, and requires the user's assistance during the process.
Furthermore, it assumes an implicit translation of call results into tables, meaning that
a WS returns properties for only one class of entities. Our approach, in contrast,
can deal with the general case where WSs return nested descriptions of entities
of di erent types, such as authors, books, and book editions.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2 Demonstration</title>
      <p>We now describe our approach DORIS. With the proposed demonstration, the
user will be able to trace every step that DORIS takes in our graphical interface.
The interface will illustrate a suite of strategies that we have investigated, and
the design decisions we made.</p>
      <p>The user rst chooses a target KB. Our demo currently supports DBpedia,
YAGO, and the KB of the French National Library BNF. Then, the user chooses
a WS that she wishes to map to the KB. This can be any WS that the user came
across (as the one depicted in Figure 1), as long as we may expect some overlap
of entities between the WS and the KB. DORIS requires as input the URL of
the WS, and the input type. We provide a list of 50 example WSs, covering the
domains of music, books, movie, and geolocations. The demonstration of DORIS
proceeds in 4 steps.
1. Probing: The service is called with several entities from the KB. The result
is a set of sample call results.
2. Path Alignment: Discover root-to-text nodes paths in the call results.
Discover input-to-literals paths in the KB. Align the paths in the call results
with the paths from the KB.
3. Entity and Property Discovery: Identify the entities from the KB and
their properties that are encoded in the call results. Find the nodes,
respective the paths in the call results that correspond to them.
4. Parameterized Query &amp; Transformation Function: Build the view
and the transformation function as a XSLT script.</p>
      <p>The demonstration will illustrate rst di erent binding selection strategies,
which aim to minimise the number of empty call results. For this purpose, we
try to learn the overlap between the WS and the KB. The interface will also
allow experimenting with di erent numbers of calls.</p>
      <p>The second and the third step are concerned with identifying complex
objects encoded in call results. We do not make any assumption about an implicit
translation from trees to RDF fragments. The intuition behind the second step
is that we can align the root of a call result to the entity in the KB that was used</p>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>
        This paper demonstrates DORIS, a system to automatically align Web Services
with Knowledge Bases. Our experiments with 50 services show that DORIS can
infer alignments with a F-measure of 81%-100%. All evaluation results, as well
as our full paper [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], can be found on http://oasis.prism.uvsq.fr/.
Acknowledgments. This work is supported by the research projects EDOP
(PATRIMA LabEx) and ALODIS (PEPS FASCIDO 2015 - CNRS).
      </p>
    </sec>
    <sec id="sec-4">
      <title>References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Halevy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Answering queries using views { a survey</article-title>
          .
          <source>The VLDB Journal</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Koutraki</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vodislav</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Preda</surname>
          </string-name>
          , N.:
          <article-title>Deriving intensional descriptions for web services</article-title>
          .
          <source>In: CIKM</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Suchanek</surname>
            ,
            <given-names>F.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abiteboul</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Senellart</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : PARIS:
          <article-title>Probabilistic Alignment of Relations, Instances, and</article-title>
          <string-name>
            <surname>Schema. PVLDB</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Taheriyan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knoblock</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szekely</surname>
            ,
            <given-names>P.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ambite</surname>
            ,
            <given-names>J.L.</given-names>
          </string-name>
          :
          <article-title>Rapidly integrating services into the linked data cloud</article-title>
          .
          <source>In: ISWC</source>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>