<!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>Pattern for Re-engineering a Classification Scheme, Which Follows the Adjacency List Data Model, to a Taxonomy</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Boris Villaz´on-Terrazas</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mari Carmen Sua´rez-Figueroa</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Asuncio´n Go´mez-P´erez</string-name>
          <email>asun@fi.upm.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ontology Engineering Group, Departamento de Inteligencia Artificial, Facultad de Inform ́atica, Universidad Polit ́ecnica de Madrid</institution>
          ,
          <addr-line>Spain WWW home page:</addr-line>
        </aff>
      </contrib-group>
      <fpage>116</fpage>
      <lpage>119</lpage>
      <abstract>
        <p>This pattern for re-engineering non-ontological resources (PR-NOR) fits in the Schema Re-engineering Category proposed by [3]. The pattern defines a procedure that transforms the classification scheme components into ontology representational primitives. This pattern comes from the experience of ontology engineers in developing ontologies using classification schemes in several projects (SEEMP1, NeOn2, and Knowledge Web3). The pattern is included in a pool of patterns, which is a key element of our method for re-engineering non-ontological resources into ontologies [2]. The patterns generate the ontologies at a conceptualization level, independent of the ontology implementation language.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <sec id="sec-1-1">
        <title>Problem</title>
        <p>Re-engineering a classification scheme, which follows the adjacency list model, to design a
taxonomy.</p>
        <sec id="sec-1-1-1">
          <title>A non-ontological resource holds a classification</title>
          <p>scheme which follows the adjacency list model. A
classification scheme is a rooted tree of concepts,
in which each concept groups entities by some
particular degree of similarity.</p>
          <p>
            The semantics of the hierarchical relation between
parents and children concepts may vary depending
of the context. The adjacency list data model [
            <xref ref-type="bibr" rid="ref1">1</xref>
            ]
for hierarchical classifications proposes to create
an entity which holds a list of items with a linking
column associated to their parent items.
1 http://www.seemp.org
2 http://www.neon-project.org
3 http://knowledgeweb.semanticweb.org
The semantics of the relation between parent and children items are subClassOf.
There is not multi-inheritance nor cyclic relations.
          </p>
        </sec>
      </sec>
      <sec id="sec-1-2">
        <title>Ontology Generated</title>
        <sec id="sec-1-2-1">
          <title>The ontology generated will be based on the tax</title>
          <p>
            onomy architectural pattern (AP-TX-01) [
            <xref ref-type="bibr" rid="ref4">4</xref>
            ].
          </p>
          <p>Each category in the classification scheme is
mapped to a class, and the semantics of the
relationship between children and parent categories
are mapped to subClassOf relations.
Suppose that someone wants to build an ontology based on the water areas classification published
by FAO. This classification scheme follows the adjacency list data model.</p>
        </sec>
        <sec id="sec-1-2-2">
          <title>The FAO classification for water areas groups</title>
          <p>them according to some different criteria as
environment, statistics, and jurisdiction, among
others. This classification scheme is available at
http://www.fao.org/figis/servlet/RefServlet
1. Create the Water area class.
2. Create the Environmental area class, and set
up the subClassOf relation between the
Environmental area class and the Water area
class.
2.1. Create the Inland/marine class, and
set up the subClassOf relation
between the Inland/marine class and the
Environmental area class.
2.2. Create the Ocean class, and set up the
subClassOf relation between the Ocean
class and the Environmental area class.
2.3. Create the North/South/Equatorial
class, and set up the
subClassOf relation between the
North/South/Equatorial class and
the Environmental area class.
3. Create the Fishing Statistical area class,
and set up the subClassOf relation between
the Fishing Statistical area class and the
Water area class.
3.1. Create the FAO statistical area class,
and set up the subClassOf relation
between the FAO statistical area class
and the Fishing Statistical area class.
3.2. Create the Areal grid system class, and
set up the subClassOf relation
between the Areal grid system class and
the Fishing Statistical area class.
4. Create the Jurisdiction area class, and set
up the subClassOf relation between the
Jurisdiction area class and the Water area
class.</p>
        </sec>
      </sec>
      <sec id="sec-1-3">
        <title>Related Resources</title>
        <p>
          This pattern is related to the architectural pattern TX-AP-01 [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] for modelling a taxonomy.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Pattern Usage</title>
      <p>This pattern was applied to re-engineer the ISTAT4, geography italian
standard, into a Geography Ontology5, within the context of the SEEMP project.
This standard is a classification scheme which consists of 4 divisions, 20 regions
and 106 provinces. ISTAT is modelled following the adjacency list data model.
Because of the number of divisions, regions and provinces of the ISTAT standard,
it was not practical to create the ontology manually. Therefore, we created an
4 http://www.istat.it/
5 The ontology is available at http://droz.dia.fi.upm.es/hrmontology/
ad-hoc wrapper, implemented in Java, that reads the data from the resource
implementation and automatically creates the corresponding elements of the new
ontology following the suggestion given by the pattern.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Summary and Future Work</title>
      <p>
        We have presented a pattern for transforming a classification scheme, which is
modelled following the adjacency list data model, into a taxonomy. The pattern
is included in a pool of patterns, which is a key element of our method for
re-engineering non-ontological resources into ontologies [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>We plan to develop software libraries within a framework that implement the
transformation process suggested by the pattern. Moreover, we will include
external resources to improve the quality of the resultant ontologies. Finally, we need
to calculate how much effort do we save re-engineering classification schemes
using patterns compared with re-engineering classification schemes without them.
Acknowledgments. This work has been partially supported by the European
Comission projects NeOn(FP6-027595) and SEEMP(FP6-027347), as well as by
an R+D grant from the UPM.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>D.</given-names>
            <surname>Brandon</surname>
          </string-name>
          .
          <article-title>Recursive database structures</article-title>
          .
          <source>Journal of Computing Sciences in Colleges</source>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>A.</given-names>
            <surname>Garc</surname>
          </string-name>
          <article-title>´ıa, A. G´omez-P´erez</article-title>
          , M. C.
          <article-title>Su´arez-</article-title>
          <string-name>
            <surname>Figueroa</surname>
            , and
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Villaz</surname>
          </string-name>
          <article-title>´on-Terrazas. A Pattern Based Approach for Re-engineering Non-Ontological Resources into Ontologies</article-title>
          .
          <source>In Proceedings of the 3rd Asian Semantic Web Conference (ASWC2008)</source>
          . Springer-Verlag,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>V.</given-names>
            <surname>Presutti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gangemi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>David</surname>
          </string-name>
          , G. Aguado de Cea,
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Surez-Figueroa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Montiel-Ponsoda</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Poveda. NeOn Deliverable</surname>
          </string-name>
          <article-title>D2.5.1. A Library of Ontology Design Patterns: reusable solutions for collaborative design of networked ontologies</article-title>
          .
          <source>In NeOn Project</source>
          . http://www.neon-project.org,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>M. C.</surname>
          </string-name>
          <article-title>Su´arez-</article-title>
          <string-name>
            <surname>Figueroa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Brockmans</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>G´omez-P´erez</article-title>
          , J. Lehmann,
          <string-name>
            <given-names>H.</given-names>
            <surname>Lewen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Presutti</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Sabou</surname>
          </string-name>
          .
          <article-title>Neon modelling components</article-title>
          .
          <source>Technical report, NeOn project deliverable D5.1.1</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>