<!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>Experiences with Multilingual Modeling in the Development of the International Classification of Traditional Medicine Ontology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Csongor Nyulas</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>Tania Tudorache</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>Samson Tu</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>Mark A. Musen</string-name>
          <email>museng@stanford.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Stanford Center for Biomedical Informatics Research, Stanford University</institution>
          ,
          <country country="US">US</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>The International Classification of Traditional Medicine</institution>
          ,
          <addr-line>ICTM</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>The World Health Organization (WHO) in collaboration with several international stakeholders have started recently the work on the International Classification of Traditional Medicine (ICTM), which will provide a standardized system for encoding and collecting health statistics data related to Traditional Medicine practice throughout the world. ICTM is represented in OWL, and is developed by Traditional Medicine experts in a collaborative Semantic Web platform, called iCAT-TM. The content of ICTM is developed simultaneously in four languages (English, Chinese, Japanese and Korean). In this paper, we describe how we modeled the multilingual content, the Web platform used for editing, and some of the challenges we have encountered related to the multilingual aspects of the model and use of the platform.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>cross-linking between them, the classifications have now a formal underpinning. ICTM,
similarly to ICD-11, is represented as an OWL ontology and is developed using
Semantic Web technologies.</p>
      <p>Given the international nature of ICTM, tackling the multilinguality problem is one
of the main challenges in the project. Domain experts from the three countries and
the project coordinators in Geneva, Switzerland, are developing the content of ICTM
simultaneously in four languages: English, Chinese, Japanese, and Korean. Our group
has provided the ontology modeling support and the Web platform infrastructure used
for editing ICTM. In this paper, we describe our experiences in supporting multiple
languages in the ICTM ontology, including the model and tooling, and the challenges
we encountered.</p>
      <p>The rest of the paper is organized as follows: Section 2 describes the related work,
in Section 3, we describe how we modeled the multilingual content in ICTM, Section 4
presents the collaborative Semantic Web platform used by the domain experts to edit
ICTM, and finally, Section 5 presents the challenges and some lessons learned in the
project, and gives an overview of the future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        As the Semantic Web matures, there is an increasing body of research on localizing
ontologies. For example, the SKOS-XL extension [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] treats labels as first order
resources, thus enabling the definition of explicit links between labels associated to the
same concept. Montiel-Ponsoda et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] try to overcome some of the limitations of the
SKOS-XL representation and propose a module for lemon [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] that supports different
types of translation relations and metadata, such as provenance and reliability scores.
Extensive work on ontology localization [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] has also been done in the NEON project3
that proposes guidelines and a tool to support this process.
      </p>
      <p>
        Silva et al. present conceptME [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], a collaboration framework that supports
ontology localization starting early in the conceptualization phase. Providing terminological
support so early in the development process proved to enhance the conceptualization
of the domain. conceptME has also support for sharing conceptual models, for content
negotiation and discussion.
      </p>
      <p>In this work we did not use any of the related approaches, as one of the main
requirements in the project (see Section 3) was to use and/or extend the ICD-11 ontology
to ensure that these two ontologies will be easily integrated at a later stage. We plan to
investigate the related approaches (such as SKOS-XL and the extensions to lemon) to
see if they would fit the requirements for ICTM, and if so, we will refactor our ontology
accordingly.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Multilingual Modeling in ICTM</title>
      <p>
        As we mentioned before, one of the main requirements for ICTM is that it should
