<!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>Problems impacting the quality of automatically built ontologies</article-title>
      </title-group>
      <abstract>
        <p>Building ontologies and debugging them is a timeconsuming task. Over the recent years, several approaches and tools for the automatic construction of ontologies from textual resources have been proposed. But, due to the limitations highlighted by experimentations in real-life applications, different researches focused on the identification and classification of the errors that affect the ontology quality. However, these classifications are incomplete and the error description is not yet standardized. In this paper we introduce a new framework providing standardized definitions which leads to a new error classification that removes ambiguities of the previous ones. Then, we focus on the quality of automatically built ontologies and we present experimental results of our analysis on an ontology automatically built by Text2Onto for the domain of composite materials manufacturing.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Toader GHERASIM1 and</title>
    </sec>
    <sec id="sec-2">
      <title>Giuseppe BERIO2 and</title>
    </sec>
    <sec id="sec-3">
      <title>Mounira HARZALLAH3 and</title>
    </sec>
    <sec id="sec-4">
      <title>Pascale KUNTZ4</title>
      <p>
        Since the pioneering works of Gruber [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], ontologies play a
major role in knowledge engineering whose importance is growing with
the rise of the semantic Web. Today they are an essential component
in numerous applications in various fields: e.g. information retrieval
[
        <xref ref-type="bibr" rid="ref20 ref22">22, 20</xref>
        ], knowledge management [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ], analysis of social semantic
networks [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] and business intelligence [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ]. However, despite the
maturity level reached in ontology engineering, important problems
remain open and are still widely discussed in the literature. The most
challenging issues concern the automation of ontology construction
and their evaluation.
      </p>
      <p>
        The increasing popularity of ontologies and the scaling changes of
this last decade have motivated the development of ontology
learning techniques. Promising results have been obtained [
        <xref ref-type="bibr" rid="ref5 ref6">6, 5</xref>
        ]. And,
