Benjamin Aw
Add updated pkl file v3
6fa4bc9
{
"paper_id": "W19-0315",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T06:19:23.696769Z"
},
"title": "The use of Extract Morphology for Automatic Generation of Language Technology for Votic",
"authors": [
{
"first": "Kristian",
"middle": [],
"last": "Kankainen",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "University of Tartu Institute of Estonian and General Linguistics",
"location": {}
},
"email": "[email protected]"
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "The article presents a source code generating extension to Spr\u00e5kbanken's morphological dictionary building tool, the \"Morphology lab\". This is done for three reasons: 1) to include the speech community in the morphological dictionary making 2) to enable a time-resistant, human readable description of Votic morphology 3) source code generation minimizes the efforts keeping multiple language technologies in sync when the morphological dictionary is updated. The morphological dictionary tool uses Extract Morphology that extracts the paradigm descriptions automatically from user input inflection tables. In this way the user's linguistic and technological knowledge is kept at a bare minimum. The presented extension encodes both the lexical information and the procedural paradigm descriptions into the ISO standard Lexical Markup Framework (LMF). From this central representation program source code is generated for morphological analysis and synthesis modules in two language technological systems: the Grammatical Framework and the Giellatekno infrastructure. Integration into the Giellatekno infrastructure is still work in progress, but the extension has allready been successfully used as a continuous integration platform for developing the morphology module of the Votic Resource Grammar Library in the Grammatical Framework. In the end the article discusses four main implications of the presented approach: 1) the work on morphology is reduced to an interface similar to Wiktionary, 2) the lexical resource is put in the middle, 3) the general benefits of source code generation, 4) benefits of lemma form agnosticity inherent in the approach. Teesid Artikkel tutvustab koodigenereerimise laiendust Spr\u00e5kbankeni morfoloogiliste s\u00f5naraamatute koostamiss\u00fcsteemile. Laiendusel on kolm eesm\u00e4rki: 1) kaasamaks k\u00f5nelejaskonda morfoloogilise s\u00f5nastiku koostamisprotsessi; 2) v\u00f5imaldada arhiveeritava ja inimloetava morfoloogiakirjelduse koostamise; 3) koodigenereerimine minimeerib j\u00f5upingutused, et hoida mitut r\u00f6\u00f6pset keeletehnoloogiat ajakohastena morfoloogilise s\u00f5naraamatu uuendamise puhul. Morfoloogilise s\u00f5naraamatu koostamiss\u00fcsteem p\u00f5hineb ekstraktmorfoloogial, mis eraldab automaatselt paradigmakirjelduse t\u00fc\u00fcps\u00f5na muutvormitabelist. Sellisel viisil viiakse kasutaja vajatud keelelised ja tehnoloogilised teadmised miinimumi.",
"pdf_parse": {
"paper_id": "W19-0315",
"_pdf_hash": "",
"abstract": [
{
"text": "The article presents a source code generating extension to Spr\u00e5kbanken's morphological dictionary building tool, the \"Morphology lab\". This is done for three reasons: 1) to include the speech community in the morphological dictionary making 2) to enable a time-resistant, human readable description of Votic morphology 3) source code generation minimizes the efforts keeping multiple language technologies in sync when the morphological dictionary is updated. The morphological dictionary tool uses Extract Morphology that extracts the paradigm descriptions automatically from user input inflection tables. In this way the user's linguistic and technological knowledge is kept at a bare minimum. The presented extension encodes both the lexical information and the procedural paradigm descriptions into the ISO standard Lexical Markup Framework (LMF). From this central representation program source code is generated for morphological analysis and synthesis modules in two language technological systems: the Grammatical Framework and the Giellatekno infrastructure. Integration into the Giellatekno infrastructure is still work in progress, but the extension has allready been successfully used as a continuous integration platform for developing the morphology module of the Votic Resource Grammar Library in the Grammatical Framework. In the end the article discusses four main implications of the presented approach: 1) the work on morphology is reduced to an interface similar to Wiktionary, 2) the lexical resource is put in the middle, 3) the general benefits of source code generation, 4) benefits of lemma form agnosticity inherent in the approach. Teesid Artikkel tutvustab koodigenereerimise laiendust Spr\u00e5kbankeni morfoloogiliste s\u00f5naraamatute koostamiss\u00fcsteemile. Laiendusel on kolm eesm\u00e4rki: 1) kaasamaks k\u00f5nelejaskonda morfoloogilise s\u00f5nastiku koostamisprotsessi; 2) v\u00f5imaldada arhiveeritava ja inimloetava morfoloogiakirjelduse koostamise; 3) koodigenereerimine minimeerib j\u00f5upingutused, et hoida mitut r\u00f6\u00f6pset keeletehnoloogiat ajakohastena morfoloogilise s\u00f5naraamatu uuendamise puhul. Morfoloogilise s\u00f5naraamatu koostamiss\u00fcsteem p\u00f5hineb ekstraktmorfoloogial, mis eraldab automaatselt paradigmakirjelduse t\u00fc\u00fcps\u00f5na muutvormitabelist. Sellisel viisil viiakse kasutaja vajatud keelelised ja tehnoloogilised teadmised miinimumi.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "The presented system is part of a broader work on defining a normative description of Votic morphology to be used in corpus planning, language teaching and language revitalization efforts.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "There was no literature developed for Votic in the 1930s (unlike for Karelian, Veps, Ingrian and other languages in the Soviet Union). But still the Votic language has many linguistic descriptions, including grammars (e.g. Ahlqvist (1856), Tsvetkov (2008) , Ariste (1968) , \u041c\u0430\u0440\u043a\u0443\u0441 and \u0420\u043e\u0436\u0430\u043d\u0441\u043a\u0438\u0439 (2011)) and big (electronic) dictionaries (Tsvetkov (1995) , Gr\u00fcnberg et al. (2013) ) but very few that gives definitive answers to language learners asking how is lexeme xyz in genitive form? For this a standardization or normative description of the morphology is needed. Metaphorically, the presented system tries to give the fishing rod instead of only the fish. That is, to give to the language community not only the normative morphology but a system where the normative can be altered. This is seen as crucial for the group of less than 20 active Votic language activists.",
"cite_spans": [
{
"start": 240,
"end": 255,
"text": "Tsvetkov (2008)",
"ref_id": "BIBREF16"
},
{
"start": 258,
"end": 271,
"text": "Ariste (1968)",
"ref_id": "BIBREF3"
},
{
"start": 337,
"end": 353,
"text": "(Tsvetkov (1995)",
"ref_id": "BIBREF15"
},
{
"start": 356,
"end": 378,
"text": "Gr\u00fcnberg et al. (2013)",
"ref_id": "BIBREF8"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "To minimize efforts, a morphological dictionary is compiled in such a way that it can be used both as a reference guide of the normative morphological description and as a basis for automatically generating the source codes implementing the morphological analysis and synthesis modules for two language technological platforms: the Giellatekno infrastructure and the Grammatical Framework.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Planned future applications for the generated morphological modules is proofing tools obtained from the integration with Giellatekno's infrastructure, and a bilingual Russian-Votic phrasebook application done in the Grammatical Framework.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The morphological dictionary is built with an existing tool called the \"Morphology Lab\". The presented method is not language dependent, but so far work has only been done with the Votic language. The most language dependent part of the system is the type system for the generated Grammatical Framework source code and this concerns only the optimization of computer memory usage.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The system has been successfully used for continuous integration when working on the morphology module of the Votic Resource Grammar Library in the Grammatical Framework. New paradigm functions has continuously and automatically been added to the morphology module when the corresponding words' inflection tables have been added to the dictionary through the Morphology Lab.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Initial work for generating source code and integrating with the Giellatekno infrastructure is presented. This is work in progress that has not been deployed nor fully tested.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The article first presents the Morphology Lab tool's workflow for working on the Votic morphological dictionary and how it uses Extract Morphology for paradigm extraction. Section 3 introduces source code generation and section 3.1 how the morphological dictionary's data is used as its ontology represented in the Lexical Markup Framework. Section 3.2 explains the source code generation for GF and section 3.3 for Giellatekno. Lastly, section 4 discusses the advantage and main implications of using the presented approach. Generated source code examples are added at the end.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The Morphology Lab is a separate online tool for working with morphological dictionaries. It was created as a prototype to integrate Extract Morphology into Spr\u00e5kbanken's lexical infrastructure Karp. It uses Extract Morphology to predict correct paradigms for new lexical entries, and to extract new paradigms not yet existing in the system from user input example inflection tables. It also integrates with the corpus tool Korp and shows frequency counts for wordforms in the inflection tables.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "The workflow for building the Votic morphological dictionary with the Morphology Lab has been straight forward. Although no users from the Votic speech community has yet been found, the tool is seen simple enough to encourage their inclusion.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "For a new entry, the user first inserts the new word (or any of its wordforms) and chooses the correct paradigm(s) for it. The paradigm can be specified either by inserting another word that shares the same paradigm or by reviewing the generated inflection tables and choosing the appropriate one(s). The generated inflection tables show for each wordform also their frequency count in a corpus.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "If a correct paradigm does not yet exist in the system, the user has to input all wordforms in the inflection table which is then saved as a new paradigm. The user can do this by filling a blank inflection table or by editing wordforms in a generated (wrong) inflection table. The newly saved paradigm is directly reflected in the system and can be chosen when adding the next new entry to the system. Next we will introduce Extract Morphology. The paradigm extraction facility of Extract Morphology has been proposed as a more natural way for a linguist to define a computational morphology (Forsberg (2016)) as it doesn't rely on any specific knowledge other than wordforms. It has been presented in detail in (Ahlberg et al. (2014)) and (Ahlberg et al. (2015) ). Extract Morphology has been used for deriving morphological guessers as weighted and unweighted finite state transducers (Forsberg and Hulden (2016) ). The design of its extraction techniques in finite state calculus has been presented more thoroughly in (Hulden (2014)).",
"cite_spans": [
{
"start": 712,
"end": 735,
"text": "(Ahlberg et al. (2014))",
"ref_id": "BIBREF0"
},
{
"start": 740,
"end": 762,
"text": "(Ahlberg et al. (2015)",
"ref_id": "BIBREF1"
},
{
"start": 887,
"end": 914,
"text": "(Forsberg and Hulden (2016)",
"ref_id": "BIBREF6"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "At the core, Extract Morphology's paradigm extraction finds the longest common subsequence (LCS) across all wordforms in an inflection table. These common parts are used as a technical stem for defining the lexeme. The common and non-common parts make up concatenation patterns for each wordform.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "As a simplified example, consider the two wordforms t\u0161iutto and t\u0161iutod ('shirt'). Their longest common subsequences are highlighted in table 1.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "The common parts are abstracted away into variables and thus define concatenation templates for the paradigm's wordforms, such as:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "x 1 \u2295 t \u2295 x 2 and x 1 \u2295 x 2 \u2295 d.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "It is obvious that replacing the variables with the values x 1 =t\u0161iut and x 2 =o recreates the inital inflection can also be instantiated, for example x 1 =kat and x 2 =o instantiates the lexeme's katto paradigm.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "The technical stem creates a too low-level interface for any practical human use. But by choosing one wordform to be used as lemma, the concatenation pattern can be used to construct a dispatch function that segment the complete lemma wordform into the needed technical stem parts. This approach is illustrated in the Grammatical Framework source code generation in section 3.2.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "Since the technical stem is independent of any wordform in the paradigm, it is also independent from the choice of what is used as the dictionary lemma.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "This has several implications. The choice of lemma form in the dictionary meant for human consumption can be post-poned after analysing the principal parts of the paradigms or consulting the end dictionary users. Also, the choice of lemma form used in the generated language technology need not be the same and can be chosen in accordance to specific needs of each generated software individually. Ideally though, the same form is used in all systems, but the point here is that this choice can be made on-the-go, or when enough data has been collected.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "This kind of lemma agnosticity in the work flow is seen as a good thing for languages that lack a lexicographic tradition and is discussed more closely in section 4.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Workflow: Morphology Lab and Extract Morphology",
"sec_num": "2"
},
{
"text": "Source code generation is a loose term used here to designate the automatic process where program source code is generated from a description or ontology. The ontology describes the what, not the how of the morphological knowledge, whereas the generators transform this knowledge into a program implementation. The implementation is a derived kind of how, trying as close as possible to resemble the original what of the ontology.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Source code generation",
"sec_num": "3"
},
{
"text": "In our work we represent the ontology using the ISO standard Lexical Markup Framework (LMF). All the data recorded by the Morphology Lab is converted into LMF form and this is used as input for the source code generator.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Source code generation",
"sec_num": "3"
},
{
"text": "Two source code generators are presented below, one for the Grammatical Framework and one for the Giellatekno infrastructure. The source code generators are implemented with the XQuery programming language.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Source code generation",
"sec_num": "3"
},
{
"text": "A shared architectural feature of both code generators is the use of translation tables for translating terms used in the LMF ontology to their corresponding terms used in the host environment. For example the names of paradigms are prefixed with as in the LMF (e.g. asT\u0161iutto), but named like actions in the GF (mkT\u0161iutto), and prefixed by their part of speech in Giellatekno (N_T\u0160IUTTO). Also the terminology for grammatical features differ between the environments.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Source code generation",
"sec_num": "3"
},
{
"text": "In this way different terminological traditions are supported and respected.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Source code generation",
"sec_num": "3"
},
{
"text": "The Lexical Markup Framework (LMF, ISO 24613:2008) is an ISO standard for natural language processing lexicons and machine readable dictionaries. It provides a common model for managing exchange of data and enables merging of different resources. (Francopoulo, 2013) . The LMF standard consists of a core model and several extensions. In our work we use two extensions: the NLP Morphological Pattern extension to model the extracted paradigm information, and the Morphology extension to represent each lexeme's inflected wordforms.",
"cite_spans": [
{
"start": 247,
"end": 266,
"text": "(Francopoulo, 2013)",
"ref_id": "BIBREF7"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "Representing the lexeme's morphology with both paradigms (describing in intension) and inflected wordform tables (describing in extension) might seem superfluous. But both representations serve their own purpose.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "Listing extensionally all inflectional wordforms for each lexeme is in this work considered part of documentation and what adds value to the work's 50-year perspective (discussed in section 4).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "Recording lexeme's all inflected wordforms extensionally also creates the possibility to further annotate the individual wordforms, such as real attested corpus attestations, or other meta-linguistic information such as judgements.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "Listing wordform information explicitly is also beneficial for the dictionary system, enabling quick searches and statistics.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "Next, we will introduce our data and how it is represented in the LMF.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Lexical Markup Framework",
"sec_num": "3.1"
},
{
"text": "All lexical entries carry information about their part of speech, their paradigm(s), the (chosen) lemma form, and the inflected wordforms together with their morphosyntactic descriptors. Also some additional information specific to Karp and the Morpholoy Lab is stored. The lexical entry for our simplified example is shown in figure 1.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the lexical entries",
"sec_num": "3.1.1"
},
{
"text": "The extracted paradigms are represented as LMF Morphological Patterns. These hold information about their part of speech and are name-tagged with an ID. The names follow the LMF tradition and are prefixed with as, such as asT\u0161iutto.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the paradigms",
"sec_num": "3.1.2"
},
{
"text": "The LMF Morphological Patterns model all the information extracted by Extract Morphology. The attested variable values, i.e. the technical stems, of all lexemes added in the Morphology Lab is saved. This information could be utilized to integrate prediction models into the generated source code, as have been demonstrated by Forsberg and Hulden (2016) . This has not been done, as the work has focused on integrating the lexical resources as a first stage.",
"cite_spans": [
{
"start": 326,
"end": 352,
"text": "Forsberg and Hulden (2016)",
"ref_id": "BIBREF6"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the paradigms",
"sec_num": "3.1.2"
},
{
"text": "The extracted paradigm's concatenation patterns are represented as LMF Transform Sets. These hold, for each inflected wordform, the morphosyntactic description and an ordered list of Processes which model the concatenation of constant strings (e.g. the non-common parts) and instantiable variables (e.g. the common parts, the LCS).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the paradigms",
"sec_num": "3.1.2"
},
{
"text": "Furthermore, the full LMF Lexical Resource also holds global meta information such as language name and language code. This is used mainly to name the generated source code files.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the paradigms",
"sec_num": "3.1.2"
},
{
"text": "Thus, for our simplified example we get its extracted paradigm represented as shown in figure 2.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Representing the paradigms",
"sec_num": "3.1.2"
},
{
"text": "Grammatical Framework (GF) is a special purpose programming language for grammars (Ranta, 2011) . It can treat grammars as software libraries called Resource Grammar Libraries (Ranta, 2008) and the aim of the work presented here is to generate the source code that implements the morphology module for the Votic resource grammar library.",
"cite_spans": [
{
"start": 82,
"end": 95,
"text": "(Ranta, 2011)",
"ref_id": "BIBREF14"
},
{
"start": 176,
"end": 189,
"text": "(Ranta, 2008)",
"ref_id": "BIBREF13"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Generating Source Code for the Grammatical Framework",
"sec_num": "3.2"
},
{
"text": "GF's concept of a paradigm is similar to that of Extract Morphology, and writing the source code generator has been intuitive.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating Source Code for the Grammatical Framework",
"sec_num": "3.2"
},
{
"text": "GF is a multilingual framework and each application is expected to define their own semantics in an abstract grammar. No attempt is made to include semantic pivots to the Votic resource, instead a simple monolingual word list is generated as a lexicon.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.2.1"
},
{
"text": "This lexicon specifies for each entry in the resource its lemma, which is appended with its part of speech and a call to the paradigm function. In the case a lemma has multiple paradigms, each one is declared as variants.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.2.1"
},
{
"text": "The GF developer could use this word list when translating the application-specific vocabulary names of the abstract grammar.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.2.1"
},
{
"text": "The source code of the generated word list is illustrated in figure 3.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.2.1"
},
{
"text": "In GF, a paradigm is a function that produces an inflection table. To generate the function for an extracted paradigm description, we need to specify its name, interface and body. The name of the function is the paradigm's ID from the LMF, where the prefix as is simply replaced with mk.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The function's interface is declared in the oper section and parameter types in the param section. The names and values of the parameters reflect the attributes and values of the grammatical features in the lMF, with minor modifications. The oper definition is largely templatic, reflecting only the parts of speech from the LMF.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "To help readers navigate the code, the paradigms are ordered by their part of speech and headers are generated in the form of comments for each part of speech section. These are the only comments generated at the moment.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "Every paradigm is split into two separate functions a high-level dispatch function (mkT\u0161iutto, and low-level to mkT\u0161iuttoConcrete). This is to allow a developer to use the low-level function for debugging or testing purposes.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The high-level function takes a string with the chosen lemma form as its input and splits it into the technical stem parts, which are then simply delegated to the low-level function. An error message is thrown in case the input string is not able to match.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The names of the variables holding the technical stem parts are taken from the paradigm's name.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The low-level, or concrete, function is the one that generates the inflection table. On the left-hand side of the table is the grammatical features and on the right-hand side are the concatenation patterns that instantiates the wordforms.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "Note that GF's implementation of regular expressions is non-greedy as opposed to many other programming languages. Because of this the expression @(-(_+\"t\"+_)) is appended to the last part of the pattern. This expression is automatically created and makes the`t`match the last letter t in the wordform. This matching strategy is suspect to be language dependent.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The source code of the generated morphology module for our example is shown in figure 4 .",
"cite_spans": [],
"ref_spans": [
{
"start": 79,
"end": 87,
"text": "figure 4",
"ref_id": null
}
],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "It can be noticed that the language code is used for naming the module (MorphoVot).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.2.2"
},
{
"text": "The Giellatekno infrastructure has been characterized in Moshagen et al. 2013to be a development environment infrastructure (as opposed to a resource infrastructure), offering a framework for building language-specific analysers and directly turn them into a wide range of useful programs. From the point of view of our work on Votic morphology, the programs of interest are proofing tools and morphological analyzers.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Giellatekno infrastructure source code integration",
"sec_num": "3.3"
},
{
"text": "For the integration with Giellatekno's infrastructure, several components are needed: a lexicon, paradigm descriptions in FST, automatic test declarations, and a Makefile that binds all the components together.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Giellatekno infrastructure source code integration",
"sec_num": "3.3"
},
{
"text": "At the work's current stage all but the Makefile is being generated. Because of this, each component has only been tested on its own but not integrated in the infrastructure.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Giellatekno infrastructure source code integration",
"sec_num": "3.3"
},
{
"text": "We don't include any examples of generated code for the Giellatekno infrastructure because of space considerations. We will only present and discuss the main design choices made.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Giellatekno infrastructure source code integration",
"sec_num": "3.3"
},
{
"text": "Instead of generating the lexicon straight into FST representation, we use Giellatekno's Sanat XML format. This is achieved by simple XML transformations from the LMF format.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.3.1"
},
{
"text": "The Giellatekno infrastructure uses the Sanat XML to generate its own source codes.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.3.1"
},
{
"text": "In its essence, the Sanat XML contains the lexical entry's lemma, the name of the paradigm (e.g a FST continuation class) and the technical stem needed by the continuation class.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.3.1"
},
{
"text": "What is crucially missing from our implementation is the Finnish translation equivalents used as interlingual pivots in the Giellatekno infrastructure. These equivalents will be generated when our work on the Votic morphological dictionary resource has reached the stage of adding them.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the lexicon",
"sec_num": "3.3.1"
},
{
"text": "The FST source code generated for the paradigm functions follow the general structure for realizational morphology introduced in (Karttunen, 2003) . This differs from Giellatekno's tradition of using two-level rules as introduced in Koskenniemi (1983) . This choice should not reflect any ideological stance, it was chosen only for pragmatic reasons.",
"cite_spans": [
{
"start": 129,
"end": 146,
"text": "(Karttunen, 2003)",
"ref_id": "BIBREF10"
},
{
"start": 233,
"end": 251,
"text": "Koskenniemi (1983)",
"ref_id": "BIBREF11"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.3.2"
},
{
"text": "A design decision was made so that currently only the low-level paradigm functions are generated. The segmenting of the lemma is done when generating the dictionary.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating the paradigm functions",
"sec_num": "3.3.2"
},
{
"text": "Tests are optional but used in Giellatekno's infrastructure for verifying that the paradigm functions work as intended.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating tests",
"sec_num": "3.3.3"
},
{
"text": "For verifying generated wordforms they need to be matched with known to be correct wordforms. For this purpose the inflected wordforms stored in the original dictionary are used.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating tests",
"sec_num": "3.3.3"
},
{
"text": "Note that the \"correct\" wordforms are currently the ones generated by the Morphology Lab. This means that the tests now only validate the performance of the generated FST paradigm functions. This could in the future be enhanced when information about corpus attestations or prescriptive information has been added to the Votic dictionary.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Generating tests",
"sec_num": "3.3.3"
},
{
"text": "Giellatekno's template for the Makefile that orchestrates the building of all the components uses two-level of the Giellatekno infrastructure. It is currently not generated by the presented system and will not be discussed here.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "The Makefile",
"sec_num": "3.3.4"
},
{
"text": "It is not yet known, which way of building language technology is the best or most beneficial for different stakeholders. The key points that will be discussed here, with regard to the presented work, is centered around the following four aspects: 1) work on morphology is done through an user interface similar to Wiktionary 2) work on a lexical resource is put in the middle 3) the general benefits of source code generation 4) inherent lemma form agnosticity.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "The work on morphology is reduced to an interface similar to Wiktionary. In the presented approach, all that is needed by the user working on the morphological resource is knowledge of wordforms, not morphology per se.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "This interface brings together the work on creating a normative morphology for Votic, but opens the process up for collaboration with the Votic language community.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Setting up a project in this way, the computational linguist could earlier start working on a higher level (e.g. describing the syntax) and delegate work on the morphology to language activists. By developing traditional GF applications, like the city or foods phrasebooks, the linguist could show the direct effect of the activists adding words to the dictionary and how the words show up in multiple phrases of the phrasebook. This direct connection is hoped to motivate the activists.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Other \"motivators\" are the benefits gained from integration with Giellatekno's infrastructure, mainly the proofing tools. Even though this is an indirect link, it is a parallel and simultaneous benefit.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Advantages of putting the resource in the middle. The key advantage of the presented approach springs out of putting the lexical resource in the middle. Here we keep in mind the LMF representation of the lexical resource. This centrality has several implications.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "One aspect is the technological neutrality this brings. The resource models the procedural (or operational) knowledge of morphology, but this is not reflected in the shape of the resource. The resource does not use terminology from Finite State Transducers, nor from functional programming, even though the resource is used as an ontology for source code generation into both these programming paradigms.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Because of this neutrality, the lexical resource is believed to be readable and understandable in a 50 year perspective, whereas any program code implementing the same kind of knowledge might not be. In fact, a working platform for executing the code will most likely not even exist after 50 years.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "The advantage of this self-documenting aspect is believed to be situated somewhere between the areas of computational linguistics, descriptive linguistics and documentational linguistics. Because of the close connection to language documentation, further research in this area is believed to be a worthwhile endeavor by the authors, especially for small and under-resourced languages.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Another advantage of putting the resource in the middle is that any faults found during the usage of the generated language technology, will get fixed up-streams in the lexical resource itself. In this way it is the resource that gets worked on, not only the language technology. This is highly connected to the benefits of source code generation, discussed next. General benefits of source code generation. The general benefits of using source code generation is that changes need only be done in one place. The usefulness of this gets larger for every added target platform, our work comprises only two.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "By only needing to change faults in one central place might also encourage in the future to keep what is then considered \"old\" software functioning and up to date.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Not only fixing any found faults or simply improving the resource needs to be done in one central place. The centrality of code also ensures consistent style in the generated source code. Changing style throughout all the generated code is done by changing only in one place: in the source code generator.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
},
{
"text": "Benefits of lemma-form agnosticity. The lemmaform agnosticity of the presented approach is seen beneficial to languages that lack a lexicographic tradition. Since Extract Morphology is independent of the choice of which wordform is used as lemma, this choice can be post-poned. This could permit more time and resources to investigate appropriate forms by linguists or lexicographers, or simply give more time to the real dictionary users to get acquainted using the dictionary. <LexicalEntry morphologicalPatterns=\"asT\u0161iutto\"> <feat att=\"partOfSpeech\" val=\"nn\"/> <feat att=\"karp-lemgram\" val=\"t\u0161iutto..nn.1\"/> <Lemma> <feat att=\"writtenForm\" val=\"t\u0161iutto\"/> </Lemma> <WordForm> <feat att=\"writtenForm\" val=\"t\u0161iutto\"/> <feat att=\"grammaticalNumber\" val=\"singular\"/> <feat att=\"grammaticalCase\" val=\"nominative\"/> </WordForm> <WordForm> <feat att=\"writtenForm\" val=\"t\u0161iutod\"/> <feat att=\"grammaticalNumber\" val=\"plural\"/> <feat att=\"grammaticalCase\" val=\"nominative\"/> </WordForm> </LexicalEntry> Figure 1 : LMF representation of the (toy example) lexical entry for t\u0161iutto.",
"cite_spans": [],
"ref_spans": [
{
"start": 996,
"end": 1004,
"text": "Figure 1",
"ref_id": null
}
],
"eq_spans": [],
"section": "Discussion",
"sec_num": "4"
}
],
"back_matter": [
{
"text": "Acknowledgments should be un-numbered last section. Do not include acknowledgements in anonymised review version.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Acknowledgments",
"sec_num": null
},
{
"text": "<feat att=\"id\" val=\"asT\u0161iutto\"/> <feat att=\"partOfSpeech\" val=\"nn\"/> <AttestedParadigmVariableSets> <AttestedParadigmVariableSet> <feat att=\"first-attest\" val=\"t\u0161iutto..nn.1\"/> <feat att=\"1\" val=\"t\u0161iut\"/> <feat att=\"2\" val=\"o\"/> </AttestedParadigmVariableSet> </AttestedParadigmVariableSets> <TransformSet> <GrammaticalFeatures> <feat att=\"grammaticalNumber\" val=\"singular\"/> <feat att=\"grammaticalCase\" val=\"nominative\"/> </GrammaticalFeatures> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddVariable\"/> <feat att=\"variableNum\" val=\"1\"/> </Process> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddConstant\"/> <feat att=\"stringValue\" val=\"t\"/> </Process> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddVariable\"/> <feat att=\"variableNum\" val=\"2\"/> </Process> </TransformSet> <TransformSet> <GrammaticalFeatures> <feat att=\"grammaticalNumber\" val=\"plural\"/> <feat att=\"grammaticalCase\" val=\"nominative\"/> </GrammaticalFeatures> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddVariable\"/> <feat att=\"variableNum\" val=\"1\"/> </Process> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddVariable\"/> <feat att=\"variableNum\" val=\"2\"/> </Process> <Process> <feat att=\"operator\" val=\"addAfter\"/> <feat att=\"processType\" val=\"pextractAddConstant\"/> <feat att=\"stringValue\" val=\"d\"/> </Process> </TransformSet> <MorphologicalPattern> ",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "<MorphologicalPattern>",
"sec_num": null
},
{
"text": "mkT\u0161iutto : Str -> Noun = \\t\u0161iutto -> case t\u0161iutto of { t\u0161iut + \"t\" + o@(-(_+\"t\"+_)) => mkT\u0161iuttoConcrete t\u0161iut o ; _ => Predef.error \"Unsuitable lemma for mkT\u0161iutto\" } ; mkT\u0161iuttoConcrete : Str -> Str -> Noun = \\t\u0161iut,o -> { s = table { NF singular nominative => t\u0161iut + \"t\" + o ; NF plural nominative => t\u0161iut + o + \"d\" } } ; } Figure 4 : Generated source code for the Votic GF morphology module.",
"cite_spans": [],
"ref_spans": [
{
"start": 330,
"end": 338,
"text": "Figure 4",
"ref_id": null
}
],
"eq_spans": [],
"section": "--------------------------------------------------Start of Noun section ------------------------------------------------",
"sec_num": null
}
],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "Semi-supervised learning of morphological paradigms and lexicons",
"authors": [
{
"first": "Malin",
"middle": [],
"last": "Ahlberg",
"suffix": ""
},
{
"first": "Markus",
"middle": [],
"last": "Forsberg",
"suffix": ""
},
{
"first": "Mans",
"middle": [],
"last": "Hulden",
"suffix": ""
}
],
"year": 2014,
"venue": "Proc. of EACL",
"volume": "",
"issue": "",
"pages": "569--578",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Malin Ahlberg, Markus Forsberg, and Mans Hulden. 2014. Semi-supervised learn- ing of morphological paradigms and lexicons. In Proc. of EACL. pages 569-578. http://www.aclweb.org/anthology/E/E14/E14-1.pdf#page=595.",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "Paradigm classification in supervised learning of morphology",
"authors": [
{
"first": "Malin",
"middle": [],
"last": "Ahlberg",
"suffix": ""
},
{
"first": "Markus",
"middle": [],
"last": "Forsberg",
"suffix": ""
},
{
"first": "Mans",
"middle": [],
"last": "Hulden",
"suffix": ""
}
],
"year": 2015,
"venue": "HLT-NAACL",
"volume": "",
"issue": "",
"pages": "1024--1029",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Malin Ahlberg, Markus Forsberg, and Mans Hulden. 2015. Paradigm classifica- tion in supervised learning of morphology. In HLT-NAACL. pages 1024-1029. http://www.aclweb.org/old_anthology/N/N15/N15-1107.pdf.",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Wotisk grammatik jemte spr\u00e5kprof och ordf\u00f6rteckning: (F\u00f6redr. d. 15 Oktober 1855). s.n",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "August Ahlqvist. 1856. Wotisk grammatik jemte spr\u00e5kprof och ordf\u00f6rteckning: (F\u00f6redr. d. 15 Oktober 1855). s.n, [Helsingfors.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "A grammar of the Votic language",
"authors": [
{
"first": "Paul",
"middle": [],
"last": "Ariste",
"suffix": ""
}
],
"year": 1968,
"venue": "Indiana University publications",
"volume": "68",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Paul Ariste. 1968. A grammar of the Votic language. Number vol. 68 in Indiana Uni- versity publications. Uralic and Altaic series. Indiana University ;",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "What can we learn from inflection tables",
"authors": [
{
"first": "Markus",
"middle": [],
"last": "Forsberg",
"suffix": ""
}
],
"year": 2016,
"venue": "BAULT 2016. Helsinki",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Markus Forsberg. 2016. What can we learn from inflection tables? In BAULT 2016. Helsinki. http://blogs.helsinki.fi/language-technology/news/bault-2016/.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "Deriving Morphological Analyzers from Example Inflections",
"authors": [
{
"first": "Markus",
"middle": [],
"last": "Forsberg",
"suffix": ""
},
{
"first": "Mans",
"middle": [],
"last": "Hulden",
"suffix": ""
}
],
"year": 2016,
"venue": "LREC",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Markus Forsberg and Mans Hulden. 2016. Deriving Morphological Analyzers from Example Inflections. In LREC. http://www.lrec- conf.org/proceedings/lrec2016/pdf/1134_Paper.pdf.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "LMF lexical markup framework",
"authors": [
{
"first": "Gil",
"middle": [],
"last": "Francopoulo",
"suffix": ""
}
],
"year": 2013,
"venue": "ISTE Ltd",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Gil Francopoulo. 2013. LMF lexical markup framework. ISTE Ltd ;",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "Vadja keele s\u00f5naraamat =: Va\u010f\u010faa t\u0161eelee s\u00f5na-t\u0161irja = \u0421\u043b\u043e\u0432\u0430\u0440\u044c \u0432\u043e\u0434\u0441\u043a\u043e\u0433\u043e \u044f\u0437\u044b\u043a\u0430",
"authors": [
{
"first": "Silja",
"middle": [],
"last": "Gr\u00fcnberg",
"suffix": ""
},
{
"first": "Ada",
"middle": [],
"last": "Ambus",
"suffix": ""
},
{
"first": "Georg",
"middle": [],
"last": "Gr\u00fcnberg",
"suffix": ""
},
{
"first": "Roman",
"middle": [],
"last": "Kallas",
"suffix": ""
},
{
"first": "Tatjana",
"middle": [],
"last": "Murnikova",
"suffix": ""
},
{
"first": "Tatjana",
"middle": [],
"last": "Nikitina",
"suffix": ""
}
],
"year": 2013,
"venue": "Eesti Keele Sihtasutus",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Silja Gr\u00fcnberg, Ada Ambus, Georg Gr\u00fcnberg, Roman Kallas, Tatjana Murnikova, Tat- jana Nikitina, Agnia-Agnes Reitsak, Savvati Smirnov, Indrek Hein, Esta Prangel, and Esta Prangel, editors. 2013. Vadja keele s\u00f5naraamat =: Va\u010f\u010faa t\u0161eelee s\u00f5na-t\u0161irja = \u0421\u043b\u043e\u0432\u0430\u0440\u044c \u0432\u043e\u0434\u0441\u043a\u043e\u0433\u043e \u044f\u0437\u044b\u043a\u0430. Eesti Keele Sihtasutus, Tallinn, 2., t\u00e4iend. ja parand. tr edition.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "Generalizing inflection tables into paradigms with finite state operations",
"authors": [
{
"first": "",
"middle": [],
"last": "Mans Hulden",
"suffix": ""
}
],
"year": 2014,
"venue": "Proceedings of the 2014 Joint Meeting of SIGMORPHON and SIGFSM",
"volume": "",
"issue": "",
"pages": "29--36",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Mans Hulden. 2014. Generalizing inflection tables into paradigms with finite state operations. In Proceedings of the 2014 Joint Meeting of SIGMORPHON and SIGFSM. pages 29-36. http://aclweb.org/anthology/W/W14/W14-2804.pdf.",
"links": null
},
"BIBREF10": {
"ref_id": "b10",
"title": "Computing with realizational morphology",
"authors": [
{
"first": "Lauri",
"middle": [],
"last": "Karttunen",
"suffix": ""
}
],
"year": 2003,
"venue": "Computational linguistics and intelligent text processing",
"volume": "",
"issue": "",
"pages": "203--214",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Lauri Karttunen. 2003. Computing with realizational morphology. In Computational linguistics and intelligent text processing, Springer, pages 203-214.",
"links": null
},
"BIBREF11": {
"ref_id": "b11",
"title": "Two-Level Model for Morphological Analysis",
"authors": [
{
"first": "Kimmo",
"middle": [],
"last": "Koskenniemi",
"suffix": ""
}
],
"year": 1983,
"venue": "",
"volume": "83",
"issue": "",
"pages": "683--685",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Kimmo Koskenniemi. 1983. Two-Level Model for Morphological Analysis. In IJ- CAI . volume 83, pages 683-685. http://ijcai.org/Past%20Proceedings/IJCAI-83- VOL-2/PDF/020.pdf.",
"links": null
},
"BIBREF12": {
"ref_id": "b12",
"title": "Building an opensource development infrastructure for language technology projects",
"authors": [
{
"first": "N",
"middle": [],
"last": "Sjur",
"suffix": ""
},
{
"first": "Tommi",
"middle": [
"A"
],
"last": "Moshagen",
"suffix": ""
},
{
"first": "Trond",
"middle": [],
"last": "Pirinen",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Trosterud",
"suffix": ""
}
],
"year": 2013,
"venue": "Proceedings of the 19th Nordic Conference of Computational Linguistics (NODALIDA 2013",
"volume": "16",
"issue": "",
"pages": "343--352",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Sjur N. Moshagen, Tommi A. Pirinen, and Trond Trosterud. 2013. Building an open- source development infrastructure for language technology projects. In: Proceed- ings of the 19th Nordic Conference of Computational Linguistics (NODALIDA 2013). Volume 16 of NEALT Proceedings Series. (May 22-24 2013) pages 343-352.",
"links": null
},
"BIBREF13": {
"ref_id": "b13",
"title": "Grammars as software libraries",
"authors": [
{
"first": "Aarne",
"middle": [],
"last": "Ranta",
"suffix": ""
}
],
"year": 2008,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Aarne Ranta. 2008. Grammars as software libraries.",
"links": null
},
"BIBREF14": {
"ref_id": "b14",
"title": "Grammatical framework : programming with multilingual grammars. Studies in computational linguistics",
"authors": [
{
"first": "Aarne",
"middle": [],
"last": "Ranta",
"suffix": ""
}
],
"year": 2011,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Aarne Ranta. 2011. Grammatical framework : programming with multilingual gram- mars. Studies in computational linguistics. CSLI Publications.",
"links": null
},
"BIBREF15": {
"ref_id": "b15",
"title": "Vatjan kielen Joenper\u00e4n murteen sanasto. Suomalais-ugrilainen seura",
"authors": [
{
"first": "Dmitri",
"middle": [],
"last": "Tsvetkov",
"suffix": ""
}
],
"year": 1995,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Dmitri Tsvetkov. 1995. Vatjan kielen Joenper\u00e4n murteen sanasto. Suomalais-ugrilainen seura ;Kotimaisten kielten tutkimuskeskus, Helsinki.",
"links": null
},
"BIBREF16": {
"ref_id": "b16",
"title": "Vadja Keele Grammatika. Eesti Keele Sihtasutus",
"authors": [
{
"first": "Dmitri",
"middle": [],
"last": "Tsvetkov",
"suffix": ""
}
],
"year": 2008,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Dmitri Tsvetkov. 2008. Vadja Keele Grammatika. Eesti Keele Sihtasutus, Tallinn.",
"links": null
},
"BIBREF17": {
"ref_id": "b17",
"title": "\u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0439 \u0432\u043e\u0434\u0441\u043a\u0438\u0439 \u044f\u0437\u044b\u043a: \u0442\u0435\u043a\u0441\u0442\u044b \u0438 \u0433\u0440\u0430\u043c\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0447\u0435\u0440\u043a. \u0422\u043e\u043c 2, \u0413\u0440\u0430\u043c\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0447\u0435\u0440\u043a \u0438 \u0431\u0438\u0431\u043b\u0438\u043e\u0433\u0440\u0430\u0444\u0438\u044f",
"authors": [
{
"first": "\u0411\u043e\u0440\u0438\u0441\u043e\u0432\u043d\u0430",
"middle": [],
"last": "\u0415\u043b\u0435\u043d\u0430",
"suffix": ""
},
{
"first": "\u0424\u0435\u0434\u043e\u0440 \u0418\u0432\u0430\u043d\u043e\u0432\u0438\u0447",
"middle": [],
"last": "\u041c\u0430\u0440\u043a\u0443\u0441",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "\u0420\u043e\u0436\u0430\u043d\u0441\u043a\u0438\u0439",
"suffix": ""
}
],
"year": 2011,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "\u0415\u043b\u0435\u043d\u0430 \u0411\u043e\u0440\u0438\u0441\u043e\u0432\u043d\u0430 \u041c\u0430\u0440\u043a\u0443\u0441 and \u0424\u0435\u0434\u043e\u0440 \u0418\u0432\u0430\u043d\u043e\u0432\u0438\u0447 \u0420\u043e\u0436\u0430\u043d\u0441\u043a\u0438\u0439. 2011. \u0421\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0439 \u0432\u043e\u0434\u0441\u043a\u0438\u0439 \u044f\u0437\u044b\u043a: \u0442\u0435\u043a\u0441\u0442\u044b \u0438 \u0433\u0440\u0430\u043c\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0447\u0435\u0440\u043a. \u0422\u043e\u043c 2, \u0413\u0440\u0430\u043c\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043e\u0447\u0435\u0440\u043a \u0438 \u0431\u0438\u0431\u043b\u0438\u043e\u0433\u0440\u0430\u0444\u0438\u044f: [\u0432 2-\u0445 \u0442\u043e\u043c\u0430\u0445].",
"links": null
}
},
"ref_entries": {
"TABREF0": {
"text": "Furthermore, other words sharing the same paradigm",
"num": null,
"html": null,
"content": "<table><tr><td colspan=\"2\">Wordform MSD</td><td>LCS</td></tr><tr><td>t\u0161iutto</td><td colspan=\"2\">Sg Nom t\u0161iut t o</td></tr><tr><td>t\u0161iutod</td><td colspan=\"2\">Pl Nom t\u0161iut o d</td></tr><tr><td colspan=\"3\">Table 1: Inflection table with morphosyntactic descriptions and underlined longest</td></tr><tr><td>common subsequence.</td><td/></tr></table>",
"type_str": "table"
}
}
}
}