The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

2.1. Introduction 16 Outline of this chapter This chapter gives an account of the text bank, that is, of its intended functions as text repository and administrative registry as well as its implementation. The db software should be able to store and give multi-user access to XML text documents, manage text supplier data, and facilitate the detection of duplicate text material. This chapter also serves as documentation for WP 1.10 and 1.21 as described in Asmussen (2008). 2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.2 Implementation . . . . . . . . . . . . . . . . . . . . . . . 16 2.2.1 XML vs. relational db systems . . . . . . . . . . . 16 2.2.2 eXist – the text bank system by choice . . . . . . 17 2.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.3.1 Text repository . . . . . . . . . . . . . . . . . . . . 18 2.3.2 Text registry . . . . . . . . . . . . . . . . . . . . . 18 2.3.3 Text supplier registry . . . . . . . . . . . . . . . . 18 2.4 Alternative approaches . . . . . . . . . . . . . . . . . . . 18 2.1 Introduction Crucial for composing corpora is a repository of texts from which texts according to a specific profile can be selected. The corpus itself is considered a separate resource. This repository is intended to contain corpus-suitable texts with certain textual metadata expressed in a systematic way that can be expressed as XML, see Chapter 3. A repository of this kind is called a text bank. 1 A text bank may provide some administrative functions as well like handling text supplier information. In the following, the implementation of the text bank, the Corpus Text Bank, CTB, is described in further detail. This is followed by a description of the text registry and the text supplier registry functionality. 2.2 Implementation 2.2.1 XML vs. relational db systems The fundamental units of a corpus are text items 2 drawn from a text repository. A repository containing potential corpus texts in a standardized text 1 See also Section ??. 2 See
2.2. Implementation 17 and metadata format only is called a text bank. As corpus texts to be included in the text bank are XML-formatted according to a specific schema, see chapter 3 and chapter 4, it seems obvious to store them in an XML database. Moreover, it is necessary to be able to access and edit these fundamental text units with a viewer/editor. Storing the text material in a relational database would require substantial processing of the material prior to database import and export. As such, conversion procedures introduce an extra amount of resources and complexity, they must be considered error-prone in terms of appliance and maintenance. Therefore, it appears obvious to apply an XML-based db solution. An overview of XML databases can be found on Wikipedia. To minimize software expenditures, only open source products have been examined. Among these, projects with low or none obvious development activities were rejected, that is Xindice, myXMLDB, ozone. Sedna could be a candidate, but it is obviously not supported by the oXygen XML editor, the same seems to be the case for MonetDB and BaseX. After these exclusions the only candidate left is eXist. 2.2.2 eXist – the text bank system by choice 2.2.2.1 Advantages ⊲ Native XML db ⊲ Easy to install and maintain ⊲ Built-in indexing (automatic and user-defined) which means quick searches ⊲ XQuery is used to manipulate data ⊲ Theoretically unlimited document size. So far, the 13,5 MB DK- PAROLE Corpus has been the largest document uploaded ⊲ Can store up to2 31 documents ⊲ Accessible from the oXygen editor ⊲ Easy to set up as a web service. This should make it straightforward to – have the eXist-based text bank to fit into the envisaged DK- CLARIN infrastructure – develop a stand-alone text bank interface and skip the oXygen editor
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 13 and 14: 1.3. Text collection, text bank, co
Page 15: Chapter 2 The text bank A platform
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 61 and 62: 3.3. Filling in the header 61 Value
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:
3.3. Filling in the header 69 Legal
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 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

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

Delete template?

Save as template?