<!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>Applying the OntoLex Model to a Multilingual Terminological Resource</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Julia Bosque-Gil</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>Elena Montiel-Ponsoda</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ontology Engineering Group, Universidad Politecnica de Madrid</institution>
          ,
          <addr-line>Spain Campus de Montegancedo, Boadilla del Monte 28660 Madrid</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Terminesp is a multilingual terminological resource with terms from a range of specialized domains. Along with de nitions, notes, scienti c denominations and provenance information, it includes translations from Spanish into a variety of languages. A linked data resource with these features would represent a potentially relevant source of knowledge for NLP-based applications. In this contribution we show that Terminesp constitutes an appropriate validating test bench for OntoLex and its vartrans module, a newly developed model which evolves the lemon model to represent the lexicon-ontology interface. We present a rst showcase of this module to account for variation across entries, while highlighting the modeling problems we encountered in this e ort. Furthermore, we extend the resource with part-of-speech and syntactic information which was not explicitly declared in the original data with the aim of exploring its future use in NLP applications.</p>
      </abstract>
      <kwd-group>
        <kwd>ontolex</kwd>
        <kwd>variation</kwd>
        <kwd>translation</kwd>
        <kwd>terminological resource</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Recent years have seen growing interest in the publication of language resources
(LRs) as linked data, and the presence of machine readable dictionaries,
lexicons, and thesauri in the Linguistic Linked Open Data (LLOD) cloud1 continues
to increase. Linking language resources not only enables humans and software
agents easier access and querying of structured data collections, but linked
multilingual LRs represent a potentially relevant source of knowledge for NLP-based
applications developed in the elds of machine translation, content analytics,
multilingual information extraction, word sense disambiguation or ontology
localization. The inclusion of terminological knowledge from di erent domains into
the LLOD cloud has already been explored with the creation and publication
of thesauri, vocabularies and terminology repositories, especially in the
environmental and geological domain [10, 1, 2], as well as in the nancial [9] and
linguistics [6, 3, 4] elds. Converting and publishing terminological dictionaries</p>
    </sec>
    <sec id="sec-2">
      <title>1 http://linguistic-lod.org/</title>
      <p>as linked data opens new doors to the reuse of these resources in domain speci c
NLP applications and machine translation.</p>
      <p>Aimed originally at bridging the gap between lexical and conceptual
information, the lemon model (LExicon Model for ONtologies) [7] is now a widespread
representation model for the publication of lexical resources as linked data which
has been gradually expanded to include new modules under the umbrella of the
W3C Ontology-Lexica Community Group2, resulting in the newly developed
model OntoLex/lemon.3 An extension to lemon that accounts for translation
relations among lexical senses from the same or di erent data sets was also
developed [5]. In such e ort, the Terminesp4 data served as a validating example
of a terminological LR to which the translation module would apply.</p>
      <p>Our contribution builds on such previous work [5] and describes a rst
showcase of the vartrans module of OntoLex in order to account for terminological
variation and translation relations among entries. In addition to showcasing the
vartrans module, we extend the resource further by adding components to
represent de nitions and terminological norms of Terminesp entries. The entries
themselves range from simple nouns and adjectives to complex nominal,
prepositional and adjectival phrases, which led us to include part-of-speech information
for each entry and turn to LexInfo [4] classes to account for that mixed
nature as well. We also draw attention to the modeling problems to which these
prepositional phrases give rise and which will be tackled in future work.</p>
      <p>The structure of this paper is as follows: Section 2 brie y explains the
OntoLex vartrans module, with special focus on the terminological variation
aspects not addressed in previous work. Section 3 introduces the Terminesp
database and provides an example of the structure of its data. Section 4 dwells on
previous work with Terminesp and describes our approach to model the entries,
including de nitions and syntactic information, among other aspects. Following,
we showcase the vartrans module to represent scienti c denominations. Lastly,
Section 5 discusses some conclusions and future lines of work.
2</p>
      <sec id="sec-2-1">
        <title>The OntoLex vartrans Module</title>
        <p>OntoLex is the resulting work of the continued e orts made by the W3C
Ontology Lexica Community Group during the past three years to build a rich
model to represent the lexicon-ontology interface. It is largely based on the
lemon model [7] and, along with the extensions to it, integrates work of the
various Community members.</p>
        <p>Broadly, each entry in the lexical database belonging to an ontolex:Lexicon
