<!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>Visualizing and Editing Ontology Fragments with OWLGrEd</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Renars Liepins</string-name>
          <email>Renars.Liepins@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Karlis Cerans</string-name>
          <email>Karlis.Cerans@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arturs Sprogis</string-name>
          <email>Arturs.Sprogis@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Mathematics and Computer Science, University of</institution>
          <country country="LV">Latvia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Renars.Liepins</institution>
          ,
          <addr-line>Karlis.Cerans</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2012</year>
      </pub-date>
      <fpage>22</fpage>
      <lpage>25</lpage>
      <abstract>
        <p>The OWLGrEd ontology editor allows graphical visualization and authoring of OWL 2.0 ontologies using a compact yet intuitive presentation that combines UML class diagram notation with textual Manchester syntax for class expressions. Here we show, how to integrate OWLGrEd with ontology module mechanism from OWL API to obtain on-demand ontology fragment visualization that is essential for many existing large ontologies that do not fit in a single reasonably perceivable UML class diagram.</p>
      </abstract>
      <kwd-group>
        <kwd>OWL ontologies</kwd>
        <kwd>visualization</kwd>
        <kwd>UML/OWL profile</kwd>
        <kwd>OWLGrEd</kwd>
        <kwd>ontology decomposition</kwd>
        <kwd>ontology modules</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Intuitive ontology visualization is a key for their learning, exchange, as well as their
use in conceptual modeling and semantic database schema design. A number of tools
and approaches exist for rendering and/or editing OWL [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] ontologies in a graphical
form, including UML Profile for OWL DL [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], ODM [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], TopBraid Composer [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ],
Protégé [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] plug-in OWLViz [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and OWLGrEd [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ]. The approaches of [
        <xref ref-type="bibr" rid="ref2 ref3 ref7 ref8">2,3,7,8</xref>
        ]
use UML [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] class diagrams to visualize OWL ontologies. This is achieved by
visualizing an independent hierarchy of ontology classes and then structuring the data
and object property visualizations along the property domain and range classes. The
OWL ontology constructions not having direct UML counterparts (e.g. class
expressions, properties with more than one domain assertion, sub-property relations etc.) are
usually handled by some auxiliary means in the notation and the editor. OWLGrEd
uses textual OWL Manchester syntax [10] for class expressions where the graphical
notation is not available or is not desired thus allowing compact and comprehensible
presentation of up to medium-sized ontologies within a single diagram.
      </p>
      <p>The main focus of this demo is on using the compact UML-style notation, offered
by OWLGrEd, on large ontologies that do not fit within any reasonably-sized class
diagram, or whose rendering appears to be too complicated due to a kind of “spider
web” effect produced by many classes and relations. Its key idea consists in splitting
the ontology into meaningful fragments of conceivable size and then visualizing each
of the fragments in a separate diagram .</p>
      <p>OWLGrEd already has the means to partition ontology into sub-diagrams
(fragments) when authoring or reengineering an existing ontology. But there was no
way to automatically partition an ontology that is imported into OWLGrEd for
visualization. In this demo we will present an extension to OWLGrEd visualization
capabilities, that allows automatic partitioning of an ontology into logical fragments.
The addition is based on Automatic Decomposition [11] that was recently
implemented in the OWL API1. The decomposition is based on signatures, i.e. for
each fragment a user selects some entities that should be included in the fragment.
Then the fragment is extended with all the logically relevant axioms for these entities.
Finally all the fragments are rendered graphically in the OWLGrEd editor.</p>
      <p>The demonstration shows (i) working with OWLGrEd tool to render and author
OWL ontologies (ii) OWLGrEd extension to automatically partition ontology into
logical overlapping fragments based on fragment signatures.
2</p>
    </sec>
    <sec id="sec-2">
      <title>OWLGrEd Notation and Editor</title>
      <p>
        OWLGrEd1 provides a complete graphical notation for OWL 2 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], based on UML
