<!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>RIF-BLD Reasoning with IRIS</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Winkler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Reto Krummenacher</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adrian Marte</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Semantic Technology Institute (STI) Innsbruck, University of Innsbruck</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>IRIS is an open-source, Java-based Datalog reasoner that supports various evaluation strategies and extensions such as function symbols and equality in the rule conclusion. The main objective of IRIS is to serve as general purpose reasoner for the Semantic Web, which is realized by an implementation that focuses on compliance with existing W3C standards like the Rule Interchange Format (RIF), thereby supporting the XML Schema De nition datatypes. Furthermore, IRIS acts as base for extensions that allow for reasoning with the OWL 2 proles EL and RL and the Web Service Modeling Language (WSML). In this demo, we present the IRIS reasoner and its applications, as well as the larger WSML2Reasoner framework with IRIS at its core. The basic IRIS implementation for RIF and OWL 2 reasoning is stable, however, further performance improvements and the implementation of e ective parallelized rule-based reasoning strategies that are ongoing work will also be presented.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>OWL 2 provides dialects that are restricted in their semantic expressivity for the
sake of better reasoning behavior; e.g., OWL EL or OWL RL pro les. The very
same idea is at the basis of the WSML language family that we will encounter
throughout this demo description, in particular the variants WSML-Rule and
WSML-Flight. De ning such language variants helps in establishing formalisms
that are expressive enough to be useful, while exhibiting reasoning characteristics
that can also scale to the size of the Web, which is exactly the application area
we address with our rule-based reasoner IRIS.</p>
      <p>The Integrated Rule Inference System IRIS is realized with generality,
exibility and extensibility in mind.2 Not at last for this reason, IRIS can be used as
core engine for di erent reasoners that tackle diverse formalism ranging across
various RIF, OWL 2 and WSML dialects; cf. subsequent sections. E ectively,
IRIS is applied in di erent research projects for diverse tasks; e.g., semantic
discovery, ranking and design-time service composition in the integrated project
SOA4All and as general purpose reasoning plug-in in LarKC.3 Being open-source
and Java-based further increases the impact, and IRIS is leveraged in many other
research projects and applications. So far, IRIS was downloaded more than 1500
times from sourceforge.net, not taking into account the accesses via the project's
Maven repository.</p>
      <p>The continuation of this paper is structured as follows. In Section 2 we present
our rule-based reasoning engine IRIS, and show how it is used as reasoner for
di erent pro les, mainly RIF-BLD. In the same section we present RIF4J, a Java
object model for RIF rule bases. Section 3 provides a comprehensive
presentation of a RIF-BLD demo application scenario, and yields some pointers towards
the use of IRIS for reasoning about time and intervals via corresponding RIF
built-ins. In Section 4, we discuss di erent extensions to IRIS that embed the
reasoner in a larger framework in order to support di erent OWL 2 and WSML
dialects. This allows for even more diverse support for reasoning on the Web.
We conclude with Section 5, and present a brief discussion of future extensions
and applications of IRIS.
2</p>
    </sec>
    <sec id="sec-2">
      <title>IRIS as RIF Reasoner</title>
      <p>The Rule Interchange Format (RIF) by the W3C RIF Working Group enables
the semantic and syntactic description of rule systems, which can be further used
to exchange axiomatic knowledge between systems.4 It includes a framework for
de ning logic dialects, several concrete dialects, datatype de nitions and
builtin predicates and functions. In a rst subsection (Section 2.1) we will shortly
present the most relevant RIF dialects, and how our Datalog reasoning engine
IRIS responds to them. 5
2 http://www.iris-reasoner.org/
3 SOA4All: http://www.soa4all.eu, LarKC: http://www.larkc.eu/
4 http://www.w3.org/2005/rules/wiki/RIF_Working_Group
5 An online demonstrator of the pure Datalog implementation, not subject to this
demonstration, is published at http://www.iris-reasoner.org/demo.</p>
      <sec id="sec-2-1">
        <title>2.1 IRIS and RIF Dialects</title>
        <p>
          The RIF Datatypes and Built-Ins (RIF-DTB, [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]) document speci es a list
of datatypes, built-in functions and built-in predicates | mostly adapted from
XPath functions [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] and XML Schema Datatypes (XSD, [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]) | that are
expected to be supported by all RIF dialects. In this sense, RIF DTB de nes the
functional baseline for any RIF reasoner; unless explicitly de ned di erently by a
given pro le. IRIS has recently been updated to support the full range of built-in
RIF functions and predicates, and all datatypes de ned by XSD | going beyond
the RIF standard | with the exception of the list-related ones.6
        </p>
        <p>
          The RIF Core dialect is contained in the intersection of the production rules
