The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

3.2. Header structure 40 3.2.3.5 The participant description The participant description () element is used to provide additional information about authors (or speakers) of texts. The element itself is considered obligatory in the CTB header, however, its contents may just be an empty element which is given as a placeholder to ensure that the header has a valid TEI structure. If additional personal info is given, one element for each participant having been involved in creating the text is inserted into. 23 The element carries a number of attributes which are used to provide encoded values for some key aspects of the person concerned, see the following example: 24 The DDOC material mentioned in Section 3.1 has a lot more information on each text creator, e.g. his place of birth which could be expressed as an element under, his place of residence which could be put into an element as sibling to , and so on. However, corpus-linguistic practice has shown that this type of information hardly ever is used (nor useful if it is not given according to clear-cut classification schemes). Therefore, new material should not be marked-up with this kind of information that is also extremely costly to gather. For DDOC (and other material) which already carries this type of information, appropriate structural elements of should be included into the header to allow keeping this information for possible future investigation, see Chapter ??. 3.2.4 The revision description A list of typical revisions which a document will undergo should be created, i.e. values for revisionType. At least the revision type “Document created” seems important. Others, which deal with the completeness of the header may be useful as well. The pattern of the revision description is as follows: 23 A possible empty placeholder element may then be deleted. 24 More details of which values to fill in can be found in Section 3.3.
3.3. Filling in the header 41 revisionType The revision description must not be confused with the application information discussed in Section 3.2.2.3. 3.3 Filling in the header 3.3.1 Full header template In the following, a complete version of the CTB header template is shown. Its four main constituents and their subdivisions are separated by horizontal lines to facilitate orientation: samplingDeclaration textTitle sponsorName Data capture organizationName captureMethod numberOfWords numberOfParagraphs organizationName textId availDesc anonymDesc availDesc anonymDesc
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 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: 3.2. Header structure 39 3.2.3.4 Te
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 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?