The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

5.2. Header constructor:make-header 108 8. The text is an excerpt, that is, not a complete text, so is set to ‘CTB excerpt’. Default is ‘CTB sample’ which means that it is not known whether the text is complete or an excerpt. If the element is left out, the make-header web-service assumes the default value. 9. Sponsor was the DDO project so is set to ‘DDO’. Sponsor means the intellectually supporting initiative behind the text capture. Default: ‘DK-CLARIN’. 10. contains the name of the organization responsible for creating the electronic version of the text. Default: nil. 11. describes how the text was captured. In this case the text was manually keyed, i.e. transcribed from audio-tapes, and proof-read. Default: ‘file’. 12. contains the year the text was captured. Default is the current year (which must be set in the corresponding value set file). 13. holds the approximate number of words (tokens) in the text sample. A word count can be made by the web-service count-units, see Section 5.6 on page 124. Default: 99999999. 14. holds the approximate number of paragraphs in the text sample. A paragraph count can be made by the web-service count-units, see Section 5.6 on page 124. Default: 99999999. 15. indicates the organization responsible for the distribution of this text (if it may be distributed). Default: nil. 16. indicates the availability of the text. In this case, the text is not available to everybody, thus is set to ‘restricted’. Default is also ‘restricted’ so the element is actually unnecessary in this case and could be left out. The resulting full header would be the same anyway. 17. describes the availability status for users from academic institutions affiliated with DK-CLARIN; ‘partial’ means that they may search and view text contents limited to what is specified in Danish citation law. Default is also ‘partial’, so this element could be left out without affecting the resulting full header. 18. describes the availability status for non-commercial user; ‘partial’ means that they may search and view
5.2. Header constructor:make-header 109 text contents limited to what is specified in Danish citation law. Default is ‘partial’ too, so this element could be left out without affecting the resulting full header. 19. describes the availability status for all other users, again it is ‘partial’. Default is also ‘partial’ again, so this element could be left out without altering the resulting full header. 20. No anonymisations required for any user group (elements,,and). Default value is in all cases ‘0’, so the anonymDesc elements could be left out. 21. The element is a container for any number of elements each of which carries a type attribute telling which organization is responsible for this note and a lang attribute that denotes the language of the note. Valid notes are listed in . Notes may give information that cannot be expressed elsewhere in the TEI-P5-WP2 header. Default for both type and content is nil. 22. The first in this example gives some information on the corpus from which this text has been taken. The lang attribute of this note is “en” meaning “English”. The lang attributes in this and other elements are not mandatory and can be left out. The make-header service described in (5.2) ignores them. 23. Another gives some admin info that is contained in the original DDOC header but cannot be expressed by means of the TEI-P5- WP2 header. The lang attribute of this note is the non ISO-value “xx” which means “formalized”, i.e. the language of the note is formally constructed to express certain properties of the text that cannot be expressed elsewhere in the header. 24. Further elements give additional author/speaker information which is contained in the original DDOC header but cannot be expressed in the TEI-P5-WP2 header. Again, the lang attribute is set to “xx”. 25. The element encapsulates all authors (or speakers) who have produced this text. It could be left out; however, as a text must have an author, the make-header web-service would create a dummy author nil (meaning the author has not yet been identified). 26. Each author/speaker carries a unique id (attribute id of the element) which should be derived from the make-id web-service devoted solely to dispatching valid ids, cf. 5.5 on page 122. In this case,
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:
3.3. Filling in the header 55 Legal
Page 57 and 58: 3.3. Filling in the header 57 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 107: 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

Create successful ePaper yourself

Delete template?

Save as template?