<!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>Extending OWL Ontology Visualizations with Interactive Contextual Verbalization</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Uldis Boj¯ars</string-name>
          <email>uldis.bojars@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ren¯ars Liepin¸ˇs</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Normunds Gru¯z¯ıtis</string-name>
          <email>normunds.gruzitis@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>K¯arlis Cˇ er¯ans</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Edgars Celms</string-name>
          <email>edgars.celms@lumii.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Computing, University of Latvia Raina bulvaris 19</institution>
          ,
          <addr-line>Riga, LV-1459</addr-line>
          ,
          <country country="LV">Latvia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institute of Mathematics and Computer Science, University of Latvia Raina bulvaris 29</institution>
          ,
          <addr-line>Riga, LV-1459</addr-line>
          ,
          <country country="LV">Latvia</country>
        </aff>
      </contrib-group>
      <fpage>5</fpage>
      <lpage>16</lpage>
      <abstract>
        <p>To participate in Semantic Web projects, domain experts need to be able to understand the ontologies involved. Visual notations can provide an overview of the ontology and help users to understand the connections among entities. However, users first need to learn the visual notation before they can interpret it correctly. Controlled natural language representation would be readable right away and might be preferred in case of complex axioms, however, the structure of the ontology would remain less apparent. We propose to combine ontology visualizations with contextual ontology verbalizations of selected ontology (diagram) elements, interactively displaying controlled natural language (CNL) explanations of OWL axioms corresponding to the selected visual notation elements. Thus, the domain experts will benefit from both the high-level overview provided by the graphical notation and the detailed textual explanations of particular elements in the diagram.</p>
      </abstract>
      <kwd-group>
        <kwd>OWL</kwd>
        <kwd>Ontology visualization</kwd>
        <kwd>Contextual verbalization</kwd>
        <kwd>Controlled natural language</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Semantic Web technologies have been successfully applied in pilot projects and
are transitioning toward mainstream adoption in the industry. In order for this
transition to go successfully, there are still hurdles that have to be overcome.
One of them are the difficulties that domain experts have in understanding
mathematical formalisms and notations that are used in ontology engineering.</p>
      <p>
        Visual notations have been proposed as a way to help domain experts to work
