The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

3.2. Header structure 22 be structurally integrated are the Corpus of the Danish Dictionary (DDOC, Norling-Christensen and Asmussen (1998)), PAROLE-DK (Keson (1998a) and Keson (1998b)), KORPUS 2000 (Andersen et al. (2002)), other corpusrelevant material from DOT/DSL and Dansk Sprognævn (DSN), as well as the LGP and LSP corpora of written Danish which are compiled as part of DK-CLARIN. 4 The TEI header structure provides extremely flexible means of expressing textual metadata. A wealth of information can be given in a more or less fine-grained way. The following Section 3.2 describes a header that exactly accommodates the needs of potential corpus texts. In many cases, TEI allows the header to be modified either by augmenting or simplifying it. However, a header with more or less information is still compatible with the model described here as long as its structure does not conflict with TEI P5 syntax (and semantics) requirements. Therefore, the following section does not describe a TEI header in general, but the specific header of a potential corpus text in the Corpus Text Bank of WP 2.1, expressed by means of TEI. 5 3.2 Header structure The header of a text item provides a structured description of the text contents, analogous to the title page and front matter of a book. Every separate text item in the Corpus Text Bank has its own header . In addition, a corpus itself may have a header containing information which is applicable to the whole corpus. The corpus header is not part of this description. To a large extent, a corpus header would be an abridged and slightly modified version of a text header. Furthermore the corpus header should contain the declaration of value sets for various elements (e.g. a domain taxonomy for LSP texts). The Corpus Text Bank contains value declarations in form of a collection of certain value set files which may be referenced by the CTB header. The content structure of the Corpus Text Bank is described in detail in Chapter 2 The value set files proper are described in detail in Section 3.3.2. The remainder of this section describes the components of the element as used within the Corpus Text Bank. A TEI header contains a file description (Section 3.2.1), an encoding description (Section 3.2.2), a profile description (Section 3.2.3), and a revision description (Section 3.2.4), represented by the following four elements: 4 Text material from the Arkiv for Dansk Litteratur (ADL) and other archives may at a later stage be integrated as well, if the header structure of their texts can be mapped to that one described here. 5 The header design has been adopted for text resources to be included in the DK- CLARIN repository developed by WP 5.
3.2. Header structure 23 (file description) contains a full bibliographic description of an electronic text as well as the source from which it was derived. (encoding description) documents the relationship between an electronic text and the source from which it was derived. (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. (revision description) summarizes the revision history for a file. 3.2.1 The file description The file description is the first of the four main constituents of the header. It is intended to document a digital file. It contains the following four subdivisions: (title statement) groups information about the title of a work represented in the electronic text sample and those responsible for its intellectual content. specifies the size of the electronic text sample in number of words and paragraphs (and other countable units). (publication statement) groups information concerning the publication or distribution of the electronic text sample. (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. (source description) supplies a description of the source text from which the digital text sample was derived. Further detail for each of these is given in the following subsections. 3.2.1.1 The title statement The title statement element of a text item contains one element, followed by one and one element as shown in the following pattern: samplingDeclaration textTitle
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 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: 3.1. Concepts 21 Section 3.3 starts
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 71 and 72: 3.3. Filling in the header 71 Value
Page 73 and 74:
3.3. Filling in the header 73 Legal
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?