The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

3.3. Filling in the header 44 theirValue revisionType 3.3.2 Value sets for header standard information When filling in the header with standard information about the text, some types of information may be undetermined or non-existent, e.g. the name of an author may be simply missing in the header for some reason, that is, it is undetermined, or a text may not have a title, that is, its title is nonexistent. Such incomplete parts of the header could be left out in these cases if permitted by TEI, however, leaving out such parts would obscure whether the information is missing because it is undetermined or because it is nonexistent. If the information is undetermined, efforts should be undertaken to occasionally add it, otherwise, if it is non-existent, such efforts would be waste of time. In order to distinguish these two cases, it is recommended to always explicitly state non-existent information by filling in empty for string and symbol values, 0 (= zero) for integers, and 1000 in the case of years (and dates), 25 in other words never to leave these parts of a header out. However, if the information is undetermined, these parts of a header may be left out indicating that the missing information occasionally should be added or be marked as non-existent if that is the case. So in the case of undetermined information, it is legal to skip the respective part of the header if allowed by TEI; however, for the sake of completeness, it is strongly recommended to state nil in case of string values 25 The value 1000 for dates is necessary in order to comply with the TEI data typedate that does not allow a value of 0.
3.3. Filling in the header 45 and 99999999 26 in the case of integers and dates to indicate that this particular information obviously is missing and should be added if it does exist or, if it turns out that the information definitely does not exist, it should be marked as non-existent. To sum up, the following constant symbols are used as values for header elements and attributes, unless otherwise stated further below in this section: 27 Symbol Type Meaning empty anonymous String Names Info is non-existent Person is unknown 0 Integer Info is non-existent 1000 Date/Year Info is non-existent nil String Info has not been determined yet 99999999 Integer and Date/Year Info has not been determined yet In all other cases, that is in cases where the desired information is available, the values listed in Section 3.3.2.1 are used replacing the header variables indicated in the full header template above. For each of these variables a description is given followed by an overview of its properties and – in the case of enumerated sets – a list of legal values. In cases where these lists are too comprehensive, they are replaced by a link to an XML version of them. All value sets are also accessible as XML files and may be referenced automatically or manually when filling in headers. All value set files are found under the path http://korpus.dsl.dk/clarin/corpus-doc/text-header/. The filenames themselves are given below. 28 The structure of the XML value set files is as shown in the following extract. The structure has been designed for this specific purpose (i.e. it is not TEI) and it should be fairly self-explanatory: 26 In former versions of the documentation the ‘undetermined’ value was 1 (minus one). However, TEI does not always allow a negative value for some of its integer datatypes which is the reason why it has been replaced. 27 In cases where TEI does not allow the undetermined/non-existent values defined here, the elements of the value sets are restricted to those that are accepted by TEI. This is the case for the following attributes:cert in,sex in,mode in,type in,level in. 28 As these are XML files, a web browser may not show them well formatted. Viewing them as HTML source may help though.
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 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: 3.3. Filling in the header 43 samp
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

Create successful ePaper yourself

Delete template?

Save as template?