<!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>A Formal Ontological Framework for Semantic Interoperability in the Fishery Domain</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Aldo Gangemi</string-name>
          <email>gangemi@ip.rm.cnr.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Frehiwot Fisseha</string-name>
          <email>Frehiwot.Fisseha@fao.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ian Pettman</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Domenico M. Pisanelli</string-name>
          <email>pisanelli@ip.rm.cnr.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marc Taconet</string-name>
          <email>Marc.Taconet@fao.org</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Johannes Keizer</string-name>
          <email>Johannes.Keizer@fao.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>FAO-GILW</institution>
          ,
          <addr-line>Rome</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>FIDI, FAO</institution>
          ,
          <addr-line>Rome</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Institute of Psychology, CNR (National Research Council)</institution>
          ,
          <addr-line>Rome</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper outlines a project (involving FAO, SIFAR, and CNR) aimed at building an ontology in the fishery domain. The ontology will support semantic interoperability among existing fishery information systems and will enhance information extraction and text marking, envisaging a fishery semantic web. The ontology is being built through the conceptual integration and merging of existing fishery terminologies, thesauri, reference tables, and topic trees. Integration and merging are shown to benefit from the methods and tools of formal ontology.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 INTRODUCTION</title>
      <p>1.1</p>
      <sec id="sec-1-1">
        <title>The general problem</title>
        <p>Specialized distributed systems are the reality of today’s information systems
architecture. Developing specialized information systems/resources in response to
specific user needs and/or area of specialization has its own advantage in fulfilling the
information needs of target users. However, such systems usually use different
knowledge organization tools such as vocabularies, taxonomies and classification
systems to manage and organize information. Although the practice of using
knowledge organization tools to support document tagging (thesaurus-based
indexing) and information retrieval (thesaurus-based search) improves the functions of
a particular information system, it is leading to the problem of integrating
information from different sources due to lack of semantic interoperability that
exists among knowledge organization tools used in different information systems.</p>
        <p>The different fishery information systems and portals that provide access to
fishery information resources are one example of such scenario. This paper
demonstrates the proposed solution to solve the problem of information integration in
fishery information systems. The proposal shows how a fishery ontology that
integrates the different thesauri and taxonomies in the fishery domain could help in
integrating information from different sources be it for a simple one-access portal or a
sophisticated web services application.</p>
      </sec>
      <sec id="sec-1-2">
        <title>1.2 The local scenario</title>
        <p>Fishery Ontology Service (FOS) is a key feature of the Enhanced Online
Multilingual Fishery Thesaurus, a project aimed at information integration in the
fishery domain. It undertakes the problem of accessing and/or integrating fishery
information that is already partly accessible from dedicated portals and other web
services.</p>
        <p>
          The organisations involved in the project are: FAO Fisheries Department
(FIGIS), ASFA Secretariat, FAO WAICENT (GIL), the oneFish service of SIFAR,
and the Ontology and Conceptual Modelling Group at ISTC-CNR. The systems to be
integrated are: the "reference tables" underlying the FIGIS portal [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], the ASFA online
thesaurus [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], the fishery part of the AGROVOC online thesaurus [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], and the
oneFish community directory [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ].
        </p>
        <p>
          The official task of the project is "to achieve better indexing and retrieval of
information, and increased interaction and knowledge sharing within the fishery
community". The focus is therefore on tasks (indexing, retrieval, and sharing of
mainly documentary resources) that involve recognising an internal structure in the
content of texts (documents, web sites, etc.). Within the semantic web community
and the intelligent information integration research area (cf. [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] and [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]), it is
becoming widely accepted that content capturing, integration, and management
require the development of detailed, formal ontologies.
        </p>
        <p>In this paper we sketch an outline of the FOS development and some hint of
the functionalities that it carries out.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2 ONTOLOGY INTEGRATION AND MERGING</title>
      <sec id="sec-2-1">
        <title>2.1 Heterogeneous systems give heterogenous interpretations</title>
        <p>An example of how formal ontologies can be relevant for fishery information
