The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

8.1. Enhancing existing material 156 The structure of the full-form list may be illustrated by the following example: * certifikat S 2 certifikat 4 certifikats 8 certifikatet 16 certifikatets 32 certifikater 64 certifikaters 128 certifikaterne 256 certifikaternes A new lemma is always preceded by an asterisk (*) on a separate line. In the following line the lemma appears in its lemma or base form, in line 3 its part of speech is given. The following part of speech markers occur: S: noun A: adjective V: verb D: adverb F: abbreviation K: conjunction L: onomatopoeic word O: pronoun P: proper noun I: prefix Æ: preposition T: numeral U: interjection X: unidentified Class X comprises words that could not be immediately identified during automatic analysis of the sources. In particular it contains words which usually occur exclusively in fixed expressions with other words, e.g. badut (springe badut), bero (stille i bero), besøgelsestid (kende sin besøgelsestid) or multi word units behaving as a single word, e.g. au pair. In addition to prefixes proper, e.g. di-, eks-, fore-, classIalso comprises the first elements of compounds, e.g. forenings-, forhandlings-, formue-. Class P comprises proper nouns (i.e. in principle, nouns), but as it is almost impossible to apply usable selection criteria discerning important from unimportant within the class, it is characterized by a degree of coincidence.
8.1. Enhancing existing material 157 ClassFreflects primarily an orthographic phenomenon. For all abbreviations, a genitive form with apostrophe -s has been generated although many of these seem questionable. The line containing part of speech is followed by the different orthographic forms which the word may take. The forms are always given in small letters even if capital letters are used in the normally correct orthographic representation. Hyphens, full stops (in abbreviations) and spaces (e.g. a la), if any, are also omitted. The omitted information can, however always be derived from the base form. Each orthographic inflectional form in the list is preceded by a number (separated from the word by a tabulator) indicating which inflectional forms of the lemma the form can be assigned to. The numbers refer to the bits which have been placed in the following bit pattern: position 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 value 1 2 4 8 16 32 64 128 256 512 1024 2048 4096 8192 16384 32768 position 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 value 1 2 4 8 16 32 64 128 256 512 1024 2048 4096 8192 16384 32768 If the bits in position 6, 10 and 11 have been entered, the number becomes 64+1024+2048=3136. Different inflectional forms are attached to each position depending on the part of speech. The following tables show the forms attached to the individual positions in the bit pattern for relevant part of speech. has been built by algorithmically generating full forms based on lemma forms and inflectional information of The Danish Dictionary (DDO). As the structure of inflectional information in the DDO is suboptimal for NLP exploitation a minor group of the automatically generated forms are erroneous, especially composite nouns. 8.1.1.2 jaPOS adaption ONC-Flexion is based on orthographic forms: each orthographic form is only listed once may have attached several inflectional functions. jaPOS is entirely based on inflectional categories, so the same orthographic forms may be listed under several categories. ONC-Flexion is based on a slightly different token concept than jaPOS as full stop, hyphen, and apostrophes are considered token characters and not boundaries as is the case in jaPOS. This means that words containing one or more of these characters need special attention. The adaption algorithm identifies these cases in ONC-Flexion and rejects them and puts them on a special list that is checked manually.
Page 1 and 2:
The Corpus Thread “Reference corp
Page 3 and 4:
Chapter 1 Aim and concepts Sketchin
Page 5 and 6:
1.1. Aim of the project 5 Metadata
Page 7 and 8:
1.2. Project tasks and documentatio
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
1.3. Text collection, text bank, co
Page 15 and 16:
Chapter 2 The text bank A platform
Page 17 and 18:
2.2. Implementation 17 and metadata
Page 19 and 20:
Chapter 3 Text metadata What the he
Page 21 and 22:
3.1. Concepts 21 Section 3.3 starts
Page 23 and 24:
3.2. Header structure 23 (file des
Page 25 and 26:
3.2. Header structure 25 great verb
Page 27 and 28:
3.2. Header structure 27 The follow
Page 29 and 30:
3.2. Header structure 29 deprecated
Page 31 and 32:
3.2. Header structure 31 the text i
Page 33 and 34:
3.2. Header structure 33 Another el
Page 35 and 36:
3.2. Header structure 35 appDesc
Page 37 and 38:
3.2. Header structure 37 informal p
Page 39 and 40:
3.2. Header structure 39 3.2.3.4 Te
Page 41 and 42:
3.3. Filling in the header 41 revi
Page 43 and 44:
3.3. Filling in the header 43 samp
Page 45 and 46:
3.3. Filling in the header 45 and 9
Page 47 and 48:
3.3. Filling in the header 47 descr
Page 49 and 50:
3.3. Filling in the header 49 ⊲ a
Page 51 and 52:
3.3. Filling in the header 51 Legal
Page 53 and 54:
3.3. Filling in the header 53 ⊲ a
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
3.3. Filling in the header 61 Value
Page 63 and 64:
Page 65 and 66:
3.3. Filling in the header 65 ⊲ p
Page 67 and 68:
3.3. Filling in the header 67 Prope
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
3.3. Filling in the header 83 3.3.3
Page 85 and 86:
4.1. Basic considerations 85 Outlin
Page 87 and 88:
4.2. Formatting text 87 russiske hi
Page 89 and 90:
4.2. Formatting text 89 Mirganjan
Page 91 and 92:
4.2. Formatting text 91 udvikle ude
Page 93 and 94:
4.2. Formatting text 93 4.2.3.4 Add
Page 95 and 96:
4.2. Formatting text 95 i dag . T
Page 97 and 98:
Part III Collecting 97
Page 99 and 100:
5.1. Implementation 99 5.5.2 Implem
Page 101 and 102:
5.1. Implementation 101 [request c
Page 103 and 104:
5.2. Header constructor:make-header
Page 105 and 106: 5.2. Header constructor:make-header
Page 115 and 116: 5.3. Pre-tokenizer:pretokenize 115
Page 117 and 118: 5.3. Pre-tokenizer:pretokenize 117
Page 119 and 120: 5.4. Text id registry:register-text
Page 121 and 122: 5.4. Text id registry:register-text
Page 123 and 124: 5.5. id dispatcher:make-id 123 0 11
Page 125 and 126: Part IV Markup 125
Page 127 and 128: 6.1. Requirements 127 Outline of th
Page 129 and 130: 6.2. Survey 129 1. IMS’s TreeTagg
Page 131 and 132: 6.2. Survey 131 Code: Java. Assessm
Page 133 and 134: 6.2. Survey 133 9. alias-i’s Ling
Page 135 and 136: 6.3. Case study 135 lemmatization c
Page 137 and 138: 6.4. Further reading 137 disambigua
Page 139 and 140: 7.1. Modifications of the PAROLE Co
Page 141 and 142: 7.2. The ePOS tag set for Danish 14
Page 153 and 154: Chapter 8 The full-form lexicon Sam
Page 155: 8.1. Enhancing existing material 15
Page 159 and 160: Part V Deployment 159
Page 161 and 162: 9.2. Text material 161 Type Source
Page 163 and 164: 10.2. Funktionaliteter 163 2. The u
Page 165 and 166: 10.2. Funktionaliteter 165 fortolke
Page 167 and 168: 10.2. Funktionaliteter 167 teknolog
Page 169 and 170: 10.2. Funktionaliteter 169 Implemen
Page 171 and 172: 10.2. Funktionaliteter 171 forbinde
Page 173 and 174: 10.2. Funktionaliteter 173 10.2.9 K
Page 175 and 176: Bibliography Andersen, M. S., Asmus
show all

The Corpus Thread - Det Danske Sprog- og Litteraturselskab

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?