<!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>rSim: Simplifying an RDF Graph at the Visualization Tier for Non-Expert Users</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Rathachai Chawuthai</string-name>
          <email>rathachai@nii.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hideaki Takeda</string-name>
          <email>takeda@nii.ac.jp</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>SOKENDAI (The Graduate University for Advanced Studies), Japan National Institute of Informatics</institution>
          ,
          <addr-line>Tokyo</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <abstract>
        <p>Using a concept-map or a node-link diagram for representing knowledge can enhance the learning ability of users. However, the queried RDF graph can be complex and difficult for non-expert users to read, because many redundant triples entailed by RDFS and OWL rules are also included. Existing tools can rearrange, filter, highlight and summarize a graph for visualization but they require human effort. For this reason, this research attempts to use Semantic Web rules and schemas to simplify a graph automatically at the visualization tier. The prototype shows that the simplified graph is easier to read than the original one. In future, this method will be positioned as a plugin for other visualization tools in order to serve attractive RDF-based knowledge to users.</p>
      </abstract>
      <kwd-group>
        <kwd>Graph Simplification</kwd>
        <kwd>RDF Visualization</kwd>
        <kwd>Semantic Web Rule</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>This research introduces a method to simplify a highly connected RDF (Resource
Description Framework) graph at the visualization tier, and demonstrates an easily
readable graph for non-expert users. This contribution is suitable for consumers who
(1) are willing to use RDF graph visualization as learning and teaching tools, and (2)
believe in the role of Linked Open Data (LOD) for future knowledge management.</p>
      <p>
        It is known that displaying RDF data to general users is very challenging as RDF