class diagrams. We visualize OWL classes as UML classes, data properties as class
attributes, object properties as associations, individuals as objects and cardinality
restrictions on association domain class as UML cardinalities. It is easy to visualize
also subclass and inverse properties notations. For the full OWL 2 construct coverage
we enrich the UML class diagrams with the new extension notations, e.g. (cf. [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ]):
• fields in classes for equivalent class, superclass and disjoint class
expressions written in Manchester OWL syntax [10];
      </p>
      <p>• fields in associations and attributes for equivalent, disjoint and super
properties and fields for property characteristics, e.g., functional, transitive, etc.;
• anonymous classes containing equivalent class expression but no name (we
show graphically only anonymous classes that need to have graphic representation
in order to be able to describe other ontology concepts in the diagram);
• connectors (as lines) for visualizing binary disjoint, equivalent, etc. axioms;
• boxes with connectors for n-ary disjoint, equivalent, etc. axioms;
• connectors (lines) for visualizing object property restrictions some, only,
exactly, as well as cardinality restrictions.</p>
      <p>OWLGrEd provides option to specify class expressions in compact textual form
rather than using separate graphical element for each logical item within class
expression. If an expression is referenced in multiple places, it can optionally be
shown as an anonymous class. An anonymous class is also used as a base for property
domain/range specification, if this domain/range is not a named class.</p>
      <p>
        Figure 1 illustrates some basic OWLGrEd constructs on a simple mini-University
ontology, including different notation options for EquivalentClasses assertion, object
property restriction and a comment. The notation is explained in more detail in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
1 http://owlapi.sourceforge.net
2 http://owlgred.lumii.lv/
      </p>
      <sec id="sec-2-1">
        <title>Thing{owl}</title>
        <p>name:string{func}</p>
        <p>&lt;&lt;Comment&gt;&gt;
"All persons,
including teachers
and students"</p>
        <p>Professor
&lt;&lt;equivalent&gt;&gt;
AcademicStaff
=Teacher</p>
        <p>
          Person
"Al persons, including teachers
and students"
key = personID
personName:string{&lt;name}
personID:string[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]
&lt;&lt;disjoint&gt;&gt;
{disjoint}
        </p>
        <p>AcademicProgram
programName:string{&lt;name} belongsTo
enrolled {&gt;takes o
belongsTo}
includes
relates coursCeNoaumrsee:string
{&lt;name}</p>
      </sec>
      <sec id="sec-2-2">
        <title>Student</title>
        <p>isTakenBy takes {&lt;relates} 1..10</p>
      </sec>
      <sec id="sec-2-3">
        <title>Teacher</title>
        <p>isTaughtBy
teaches {&lt;relates} {&lt;&gt;takes}</p>
      </sec>
      <sec id="sec-2-4">
        <title>PermanentTeaching Staff</title>
        <p>&lt;teaches some MandatoryCourse
teaches some [1..*] MandatoryCourse</p>
        <p>
          The OWGrEd editor offers ontology interoperability (import/export) functionality
