<!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>Representing Translations on the Semantic Web</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Elena Montiel-Ponsoda</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jorge Gracia</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Guadalupe Aguado-de-Cea</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Asuncion Gomez-Perez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ontology Engineering Group, Dpto. Inteligencia Arti cial Facultad de Informatica, Universidad Politecnica de Madrid Campus de Montegancedo s/n, 28660 Boadilla del Monte</institution>
          ,
          <addr-line>Madrid, Spain jgracia, emontiel, lupe</addr-line>
        </aff>
      </contrib-group>
      <fpage>25</fpage>
      <lpage>37</lpage>
      <abstract>
        <p>The increase of ontologies and data sets published in the Web in languages other than English raises some issues related to the representation of linguistic (multilingual) information in ontologies. Such linguistic descriptions can contribute to the establishment of links between ontologies and data sets described in multiple natural languages in the Linked Open Data cloud. For these reasons, several models have been proposed recently to enable richer linguistic descriptions in ontologies. Among them, we nd lemon, an RDF ontology-lexicon model that de nes speci c modules for di erent types of linguistic descriptions. In this contribution we propose a new module to represent translation relations between lexicons in di erent natural languages associated to the same ontology or belonging to di erent ontologies. This module can enable the representation of di erent types of translation relations, as well as translation metadata such as provenance or the reliability score of translations.</p>
      </abstract>
      <kwd-group>
        <kwd>multilingual Semantic Web</kwd>
        <kwd>multilingual Linked Data</kwd>
        <kwd>lemon model</kwd>
        <kwd>translation relations</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The Linked Open Data [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ] initiative has triggered the publication and linking
of data sets in the RDF [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] format, contributing in this way to semantically
structuring huge amounts of data on the Web. Thanks to the representation
format propounded by Linked Data, concepts are connected across resources,
breaking down the barriers imposed by data silos, and enabling machines to
smartly navigate the Web as a big data set. Currently, more than 250 data
sets containing more than 30 billion triples are available in the Linked Open
Data (LOD) cloud1, ranging from domains as far apart as biomedicine, music
or geography. Governmental institutions, enterprises and the private sector have
realized the bene ts and potential of such an initiative and have made their data
sets available for linking and exploitation by third parties.
      </p>
      <p>The launching phase of the LOD was led by English speaking countries, but
in recent years, the LOD cloud has also seen an increase in resources documented
in languages other than English. By having a quick look at the CKAN2 catalogue
of data sets, we come across the data.bnf.fr data set from the French National
Library, the GeoLinkedData.es data set of Spanish geographical data,
Rechtspraak.nl from the Netherlands Council of the Judiciary, or the FAO geopolitical
ontology with labels in English, French, Spanish, Arabic, Chinese, Russian and
Italian.</p>
      <p>
        This proliferation of semantic data described in several natural languages
