<!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>RDF Explorer: A Visual Query Builder for Semantic Web Knowledge Graphs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hernan Vargas</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carlos Buil-Aranda</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aidan Hogan</string-name>
          <email>ahogan@dcc.uchile.cl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Claudia Lopez</string-name>
          <email>claudiag@inf.utfsm.cl</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DCC, Universidad de Chile</institution>
          ,
          <addr-line>Santiago</addr-line>
          ,
          <country country="CL">Chile</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Instituto Milenio de Fundamentos de los Datos</institution>
          ,
          <addr-line>Santiago</addr-line>
          ,
          <country country="CL">Chile</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Universidad Tecnica Federico Santa Mar a</institution>
          ,
          <addr-line>Valpara so</addr-line>
          ,
          <country country="CL">Chile</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Despite the growing popularity of knowledge graphs for managing diverse data at large scale, users who wish to pose expressive queries against such graphs are often expected to know (i) how to formulate queries in a language such as SPARQL, and (ii) how entities of interest are described in the graph. In this demo we present a system that allows non-expert users to simultaneously navigate and query knowledge graphs by incrementally exploring the dataset.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        In a previous work [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], we presented a visual language whose operators are based
on an interactive graph-based exploration. That exploration allows non-expert
users to simultaneously navigate and query knowledge graphs e ectively. In that
work we discussed various desirable properties that a language for querying
SPARQL endpoints should have, such as avoiding interactions that lead to empty
results. Here we present a demo of the tool that implements such a language and
that allows querying SPARQL endpoints based on an exploration activity.
      </p>
      <p>
        Most popular user interfaces to query SPARQL endpoints simply propose a
text box that allows end users to write a query. However, using such interface
for querying graphs is challenging. First, users are required to have technical
knowledge of the query language and the semantics of its operators. Second,
graph data usually represents a variety of data from di erent domains, meaning
that the users may not be easily able to conceptualize the data that they are
querying. Despite these limitations, query services for DBpedia and Wikidata
are receiving in the order of millions of queries per day [
        <xref ref-type="bibr" rid="ref3 ref5">5,3</xref>
        ].
      </p>
      <p>Some approaches adopted by interfaces that allow lay users to visualise,
search, browse and query knowledge graphs involve keyword search, faceted
browsing, graph-based browsing, query building, graph summarization,
visualization techniques, and combinations thereof. Many of these systems however,
foster usability by removing SPARQL features such as the use of the OPTIONAL
operator or cycles within the query. Furthermore, interfaces that allow cycles
within graph patterns assume technical expertise of the query language and/or
knowledge of how data are modeled.</p>
      <p>Here we present an interface that aims to allow lay users to build and
execute graph-pattern queries on knowledge graphs; within our proposal, the user
navigates a visual representation of a sub-graph, and in so doing, incrementally
builds a potentially complex (cyclical) graph pattern. The interface can be
accessed at https://www.rdfexplorer.org and the code can be found in its
corresponding GitHub repository4.
2</p>
    </sec>
    <sec id="sec-2">
      <title>RDF Explorer</title>
      <p>
        In this section, we present the RDF Explorer system, whose goal is to enable lay
