<!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>Building Applications and Tools for OWL - Experiences and Suggestions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Thorsten Liebig</string-name>
          <email>thorsten.liebig@uni-ulm.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marko Luther</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Olaf Noppens</string-name>
          <email>olaf.noppens@uni-ulm.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Massimo Paolucci</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matthias Wagner</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Friedrich von Henke</string-name>
          <email>friedrich.von-henke@uni-ulm.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Dept. of Artificial Intelligence, University of Ulm</institution>
          ,
          <addr-line>D-89069 Ulm</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Future Networking Lab, DoCoMo Communications Laboratories Europe</institution>
          ,
          <addr-line>D-80687 Munich</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The success of the Semantic Web will largely depend on whether W3C's Web Ontology Language can reach broad acceptance and a critical mass of industry-strength applications. We have been exploiting the use of OWL with a particular focus on tool support for ontology authoring and on providing access to the Semantic Web for mobile applications. In the latter case our vision is to overlay the Semantic Web on ubiquitous computing environments making it possible to represent and interlink content and services as well as users, devices, their capabilities and the functionality they offer. In this paper we present our first experiences and lessons learned from early work and try to give constructive feedback for possible enhancements of OWL and its tools.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>OWL ontologies are arguably key building blocks of the future Semantic Web. In
fact, the success of the Semantic Web will largely depend on whether W3C’s Web
Ontology Language can reach broad acceptance and a critical mass of
industrystrength applications. In our research – with the vision of mobile and ubiquitous
access to the Semantic Web in mind – ontologies are also crucial in aspects
of mobile and pervasive computing. For the past few years, we have exploited
the usage of OWL within several practical projects that we briefly introduce in
the following. These projects are either concerned with fundamental support for
OWL-based development and/or with OWL-based services and applications in
the mobile computing arena.</p>
      <p>After shortly presenting our projects in the following section, we discuss
fundamental language as well as technical aspects of the Web Ontology Language
from the perspective of developing OWL applications and tools. Within the
context of our projects we have identified limitations and problematic issues in
the language specification itself as well as in the tool support. As the usage of
ontologies is typically tightly coupled with reasoning systems, a particular focus
is put on DL-based reasoning support for OWL.</p>
    </sec>
    <sec id="sec-2">
      <title>ContextWatcher</title>
    </sec>
    <sec id="sec-3">
      <title>MobiXpl</title>
      <p>OWL-SF</p>
    </sec>
    <sec id="sec-4">
      <title>MobileOWLS</title>
      <p>Context</p>
    </sec>
    <sec id="sec-5">
      <title>MobiOnt</title>
      <p>OWL-S</p>
    </sec>
    <sec id="sec-6">
      <title>OntoTrack</title>
      <p>Representation
Service
g
n
i
n
o
s
a
e
R</p>
    </sec>
    <sec id="sec-7">
      <title>DL-Reasoner</title>
    </sec>
    <sec id="sec-8">
      <title>McAnt</title>
      <p>OWL</p>
    </sec>
    <sec id="sec-9">
      <title>Knowledge Editors</title>
      <p>
        Major challenges in designing ubiquitous context-aware systems include the