follow similar modeling patterns to the ICD-11 ontology [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], so that these two can be
easily integrated.4 In addition, all ICTM textual content should be available in four
languages: English, Chinese, Japanese and Korean, which Traditional Medicine experts
3 http://www.neon-project.org
4 As we mentioned before, part of ICTM will be available as a separate chapter in ICD-11.
from different countries will input during development. A further requirement, which
came later in the project, was to support transliteration of titles, i.e., converting the
Chinese, Japanese and Korean scripts into Latin script. For example, a common
transliteration for converting Chinese characters into Latin script is Pinyin. Figures 1 and 2
show the transliteration of the simplified Chinese disease title 气瘿 (meaning, Qi goiter
disorder) into Pinyin as Qi ying. Other metadata will be attached to the label of a term
into a specific language, such as the source of the label (e.g., the Traditional Medicine
classification where the label originates from), and an internal id that is used by other
WHO software.
      </p>
      <p>We modeled ICTM in OWL 1.0. We used a reified class, LanguageTerm, to
represent all linguistic terms in the ontology. We have created a taxonomy of language terms
as subclasses of the LanguageTerm class, as some of the term types have additional
properties attached to them. For example, the SynonymTerm has additional properties
that describe if and how it will be included in an electronic index for the classification.
In the current version of the model, there are eight subclasses of LanguageTerm that
represent among others, the title, the fully specified title, the definition, other external
definitions, the synonyms, and so on. The actual value for a language term is an instance
of a subclass of LanguageTerm.</p>
      <p>Figure 1 shows an excerpt of the class level modeling for language terms and how
different properties of a disease class (title, definition, synonym, etc.) have been reified.
The figure also shows an example for modeling the five title terms for the Qi goiter
disorder disease class. The Qi goiter disorder class has a property title that has as values
five instances of the class TitleTerm that correspond to the titles in 5 languages
(English, Japanese, Korean, simplified Chinese and traditional Chinese). Some TitleTerm
instances (e.g., TitleTerm 4788 for simplified Chinese) has in addition to the label and
language properties, also another property, alternativeLabel, to represent the
transliteration of the Chinese script to Latin characters. Other language terms (not shown in the
figure), such as the ExternalDefinitionTerm—used to reference textual definitions from
external resources — have additional properties that specify the source of the definition
in greater detail (e.g., the ontology name, the IRI of the source ontology entity, the URL
for the source ontology, etc.).</p>
      <p>As there might be confusion about the difference between synonyms and
transliterations, we would like to clarify this issue. A synonym is a term that has a similar meaning
to a another term (in our case, the title term). In ICTM, as in ICD-11, synonyms are also
used to store alternative titles for a disease, that are either found in scientific literature,
or have minor linguistic variations, or are used in the colloquial language (e.g, the
synonym for Roseola infantum is Sixth disease). The synonyms apply for terms in the same
language (e.g., an English title may have other English synonyms). A transliteration, on
the other hand, represents exactly the same term in the same language, but in a different
script. A term may have several transliterations (Korean has 4 different transliterations).
4</p>
    </sec>
    <sec id="sec-4">
      <title>The iCAT-TM Platform</title>
      <p>
        Traditional Medicine experts around the world are editing ICTM using the collaborative