is modeled as an ontolex:LexicalEntry and mapped to its respective ontology
entity. The mappings are established at the sense level through the property
ontolex:reference and the class ontolex:LexicalSense, thereby capturing</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>2 https://www.w3.org/community/ontolex/</title>
    </sec>
    <sec id="sec-4">
      <title>3 See http://www.w3.org/community/ontolex/wiki/Final_Model_Specification.</title>
      <p>We will refer to it as OntoLex in the rest of this paper.</p>
    </sec>
    <sec id="sec-5">
      <title>4 http://www.wikilengua.org/index.php/Wikilengua:Terminesp</title>
      <p>the fact that a single lexical entry may have di erent senses, each one referring
to a di erent ontology entity and evoking a particular lexical concept. However,
information regarding the realization of a lexical entry (e.g. in ection,
pronunciation, etc.) is recorded at the lexical form level via ontolex:Form.</p>
      <p>The OntoLex vartrans module was developed to record variation relations
across entries in the same or di erent languages. The intuition behind it is to
capture two kinds of relations: those among senses and those among lexical
entries and/or forms. Variation relations among senses are of semantic nature and
include terminological relations (dialectal, register, chronological, discursive, and
dimensional variation)5 and translation relations. In contrast, relations among
lexical entries and/or forms concern the surface form of a term and encode
morphological and orthographical variation, among other aspects. This last kind of
relations are not considered semantic in nature; grammatical meaning encoded
in morphological a xes is thus represented at a di erent layer than lexical
meaning (senses), and variation in orthography is thought as a relation between two
similar forms (e.g. analyze, analyse), in contrast to synonymy and antonymy
relations between two senses (e.g. shut, close) in which the surface forms are not
involved. In this paper we only focus on the rst kind of relations, variation
relations among senses, to represent translations and register (also called diaphasic)
relations between a term and its scienti c denomination.
2.1</p>
      <sec id="sec-5-1">
        <title>Translations</title>
        <p>The OntoLex vartrans module frames translation relations as a special type
of lexico-semantic variation across the entries of di erent lexica, more speci
cally, as relations that hold among senses. The translation component goes back
to the lemon Translation module. In this view, the vartrans module turns
to a pivot class vartrans:Translation to represent translations among
lexical entries as relations among ontolex:LexicalSenses that point to the same
ontology concept. One of the main di erences between the OntoLex and the
lemon translation modules is the conception of a class to encompass variation
relations, the vartrans:LexicoSemanticRelation class. Its subclasses denote
relations that hold among lexical entries (vartrans:LexicalRelation) and
relations that hold among lexical senses (vartrans:SenseRelation). The pivot class
vartrans:Translation mentioned before is thus a vartrans:SenseRelation,
and so are the relations among terminological variants as well
(vartrans:TerminologicalVariant). The Terminesp database contains translation relations of
the directEquivalent category, but other translation categories (e.g.
culturalEquivalent, for culture-dependent concepts; lexicalEquivalent, for literal
translations of the source term, etc.) are supported as well and can be included from
an external ontology [5]. In addition to translation relations among their senses,
lexical entries in di erent languages can be directly related through the property
vartrans:translatableAs.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>5 http://www.w3.org/community/ontolex/wiki/Specification_of_Requirements/</title>
      <p>Properties-and-Relations-of-Entries</p>
      <sec id="sec-6-1">
        <title>2.2 Terminological variants in the same language</title>
        <p>Terminological variants in the same language are modeled as relations among
senses, too. The vartrans module allows for the encoding of dialectal (diatopic),
register (diaphasic), chronological (diachronic), stylistical (diastratic) as well as
dimensional variation among entries. In this way and in the same fashion as
translations, two lexical entries are mapped to their respective lexical senses, and
these are related through the pivot class vartrans:TerminologicalVariant,
with the property vartrans:category allowing for the speci c type of
terminological variation at hand to be included as well. For cases in which there is
not any directionality involved, that is, there is not any source or target term,
the property vartrans:relates (similar to the former tr:translationSense
in lemon) links the two senses to the element acting as pivot. In the following
example, there is a diachronic variation between the terms phthisis and
tuberculosis, being the latter one the one used nowadays. This shift is captured by
representing the two senses as source and target respectively.
@prefix ontolex : &lt; http :// www . w3 . org / ns / lemon / ontolex # &gt; .
@prefix vartrans : &lt; http :// www . w3 . org / ns / lemon / vartrans # &gt; .
@prefix dct : &lt; http :// purl . org / dc / terms / &gt;.
: tuberculosis a ontolex : LexicalEntry ;
ontolex : lexicalForm : tuberculosis_form ;
ontolex : sense : tuberculosis_sense .
: tuberculosis_form ontolex : writtenRep " tuberculosis " @en .
: tuberculosis_sense ontolex : reference</p>
        <p>&lt; http :// dbpedia . org / resource / Tuberculosis &gt;.
