The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

5.2. Header constructor:make-header 110 for illustration purposes, the id is the original one used in the DDOC. Default is nil. 27. The of the author given as ‘lastName, firstName’ if possible. Default: nil. 28. The element tells who has contributed most to the text. The role of the major author is ‘major’, all other authors are classified as ‘minor’. However, in this text, both authors have contributed equally much which means that the role is undeterminable which is indicated by the empty value. Default: ‘major’. 29. The element indicates the age group to which the author belonged when he produced the text. Default is ‘adult’ so in this example the element could be left out as well. 30. The element gives the sex of the author/speaker: ‘1’ means male. Default: ‘0’ meaning unknown. 31. Author’s date of birth given in the pattern yyyy[-mm[-dd]]. Default is 99999999. 32. Certainty of the date of birth is expressed in the element. Default is ‘high’ so in this case the element is actually unnecessary. 33. Another author (that is speaker in this example). OBS! Each element comprises the following subelements: , , ,,, and. They can be left out which means that they are automatically filled in with default values. 34. The element encapsulates any number of possible translators of the text. The element can be left out if it is not relevant. The make-header web-service then inserts a placeholder dummy translator named empty in the full header. In contrary to the dummy author whose name value is nil, the dummy translator carries the value empty, meaning that this information is irrelevant, that there is no translator. 35. A dummy always has id attribute of nil and a element of empty. In the example, for illustration purposes, the element explicitly creates a dummy translator in the full header. However, the whole structure could be left out in this case, the result would remain the same. Each element has the same child elements as has an element. So additional info concerning the translator(s) could be given as well.
5.2. Header constructor:make-header 111 36. The block comprises information about editors, its children being elements. Apart from its different element name, it is structurally fully identical to the and blocks. If no editors were involved in producing/publishing the text, this block can be left out. In that case, the make-header web-service inserts a dummy editor in the full header. 37. In the case of the present text, which is a (transcribed) radio broadcast in a series of broadcasts, there should be an editor involved, i.e. the person responsible for this series. However, the DDOC header structure is not designed for that type of information so it is missing in the DDOC. Hence, editor is set to nil in the editor element. Default is empty. 38. contains the id of the publisher pointing to a data collection with further info on the publisher or distributor of the text source. Publisher ids are defined in value set documents. Default: 99999999. 39. contains the name of the publisher/distributor. Default: nil. 40. contains the date of publication. Default: 99999999. 41. indicates the certainty of publication date. Default: ‘high’. 42. Imprint info indicates the issue of this publication. Default: nil. 43. Imprint info gives the section. Default: nil. 44. Imprint info contains volume information. Default: nil. 45. Imprint info: the chapter. Default: nil. 46. Imprint info: pages info. Default: nil. 47. contains URI of online version of the source text. Default: nil. 48. contains the file name of the input version of the text. Default: nil. 49. Parallel versions of this text or texts otherwise related are listed within the block. Defaults: nil. In this case there are no related texts, so the block containing pointers to related texts could be left out and the web-service would just insert a dummy with default values. For illustration purposes, an explicit default dummy is defined.
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 9 and 10:
Page 11 and 12:
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 55 and 56:
Page 57 and 58:
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 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 109: 5.2. Header constructor:make-header
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 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?