users to query and explore RDF graphs. We present the main characteristics of
the system as well as a description of how the overall system is implemented.
RDF Explorer Interface The interface is composed of six main components
displayed in three panes. Figure 1 provides a screenshot of the interface for
querying Wikidata, where we can see three components: a search panel (left
pane), a visual query editor (center pane), a node detail view (right pane); in the
top right corner are buttons to switch the right pane to display one of the three
other components: a node editor (allowing to add restrictions to a highlighted
node), a SPARQL query editor (showing the current query), and a help panel.
{ The search panel allows the user to search for an RDF resource (in Wikidata
currently, Figure 1 left). This feature uses a Wikidata index [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] to display
the results. The user can drag these resources onto the visual query panel to
start either exploring the graph or developing the SPARQL query.
{ The visual query panel allows the user to visually generate a SPARQL query
by adding variables as nodes and edges as properties. To be able to draw
an edge there has to be either a variable or an RDF resource previously
added from the search panel. If there are two RDF resources the interface
automatically adds a variable within the origin node and lists in the node
detail view the existing properties that relate these two nodes. The visual
query panel allows to draw a graph based on the data stored at the endpoint,
displaying information about each node in the node detail view.
{ The node detail view allows the user to visualize the properties of a node,
or a result set in the case that the node is a variable, iterating over the
possible results (Figure 1, center). The node view also allows to view the
SPARQL code of the query that is being developed and presents to the user
the possibility of manually adding speci c URIs to the node (Figure 1 right).
4 https://github.com/hvarg/RDFExplorer
      </p>
      <p>A Visual Query Builder for Semantic Web Knowledge Graphs
Query creation process The process starts with a blank visual query editor.
The user must then start by adding a new node, be it a variable node or a
constant node; for selecting x, the user can type a keyword phrase into the
search pane on the left, which will generate autosuggestions, where any of the
results shown can be dragged into the central query editor pane. The user may
then proceed to add a second node by the same means. With two or more nodes
available, the user can now click and drag between two nodes to generate an
edge with a variable edge-label (shown as a box nested inside the source node);
a list of potential IRIs will be suggested for replacing the variable, where only
IRIs that generate non-empty results for the underlying query will be o ered.</p>
    </sec>
    <sec id="sec-3">
      <title>Conclusions</title>
      <p>
        In this demo we presented the companion user interface to the paper in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
This user interface allows lay users to explore and query knowledge graphs,
currently con gured to access the Wikidata endpoint. The interface does this by
allowing users to understand how data is organized and presenting such data in
a comprehensible manner through di erent elements of the interface.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>S. S.</given-names>
            <surname>Bhowmick</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Choi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Li</surname>
          </string-name>
          .
          <article-title>Graph querying meets HCI: State of the art and future directions</article-title>
          .
          <source>In ACM International Conference on Management of Data</source>
          , pages
          <volume>1731</volume>
          {
          <fpage>1736</fpage>
          . ACM,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>A.</given-names>
            <surname>Clemmer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Davies</surname>
          </string-name>
          .
          <article-title>Smeagol: a \speci c-to-general" semantic web query interface paradigm for novices</article-title>
          .
          <source>In Database and Expert Systems Applications (DEXA)</source>
          , pages
          <fpage>288</fpage>
          {
          <fpage>302</fpage>
          . Springer,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>S.</given-names>
            <surname>Malyshev</surname>
          </string-name>
          , M. Krotzsch, L. Gonzalez,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gonsior</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Bielefeldt</surname>
          </string-name>
          .
          <article-title>Getting the Most Out of Wikidata: Semantic Technology Usage in Wikipedia's Knowledge Graph</article-title>
          .
          <source>In International Semantic Web Conference (ISWC)</source>
          , pages
          <fpage>376</fpage>
          {
          <fpage>394</fpage>
          . Springer,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. J.
          <string-name>
            <surname>Moreno-Vega</surname>
            and
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Hogan</surname>
          </string-name>
          . Grafa:
          <article-title>Scalable faceted browsing for RDF graphs</article-title>
          .
          <source>In The Semantic Web - ISWC 2018 - 17th International Semantic Web Conference</source>
          , Monterey, CA, USA, October 8-
          <issue>12</issue>
          ,
          <year>2018</year>
          , Proceedings,
          <string-name>
            <surname>Part</surname>
            <given-names>I</given-names>
          </string-name>
          , pages
          <volume>301</volume>
          {
          <fpage>317</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>M.</given-names>
            <surname>Saleem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. I.</given-names>
            <surname>Ali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Mehmood</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          . LSQ:
          <article-title>The Linked SPARQL Queries Dataset</article-title>
          .
          <source>In International Semantic Web Conference (ISWC)</source>
          , pages
          <fpage>261</fpage>
          {
          <fpage>269</fpage>
          . Springer,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>H.</given-names>
            <surname>Vargas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Buil-Aranda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Lopez</surname>
          </string-name>
          . RDF Explorer:
          <article-title>A Visual Query Builder for Semantic Web Knowledge Graphs</article-title>
          .
          <source>In International Semantic Web Conference (ISWC)</source>
          . To appear,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>