expressions are not human-friendly. For this reason, graph visualization becomes an
alternative way to enhance the learning ability of users from beginners to advanced
levels. In this paper, a term “beginner” is used as a user who does not know Semantic
Web well (lay-user) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], and one is new to domain knowledge (non-domain-expert)
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. In terms of using LOD for education, concept maps can be successfully adopted
for e-learning for beginners [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and the graph should be sparse and easy to read [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>However, in practice, a displayed graph is sometimes extremely difficult to read as
shown in Figure 2(a) due to a large number of inferred triples. They are resulted from
some well-prepared RDF repositories having reasoning on schemas, rules, and
sameas instances (owl:sameAs). In general, a schema defines members of classes,
hierarchies of classes and properties, and characteristics of properties. For example,
rdf:type, rdfs:subClassOf, rdfs:subPropertyOf, owl:equivalentProperty,
owl:TransitiveProperty, owl:inverseOf, etc. are always found in any schema. After
having RDFS and/or OWL entailments, a network dataset becomes more complex
because giant components and node pairs with multiple edges are arisen. This
condition makes a visualization tier is not suitable for reading.</p>
      <p>
        To display an easy and readable RDF graph, there are several pieces of research
working on this issue. Motif Simplification compresses some topologies of subgraphs
into basic shapes such as diamonds and fans [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. RDF Gravity offers a zoomable
graph with text overlays [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Fenfire gives a clear display for immediate nodes, but
fades away the others, which are far from the focus [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. IsaViz uses graph style sheets
to draw a graph with meaningful icons and it groups metadata into tables to display in
a canvas [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Motif Simplification aims to give the overall structure of a network
rather than detail. RDF Gravity and Fenfire do not reduce the issue of redundant data.
IsaViz requires human effort to filter some nodes or properties to sparsify a dense
graph. For this reason, this study is an attempt to simplify an RDF graph for beginners
by reducing some redundant nodes and inferred links with less human effort.
      </p>
      <p>According to the mentioned issue, this paper proposes a rule-based methodology
named rSim where its scope is to give a simplified graph visualization for beginners
to read and learn knowledge represented by RDF data. A prototype is implemented in
order to demonstrate the possibility and feasibility of the proposed approach.
2</p>
      <p>rSim Approach
To visualize an RDF query result for beginners, rSim (RDF Simplification) approach
is introduced to eliminate some redundant triples which are resulted from reasoning
on schemas. This research initiates a set of rules (rSim’s rules) that works with the
available schemas to clean up a graph of query result. Thus, it requires queried triples,
schemas, and rSim’s rules as inputs to produce a clean graph for the visualization tier
as shown in Figure 1. The involved components are displayed in the dash rectangular.
The query result is in RDF format, the schemas such as owl files are provided by any
repositories, the rSim’s rules are described hereafter, and the process “Simplify” does
the reasoning on the three input components for generating simplified RDF data.
The rSim’s ruleset is formally defined in Table 1 and the objective of each rule is
described in the following list.</p>
      <p>- Rules #1-4 are to merge either nodes or triples that contain some same-as
resources by selecting high frequently occurring nodes to display.
- Rule #5 is to remove some transitively inferred individual-class relationships.
- Rule #6 is to eliminate some links that are resulted from transitive entailment.
- Rules #7-8 are to select only one link among multiple links of a node pair based
on the characteristics of properties that are transitive and inverse links.
- Rule #9 is to choose the most frequent property from some equivalent properties.
- If a canvas cannot well-display multiple links between a node pair, the Rule #10
is used to select only one link that is the most frequent occurring property.
The occurrence number should be counted across repositories, because a popular URI
has a high chance to discover more knowledge in next queries. Further, the graph
should display human-readable labels instead of URIs.
To demonstrate the possibility and feasibility of the proposed approach, a prototype is
developed and accessible at “http://rc.lodac.nii.ac.jp/rsim/ ”. The dataset and schema
are from the LODAC repository1 that gathers a large number of inferred triples of
biodiversity data. In our experiment, we queried the whole neighborhood of a given
node within two hops, and compared the original query result with our simplified
graph. Figure 2(a) shows about 200 raw triples queried using the resource
lodac:Bubo, whereas rSim simplifies them into 20 triples as shown in Figure 2(b).</p>
      <p>For the user perspective, any beginners, who have less background knowledge
about biodiversity and RDF, are appreciated the result of rSim. This work helps to
inspire users to use a graph visualization as a learning tool. It also induces them to
understand and realize the power of Linked Open Data for knowledge management.</p>
      <p>In future, we intend to integrate rSim with some existing visualization features
from the related works such as zoom in/out, blur unfocused nodes, replace blurred
area by motif shapes, group node-attribute triples into a table, show meaningful icons,
and allow user-defined conditions for filtering triples.
1 LODAC: Linked Open Data for Academia (http://lod.ac)
Coelurosauria</p>
      <p>hasParentTaxon
hasSynonym
birds</p>
      <p>Class
hasTaxonRank</p>
      <p>Neognathae
hasParentTaxon
Aves
hasTaxonRank
type</p>
      <p>Order
hasTaxonRank owls</p>
      <p>hasSynonym
Strigiformes
hasParentTaxon Family</p>
      <p>StrigidaehasTaxonRank
hasParentTaxon
BubohasSynonym
hasTaxonRank
Genus</p>
      <p>type
eagle owls</p>
      <p>Common Name
(a)</p>
      <p>Conclusion and Future Work
This research introduced the method name rSim to simplify an RDF graph for
visualizing data to general users by using Semantic Web rules to eliminate some redundant
triples. The proposed rules can be viewed as inversions of RDFS and OWL in order to
handle some cases of same-as resources, equivalent properties, class hierarchies,
property hierarchies, transitive properties, inverse properties, etc. Most redundant
triples are eliminated while the remaining triples can serve the overall information
that is easy to be read by for non-domain-expert users.</p>
      <p>Since this work focuses on RDF visualization for beginners, more details should be
added according the learning ability of a user when they becomes more expert. This
research is planned to be enhanced for more flexibility to every level of users based
on domain knowledge, user preference, and ability to understand RDF expression.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Dadzie</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rowe</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Approaches to visualising Linked Data: A survey</article-title>
          .
          <source>In: Semantic Web Journal</source>
          , pp.
          <fpage>89</fpage>
          -
          <lpage>124</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Edelson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gordin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Visualization for learners: a framework for adapting scientists' tools</article-title>
          .
          <source>In: Computers &amp; Geosciences</source>
          , pp.
          <fpage>607</fpage>
          -
          <lpage>616</lpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Schwendimann</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Concept maps as versatile tools to integrate complex ideas: From kindergarten to higher and professional education</article-title>
          . (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Novak</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cañas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The theory underlying concept maps and how to construct and use them</article-title>
          .
          <source>In: Florida Institute for Human and Machine Cognition</source>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dunne</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shneiderman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Motif simplification: improving network visualization readability with fan, connector, and clique glyphs</article-title>
          .
          <source>In: SIGCHI2013</source>
          , pp.
          <fpage>3247</fpage>
          -
          <lpage>3256</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Goyal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Westenthaler</surname>
          </string-name>
          , R.:
          <article-title>RDF gravity (RDF graph visualization tool</article-title>
          ). (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Tuukka</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , et al.:
          <article-title>Browsing linked data with Fenfire</article-title>
          .
          <source>In: LDOW</source>
          <year>2008</year>
          .
          <article-title>(</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Pretorius</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , et al.:
          <article-title>What does the user want to see? What do the data want to be?</article-title>
          .
          <source>In: Information Visualization</source>
          , vol.
          <volume>8</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>153</fpage>
          -
          <lpage>166</lpage>
          . (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>