iCAT-TM Web platform. iCAT-TM is a customization of the generic WebProte´ge´
ontology editor [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The user interface of iCAT-TM is tailored for domain experts, who are
not knowledgeable about ontologies or knowledge representation. iCAT-TM presents a
form-based interface shown in Figure 2 that is is less intimidating for the experts than
a generic ontology editor would be. The experts can edit the class taxonomy in the left
panel of the ICTM Content Tab, and the class details, including the language terms, in
the right panel.
      </p>
      <p>iCAT-TM has many collaboration features inherited from WebProte´ge´, such as the
support for simultaneous editing, change history of users’ actions, and notes and
discussions attached to any entity in the ontology.</p>
      <p>We have created a generic widget that displays the content of reified individuals,
and we have reused it for displaying and editing the different language terms. In
Figure 2, the ICTM Title uses this widget to display the values of the TitleTerm individuals
associated to the title property of a disease. A row in the widget table corresponds to one
of the reified individual values, and the columns display the properties of the respective
row individual value. The same widget is also used for displaying the short definition
of a disease (the transliteration column has been hidden from view).</p>
      <p>One “bonus” of using reified individual for language terms (which, as a
consequence, have identity) is that we can attach notes and discussion threads to a particular
individual. For example, in Figure 2, the second short definition of the disease has a
comment attached to it (shown as the number 1 next to the comment icon on the
second row). This feature enables domain experts to have focused discussions right in the
context in which they are editing. The contextual discussions are particularly useful
because each disease has several properties that need to be filled, in many cases by
different experts, and the overview and management of notes and discussions is much
easier.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Discussions and Future Work</title>
      <p>The iCAT-TM has been in production use since February 2011 by 25 Traditional Medicine
experts. As a result, ICTM contains now more than 1,500 classes, 15,000 reified terms,
out of which, 10,000 are language terms. The users have created more than 60,000
changes in the ontology, and added more than 1,100 notes and discussions.</p>
      <p>Since the beginning of the project, we have encountered several challenges related
to the multilingual aspects in the modeling, tooling and use of the platform.</p>
      <p>Modeling. ICTM was developed using OWL 1.0 to make it compatible with the
ICD-11 ontology. For this reason, we had to use reified relations to model the language
terms. Reified relations, even though they have the advantages described earlier, have
several disadvantages, as well. First, the reified individuals clutter the domain
ontology, and increase its size significantly (in ICTM, almost all property values are reified).
Second, these anonymous individuals are used in reasoning (as part of the domain
ontology) and can slow it down significantly. We plan to overcome these limitations by
upgrading the ontology to OWL 2.0 (ICD-11 will also upgrade), and rather than using
reified individuals, we plan to use annotations on axioms. We plan to change the
modeling in other aspects, too. For example, the transliterations are currently modeled as
a multiple cardinality datatype property that take string literals as values. Even if we
can now add more transliterations for the same label (e.g., Korean has four different
transliterations), we cannot specify to which script or alphabet a transliteration belongs
to. We plan to address this issue by using nested annotations on axioms in the OWL 2.0
modeling. Additionally, we plan to investigate if other approaches for ontology
localizations, such as the ones we mentioned in the Related Work section, are suitable for
ICTM. If these approaches fit the requirements, we will refactor the ontology to use a
more standard approach. This undertaking will, however, require significant effort, as
we need to also change the modeling of ICD-11, as well as migrate all existing content
of two live production system (iCAT for ICD-11, and iCAT-TM for ICTM) to the new
structure.</p>
      <p>Tooling. We had to make sure that our tooling works well with international
characters. While these are not an issue for the Web application per se (Web browsers can
show pages in different encodings), we had to adjust our Lucene-based search
mechanism to work properly with multiple languages. One hurdle for the domain experts in
using iCAT-TM is that the user interface is presented in English, and many of them are
not very comfortable with it. We plan to redesign the user interface to better follow the
principles of internationalization, so that we can more easily provide language specific
user interfaces. We do expect that this step will involve a significant re-design effort.</p>
      <p>Use of the platform. We had several user related challenges that are not
necessarily of technical nature. For example, when we started the project, we used (wrongly)
the country codes to model the languages (ch, jp, and kr). Later, in the process, we
changed the language codes to the correct ones from the ISO 639-1 (en, zh, ja, ko),
however, some of the domain experts complained that the correct language codes are
less intuitive to use. Also, when we started the project, we did not anticipate that some
content will be entered in simplified Chinese, while other will be entered in traditional
Chinese, which created some confusion with the users. As a solution, we added also
the traditional Chinese language code (zh-Hant), so that at a later date the Chinese
content can be easier curated and harmonized (it is expected that in the official distribution
only simplified Chinese will be used). Another challenge is related to the
communication among the domain experts, as most of them speak only their native language,
and sometimes English, too. To improve the communication among the domain experts
and the WHO coordinators in Geneva, we have introduced the transliteration. Another
challenge related to the language barrier is that experts do not agree on the English
translation for a term, and “invent” new English translations. This fact also makes the
curation and verification of the entire classification content very challenging, because
finding Traditional Medicine experts who understand all languages and can verify that
the terms in different languages really mean the same thing, is very difficult.</p>
      <p>As future work, we plan to upgrade ICTM to OWL 2.0 to overcome the modeling
issues we described before. We will also create linkages between ICTM classes and
ICD-11 classes that will put into correspondence Traditional Medicine disorders with
“Western” diseases. As the project progresses, we will also provide a peer-reviewing
mechanism, in which external domain experts will review different aspects of ICTM.</p>
      <p>The iCAT-TM platform is currently in production use, and we expect that by 2015,
when the ICD-11 major revision is planned to end, the ICD-11 Chapter 23, containing
a part of ICTM, will be finalized as well. Even after 2015, ICTM will continue to be
developed as an independent classification that will address the needs of the Traditional
Medicine practices around the world.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>We thank our WHO collaborators and the ICTM project members for developing the project
requirements and for the fruitful collaboration. The work presented in this paper is partly supported
by the NIGMS Grant 1R01GM086587.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>SKOS</given-names>
            <surname>Simple</surname>
          </string-name>
          <article-title>Knowledge Organization System eXtension for Labels (SKOS-XL) Namespace Document - HTML Variant</article-title>
          . http://www.w3.org/TR/skos-reference/ skos-xl.
          <source>html. Last accessed: August</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>M.</given-names>
            <surname>Espinoza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Montiel-Ponsoda</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Go</surname>
          </string-name>
          <article-title>´mez-Pe´rez. Ontology localization</article-title>
          .
          <source>In Proceedings of the fifth international conference on Knowledge capture</source>
          , pages
          <fpage>33</fpage>
          -
          <lpage>40</lpage>
          . ACM,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>J. McCrae</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Aguado-de Cea</surname>
            ,
            <given-names>P.</given-names>
            Buitelaar, P.
          </string-name>
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Declerck</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Garcia</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Hollink</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Spohr</surname>
          </string-name>
          , et al.
          <article-title>Interchanging lexical resources on the semantic web</article-title>
          .
          <source>Language Resources and Evaluation</source>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>E.</given-names>
            <surname>Montiel-Ponsoda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gracia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Aguado-de Cea</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Go</surname>
          </string-name>
          <article-title>´mez-Pe´rez. Representing translations on the semantic web</article-title>
          .
          <source>MSW</source>
          <year>2011</year>
          , page
          <volume>25</volume>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>M.</given-names>
            <surname>Silva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Soares</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Costa</surname>
          </string-name>
          .
          <article-title>Supporting collaboration in multilingual ontology specification: the conceptme approach</article-title>
          .
          <source>TKE</source>
          <year>2012</year>
          , page 27.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>T.</given-names>
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Falconer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Nyulas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Noy</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Musen</surname>
          </string-name>
          .
          <article-title>Will Semantic Web Technologies Work for the Development of ICD-11? In The 9th Intl</article-title>
          .
          <source>Semantic Web Conference (ISWC</source>
          <year>2010</year>
          ), pages
          <fpage>257</fpage>
          -
          <lpage>272</lpage>
          . Springer,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>T.</given-names>
            <surname>Tudorache</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Nyulas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Noy</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Musen</surname>
          </string-name>
          .
          <article-title>Webprote´ge´: A collaborative ontology editor and knowledge acquisition tool for the web</article-title>
          .
          <source>Semantic Web Journal</source>
          , pages
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. World Health Organization.
          <article-title>International Classification of Diseases (ICD)</article-title>
          . http://www. who.int/classifications/icd/.
          <source>Last accessed: August</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. World Health Organization.
          <source>Traditional Medicine in Health Information Systems: Integrating Traditional Medicine into the WHO Family of International Classifications</source>
          . https: //sites.google.com/site/whoictm/home/ICTMProjectPlan.pdf.
          <source>Last accessed: August</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>