although these techniques have been often experimentally proved to
be not sufficient enough for constructing ready-to-use ontology [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
their interest is not questioned in particular in technical domains [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
Few recent works recommend an integration between ontology
learning techniques and manual intervention [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ].
      </p>
      <p>
        Whatever their use, it is essential to assess their quality
throughout their development. Several ontology quality criteria and
different evaluation methods have been proposed in the literature
[
        <xref ref-type="bibr" rid="ref1 ref11 ref19 ref21 ref4">19, 4, 11, 21, 1</xref>
        ]. However, as mentioned by [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ], defining ”a good
ontology” remains a difficult problem and the different approaches
only permit to ”recognize problematic parts of an ontology”. From
an operational point of view, error identification is a very important
step for the ontology integration in real-life complex systems. And,
different researches recently focused on that issue [
        <xref ref-type="bibr" rid="ref13 ref2 ref24">13, 2, 24</xref>
        ].
However, as far as we know, a generic standardized description of these
errors does not still exist. It seems however a preliminary step for the
development of assisted construction method.
      </p>
      <p>
        In this paper, we focus on the most important errors that affect
the quality of semi-automatically built ontologies. To get closer the
operational concerns we propose a detailed typology of the different
types of problems that can be identified when evaluating an ontology.
Our typology is inspired from a generic standardized description of
the notion of quality in conceptual modeling [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. And, our analysis
is applied on a real-life situation concerning the manufacturing of
pieces in composite materials for the aerospace industry.
      </p>
      <p>The rest of this paper is organized as follows. Section 2 is a
stateof-the art of the ontology errors. Section 3 describes a framework
which provides a standardized description of the errors and draws
correspondences between our new classification and the main errors
previously identified in the literature. Section 4 presents our
experimental results in the domain of composite materials manufacturing.
More precisely, we analyze errors affecting an ontology produced by
an automatic construction tool (here Text2Onto) from a set of
technical textual resources.
2</p>
      <sec id="sec-4-1">
        <title>State-of-the art on ontological errors</title>
        <p>
          In the literature, the notion of ”ontological error” is often used in a
broad sense covering a wide variety of problems which affect the
ontology quality. But, from several studies published this last decade,
we have identified four major denominations associated to
complementary definitions: (1) ”taxonomic errors” [
          <xref ref-type="bibr" rid="ref13 ref14 ref2 ref9">14, 13, 9, 2</xref>
          ], (2) ”design
anomalies” or ”deficiencies” [
          <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
          ], (3) ”anti-patterns” [
          <xref ref-type="bibr" rid="ref23 ref25 ref7">7, 25, 23</xref>
          ],
and (4) ”pitfalls” or ”worst practices [
          <xref ref-type="bibr" rid="ref23 ref24">23, 24</xref>
          ].
2.1
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>Taxonomic errors</title>
        <p>
          From the pioneering works of Gomez-Perrez [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], the denomination
”taxonomic error” is used to refer to three types of errors that affect
the taxonomic structure of ontologies: inconsistency, incompleteness
and redundancy. Recently, extensions have been proposed to
nontaxonomic properties [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], but in this synthesis we focus on taxonomic
errors.
        </p>
        <p>Inconsistencies in the ontology may be logical or semantic. More
precisely, three classes of inconsistencies in the taxonomic structure
have been detailed: circularity errors (e.g. a concept that is a
specialization or a generalization of itself), partitioning errors which
produce logical inconsistencies (e.g. a concept defined as a
specialization of two disjoint concepts), and semantic errors (e.g. a taxonomic
relationship between two concepts that is not consistent with the
semantics of the latter).</p>
        <p>Incompleteness is met when concepts or relations of specialization
are missing, or when some distributions of the instances of a concept
between its sons are not stated as exhaustive and/or disjoint.</p>
        <p>In the opposite way, redundancy errors are met when a taxonomic
relationship can be directly deduced by logical inference from the
other relationships of the ontology, or when concepts with the same
father in the taxonomy do not share any common information (no
instances, no children, no axioms, etc.) and can be only differentiated
by their names.
2.2</p>
      </sec>
      <sec id="sec-4-3">
        <title>Design anomalies</title>
        <p>Roughly speaking, design anomalies mainly focus on ontology
understanding and maintainability. They are not necessarily errors but
undesirable situations. Five classes of design anomalies have been
described: (1) ”lazy concepts” (leaf concepts in the taxonomy not
implied in any axiom and without any instances); (2) ”chains of
inheritance” (long chains composed of intermediate concepts with a
single child); (3) ”lonely disjoint” concepts (superfluous disjunction
axiom between distant concepts in the taxonomy which may disrupt
inference reasoning); (4) ”over-specific property range” (too specific
property range which should be replaced by a coarser range which
fits the considered domain better); (5) ”property clumps”
(duplication of the same properties for a large set of concepts instead of the
inheritance of these properties from a more general concept).
2.3</p>
      </sec>
      <sec id="sec-4-4">
        <title>Anti-patterns</title>
        <p>
          Ontology design patterns (ODP) are formal models of solutions
commonly used by domain experts to solve recurrent modeling problems.
Anti-patterns are ODP that are a priori known to produce
inconsistencies or unsuitable behaviors. [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] also called anti-patterns
adhoc solutions specifically designed for a problem even if well-known
ODP are available. Three classes of anti-patterns have been described
[
          <xref ref-type="bibr" rid="ref23 ref25 ref7">7, 25, 23</xref>
          ]: (1) ”logical anti-patterns” that can be detected by
logical reasoning; (2) ”cognitive anti-patterns” (possible modeling errors
due to misunderstanding of the logical consequences of the used
expression); (3) ”guidelines” (complex expressions valid from a logical
and a cognitive point of view but for which simpler or more accurate
alternatives exist).
2.4
        </p>
      </sec>
      <sec id="sec-4-5">
        <title>Pitfalls</title>
        <p>
          Pitfalls are complementary to ODPs. Their broad definition covers
problems affecting the ontology quality for which ODPs are not
available. Poveda et al. [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] described 24 types of experimentally
identified pitfalls as, for instance, forgetting the declaration of an
inverse relation when this latter exists or of the attribute range. And
they proposed a pitfall classification which follows the three
evaluable dimensions of an ontology proposed by Gangemi et al. [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]:
(1) structural dimension (aspects related to syntax and logical
properties), (2) functional dimension (how well the ontology fits a
predefined function), (3) the usability dimension (to which extent the
ontology is easy to be understood and used). Four pitfall classes
correspond to the structural dimension: ”modeling decisions” (MD,
situations where OWL primitives are not used properly), ”wrong
inference” (WI, e.g. relationships or axioms that allow false reasoning),
”no inference” (NI, gaps in the ontology which do not allow
inferences required to produce new desirable knowledge), ”real world
modeling” (RWM, when commonsense knowledge is missing in the
ontology). One class corresponds to the functional dimension:
”requirement completeness” (RC, when the ontology does not cover its
specifications). And, two classes correspond to the usability
dimension: ”ontology understanding” (OU, information that makes
understandability more difficult e.g. concept label polysemy or label
synonymy for distinct concepts, non explicit declaration of inverse
relations or equivalent properties) and ”ontology clarity” (OC, e.g.
variations of writing-rule and typography for the labels).
        </p>
        <p>
          It is easy to deduce from this classification that some pitfalls
should belong to different classes associated to different dimensions
(e.g. the fact that two inverse relations are not stated as inverse is
both a ”no inference” (NI) pitfall and an ”ontology understanding”
(OU) pitfall). Another attempt [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] proposed a classification of the
24 identified pitfalls in the three error classes (inconsistency,
incompleteness and redundancy) given by Gomez-Perrez et al. [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. But,
these classes are concerned by the ontology structure and content,
and consequently four pitfalls associated with the ontology context
do not fit with this classification.
        </p>
        <p>
          In order to highlight the links between the different classifications,
Poveda et al. tried to define a mapping between the classification in 7
classes deduced from the dimensions defined by Gangemi et al. [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]
and the 3 error classes proposed by Gomez-Perrez et al. [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
However, this task turned out to be very complex, and only four pitfall
classes exactly fit with one of the error classes. For the other, there is
overlapping or no possible fitting.
3
        </p>
      </sec>
      <sec id="sec-4-6">
        <title>The framework</title>
        <p>The state of the art briefly presented in the previous section shows
that the terminology used for describing the different problems
impacting on the quality of ontologies is not yet standardized and that
existing classifications do not cover the whole diversity of problems
described in the literature.</p>
        <p>In this section we present a framework providing standardized
definitions for quality problems of ontologies and leading to a new
classification of these problems. The framework comprises two distinct
and orthogonal dimensions: errors vs. unsuitable situations (first
dimension) and logical facet vs. social facet of problems (second
dimension).</p>
        <p>Unsuitable situations identify problems which do not prevent the
usage of an ontology (within specific targeted domain and
applications). On the contrary, errors identify problems preventing the usage
of an ontology.</p>
        <p>It is well known that one ontology has two distinct facets: an
ontology can be processed by machines (according to its logical
specification) and can be used by humans (including an implicit reference
to a social sharing).</p>
        <p>The remainder of the section is organized alongside the second
dimension (i.e. logic vs. social facet) and within each facet, errors and
unsuitable situations are defined. The framework is based on
”natural” analogies between respectively social and logical errors and
social and logical unsuitable situations.
3.1
3.1.1</p>
      </sec>
      <sec id="sec-4-7">
        <title>Problem classification</title>
        <sec id="sec-4-7-1">
          <title>Logical ground problems</title>
          <p>
            The logical ground problems can be formally defined by
considering notions defined by Guarino et al. [
            <xref ref-type="bibr" rid="ref16">16</xref>
            ]: e.g. Interpretation
(Extensional first order structure), Intended Model, Language, Ontology
and the two usual relations , ` provided in any logical language.
The relation is used to express both that one interpretation I is a
model of a logical theory T , written as I T (i.e. all the formulas
in T are true in I, written for each formula ' 2 T , I '), and
also for expressing the logical consequence (i.e. that any model of a
logical theory T is also a model of a formula, written as T '). The
relation ` is used to express the logical calculus i.e. the set of rules
used to prove a theorem (i.e. any formula) ' starting from a theory
T , written as T ` '.
          </p>
          <p>Examples and formalizations hereinafter are provided by using a
typical Description Logics notation (but easily transformable in first
order or other logics).</p>
          <p>The usual logical ground errors are listed below.
1. Logical inconsistency corresponding to ontologies containing
logical contradictions for which a model does not exist (because the
set of intended models is never empty, an ontology without
models does not make sense anyway; formally, given an ontology O
and the logical consequence relation according to the logical
language L used for building O, there is no interpretation I of
O such that I O). For example, if an ontology contains the
following axioms B A (B is a A), A \ B &gt; (A and B
are disjoint), c B (c is instance of B), then c A and
c A \ B, so there is a logical contradiction in the definition of
this ontology;
2. Unadapted5 ontologies wrt to intended models6 i.e. an ontology
for which something that is false in all (some of) the intended
models of L is true in the ontology; formally, there exists a
formula ' such that for each (for some) intended model(s) of L, '
is false and O '. For example, if we have in the ontology two
concepts A and B that are declared as disjoint (O A \ B ?)
and in each intended model there exists an instance c that is
common between A and B (i.e. c A \ B), then the ontology is
unadapted;
3. Incomplete ontologies wrt to intended models i.e. an ontology for
which something that is true in all the intended models of L, is
not necessarily true in all the models of O; formally, there exists
a formula ' such that for each intended model of L, ' is true and
O 2 '. As an example, if in all the intended models C [ B = A,
and the ontology O defines B A and C A, it is not possible
to prove that C [ B = A;
4. Incorrect (or unsound) reasoning wrt the logical consequence i.e.
when some specific conclusions are derived by using suitable
reasoning systems for targeted ontology applications even if these
conclusions are not true in the intended models and must not be
derived by any reasoning according to the targeted ontology
applications (formally, when a specific formula ', false in the intended
models O 2 ', can be derived O ` ' within any of those suitable
reasoning systems);
5. Incomplete reasoning wrt the logical consequence i.e. when some
specific conclusions cannot be derived by using suitable reasoning
systems for targeted ontology applications even if these
conclusions are true in intended models and must be derived by some
5 We use the term ”unadapted” instead of ”incorrect” ontologies because it
remains unclear if intended models are defined for building the ontology
or may also be defined independently. However, if intended models are
defined for building the ontology, the term ”incorrect” may be more
appropriate.
6 Intended models should have been defined fully and independently as in the
case of models representing abstract structures or concepts such as
numbers, processes, events, time and other ”upper concepts”, often defined
according to their own properties. If intended models are not available, some
specific entailments can be defined as facts that should necessarily be true
in the targeted domain (or for targeted applications); specific
counterexamples can also be defined instead of building entire intended models.
reasoning according to the targeted ontology applications
(formally, for some specific formula ', true in the intended models
O ', cannot be derived O 0 ' within those suitable reasoning
systems);</p>
          <p>The most common logical ground unsuitable situations are
listed below. These situations impact negatively on the ”non
functional qualities” of ontologies such as reusability, maintainability,
efficiency as defined in the ISO 9126 standard for software quality.
6. Logical equivalence of distinct artifacts (concepts / relationships
/ instances) i.e. whenever two distinct artifacts are proved to be
logically equivalent; for example, A and B are two concepts in O
and O A = B;
7. Symmetrically, logically indistinguishable artifacts i.e. whenever
it is not possible to prove that two distinct artifacts are not
equivalent from a logical point of view; in other words, if not
possible to prove anyone of the following statements: (O A = B),
(O A \ B ?) and (O c AandO c B); this case
(7) can be partially covered in the case (3) above whenever
intended models provide precise information on the equivalence or
the difference between A and B;
8. OR artifacts i.e. an artifact A equivalent to a disjunction like C[S,
A 6= C; S but for which, if applicable, it does not exist at least a
common (non optional) role / property for C and S or because C
and S have common instances; in the first case, a simple
formalization can be expressed by saying that it does not exist a (non
optional) role R such that O (C [ S) 9R:&gt;; in the second
case, an even simpler formalization is O c C and O c S,
being c one constant not part of O; the first case targets potentially
heterogeneous artifacts such as Car [ P erson, with probably
no counterpart in the intended models, thus possibly leading to
unadapted ontologies according to case (2) above; the second case
targets potential ambiguities as, for instance, one role (property)
R logically equivalent to a disjunction (R1 [ R2) being (R1 \ R2)
satisfiable;
9. AND artifacts i.e. one artifact A equivalent to a conjunction like
C \ S, A 6= C; S but for which, if applicable, it does not exist
at least a common (non optional) role / property for C and S;
this case is relevant to limit as much as possible some potentially
heterogeneous artifacts such as Car \ P erson, possibly leading
to artifact unsatisfiability;
10. While some case of unsatisfiability of ontology artifacts (concepts,
roles, properties etc.) can be covered by (2) because intended
models may not contain void concepts, unsatisfiability tout-court is not
necessarily an error but a situation which is not suitable for
ontology artifacts (i.e. given an ontology artifact A, O A ?); even
if in ontologies it might be possible to define what must not be true
(instead of what must be true), this practice is not encouraged;
11. High complexity of the reasoning task i.e. whenever something
is expressed in a way that complicates the reasoning, while there
exist more simple ways to express the same thing;
12. Ontology not minimal i.e. whenever the ontology contains
unnecessary information:</p>
          <p>Unnecessary because it can be derived or built7. An example of
such unsuitable situation is the redundancy of taxonomic
relations such as whenever A B, B C, and A C are all
ontology axioms, the last axiom can be derived from the first
two ones;
7 Built means that the artifact can be defined by using other artifacts.
Unnecessary because it is not part of the intended models. For
instance, a concept A being part of the ontology (language) but
not defined by intended models.
3.1.2</p>
        </sec>
        <sec id="sec-4-7-2">
          <title>Social ground problems</title>
          <p>Social ground problems are related to the perception
(interpretation) and the targeted usage of ontologies by social actors (humans,
applications based on social artifacts like WordNet, etc.).
Perception (interpretation) and usage may not be formalized at all. In some
sense, a further distinction between social facet and logical facet is
as the distinction between respectively tacit and explicit knowledge.</p>
          <p>There are four social ground errors:
1. Social contradiction i.e. the perception (interpretation) that the
social actor gives to the ontology or to the ontology artifacts is in
contradiction with the ontology axioms and their consequences; a
natural analogy is with unadapted ontologies;
2. Perception of design errors i.e. the social actor perception
accounts for some design errors such as modeling instances as
concepts; a natural analogy is with unadapted ontologies;
3. Socially meaningless i.e. the social actor is unable to give any
interpretation to the ontology or to ontology artifacts as in the case
of artificial labels such as ”XYHG45”; a natural analogy is with
unadapted ontologies;
4. Social incompleteness i.e. the social actor perception is that one or
several artifacts (axioms and/or their consequences) are missing in
the ontology; a natural analogy is with incomplete ontologies;
The social ground unsuitable situations are mostly related to the
difficulties that a social actor has to overcome for using the ontology
especially due to limited understandability, learnability and
compliance (as defined in ISO 9126). As for the logical ground unsuitable
situations, it is difficult to dress an exhaustive list; the most common
and important are listed below.
5. Lack of or poor textual explanations i.e. when there are few, no or
poor annotations; prevents understanding by social actors; there
are no natural analogies;
6. Potentially equivalent artifacts i.e. the social actors may identify
as equivalent (similar) distinct artifacts as in the case of artifacts
with synonymous or exactly the same labels assigned to distinct
artifacts; a natural analogy is with logically equivalent artifacts;
7. Socially indistinguishable artifacts i.e. the social actors would not
be able to distinguish two distinct artifacts as, for instance, in the
case of artifacts with polysemic labels assigned to distinct
artifacts; a natural analogy is with logically indistinguishable
artifacts;
8. Artifacts with polysemic labels may be interpreted as union or
intersection of their several rather distinct meanings associated to
labels; a natural analogy is therefore with OR and AND artifacts.
9. Flatness of the ontology (or non modularity), i.e. ontology
presented as a set of artifacts without any additional structure,
especially if coupled with a important number of artifacts; a natural
analogy is with high complexity of the reasoning task but also
preventing effective learning and understanding by social actors;
10. Non-standard formalization of the ontology, using a very specific
logics or theory, requires a specific effort by social actors for
understanding and learning the ontology but also to use the ontology
in standard contexts (reduced compliance); there are no natural
analogies;
11. Lack of adapted and certified versions of the ontology in various
languages requires specific efforts by social actors for
understanding and learning the ontology but also to use the ontology in
specific standard contexts (limited compliance); there are no natural
analogies;
12. Socially useless artifacts included in the ontology; a natural
analogy is with ontology not minimal.
3.2</p>
        </sec>
      </sec>
      <sec id="sec-4-8">
        <title>Positioning state of the art relevant problem classes in to the proposed framework</title>
        <p>The precise definitions of the proposed framework allow us to
classify most of the ontology quality problems described in literature.
Table 1 presents our classification of the different problems mentioned
in Section 2. Some of the problems described in literature may
correspond to more than one class of problems from our framework, as
the definitions of these problems are often very large and sometimes
ambiguous.</p>
        <p>Table 1 reveals, at a first view, that the proposed framework
provides additional problems that are not directly pointed out, to our
knowledge, in the current literature about ontology quality and
evaluation (but may be mentioned elsewhere). These problems are No
adapted and certified ontology version, Indistinguishable artifacts,</p>
        <sec id="sec-4-8-1">
          <title>Socially meaningless, High complexity of the reasoning task and In</title>
          <p>correct reasoning. However, while covered, other problems are, in
our opinion, too much narrowly defined in existing literature about
ontology quality and evaluation. For instance, No standard
formalization is specific to very simple situations while we refer to
complete non standard theories.</p>
          <p>
            A deeper analysis of Table 1 reveals that the ”logical anti-patterns”
presented in [
            <xref ref-type="bibr" rid="ref25 ref7">7, 25</xref>
            ] belong to the logical ground category and are
focusing on unadapted ontologies error and unsatisfability
unsuitable situation. The ”non-logical anti patterns” presented in [
            <xref ref-type="bibr" rid="ref25 ref7">7, 25</xref>
            ]
partially cover the logical ground unsuitable situations. The
”guidelines” presented in [
            <xref ref-type="bibr" rid="ref25 ref7">7, 25</xref>
            ] span only over unsuitable situations from
both logical and social ground category.
          </p>
          <p>
            What is qualified as ”inconsistency” in [
            <xref ref-type="bibr" rid="ref14">14</xref>
            ] span over errors and
unsuitable situations and also (as in the case of ”semantic
inconsistency”) over the two dimensions (logical and social), making, in
our opinion, the terminology a little bit confusing. According to our
framework, we perceive ”circularity in taxonomies”, as defined in
[
            <xref ref-type="bibr" rid="ref14">14</xref>
            ], as an unsuitable situation (logical equivalence of distinct
artifacts) because, from a logical point of veiw, this only means that
artifacts are equivalent (not requiring a fixpoint semantics). However,
”circularity in taxonomies” can be seen also within a social
contradiction if actors assign distinct meanings to the various involved
artifacts. The problems presented as ”incompleteness errors” in [
            <xref ref-type="bibr" rid="ref13">13</xref>
            ]
belong to the incomplete ontologies class of logical errors. The
”redundancy errors” fits, in our classification, within the ontology not
minimal class of logical unsuitable situations.
          </p>
          <p>
            None of the ”design anomalies” presented in [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ] is perceived as a
logical error. Two of them correspond to a logical unsuitable situation
(logically undistinguishable artifacts), one to a social error
(perception of design errors) and the last one to a social unsuitable situation
(no standard formalization).
          </p>
          <p>
            Concerning ”pitfalls” [
            <xref ref-type="bibr" rid="ref24">24</xref>
            ], the most remarkable fact concerns
what we call incomplete reasoning. Indeed, introducing ad-hoc
relations such as is a, instance of , etc., replacing the ”standard”
relations such as subsumption, member of , etc., should not be
considered as a case of incomplete ontologies but as a case of incomplete
reasoning. This is because accepting a specific ontological
commitd
n
u
o
r
g
l
a
c
i
g
o
L
d
n
u
o
r
g
l
a
i
c
o
S
          </p>
          <p>Framework
Logical inconsistency
Unadapted ontologies
Incomplete ontologies
Incorrect reasoning
Incomplete reasoning
Logical equivalence of
distinct artifacts
Logically indistinguishable
artifacts
OR artifacts
AND artifacts
Unsatisfiability
High complexity of the
reasoning task
Ontology not minimal
Social contradiction
Perception of design errors
Socially meaningless
Social incompleteness
Lack/poor textual
explanations
Potentially equiv. artifacts
Indistinguishable artifacts
Polysemic labels
Flatness of the ontology
No standard formalization
No adapted and certified
ontology version
Useless artifacts</p>
          <p>State of the art problems
â inconsistency error: ”partition errors - common instances in disjoint decomposition”
â inconsistency errors: ”partition errors - common classes in disjoint decomposition”, ”semantic inconsistency”
â logical anti-patterns: ”OnlynessIsLoneliness”, ”UniversalExistence”, ”AndIsOR”, ”EquivalenceIsDifference”
â pitfalls: P5 (wrong inverse relationship, WI), P14 (misusing ”allValuesFrom”, MD), P15 (misusing ”not
some”/”some not”, WI), P18 (specifying too much the domain / range, WI), P19 (swapping \ and [, WI)
â incompleteness errors: ”incomplete concept classification”, ”disjoint / exhaustive knowledge omission”
â pitfalls: P3 (”is a” instead of ”subclass-of”, MD), P9 (missing basic information, RC &amp; RWM), P10 (missing
disjointness, RWM), P11 (missing domain / range in prop., NI &amp; OU), P12 (missing equiv. prop., NI &amp; OU), P13
(missing inv. rel., NI &amp; OU), P16 (misusing primitive and defined classes, NI)
â pitfalls: P3 (using ”is a” instead of ”subclass-of”, MD), P24 - using recursive def., MD)
â inconsistency error: ”circularity”
â pitfall: P6 (cycles in the hierarchy, WI)
â non logical anti-pattern: ”SynonymeOfEquivalence”
â pitfall: P4 (unconnected ontology elements, RC)
â design anomalies: ”lazy concepts” and ”chains of inheritance”
â pitfall: P7 (merging concepts to form a class, MD &amp; OU)
â pitfall: P7 (merging concepts to form a class, MD &amp; OU)
inconsistency error: ”partition errors - common classes in disjoint decomposition”
â logical anti-patterns: ”OnlynessIsLoneliness”, ”UniversalExistence”, ”AndIsOR”, ”EquivalenceIsDifference”
â redundancy error: ”redundancy of taxonomic relations”
â pitfalls: P3 (using ”is a” instead of ”subclass-of”, MD), P7 (merging concepts to form a class, MD &amp; OU), P21
(miscellaneous class, MD)
â non logical anti-pattern: ”SomeMeansAtLeastOne”
â guidelines: ”Domain&amp;CardinalityConstraints”, ”MinIsZero”
â inconsistency error: ”semantic inconsistency”
â logical anti-pattern: ”AndIsOR”
â pitfalls: P1 (polysemic elements, MD), P5 (wrong inv. rel., WI), P14 (misusing ”allValuesFrom”, MD), P15
(misusing ”not some”/”some not”, WI), P19 (swapping \ and [, WI)
â pitfalls: P17 (specializing too much the hierarchy, MD), P18 (specifying too much the domain / range, WI), P23
(using incorrectly ontology elements, MD)
â non logical anti-pattern: ”SumOfSome”
â design anomaly: ”lonely disjoints”
â pitfalls: P12 (missing equiv. prop., NI &amp; OU), P13 (missing inv. rel., NI &amp; OU), P16 (misusing primitive and
defined classes, NI)
â pitfalls: P8 (missing annotation, OC &amp; OU)
â pitfalls: P2 (synonym as classes, MD &amp; OU)
â pitfalls: P1 (polysemic elements, MD &amp; OU)
â pitfalls: P20 (swapping label and comment, OU), P22 (using different naming criteria in the ontology, OC)
â guidelines: ”GroupAxioms”, ”DisjointnessOfComplement” and ”Domain&amp;CardinalityConstraints”
â design anomaly: ”property clumps”
â pitfall: P21 (using a miscellaneous class, MD &amp; OU)</p>
          <p>What problems are expected in automatically built ontologies.
ment for building intended models, ad-hoc relations can be defined
in the same way as standard relations. However, using standard
reasoning it is expected (and even proved once fixing the logics) that
reasoning algorithms are incomplete. However, adding artifacts may
also solve some incompleteness and may also be useful for speeding
up reasoning.</p>
          <p>
            Only one of the seven classes of ”pitfalls” [
            <xref ref-type="bibr" rid="ref24">24</xref>
            ] perfectly fits in one
class of our typology: the ”real world modeling” pitfalls belong to the
incomplete ontologies logical errors. All the ”ontology clarity”
pitfalls are social unsuitable situations. All the ”requirement
completeness” pitfalls are logical problems. The ”no inference” pitfalls are
logical or social incomplete ontologies errors. Most (6/9 and 4/5) of
the ”modeling decisions” and ”wrong inference” pitfalls are
considered as errors. The class of ”ontology understanding” pitfalls spans
over 10 classes of problems, covering logical and social errors and
unsuitable situations.
          </p>
          <p>
            Most (16/20) of the pitfalls concerning the ”structural dimension”
of the ontology [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ] are perceived as errors. All (2/2) the pitfalls
concerning the ”functional dimension” of the ontology are logical
problems.
4
          </p>
        </sec>
      </sec>
      <sec id="sec-4-9">
        <title>Problems that affect the quality of automatically built ontologies</title>
        <p>Although the proposed framework is general, we are especially
concerned by ontologies automatically built from textual resources. We
therefore aim at pointing the problems that are expected in
automatically constructed ontologies (i.e. there is evidence of their presence
or they will appear in future enrichments8 of the ontology). We are
also interested by the opposite case, i.e. if there are unexpected
problems in automatically constructed ontologies: it should be noted that
unexpected problems are problems that even if the ontology may
suffer of them, there is no evidence of their presence/absence for the
ontology as it is (however, these problems may appear in future
enrichments of the ontology). Our analysis is performed in two steps. In
the first step (Section 4.1), we point out expected/unexpected
problems due to inherent limitations of the tools for automatic ontology
construction. In the second step (Section 4.2), we assess the results
obtained in the first step by discussing our experience with the tool
Text2Onto.
4.1</p>
      </sec>
      <sec id="sec-4-10">
        <title>Expected and unexpected problems in an automatically built ontology</title>
        <p>
          In a previous work [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] we have deeply studied four approaches (and
associated tools) for the automatic construction of ontologies form
texts and we compared them with a classical methodology for manual
ontology construction (Methontology). This analysis highlighted that
none of the automated approaches (and associated tools) covers all
the tasks and subtasks associated to each step of the classical manual
method. The ignored tasks/subtasks are:
1. The explicit formation of artifacts (concepts, instances and
relationships) from terms9; usually, the automatic tools consider that
each term represents a distinct artifact: they do not group
synonymous terms and do not choose a single sense for polysemic terms
2. The identification of axioms (e.g. the disjunction axioms)
3. The identification of attributes for concepts
4. The identification of natural language definitions for concepts
8 Enrichment should be understood as adding artifacts to the existing ones.
9 A term corresponds to one or several words found in one text.
Types of problems
1. Logical inconsistency
2. Unadapted ontologies
3. Incomplete ontologies
4. Incorrect reasoning
5. Incomplete reasoning
6. Logical equivalence of
distinct artifacts
7. Logically
indistinguishable artifacts
8. OR artifacts
9. AND artifacts
10. Unsatisfiability
11. High complexity of
the reasoning task
12. Ontology not
minimal
1. Social contradiction
2. Perception of design
errors
3. Social meaningless
6. Potentially equivalent
artifacts
7. Indistinguishable
artifacts
8. Artifacts with
polysemic labels
9. Flatness of the
ontology
        </p>
        <p>Expected (Yes/No) and Why
N (no axiom is defined ) contradictions are
unexpected; but they remain possible in the
case of future enrichments)
Y (taxonomic relationships extraction
algorithms are syntax based 6= from the intended
models)
Y (automatically extracted knowledge is
limited to concepts and taxonomies 6= from
the intended models)
N (they might appear for complete
formalization of concepts and relationships)
Y (automatic tools consider that each term
defines a different artifact ) the ontology
may contain logically equivalent &amp; logically
indistinguishable artifacts)
Y (polysemy of terms directly affects
concepts / relationships: OR / AND concepts /
relationships may appear)
Y (polysemy of terms directly affects
concepts / relationships: these latter may
become unsatisfiable if their polysemic senses
are combined)
N (few or no axioms are defined )
reasoning remains very basic; but, it can be more
complex if the ontology is further enriched)
Y (automatic tools introduce redundancies in
taxonomies)
Y (ontologies are built from limited textual
resources which may introduce contradiction
in taxonomies)
Y (the built ontology may contain concepts
that are considered more close to instances
by the social actor.)
Y (several meaningless concepts with
obscure labels are often introduced)
Y (automatic tools consider that each term
defines a different artifact ) distinct
concepts can have synonymous labels ) these
latter are perceived as potentially equivalent)
Y (the ontology is incomplete ) it contains
concepts that can be distinguished only by
their labels; if such concepts have
synonymous labels, they are indistinguishable)
Y (automatic tools consider that each term
defines a different artifact ) it is possible to
have concepts with polysemic labels)
Y (the ontology is poorly structured and has
no design constraints - e.g. no disjunction
axiom, lazy concepts)
4. Social incompleteness</p>
        <p>Y (probably due to limited textual corpus)
5. Lack of or poor textual
explanations</p>
        <p>Y (usually automatic tools do not provide
textual explanations)
10. No standard
formalization</p>
        <p>N (automatic tools usually can export their
results in different formalization)
11. No adapted and
certified ontology version
12. Useless artifacts</p>
        <p>Y (automatically obtained results closely
depend on the input texts language (often
English) and certifying them is difficult)
Y (automatic tools often generate useless
artifacts from additional external resources)</p>
      </sec>
      <sec id="sec-4-11">
        <title>Experience with Text2Onto</title>
        <sec id="sec-4-11-1">
          <title>The experimental setup</title>
          <p>During the last two years we were implied in a project called ISTA3
that proposed an ontology based solution for problems related to the
integration of heterogeneous sources of information. The application
domain was the management of the production of composite
components for the aerospace industry. In this context, we tried to simplify
the process of deploying the interoperability solution in new domains
by using automatic solution for constructing the required ontologies.</p>
          <p>
            The analysis presented in [
            <xref ref-type="bibr" rid="ref12">12</xref>
            ] conducted us to choose Text2Onto
[
            <xref ref-type="bibr" rid="ref6">6</xref>
            ] for the automatic construction of our ontologies. Text2Onto takes
as input textual resources from which it extracts different
ontological artifacts (concepts, instances, taxonomic relationships, etc.) that
are structured together to construct an ontology. Text2Onto
performances for extracting concepts and taxonomical relationships are
better than its performances for extracting other types of
ontological artifacts; consequently, in our tests we used Text2Onto for
constructing ontologies containing concepts and taxonomical
relationships only.
          </p>
          <p>The textual resource used in the experiment presented in this paper
is a technical glossary composed of 376 definitions of the most
important terms of the domain of composite materials and how are they
used for manufacturing pieces. The glossary contains 9500 words.
For constructing the ontology we resort to the standard
configuration for the different parameters of Text2Onto: all the proposed
algorithms for concepts (and respectively for taxonomic relations)
extractions have been used and their results have been combined with
the default strategy.</p>
          <p>The constructed ontology is an automatically built domain
ontology that contains 965 concepts and 408 taxonomic relationships.
Some of the central concepts of this ontology are: ”technique”,
”step”, ”compound”, ”fiber”, ”resin”, ”polymerization”, ”laminate”,
”substance”, ”form”.
4.2.2</p>
        </sec>
        <sec id="sec-4-11-2">
          <title>Identified problems</title>
          <p>Table 3 summarizes which types of problems have been identified
in the automatically constructed ontology in our experience with
Text2Onto. It also indicates, when possible, how many problems
have been identified. Most of problems are relatively easy to
identify and to quantify (e.g. the number of cycles in the taxonomical
structure), but there are exceptions (e.g. the number of concepts or
taxonomic relationships that are missing from the ontology).
4.2.3</p>
        </sec>
        <sec id="sec-4-11-3">
          <title>Discussion</title>
          <p>No intended model or use case scenario was available when the
expert analyzed the automatically constructed ontology. Consequently,
it was able only to make a supposition concerning the logical
completeness of the ontology and no logical error (unadapted ontology,
incomplete or incorrect reasoning) was identified.</p>
          <p>Few logical unsuitable situations are identified, but it is remarkable
that they were identified automatically.</p>
          <p>Unsurprisingly, most of the identified problems are social
problems.</p>
          <p>Yes: one taxonomical relationship can be
deduced from two taxonomical relationships
already present in the ontology
(automatically identified by an ad-hoc algorithm)
Yes: 15 taxonomic relationships are jugged
semantically inconsistent by the expert
Yes: 5 concepts that are interpreted as
instances by the expert (units of measure and
proper names)
Yes: 21 concepts that have meaningless
labels, for the expert
Yes: no annotation associated to the ontology
or to its artifacts
Yes: 6 pairs of concepts have synonym
labels, for the expert
Yes: 69 concepts with polysemic labels, for
the expert
Yes: 389 lazy concepts lead to a poorly
structured ontology
Yes: 28 concepts are not necessary (3 are too
generic, 25 are out of the domain)
6. Logical equivalence of
distinct artifacts
7. Logically
indistinguishable artifacts
8. OR artifacts
9. AND artifacts
10. Unsatisfiability
11. High complexity of
the reasoning task
12. Ontology not
minimal
1. Social contradiction
2. Perception of design
errors
3. Social meaningless
4. Social incompleteness
5. Lack of or poor textual
explanations
6. Potentially equivalent
artifacts
7. Indistinguishable
artifacts
8. Artifacts with
polysemic labels
9. Flatness of the
ontology
10. No standard
formalization
11. No adapted and
certified ontology version
12. Useless artifacts</p>
          <p>No
No
No
No
No
No
Yes
No
No
No</p>
          <p>The analysis in Section 4.1 suggest that most of the problems that
are expected in the automatically constructed ontologies are due to
the fact that the automatic tool do not take into account the synonymy
and the polysemy of terms when constructing concepts. However,
even if Text2Onto, as configured for our test, do not group synonym
terms when forming concepts, and allows polysemic terms to be
labels for concepts, our test-case reveals that only two types of
problems (socially indistinguishable artifacts and artifacts with polysemic
labels) may be imputed to this limitation.</p>
          <p>Most of the identified problems are related to the fact that the
automatically constructed ontology seems to be incomplete.
5</p>
        </sec>
      </sec>
      <sec id="sec-4-12">
        <title>Conclusion</title>
        <p>In this paper, we have introduced a framework providing
standardized definitions for different errors that have some impact on the
quality of the ontologies. This framework aims at both unifying
various error descriptions presented in the recent literature and
completing them. It also leads to a new error classification that removes
ambiguities of the previous ones. During ontology evaluation this
framework may be used as a support for verifying in a systematic
way if the ontology contains errors or unsuitable situations.</p>
        <p>In the second part of the paper we focused on the quality of
automatically built ontologies and we present experimental results of
our analysis on an ontology automatically built by Text2Onto. The
results show that a large part of the identified errors are linked to
the ontology incompleteness. Moreover, it confirms that the
identification of logical errors other than inconsistency requires intended
models (or at least a set of positive and negative examples) and use
case scenarii.</p>
        <p>
          Due to the increasing complexity of the software, the identification
of the origin of each error in the ontology building process remains an
open question. And a further works consists in associating the
identified errors with the different tasks of an ontology construction (e.g.
the Methontology tasks [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]). This work could help to improve the
quality results of the software by a retro-engineering process and/or
to design assistant to detect and to solve major errors.
        </p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Almeida</surname>
          </string-name>
          , '
          <article-title>A proposal to evaluate ontology content'</article-title>
          ,
          <source>Journal of Applied Ontology</source>
          ,
          <volume>4</volume>
          (
          <issue>3-4</issue>
          ),
          <fpage>245</fpage>
          -
          <lpage>265</lpage>
          , (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Baumeister</surname>
          </string-name>
          and
          <string-name>
            <given-names>D.</given-names>
            <surname>Seipel</surname>
          </string-name>
          , '
          <article-title>Smelly owls design anomalies in ontologies'</article-title>
          ,
          <source>in Proc. of 18th Int. Florida Artificial Intelligence Research Society Conf. (FLAIRS)</source>
          , pp.
          <fpage>215</fpage>
          -
          <lpage>220</lpage>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Baumeister</surname>
          </string-name>
          and
          <string-name>
            <given-names>D.</given-names>
            <surname>Seipel</surname>
          </string-name>
          , '
          <article-title>Anomalies in ontologies with rules'</article-title>
          ,
          <source>Web Semantics: Science, Services and Agents on the World Wide Web</source>
          ,
          <volume>8</volume>
          (
          <issue>1</issue>
          ),
          <fpage>55</fpage>
          -
          <lpage>68</lpage>
          , (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Burton-Jones</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Storey</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Sugumaran</surname>
          </string-name>
          , '
          <article-title>A semiotic metrics suite for assessing the quality of ontologies', Data Knowl</article-title>
          . Eng.,
          <volume>55</volume>
          (
          <issue>1</issue>
          ),
          <fpage>84</fpage>
          -
          <lpage>102</lpage>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>P.</given-names>
            <surname>Cimiano</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Madche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Volker</surname>
          </string-name>
          , '
          <article-title>Ontology learning'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          ,
          <fpage>245</fpage>
          -
          <lpage>267</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>P.</given-names>
            <surname>Cimiano</surname>
          </string-name>
          and
          <string-name>
            <given-names>J.</given-names>
            <surname>Volker</surname>
          </string-name>
          , '
          <article-title>Text2onto - a framework for ontology learning and data-driven change discovery'</article-title>
          ,
          <source>in 2nd Eur. Semantic Web Conf</source>
          ., eds.,
          <string-name>
            <given-names>A.</given-names>
            <surname>Montoyo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Munoz</surname>
          </string-name>
          , and E. Metais, volume
          <volume>3513</volume>
          , pp.
          <fpage>227</fpage>
          -
          <lpage>238</lpage>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>O.</given-names>
            <surname>Corcho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Roussey</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L. M. V.</given-names>
            <surname>Blazquez</surname>
          </string-name>
          , '
          <article-title>Catalogue of antipatterns for formal ontology debugging', in Atelier Construction d'ontologies: vers un guide des bonnes pratiques</article-title>
          ,
          <source>AFIA</source>
          <year>2009</year>
          , (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>G.</given-names>
            <surname>Ereteo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Buffa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Corby</surname>
          </string-name>
          , and
          <string-name>
            <given-names>F.</given-names>
            <surname>Gandon</surname>
          </string-name>
          , '
          <article-title>Semantic social network analysis: A concrete case'</article-title>
          ,
          <source>in Handbook of Research on Methods and Techniques for Studying Virtual Communities: Paradigms and Phenomena</source>
          ,
          <volume>122</volume>
          -
          <fpage>156</fpage>
          , IGI Global,
          <article-title>(</article-title>
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M.</given-names>
            <surname>Fahad</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Qadir</surname>
          </string-name>
          , '
          <article-title>A framework for ontology evaluation'</article-title>
          ,
          <source>in Proc. of the 16th Int. Conf. on Conceptual Struct. (ICCS2008)</source>
          , volume
          <volume>354</volume>
          , pp.
          <fpage>149</fpage>
          -
          <lpage>158</lpage>
          , (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Fernandez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Prez</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>N.</given-names>
            <surname>Juristo</surname>
          </string-name>
          , '
          <article-title>Methontology: From ontological art towards ontological engineering'</article-title>
          ,
          <source>in Proc. of the AAAI97 Spring Symposium Series on Ontological Engineering</source>
          , pp.
          <fpage>33</fpage>
          -
          <lpage>40</lpage>
          , (
          <year>1997</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Catenacci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ciaramita</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          , '
          <article-title>Modelling ontology evaluation and validation'</article-title>
          ,
          <source>in Proc. of Eur. Sem. Web Conf</source>
          .
          <article-title>(ESWC2006), number</article-title>
          4011 in
          <string-name>
            <surname>LNCS</surname>
          </string-name>
          , (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>T.</given-names>
            <surname>Gherasim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Harzallah</surname>
          </string-name>
          , G. Berio, and
          <string-name>
            <given-names>P.</given-names>
            <surname>Kuntz</surname>
          </string-name>
          , '
          <article-title>Analyse comparative de methodologies et d'outils de construction automatique d'ontologies a partir de ressources textuelles'</article-title>
          ,
          <source>in Proc. of EGC'2011</source>
          , pp.
          <fpage>377</fpage>
          -
          <lpage>388</lpage>
          , (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          , '
          <article-title>Ontology evaluation'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          , pp.
          <fpage>251</fpage>
          -
          <lpage>274</lpage>
          , Springer,
          <volume>1</volume>
          <fpage>edn</fpage>
          ., (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.F.</given-names>
            <surname>Lopez</surname>
          </string-name>
          , and
          <string-name>
            <given-names>O.C.</given-names>
            <surname>Garcia</surname>
          </string-name>
          , Ontological Engineering:
          <article-title>With Examples from the Areas of Knowledge Management, ECommerce and the Semantic Web</article-title>
          ,
          <source>chapter Chap 3.8</source>
          .
          <issue>2 Taxonomy evaluation</issue>
          ,
          <fpage>180</fpage>
          -
          <lpage>184</lpage>
          ,
          <string-name>
            <given-names>Advanced</given-names>
            <surname>Information</surname>
          </string-name>
          and
          <string-name>
            <given-names>Knowledge</given-names>
            <surname>Processing</surname>
          </string-name>
          , Springer,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>T. R.</given-names>
            <surname>Gruber</surname>
          </string-name>
          , '
          <article-title>A translation approach to portable ontology specifications'</article-title>
          ,
          <source>Knowl. Acquisition</source>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ),
          <fpage>199</fpage>
          -
          <lpage>220</lpage>
          , (
          <year>1993</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Oberle</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          , '
          <article-title>What is an ontology?'</article-title>
          , in Handbook on Ontologies,
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>G.</given-names>
            <surname>Hirst</surname>
          </string-name>
          , '
          <article-title>Ontology and the lexicon'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          ,
          <fpage>269</fpage>
          -
          <lpage>292</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>J.</given-names>
            <surname>Krogstie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.I.</given-names>
            <surname>Lindland</surname>
          </string-name>
          , and G. Sindre, '
          <article-title>Defining quality aspects for conceptual models'</article-title>
          ,
          <source>in Proc. of the IFIP8.1 Working Conference on Information Systems Concepts</source>
          :
          <article-title>Towards a Consolidation of Views (ISCO3), (</article-title>
          <year>1995</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>A.</given-names>
            <surname>Lozano-Tello</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          , '
          <article-title>Ontometric: A method to choose the appropriate ontology'</article-title>
          ,
          <source>Journal of Database Management</source>
          ,
          <volume>15</volume>
          (
          <issue>2</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          , (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>N. Ben</given-names>
            <surname>Mustapha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. Baazaoui</given-names>
            <surname>Zghal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.A.</given-names>
            <surname>Aufaure</surname>
          </string-name>
          , and
          <string-name>
            <given-names>H.</given-names>
            <surname>Ben Ghezala</surname>
          </string-name>
          , '
          <article-title>Enhancing semantic search using case-based modular ontology'</article-title>
          ,
          <source>in Proc. of the 2010 ACM Symposium on Applied Computing</source>
          , pp.
          <fpage>1438</fpage>
          -
          <lpage>1439</lpage>
          , (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>L.</given-names>
            <surname>Obrst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Ashpole</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Ceusters</surname>
          </string-name>
          , I. Mani,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ray</surname>
          </string-name>
          , and
          <string-name>
            <given-names>B.</given-names>
            <surname>Smith</surname>
          </string-name>
          , '
          <article-title>The evaluation of ontologies: toward improved semantic interoperability', in SemanticWeb: Revolutionizing Knowledge Discovery in the Life Sciences</article-title>
          , ed.,
          <string-name>
            <surname>K.-H. Cheung C. J. O. Baker</surname>
          </string-name>
          ,
          <volume>139</volume>
          -
          <fpage>158</fpage>
          , Springer, (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>J.D.</given-names>
            <surname>Osborne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Flatow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Holko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.M.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.A.</given-names>
            <surname>Kibbe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.I.</given-names>
            <surname>Danila</surname>
          </string-name>
          , G. Feng, and
          <string-name>
            <given-names>R. L.</given-names>
            <surname>Chisholm</surname>
          </string-name>
          , '
          <article-title>Annotating the human genome with disease ontology'</article-title>
          ,
          <source>BMC Genomics</source>
          ,
          <volume>10</volume>
          ,
          <fpage>63</fpage>
          -
          <lpage>68</lpage>
          , (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Suarez-Figueroa</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          , '
          <article-title>Common pitfalls in ontology development'</article-title>
          ,
          <source>in Proc. of the Current topics in artificial intelligence (CAEPIA09), and 13th conference on Spanish association for artificial intelligence,</source>
          (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Suarez-Figueroa</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          ,
          <article-title>'A double classification of common pitfalls in ontologies'</article-title>
          ,
          <source>in Proc. of Workshop on Ontology Quality (OntoQual</source>
          <year>2010</year>
          ), Co-located
          <source>with EKAW</source>
          <year>2010</year>
          , (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>C.</given-names>
            <surname>Roussey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Corcho</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L. M. V.</given-names>
            <surname>Blzquez</surname>
          </string-name>
          , '
          <article-title>A catalogue of owl ontology antipatterns'</article-title>
          ,
          <source>in Proc. of the Fifth Int. Conf. on Know. Capture KCAP</source>
          , pp.
          <fpage>205</fpage>
          -
          <lpage>206</lpage>
          , (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>N. H.</given-names>
            <surname>Shah</surname>
          </string-name>
          and
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Musen</surname>
          </string-name>
          , '
          <article-title>Ontologies for formal representation of biological systems'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          ,
          <fpage>445</fpage>
          -
          <lpage>462</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>E.</given-names>
            <surname>Simperl</surname>
          </string-name>
          and
          <string-name>
            <surname>Tempich C.</surname>
          </string-name>
          , '
          <article-title>Exploring the economical aspects of ontology engineering'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          ,
          <fpage>445</fpage>
          -
          <lpage>462</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrandecic</surname>
          </string-name>
          , '
          <article-title>Ontology evaluation'</article-title>
          , in Handbook on Ontologies, eds.,
          <string-name>
            <given-names>R.</given-names>
            <surname>Studer</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <source>Int. Handbook on Inf. Syst.</source>
          ,
          <fpage>293</fpage>
          -
          <lpage>314</lpage>
          , Springer,
          <volume>2</volume>
          <fpage>edn</fpage>
          ., (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>