The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

1.2. Project tasks and documentation outline 8 D2 Tokenizer A consistent and easy-to-use token concept needs to be defined. The token concept has important implications on the design of the tokenizer tool (Chapter 5) and the POS-tagger (Chapter 7) applied in WP 2.1. Outcome: Tool and report. ⊲ Chapter 4 ⊲ Chapter 5 D3 Decision on text bank system A text bank system is necessary for project-internal text administration. Investigations of different approaches to such a system will be carried out. Two general options seem viable – either one based on a relational db or on an XML db. The text bank system is the core component of the CMRS. Outcome: Report. ⊲ Chapter 2 D4 Text supplier registry A registry of active and potential text suppliers needs to be designed as an integrated component of the CMRS. Outcome: Report. ⊲ Chapter 2 D5 Implementation of text bank system The chosen text bank approach (see D3) implemented (possibly with a GUI) as component of the CMRS. Outcome: Report and a project-internal service. ⊲ Chapter 2 D6 Processing of Infomedia text Conversion to the DK-CLARIN format and text bank import of Infomedia material collected by DSL and DSN in 2008 and 2009. Outcome: Report. ⊲ Chapter 5 D7 Development of format transducers Design and development of transducers capable of transforming all supplier formats into the WP2.1 text format. Outcome: Report and project-internal services. ⊲ Chapter 5 D8 Processing of other text Collected text material is converted and inserted into the text bank component of the CMRS. Outcome: Report. ⊲ Chapter 5
1.2. Project tasks and documentation outline 9 D9 Full-form lexicon Development and/or configuration of a full-form lexicon for POS tagging. Outcome: Resource with documentation. ⊲ Chapter 8 D10 Lemmatizer It is considered indispensable that corpus texts need to indicate the lemma form of each inflected word form in the corpus to let the user of the corpus perform more flexible queries. Therefore, it is necessary to either develop or configure a lemmatizer (that may be based on a full-form lexicon or a morphological analyzer). In the context of WP 2.1, a lemmatizer designed as an integral part of a POS tagger is the preferable solution. Outcome: Tool with documentation. ⊲ Chapter 6 ⊲ Chapter 7 ⊲ Chapter 8 D11 POS tagger In order to tag tokens in corpus texts with part-of-speech information, it is necessary to either develop or configure a POS tagger (either based on a full-form lexicon or a morphological analyzer) and a suitable tag set. Outcome: Tool with documentation. ⊲ Chapter 6 ⊲ Chapter 7 ⊲ Chapter 8 D12 Download service Implementation of download option for copyrightcleared or scrambled text material. Outcome: None. Cancelled due to project cutbacks. D13 TEI transducer The original plan for WP 2.1 was based on the assumption that the repository of potential corpus texts – the corpus text bank – most likely would have a non-XML structure (relational db). In order to make interchange of texts easy and in order to make them fit into the intended resource repository of DK-CLARIN, the development of a transducer that could reshape the texts and metadata stored in the corpus text bank to valid TEI XML seemed necessary. However, during the course of the project, it became clear that the text bank itself should be implemented as an XML database so that the texts could be stored in their final TEI XML format. Therefore, the task of developing a transducer became a task of defining an appropriate subset of TEI in order to suit the metadata and text format needs of DK-CLARIN. Outcome: Report.
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: 1.2. Project tasks and documentatio
Page 11 and 12: 1.2. Project tasks and documentatio
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 59 and 60:
3.3. Filling in the header 59 Legal
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:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
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 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
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?