The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

6.2. Survey 132 7. Eric Brill’s simple rule-based part of speech tagger 12 Availability: Source code accessible at Plymouth Tech. 13 Assessment: good. Features: Based on rules derived from a training corpus. No lemmatization. However, absence of lemmatization may be resolved by modifying the code and implementing a lexicon (if the tagger is open source). Assessment: fair. Code: Originally implemented in C. Also implemented in Python as part of NLTK 14 . An interesting implementation of Brill’s ideas combined with an HMM approach is the Erlangen-Tagger 15 though documentation of this approach seems poor and it is not open source. The same approach however is applied by Sujit Pal 16 whose Java code is available as open source (see also the next tagger reviewed here). Assessment: good. Architecture: Depending on the implementation, the tagger can be easily adopted to various conditions. Assessment: good. Usability: Especially the Python and the Java implementations come with good documentation. Assessment: good. 8. Sujit Pal’s HMM-based tagger 17 Availability: Source code available from Sujit Pal’s blog. Comes with a model for English derived from the Brown Corpus. Assessment: good. Features: HMM tagger based on Konchady (2006). No lemmatization. However, as the code is well-structured and not too complex, other features may be added. Sujit Pal is a software developer, not a linguist. His example makes some linguistic simplifications that may conceal the actual capabilities of his implementation. Assessment: fair. Code: Java. Assessment: good. Architecture: The code is well-documented and can easily be adopted to various needs. Assessment: good. Usability: Documentation is OK, code is clear and easy to modify. Assessment: good. 12 http://en.wikipedia.org/wiki/Brill_tagger 13 http://www.tech.plym.ac.uk/soc/staff/guidbugm/software/RULE_BASED_TAGGER_V.1.14.tar.Z 14 http://www.nltk.org/ 15 http://www8.informatik.uni-erlangen.de/en/demosdownloads.html 16 http://sujitpal.blogspot.com/2008/11/ir-math-in-java-rule-based-pos-tagger.html 17 http://sujitpal.blogspot.com/2008/11/ir-math-in-java-hmm-based-pos.html
6.2. Survey 133 9. alias-i’s LingPipe 18 toolkit Availability: Commercial. Assessment: poor. Features: HMM tagger. No lemmatization. Assessment: fair. Code: Java API. Assessment: fair. Architecture: Because of the Java API, integration in various settings seems feasible. Assessment: fair. Usability: Seems well-documented. POS tutorial 19 available on homepage. Assessment: good. 10. Jitar 20 is a simple trigram HMM POS tagger Availability: Open source. However, the code provided on the project homepage is incomplete. 21 Assessment: poor (as code is incomplete). Features: Simple trigram HMM tagger. No lemmatization. Assessment: fair. Code: Java. Assessment: good. Architecture: In principle, easy integration. Assessment: fair. Usability: Does not seem too complex which probably would make it fairly easy to use. However, it is maintained by just one person who already announced that Jitar development will be discontinued in favor of Jitar’s C++ counterpart Citar. 22 Assessment: poor. 6.2.2 Taggers for Danish Only two established taggers seem to be available although some others may be around as well. However, they may be narrowly tied to certain (closed) projects or companies. 1. CST’s POS tagger Availability: Brill’s allegedly modified code can be downloaded from the site of the Centre for Language Technology (CST) as “open source”. CST has trained the tagger on DSL’s publicly accessible PAROLE Corpus and thus derived a language model for Danish 18 http://alias-i.com/lingpipe/index.html 19 http://alias-i.com/lingpipe/demos/tutorial/posTags/read-me.html 20 http://github.com/danieldk/jitar 21 Classes LanguageModel.java and LinearInterpolationLM.java have no con- tents. 22 http://langkit.org/
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:
3.3. Filling in the header 71 Value
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82: 3.3. Filling in the header 81 Value
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 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: 6.2. Survey 131 Code: Java. Assessm
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 and 156: 8.1. Enhancing existing material 15
Page 157 and 158: 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

Create successful ePaper yourself

Delete template?

Save as template?