evidences the need for accounting for the linguistic information relative to
ontologies and linked data because of several reasons. One of the main reasons is
that the linguistic descriptions of these resources help in nding and establishing
mappings between concepts and individuals of di erent ontologies and data sets
[
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. Another evident reason is that such descriptions contribute to a better
exploitation of the data sets by tasks such as information extraction [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], natural
language generation [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], or multilingual data access [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], to mention but a few.
      </p>
      <p>
        Several formats and annotation properties have been developed in the
Semantic Web to represent natural language descriptions associated to ontologies
and linked data, such as the rdfs:label [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] or skos:prefLabel [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] properties. Their
limitations have been discussed in several fora [
        <xref ref-type="bibr" rid="ref14 ref18 ref5">5, 18, 14</xref>
        ], and extensions or new
models have been proposed in the last years for the representation of
linguistic descriptions relative to ontologies and linked data in more principled ways.
Some of these models are SKOS-XL [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], LexInfo [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], LIR [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], or the recently
appeared lemon model [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Most of these models also provide some
mechanisms to allow for the representation of multilingual descriptions associated to
the same ontological representation. However, we argue that explicit relations
between descriptions in di erent languages, i.e., translation relations, as well
as translation descriptive metadata, would help in a more e cient exploitation
of these multilingual annotations. Moreover, they would also contribute to the
establishment of principled links between ontologies and data sets described in
multiple natural languages in the LOD cloud.
      </p>
      <p>In this paper, we propose a representation mechanism of translations
between labels in di erent languages associated to ontology terms. To that end, we
propose a metamodel in OWL which extends the lemon ontology, and which is
o ered as a module of the lemon model. lemon is a linguistic model developed
in the framework of the Monnet3 project to represent lexical and terminological
descriptions relative to an ontology. The lemon extension we propose in this
paper enables the representation of translations in a separate linguistic layer, thus
leaving the original ontologies or data sources untouched. It also contributes to
the linking of ontologies and data sets described in di erent natural languages
in the Web of Data.</p>
      <p>The rest of the paper is organized as follows. Section 2 summarizes the
mechanisms that some Semantic Web formats or models have for linking linguistic
2 http://ckan.net/
3 http://www.monnet-project.eu/
descriptions in several natural languages. In section 3, we analyze the problem of
translation relations in the context of the Semantic Web. After that, in section
4, we brie y present the lemon model. Thanks to the modular conception of
this model, we are now able to propose a translation module, i.e., a module to
explicitly represent translations in lemon. Section 5 will be devoted to a detailed
description of the translation module, and some examples will be provided to
illustrate the use of this module. Finally, we conclude the paper in section 6.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related work</title>
      <p>
        As it is well known, RDFS [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] and SKOS [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] rely on limited annotation
properties to represent labels or linguistic descriptions associated to ontologies and
linked data. They also enable a simple form of multilingual labeling by using
language tags to restrict the scope of a label to a particular language (e.g.,
skos:prefLabel \bank"@en). This representation allows for indirect or non-explicit
links between or among multilingual labels, when associated to the same resource
in the data set.
      </p>
      <p>
        Conscious of these limitations, SKOS developers worked on an extension of
SKOS called SKOS-XL [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] , that allows to make links explicit between labels
associated to the same concept. This extension introduces a skosxl:Label class that
allows labels to be treated as rst-order RDF resources, and a skosxl:labelRelation
property that provides links between the instances of skosxl:Label classes. In this
way, we can specialize the skosxl:labelRelation into a translation relation and
explicitly link skosxl:Label instances in di erent natural languages.
      </p>
      <p>
        The LIR [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] model also focuses on the representation of links between labels
within and across natural languages. This model was created with the purpose
of keeping the ontology and the linguistic information independent from each
other, so that lexical and terminological properties of labels could be further
described (e.g., part-of-speech, gender, terminological variants). The relations
provided by LIR to labels within the same natural language have lexical
(hasSynonym, hasAntonym) or terminological nature (hasVariant, hasAbbreviation,
hasTransliteration, etc.). And the ones between labels across di erent natural
languages have a translational nature (hasTranslation or hasScienti cName).
      </p>
      <p>Now, the relations provided by the SKOS-XL and LIR models, though being
useful for certain applications because of the explicitness of the hasTranslation
relation between labels in di erent natural languages, do not allow to account
for some aspects of the translation process that may also be relevant for
certain applications. For instance, the di erence between original and target label.
This may be interesting in the case that we have an ontology documented in
four natural languages, and we want to specify which labels (or which linguistic
descriptions) have been taken as the source in the translation process. Another
aspect to be considered could be the type of translation relation existing
between labels (we will come back to this in section 3). Moreover, the provenance,
i.e., the resource from which translations have been obtained may also be the
kind of metadata that enriches the information about translation. Finally, it is
important to account for the adequacy and reliability of the translation in the
speci c context of the ontology. An extension of these models would be required
to represent further translation metadata. However, we have chosen the lemon
model for this purpose, because its design principles make it specially
appropriate for the Web of Data scenario. Firstly, lemon introduces a `well-de ned
lexical-conceptual' path between linguistic descriptions and ontology elements.
Secondly, lemon has been designed as a concise RDF model that captures
complex linguistic descriptions by dereferencing resources that contain them. And
thirdly, it is an extensible and modular model, which allows the use or
inclusion of certain modules if so required by the nal application. These and other
features of the model will be further detailed in section 4.</p>
      <p>Finally, we will refer to the LOD in Translation work 4, in which a model
has been created to describe and retrieve translations in the LOD cloud relying
on resources that contain labels in di erent natural languages. This model takes
advantage of multilingual labels associated to resources by means of language
tags (as in rdfs:label \bank"@en, rdfs:label \Bank"@de, rdfs:label \banco"@es )
and retrieves available translations. Our purpose, on the other hand, is to
contribute to the creation of explicit translation links within the same data source
and across data sources, so that this and other systems can bene t from the
multilingual data in the LOD cloud.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Translation relations in the Semantic Web</title>
      <p>
        Ontology localization [
        <xref ref-type="bibr" rid="ref21 ref6 ref8">21, 8, 6</xref>
        ] has been de ned as the activity of adapting an
ontology to the needs of a particular (linguistic and cultural) community.
Methodological guidelines, tools and models have been developed to support the
ontology localization activity, which normally results in an ontology in which labels
are documented in multiple natural languages, what is the same, a multilingual
ontology [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Since the di erent linguistic versions are assumed to be pointing
to the same ontology concepts, it could be derived that they are all translations
of each other. However, if we have several terms in each language (synonyms or
term variants), we may want to unambiguously express which term variant in
language A is translation of which term variant in language B. At this point,
translation relations acquire signi cance.
      </p>
      <p>Let us illustrate this with a simple example. In the FAO geopolitical
ontology mentioned in the introduction, one ontology term may describe the
organization as such and have the labels \Food and Agriculture Organization" and
\FAO". Translations of full form and acronym will be provided in the rest of
languages, and, ideally, explicit links will be created between the full forms and
the acronyms, respectively.</p>
      <p>
        However, translation relations are not always so direct and simple. As claimed
in [
        <xref ref-type="bibr" rid="ref6 ref8">8, 6</xref>
        ], depending on the type of conceptualization represented in the ontology,
direct translations in the target language will be available or not. A distinction
4 http://sites.google.com/site/pierreyvesvandenbussche/apps/lod-in-translation
is made between the so-called internationalized or standardized
conceptualizations, and conceptualizations more prone to reproduce the vision of the world of
a certain community, the so-called, culturally-in uenced domains. When
localizing ontologies of these two types, translation relations may also need to be of
di erent types. To put it in other words, when dealing with internationalized
domains, i.e., technical or specialized domains of knowledge such as engineering or
medicine that have standards for processes and descriptions, and whose
categorizations usually re ect the common view of di erent cultures [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], we may nd
translations for all terms describing the concepts in the ontology, since the same
conceptualization is shared among the languages represented in the ontology.
Contrary to that, when localizing ontologies representing culturally-in uenced
domains, in which the granularity level of some concepts may di er from culture
to culture, we may come across mismatches that need to be solved to provide
adequate translations. Under this group we include domains such as law,
geography or the political and administrative organization of countries, universities,
and so on.
      </p>
      <p>Imagine an ontology of nancial institutions in Germany. One of the
concepts represented in the ontology may be Sparkasse (which we could generally
translate as savings bank in English). However, there may be di erences between
these concepts concerning business purpose, ownership or governance of the
institution. So, maybe, a more adequate translation of Sparkasse could be German
savings institution, although we usually tend to look for the closest equivalent
concept in the target language and get the term used to refer to it, i.e., savings
bank in this case. This simple example aims at illustrating the di erence
between `literal or documentary translations', and `functional translations'5. The
rst type usually describes the concept in the target language, because there is
no exact equivalence in the target language. The second type looks for the
closest equivalence -though being conscious of the existence of disparities- because
it may be convenient for practical reasons. For instance, when aiming at
interoperability (at a European or international level), near-equivalents are assumed
to match although a complete overlap between them does not exist.</p>
      <p>
        According to this, we make a distinction between literal translations and
cultural equivalences. In the context of the Semantic Web, this distinction may
be quite simple to make. The literal translation would be pointing to the same
ontology concept, whereas the cultural equivalent would most probably belong
to an equivalent ontology documented in the target language. See gure 1 for an
illustration of this. Ontology A is an ontology of German credit institutions in
which labels have been translated into English, whereas Ontology B
conceptualizes the structuring of British credit institutions in English. It would be highly
interesting to specify the links between these terms in a multilingual scenario.
For these reasons, we claim that further speci cations of the translation relation
would contribute to envisage a true Multilingual Semantic Web.
5 Many practitioners and translation theorists agree on this di erence and speak about
overt vs. covert translation [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], or documentary vs. instrumental or functional
translation [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ], respectively.
      </p>
      <p>Ontology A
(German)</p>
      <p>Ontology B
(English)
Concept A</p>
      <p>Concept B
Sparkasse German savings institution</p>
      <p>Savings bank
lemon, an interchange model for the Multilingual</p>
    </sec>
    <sec id="sec-4">
      <title>Semantic Web</title>
      <p>
        The lemon model (lexicon model for ontologies) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] is an RDF model of
linguistic descriptions that has been designed to a) be published with ontologies, b)
extend their lexical layer with as much linguistic information as needed, and c)
exchange the resulting lexical resources on the Web. Technical details and usage
of the model can be found at http://lexinfo.net/lemon-cookbook.pdf The main
features of the model can be summarized as follows:
{ Linguistic descriptions are kept separated from the ontology, but their
semantics are de ned by pointing to the corresponding semantic objects in the
ontology (what has been called `semantics by reference' [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]).
{ The model consists of a core set of classes (as described below) and several
modules capturing di erent types of lexical and terminological descriptions.
{ Rich lexical and terminological descriptions are grouped into ve modules:
linguistic properties (part-of-speech, gender, number...), lexical and
terminological variation, decompositions of phrase structures (representation of
multi-word expressions), syntactic frames and their mappings to the logical
predicates in the ontology, and morphological decomposition of lexical forms.
{ Linguistic annotations (data categories or linguistic descriptors) are not
captured in the model, but have to be speci ed for each lexicon by dereferencing
their URIs as de ned in the repositories that contain them (for instance, the
ISOcat repository [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]).
      </p>
      <p>The di erent types of linguistic descriptions captured by the model and its
main classes can be seen in gure 2. The core classes of the model are the ones
that form the main path between the Ontology and the lexical variants
represented in the LexicalEntry class. The LexicalSense class provides a principled
link between an ontology concept and its lexical materialization (LexicalEntry ).
Component
leaf</p>
      <p>Node
constituent:Resource
separator:String
tree
Frame</p>
      <p>synArg
Argument
optional:boolean</p>
      <p>marker
Lexical
Category
edge</p>
      <p>leaf
lemon
Morph</p>
      <p>Pattern
nextTransform</p>
      <p>transform</p>
      <p>Morph
Transform
rule:string</p>
      <p>equivalent
onStem generates innacroromwpeartible</p>
      <p>
        broader
Prototype
prefRef
altRef
hiddenRef
Since `concepts', as de ned in ontologies, and `lexical entries', as de ned in
lexicons, cannot be said to overlap [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], the LexicalSense class provides the adequate
restrictions (usage, context, register, etc.) that make a certain lexical entry
appropriate for naming a certain concept in the speci c context of the ontology
being lexicalized.
      </p>
      <p>LexicalSense is also the class that is foreseen to provide the links between
lexical entries within and across languages. Four specializations of this relation are
provided: equivalent, incompatible, narrower and broader, as illustrated in
gure 2. As the lemon model de nes one lexicon per language, translation relations
could be inferred as lexical entries in di erent languages would be all pointing
to the same ontology reference. However, it is also foreseen to make this type of
relation explicit between lexical senses, in the case that, for instance, lexical
entries are not pointing to the same ontology reference, but belong to the linguistic
descriptions associated to other ontologies.</p>
      <p>
        As such, the translation relation between lexical senses is a powerful
mechanism to represent translations. Nevertheless, and as already pointed out in
section 1, when dealing with translations, additional properties of the
translation relation need to be made explicit, such as reliability score, provenance, or
type of translation relation, as already introduced in section 2. In this sense,
the exibility provided by the lemon model by means of modules allows us to
propose a so-called `translation module', by reifying a translation relation
between lexical senses into a class. The use of such a module could be exploited
by applications that require multilingual ontologies and want to keep track of
the relations between the lexical entries in di erent languages. This information
would be very valuable if translations have been automatically generated via an
ontology localization system (e.g., LabelTranslator NeOn Toolkit plug-in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]).
5
      </p>
      <p>lemon module for translations
In this section we describe the entities of the translation module in lemon6 and
illustrate its use by means of some examples. Figure 3 shows the class diagram of
the translation ontology. Some classes are imported from the core of the lemon
ontology, namely Lexicon, LexicalEntry, Form, and LexicalSense.
{ Translation. This is the central class of the translation module. It mediates
the translation relation between lexical senses, and contains also
information that characterizes the translation process, such as a con dence level.
This con dence level will ultimately depend on the translation tools and
translation resources employed to obtain translations. We do not deal here
with the algorithms used for its computation, but it will typically combine
di erent features such as probabilities of translation systems, reliability of
translations resources, scores of disambiguation methods, etc.
6 It will be available at http://www.monnet-project.eu/lemon translation.owl
{ Literal Translation. It is a subtype of the translation class that corresponds
to the idea of literal translations mentioned above.
{ Cultural Equivalence Translation. A subtype of the translation class that
covers translations that are not literal, but close cultural equivalences between
the languages considered.
{ Resource. It represents resources from which translations have been obtained.
{ Lexical Sense. A sense links a lexical entry to the reference (ontology term)
used to represent its meaning.
{ Lexical Entry. It is a container of the di erent forms and meanings of a
lexeme.
{ Form. An in ectional form of an entry. It admits several representations
(written, phonetic, etc.).
{ Lexicon. This class represents the whole lexicon. It has a language associated,
so it is assumed to be monolingual. Translations will typically connect entries
between di erent monolingual lexicons.
5.1</p>
      <p>Examples of use of the lemon translation module
In order to illustrate the usage of the translation module, in this section we
provide some examples of the nancial and politics domains.</p>
      <sec id="sec-4-1">
        <title>LEXICONEN</title>
        <p>LexicalEntry
“payment method”
LexicalEntry
“medio de pago”</p>
      </sec>
      <sec id="sec-4-2">
        <title>LEXICONES</title>
        <p>LexicalSense
LiteralTranslation</p>
        <p>LexicalSense</p>
        <p>ONTOLOGY
http://purl.org/goodrelations/v1#PaymentMethod</p>
        <p>Figure 4 represents an ontology term extracted from the GoodRelations
ontology7. In lemon we would be able to associate as many lexicons in di erent
languages to the ontology as wished. In the gure, we show two lexicons that have
been associated to the ontology: one lexicon with English descriptions and the
other with Spanish descriptions. Both lexicalize in di erent languages the same
ontology concept, namely, http://purl.org/goodrelations/v1#PaymentMethod. Each
lexicon contains a lexical entry and a lexical sense representing the ontology
concept in each language. The lexical sense belonging to the English lexicon would
be the sourceLexicalSense, and the one of the Spanish lexicon would be the
targetLexicalSense, since the ontology was conceived in English. The provenance of
the translation would be speci ed at the Resource class. It could be an on-line
resource (machine translation service), a lexicon or terminology of the domain,
or even a human translator. A con dence value could also be assigned to the
translation by means of the con denceLevel property of the Translation class.
Finally, we would relate these two translations by means of the LiteralTranslation,
subclass of the Translation class. This would mean that in the speci c
context of the ontology being lexicalized and localized, the target lexical
sense provides a description or literal translation of the term, which
is to be used in the context of the original ontology. It is highly
probable that the Spanish translation \medio de pago" is also its cultural equivalent,
which would mean that the same concept exists in the Spanish nancial system
and has been termed as the literal translation. So in this case, both translation
relations would be valid.</p>
        <p>LexicalEntry
“Prime Minister”
“Presidente del Gobierno”</p>
      </sec>
      <sec id="sec-4-3">
        <title>LEXICONES</title>
        <p>LexicalSense</p>
        <p>http://www.gobernontology.co.uk/prime</p>
        <p>Cultural Equivalent Translation
LexicalEntry</p>
        <p>LexicalSense
http://www.ontologiagobierno.es/presidente</p>
        <p>ONTOLOGY
Ontology term
Ontology term</p>
        <p>ONTOLOGY</p>
        <p>Now, let us have a look at gure 5. This aims at illustrating cultural
equivalents between political systems. Here we have two ontologies, each one
representing a di erent political system, and each one documented in a di erent natural
language. The concept of \Prime Minister" in the British political system and
the concept of \Presidente del Gobierno" in the Spanish political system are not
exact equivalents, but can be considered the closest equivalents in the respective
cultures. This is why we would use the class CulturalEquivalenceTranslation to
relate the two lexical senses that we assume would belong to two lexicons
associated to two di erent ontologies. Such a relation would indicate that these
two terms are substitutable or translations of each other, when
looking for interoperability and referring to (close) equivalents in di erent
languages and cultures, whose extention may not completely overlap.
In this case, we could also include literal translations of each lexical entry in
the respective lexicons. In the English lexicon we could include the Spanish
lexical entry \Primer Ministro Britanico", which would be a literal translation in
Spanish. In the same way, we could also add the lexical entry \Spanish
President" or \Spanish President of the Government" in the Spanish lexicon. These
translations would be related to each other by the LiteralTranslation class.
6</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>The publication of ontologies and data sets in multiple natural languages has
raised some issues related to the representation of the linguistic descriptions
relative to ontologies. In the context of Linked Data, this takes on more importance
since ontologies and data sets described in di erent natural languages have to be
linked to each other. Moreover, such natural language descriptions have proven
essential in enabling the exploitation of semantically structured knowledge by
language-based tasks. With the purpose of establishing explicit links between the
linguistic descriptions associated to ontologies and linked data in several natural
languages, in this paper we propose an extension of the lemon model to represent
translation relations. This translation module allows us to di erentiate between
literal and cultural equivalence translations. In addition to that, we can provide
metadata relevant to the localization process that may be of great interest when
relying on the automatic translation of ontologies.</p>
      <p>As future work we plan to carry out some experiments to provide statistics
on the impact of such translation relations in the Multilingual Semantic Web,
speci cally the distinction between literal translations and cultural equivalences.
We also aim at investigating the implementation of algorithms that would
automatize this process.</p>
      <p>Acknowledgments. This work is supported by the EU project Monnet
(FP7248458), and by the Spanish national project BabeLData (TIN2010-17550).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berbers-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked data - the story so far</article-title>
          .
          <source>International Journal on Semantic Web and Information Systems</source>
          .
          <volume>5</volume>
          ,
          <issue>1</issue>
          {
          <fpage>22</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Idehen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked data on the web (LDOW2008)</article-title>
          .
          <source>In: 17th international conference on World Wide Web</source>
          , pp.
          <volume>1265</volume>
          {
          <issue>1266</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bontcheva</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <article-title>The Semantic Web: Research and Applications</article-title>
          . In: Generating tailored textual summaries from ontologies Springer, pp.
          <volume>531</volume>
          {
          <issue>545</issue>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Ontology-based Semantic Lexicons: Mapping between Terms and Object Descriptions</article-title>
          .
          <source>In: Ontology and the Lexicon</source>
          , pp.
          <volume>212</volume>
          {
          <fpage>223</fpage>
          . Cambridge University Press (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haase</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sintek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <source>Towards Linguistically Grounded Ontologies In: 6th European Semantic Web Conference (ESWC09)</source>
          , pp.
          <volume>111</volume>
          {
          <issue>125</issue>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Espinoza</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Note on Ontology Localization</article-title>
          .
          <source>Journal of Applied Ontology</source>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ), pp.
          <volume>127</volume>
          {
          <issue>137</issue>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Declerck</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krieger</surname>
          </string-name>
          , H.-U.,
          <string-name>
            <surname>Thomas</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ORiain</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wunner</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maguet</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCrae</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spohr</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Ontology-based Multilingual Access to Financial Reports for Sharing Business Knowledge across Europe</article-title>
          . In Rooz, J.,
          <string-name>
            <surname>Ivanyos</surname>
            ,
            <given-names>J</given-names>
          </string-name>
          . (eds.)
          <article-title>Internal Financial Control Assessment Applying Multilingual Ontology Framework</article-title>
          , HVG Press Kft, pp.
          <fpage>67</fpage>
          -
          <lpage>76</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Espinoza</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Ontology Localization</article-title>
          .
          <source>In: 5th International Conference on Knowledge Capture (KCAP09)</source>
          , pp.
          <volume>33</volume>
          {
          <issue>40</issue>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Espinoza</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mena</surname>
          </string-name>
          , E.:
          <article-title>Enriching an Ontology with Multilingual Information</article-title>
          .
          <source>In: 5th Annual of the European Semantic Web Conference (ESWC08)</source>
          , pp.
          <volume>333</volume>
          {
          <issue>347</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Hirst</surname>
          </string-name>
          , G.:
          <article-title>Ontology and the Lexicon</article-title>
          . In: Staab,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Studer</surname>
          </string-name>
          ,
          <string-name>
            <surname>R</surname>
          </string-name>
          . (eds.) Handbook on Ontologies,
          <source>International Handbooks on Information Systems</source>
          , Springer, pp.
          <volume>209</volume>
          {
          <issue>230</issue>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>House</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Model for Translation Quality Assessment</article-title>
          , Narr, (
          <year>1977</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Kemps-Snijders</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Windhouwer</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wittenburg</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wright</surname>
            <given-names>S.:</given-names>
          </string-name>
          <article-title>ISOcat: Corralling data categories in the wild</article-title>
          .
          <source>In: International Conference on Language Resource and Evaluation (LREC)</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Manola</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>E.: RDF</given-names>
          </string-name>
          <string-name>
            <surname>Primer</surname>
          </string-name>
          .
          <source>Technical report, W3C Recommendation World Wide Web Consortium (W3C)</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>McCrae</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aguado-de-Cea</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buitelaar</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cimiano</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Declerck</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>GomezPerez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gracia</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hollink</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spohr</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wunner</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Interchanging Lexical Resources in the Semantic Web. Language Resources and Evaluation</article-title>
          , in press (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>SKOS-Simple Knowledge Organization System Reference, W3C</article-title>
          ,
          <source>Retrieved April 11</source>
          ,
          <year>2011</year>
          , from http://www.w3.org/TR/skos-reference/ (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>SKOS Simple Knowledge Organization System eXtension for Labels (SKOS-XL) Namespace Document - HTML Variant , W3C</article-title>
          , Retrieved June 21,
          <year>2011</year>
          , from http://www.w3.org/TR/skos-reference/skos-xl.
          <source>html</source>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          : Multilingualism in Ontologies.
          <source>Building Patterns and Representation Models. LAP LAMBERT Academic Publishing, Germany</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Montiel-Ponsoda</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , Aguado de Cea, G.,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peters</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Enriching Ontologies with Multilingual Information</article-title>
          .
          <source>Journal of Natural Language Engineering</source>
          ,
          <volume>17</volume>
          (
          <issue>3</issue>
          ),
          <volume>283</volume>
          {
          <fpage>309</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. Muller, H.-M.,
          <string-name>
            <surname>Kenny</surname>
            ,
            <given-names>E. E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sternberg</surname>
            ,
            <given-names>P. W.</given-names>
          </string-name>
          :
          <article-title>Textpresso: An Ontology-Based Information Retrieval and Extraction System for Biological Literature</article-title>
          .
          <source>PLoS Biol</source>
          ,
          <volume>2</volume>
          ,
          <issue>e309</issue>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Nord</surname>
          </string-name>
          , Ch.:
          <article-title>Loyalitt statt Treue</article-title>
          .
          <source>Lebende Sprachen</source>
          ,
          <volume>34</volume>
          , pp.
          <volume>100</volume>
          {
          <issue>105</issue>
          (
          <year>1989</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Surez-Figueroa</surname>
            ,
            <given-names>M. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Perez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Towards a Glossary of Activities in the Ontology Engineering Field In: 6th Language Resources and Evaluation Conference (LREC08) (</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Svab-Zamazal</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Svatek</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Analysing Ontological Structures through Name Pattern Tracking</article-title>
          .
          <source>In: EKAW 2008 - 16th International Conference on Knowledge Engineering and Knowledge Management</source>
          , pp.
          <volume>213</volume>
          {
          <issue>228</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Volz</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gaedke</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kobilarov</surname>
          </string-name>
          , G.:
          <article-title>Silk A Link Discovery Framework for the Web of Data</article-title>
          .
          <source>In: 2nd Workshop about Linked Data on the Web (LDOW2009)</source>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>