with ontologies. Indeed, when domain experts collaborate with ontology experts
in designing an ontology “they very quickly move to sketching 2D images to
communicate their thoughts” [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The use of diagrams has also been supported
by an empirical study done by Warren et al. where they reported that “one-third
[of participants] commented on the value of drawing a diagram” to understand
what is going on in the ontology [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>
        Despite the apparent success of the graphical approaches, there is still a
fundamental problem with them. When a novice user wants to understand a
particular ontology, he or she cannot just look at the diagram and know what it
means. The user first needs to learn the syntax and semantics of the notation –
its mapping to the underlying formalism. This limitation has long been noticed
in software engineering [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] and, for this reason, formal models in software
engineering are often translated into informal textual documentation by systems
analysts, so that they can be validated by domain experts [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        A similar idea of automatic conversion of ontologies into seemingly informal
controlled natural language (CNL) texts and presenting the texts to domain
experts has been investigated by multiple groups [
        <xref ref-type="bibr" rid="ref14 ref20 ref9">14,20,9</xref>
        ]. CNL is more
understandable to domain experts and end-users than the alternative representations
because the notation itself does not have to be learned, or the learning time is
very short. Hoverer, the comparative studies of textual and graphical notations
have shown that while domain experts that are new to graphical notations better
understand the natural language text, they still prefer the graphical notations in
the long run [
        <xref ref-type="bibr" rid="ref13 ref17">13,17</xref>
        ]. It leads to a dilemma of how to introduce domain experts to
ontologies. The CNL representation shall be readable right away and might be
preferred in case of complex axioms (restrictions) while the graphical notation
makes the overall structure and the connections more comprehensible.
      </p>
      <p>We present an approach that combines the benefits of both graphical
notations and CNL verbalizations. The solution is to extend the graphical notation
with interactive contextual verbalizations of the axioms that are represented by
the selected graphical element. The graphical representation gives the users an
overview of the ontology while the contextual verbalizations can explain what
the particular graphical element means. Thus, domain experts that are novices
in ontology engineering shall be able to learn and use the graphical notation
rapidly and independently without special training.</p>
      <p>
        Throughout this paper we refer to the OWLGrEd visual notation and
ontology editing and visualization tools that are using it. The OWLGrEd notation [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
is a compact and complete UML-style notation for OWL 2 ontologies. It relies
on Manchester OWL Syntax [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] for certain class expressions. This notation is
implemented in the OWLGrEd ontology editor3 and its online ontology
visualization tool4 [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. The approach proposed in this article is demonstrated on an
experimental instance of the OWLGrEd visualization tool.
      </p>
      <p>In Section 2, we present the general principles of extending graphical
ontology notations with contextual natural language verbalizations. In Section 3, we
demonstrate how the proposed approach may be used in practice by extending
ontology visualizations in the OWLGrEd notation with interactive contextual
verbalizations in controlled English. In Section 4, we discuss the benefits and
limitations of our approach. Section 5 discusses related work while Section 6
summarizes the article.</p>
    </sec>
    <sec id="sec-2">
      <title>3 http://owlgred.lumii.lv</title>
    </sec>
    <sec id="sec-3">
      <title>4 http://owlgred.lumii.lv/online_visualization/</title>
      <p>2</p>
      <sec id="sec-3-1">
        <title>Extending Graphical Notations with Contextual</title>
      </sec>
      <sec id="sec-3-2">
        <title>Verbalizations</title>
        <p>This section describes the proposed approach for contextual verbalization of
graphical elements in ontology diagrams, starting with a motivating example. We
are focusing particularly on OWL ontologies, assuming that they have already
been created and that the ontology symbols (names) are lexically motivated and
consistent, i.e., in this paper we do not consider the authoring of ontologies,
although the contextual verbalizations might be helpful in the authoring process
as well and it would provide a motivation to follow a lexical and consistent
naming convention.
2.1</p>
        <sec id="sec-3-2-1">
          <title>Motivating Example</title>
          <p>
            In most diagrammatic OWL ontology notations, object property declarations
are shown either as boxes (e.g. in VOWL [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ]) or as labeled links connecting the
property domain and range classes (e.g. in OWLGrEd [
            <xref ref-type="bibr" rid="ref1">1</xref>
            ] or Graffoo [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]).
Figure 1 illustrates a simplified ontology fragment that includes classes Person and
Thing, an object property likes and a data property hasAge. This fragment is
represented by using three alternative formal notations: Manchester OWL
Syntax [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ], VOWL and OWLGrEd. As can be seen, the visualizations are tiny and
may already seem self-explanatory. Nevertheless, even in this simple case, the
notation for domain experts may be far from obvious. For example, the
Manchester OWL Syntax uses the terms domain and range when defining a property,
and these terms may not be familiar to a domain expert. In the graphical
notations, the situation is even worse because the user may not even suspect that the
edges represent more than one assertion and that the assertions are far-reaching.
In the case of likes in Figure 1, it means that everyone that likes something is
necessarily a person.
          </p>
          <p>We have encountered such problems in practice when introducing ontologies
visualized using the OWLGrEd notation to users familiar with the UML
notation. Initially, the users were misunderstanding the meaning of the association
edges. For example, they would interpret that the edge likes in Figure 1 means
“persons may like persons”, which is true, however, they would also assume that
other disjoint classes could have this property, which is false in OWL because
multiple domain/range axioms of the same property are combined to form an
intersection. Thus, even having a very simple ontology, there is a potential for
misunderstanding the meaning of both the formal textual notation (e.g.,
Manchester OWL Syntax) and the graphical notations.
2.2</p>
        </sec>
        <sec id="sec-3-2-2">
          <title>Proposed Approach</title>
          <p>We propose to extend graphical ontology diagrams with contextual on-demand
verbalizations of OWL axioms related to the selected diagram elements, with
the goal to help users to better understand their ontologies and to learn the
graphical notations based on their own and/or real-world examples.
WOLGrEd
oNtain
oNtain</p>
          <p>Clas: Person</p>
          <p>likes
Domain: Person
Range: xsd:integer
vEery person si a thing.
vEerything hta
vEerything hta
ilkes something si a person.
si liked</p>
          <p>yb something si
vEerything hta ahs an age is a person.
vEerything hta si an age of something si an integr.</p>
          <p>a person.
ahsAge</p>
          <p>aLngue</p>
          <p>The contextual verbalization of ontology diagrams relies on the assumption
that every diagram element represents a set of ontology axioms, i.e., the ontology
axioms are generally presented locally in the diagram, although possibly a single
ontology axiom can be related to several elements of the diagram.</p>
          <p>The same verbalization can be applied to all the different OWL visual
notations, i.e., we do not have to design a new verbalization (explanation) grammar
for each new visual notation, because they all are mapped to the same underlying
OWL axioms. Thus, the OWL visualizers can reuse the same OWL verbalizers
to provide contextual explanations of any graphical OWL notation.</p>
          <p>By reusing ontology verbalizers, existing ontology visualization systems can
be easily extended with a verbalization service. Figure 2 illustrates how the
proposed approach might work in practice:
1. Visualizer is the existing visualization component that transforms an OWL
ontology into its graphical representation.
2. The system is extended by a User Selection mechanism that allows users to
select the graphical element that they want to verbalize.
3. Collector gathers a subset of the ontology axioms that correspond to the
selected graphical element.</p>
          <p>– a textual explanation that is shown to the user.
4. The relevant axioms are passed to Verbalizer that produces CNL statements</p>
          <p>The actual implementation would depend on the components used and on
how the output of the verbalization component can be integrated into the
resulting visualization.</p>
          <p>With the proposed approach, when domain experts encounter the example
ontology in Figure 1, they would not have to guess what the elements of this
graphical notation mean. Instead, they can just ask the system to explain the
notation using the ontology that they are exploring. When the user clicks on
the edge likes in Figure 1 (in either visual notation), the system would show
User Selicton</p>
          <p>LWO yglotnO
vEery C is a B
erbalizotnV of</p>
          <p>User Selicton
the verbalization that unambiguously explains the complete meaning of this
graphical element:</p>
          <p>Everything that likes something is a person. Everything that is liked by
something is a person.</p>
          <p>By applying the proposed approach and by using natural language to
interactively explain what the graphical notation means, developers of graphical OWL
editors and viewers can enable users (domain experts in particular) to avoid
misinterpretations of ontology elements and their underlying axioms, resulting
in a better understanding of both the ontology and the notation.</p>
          <p>The verbalization can help users even in relatively simple cases, such as
object property declarations where user’s intuitive understanding of the domain
and range of the property might not match what is asserted in the ontology. The
verbalization of OWL axioms makes this information explicit while not requiring
users to be ontology experts. The value of contextual ontology verbalization is
even more apparent for elements whose semantics might be somewhat tricky
even for more experienced users (e.g., some, only and cardinality constraints
on properties, or OWLGrEd generalization forks with disjoint and complete
constraints).</p>
          <p>
            The verbalization of ontology axioms has been shown to be helpful in
teaching OWL to newcomers both in practical experience reports [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ] as well as in
statistical evaluations [
            <xref ref-type="bibr" rid="ref9">9</xref>
            ] and thus it would be a valuable addition to ontology
visualizations.
3
          </p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>Proof of Concept: Interactive Verbalizations in</title>
      </sec>
      <sec id="sec-3-4">
        <title>OWLGrEd Visualizations</title>
        <p>
          We illustrate the approach by extending OWLGrEd ontology visualizations
(i.e. visualizations in the OWLGrEd notation used by the OWLGrEd
ontology editor and its online ontology visualization tool) with on-demand
contextual verbalizations of the underlying OWL axioms using Attempto Controlled
English (ACE) [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>The interactive ontology verbalization layer allows users to inspect a
particular element of the presented ontology diagram and to receive a verbal explanation
of the ontology axioms that are related to this ontology element. By clicking a
mouse pointer on an element, a pop-up widget is displayed, containing a CNL
verbalization of the corresponding axioms in Attempto Controlled English. By
default, the OWLGrEd visualizer minimizes the number of verbalization
widgets shown simultaneously by hiding them after a certain timeout. For users to
simultaneously see the verbalizations for multiple graphical elements, there is an
option to “freeze” the widgets and prevent them from disappearing.
A demonstration of our approach, based on an example mini-university ontology,
is available online5. Figure 3 shows a screenshot of the OWLGrEd visualization
of this ontology containing a number of verbalizations.</p>
        <p>These verbalizations describe the ontology elements that represent the class
Course, the object property teaches, the individual Alice and the restriction on
the class MandatoryCourse. Verbalizations are implicitly linked to the
corresponding elements using the element labels. While it might be less convenient
to identify the implicit links in a static image, the interactive nature of the
combined ontology visualization and verbalization tool makes it easier for users to
keep track of relations between diagram elements and their verbalizations.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>5 http://owlgred.lumii.lv/cnl-demo</title>
      <p>To illustrate the verbalization functionality, let us look at the object property
teaches, represented in the diagram by an edge connecting the class Teacher to
the class Course (Figure 4). It leads to the following ACE verbalization:
(V1)
(V2)
(V3)</p>
      <p>Every teacher teaches at most 2 courses.</p>
      <p>Everything that is taught by something is a course.</p>
      <p>Everything that teaches something is a teacher.
(V4) If X takes Y then it is false that X teaches Y.</p>
      <p>Note that the specific OWL terms, like disjoint, subclass and inverse, are not
used in the ACE statements. The same meaning is expressed implicitly – via
paraphrasing – using more general common sense constructions and terms.</p>
      <p>In this case, the edge represents not only the domain and range axioms of
the property (verbalized stentences V2, V3) but also the cardinality of its range
(V1) and the restriction that teaches is disjoint with takes (expressed by the
if-then statement in V4).</p>
      <p>
        Further information about combining interactive contextual CNL
verbalization with OWLGrEd ontology visualizations is available at [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
4
      </p>
      <sec id="sec-4-1">
        <title>Discussion</title>
        <p>This section discusses the use of contextual ontology verbalization, focusing on
its applicability to various graphical notations, multilinguality and the potential
limitations of the approach.
4.1</p>
        <sec id="sec-4-1-1">
          <title>Applicability to Different Visual Notations</title>
          <p>The proposed approach is applicable to any ontology visualization where
graphical elements represent one or more OWL axioms. The value of using
verbalization functionality is higher for more complex notations (e.g., OWLGrEd) where
graphical elements may represent multiple axioms but even in simple graphical
notations, where each graphical element corresponds to one axiom, users will
need to know how to read the notation. Contextual ontology verbalization
addresses this need by providing textual explanations of diagram elements and the
underlying OWL axioms.</p>
          <p>
            A more challenging case is notations where some OWL axioms are
represented as spatial relations between the elements and are not directly represented
by any graphical elements (e.g., Concept Diagrams represent subclass-of
relations as shapes that are included in one another [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ]). In order to represent
these axioms in ontology verbalization they need to be “attached” to one or
more graphical elements that these axioms refer to. As a result, they will be
included in verbalizations of relevant graphical elements. In the case of
Concept Diagrams, the subclass-of relation, which is represented by shape inclusion,
would be verbalized as part of the subclass shape.
4.2
          </p>
        </sec>
        <sec id="sec-4-1-2">
          <title>Lexical Information and Multilinguality</title>
          <p>In order to generate lexically and grammatically well-formed sentences,
additional lexical information may need to be provided, e.g., that the property
teaches is verbalized using the past participle form “taught” in the passive voice
(inverse-of ) constructions or that the class MandatoryCourse is verbalized as a
multi-word unit “mandatory course”.</p>
          <p>In terms of multilinguality, contextual verbalizations can be generated for
multiple languages, assuming that the translation equivalents are available for
the lexical labels of ontology symbols. This would allow domain experts to
explore ontologies in their native language and avoid information getting lost in
translation.</p>
          <p>
            An appropriate and convenient means for implementing a multilingual OWL
verbalization grammar is Grammatical Framework (GF) [
            <xref ref-type="bibr" rid="ref15">15</xref>
            ] which provides
a reusable resource grammar library for about 30 languages, facilitating rapid
implementation of multilingual CNLs6. Moreover, an ACE grammar library
based on the GF resource grammar library is already available for about 10
languages [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ]. This allows for using English-based entity names and the OWL
subset of ACE as an interlingua, following the two-level OWL-to-CNL approach
suggested in [
            <xref ref-type="bibr" rid="ref6">6</xref>
            ].
          </p>
          <p>We have used this GF-based approach in order to provide an experimental
support for lexicalization and verbalization in OWLGrEd tools for both English
and Latvian, a highly inflected Baltic language.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>6 http://www.grammaticalframework.org/</title>
      <p>4.3</p>
      <sec id="sec-5-1">
        <title>Limitations</title>
        <p>Verbalization techniques that are a part of the proposed approach have the same
limitations as ontology verbalization in general. In particular, verbalization may
require additional lexical information to generate grammatically well-formed
sentences. To some degree, by employing good ontology design practices and naming
conventions as well as by annotating ontology entities with lexical labels, this
limitation can be overcome. Another issue is specific kinds of axioms that are
difficult or verbose to express in natural language without using terms of the
underlying formalism.
5</p>
        <sec id="sec-5-1-1">
          <title>Related Work</title>
          <p>
            To the best of our knowledge, there are no publications proposing combining
OWL ontology visualizations with contextual CNL verbalizations but there has
been a movement towards cooperation between both fields. In ontology
visualizations, notations have been adding explicit labels to each graphical element
that describes what kind of axiom it represents. For example, in VOWL a line
representing a subclass-of relation is explicitly labeled with the text “Subclass
of”. This practice makes the notation more understandable to users as reported
in the VOWL user study where a user stated that “there was no need to use
the printed [notation reference] table as the VOWL visualization was very
selfexplanatory” [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ]. However, such labeling of graphical elements is only useful
in notations where each graphical element represents one axiom. In more
complex visualizations where one graphical element represents multiple axioms there
would be no place for all the labels corresponding to these axioms. For example,
in the OWLGrEd notation, class boxes can represent not just class definitions
but also subclass-of and disjoint classes assertions. In such cases, verbalizations
provide understandable explanations. Moreover, in some notations (e.g.,
Concept Diagrams [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ]) there might be no graphical elements at all for certain kinds
of axioms, as it was mentioned in Section 4.1.
          </p>
          <p>
            In the field of textual ontology verbalizations there has been some exploration
of how to make verbalizations more convenient for users. One approach that
has been tried is grouping verbalizations by entities. It produces a kind of a
dictionary, where records are entities (class, property, individual), and every
record contains verbalizations of axioms that refer to this entity. The resulting
document is significantly larger than a plain, non-grouped verbalization because
many axioms may refer to multiple entities and thus will be repeated in each
entity. Nevertheless, the grouped presentation was preferred by users [
            <xref ref-type="bibr" rid="ref22">22</xref>
            ]. Our
approach can be considered a generalization of this approach, where a dictionary
is replaced by an ontology visualization that serves as a map of the ontology.
          </p>
          <p>An ad-hoc combination of verbalization and visualization approaches could
be achieved using existing ontology tools such as Prot´eg´e by using separate
visualization and verbalization plugins (e.g., Prot´eg´eVOWL7 for visualization and</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>7 http://vowl.visualdataweb.org/protegevowl.html</title>
      <p>ACEView8 for verbalization). However, this would not help in understanding
the graphical notation because the two views are independent, and thus a user
cannot know which verbalizations correspond to which graphical elements. Our
approach employs closer integration of the two ontology representations and
provides contextual verbalization of axioms that directly correspond to the selected
graphical element, helping users in understanding the ontology and learning the
graphical notation used. The usefulness of combining ontology visualization and
verbalization is also demonstrated by a course for ontology engineering that uses
a CNL-based Fluent Editor and employs OWLGrEd visualizations for
illustrating the meaning of CNL assertions9.
6</p>
      <sec id="sec-6-1">
        <title>Conclusions</title>
        <p>Mathematical formalisms used in ontology engineering are hard to understand
for domain experts. Usually, graphical notations are suggested as a solution
to this problem. However, the graphical notations, while preferred by domain
experts, still have to be learned to be genuinely helpful in understanding. Until
now the only way to learn these notations was by reading the documentation.</p>
        <p>In this article, we propose to combine ontology visualizations and CNL
verbalizations in order to solve the learning problem. Using this approach the
domain expert can interactively select a graphical element and receive the
explanation of what the element means. The explanation is generated by passing the
corresponding axioms of the element through one of the existing verbalization
services. The service returns natural language sentences explaining the OWL
axioms that correspond to the selected element and thus explaining what it
means.</p>
        <p>CNL explanations can help domain experts to rapidly and independently
learn and use the graphical notation from the beginning, without extensive
training, thus making it easier for domain experts to participate in ontology
engineering thus solving one of the problems that hinder the adoption of Semantic Web
technologies in the mainstream industry.</p>
        <p>Acknowledgments. This work has been supported by the Latvian State
Research program NexIT project No.1 “Technologies of ontologies, semantic web
and security”, the ESF project 2013/0005/1DP/1.1.1.2.0/13/APIA/VIAA/049,
and the University of Latvia Faculty of Computing project “Innovative
information technologies”.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>8 http://attempto.ifi.uzh.ch/aceview/</title>
    </sec>
    <sec id="sec-8">
      <title>9 http://www.slideshare.net/Cognitum/introduction-to-ontology</title>
      <p>engineering-with-fluent-editor-2014/19</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Ba¯rzdin¸ˇs,
          <string-name>
            <surname>J.</surname>
          </string-name>
          , Ba¯rzdin¸ˇs,
          <string-name>
            <surname>G.</surname>
          </string-name>
          , Cˇera¯ns,
          <string-name>
            <surname>K.</surname>
          </string-name>
          , Liepin¸ˇs,
          <string-name>
            <surname>R.</surname>
          </string-name>
          , Spro`gis, A.:
          <article-title>UML-style graphical notation and editor for OWL 2</article-title>
          . In: Perspectives in Business Informatics Research, pp.
          <fpage>102</fpage>
          -
          <lpage>114</lpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Camilleri</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fuchs</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaljurand</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>ACE grammar library</article-title>
          .
          <source>Tech. Rep. Project Deliverable D11.1</source>
          , MOLTO project (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Falco</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peroni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vitali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Modelling OWL ontologies with Graffoo</article-title>
          . In: The Semantic Web:
          <article-title>ESWC 2014 Satellite Events: ESWC 2014 Satellite Events</article-title>
          , Anissaras, Crete, Greece, May
          <volume>25</volume>
          -29,
          <year>2014</year>
          , Revised Selected Papers. pp.
          <fpage>320</fpage>
          -
          <lpage>325</lpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Frederiks</surname>
          </string-name>
          , P.J.,
          <string-name>
            <surname>Van der Weide</surname>
          </string-name>
          , T.P.:
          <article-title>Information modeling: The process and the required competencies of its participants</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          <volume>58</volume>
          (
          <issue>1</issue>
          ),
          <fpage>4</fpage>
          -
          <lpage>20</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Fuchs</surname>
            ,
            <given-names>N.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaljurand</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Attempto Controlled English for knowledge representation</article-title>
          .
          <source>In: Reasoning Web</source>
          , pp.
          <fpage>104</fpage>
          -
          <lpage>124</lpage>
          . Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Gruzitis</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barzdins</surname>
          </string-name>
          , G.:
          <article-title>Towards a more natural multilingual controlled language interface to OWL</article-title>
          .
          <source>In: Proceedings of the 9th International Conference on Computational Semantics</source>
          . pp.
          <fpage>1006</fpage>
          -
          <lpage>1013</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          :
          <article-title>OWL 2 Web Ontology Language Manchester Syntax</article-title>
          . W3C Working Group Note (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Howse</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stapleton</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taylor</surname>
          </string-name>
          , K.,
          <string-name>
            <surname>Chapman</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Visualizing ontologies: A case study</article-title>
          .
          <source>In: The Semantic Web - ISWC</source>
          <year>2011</year>
          , pp.
          <fpage>257</fpage>
          -
          <lpage>272</lpage>
          . Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The understandability of OWL statements in controlled English</article-title>
          .
          <source>Semantic Web</source>
          <volume>4</volume>
          (
          <issue>1</issue>
          ),
          <fpage>101</fpage>
          -
          <lpage>115</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. Liepin¸ˇs,
          <string-name>
            <surname>R.</surname>
          </string-name>
          , Boja¯rs,
          <string-name>
            <surname>U.</surname>
          </string-name>
          , Gru¯z¯ıtis, N., Cˇera¯ns,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Celms</surname>
          </string-name>
          , E.:
          <article-title>Towards selfexplanatory ontology visualization with contextual verbalization</article-title>
          .
          <source>In: Databases and Information Systems: 12th International Baltic Conference, DB&amp;IS</source>
          <year>2016</year>
          , Riga, Latvia,
          <source>July 4-6</source>
          ,
          <year>2016</year>
          , Proceedings. pp.
          <fpage>3</fpage>
          -
          <lpage>17</lpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Liepins</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grasmanis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bojars</surname>
          </string-name>
          , U.:
          <article-title>OWLGrEd ontology visualizer</article-title>
          .
          <source>In: ISWC Developers Workshop 2014</source>
          . CEUR (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Negru</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haag</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ertl</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>VOWL 2: User-oriented visualization of ontologies</article-title>
          .
          <source>In: Knowledge Engineering and Knowledge Management</source>
          , pp.
          <fpage>266</fpage>
          -
          <lpage>281</lpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Ottensooser</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fekete</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Menictas</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Making sense of business process descriptions: An experimental comparison of graphical and textual notations</article-title>
          .
          <source>Journal of Systems and Software</source>
          <volume>85</volume>
          (
          <issue>3</issue>
          ),
          <fpage>596</fpage>
          -
          <lpage>606</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Power</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Expressing OWL axioms by English sentences: dubious in theory, feasible in practice</article-title>
          .
          <source>In: Proceedings of the 23rd International Conference on Computational Linguistics: Posters</source>
          . pp.
          <fpage>1006</fpage>
          -
          <lpage>1013</lpage>
          . Association for Computational Linguistics (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Ranta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Grammatical Framework, a type-theoretical grammar formalism</article-title>
          .
          <source>Journal of Functional Programming</source>
          <volume>14</volume>
          (
          <issue>2</issue>
          ),
          <fpage>145</fpage>
          -
          <lpage>189</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <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>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rogers</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knublauch</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevens</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wroe</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>OWL pizzas: Practical experience of teaching OWL-DL: Common errors &amp; common patterns</article-title>
          . In:
          <article-title>Engineering Knowledge in the Age of the Semantic Web</article-title>
          , pp.
          <fpage>63</fpage>
          -
          <lpage>81</lpage>
          . Springer (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Sharafi</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchetto</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antoniol</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , Gu´eh´eneuc,
          <string-name>
            <surname>Y.G.</surname>
          </string-name>
          :
          <article-title>An empirical study on the efficiency of graphical vs. textual representations in requirements comprehension</article-title>
          .
          <source>In: 21st International Conference on Program Comprehension</source>
          . pp.
          <fpage>33</fpage>
          -
          <lpage>42</lpage>
          . IEEE (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Siau</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Informational and computational equivalence in comparing information modeling methods</article-title>
          .
          <source>Journal of Database Management</source>
          <volume>15</volume>
          (
          <issue>1</issue>
          ),
          <fpage>73</fpage>
          -
          <lpage>86</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Stapleton</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Howse</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonnington</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burton</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A vision for diagrammatic ontology engineering</article-title>
          . In:
          <article-title>Visualizations and User Interfaces for Knowledge Engineering and Linked Data Analytics</article-title>
          .
          <source>CEUR</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Stevens</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malone</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Williams</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Power</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Automating generation of textual class definitions from OWL to English</article-title>
          .
          <source>J. Biomedical Semantics 2(S-2)</source>
          ,
          <source>S5</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Warren</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mulholland</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Collins,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Motta</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          :
          <article-title>The usability of Description Logics</article-title>
          .
          <source>In: The Semantic Web: Trends and Challenges</source>
          , pp.
          <fpage>550</fpage>
          -
          <lpage>564</lpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Williams</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Power</surname>
          </string-name>
          , R.:
          <article-title>Levels of organisation in ontology verbalisation</article-title>
          .
          <source>In: Proceedings of the 13th European Workshop on Natural Language Generation</source>
          . pp.
          <fpage>158</fpage>
          -
          <lpage>163</lpage>
          . Association for Computational Linguistics (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>