services is shown by the information that someone could get if interested in
aquaculture.</p>
        <p>In fact, beyond simple keyword-based searching, searches based on tagged
content or sophisticated natural-language techniques require some conceptual
structuring of the linguistic content of texts. The four systems concerned by this
project provide this structure in very different ways and with different conceptual
AQUACULTURE
uf aquiculture
uf mariculture
uf sea ranching
NT1 fish culture</p>
        <p>NT2 fish feeding
NT1 frog culture
rt agripisciculture
rt aquaculture equipment
Fr aquaculture</p>
        <p>Es acuicultura
AQUACULTURE
uf Aquaculture industry
uf Aquatic agriculture
uf Aquiculture
NT Brackishwater aquaculture
NT Freshwater aquaculture
NT Marine aquaculture
rt Aquaculture development
rt Aquaculture economics
rt Aquaculture engineering
rt Aquaculture facilities</p>
        <p>The AGROVOC thesaurus seems to frame aquaculture from the viewpoint of
techniques and species. On the other hand, the ASFA aquaculture hierarchy is
substantially different:
’textures’. For example, the AGROVOC and ASFA thesauri put aquaculture in the
context of different thesaurus hierarchies; an excerpt of the AGROVOC result is (uf
means used for, NT means narrower than; rt means related term, Fr and Es are the
corresponding French and Spanish terms):</p>
        <p>Actually this hierarchy seems to stress the environment and disciplines related to
aquaculture.</p>
        <p>A different resource is constituted by the so-called reference tables in FIGIS
system; the only reference table mentioning aquaculture puts it into another context
(taxonomical species):</p>
        <p>Biological entity</p>
        <p>Taxonomic entity</p>
        <p>Major group
Order
Family
Genus
Species</p>
        <p>Capture species (filter)
Aquaculture species (filter)
Production species (filter)</p>
        <p>Tuna atlas spec</p>
        <p>The last resource examined is oneFish directory, which returns the following
context (related to economics and planning):</p>
        <p>SUBJECT</p>
        <p>Aquaculture</p>
        <p>Aquaculture development</p>
        <p>Aquaculture economics @</p>
        <p>Aquaculture planning</p>
        <p>With such different interpretations of aquaculture, we can reasonably expect
different search and indexing results. Nevertheless, our approach to information
integration and ontology building is not that of creating a homogeneous system in
the sense of a reduced freedom of interpretation, but in the sense of navigating
alternative interpretations, querying alternative systems, and conceiving alternative
contexts of use.</p>
        <p>To do this, we require a comprehensive set of ontologies that are designed in
a way that admits the existence of many possible pathways among concepts under a
common conceptual framework. This framework should reuse domain-independent
components, be flexible enough, and be focused on the main reasoning schemas for
the domain at hand.</p>
        <p>Domain-independent, upper ontologies should characterise all the general
notions needed to talk about economics, biological species, fish production
techniques; for example: parts, agents, attribute, aggregates, activities, plans,
devices, species, regions of space or time, etc. While the so-called core ontologies
should characterise the main conceptual habits (schemas) that fishery people actually
use, namely that certain plans govern certain activities involving certain devices
applied to the capturing or production of a certain fish species in certain areas of water
regions, etc.</p>
        <p>
          Upper and core ontologies [
          <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
          ] provide the framework to integrate in a
meaningful and intersubjective way different views on the same domain, such as
those represented by the queries that can be done to an information system.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 Methods applied to develop the integrated fishery ontology</title>
        <p>
          Once made clear that different fishery information systems provide different
views on the domain, we directly enter the paradigm of ontology integration, namely
the integration of schemas that are arbitrary logical theories, and hence can have
multiple models (as opposed to database schemas that have only one model) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. As a
matter of fact, thesauri, topic trees and reference tables used in the systems to be
integrated could be considered as informal schemas conceived to query semi-formal or
informal databases such as texts and tagged documents.
        </p>
        <p>In order to benefit from the ontology integration framework, we must