: phthisis a ontolex : LexicalEntry ;
ontolex : lexicalForm : phthisis_form ;
ontolex : sense : phthisis_sense .
: phtisis_sense ontolex : reference
&lt; http :// dbpedia . org / resource / Tuberculosis &gt;;
dct : subject</p>
        <p>&lt; http :// dbpedia / resource / Medicine &gt; .
:phtisis diachronic var a vartrans:TerminologicalVariant;
vartrans:source :phthisis sense ;
vartrans:target :tuberculosis sense ;
vartrans:category isocat:diachronic.</p>
        <sec id="sec-6-1-1">
          <title>The Terminesp Database</title>
          <p>The Terminesp terminological database was created by the Asociacion Espan~ola
de Terminolog a (Spanish Association for Terminology, AETER) by
extracting the terminological data from the UNE (`Una Norma Espan~ola' a Spanish
norm) documents produced by AENOR (Asociacion Espan~ola de Normalizacion
y Certi cacion). It contains the terms and de nitions used in the UNE
Spanish technological norms (standards) and amounts to more than thirty thousand
terms with equivalences in other languages whenever they are available. These
norms, similar to the ISO standards, have been elaborated by Spanish
committees composed of experts in di erent elds. The norms are de ned over a range
of domains, from aeronautics and electro-technical engineering to fruit
nomenclature. An entry in Terminesp consists of the de nition of the term, the norm
from which the term is extracted, the norm title, and, if available, the
translation of the term to one or several di erent languages, namely German, French,
Italian, Swedish, and/or English. A Terminesp entry is presented in Table 1.6</p>
        </sec>
        <sec id="sec-6-1-2">
          <title>Migrating Terminesp to Linked Data</title>
          <p>
            In this contribution we renew the previous work with Terminesp [5] in order
to (
            <xref ref-type="bibr" rid="ref1">1</xref>
            ) detect errors and inconsistencies in the data before linking the data set
to other lexical resources (i.e. LexInfo), (
            <xref ref-type="bibr" rid="ref2">2</xref>
            ) provide a validating example of the
OntoLex vartrans module to account for variation across entries, with emphasis
on scienti c naming, (
            <xref ref-type="bibr" rid="ref3">3</xref>
            ) extend the LD resource with de nitions, norms, and
6 En. Norm: Electrotechnical vocabulary: Chapter 801. Acoustics and electroacoustics.
          </p>
          <p>De nition: Referred to a transducer, the di erence between the electrical admittance
on charge and its electrical admittance when it is mechanically locked. Note: NOTE
- This de nition applies mainly to transducers with transformer coupling.
part-of-speech categories, and (4) create a database of nominal, prepositional,
and adjectival phrases with highly specialized content (not covered by other LRs)
to be used by NLP applications. Since we have built upon previous work [5] with
the lexical database, we have stuck to the resource structure and URI naming
strategy that the authors followed in their approach.7 Being OntoLex still under
development, the RDF les resulting from our tests with Terminesp are not
published as linked data yet, but they are open and accessible online.8</p>
          <p>As in [5], we instantiate a skos:Concept for any given Terminesp entry in
order to ground the terms conceptually. A Terminesp entry, in turn, is modeled
as an ontolex:LexicalEntry whose ontolex:LexicalSense points to the
appropriate skos:Concept. Translations are included by instantiating a vartrans:
Translation element with the properties source and target linking the two
translation senses, one for each language. The senses are attached to the vartrans:
Translation by an additional property too, vartrans:relates.
4.1</p>
        </sec>
      </sec>
      <sec id="sec-6-2">
        <title>De nitions, notes, and norms</title>
        <p>In addition to the available translations for a given entry that were captured in
the previous lemon version [5], de nitions, notes, norm codes, norm titles and
provenance were added as linked data as well.</p>
        <p>Speci cally, de nitions are attached to the skos:Concept the
ontolex:LexicalSense is mapped to. This is done through the property skos:definition.
Moreover, some of these de nitions include a note that provides additional
information about the de nition content, use cases, etc. and, in order to distinguish
this from the de nition itself, we use rdfs:comment to relate the skos:Concept
to the string acting as note. In lemon, the class lemon:SenseDefinition
allowed to treat the de nition of a term as an object whose property lemon:value
pointed to the de nition string itself. This was particularly well-suited for
capturing elements that were not de nitions but which were nonetheless related
to them, as in the case of notes to de nitions, as we have in Terminesp. The
class lemon:SenseDefinition is not included in OntoLex, in fact, de nitions
are not encoded at the sense, but at the ontolex:LexicalConcept level with
the property ontolex:definition. A lexical concept in OntoLex aims to reify
the concept one or several senses evoke and lexicalize, resembling a synset in
WordNet. In our view, the approach based on the skos:definition property
appeared more suitable for the task. That is, an account of Terminesp de nitions
in terms of LexicalConcept de nitions would imply instantiating a lexical
concept for any Terminesp entry, which, along with the lexical sense, would bring
unnecessary complexity to the representation.</p>
        <p>Terminesp entries are all extracted from Spanish UNE documents and, in
addition to de nitions, the database provides norms and norm code information.
The norm each entry comes from is thus captured by dc:title, and the norm
code included with an instantiation of the dc:source property.
7 e.g. http://linguistic.linkeddata.es/data/terminesp/lexiconES
8 http://dx.doi.org/10.6084/m9.figshare.1344810</p>
      </sec>
      <sec id="sec-6-3">
        <title>Part-of-speech tags and syntactic phrases</title>
        <p>Part-of-speech (POS) tags were not provided in the original data. In order to link
each entry to its corresponding syntactic category through
lexinfo:partOfSpeech at the ontolex:LexicalEntry level, TreeTagger9 was used. The initial
idea was to tag the Spanish data in order to obtain part-of-speech information
that holds for translations to di erent languages as well. In other words, given
that the terms are highly specialized, a mechanical term in Spanish that is a
noun is likely to have a corresponding translation in English or German that
is a noun as well. However, the nature of Terminesp entries is mixed: the data
set is made up of adjectives, verbs and nouns, along with complex noun phrases
(NP), prepositional phrases (PP) and adjective phrases (AP). In order to
represent this, we linked multi-word Terminesp entries to lexinfo:NounPhrase,
lexinfo:AdjectivePhrase and lexinfo:PrepositionPhrase accordingly. In
this way we are encoding the syntax of a prepositional phrase and also stating
that it may function as an adjective or as an adverb (via lexinfo:partOfSpeech),
for instance. Table 2 shows the distribution of the di erent part of speech tags,
and which of them involve a complex phrase structure (NPs, PPs, APs).
lexinfo:PartOfSpeech Synt.Phrase Entries
noun simple 13777</p>
        <p>NP 18552
verb simple 69
adjective simple 31</p>
        <p>PP 56</p>
        <p>AP 4
adverb PP 2</p>
        <p>Total 32491</p>
        <p>Interestingly, the PPs are regarded here as independent entries and there is
not any information pointing to their syntactic governor, even though there are
complex NPs in the data that are formed by a noun and a PP that occurs as
lexical entry too. Thus, we nd a PP such as en reposo `idle' as a Terminesp entry
and other entries (NPs) with that same PP as constituent: masa en reposo, tinta
en reposo, pasador en reposo. However, the PP and the NP entries are not related
in the data. Not only does this contrast with conventional dictionaries, where
the preposition is usually accessed through its NP complement (reposo, en { )
or the whole PP is accessed through its syntactic governor (masa, { en reposo),
9 http://www.cis.uni-muenchen.de/~schmid/tools/TreeTagger/
but it also prevents us from using OntoLex's syntax and semantics module to
encode syntactic behavior, since we cannot access the syntactic governor of the
PP or the syntactic frame in which the PP would be t as argument. Moreover,
some of these PPs can also accompany a verb (estar en reposo, `to be idle';
funcionar en reposo, `to work idle'), so that the type of syntactic frame we are
dealing with is not always inferable from the PP alone.</p>
        <p>Most entries in Terminesp are actually NPs (see Table 2): e.g. potencia
isotropa radiada equivalente `equivalent isotropically radiated power'. With an
initial random test set of 500 entries, TreeTagger achieved 0.997 precision and
0.995 recall. The reason behind this is the high number of nouns. In cases in
which the entry was a complex phrase, TreeTagger tagged every element in it,
which allowed us to identify prepositional phrases. The remaining multi-word
entries were initially tagged as nouns. An analysis of the errors revealed that
deverbal adjectives were used as nouns throughout the data, and that some
multi-word entries included their tag (capacitivo, adj., `capacitive') or even a
disambiguation note: funcionar (para los reles elementales), `function (for
elemental relays)'. The tags for the scarce adjectives and verbs were checked and
corrected manually, and PPs were tagged as adjectives or adverbs according to
their de nition and sample uses, if the latter were available.</p>
        <p>It is worth mentioning, however, that PPs pose modeling problems still. There
seem to be di erent degrees of lexicalization among them: some of them are xed
both in the specialized domain and in the general language (en reposo); others,
e.g. a circuito abierto `open-circuited', may admit a certain degree of variation
and are not even regarded as a set phrase outside the specialized domain. Being
the meaning of these entries compositional (to a certain degree), they could not
be considered idioms according to the de nition of lexinfo:idiom, nor are they
collocations in the sense of olia:Collocation,10 and they do not correspond
either to the category of prepositional constructions as, for instance, composite
prepositions (in front of ) or prepositional adverbs (outside), which are accounted
for in linguistic terminology repositories. Furthermore, translations from the
Spanish entry (a PP) into other language may be in the form of PPs as well,
adjectives, or adverbs, depending on the target language. The part-of-speech
that we assigned to the Spanish entry itself is subject to change given that we
do not have the syntactic context in which the entry occurs: some of them are
eligible for both adjectival and adverbial use. Capturing these nuances, however,
was outside the scope of this paper but will be considered for future work on
terminological data.</p>
        <p>Figure 1 is included as an example of a Terminesp entry in OntoLex with
information about the de nition, the norm code, the norm title, the
part-ofspeech category and the syntactic phrase. Translations are not included in this
gure, but we refer the reader to Figure 2.
Another important issue is the scienti c naming of Terminesp terms. The
entries that provide a Latin term come mainly from the botanical domain, denoting
10 http://purl.org/olia/olia.owl#Collocation
most of them fruits and vegetables. e.g. Sp. uva `grape', Lat. Vitis vinifera
Linnaeus. These Latin terms could have been modeled as translations from Spanish
into Latin, following the approach adopted for all other translations, since, after
all, we are dealing with variation across di erent languages. Nonetheless, and
inspired by previous work on this domain, particularly on the LIR (Linguistic
Information Repository) model [8], we have decided to identify the Latin
entry as the international scienti c denomination. In this sense, scienti c names
are considered a speci c type of terminological variants subject to domain and
register rather than to any other factor. Also, they are internationally accepted
over scienti c communities and can appear in texts written in any language,
provided that the register and the domain are adequate for their use. Taking
this into account, Latin terms are thought here as terminological variants (see
Figure 3) and, more speci cally, as
lexinfo:InternationalScientificTerm(s). Relations among the Latin term and the entries in other languages are not
included, since the Spanish lexicon is taken to be the core of the resource, but
we do not discard adding them in future versions. The language tag of Latin
entries remains Latin, even though this results in a relation between two senses
in di erent languages that does not use a vartrans:Translation element.
5</p>
        <sec id="sec-6-3-1">
          <title>Conclusions and Future Work</title>
          <p>Terminesp has proved to be a suitable testing bench for the OntoLex core and
the vartrans module. Since OntoLex is still under development, migrating
Terminesp to RDF allowed us to carry out a rst application of the model on a
multilingual and terminological data set to check for any gaps or incongruities in the
representation approach. On the one hand, the multilingual nature of Terminesp
provided an appropriate use case of the vartrans module to account for
translations, and on the other hand, the scienti c denominations available in some
Terminesp entries proved suitable to encode register variation as well. However, we
missed the inclusion of a class or property in OntoLex to capture sense de nitions
or notes to them, since just modeling in terms of
ontolex:LexicalConcept(s) would overly complicate the task and did not seem to t for this particular
resource. Lastly, we draw attention to the modeling problems that entries with
varying degrees of lexicalization might give rise to in future e orts with
terminological data.</p>
          <p>As a rst future step, the data set will be published as linked data as soon
as the OntoLex model is released. This contribution not only aims to report
on the rst results of applying the model, but the Terminesp RDF data set
promises to be a potential signi cant resource for NLP-based applications. It
provides terminological information in several languages, some of them currently
under-represented in the LLOD cloud (e.g. Swedish), and translations among the
di erent languages are accessible through the Spanish terms acting as interlingua
elements. We will also explore the use of the pool of syntactic phrases discussed
in Section 4.2 in multilingual information extraction and language generation
tasks.</p>
          <p>
            Acknowledgments. This work is supported by the FP7 European project
LIDER (610782) and by the Spanish Ministry of Economy and Competitiveness
(project TIN2013-46238-C4-2-R).
4. Cimiano, P., Buitelaar, P., McCrae, J., Sintek, M.: LexInfo: A declarative model
for the lexicon-ontology interface. Web Semantics: Science, Services and Agents on
the World Wide Web 9(
            <xref ref-type="bibr" rid="ref1">1</xref>
            ), 29{51 (2011)
5. Gracia, J., Montiel-Ponsoda, E., Vila-Suero, D., Aguado-de Cea, G.: Enabling
Language Resources to Expose Translations as Linked Data on the Web. In: Proc.
of 9th Language Resources and Evaluation Conference (LREC'14), Reykjavik
(Iceland). pp. 409{413. European Language Resources Association (ELRA) (May
2014), http://www.lrec-conf.org/proceedings/lrec2014/pdf/863\_Paper.pdf
6. Kemps-Snijders, M., Windhouwer, M., Wittenburg, P., Wright, S.E.: ISOcat:
Corralling Data Categories in the Wild. In: Calzolari, N., Choukri, K., Maegaard, B.,
Mariani, J., Odijk, J., Piperidis, S., Tapias, D. (eds.) Proceedings of the Sixth
International Conference on Language Resources and Evaluation (LREC'08).
European Language Resources Association (ELRA), Marrakech, Morocco (May 2008),
http://www.lrec-conf.org/proceedings/lrec2008/
7. McCrae, J., Aguado-de Cea, G., Buitelaar, P., Cimiano, P., Declerck, T.,
GomezPerez, A., Gracia, J., Hollink, L., Montiel-Ponsoda, E., Spohr, D., Wunner, T.:
Interchanging lexical resources on the Semantic Web. Language Resources and
Evaluation 46(4), 701{719 (2012), http://dx.doi.org/10.1007/s10579-012-9182-3
8. Montiel-Ponsoda, E., Aguado-de Cea, G., Gomez-Perez, A., Peters, W.: Enriching
ontologies with multilingual information. Natural Language Engineering 17(
            <xref ref-type="bibr" rid="ref3">3</xref>
            ), 283
{309 (2010)
9. Neubert, J.: Bringing the \Thesaurus for Economics" on to the Web of Linked
Data. In: Bizer, C., Heath, T., Berners-Lee, T., Idehen, K. (eds.) LDOW. CEUR
Workshop Proceedings, vol. 538. CEUR-WS.org (2009), http://dblp.uni-trier.
de/db/conf/www/ldow2009.html#Neubert09
10. Ruther, M., Fock, J., Bandholtz, T., Schulte-Coerne, T.: Linked Environment Data.
          </p>
          <p>In: Gerlinde Knetsch, K.J. (ed.) Umweltbundesamt. pp. 89{92. Umweltbundesamt
(2010), ISSN 1862-4804</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Albertoni</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martino</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franco</surname>
            ,
            <given-names>S.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santis</surname>
            ,
            <given-names>V.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plini</surname>
            ,
            <given-names>P.:</given-names>
          </string-name>
          <article-title>EARTh: An Environmental Application Reference Thesaurus in the Linked Open Data cloud</article-title>
          .
          <source>Semantic Web</source>
          <volume>5</volume>
          (
          <issue>2</issue>
          ),
          <volume>165</volume>
          {
          <fpage>171</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Caracciolo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stellato</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morshed</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannsen</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rajbhandari</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jaques</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keizer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <source>The AGROVOC Linked Dataset. Semantic Web</source>
          <volume>4</volume>
          (
          <issue>3</issue>
          ),
          <volume>341</volume>
          {
          <fpage>348</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Chiarcos</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sukhareva</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>OLiA { Ontologies of Linguistic Annotation</article-title>
          .
          <source>Semantic Web</source>
          <volume>6</volume>
          (
          <issue>4</issue>
          ) (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>