(RIF-PRD) and basic logic (RIF-BLD, [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]) pro les, thereby building a base
for both of them. From a theoretical point of view, the expressivity of RIF
Core corresponds to Datalog. Due to the very nature of IRIS, Datalog and thus
the expressivity of RIF Core are captured by the implementation, furthermore
various evaluation strategies and optimizations are implemented.
        </p>
        <p>
          The RIF-BLD dialect corresponds, in terms of expressivity, to the language
of de nite Horn rules with equality and a standard rst-order semantics. IRIS
was extended to support the full range of language constructs de ned in
RIFBLD, thereby investigating the impacts of equality in rule conclusions in detail.
In speci c, IRIS uses semi-naive bottom-up evaluation as default evaluation
strategy for query answering [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. In case of equality assertions, however, the
strategy has to fall back to naive evaluation as pre-computed facts need to be
reevaluated in terms of equality. Improvements are subject to further investigations
and none are yet re ected in the implementation.
        </p>
        <p>
          RIF Core and RIF-BLD are also at the basis of the W3C recommendation
on how to interpret combinations of RIF documents and RDF data, as well as
RDFS and OWL ontologies [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. Supporting RIF-BLD can thus also be seen as
a prerequisite for the implementation of a fully- edged rule-based reasoner for
the (Semantic) Web.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>RIF4J | An Object Model for RIF Rule Bases</title>
        <p>While IRIS supports all the necessary logical constructs to o er a RIF-BLD
reasoner, it still needed to parse and understand the RIF syntax. The RIF4J Java
library provides the necessary extensions and o ers a parser and object model for
RIF rule bases.7 Although RIF4J was conceptualized and developed as interface
for RIF rule bases on top of IRIS, the object model is fully independent of any
IRIS libraries. Consequently, RIF4J not only provides the required functionality
to make IRIS a RIF-minded reasoning engine, but rather provides a general
purpose set of technicalities for working with RIF construct.</p>
        <p>
          Besides support for parsing RIF rule bases and for processing and modeling
RIF rules in a Java object model, RIF4J o ers an extension to serialize rule bases
6 RIF Lists, xsd:ENTITIES, xsd:IDREFS, xsd:NMTOKENS
7 http://sourceforge.net/projects/rif4j/
to WSML logical expressions. In fact, WSML was the initial language stack which
IRIS was built for [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. The WSML language variants partly form supersets and/or
subset of RIF-BLD, which allows for a simple syntactical mapping from RIF to
WSML (cf. Section 4.2). To this end, by translating RIF rule bases to WSML
logical expression, RIF4J realizes the RIF reasoner functionalities of IRIS on
top of and by means of the well-tested and stable WSML2Reasoner framework,
which is shortly presented in Section 4.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>RIF-BLD Application Scenario</title>
      <p>
        To illustrate how IRIS can be leveraged to reason with RIF-BLD rules, we present
a hypothetical scenario based on the use case \Negotiating eBusiness Contracts
Across Rule Platforms" in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. The core rule of the scenario is provided as \If
an item is perishable and it is delivered to John more than 10 days after the
scheduled delivery date then the item will be rejected by him". This rule is
formally given in Table 1 on lines 6{14, using RIF presentation syntax (cf. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]).
      </p>
      <p>According to the core rule of the example, John is negotiating a business
contract for the shipment of di erent goods. John is very critical about the late
delivery, and indicates that products, which arrive more than ten days after the
scheduled date, will be rejected, if they are perishable. The rule base for our
example moreover contains the claim that groceries are perishable (line 15), and
that the scheduled delivery date of an item is inherited from the delivery date of
the order (lines 16{19). In this weeks order (line 20), John requests, among many
other things, that the IRIS software package and some milk shall be delivered to
him (lines 22{27). According to the agree delivery schedule, the products should
reach John by August 20, 2010 (line 21). The fact base states as well, on lines
28{30, when the di erent good were delivered to John.</p>
      <p>The RIF-BLD reasoner can then be used for entailment checking against or
querying over the speci ed rule base. For the purpose of this demo, there is a user
interface publicly available at http://iris.sti2.at/reasoners/rif-reasoner/.
By means of the following query: cpt:reject(ex:John ?x), it is possible, for
example, to check if John does reject any of the delivered items. In the given
case of Table 1, John indeed does not accept the milk item, as it is eventually
delivered signi cantly later than the agreed August 20, 2010.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Reasoner Extensions</title>
      <p>This section brings IRIS into a larger context, and discusses the use of the
Datalog reasoning engine as fundamental building block for the WSML2Reasoner
framework, including the ELP reasoner Elly. Figure 1 reconciles the relevant
software components. The two components on the left, RIF4J and WSMO4J,8
represent the object models that are used to maintain the static data of the
knowledge bases that can be reasoned over. Additionally, the OWL API, a
development mostly driven by the University of Manchester,9 provides a third
data model component for the reasoning and manipulation of OWL ontologies.
As such, the OWL API provides the reasoner interface that is implemented
by Elly for supporting OWL 2 EL and RL pro les, as shortly discussed in
Section 4.1. Subsequently, in Section 4.2, we present how the WSML2Reasoner
framework serves as entry point for RIF and WSML reasoning by means of
RIF4J/WSMO4J as object models, and IRIS and Elly as default reasoning
engines.
4.1</p>
      <sec id="sec-4-1">
        <title>Web Ontology Language (OWL) 2 EL and RL Reasoning</title>
        <p>ELP has been presented as a hybrid between Logic Programming (LP) and
Description Logics (DL) that combines the tractable DLs EL++ and DLP in a novel
8 WSMO4J is an API and a reference implementation for WSML constructs.
9 http://owlapi.sourceforge.net</p>
        <p>WSML2Reasoner</p>
        <p>OWL API
Object Model</p>
        <p>LP Reasoner</p>
        <p>DL Reasoner</p>
        <p>OWL Reasoner
WSMO4J
Datalog</p>
        <p>Reasoner
IRIS</p>
        <p>
          ELLY
way [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. These two formalisms serve as logical foundation for the OWL 2 pro les
EL and RL, which are thus fully captured by the semantics of ELP [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Since ELP
does not only de ne the semantics of the language, but also provides a tractable
reasoning algorithm that translates ELP rule bases into Datalog rule bases, a
corresponding extension to IRIS could be implemented.
        </p>
        <p>
          Elly is a reasoner for entailment and satis ability checking of ELP rule
bases.10 Its core package implements an object model for ELP rule bases and
a reasoner based on the translation algorithm to Datalog [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. Elly is
implemented on top of IRIS and reuses, but abstracts, all of the built-in datatypes
and predicates of IRIS; as such that Elly can be considered an extension to
IRIS. Elly, like all other software presented in this paper, is released under the
LGPL 2.1 license.11.
        </p>
        <p>As mentioned above, ELP subsumes the semantics of the OWL 2 pro les EL
and RL. To this end, the ELP reasoner Elly, in integration with the parsers,
object models and reasoning interfaces of the OWL API, becomes a fully- edged
OWL 2 EL and RL reasoner.12
4.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Web Service Modeling Language (WSML) Reasoning</title>
        <p>
          The Web Service Modeling Language WSML is a formal language for the speci
cation of ontologies and the modeling of Semantic Web services descriptions [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
Several di erent WSML language variants exist, which are based upon di erent
logical formalisms. More recently, WSML has been released in version 2.0 such
that it provides an alignment of the LP-based variants with RIF and tractability
of the WSML-DL dialect due to alignment of the semantics to ELP [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
        <p>WSML2Reasoner is a highly modular framework that combines various
validation, normalization and transformation algorithms that enable the translation
10 http://elly.sourceforge.net/
11 http://www.gnu.org/licenses/lgpl.txt
12 Notably, Elly is listed on http://www.w3.org/2007/OWL/wiki/Implementations as
reasoner for the OWL 2 EL and RL pro les.
of ontology descriptions in WSML to a generic syntax, which is interpretable by
underlying reasoning engines.13 A rst task of WSML2Reasoner is the
provisioning of translation modules for the mapping of WSML variants onto Datalog (with
certain extensions) or ELP. Although designed to be extensible for other
reasoners, the default release of WSML2Reasoner is shipped with IRIS and Elly only,
as this o ers the most comprehensive support for the semantics of the
respective variants and all built-ins required by RIF-DTB. All in all, WSML2Reasoner
yields a complete reasoning infrastructure for the WSML language family.</p>
        <p>Online demonstrators for WSML-based reasoning are also available:
{ WSML-DL v2.0, http://iris.sti2.at/reasoners/wsml-dl-reasoner/
{ WSML-Rule v2.0, http://iris.sti2.at/reasoners/wsml-rule-reasoner/
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusions and Future Work</title>
      <p>Going beyond the initial purpose of being a Datalog reasoner for WSML, IRIS
{ together with WSML2Reasoner and other presented software components {
evolved to a comprehensive reasoning infrastructure for the (Semantic) Web.
Important in this respect is a strict conformance to existing Web standards
and di erent knowledge base representation formalisms, such as RIF, OWL and
WSML.</p>
      <p>In this paper we presented the current status of IRIS, and emphasized on
the application and demonstration of IRIS as RIF-BLD reasoner. Although
stable and already used in various projects, there is still further work to be done.
To conclude the paper, we shortly address the two most relevant and currently
ongoing improvements. IRIS currently relies on an in-memory Java
implementation, and hence, performance-wise, cannot keep up to comparable reasoners
that leverage database bindings; in particular when dealing with big and growing
knowledge bases. To counter-act this limitation, work has started to persist facts
in a relational database system. The reasoning algorithms would still be run on
an in-memory object model, and hence, subsequent work will deal with moving
the reasoning tasks (closer) to the database query engine. The envisaged result
would be a feature-rich Datalog reasoner for the Web enhanced with the speed
and scalability of a relational database engine.</p>
      <p>
        A second enhancement currently under investigation in the LarKC project
is the development of parallelized Datalog rule bases leveraging techniques such
as data and rule partitioning [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and map-reduce-style programming models [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
The LarKC project develops a platform for massive distributed incomplete
reasoning that shall remove the scalability barriers of currently existing reasoning
systems for the Semantic Web.
      </p>
      <p>Acknowledgment: The work on IRIS is supported by the EU FP7 IP
SOA4All, and the e-Infrastructures project SEALS.
13 http://tools.sti2.at/wsml2reasoner/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bishop</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fischer</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>IRIS - Integrated Rule Inference System</article-title>
          .
          <source>In: 1st Workshop on Advancing Reasoning on the Web: Scalability and Commonsense (June</source>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kifer</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>RIF Basic Logic Dialect</article-title>
          . W3C
          <string-name>
            <surname>Recommendation</surname>
          </string-name>
          (
          <year>June 2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. de Bruijn, J.,
          <string-name>
            <surname>Lausen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>The Web Service Modeling Language WSML: An Overview</article-title>
          .
          <source>In: 3rd European Semantic Web Conference</source>
          . pp.
          <volume>590</volume>
          {
          <issue>604</issue>
          (
          <year>June 2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. de Bruijn, J.:
          <source>RIF RDF and OWL Compatibility. W3C Recommendation</source>
          (
          <year>June 2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dean</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghemawat</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>MapReduce: Simpli ed Data Processing on Large Clusters. Communications of the ACM</source>
          <volume>51</volume>
          (
          <issue>1</issue>
          ),
          <volume>107</volume>
          {113 (
          <year>January 2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ganguly</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Silberschatz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tsur</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A Framework for the Parallel Processing of Datalog Queries</article-title>
          .
          <source>ACM SIGMOD Record</source>
          <volume>19</volume>
          (
          <issue>2</issue>
          ),
          <volume>143</volume>
          {152 (
          <year>June 1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. Krotzsch,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Rudolph</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Hitzler</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          : ELP:
          <article-title>Tractable Rules for OWL 2</article-title>
          .
          <source>In: 7th Int'l Semantic Web Conference</source>
          . pp.
          <volume>649</volume>
          {
          <issue>664</issue>
          (
          <year>October 2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Malhotra</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melton</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Walsh</surname>
          </string-name>
          , N.:
          <article-title>XQuery 1.0 and XPath 2.0 Functions and Operators</article-title>
          . W3C
          <string-name>
            <surname>Recommendation</surname>
          </string-name>
          (
          <year>January 2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Motik</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lutz</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>OWL 2 Web Ontology Language Pro les</article-title>
          .
          <source>W3C Recommendation (October</source>
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hirtle</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ginsberg</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patranjan</surname>
            ,
            <given-names>P.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCabe</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>RIF Use Cases and Requirements</article-title>
          .
          <source>W3C Working Draft (December</source>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Peterson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gao</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malhotra</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sperberg-McQueen</surname>
            ,
            <given-names>C.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thompson</surname>
            ,
            <given-names>H.S.</given-names>
          </string-name>
          :
          <string-name>
            <surname>W3C XML Schema</surname>
          </string-name>
          <article-title>De nition Language (XSD) 1.1 Part 2</article-title>
          :
          <string-name>
            <surname>Datatypes. W3C Working Draft</surname>
          </string-name>
          (
          <year>December 2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kifer</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>RIF Datatypes and Built-Ins 1.0</article-title>
          .
          <string-name>
            <given-names>W3C</given-names>
            <surname>Recommendation</surname>
          </string-name>
          (
          <year>June 2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Ullman</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          :
          <article-title>Principles of Database and Knowledge-Base Systems: Volume II: The New Technologies</article-title>
          . W. H. Freeman &amp; Co. (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Winkler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>ELLY - An ELP Reasoner</article-title>
          .
          <source>Master Thesis</source>
          , Semantic Technology Institute (STI) Innsbruck, University of Innsbruck (April
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>