<!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>
      <article-id pub-id-type="urn">nbn:de:0074-596-3</article-id>
      <title-group>
        <article-title>ORES-2010 Ontology Repositories and Editors for the Semantic Web</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Proceedings of the</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>st Workshop on Ontology Repositories</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>Editors for the Semantic Web</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Hersonissos</institution>
          ,
          <addr-line>Crete</addr-line>
          ,
          <country country="GR">Greece</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Mathieu d'Aquin, The Open University, UK Alexander García Castro, Universität Bremen, Germany Christoph Lange, Jacobs University Bremen, Germany Kim Viljanen, Aalto University</institution>
          ,
          <addr-line>Helsinki</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <volume>596</volume>
      <abstract>
        <p>pCaoppeyrrsightby© 2th0e10 fpoarpethrse' inaduivthidoursa.l Copying permitted only for private and aepdcuaibtdloisershm.eidc paunrdposecos.pyTrihgihstedvolubmye itiss</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>10-Jun-2010: submitted by Christoph Lange
11-Jun-2010: published on CEUR-WS.org</p>
      <p>Using extended metadata model OMV and
metrics in OntoLP Portal
Anderson Bestteti, Larissa A. de Freitas, and Renata Vieira</p>
      <p>College Computer, PPGCC,
Ipiranga Avenue, 6681, Partenon, Building 32, Porto Alegre, RS, Brazil
{anderson.bestteti,larissa.freitas,renata.vieira}@pucrs.br
http://www.inf.pucrs.br/~linatural/
1</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>One of the main features of ontologies is to enable humans and machines to
communicate through semantic formalization. With this purpose, ontologies are
used in many areas of Computer Science, such as arti cial intelligence, database
and software engineering. It has been also the key component for information
systems in a increasing variety of domains, well-known examples are the areas
of biology, geography and law.</p>
      <p>The Semantic Web Project contributed for popularization of ontology as an
artifact to build the knowledge representation, shared and reused. With the reuse
of ontologies costs can be reduced, mainly in development phase.</p>
      <p>
        As presented in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], the reuse of ontologies can be seen from two main points:
one is to create, extend, specialize and adapt an ontology to build a new one;
the other is to combine di erent ontologies in a single one.
      </p>
      <p>
        A rst problem for reuse is ontology search. Usually, repositories o er poor
