<!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>Joint Handling of Semantic Knowledge Resources and their Alignments ?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Bruno Thiao-Layel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vianney Jouhet</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>Gayo Diallo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>BPH Center, INSERM U1219, Team ERIAS</institution>
          ,
          <addr-line>Univ. Bordeaux</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>CHU de Bordeaux</institution>
          ,
          <addr-line>Univ. Bordeaux, Bordeaux</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Synapse Medicine</institution>
          ,
          <addr-line>2 place de la bourse, Bordeaux</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Motivation
With the adoption of the Semantic Web vision , semantic knowledge resources
(KR), which include taxonomies, structured vocabularies and ontologies, acting
as pivotal resources, are nowadays commonly used. This is a direct consequence
of the desire to attach formal semantic meaning to manipulated data. These
KR, developed by di erent communities with various needs and purposes, are
by nature heterogeneous. This heterogeneity leads to the development of systems
for nding the correspondences between entities of di erent KR, called alignment
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. In addition, KR increasingly involve large volumes of formalized knowledge,
containing hundred of thousand entities, which raises the question of generating
and validating alignments between large resources.
      </p>
      <p>In order to help nding and reusing these more and more available KRs, a
signi cant e ort has been made for providing multi-knowledge resources
repositories. This e ort is particularly noticeable in the biomedical domain, where
classifying existing objects is a secular tradition.</p>
      <p>However, to the best of our knowledge, there is no currently available
framework which o ers the possibility to handle both multiple KRs together with
their respective alignments, while keeping their native semantics and o ering
a support for a transparent visualization of these resources. In addition, with
the development of the ontology matching domain, as di erent systems could
be used to generate alignments and sometimes relying on user input, either for
mappings validation purpose or initial alignment providing, it is a crucial issue
to keep track of users and involved alignment methods or tools.</p>
      <p>
        To ll this gap, we have designed the K-Ware framework [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] which
complement existing multi-knowledge resources repositories. Its aim is not to provide a
single access point for all available biomedical ontologies and alignments. Rather,
it is a framework which could be embedded within projects that have an
extensive use of multiple KRs and their respective alignments. In particular, enabling
a support for multi point of view navigation and hierarchical visualization of any
KR relevant for a dedicated purpose or suitable for a given project.
? This study is supported by the Drugs Systematized Assessment in real-liFe
Environment (DrugSafe) platform, funded by the French Agency for Drugs Monitoring.
      </p>
      <p>Joint handling of knowledge resources and alignments
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Alignment management</title>
      <p>
        In order to properly take into account alignments between di erent KRs, we
have introduced additional properties to the de nition of the notion of
correspondence introduced in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Therefore, we identify the following components
for a correspondence : i) the two entities to be mapped, linked with a
MappingRelation, in an directed order (e1-mappingRelation-e2 ); ii) its con dence
value; iii) the mapping's author / User; iv) the mapping's method called
MappingMethod, either if it is an alignment provided by an automated method
ComputerizedProcess with an alignment Tool or a manual one; v) nally, a
ag which indicates whether the considered mapping is valid (and validated by
a User) for an Alignment between two KRs.
2.2
      </p>
    </sec>
    <sec id="sec-3">
      <title>Handling structural relations within knowledge resources</title>
      <p>KRs often exhibits a structural hierarchical organization : the is-a relationship
translated into rdfs:subClassOf or the part-whole relationship for formal
ontologies and the narrower/broader relationship for taxonomies, translated into
skos:narrower and skos:broader respectively. We nd similar notions when it
comes to express inter relationships between entities in di erent KRs. For
instance, the skos:narrowMatch is used to state a hierarchical mapping link
between two conceptual resources in di erent concept schemes. Hierarchical aspect
is the the main information to be kept when one wishes to integrate many
different semantic resources.</p>
      <p>To allow navigating easily KR represented in the OWL or SKOS languages,
we distinguish three types of relations : HierarchicalRelation, LiteralDe
nition and MappingRelation. In a given KR, a hierarchical relation could be
rdfs:subClassOf, skos:broader, part of, etc.). A literal de nition helps rendering
a human readable description of an entity (rdfs:label, skos:prefLabel, etc.). While
a mapping relation (for instance owl:equivalentTo, skos:exactMatch) handle
correspondences between entities.</p>
      <p>An API has been implemented for the features de ned models of K-Ware4.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Thiao-Layel</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jouhet</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Diallo</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>K-Ware: vers une gestion conjointe de ressources semantiques et leurs alignements 6iemes Journees Francophone sur les Ontologies</article-title>
          ,
          <year>Oct 2016</year>
          , Bordeaux, France Hepp, M.,
          <string-name>
            <surname>de Bruijn</surname>
          </string-name>
          , J.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Shvaiko</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Euzenat</surname>
          </string-name>
          , J.: Ontology Matching:
          <article-title>State of the Art and Future Challenges</article-title>
          .
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          , Volume:
          <volume>25</volume>
          , Issue: 1,
          <string-name>
            <surname>Jan</surname>
          </string-name>
          .
          <year>2013</year>
          , Page(s):
          <fpage>158</fpage>
          -
          <lpage>176</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>