The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

5.2. Header constructor:make-header 104 Request body 6 The following request contains a so-called simplified header to be converted into a full TEI-P5-WP2 header by the make-header web-service. The simplified header is considered an interface between user applications and the full header: User apps just need to transform information into the simple and flexible structure of the simplified header, the make-header web-service ensures that any simplified header is converted into a – at any time – correct full TEI-P5-WP2 header. Hence, validating against a dedicated TEI-P5-WP2 header schema should not be necessary. However, testing the validity of values from fixed inventories is still necessary. If the structure of the full header is changed, the make-header web-service will be changed accordingly; all other conversion tools that just convert to the simplified header structure will not be directly affected by such structural changes. So using the simplified header as an interface between conversion tools and the full TEI-P5-WP2 header makes it easier to maintain conversion tools and conversions themselves less error-prone. The structure of the simplified header is deliberately flat with just one level beneath the outermost request node. However, some elements work as containers for any number of other elements, cf. further descriptions below. The order of the elements in a simplified header is arbitrary. The element names are (almost) identical to the corresponding variable and valueset names used in. A simplified header does not need to be complete: Elements may be left out and the corresponding elements or attributes in the full header will be filled in with default values. If a value-set exists for a certain type of information, the default value from this value-set is used if it is declared. If it is not declared, default is nil (or 99999999 in the case of dates and numbers). If a value-set does not exist, default is always nil (or 99999999). The following example shows how header data of a DDOC text can be expressed by means of the simplified header. It shows all elements possible in the the simplified header, even such which in this particular case could be left out as they just contain default values which would be added automatically by the service. Numbers in square brackets refer to comments further below in this description. Skal vi have 35-timers arbejdsuge... nu? (1) a (2) Bytinget (3) (4) 1200001003 (5) HRfX (6) (7) CTB excerpt (8) 6 A make-header request demo can also be downloaded directly from http://ctbws.dsl.dk/request-templates/make-header.xml.
5.2. Header constructor:make-header 105 DDO (9) dsl.dk (10) keyed-proof (11) 1992 (12) 463 (13) 2 (14) dsl.dk (15) restricted (16) partial (17) partial (18) partial (19) 0 (20) 0 (20) 0 (20) (21) (22) DDOC text sample converted to TEI-P5-WP2 format Grp:Bytinget1KK; Num:1 (23) (24) SpbId: LPG; FøS: Århus; Bop: ?; Reg: Øs; Udd: cand.scient.pol.; Erh: folketingsmedlem; SpV: i; Rol: de; (24) SpbId: LIG; FøS: Horsens; Bop: ?; Reg: Ve; Udd: tekn. forb.eksamen; Erh: folketingsmedlem; SpV: i; Rol: de; (25) (26) Gammelgaard, Lars P. (27) empty (28) adult (29) 1 (30) 1945 (31) high (32) (33) Gyldenkilde, Lilli empty adult 2 1936 high (34) (35) nil
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 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: 5.2. Header constructor:make-header
Page 107 and 108: 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?