transform informal schemas into formal ones. In other words, thesauri and other
terminology management resources must be transformed into (formal) ontologies.</p>
        <p>
          To perform this task, we apply the techniques of three methodologies:
OntoClean [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], ONIONS [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], and OnTopic [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
        </p>
        <p>
          The first one contains principles for building and using upper ontologies for
core and domain ontology analysis, revision, and development. In its current form,
OntoClean also features an axiomatised domain-independent top-level of formal
criteria, concepts and relations (Figure 3) [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
        <p>ONIONS is a set of methods for enhancing the informal data of
terminological resources to the status of formal ontological data types. Some methods
are aimed at reusing the structure of hierarchies (e.g., BT/NT relations, subtopic
relation, etc.), the additional relations that can be found (e.g., RT relations), and at
analysing the compositional structure of terms in order to capture new relations and
definitional elements. Other methods concern the management of semantic
mismatches between alternative or overlapping ontologies, and the exploitation of
systematic polysemy to discover relevant domain conceptual structures.</p>
        <p>OnTopic is about creating dependencies between topic hierarchies and
ontologies. It contains methods for deriving the elements of an ontology that describe
a given topic, and methods to build ’active’topics that are defined according to the
dependency of any individual, concept, or relation in an ontology.</p>
        <p>In Figure 1, a class diagram is shown of the informal and formal data types
taken into account by the forementioned methodologies.</p>
        <p>In section 3.1 the types of (meta)data extracted from the resources are
described. In the subsequent sections the (meta)data types obtained from the
transformation of resources into a merged ontology are also described.</p>
        <p>We briefly describe:
• the resources that are integrated
• how the Integrated Fishery Ontology (IFO) is being built
• a mediation architecture to interface the fishery ontology service with the
source information systems.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>OUTLINE OF THE FOS PROJECT</title>
      <sec id="sec-3-1">
        <title>3.1 Resources</title>
        <p>The following resources have been singled out from the fishery information
systems considered in the project:</p>
        <p>the oneFish topic trees (about 1,800 topics), made up of hierarchical topics
with brief summaries, identity codes and attached knowledge objects (documents,
web sites, various metadata). The hierarchy (average depth: 3) is ordered by (at least)
two different relations: subtopic, and intersection between topics, the last being
notated with @, similarly to relations found in known subject directories like
DMOZ. There is one ’backbone’ tree consisting of five disjoint categories, called
worldviews (subjects, ecosystem, geography, species, administration) and one
worldview (stakeholder), maintained by the users of the community, containing own
topics and topics that are also contained in the first four other categories (Figure 5).
Alternative trees contain new ’conjunct’ topics deriving from theintersection of topics
belonging to different categories.</p>
        <sec id="sec-3-1-1">
          <title>Resource for ontology development</title>
        </sec>
        <sec id="sec-3-1-2">
          <title>Processed namespace</title>
        </sec>
        <sec id="sec-3-1-3">
          <title>Ontology element</title>
        </sec>
        <sec id="sec-3-1-4">
          <title>Ontological structure</title>
        </sec>
        <sec id="sec-3-1-5">
          <title>Upper ontology</title>
          <p>OntologicalStructure</p>
        </sec>
        <sec id="sec-3-1-6">
          <title>Glossary</title>
          <p>Documentation</p>
        </sec>
        <sec id="sec-3-1-7">
          <title>Thesaurus</title>
          <p>BT,NT,RT informal axioms</p>
        </sec>
        <sec id="sec-3-1-8">
          <title>Informal domain ontology</title>
          <p>InformalAxioms</p>
        </sec>
        <sec id="sec-3-1-9">
          <title>Domain schema (conceptual template)</title>
          <p>(Informal) axioms</p>
        </sec>
        <sec id="sec-3-1-10">
          <title>Fishery resource types::Ontological structure</title>
          <p>as reusable component
n n</p>
          <p>Reusable component from original n</p>
        </sec>
        <sec id="sec-3-1-11">
          <title>Topic tree fragment</title>
        </sec>
        <sec id="sec-3-1-12">
          <title>RT informal axioms</title>
        </sec>
        <sec id="sec-3-1-13">
          <title>Documentation</title>
        </sec>
        <sec id="sec-3-1-14">
          <title>BT/NT hierarchy Informal ontology fragment</title>
          <p>Fig. 1. A class diagram of the source data types taken into account</p>
        </sec>
        <sec id="sec-3-1-15">
          <title>Source</title>
          <p>1
HAS-PART</p>
        </sec>
        <sec id="sec-3-1-16">
          <title>Topic tree</title>
          <p>Inclusion hierarchies
1</p>
          <p>AGROVOC thesaurus (about 500 fishery-related descriptors), with thesaurus
relations (narrower term, related term, used for) among descriptors, lexical relations
among terms, terminological multilingual equivalents, and glosses (scope notes) for
some of them.</p>
          <p>ASFA thesaurus, similar to AGROVOC, but with about 10,000 descriptors.</p>
          <p>FIGIS reference tables, with 100 to 200 top-level concepts, with a max
depth of 4, and about 30,000 ’objects’ (mixed concepts and individuals), relations
(specialised for each top category, but scarcely instantiated) and multilingual support.
There are modules (water areas, continental areas, biological entities, vessels,
commodities, stocks, etc.), also organised by ’views’.</p>
          <p>In Figure 2 a diagram is sketched of the methodology used to extract and
refine the informal data from the fishery information systems. The methodology is
also described in the next sections.</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 Translation and refining of the components for IFO building</title>
        <p>
          The (meta)data from the resources that have been singled out have been
processed, in order to integrate them within a homogeneous environment, and with a
clear assessment of their nature. In the following we list a set of guidelines that have
been followed to translate and refine data components:
• A detailed evaluation of each source (find the schema -explicit or not- underlying
the implementation of source data, then describe each data type both qualitatively
and quantitatively) is performed.
• A language to represent the KB is chosen that hosts the integration activity. A
description logic like DLR [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] is an ideal choice for its compatibility with the
ontology integration framework.
• An ontology server is installed that supports DLR or compatible languages.
• Some data types from the sources (Figure 1) seem appropriate to be included in a
preliminary prototype. The following steps are performed on them:
• Discuss, refine and formalise FIGIS fishery conceptual schemas [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] to build
a preliminary core ontology. Also the upper-level concepts from the source
thesauri should be matched against the FIGIS conceptual schemas. This
results in a resource for core ontology development.
• Translate FIGIS reference tables: taxonomy, individuals, and local relations
(to be transformed into formal axioms). This results in a draft resource for
domain ontology development.
• Reuse oneFish topic trees to design a preliminary architecture for IFO
library. This architecture should match the preliminary core ontology. This
results in a resource for ontology library design.
        </p>
        <p>Documentation translated
entry/ Domain documentation resources defined [al ]
do: Translate resources to common format. Trace origin
exit/ DOC resources formalised</p>
        <p>Lexical sets translated
entry/ Lexical resources defined [all]
do: Translate resources to common format. Trace origin
exit/ Lexicalisation resources formalised</p>
        <p>Domain conceived
exit/ Resources selected</p>
        <p>Resources described
entry/ Domain resources col ected
do: Use a classification scheme from an ontology of resources
exit/ Resources classified
Resource processing packages created
entry/ Resources classified
do: Define activities to be done
exit/ Homogeneous resource set defined</p>
        <p>Reusable components from resources identified
entry/ Homogeneous resource set defined
do: Analyse resource schemas
exit/ Reusable components identified</p>
        <p>Rough list of ontology elements ready
entry/ Homogeneous resource set defined, reusable components identified
do: Collect all namespaces (concepts,relations,individuals,topics) from resources,</p>
        <p>start assigning data types, documentation and terms collected
exit/ Rough namespaces created with flags to resources</p>
        <p>Core ontologies translated
entry/ Core ontology resources defined [FIGIS, top ASFA, top Agrovoc, else]
do: Translate core resources to common format
exit/ Preliminary core ontology formalised</p>
        <p>Domain ontologies translated
entry/ Domain ontology resources defined [FIGIS]
do: Translate resources to common format
exit/ Domain ontology resources formalised</p>
        <p>RT axioms translated
entry/ Domain RT resources defined [ASFA,Agrovoc]
do: Translate resources to common format
exit/ RT resources formalised</p>
        <p>RT resources refined
entry/ RT resources formalised
do: Refine with heuristics based on taxonomies and core ontologies
exit/ Refined subset of RT axioms ready</p>
        <p>Axiomatic resources ready
entry/ Domain ontologies translated, RT axioms refined
do: Prepare integration space of axioms
exit/ Axioms to be integrated</p>
        <p>Topic trees translated
entry/ Topic resources defined [oneFish]
do: Translate resources to common format
exit/ Preliminary topic trees formalised</p>
        <p>BT/NT hierarchies translated
entry/ Domain BT/NT resources defined [ASFA,Agrovoc]
do: Translate resources to common format
exit/ BT/NT resources formalised</p>
        <p>BT/NT hierarchies refined
entry/ BT/NT resources formalised
do: Refine with heuristics based on core ontologies
exit/ Refined subset of BT/NT hierarchies ready</p>
        <p>Taxonomical resources ready
entry/ Domain ontologies translated, BT/NT hierarchies refined
do: Prepare integration space of taxonomies
exit/ Taxonomies to be integrated</p>
        <p>Topic trees refined
entry/ Preliminary topic trees formalised
do: Refine trees according to set-theoretic principles
exit/ Refined topic trees ready</p>
        <p>Assertional resources ready
entry/ Domain ontologies translated, BT/NT hierarchies refined, RT resources refined,</p>
        <p>DOC and lexicalisation resources formalised
do: Prepare integration space of assertions
exit/ Assertions to be integrated</p>
        <p>List of integratable ontology elements ready
entry/ Taxonomical, axiomatic, and assertional resources ready, refined topic trees ready
do: Create working namespaces with flags to original resources, maintain links between current resources
exit/ Working, interlinked namespaces created with flags to resources</p>
        <p>Fig. 2. A diagram of the methodology used to extract and refine the informal data
•
•
•</p>
        <p>Extract IS_A taxonomies from AGROVOC and ASFA BT/NT (Broader
Term/Narrower Term) hierarchies. Heuristics from upper and core ontologies
can be applied to clean up BT/NT hierarchies, for example, the following
rule can be applied: if a body part descriptor is NT of an organism
descriptor, then this is probably not an IS_A use of NT (probably it is a
part-of relation). This results in resources for core and domain taxonomies
building.</p>
        <p>Expand RT (Related Term) relations from AGROVOC and ASFA. Also
non-IS_A BT/NT hierarchies could be refined (expanded) here. Heuristics can
be applied here as well, for example, if there exists a systematic relation
between to concepts in the core ontology, and there exists a RT relations
between two subconcepts of those concepts, then this is an indication for that
relation to be the refinement of the RT one. This results in resources for core
and domain axioms building.</p>
        <p>Reuse UF (Used For) relations and (multi-)linguistic equivalents from all
resources. Track must be kept of the context from which a linguistic item
has been extracted. This results in resources for ontology lexicalisation.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3 Parallel tasks</title>
        <p>In the following sections we outline the main steps to build the basic
taxonomy, documentation, and architecture for the integrated fishery ontology.
3.3.1 Developing a fishery core ontology (FCO)</p>
        <p>In this step, we pick up uppermost concepts and conceptual (categorisation)
schemas from sources and integrate them with a certified top-level containing
domain-independent concepts, relations and meta-properties. The resources needed for
such a task are:</p>
        <p>
          Upper ontology resources: the OntoClean upper level [
          <xref ref-type="bibr" rid="ref18 ref8">8,18</xref>
          ] (Figure 3) is a
preferential choice for its compatibility with the methodology. For alternatives, see
[
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Moreover, various formal ontologies and standards for relations, and general
lexical repositories like WordNet [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
        </p>
        <p>Core ontology resources: conceptual templates, (selected in the preliminary
phases), relational database schemas, theoretical views on domain topics, domain
standards, etc. An informal fishery core ontology (the FIGIS composite concepts) is
shown in Figure 4.</p>
        <p>In the context of core ontology development, some taxonomical branches
(core concepts) have relevant conceptual integration issues that are being studied by
ontological engineers and domain experts in close collaboration:
•
•
•
biological taxonomies: difficult having a stable framework of reference (in
principle, mapping from local taxonomies to a biological one is feasible, but
in practice it could be not cost effective)
geographic regions: use GIS as a stable framework of reference? geographic
names?
institutions: maybe automatic clustering of individuals through classification
•
•
•
•
•
•
fishing devices (including vessels)
fishing and fish farming techniques (plans and activity types)
farming systems (sets of components)
fishery regulations (norms)
fishery managament systems (plans)
production centers</p>
      </sec>
      <sec id="sec-3-4">
        <title>Quality</title>
      </sec>
      <sec id="sec-3-5">
        <title>Quality Region</title>
      </sec>
      <sec id="sec-3-6">
        <title>Aggregate</title>
      </sec>
      <sec id="sec-3-7">
        <title>Object</title>
        <p>Body
Ordinary object</p>
      </sec>
      <sec id="sec-3-8">
        <title>Feature</title>
      </sec>
      <sec id="sec-3-9">
        <title>Occurrence Abstract</title>
        <p>Amount of matter
Arbitrary collection
Physical Object
Mental Object
Relevant part
Place
State
Process</p>
        <p>Accomplishment</p>
        <p>Development is performed as incremental loading and classification of upper
and core level ontologies in the Ontology Server.</p>
        <p>
          Another indirect resource that can be exploited to build the core ontology is
the analysis of systematic polysemies (they have been already used in the mining of
large medical thesauri, cf.[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]). A systematic polysemy is discovered when a relation
exists between two senses of a term, and this relation is relevant for the domain that
is being analysed. Consequently, if we find many polysemies with senses that have
been conceptualised within the same concept pairs, this is an indication for a possible
core ontology relation.
3.3.2 Building domain IS-A taxonomies
        </p>
        <p>This phase deals with the integration of the resources for domain ontology
development with the fishery core ontology (developed in the previous phase).</p>
        <p>Resulting taxonomies could be either ’tolerated’ or ’cleaned up’. Tolerance
amounts to have widespread and unexplained polysemy for terms, but it is not time
consuming. Cleaning is the most time consuming task, since a frequent scenario is
the following: concept C from source S1 (C^S1) is in principle similar to a D^S2
(usually because they share one or more terms), but they actually occupy two
taxonomical places that make them disjoint according to the upper or core ontology.</p>
        <p>
          The ONIONS methodology [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] in this case suggests to axiomatise their
glosses (cf. ⁄3.2.3, 3.3.3) and to check if their taxonomical position is correct. If it is
not, then they are probably polysemous senses of the same term, and some alternative
methods can be applied to relate those senses, to merge them, or to accept the
conceptual split of the senses.
        </p>
        <p>Some cleaning will be needed in any case to remove at least the major
taxonomical clashes. This results into a domain taxonomy. Additional effort should
be dedicated to distinguish:</p>
        <p>Concepts vs individuals (heuristics applicable: country names, institutions,
etc.).</p>
        <p>
          Backbone concepts vs viewpoint
contingent notions), cf. [
          <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
          ].
        </p>
        <p>This eventually results into a refined domain taxonomy.</p>
        <p>concepts (roles, reified
properties,
3.3.3 Collecting existing documentation and producing glosses</p>
        <p>Available resources for ontology documentation are collected and associated
as a kind of annotation (gloss) to domain concepts. Concepts lacking a gloss require a
new one.</p>
        <p>For core concepts and relations, besides existing glosses, an extensive
description of their scope in the FCO is provided.
3.3.4 Designing a preliminary topic architecture</p>
        <p>
          A preliminary topology for most general topics (to be used for ontology
modularisation as well) is figured out. Here the following resources are reused:
ontologies for topics (Welty s topic topology [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], topic maps standard [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ],
OnTopic principles [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]), semantic portals design [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], oneFish topic trees.
        </p>
        <p>Administration
Subjects</p>
        <p>Ecosystem
Geography</p>
        <p>Species
Stakeholders</p>
        <p>The topic topology will be used both for maintaining the ontology library and for
managing text indexing and retrieval. Figure 5 shows how the current topic spaces of
oneFish are structured. Figure 6 shows an ontology-based architecture for the
Integrated Fishery Ontology.</p>
      </sec>
      <sec id="sec-3-10">
        <title>3.4 Building domain axioms</title>
        <p>Once taxonomies are cleaned to a certain extent, documented, and divided
into appropriate namespaces, activities aimed at raising the conceptual detail of the
ontology can be started. The most important is the characterisation of domain
concepts with axioms. In order to realise this, domain resources containing informal
relationships, and (at least some) glosses from documentation are upgraded to the
status of logical axioms.</p>
        <p>Informal relationships can be found in thesauri (e.g. related term) as well as
reference tables and topic trees. They are mined in order to understand:
1) if the axioms are applicable to all the subconcepts of the concept to
which the axiom pertain, and
2) what quantification is applicable to those axioms: existential (necessary)
or universal (contingent)?</p>
        <p>
          This results into formal Domain Axioms. This axiom set is enhanced by
axiomatising glosses. Here the ONIONS methodology [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] is applied to derive
formal domain axioms from natural language descriptions. The typical technique
consists in extracting terms, parsing them according to a dependency grammar, and
applying core and upper ontologies to assign concepts and relations to the resulting
dependency trees.
        </p>
        <p>
          This activity is time-consuming, and semi-automatic techniques are still a
research issue [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Scalability and approximate results are considered here.
        </p>
        <p>The axioms obtained from informal relationships and glosses are revised
according to the fishery core ontology developed so far.</p>
      </sec>
      <sec id="sec-3-11">
        <title>3.5 Modularising ontology library according to topics</title>
        <p>
          Following OnTopic methodology [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ], dependency chains of core concepts
are automatically generated and the existing preliminary topic topology is checked in
order to produce a first version of the ontology library architecture. Dependency
chains are also applied to derive indexing tags and boolean search spaces.
        </p>
        <p>A dependency chain is the transitive closure of the logical depend-ons of a
concept. The transitive closure is applied to the defining elements of a concept. Here a
set of relevance parameters are applied in order to</p>
      </sec>
      <sec id="sec-3-12">
        <title>3.6 Providing multi-lingual lexicalisation to elements in the ontology library</title>
        <p>An integrated fishery ontology benefits from the existence of terms already
related to concepts in the original resources, since they semi-automatically provide the
so-called lexicalisation of concepts. On the other hand, having an integrated ontology
also provides a powerful tool to check polysemous senses of terms, as well as to
check consistency of UF thesaurus relations and consistency of multi-lingual
equivalents.</p>
      </sec>
      <sec id="sec-3-13">
        <title>3.7 A unified architecture</title>
        <p>The basic idea is that user queries, through a query interface, can be
submitted to two kinds of servers: if the query aims at retrieving documents, a
topicbased fishery agent rewrites the query in order to submit it to heterogeneous databases
(brokering); if the query aims at finding specialised conceptual or terminological
information, it is directed to the Fishery Ontology Server (FOS). In both cases, the
query interface uses FOS. Query rewriting needs also mapping relations from the
integrated fishery ontology to the source thesauri.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>CONCLUSIONS</title>
      <p>In this paper we have outlined some research solutions within the framework
of ontology integration that are based on formal upper and core ontologies. Some
details have been given on how informal schemata such as thesauri, reference tables,
and topic trees can be reused and refined in order to be manipulated by ontology
integration. Some hints have also been shown about the dependence of topic trees
from ontologies, a promising research area for the semantic web.</p>
      <p>In fact, the overall research issue underlying the FOS project is to provide a
unified methodology of ontology integration and merging based on formal
ontologies, ontology library design, topic trees building and maintainance, and
efficient web search and indexing.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>[1] http://www.fao.org/fi</mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>[2] http://www4.fao.org/asfa</mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>[3] http://www.fao.org/agrovoc</mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>[4] http://www.onefish.org</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>[5] http://www.ontoweb.org</mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>[6] http://www-2.cs.cmu.edu/afs/cs.cmu.edu/project/theo-6/web-agent/www/i3.html</mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guarino</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Masolo</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <article-title>Oltramari A.: Understanding Top-Level Ontological Distinctions</article-title>
          , in: H. Stuckenschmidt (ed),
          <source>Proceedings of the IJCAI 2001 Workshop o n Ontologies and Information Sharing</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guarino</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oltramari</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Conceptual Analysis of Lexical Taxonomies: The Case of WordNet Top-Level</article-title>
          , in: C Welty, B Smith (eds.),
          <source>Proceedings of the 2001 Conference on Formal Ontology and Information Systems</source>
          , Amsterdam, IOS Press (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Calvanese</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Giacomo</surname>
            <given-names>G</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Framework for Ontology Integration</article-title>
          .
          <source>Proceedings of 2001 Int. Semantic Web Working Symposium (SWWS</source>
          <year>2001</year>
          )
          <article-title>(</article-title>
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pisanelli</surname>
            <given-names>DM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steve</surname>
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>An Overview of the ONIONS Project: Applying Ontologies to the Integration of Medical Terminologies</article-title>
          .
          <source>Data and Knowledge Engineering</source>
          ,
          <year>1999</year>
          , vol.
          <volume>31</volume>
          , pp.
          <fpage>183</fpage>
          -
          <lpage>220</lpage>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pisanelli</surname>
            <given-names>DM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steve</surname>
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>The OnTopic Methodology for Supporting Active Catalogues with Formal Ontologies</article-title>
          .
          <source>ISTC-CNR-OCMG Internal Report iii-01</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Taconet</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roux</surname>
            <given-names>O: FIGIS</given-names>
          </string-name>
          ,
          <source>The Fisheries Global Information System.</source>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>[13] http://www.ontoweb.org/SIG</mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Velardi</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Missikoff</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fabriani</surname>
            <given-names>P</given-names>
          </string-name>
          :
          <article-title>Using Text Processing Techniques t o Automatically Enrich a Domain Ontology</article-title>
          , in: C Welty, B Smith (eds.),
          <source>Proceedings o f the 2001 Conference on Formal Ontology and Information Systems</source>
          , Amsterdam, IOS Press (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Welty</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <article-title>The Ontological Nature of Subject Taxonomies</article-title>
          ,
          <string-name>
            <surname>N</surname>
          </string-name>
          Guarino (ed.),
          <source>Proceedings of the First Conference on Formal Ontology and Information Systems</source>
          , Amsterdam, IOS Press (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>Pepper</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>The</surname>
            <given-names>TAO</given-names>
          </string-name>
          of Topic Maps: http://www.gca.org/papers/xmleurope2000/papers/s11-
          <fpage>01</fpage>
          .html
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Stojanovic</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maedche</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Staab</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Studer</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sure</surname>
            <given-names>Y</given-names>
          </string-name>
          :
          <string-name>
            <surname>SEAL - A Framework for Developing SEmantic PortALs</surname>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Oltramari</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guarino</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Masolo</surname>
            <given-names>C</given-names>
          </string-name>
          ,:
          <article-title>Restructuring WordNet's Top-Level: The OntoClean approach</article-title>
          , in K Simov (ed):
          <source>Proceedings of the The LREC2002 Workshop on Ontologies and Text</source>
          , Las
          <string-name>
            <surname>Palmas</surname>
          </string-name>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>