distributed nature of context information and the heterogeneity of devices that
provide services and deliver context. We have approached these challenges within
the project Owl-SF [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], a distributed semantic-based service framework. In the
Owl-SF prototype, OWL is used to capture high-level context elements in
semantically well founded ways. Devices, sensors and other environmental entities
are encapsulated and connected to the upper context ontology using OMG’s
Super Distributed Objects technology and communicate using the
Representational State Transfer model. An early use case of Owl-SF studies enhanced
presence control to realize intelligent call forwarding [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
2.2
      </p>
      <sec id="sec-9-1">
        <title>ContextWatcher</title>
        <p>
          Within the IST project MobiLife3 [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] we have implemented ContextWatcher,
an early prototype for semantic-based monitoring of mobile users. The project
aims at frameworks for context-aware services that support users in their daily
life. OWL upper context ontologies define the basic contextual categories and
the relations among them. Such high-level structuring of context information
enables its integration and consolidation on a semantic basis. Furthermore, the
axiomatic descriptions of context elements such as personal situations (i.e.,
Working, At home, etc.) can directly be used by logical inference engines to realize
reasoning about the user’s presence and virtual location [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ].
2.3
        </p>
      </sec>
      <sec id="sec-9-2">
        <title>McAnt</title>
        <p>
          With our prototype McAnt we try to explore possibilities and core
technologies towards leveraging the Semantic Web for desktop application enhancements
[
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. The idea is to deploy qualitative reasoning on the user’s personal desktop
environment to enable a more refined support for personal information
organization. As in our related activities, OWL and DL-based reasoning are explored as
enabling technologies for semantic enrichment. McAnt currently extends
Apple’s desktop environment in terms of the Apple Address Book and the iCal
calendar tool. The project introduces a set of core ontologies that describe novel
OWL-based smart groups that build on Apple’s smart groups and folders.
2.4
        </p>
      </sec>
      <sec id="sec-9-3">
        <title>OntoTrack</title>
        <p>
          OntoTrack [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] is a novel graphical ontology editor and authoring tool. In
contrast to many other ontology authoring tools it combines an interactive
graphbased visualization with instant reasoning feedback about logical consequences
of ontology changes. The graphical representation provides a directly editable
subsumption graph. Moreover, each editing step is instantly synchronized with
a reasoner to provide feedback about logical consequences such as subsumption
relationships or unsatisfiablity of classes. This kind of direct feedback promise
to help the user identify non-intended modeling errors. Recently, we extended
OntoTrack with an on-demand textual explanation of subsumption.
2.5
        </p>
      </sec>
      <sec id="sec-9-4">
        <title>MobiONT and MobiXPL</title>
        <p>
          The discovery of adequate services will become a more and more demanding
problem especially for the mobile user who has to cope with changing context
3 MobiLife is an integrated project within the 6th Framework Program of the
European Commission, Project-No. IST-2004-511607(IP)
and limitations of mobile terminals. We have implemented MobiOnt and
MobiXpl – a semantic matchmaker for service discovery and a personal mobile
client – to explore mobile user-centered services on the Semantic Web [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Our
vision is to take full advantage of future complex service offerings on limited
client devices and to handle the need for personalized service discovery in mobile
environments. Main contributions are in support for browsing service ontologies,
the cooperative discovery of services as well as an intuitive preference model that
can be easliy managed on restricted clients [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
2.6
        </p>
      </sec>
      <sec id="sec-9-5">
        <title>MobiOWLS</title>
        <p>
          MobiOwlS is a new project in which we attempt to extend the OWL-S [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] upper
ontology for services to describe services for mobile and ubiquitous computing.
Our initial investigation concentrated on extending the OWL-S Profile to include
crucial quality-of-service information and contextual information that in our
experience is required to locate the best service that satisfies the needs of the
user. For example, we extended OWL-S with properties such as Media that
specifies the type of media, such as video vs text, that is used to deliver the
service, or the CostModel of the service, such as flat rate or a fee-per-use.
3
3.1
        </p>
        <sec id="sec-9-5-1">
          <title>Experiences and Suggestions</title>
        </sec>
      </sec>
      <sec id="sec-9-6">
        <title>Representation</title>
        <p>
          References, Imports, and Ontology Headers. As a vocabulary extension
of RDF the Web Ontology Language inherits all of the reference and distribution
mechanisms of the lower language levels. For example, an OWL class (or
property) can be identified with help of an unambiguous URI given in the rdf:ID
tag. Furthermore, OWL allows for the distribution of a class (or property) across
multiple defining axioms within various RDF documents. It is even possible to
define a class bearing a virtual URI not related to any of the defining documents.
Syntactically this will raise a number of issues not only w.r.t. editing support
with help of authoring tools [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Because, when referring to this class from
elsewhere, its corresponding definition cannot be found at the URI implied by the
class ID.
        </p>
        <p>
          Another problem is related to imports and ontology editing. Importing means
to include all statements of the imported ontology into the importing ontology.
Now, an ontology authoring tool has to distinguish between those statements of
the importing and those of the imported ontology during editing [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. Imported
axioms should be visible because they are important for capturing the complete
set of definitions of the importing ontology. On the other hand, the imported
axioms do not belong to the ontology the user currently is editing. Very likely
the user is not interested to change imported ontologies by accident.
        </p>
        <p>Furthermore, the notion of an ontology, by specifying an ontology header
with the owl:Ontology tag, is an additional structuring element within OWL.
Such an ontology header is optional or may even appear more than once in a
document. As a result, the relationship between class and property axioms and
an ontology is unclear. To make things even more confusing, an ontology header
is the only way to import other documents or to encode versioning information
for ontologies.</p>
        <p>
          In addition, the vision of the Semantic Web heavily builds on sharing and
re-using ontologies. However, neither importing nor referencing are appropriate
mechanisms for this task. Importing requires to include all ontologies (within
the transitive closure of the import relationship) into reasoning. In contrast,
referencing entities of other ontologies is just a syntactical mechanism without
considering any semantics. To overcome these fundamental problems, OWL needs a
clearer semantical foundation, and practical mechanisms for handling imports,
ontologies and cross ontology references in first place. The recently proposed
E -connection mechanisms [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] seem to be a good starting point for supporting
the sharing and re-usage of ontologies.
        </p>
        <p>
          The Sublanguages of OWL. OWL comes with three increasingly expressive
sublanguages in order to meet different user requirements and developer efforts.
OWL Lite – the least expressive language – is aiming to provide a useful
subset of language features that are easy to present to naive users and relatively
straightforward for tool implementers to support [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. However, the syntactical
limitations come with relatively little loss in expressive power. With the help of
syntactical tricks all of OWL DL, the sub-language next-higher in expressiveness,
can be captured in OWL Lite with the exception of those descriptions containing
either individuals or cardinalities greater than 1 [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. In fact, OWL Lite is a very
expressive language, whose set of syntactical language constructs has been more
or less randomly restricted. As a result, when using the whole expressiveness
of OWL Lite the resulting ontology is much harder to grasp as a semantically
equivalent OWL DL representation. The most expressive sub-language, OWL
Full, combines OWL DL with all of RDF(S). As a result of non-standard and
second order features of RDF(S) (reification, no division between individuals and
classes, etc.) OWL Full is not decidable which restricts its practical use.
Furthermore, OWL Full bears conceptual problems like the possibility to redefine
language constructs of OWL itself.
        </p>
        <p>
          In conclusion, OWL virtually consists of only one language, OWL DL, since
Lite is nearly as complex as DL and Full is not attractive for semantical and
computational reasons. We suggest to restrict OWL Lite in a way that we believe
was originally intended by the language designers. In particular, we propose to
forbid general concept inclusions (GCIs) as well as multiple definitions for one
class identifier, as we have done in the context of our ontology authoring tool
OntoTrack [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Very likely those constructs will rarely occur in real world OWL
Lite ontologies. Instead, users will presumably use OWL DL when disjunction or
negation are needed for a certain application domain. In addition, we believe it
would make sense to have a set of more finely graded sublanguages ranging from
AL or ALC up to OWL DL, including at least two intermediate sublanguages.
First, this probably would make it easier for novice users to adopt OWL. Second,
the less expressive languages would benefit from a broader variety of reasoning
technology (e. g. from the Datalog/DB community). Third, this would allow us
to add non-standard language extensions (see below) to OWL, which typically
require to be combined with less expressive languages.
        </p>
        <p>
          Language Extensions. OWL is a declarative language tailored to represent
conceptual knowledge. Many applications, however, require the modeling of
actions, states, uncertainty, or an explicit notion of time. Besides the ongoing
efforts for an Semantic Web Rules Language (SWRL) we strongly suggest the
development of other extensions. For example, recent extensions of Description
Logics with fuzzy modifiers [
          <xref ref-type="bibr" rid="ref14 ref15">14,15</xref>
          ] should be taken into consideration for further
investigations. Other DL extensions concerning action formalisms [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] and time
[
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] are also candidates for optional OWL add-ons. Beyond that, OWL lacks an
official query language which is needed in order to have a common platform for
applications and reasoning systems.
        </p>
        <p>Representing Services. Our experience with MobiOWLS highlighted two
problems related to representing and reasoning with service descriptions. The
first problem is that it is very difficult to restrict the ontology within the
boundaries of OWL DL. For example, it is very difficult to describe a service that works
only in some contexts such as office buildings. The problem of such a description
is that it is within OWL Full, because the instance of a service refers to the
class of all office buildings. To work around this problem we adopted the same
solution adopted by OWL-S, which is to refer to URIs of the OWL classes and
instances that we want to use. As a consequence our ontology is still within the
boundaries of OWL-DL, at the expense of essentially giving up OWL reasoning
on our service descriptions. The second problem is that there is no
representation, and reasoning, for quantities and comparing quantities. For example, it is
impossible to define a broadband terminal as a terminal with bandwidth greater
than 1Mbps or any other quantity. In general, the lack of representation and
reasoning about quantities hampers the representations of important quality
of service features of services, greatly reducing the usefulness of OWL for the
representation of services.
3.2</p>
      </sec>
      <sec id="sec-9-7">
        <title>Reasoning</title>
        <p>
          Incremental Reasoning and Retraction. Our experience in developing
ontologies shows us that instant reasoning feedback is a key functionality for
ontology authoring tools. Therefore, we developed OntoTrack to effectively
support the user in creating and maintaining ontologies [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. It should not rely on
the user’s discipline to (re-)classify the ontology after some editing steps.
Moreover, understanding all classification consequences (such as taxonomy changes
and inconsistency) even after a few editing steps becomes a difficult task.
        </p>
        <p>
          Unfortunately, current OWL reasoners typically only provide some kind of
batch-oriented reasoning procedure. After loading an ontology and classification
one can pose TBox as well as ABox queries. But there is no possibility to
retract or change statements without reloading the updated ontology. A notable
exception here is RACER [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] which offers low-level retraction support for most
of its statements. However, because of the lack of algorithms for appropriatly
handling incremental additions as well as retractions [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], complete
reclassification is necessary after each change in the ontology. In addition, when using
an optimized tableaux-based reasoner for a language as expressive as OWL,
retracting and changing definitions may be of high complexity because of
optimization techniques such as absorption. However, incremental reasoning and
retraction is an important premise for almost all interactive OWL-based tools
or applications. An ad-hoc solution could consist of a heuristic that analyzes the
retraction statement and decides about local deletion of statements or complete
reclassification.
        </p>
        <p>
          Furthermore, technical aspects concerning standard interfaces and
communication are also an important issue for building interoperable applications.
Stateof-the-art reasoners should be network-aware, able to manage multiple clients,
and support standard interfaces such as DIG [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. We suggest to extend the
DIG interface for incremental reasoning and retraction. Even if reasoners do not
distinguish between some kind of on-the-fly retractions and reclassification,
providing such functionality in DIG will not only reduce the application’s burden
in an interactive environment such as ontology authoring, but also minimize
the amount of unnecessary data transfer. For instance, interactive applications
(resp. reasoner) which would like to perform retractions via a retraction-unaware
interface would have to re-submit the whole ontology after each retraction step
althought most of the explicit statements are unmodified and therefore typically
already available in the reasoner system as explicitly added statements.
Non-standard Inference Services. OWL is expected and explicitly intended
to be used by users without much formal background. Therefore, the ability to
support users to understand and debug ontologies is crucial for the Semantic
Web in general and identified as a major research challenge [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. Non-standard
reasoning services are of cource not directly related to the OWL specification.
However, they are important for users in order to design and maintain sound
and well-balanced ontologies. Therefore, we suggest to add some of them as an
optional extension to standard interfaces commonly used within OWL reasoning.
        </p>
        <p>
          Potential helpful non-standard services mainly cover explaining the
reasoning about and debugging of ontologies on both the conceptual (TBox) and the
instance (ABox) side. Explaining TBox queries like subsumption,
unsatisfiability, and equivalence for nearly all of OWL Lite can be found in [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. There is also
work on explaining ABox query answers [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] as well as why such a query failed
[
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]. Debugging of ontologies by identifying the core of incoherence also produced
some prototypical services [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ], [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]. There are additional non-standard reasoning
services suitable to support ontology authoring like matching of class patterns,
rewriting or approximation [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] as well as the least common subsumer (TBox)
or the most specific concept (ABox) [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]. Work on explaining non-subsumption
(why a subsumption does not hold) is still missing.
3.3
        </p>
      </sec>
      <sec id="sec-9-8">
        <title>Infrastructure</title>
        <p>
          Publish-Subscribe Standard Protocol. It is not only applications like
OntoTrack which are sensitive to incremental logical consequences. Almost all
reasoning intensive applications require an API offering a high-level
publishsubscribe mechanism. Otherwise such an application would be responsible for
querying the reasoner for all consequences it is interested in – or even worse the
application needs to compute or filter the desired consequences out of low-level
reasoner queries. For instance, to become aware of changes in the ontology’s
hierarchy an application has to check for direct superclasses for almost all classes
in the worst case. Then it has to compute the differences with respect to the
previous state. Using an external reasoner via a standard interface such as DIG [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]
will cause additional communication overhead, especially if the ratio between
ontology entities (or axioms) involved in the change(s) and queries needed to
perform is low. However, information about logical consequences are typically
already available on reasoner side after reclassification.
        </p>
        <p>We therefore propose a TBox publish-subscribe mechanism on the reasoner
side which roughly corresponds to a similar technique of RACER’s ABox
publishsubscribe mechanism. As not all applications will be interested in all ontology
changes (or even in none of them) and in order to minimize a possible notification
overhead, such a publish-subscribe is to be characterized as follows: (i) it should
be optional, (ii) specific w.r.t. the kind of ontology query, (iii) selective to the
set of ontology entities (subset or all), and (iv) granular on the interval it will
give its notification feedback. Adjusting the granularity may allow for defining
notification “points” in an incremental environment. For instance, an application
may only want to be informed about the consequences of a whole set of changes
– not about the consequences of each of the changes separately.</p>
        <p>In order to standardize such a publish-subscribe mechanism we suggest to
extend the specification of the common DIG interface in the following way. We
propose to divide the DIG interface into two parts: the core DIG and optional
extensions. It is desirable that the core will be extended to support an interface
for incremental reasoning and retraction of statements. The extensions should
cover a publish-subscribe mechanism as well as non-standard inference service
(see the previous subsection). The main idea behind a modularized DIG interface
is that all DIG-compliant reasoners support the core interface, but it depends
on the functionality of the reasoner which extension it will support – the more
the better.
4</p>
        <sec id="sec-9-8-1">
          <title>Conclusion and Suggestions</title>
          <p>The wide adoption and success of Semantic Web applications strongly depends
on a description language reflecting the character of distributed resources on
the Semantic Web, as well as on inference services and appropriate interfaces
to access them. Due to our experience in a broad spectrum of Semantic Web
applications ranging from an ontology tool to applications in mobile and
servicerelated environments, we have identified general problematic issues.</p>
          <p>We argue that for sharing and reusing ontologies the currently provided
ontology import, which brings all triples into the imported ontologies, is not sufficient.
Therefore, an appropriate mechanism on the syntactical as well as the semantic
level is necessary for importing ontologies and referencing entities in other
ontologies. Another important issue is the sublanguage ranking of OWL. We have
shown that OWL basically consists only of one language and therefore propose
a more finely graded sublanguage ranking. From a less expressive sublanguage
than OWL DL non-standard language extensions can also benefit which may be
otherwise un-decidable.</p>
          <p>In addition, in a number of applications we have encountered the limitations
of purely conceptual knowledge. We therefore suggest to also take into
consideration extensions such as action formalisms, time, and uncertainty. Technical
issues such as non-standard inference services and incremental reasoning are
also important, especially for interactive environments. We propose a
modularized extension to the common DIG interface not only to support incremental
reasoning and retraction of statements but also to plug-in additional extensions
for non-standard inference services as well as a publish-subscribe protocol for
the notification of logical changes within an ontology.</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Mrohs</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vaidya</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steglich</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kellerer</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arbanowski</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>OWL-SF - a distributed semantic service framework</article-title>
          .
          <source>In: Proc. of the Workshop on Context Awareness for Proactive Systems (CAPS'05)</source>
          , Helsinki (
          <year>2005</year>
          )
          <fpage>67</fpage>
          -
          <lpage>77</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mrohs</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vaidya</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>OWL-SF - distributed owl-based reasoning on objects in the real world</article-title>
          .
          <source>In: Proc. of ISWC'05 Demo Track</source>
          ,
          <string-name>
            <surname>Galway</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. MobiLife:
          <article-title>Project homepage</article-title>
          . http://www.ist-mobilife.
          <source>org</source>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>B</surname>
          </string-name>
          ¨ohm,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Wagner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Koolwaaij</surname>
          </string-name>
          , J.:
          <article-title>Enhanced presence tracking for mobile applications</article-title>
          .
          <source>In: Proc. of ISWC'05 Demo Track</source>
          ,
          <string-name>
            <surname>Galway</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. B¨ohm,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Luther</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Wagner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            :
            <surname>Smarter</surname>
          </string-name>
          groups
          <article-title>- reasoning on qualitative information from your desktop</article-title>
          .
          <source>In: Proc. of the 1st Workshop on The Semantic Desktop at ISWC'05</source>
          ,
          <string-name>
            <surname>Galway</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noppens</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>OntoTrack: A semantic approach for ontology authoring</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>3</volume>
          (
          <year>2005</year>
          ) in press.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noppens</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Balzer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kellerer</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Towards Semanticbased Service Discovery on Tiny Mobile Devices</article-title>
          .
          <source>In: Proc. of the Workshop on Semantic Web Technology for Mobile and Ubiquitous Applications</source>
          at ISWC'
          <volume>04</volume>
          ,
          <string-name>
            <surname>Hiroshima</surname>
          </string-name>
          (
          <year>2004</year>
          )
          <fpage>90</fpage>
          -
          <lpage>101</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noppens</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paolucci</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Semantic-based Service Discovery on mobile Devices</article-title>
          .
          <source>In: Proc. of ISWC'05 Demo Track</source>
          ,
          <string-name>
            <surname>Galway</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burstein</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hobbs</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McDermott</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McIlraith</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Narayanan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paolucci</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Payne</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srinivasan</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sycara</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>OWL-S: Semantic Markup for Web Services</article-title>
          . Member Submission,
          <source>W3C</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kalyanpur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Tool for Working with Web Ontologies</article-title>
          .
          <source>Journal of Semantic Web and Information Systems</source>
          <volume>1</volume>
          (
          <year>2005</year>
          )
          <fpage>36</fpage>
          -
          <lpage>49</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
          </string-name>
          , E.:
          <article-title>Working with Multiple Ontologies on the Semantic Web</article-title>
          .
          <source>In: Proc. of the 3rd Int. Semantic Web Conference (ISWC'04)</source>
          , Hiroshima, Springer (
          <year>2004</year>
          )
          <fpage>620</fpage>
          -
          <lpage>634</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Bechhofer</surname>
          </string-name>
          , S., van
          <string-name>
            <surname>Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>PatelSchneider</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stein</surname>
            ,
            <given-names>L.A.: OWL</given-names>
          </string-name>
          <string-name>
            <surname>Web Ontology Language Reference. W3C Recommendation</surname>
          </string-name>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>van Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <string-name>
            <surname>From</surname>
            <given-names>SHIQ</given-names>
          </string-name>
          and
          <article-title>RDF to OWL: The making of a web ontology language</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>1</volume>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Straccia</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Fuzzy ALC with Fuzzy Concrete Domains</article-title>
          .
          <source>In: Proc. of the Int. Workshop on Description Logics (DL'05)</source>
          , Edinburgh (
          <year>2005</year>
          )
          <fpage>96</fpage>
          -
          <lpage>103</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. H¨olldobler,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Nga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.H.</given-names>
            ,
            <surname>Khang</surname>
          </string-name>
          , T.D.:
          <article-title>The Fuzzy Description Logic ALCF LH</article-title>
          .
          <source>In: Proc. of the Int. Workshop on Description Logics (DL</source>
          <year>2005</year>
          ), Edinburgh (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lutz</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , Miliˇci´c,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Sattler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            ,
            <surname>Wolter</surname>
          </string-name>
          ,
          <string-name>
            <surname>F.</surname>
          </string-name>
          :
          <article-title>Integrating Description Logics and Action Formalisms: First Results</article-title>
          .
          <source>In: Proc. of the Int. Workshop on Description Logics (DL'05)</source>
          , Edinburgh (
          <year>2005</year>
          )
          <fpage>192</fpage>
          -
          <lpage>199</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Artale</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franconi</surname>
          </string-name>
          , E.:
          <article-title>A Survey of Temporal Extensions of Description Logics</article-title>
          .
          <source>Annals of Mathematics and Artificial Intelligence (AMAI) 30</source>
          (
          <year>2001</year>
          )
          <fpage>171</fpage>
          -
          <lpage>210</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Haarslev</surname>
            ,
            <given-names>V.,</given-names>
          </string-name>
          <article-title>M¨oller</article-title>
          , R.:
          <article-title>RACER System Description</article-title>
          .
          <source>In: Proc. of the Int. Joint Conference on Automated Reasoning (IJCAR</source>
          '
          <year>2001</year>
          ), Siena, Springer (
          <year>2001</year>
          )
          <fpage>701</fpage>
          -
          <lpage>705</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvanese</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
          </string-name>
          , P., eds.:
          <source>Description Logics Systems. In: The Description Logic Handbook</source>
          . Cambridge University Press (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>The DIG Description Logics Interface: DIG/1.1. Technical report</source>
          , University of Manchester (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Applications of Description Logics: State of the Art and Research Challenges</article-title>
          .
          <source>In: Proc. of the 13th Int. Conf. on Conceptual Structures (ICCS'05)</source>
          . (
          <year>2005</year>
          ) to appear.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Halfmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Explaining Subsumtion in ALEHF R+ TBoxes</article-title>
          .
          <source>In: Proc. of the Int. Workshop on Description Logics (DL'05)</source>
          , Edinburgh (
          <year>2005</year>
          )
          <fpage>144</fpage>
          -
          <lpage>151</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , da Silva, P.:
          <article-title>Explaining Answers from the Semantic Web: The Inference Web Approach</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>1</volume>
          (
          <year>2004</year>
          )
          <fpage>397</fpage>
          -
          <lpage>413</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Chalupsky</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Russ</surname>
          </string-name>
          , T.:
          <article-title>WhyNot: Debugging Failed Queries in Large Knowledge Bases</article-title>
          .
          <source>In: Proc. of the Innovative Applications of Artificial Intelligence Conf. (IAAI-02)</source>
          , Edmonton, AL,
          <string-name>
            <surname>Canada</surname>
          </string-name>
          (
          <year>2002</year>
          )
          <fpage>870</fpage>
          -
          <lpage>877</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalyanpur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Debugging owl ontologies</article-title>
          .
          <source>In: The 14th International World Wide Web Conference (WWW2005)</source>
          , Chiba, Japan (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rector</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drummond</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seidenberg</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Heuristic Approach to Explain the Inconsistency in OWL Ontologies</article-title>
          .
          <source>In: Proc. of the Int. Prot´eg´e Conference</source>
          , Madrid, Spain (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Brandt</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turhan</surname>
            ,
            <given-names>A.Y.</given-names>
          </string-name>
          :
          <article-title>An Approach for Optimized Approximation</article-title>
          .
          <source>In: Proc. of the Workshop on Applications of Description Logics (ADL'02)</source>
          . (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sertkaya</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turhan</surname>
            ,
            <given-names>A.Y.</given-names>
          </string-name>
          :
          <article-title>Computing the Least Common Subsumer w</article-title>
          .r.t. a
          <article-title>Background Terminology</article-title>
          .
          <source>In: Proc. of the 2004 Int. Workshop on Description Logics (DL</source>
          <year>2004</year>
          ), Whistler (
          <year>2004</year>
          )
          <fpage>11</fpage>
          -
          <lpage>20</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>