navigation interfaces [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The lack of good quality documentation about available
ontologies also contributes to this di culty. The Metadata models that describe
ontologies have been proposed to deal with these problems[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The use of a
standard vocabulary for ontologies is understood as a basic requisite for a good
description of ontologies on the Web.
      </p>
      <p>In this paper we extend and evaluate the previously proposed OMV
metadata model through its application to a portal for Portuguese ontologies. The
motivation is to help users searching for ontologies and ontology research related
resources.</p>
      <p>The paper is organized as follows: in Section 2 we present our extension which
we call OMV-R; in Section 3 we describe a set of ontology metrics that we use
in the description of the ontologies in our portal; in Section 4 we discuss the
evaluation of the model; nally, in Section 5 we show the conclusion and future
works.
2</p>
    </sec>
    <sec id="sec-3">
      <title>The extended metadata model OMV-R</title>
      <p>Our extension of the OMV model and its application to a portal aims to assist
users in the process of nding out ontologies for reuse.</p>
      <p>
        The original model proposed by [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] does not include information about
ontology evaluation and evolution. We included those elements in the model and
we also propose more elaborated ways for describing ontology metrics.
      </p>
      <p>
        According to [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], metrics are useful to help evaluate ontologies during the
build and application phase, enabling a quick and simple understanding about
what are being modeled through these structures and facilitating the control of
its future evolution. This also holds for ontology reuse.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] a study is performed about the maturity of the current process,
methodologies and tools focused on ontology reuse. Their strengths and
requirements are identi ed.
      </p>
      <p>
        Speci cally on the evaluation of ontologies, [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] presents a methodology called
Requirements-Oriented Methodology for Evaluation Ontologies (ROMEO). This
methodology propose a set of criteria for ontology evaluation. Inspired by these
previous works, we considered that ontology evaluation is another important
feature in the ontology selection process.
      </p>
      <p>As OMV does not provide such information so important to enable reuse, we
extended it with new classes as shown in Figure 1.
2.1</p>
      <p>Description of the new classes, properties and relations
This section will present the classes, properties and relations such as were added
to metadata model OMV.</p>
      <p>OntologyEvaluation Class: this class represents the evaluation of an ontology.
The properties of this class are:
{ evaluationComments: free text that can be used to comment the evaluation
criteria;
{ evaluationDate: date when the evaluation was made;
{ evaluationValue: value assigned to evaluation criteria.</p>
      <p>
        EvaluationCriteria Class: this class represents the evaluation criteria used
to evaluate the ontology. In our implemented model, this class has an evaluation
criteria set as discussed in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. The properties of this class are:
{ criteriaQuestion: question describing the evaluation criteria;
{ criteriaType: de ne whether a question accept a textual or numeric answer.
Metric Class: this class represents metrics. Such metrics can be used to score
an ontology, assigning a quantitative value, in order to assist users to select
ontologies. In OMV-R there are 20 implemented metrics, which will be discussed
in the next subsection. The properties of this class are:
{ name: metric name;
{ usages: free text to describe and guide the user how to use the metric as well
how the metric results may be interpreted.
      </p>
      <p>OntologyMetric Class: this class represents instances of the calculated
metrics of an ontology. One or more metrics may be assigned to an ontology, they
can help users to select ontologies on the basis of di erent points of view. The
properties of this class are:
{ comments: free text to give more information about a metric;
{ creationDate: date when the metric was calculated;
{ value: value assigned to a metric.
Project Class: this class represents research or commercial projects that use a
given ontology or a set of them. The properties of this class are:
{ creationDate: date of the project's beginning;
{ description: free text to describe the project's objectives and artifacts
produced by them;
{ name: the project's name.</p>
      <p>Relations: here we present the relations among these new classes.
{ evaluatedOntology: relation between ontologies with their respective ratings;
{ isBasedOn: reference to another ontology which was used in its construction,
this reference allows to identify the reuse level that one ontology has, based
on the quantity of references;
{ hasEvaluator: reference to a research group or enterprise responsible by
ontology evaluation;
{ evaluationCriteria: reference to an evaluation criteria associated to an
ontology;
{ hasSponsor: reference to the institution sponsoring the project;
{ usedByProject: reference to the project that uses an ontology;
{ hasCreator: reference to the research group or institution that has developed
the metric;
{ usedMetric: reference to the metric assigned to a given ontology.</p>
      <p>
        From the adaptation made, the OMV-R supports now the ontology
evaluation description according to the methodologies proposed by [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] and
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Another contribution is to allow OMV-R to store new metrics whenever
is needed. These metrics may be used to evaluate an ontology over di erent
points of view. Finally, it is expected that the extended model OMV-R provides
a greater exibility in the search of ontologies, as it o ers to users additional
information about reuse.
      </p>
      <p>In the next section we described the set of implemented metrics.
3</p>
    </sec>
    <sec id="sec-4">
      <title>Implemented Ontology Metrics</title>
      <p>
        The model has been extended to accommodate a more elaborated description
through metrics. In our application of the model we have implemented ways of
calculating a set of metrics to describe the ontologies in the repository. The choice
of metrics were based on a detailed systematic review of the literature of ontology
metrics. Following the systematic review their presentation was standardized in
a common representation formalism, where C is used for classes, CS is used for
set classes with subclasses, CR is used for set of root classes, CL is used for set
of leaf classes, HC (CRj ; CLi) for hierarchy of classes where CRj is a subclass
of CLi, prop for the function that relates the classes in a non-hierarchy and att
for the function that relates classes with literal values (string ), I for instances
and inst(C) for the function of instantiated classes [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        Number of root classes [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
      </p>
      <sec id="sec-4-1">
        <title>Number of leaf classes [15] [1] [14]</title>
        <p>
          Number of classes [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>Number of properties (attributes) [1]</title>
      </sec>
      <sec id="sec-4-3">
        <title>Number of properties (relations) [1]</title>
        <p>Besides, we use Count for count, SuperClass for superclass function, SubClass
for subclass function, M ax for maximum (M axDepth and M axW idth), Depth
for depth, W idth for width, Avg for average (AvgDepth, AvgM axAvg, AvgW idth,
AvgAttClass, AvgP ropClass, AvgP Class, AvgCRC, AvgCRCL, AvgCIC,
AvgIC) and StdDev for standard deviation (StdDevIC).</p>
        <p>All chosen metrics presented result in numeric values and their calculation
could be implemented. The metrics were separated in three groups as follows:
1. Group 1 is simply the count of the basic elements of an ontology (classes,
properties, and instances), metrics 1 to 7.</p>
        <p>Count(CR) = jCRj
where: jCRj is the set cardinality</p>
        <p>Count(CL) = jCLj
where: jCLj is the set cardinality</p>
        <p>Count(C) = jCj
where: jCj is the set cardinality</p>
        <p>Count(att) = jattj
where: jattj is the set cardinality</p>
        <p>
          Count(prop) = jpropj
where: jpropj is the set cardinality
Number of properties [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
        </p>
      </sec>
      <sec id="sec-4-4">
        <title>Number of instances</title>
        <p>Count(att) + Count(prop)</p>
        <p>
          Count(I) = jIj
where: jIj is the set cardinality
2. Group 2 represents the depth and width of the structure, metrics 8 to 12.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Maximum depth [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
Average depth [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]
the major ontology depth counted from each
        </p>
        <p>root class (CRj )
M axDepth(HC ) =</p>
        <p>AvgDepth(HC ) =
the average ontology depth added from all root classes (CR)</p>
        <p>
          by counted from each leaf class (CLi)
Average maximum depth to average depth [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
        </p>
        <p>
          AvgM axAvg(HC ) = M axDepth(HC )=AvgDepth(HC )
Maximum width [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]
        </p>
      </sec>
      <sec id="sec-4-5">
        <title>Average width [1]</title>
        <p>M axW idth(HC ) =
the major ontology width counted from each
class with subclass (CSk)</p>
        <p>AvgW idth(HC ) =
the average ontology width added from all classes with subclasses (CS)
by counted from each class with subclass (CSk)
3. Group 3 represents the calculation of simple averages and standard deviation
from combinations of the basic elements, metrics 13 to 20.</p>
        <p>
          Average number of properties (attributes) to total number of classes [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]
        </p>
        <p>
          AvgAttClass = Count(att)=Count(C)
Average number of properties (relations) to total number of classes [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
        </p>
        <p>
          AvgP ropClass = Count(prop)=Count(C)
Average number of properties to total number of classes [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]
(8)
(9)
(10)
(11)
(12)
(13)
(14)
        </p>
        <p>
          AvgP Class = (Count(att) + Count(prop))=Count(C)
Average number of leaf classes to total number of classes [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]
Average number of leaf classes to number of classes root [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]
        </p>
        <p>AvgCRC = Count(CR)=Count(C)</p>
        <p>
          AvgCRCL = Count(CR)=Count(CL)
Average number of classes populated to total number of classes [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]
Average of the total number of instances to total number of classes
AvgCIC(HC ) = Count(inst(C))=Count(C)
        </p>
        <p>
          AvgIC(HC ) = Count(I)=Count(C)
Standard deviation of the total number of instances to total number of
classes [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]
(15)
(16)
(17)
(18)
(19)
StdDevIC(HC ) = qX(Count(inst(C))
AvgIC(HC ))2=Count(I)
(20)
        </p>
        <p>The AvgIC(HC ) and Count(I) were calculated and used in StdDevIC(HC ).
It is not directly referenced in papers obtained in the systematic review.</p>
        <p>Note that OMV documentation refer to four metrics only: number of class,
number of property, number of individuals and number of axioms.
4</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Application evaluation</title>
      <p>OntoLP Portal1 o ers ontologies and ontology research related resources, with
special preference to ontologies written in Portuguese language. At Home link
the objectives of the portal are shown, whilst the link Resources list ontologies
and related works. The link About contains information referring to the research
group involved in this project. Through the Contact link others research groups
in the eld can send their works and suggestions. Finally, the link Links shows
researches groups that have been colaborated directly or indirectly with the
OntoLP Portal as well as events related with ontology research.</p>
      <p>An ontology search was performed just to build the repository. We conducted
searches in Google 2 specifying the type of query (e.g. \ eld letype: owl"), in
Swoogle 3, in OntoSelect 4 and pages of projects and research groups
working with the subject. Also we announce the OntoLP portal in several Brazilian
1 http://www.inf.pucrs.br/~ ontolp/index.php
2 http://www.google.com.br/
3 http://swoogle . umbc.edu /
4 http://olp.dfki.de/ontoselect/
research lists and organized an event with the intention of receiving these
resources.</p>
      <p>As a result we nd resources in di erent domains such as ecology,
nanotechnology, art, curriculum, emotion, privacy, network of scienti c knowledge,
smartphones, music and stimulus equivalence. Today the OntoLP portal has 25
ontologies. Note that the currently portal does not use any advanced structure, such
as a metamodel, to store the descriptions of ontologies. Such descriptions were
manually built and hard coded in HTML, which are stored in the le system
on the Web server. In order to improve the current services of OntoLP portal,
a new prototype application was developed that uses the OMV-R to keep the
descriptions of ontologies. The next subsection will take a look deeper how this
new version of OntoLP portal was developed.
4.1</p>
      <p>Infrastructure
A tool has been developed in order to automate the receiving process. This
tool reads the ontology and includes information about ontology metrics. It has
also another interface for the inclusion of other metadata, to be used in the
description of ontologies in the OntoLP Portal, that corresponds with instances
of OMV-R. Ontologies are thus received through a submission form. Figure 2
shows the ow of information during the ontology reception process.</p>
      <p>Besides the ability to create OMV-R's instances, the tool o ers others
services such as information retrieval of the ontologies, ability to create and retrieve
ontology evaluation instances as well as the metrics values for each OMV-R
instance that represents a description of the ontology. The recovery of information
from ontologies is made through a set of methods that read data from OMV-R
and then, record the information on a XML le wich will be used by
presentation layer of the prototype application. Therefore, this XML le works like a
communication area between OMV-R ontology and end user interface.</p>
      <p>Finally, the tool uses the Jena's SPARQL query engine to implement the
advanced search service in the OntoLP Portal. The query is performed on the
OMV-R, speci cally over the Ontology class to retrieve all the ontologies that
match the user's lter.
We applied two questionnaires to evaluate the adaptations made to the portal
which follows the new proposed model.</p>
      <p>The goal of the rst questionnaire was to evaluate the opinion of a users'
group, researchers and engineering of ontologies about the usefulness of metrics
in speci c repositories, in this case in OntoLP portal.</p>
      <p>In the rst phase, the questionnaire (in print format) was applied to people
in national workshop about ontologies. In the nal phase the questionnaire (in
digital format) was applied to visitors of the OntoLP portal. The questionnaire
was available for a month (December 6, 2009 until January 6, 2010).</p>
      <p>The nal result showed that 76 % respondents have developed ontologies, 83
% have searched for ontologies written in English, Portuguese, or Spanish. The
language most cited was English and Portuguese was in the second position. The
sample consisted of 14 PhD, 11 MSc and 5 senior experts. At last, ontologies in
many domains were mentioned.</p>
      <p>We observed that there was no preference regarding groups 1, 2 and 3, their
usefulness was better appreciation as a whole. Most people consider the use of
metrics important for the portal.</p>
      <p>The respondents commented about the lack of more speci c metrics (total
number of relations' types, where such relations would be \ is-a", \ part-of")
and about the lack of the presentation in percentages the results (percentage of
classes that did not have superclasses). These suggestions will be considered as
future work.</p>
      <p>The goal of the second questionnaire was to get impressions about the new
services of the OntoLP Portal such as description and retrieval of ontologies
based on the OMV-R metadata.</p>
      <p>Here, the sample was formed by 19 respondents. They were instructed to visit
the OntoLP Portal and to evaluate the new services such as ontology submission
and search. Next, the respondents were oriented to compare the services of the
current version of the portal. When asked whether these new services have eased
the ontology search process, about 58% of respondents agreed, 26% remained
neutral and about 15% disagreed.</p>
      <p>Despite some disagreement about how easy is to locate ontologies in the
new OntoLP Portal, about 95% of respondents believe that the new ontology
submission and search services are better than the original one.</p>
      <p>In addition to the two close questions about the satisfaction and improvement
about the ontology search services, the respondents were conducted to comment
referring to other information that could be added to the metadata model
OMVR. About 25% of respondents have contributed with suggestions; 32 % said that
the new set of the model's information was su cient or reasonable; and 36 %
didn't answer.</p>
      <p>The suggestions are related mainly with the ontology domain, and this
information is the best way to locate ontologies. Other respondent claimed that the
new portal should o er information about the relationship among ontologies, as
evidence: \At rst glance I would say that at some point we will need a hierarchy
of ontologies (when there are more than 20 or 30 ontologies) and some mechanism
to relate them (meta-ontology)". Notice tha both questionaries can by accessed
through the following links: http://www.inf.pucrs.br/~ontolp/questionario.php
(for metric's questions) and http://www.ontolp.com.br/questionarioOMVR.php
(for metamodel and prototype application's questions)
5</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion and Future Work</title>
      <p>This paper presented an extended model based on OMV, which is called
OMVR. The new model includes key ontology metrics identi ed through literature
review. The model was applied to OntoLP portal which aims to maintain and
distribute Portuguese resources. The model is used for the description of the
resources, and was also useful as a basis for new search and retrieval services.
Finally, this paper discussed the surveys performed to evaluate the model, the
new portal and the use of metrics, where the objective was to assess with the
community the bene ts and contributions of the model for ontology description
and location as well as the process of reuse of such resources.</p>
      <p>We hope to have contributed with ideas for describing ontologies that can
be included in previously proposed standards. We have also shown its usefulness
for the development of software that can help researchers and engineers to nd
and inspect available ontologies in an organized and e cient way.</p>
      <p>Potential future work are: (i ) adaptation of the OMV-R API to work with
the OMV-R model stored in commercial database as well as free ones; (ii ) the
development of Web services for distributed applications; (iii ) improving the
advanced search interface of the new OntoLP Portal, in order to allow users query
any property of the metamodel through free-text. Nowadays only three
properties have been added to advanced search interface; (iv ) building mechanisms for
visualization of ontologies described in the metadata model OMV-R.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Cross</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pal</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Metrics for ontologies</article-title>
          .
          <source>In: Annual Meeting of the North American Fuzzy Information Processing Society</source>
          , pp.
          <fpage>448</fpage>
          -
          <lpage>453</lpage>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ding</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Finin</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Joshi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Cost</surname>
            ,
            <given-names>R. S.</given-names>
          </string-name>
          <string-name>
            <surname>Peng</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Reddivari</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Doshi</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          <string-name>
            <surname>Sachs</surname>
          </string-name>
          , J.:
          <article-title>Swoogle: A Semantic Web Search and Metadata Engine</article-title>
          .
          <source>In: Proceedings of the thirteenth ACM international conference on Information and knowledge management</source>
          , pp.
          <fpage>652</fpage>
          -
          <lpage>659</lpage>
          , (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Fensel</surname>
          </string-name>
          , D., van
          <string-name>
            <surname>Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : OIL:
          <article-title>An Ontology Infrastructure for the Semantic Web</article-title>
          .
          <source>IEEE Intelligent Systems, v. 16</source>
          , pp.
          <fpage>38</fpage>
          -
          <lpage>45</lpage>
          , Mar./Apr., (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Catenacci</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ciaramita</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
          </string-name>
          , J.:
          <article-title>Modelling ontology evaluation and validation</article-title>
          .
          <source>In: The Semantic Web: Research and Applications</source>
          , pp.
          <fpage>140</fpage>
          -
          <lpage>154</lpage>
          , (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Gruber</surname>
            ,
            <given-names>T. R.</given-names>
          </string-name>
          :
          <article-title>Toward principles for the design of ontologies used for knowledge sharing</article-title>
          .
          <source>International Journal of Human Computer Studies</source>
          <volume>43</volume>
          ,
          <fpage>907</fpage>
          -
          <lpage>928</lpage>
          (
          <year>1995</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Hartmann</surname>
          </string-name>
          , J.;
          <string-name>
            <surname>Bontas</surname>
            ,
            <given-names>E. P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Palma</surname>
            ,
            <given-names>R.; Gmez</given-names>
          </string-name>
          <string-name>
            <surname>Prez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Demo - Design Environment for Metadata Ontologies</article-title>
          .
          <source>In: The Semantic Web: Research and Applications</source>
          , pp.
          <fpage>427</fpage>
          -
          <lpage>441</lpage>
          , (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lozano-Tello</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gmez-Prez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Ontometric: A method to choose the appropriate ontology</article-title>
          .
          <source>Journal of Database Management</source>
          <volume>15</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          (
          <year>2004</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Palma</surname>
            , R.; Hartmann,
            <given-names>J.</given-names>
          </string-name>
          ; Haase,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <source>OMV Report 2</source>
          .4
          <article-title>- Ontology Metadata Vocabulary for the Semantic Web</article-title>
          .
          <source>Technical Report</source>
          , p.
          <fpage>94</fpage>
          , (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Pinto</surname>
          </string-name>
          ,H. S,
          <string-name>
            <surname>Martins</surname>
            <given-names>J. P.</given-names>
          </string-name>
          :
          <article-title>Reusing Ontologies</article-title>
          . In: AAAI 2000 Spring Symposium Series, Workshop on Bringing Knowledge to Business Processes, pp.
          <fpage>77</fpage>
          -
          <lpage>84</lpage>
          , (
          <year>2000</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Simperl</surname>
          </string-name>
          , E.:
          <article-title>Reusing Ontologies on the Semantic Web: A Feasibility Study</article-title>
          .
          <source>Data and Knowledge Engineering</source>
          , v.
          <volume>68</volume>
          -
          <issue>10</issue>
          , pp.
          <fpage>905</fpage>
          -
          <lpage>925</lpage>
          , October, (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>M. K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Welty</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D. L.</given-names>
          </string-name>
          :
          <source>OWL Web Ontology Language Guide: W3C Recommendation 10 February</source>
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Tartir</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arpinar</surname>
            ,
            <given-names>I.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moore</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheth</surname>
            ,
            <given-names>A. P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aleman-Meza</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>OntoQA: Metric-based ontology quality analysis?</article-title>
          .
          <source>In: IEEE Workshop on Knowledge Acquisition from Distributed</source>
          , Autonomous,
          <source>Semantically Heterogeneous Data and Knowledge Sources</source>
          , p.
          <fpage>9</fpage>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Tartir</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arpinar</surname>
            ,
            <given-names>I.B.</given-names>
          </string-name>
          :
          <article-title>Ontology Evaluation and Ranking using OntoQA</article-title>
          .
          <source>In: First IEEE International Conference on Semantic Computing</source>
          , pp.
          <fpage>185</fpage>
          -
          <lpage>192</lpage>
          , (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ye</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Evaluation Metrics for Ontology Complexity and Evolution Analysis</article-title>
          . In: IEEE International Conference on e-Business Engineering, pp.
          <fpage>162</fpage>
          -
          <lpage>170</lpage>
          , (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Yao</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orme</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Etzkorn</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Cohesion metrics for ontology design and application</article-title>
          .
          <source>Journal of Computer Science</source>
          <volume>1</volume>
          ,
          <fpage>107</fpage>
          -
          <lpage>113</lpage>
          (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Thom</surname>
            ,
            <given-names>J. A.</given-names>
          </string-name>
          <string-name>
            <surname>Tam</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Requirements-Oriented Methodology for Evaluating Ontologies</article-title>
          .
          <source>Information Systems</source>
          , v.
          <fpage>34</fpage>
          -
          <issue>8</issue>
          , pp.
          <fpage>766</fpage>
          -
          <lpage>791</lpage>
          , December, (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>