<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Challenges of Terminology Extraction from Legal Spanish Corpora</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Patricia</forename><surname>Martín-Chozas</surname></persName>
							<affiliation key="aff0">
								<orgName type="laboratory">Ontology Engineering Group</orgName>
								<orgName type="institution">Universidad Politécnica de Madrid</orgName>
							</affiliation>
						</author>
						<author role="corresp">
							<persName><forename type="first">Pablo</forename><surname>Calleja</surname></persName>
							<email>pcalleja@fi.upm.es</email>
							<affiliation key="aff0">
								<orgName type="laboratory">Ontology Engineering Group</orgName>
								<orgName type="institution">Universidad Politécnica de Madrid</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Challenges of Terminology Extraction from Legal Spanish Corpora</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">84EB0158553A958DBE6D6093BAE78D31</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T04:58+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Legal terminology</term>
					<term>Automatic Term Extraction</term>
					<term>Natural Language Processing</term>
					<term>Semantic Web Technologies</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Untangling the complexities of legal documentation is an imperative need for non practitioners of the legal profession. The terminology used in the domain is complex and it usually requires expert knowledge to be fully understood, since the legal framework is constantly being updated and the meaning of terms vary accordingly. Non-proprietary Automatic Terminology Extraction (ATE) tools are required in this particular domain in which documents contain private and sensitive data. This paper describes methods for obtaining accurate legal terms from labour law corpora, overcoming the difficulties present in the area, and also analyses the peculiarities of the legal jargon, specifically, in Spanish language. The performed experiments, executed with JATE, a wellknown open source library in the ATE literature, are still preliminary, but promising.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>As evidenced by legal summaries published in Eurlex <ref type="foot" target="#foot_0">1</ref> , legal documentation such as laws, directives, decrees and even regular notices are often complex to understand by general public: legal terminology can be a real headache for people that are not used to this type of language. At the same time, many citizens and businesses across the European Union have to deal with significant compliance problems: breach of contracts, overdue debts, excessive working hours, etc.</p><p>With the aim of softening such complications, this paper proposes to retrieve legal terms from Spanish corpora through Automatic Term Extraction (ATE) techniques. Such legal terms are understood as words and multi-word expressions with a specific meaning within a legal text; collections of such terms are considered terminologies. These terminologies could be afterwords interlinked with other language resources to share information, which contributes to obtain definitions, translations and context, easing the comprehension of legal documentation.</p><p>ATE is a well-known technique in Natural Language Processing (NLP) that supports important tasks such as machine translation, speech recognition or information retrieval, to mention but a few. Several tools are already offering this kind of technology; however, many of them still present unresolved limitations, such as noise generation, disambiguation issues or performance, delays with big corpora, which are some of the most frequent. Here, two additional limitations have been identified as crucial when dealing with legal information: domain specificity and data privacy. Current ATE tools find difficulties when extracting highly-specific legal expressions and, on the other hand, they might include personal data such as proper names and identity numbers in the resulting term lists.</p><p>For this reason, this contribution proposes to configure the tool JATE <ref type="bibr" target="#b12">[13]</ref> to extract terminology from the legal domain by analysing the peculiarities of the legal language and adapting the extraction patterns to this jargon.</p><p>The first use case has been developed within the Lynx project, which has provided the Spanish legal corpus<ref type="foot" target="#foot_1">2</ref> used in the experiments. Lynx project<ref type="foot" target="#foot_2">3</ref> is an H2020 Innovation Action towards the creation of a Knowledge Graph of legal and regulatory data from different jurisdictions and languages. This Legal Knowledge Graph interlinks multilingual legal information and provides explanations and context for legal expressions appearing in each document.</p><p>The terms extracted with the model developed here contribute to the creation of this platform that help European citizens understand legal documentation without having to invest time and money in specific legal consulting.</p><p>JATE was originally developed for English terminology extraction; since this use case deals with Spanish corpora, it was also required an extension of the tool to cover Spanish language.</p><p>This paper is organised as follows: Section 3 presents the related work on term extraction technologies, Section 2 exposes the motivation behind this contribution and the analysis of the problem, Section 4 describes the experiments performed during this work and finally Section 5 includes conclusions and future work to be performed in next stages.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Motivation</head><p>Some hints of the motivation behind this project have already been presented in the introduction: legal documentation is an unsolvable puzzle for laymen and non-practitioners of the legal domain.</p><p>In addition, many of the available legal language resources are not in machine readable formats yet. The major part is published as PDF, which hinders their look-up, and some of them are still distributed in physical format.</p><p>The work proposed here tackles this situation by researching on a most accurate terminology extraction methodology from those machine-readable legal documents with the aim of creating new language resources that can be processed by the newest technologies.</p><p>A higher level of accuracy in the extracted terms means less time and money invested in human post processing of the resulting term list. However, the most important advantage lays on the efficacy of Semantic Web technologies: accurate legal terms can easily be linked with other legal language resources, offering users more information such as translations, synonyms, context and related terms. This additional information can help them improve their comprehension of the legal documentation.</p><p>Available tools present several limitations, and only a few of them are open source. This means a major drawback since one of the ideas of this contribution is to avoid using proprietary software to address privacy issues.</p><p>Also, a common shortcoming of web based applications is personal data management. Legal documents contain private data and it may not be safe to upload them on a web-based tool. In the Lynx project, both public and sensitive documents are being handled, thus, data privacy is an important factor to keep in mind.</p><p>Since JATE is an open source framework, it allows the use of a given algorithm selected by the user and even the creation of new ones. This work includes the extension of the tool to cover terminology extraction from Spanish corpora, the analysis of the labour law corpora provided by Lynx partners to discover specific patterns of legal language and the configuration of such patterns in the tool with the aim of extracting more accurate terms.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Related Work</head><p>Prior to the availability of term extraction tools, this activity was carried out by domain experts and terminology professionals. Despite being the most accurate manner for terminology extraction, it is also the most expensive and timeconsuming. Taking into account the amount of information generated nowadays, human terminology extraction is unpractical.</p><p>For this reason, automatic term extraction technologies have been extensively studied in the literature <ref type="bibr" target="#b3">[4]</ref> and several tools based on statistical and linguistic methods have already been developed.</p><p>In previous work, a comparative evaluation of available ATE tools has been performed <ref type="bibr" target="#b10">[11]</ref>. Each of them presents different features depending on the format of the tool, typology of the targeted corpus, supported languages, types of extracted terms, etc.</p><p>Many of the tools analysed are web based applications: Translated.net<ref type="foot" target="#foot_3">4</ref> , Ter-moStat <ref type="foot" target="#foot_4">5</ref> and FiveFilters<ref type="foot" target="#foot_5">6</ref> , for instance, are free tools that can be accessed online.</p><p>However, some of the issues found in the evaluation above mentioned include the extraction of stop words, visualisation of terms only in the website (not downloadable) and difficulties to find terms from specific domains.</p><p>Other tools offer payable services, such as SketchEngine<ref type="foot" target="#foot_6">7</ref> , which is a sophisticated tool with a good performance and additional services <ref type="bibr" target="#b9">[10]</ref>. Still, this application presents some difficulties in dealing with big corpora: at least in the trial version, files need to be attached one by one.</p><p>On the other hand there are other downloadable tools available, such as TBXTools<ref type="foot" target="#foot_7">8</ref> and TermSuite<ref type="foot" target="#foot_8">9</ref> . The first one has been developed to offer domain and language independent services, thus, implemented patterns might be too general; and the latter does not extract compound terms, the main feature of legal jargon.</p><p>This contribution uses the open source library JATE<ref type="foot" target="#foot_9">10</ref> , since it integrates the most important terminology extraction algorithms and can be integrated in a local Solr indexer. Furthermore, it can also process large corpora and be extended for other languages or for different purposes, such as the Spanish legal domain.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Experiments</head><p>In the first place, subsection 4.1 describes the extension of JATE for Spanish language and the initial set of patterns applied. Secondly, subsection 4.2 contains an analysis of the features of legal terminology, specifically within Spanish labour law corpora. Afterwards, subsection 4.3 proposes the Spanish language patterns to be configured in JATE based on the analysis above mentioned. Lastly, subsection 4.4 contains a description of the extraction tests performed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">JATE extension for Spanish</head><p>JATE has implemented ten algorithms: TTF, ATTF, TTF-IDF, RIDF, CValue, X2, RAKE, Weirdness, GlossEx and TermEx.</p><p>In these experiments, only Cvalue [2] and TTF-IDF <ref type="bibr" target="#b8">[9]</ref> have been used, since the former is intended for multi-word term extraction, one of the main features of legal documents, while the latter measures the significance each term of based on its frequency on the corpus.</p><p>JATE relies on the OpenNLP library <ref type="foot" target="#foot_10">11</ref> for tasks such as tokenisation, sentence segmentation, part-of-speech (POS) tagging and chunking, being the last two the most significant to process Spanish documents. For the POS tagging in Spanish, a model trained for version 1.3 has been adapted to the latest version. The different POS tags are coded with Cast3LB format <ref type="bibr" target="#b2">[3]</ref>, a freely available treebank for Spanish (see morphological tagset in Figure <ref type="figure" target="#fig_0">1</ref>). For the chunking in Spanish, there are no trained models available. However, JATE allows the creation of patterns to identify chunks in natural language based on POS tags. This chunks will reflect potential candidate terms. The Spanish patterns were built from a general corpus composed by newspapers and general articles as per the morphological instructions in Figure <ref type="figure" target="#fig_0">1</ref>:</p><p>In order to create the Spanish patterns, previous work with English tagsets has been taken as a reference <ref type="bibr" target="#b6">[7]</ref>. Such patterns have been translated to the Spanish POS tags and modified according to the grammatical structures of the Spanish language <ref type="bibr" target="#b4">[5]</ref>. Some peculiarities of the patterns showed in Figure <ref type="figure" target="#fig_1">2</ref> are, for instance, that only common nouns have been considered to be extracted as simple terms. Verbs and adjectives of general knowledge tend to be less relevant when building a domain independent vocabulary. Hence, their tags have not been added to the patterns to avoid noise generation. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Analysis of legal corpora</head><p>The patterns exposed in the previous section were intended for general information extraction. However, legal language has its own peculiarities that need to be considered <ref type="bibr" target="#b5">[6]</ref> [8]:</p><p>-Long and intricate sentences -Scarce punctuation marks -Expressions in foreign languages (usually Latin) (e.g. inter alia) -Rare and complex expressions only used in a legal context:</p><p>• Legal terms of art: technical words with exact meaning that cannot be replaced by other terms (e.g. comodato, meaning "bailment") • Legal jargon: terms and expressions used by lawyers, often archaic and obsolete words (e.g. lo antedicho, meaning "the aforesaid") • Terms from the general language with a different meaning in the legal domain (e.g. furnish, meaning "to provide something or send something")</p><p>These terms should be identified since, although in a general context they may have little significance, they are relevant in a legal context.</p><p>The labour law corpus used for this experiment is composed by 20 documents containing information on national company agreements from different regions in Spain. Keeping the previous characteristics in mind, this corpus was analysed before the extraction and the following considerations regarding legal terminology were raised:</p><p>-The major part of the terms are multiword expressions (e.g. convenio colectivo, Boletín Oficial del Estado, grupo profesional ) -Many of these multiword expressions are built with prepositions and contractions connecting their elements (e.g. comité de empresa, prevención de riesgos laborales, estatuto del trabajador )</p><p>-Some types of words that in a general context are not considered terms, such verbs and adjectives, in the legal domain do need to be extracted as terms since they have specific meaning (e.g. vigente, enunciativo, devengar, retribuir ) -For the purposes of these experiments, proper names are not considered legal terms and must be avoided in the extraction stage (e.g. Comunidad de Madrid, Principado de Asturias, empresa Hermanos Fernández ) -Similarly, URLs, numbers and dates must also be kept out from the resulting termlists (e.g."https://www.boe.es/") -Finally, terms including ordinal adjectives that in other jurisdictions may have a unique meaning, such as the "Third Amendment", do not exist in Spanish legislation, so these types of words should not be extracted</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Proposal of Spanish legal language patterns</head><p>Thus, the first version of the Spanish general patterns was modified accordingly. Some of the patterns were removed and other new tag configurations were added: On the other hand, other patterns have been removed to avoid noise generation, since they were not considered relevant for legal terminology:</p><p>-(\bAO\b) (\bNC\b): Adjective Ordinal + Noun Common (e.g. Third Amendment) -(\bNC\b) (\bNC\b): Noun Common + Noun Common. This pattern was deleted since it was observed that the POS tagger sometimes tags proper nouns as NC (common nouns), and the tool extracts structures that are not real terms, such as empresa Apple. -Patterns that link several common nouns or several adjectives have also been removed, since they are very extended in English but not in Spanish grammar which, normally, uses prepositions to separate each component of the term.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.4">Extraction tests</head><p>The testing corpus provided by Lynx partners contains 20 files comprised of 21,475 tokens in TXT format that have been automatically converted apart from PDF files from the labour law domain in Spanish. Two tests have been performed over the Lynx corpus, one per pattern set:</p><p>-Extraction tests with Cvalue and TTF-IDF algorithms applying the General Spanish patterns. Samples of the most relevant extracted terms are convenio colectivo (collective agreement), dirección de la empresa (company management), empresa (company) and trabajador (worker). -Extraction tests with Cvalue and TTF-IDF algorithms applying the Legal Spanish patterns. Most of the main terms recognised with the general Spanish patterns still remain in the same positions with similar scores. However, legal patterns have introduced new relevant terms in the legal domain such as vacaciones por antigüedad (seniority holidays), asambleas convocadas por el comité (committeeorganised assemblies), documentos relativos a la liquidación (liquidation documents), jubilado (retired) or disciplinarios (discplinary).</p><p>From the resulting lists of terms, sorted by relevance, the first 200 terms<ref type="foot" target="#foot_11">12</ref> have been considered as the most meaningful, since they have significance in their scores. In this context, "relevant terms" are those legal expressions that can be used to annotate and classify documents by topic or typology, this is, terms that represent the legal domain. Table <ref type="table">1</ref> collects some of the new extracted by JATE, applying the Spanish Legal Patterns <ref type="foot" target="#foot_12">13</ref> . and adjectives are extracted as common nouns, spoiling the patterns. Training the model again with larger corpora from the domain would avoid many of these mistaken tags.</p><p>Also, not all the extracted terms are relevant for the legal domain. Some terms (e.g. sanitario, dura, mixta) do not belong to the legal terminology, so it would be required to generate a list with terms from the general usage to escape such extractions in future experiments.</p><p>On the other hand, many of the wrong extractions are caused by tokenisation mistakes in the original corpus: clean and well structured source documents would avoid this issue. Moreover, other libraries such as IXA Pipes <ref type="bibr" target="#b0">[1]</ref> cover better NLP tasks for Spanish Language. It is proved that its POS tagger retrieves better results for Spanish corpora and it uses EAGLE tags 14 for the word classes, which contain more information about them (e.g, gender, number, form). Even though patterns would require to be coded again, they could represent much more grammatical content.</p><p>Another immediate convenient step to improve and generate a sound set of legal patterns is to consult grammatical peculiarities of legal language with actual legal experts: lawyers, prosecutors, judges, law students, etc., since these professionals are the best knowledge source of this domain.</p><p>On the whole, these experiments have been performed to highlight the importance of developing terminology extractors without the need of using online platforms for domains that deal with sensible data that cannot be distributed to third parties.</p><p>Regarding the use of JATE, the best approach here is to use several algorithms (in this case, Cvalue and TTF-IDF) with different features and performances to get more comprehensive results and to get a better overview of terms of the corpus. For instance, in the experiments, the results have shown the importance of the nominal chunks in the corpus although there are adjectives and nouns that are importance by themselves.</p><p>Also, since the tool allows the implementation and creation of new algorithms, another interesting experiment is the testing of other existing algorithms such KEA <ref type="bibr" target="#b11">[12]</ref>, used by other available tools, and the generation of a customised algorithm for legal language to test its accuracy.</p><p>Finally, although in these experiments only public data have been handled, a future line of work would be focused on identifying sensitive data to identify and remove named entities of persons and organizations in a given corpus to treat personal and private data. Furthermore, entity linking processes of the retrieved terms are also considered in order to validate accuracy of the terms, and search for related terms in relevant knowledge bases.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 .</head><label>1</label><figDesc>Figure 1. Morphological tagset of Cast3LB</figDesc><graphic coords="5,186.67,261.22,242.02,125.58" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 .</head><label>2</label><figDesc>Figure 2. First configuration of Spanish general terminology patterns</figDesc><graphic coords="6,203.93,115.84,207.49,161.76" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 .</head><label>3</label><figDesc>Figure 3. First configuration of Spanish legal terminology patterns</figDesc><graphic coords="7,203.93,340.79,207.49,129.86" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://eur-lex.europa.eu</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">http://data.lynx-project.eu/dataset/llcorpuses</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">http://lynx-project.eu/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://labs.translated.net/terminology-extraction/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">http://termostat.ling.umontreal.ca/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://fivefilters.org/term-extraction/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">https://www.sketchengine.eu/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">https://sourceforge.net/projects/tbxtools/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_8">http://termsuite.github.io/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="10" xml:id="foot_9">https://github.com/ziqizhang/jate</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_10">http://opennlp.apache.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_11">http://doi.org/10.5281/zenodo.2385437</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="13" xml:id="foot_12">https://github.com/oeg-upm/terminology-extractor</note>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>New terms Cvalue</head><p>New terms TTF-IDF • trabajador tendrá (worker will have) • conocimientos adquiridos en el desempeño (acquire knowledge during the performance) • ley de prevención de riesgos (risk prevention law) • representación legal de los trabajadores (legal representation of workers) • firma del presente (signing the present) • texto refundido de la ley (combined text of law)</p><p>• bocmboletín oficial de la comunidad (bocmofficial bulletin of the community) • entrada en vigor del presente (implementation of the present contract) • miembros del comité de empresa (members of the company committee) • comisión mixta de interpretación (mixed interpretation commission) • boletín oficial de la comunidad (official bulletin of the community) • boletín oficial de la junta (official bulletin of the council) From this table, the following considerations can be educed:</p><p>-New terms retrieved by CValue algorithm are comprised of multiword terms.</p><p>The algorithm has been enriched with more complex nominal chunks that are relevant in the corpus. However, for the TTF-IDF algorithm, the main results retrieved are based on the individual terms, in this case adjectives. -The tool presents some tagging mistakes: the term trabajador tendrá has not correctly been extracted, since the last component is a verb and there is not such pattern in the set. From the configuration of the patterns, the tool has tagged this verb as a common noun or a qualifying adjective (see Figure <ref type="figure">3</ref>). -Also, there might be some tokenisation mistakes in the source corpus, since the term bocmboletín oficial de la comunidad has not been correctly extracted either. Another possibility is that the PDF to TXT conversion inserted mistakes such this one in the source files. The quality of the source file must be reviewed and improved.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions and future work</head><p>Results present little variations: 6% of new terms applying legal patterns with Cvalue and 3.5% with TTF-IDF. This situation is mainly given by POS tagging mistakes: the tool tends to tag any unknown word as common noun since it is the most frequent type of word in texts. Thus, some proper names, URLs, verbs</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Ixa pipeline: Efficient and ready to use multilingual nlp tools</title>
		<author>
			<persName><forename type="first">R</forename><surname>Agerri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bermudez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Rigau</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">LREC</title>
				<imprint>
			<date type="published" when="2014">2014</date>
			<biblScope unit="volume">2014</biblScope>
			<biblScope unit="page" from="3823" to="3828" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A methodology for automatic term recognition</title>
		<author>
			<persName><surname>Ananiadou</surname></persName>
		</author>
		<ptr target="http://www.lsi.upc.es/nlp/tools/parole-sp.html" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 15th conference on Computational linguistics-Volume 2</title>
				<meeting>the 15th conference on Computational linguistics-Volume 2</meeting>
		<imprint>
			<publisher>Association for Computational Linguistics</publisher>
			<date type="published" when="1994">1994</date>
			<biblScope unit="page" from="1034" to="1038" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Building cast3lb: A spanish treebank</title>
		<author>
			<persName><forename type="first">M</forename><surname>Civit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Martí</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Research on Language and Computation</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="549" to="574" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Nine terminology extraction tools: Are they useful for translators? Multilingual</title>
		<author>
			<persName><forename type="first">H</forename><surname>Costa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Zaretskaya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">C</forename><surname>Pastor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Seghiri</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">A</forename><surname>Española</surname></persName>
		</author>
		<title level="m">Nueva gramática de la lengua española</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Legal English</title>
		<author>
			<persName><forename type="first">R</forename><surname>Haigh</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2018">2018</date>
			<publisher>Routledge</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">The acl rd-tec: a dataset for benchmarking terminology extraction and classification in computational linguistics</title>
		<author>
			<persName><forename type="first">S</forename><surname>Handschuh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Qasemizadeh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">COLING 2014: 4th International Workshop on Computational Terminology</title>
				<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">La ambigüedad en el lenguaje jurídico: su diagnóstico e interpretación a través de la lingüística forense</title>
		<author>
			<persName><forename type="first">A</forename><surname>Hidalgo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Anuari de Filologia. Estudis de Lingüística</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="page" from="73" to="96" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Technical terminology: some linguistic properties and an algorithm for identification in text</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">S</forename><surname>Justeson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">M</forename><surname>Katz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Natural language engineering</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="9" to="27" />
			<date type="published" when="1995">1995</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">The sketch engine: ten years on</title>
		<author>
			<persName><forename type="first">A</forename><surname>Kilgarriff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Baisa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bušta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Jakubíček</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Kovář</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Michelfeit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Rychlỳ</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Suchomel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lexicography</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="7" to="36" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Towards a Linked Open Data Cloud of language resources in the legal domain</title>
		<author>
			<persName><forename type="first">P</forename><surname>Martín Chozas</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2018">2018</date>
			<publisher>UPM</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Kea: Practical automated keyphrase extraction</title>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">H</forename><surname>Witten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">W</forename><surname>Paynter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Frank</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gutwin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">G</forename><surname>Nevill-Manning</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Design and Usability of Digital Libraries: Case Studies in the Asia Pacific</title>
				<imprint>
			<publisher>IGI Global</publisher>
			<date type="published" when="2005">2005</date>
			<biblScope unit="page" from="129" to="152" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Jate 2.0: Java automatic term extraction with apache solr</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Gao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Ciravegna</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">LREC</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