with the Protégé 4.2 ontology editor [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. The principal OWLGrEd usage ways are:
- ontology authoring (create and edit an ontology in OWLGrEd, then export it to
        </p>
        <p>Protégé to analyze and possibly submit it to other ontology processing tools)
- ontology visualization (an ontology that is imported from Protégé is displayed
graphically to obtain a comprehensible visual view on it).
3 Visualizing Fragments of Ontology
The graphical form is ideal for understanding small ontologies, but for large
ontologies it fast becomes overwhelming because of too many line crossings. For
visualization of the ontology in the form of fragments an issue is to describe the
fragments to be visualized since manual enumeration of all axioms to be included into
a fragment would clearly be infeasible. Recently there has been work on
signaturebased automatic decomposition [11] of ontologies that allows specify ontology
modules just in terms of their “core” terms/entities. The decomposition then finds all
the axioms that are logically relevant for the given entities.</p>
        <p>We have extended OWLGrEd editor with the Automatic Decomposition feature. A
user can specify either a single ontology fragment, or a list of fragments covering the
whole ontology that is to be visualized. The automatic decomposition then finds all
the relevant axioms for each specified fragment thus allowing OWLGrEd showing the
fragments visually in a graphical form.</p>
        <p>As an example consider the schema.org ontology. It consists of about 300 classes,
110 object properties, 70 data properties and 310 subclass assertions. The ontology is
clearly too large to be easily perceived as a single diagram. However, it would be
feasible as well as meaningful to visualize fragments of the. For example, in the
Figure 2 is shown a fragment that is centered on entities “Event”, “Product” and
“Person”. Once the user has specified such an entity list, the tool automatically finds
the relevant axioms for these entities and then shows this fragment graphically. It is
possible to specify any number of such fragment signatures at a time and the tool will
create visualization for each of them.</p>
        <p>The experiments we have performed allows us to judge that the offered approach
of combining of the traditional OWLGrEd ontology visualization means with
ontology decomposition techniques would be a useful tool for the semantic
technology community in ontology schema structure representation.</p>
        <p>Thing{owl}</p>
        <p>model Product
itemOfered productID
brand
manufacturer
performers
at endees
homeLocation
alumniOf
workLocation
worksFor
af iliation
nationality
memberOf</p>
        <p>subEvents
superEvent endDateEvent</p>
        <p>startDate
events
founders
editor
actors
musicGroupMember
il ustrator
producer
alumni
employees
director</p>
        <p>EducationEvent
BusinessEvent
SportsEvent
SocialEvent
VisualArtsEvent
TheaterEvent
DanceEvent</p>
        <p>Festival
UserInteraction
LiteraryEvent
ChildrensEvent
MusicEvent
ComedyEvent
Fig. 2. Automatically extracted fragment of schema.org ontology based on a
signature “Event, Product, Person”.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Motik</surname>
            ,
            <given-names>B</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Patel-Schneider P.F; Parsia</surname>
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>OWL 2 Web Ontology Language Structural Specification</article-title>
          and
          <string-name>
            <surname>Functional-Style Syntax</surname>
          </string-name>
          ,
          <year>2009</year>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Brockmans</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Volz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eberhart</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Löffler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>Visual Modeling of OWL DL Ontologies Using UML</article-title>
          ,
          <source>Proc. of ISWC</source>
          <year>2004</year>
          , LNCS 3298, pp.
          <fpage>198</fpage>
          -
          <lpage>213</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>ODM</given-names>
            <surname>UML profile for</surname>
          </string-name>
          <string-name>
            <surname>OWL</surname>
          </string-name>
          , http://www.omg.org/spec/ODM/1.0/PDF/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>TopBraid</given-names>
            <surname>Composer</surname>
          </string-name>
          , http://www.topquadrant.com/products/TB_Composer.html.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>5. Protégé 4, http://protege.stanford.edu/</mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>OWL</given-names>
            <surname>Viz</surname>
          </string-name>
          , http://www.co-ode.org/downloads/owlviz/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Barzdins</surname>
            , J.; Barzdins,
            <given-names>G.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Cerans</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Liepins</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Sprogis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>OWLGrEd: a UML Style Graphical Notation and Editor for OWL 2</article-title>
          .
          <source>In Proc. of OWLED</source>
          <year>2010</year>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Barzdins</surname>
          </string-name>
          , J.;
          <string-name>
            <surname>Cerans</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Liepins</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Sprogis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>UML Style Graphical Notation and Editor for OWL 2</article-title>
          .
          <source>In Proc. of BIR'</source>
          <year>2010</year>
          , LNBIP, Springer
          <year>2010</year>
          , vol.
          <volume>64</volume>
          , p.
          <fpage>102</fpage>
          -
          <lpage>113</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Unified</given-names>
            <surname>Modeling</surname>
          </string-name>
          <article-title>Language: Infrastructure, version 2.1</article-title>
          . OMG Specification ptc/
          <fpage>06</fpage>
          -04-03, http://www.omg.org/docs/ptc/06-04-03.pdf 10.
          <article-title>OWL 2 Manchester Syntax</article-title>
          , http://www.w3.org/TR/owl2-manchester-syntax/ 11.Klinov,
          <string-name>
            <given-names>P.</given-names>
            ;
            <surname>Vescovo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ;
            <surname>Schneider</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.</surname>
          </string-name>
          :
          <article-title>Incrementally Updateable and Persistent Decomposition of OWL Ontologies</article-title>
          .
          <source>In Proc of OWLED</source>
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>