<!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>Fast In-Memory Reasoner for Oracle NoSQL Database EE: Uncover Hidden Relationships that Exist in Your Enterprise Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Zhe Wu</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gabriela Montiel</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yuan Ren</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Je Z. Pan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Departmentof Computing Science, University of Aberdeen</institution>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Graph databases and NoSQL databases, two very important topics in Big Data, have gained popularity in recent years due to their unique characteristics in their horizontally scale-out capability and exible schema or schema-free design. The recent release of OWL-DBC 1, an adaptor between Oracle Spatial and Graph 2 and the TrOWL reasoner [2, 1], has built a tight integration between one of the leading industrial graph databases and the cutting edge, in-memory, semantic reasoner to achieve high quality and e cient semantic reasoning on large scale enterprise data. In this session we present OWL-NOSQL, which enhances the Oracle NoSQL Database EE 3 with e cient in-memory reasoning capability from TrOWL. With OWL-NOSQL, users are able to manage their enterprise data in the form of RDF Graph stored in Oracle NoSQL Database EE and gain insight into their data through powerful semantic reasoning. Oracle NoSQL Database EE is a horizontally scaled, key-value database for Web services and cloud. This system uses a simplistic key-value pair data model to achieve e ciency and high scalability. Despite of its simplicity, such a data model can be engineered to represent rather complex knowledge and structures in data, including RDF graphs and OWL ontologies. In fact, key-value pair databases have emerged as one of the promising solutions for semantic exploitation in recent years. Such exibility enables Oracle NoSQL Database EE to expose its data to external semantic applications, including semantic reasoners, to uncover hidden relationships in the stored data, especially those represent semantic annotations. More concretely, such a semantic extension of Oracle NoSQL Database EE is performed as follows: 1. Exporting RDF data stored in Oracle NoSQL Database EE into an ontology. 2. Performing reasoning using the semantic reasoner TrOWL to uncover hidden relationships in the data. 3. Importing reasoning results into Oracle NoSQL Database EE to persistent the uncovered relationships. According to our previous experience with OWL-DBC, the most signi cant performance challenge of such a solution rises from the data transferring be1 http://trowl.eu/owl-dbc/ 2 http://www.oracle.com/technetwork/database/options/spatialandgraph/overview/index.html 3 http://www.oracle.com/us/products/database/nosql/overview/index.html</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>tween database and reasoner. To address such an issues and o er faster data
exploitation, the following means have been taken:</p>
      <p>With the above solutions, we are able to improve the e ciency of data
transferring and reasoning. Together, OWL-NOSQL enhances Oracle NoSQL
Database EE with semantic reasoning, o ering more exibility to our clients in
terms of data storage, management and exploitation options.</p>
      <p>We are optimistic about OWL-NOSQL because many industries have already
embraced Semantic Web and NoSQL technologies. In the past decade, we have
observed more and more enterprise applications built on top of RDF and OWL
standards; and NoSQL technologies at the same time play an ever-increasingly
critical role for the management and analysis of Big Data. There clearly is a
natural synergy between these two sets of technologies.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Ren</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>J.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Soundness Preserving Approximation for TBox Reasoning</article-title>
          .
          <source>In: the Proc. of the 25th AAAI Conference Conference (AAAI2010)</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Thomas</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>J.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ren</surname>
          </string-name>
          , Y.:
          <article-title>TrOWL: Tractable OWL 2 Reasoning Infrastructure</article-title>
          .
          <source>In: the Proc. of the Extended Semantic Web Conference (ESWC2010)</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>