<!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>SPARQL Query Construction with Monitoring Service for Endpoints</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Atsuko Yamaguchi</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yasunori Yamamoto</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kouji Kozaki</string-name>
          <email>kozaki@ei.sanken.osaka-u.ac.jp</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kai Lenz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hiroshi Masuya</string-name>
          <email>hmasuya@brc.riken.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Norio Kobayashi</string-name>
          <email>norio.kobayashig@riken.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Advanced Center for Computing and Communication (ACCC), RIKEN</institution>
          ,
          <addr-line>2-1 Hirosawa, Wako, Saitama, 351-0198</addr-line>
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>BioResource Center (BRC), RIKEN</institution>
          ,
          <addr-line>3-1-1, Koyadai, Tsukuba, Ibaraki, 305-0074</addr-line>
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Database Center for Life Science (DBCLS), ROIS</institution>
          ,
          <addr-line>178-4-4 Wakashiba, Kashiwa, Chiba, 277-0871</addr-line>
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>The Institute of Scienti c and Industrial Research (ISIR), Osaka University</institution>
          ,
          <addr-line>8-1 Mihogaoka, Ibaraki, Osaka, 567-0047</addr-line>
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Many databases in life sciences have been provided in Resource Description Framework (RDF) with their SPARQL endpoints. To support a user in constructing SPARQL queries, we developed a service called SPARQL Builder. Although SPARQL Builder makes a user write a query for obtaining data from LOD, empty results or incorrect data might be retrieved by the query if the SPARQL endpoint for the query is not alive or provides out-of-date data. To avoid such queries from SPARQL Builder, YummyData which monitors SPARQL endpoints and gathers information about alive rate, last update, response time, etc. was used. By connecting YummyData to SPARQL Builder, our system can always obtain a SPARQL query for SPARQL endpoints with high usability.</p>
      </abstract>
      <kwd-group>
        <kwd>SPARQL</kwd>
        <kwd>RDF</kwd>
        <kwd>life-science databases</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        SPARQL Builder (http://www.sparqlbuilder.org/) is a web application that
enables users to access life science data provided as Linked Open Data by assisting
them in writing SPARQL queries for the data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Although SPARQL is a
standardized query language for searching Linked Open Data and there are many
Web APIs, called SPARQL endpoints, that accept SPARQL queries, a user may
have di culties in writing a SPARQL query because the user requires knowledge
of the linked data schema including data classes and terms in a wide variety of
published life science data in advance. Our tool assists users to build a SPARQL
query for SPARQL endpoints of life science databases without knowledge of data
schemata or SPARQL by providing an intuitive graphical user interface (GUI).
      </p>
      <p>
        Our system use metadata extracted from SPARQL endpoint in advance,
to display data schema quickly. Because point in time when a user accesses
SPARQL Builder is di erent from the time when metadata was extracted, some
SPARQL endpoints might be down or out-of-date. Therefore, our system requires
a monitoring service for SPARQL endpoints. In this paper, we used a monitoring
service called YummyData [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and tried it to connect to SPARQL Builder. By
obtaining the latest states of SPARQL endpoints from YummyData, SPARQL
Builder always outputs a SPARQL query by which a user can obtain data from
reliable SPARQL endpoints.
2
      </p>
      <p>
        Method and Result
To support a user in constructing a SPARQL query, SPARQL Builder rst
displays classes that appear in life science RDF datasets. All of the classes are
associated with SPARQL endpoints. YummyData has a Web API called Umaka
API [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] providing a list of SPARQL endpoints with their information about
accessibility and usability. Using the API, we added a lter of SPARQL endpoints
into SPARQL Builder, to select SPARQL endpoints with alive rate 80 and
execution time 10 seconds. Because the alive rate corresponds to rate that
returns 200 as http status code, it does not show that it is accessible as a SPARQL
endpoint. On the other hand, because execution time shows the response time for
some SPARQL query at a particular time, it does not show that the site is stable.
Therefore, we used these two criteria for selecting SPARQL endpoints. Because
YummyData obtains its data from SPARQL endpoint everyday, by using the
lter, SPARQL Builder can dynamically obtain reliable SPARQL endpoints at
that time.
      </p>
      <p>Currently, although we uses YummyData as just a lter for SPARQL
endpoints, we are considering the use of the data in YummyData to weight classes,
properties, and SPARQL queries, to construct queries for more valuable data.
Because the numbers of classes and properties are very large, an appropriate
weighting method should be very useful to display them for users.
Acknowledgments. This work was supported by the National Bioscience
Database Center (NBDC) of the Japan Science and Technology Agency (JST).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Yamaguchi</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kozaki</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenz</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wu</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kobayashi</surname>
            <given-names>N.:</given-names>
          </string-name>
          <article-title>An Intelligent SPARQL Query Builder for Exploration of Various Life-science Databases</article-title>
          ,
          <source>CEUR Workshop Proceedings 1279, The 3rd International Workshop on Intelligent Exploration of Semantic Data (IESD</source>
          <year>2014</year>
          ),
          <source>Riva del Garda</source>
          , Italy.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>2. YummyData: http://yummydata.org/</mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Umaka</surname>
            <given-names>REST</given-names>
          </string-name>
          API: http://d.umaka.dbcls.jp/api/speci cations
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>