<!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>ConceptTerms</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <string-name>Domains Linguistic, Vocabulary.</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DSI AP-HP</institution>
          ,
          <addr-line>Paris</addr-line>
          ,
          <country country="FR">FRANCE</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>INSERM UMRS 872</institution>
          , ́
          <addr-line>eq.20, 15, rue de l' ́ecole de m ́edecine, 75006 Paris</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>MONDECA</institution>
          ,
          <addr-line>3, cit ́e Nollez, 75018 Paris</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Pierre-Yves Vandenbussche</institution>
        </aff>
      </contrib-group>
      <fpage>124</fpage>
      <lpage>126</lpage>
      <abstract>
        <p>The integration of domain terminological resources is a major issue for their full utilization. This integration is made difficult by the nature of these resources and their formal representation heterogeneity. In order to tackle this integration problem, we foster a solution based on metamodeling: the unfied metamodel for structured vocabularies. In this abstract, we sketch out assets for using Ontology Design Patterns (ODPs) in a unified metamodel by reusing n-ary relation pattern and describing new ODP for concept-terms representation. This ConceptTerms ODP allows designers to represent jointly conceptual and linguistic part of a vocabulary. The pattern purpose is not to encompass all linguistic complexity as Linginfo or LMF does, but to describe linguistic information in more details than SKOS which names concept with simple labels.</p>
      </abstract>
      <kwd-group>
        <kwd>Covers Requirements What preferred terms and synonyms (simple non pre- ferred term) have a concept? What is the preferred term of a concept in a specific language? By which preferred term a coumpound non preferred term is composed?</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Pattern</title>
      <sec id="sec-2-1">
        <title>Problem</title>
        <p>Intent ConceptTerms pattern allows designers to represent jointly conceptual
and linguistic part of a vocabulary. The pattern purpose is not to encompass
all linguistic complexity as Linginfo or LMF does, but to describe linguistic
information in more details than SKOS which names concept whith simple labels.</p>
      </sec>
      <sec id="sec-2-2">
        <title>Solution</title>
        <p>A concept is named in a particular language by a preferred term and a set
of simple non preferred terms (multilinguism). Those terms artifacts specialize
the term entity which owns common properties. This list of properties may be
extended depending on vocabulary specific needs. This pattern suits for
various vocabularies (thesaurus, terminology, taxonomy) and has been applied to
GEMET, Eurovoc, CIM10 among other. Modeling takes into account: - the
possibility to extend the current pattern in order to add some more precise linguistic
information (for instance represent translation relation between two terms since
term is a class) - minimal linguistic artifacts necessary for vocabulary resource
access by providing a preferred Term to name a concept and some synonyms
which are Simple non preferred terms.
Consequences Compare to labels on a concept class, this solution has a higher
data load.
2.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Example</title>
        <p>Used for vocabulary representation. For example in Eurovoc (http://europa.eu/eurovoc/),
a concept has a preferred term social sciences in english and a simple non
preferred term (i.e. synonyms) humanities in the same language whereas the same
concept has a preferred term sciences sociales in french and a simple non
preferred term sciences humaines in this language. If we wanted to add a
translation relation between terms we could state that social sciences english
term is a translation of sciences sociales french term. If we consider a second
preferred term in english award which names a concept, in a particular
information retrieval context, we could define a coumpound non preferred term
social sciences awards which is related to preferred terms social sciences and
award .
2.4</p>
      </sec>
      <sec id="sec-2-4">
        <title>Related Resources</title>
        <p>In BS8723 model, triangular-shaped relations are defined between a thesaurus
concept, a preferred term and some simple non preferred terms. We are convinced
that maintaining this model can be optimized by reifying those relations in a
single relation class. That is why we defines the Concept-Terms relation which
reusing N-ary pattern in order to represent terms on a concept. Between all
terms, we distinguish a preferred term and some synonyms (simple non preferred
terms).
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Pattern Usage</title>
      <p>This pattern suits for various vocabularies (thesaurus, terminology, taxonomy)
and has been applied to Eurovoc authoring management.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Summary and Future Work</title>
      <p>This pattern allows ontology designers to represent jointly conceptual and
linguistic part of a vocabulary. Therefore, it is a complementary pattern to linguistic
ones.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>