The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

5.3. Pre-tokenizer:pretokenize 114 75. The block contains revision information on this text. If no revisions are given, the web-service generates a dummy element with a of 99999999, a of nil, and a of ‘created’. The example given above shows all elements of the simplified header. However, as the make-header service employs defaults in all cases where corresponding information in the simplified header is missing, many elements of the example above would be left out in a real setting. The resulting response would be exactly the same. The reader is encouraged to experiment with this in the interactive demo application at http://korpus.dsl.dk/clarin/demo/webservice/. Response The response from the make-header service is a full TEI-CTB header formatted according to the specifications given in . What this header looks like can be seen by running the above example in the demo application at http://korpus.dsl.dk/clarin/demo/webservice/. The above example is the default example of the demo app. Client development The Java client example shown in Section 5.1.2 on page 101 can easily be adopted to be used with this web-service too. 5.3 Pre-tokenizer:pretokenize 5.3.1 Description The pre-tokenizer web-service takes as input a raw text (preferably with annotations), a prefix letter (for prefixing token ids) and finally a text id which has to be unique within the DK-CLARIN project. The input must comply with a specific XML structure (cf. the demo in Section 5.1.1.1). On the basis of this input, a pretokenized version of the text (no header) is returned to the client. The pretokenized format complies with TEI-P5 and will be referred to as TEI-P5-WP2 format in this document. For some tasks the TEI-P5-WP2 format will constitute an adequate degree of tokenization, but for other tasks it may not. For example, common multiword expressions like i går (‘yesterday’) are not recognized and annotated as a single token. For this reason we refer to the tokenizer as a “pretokenizer” and encourage users to produce separate annotation layers (span
5.3. Pre-tokenizer:pretokenize 115 groups) on the basis of TEI-P5-WP2 in case they need more sophisticated or customized tokenization, see . A key issue when implementing a tokenizer is which characters should be considered punctuation (i.e. non-word characters). Punctuation characters should be characterized by having no semantic impact on the words in the text. In other words, if a punctuation character is removed from the text, this should in no way change the meaning of the words in the text (denotational, connotational, or otherwise). If, for example, currency symbols, degree symbols and so on were to be deleted, it would cause a loss of meaning. For this reason such characters are not considered punctuation. 5.3.1.1 List of punctuation characters On the basis of discussions in the WP2 project group, which agreed upon using the punctuation characters listed in Wikipedia, cf.http://da.wikipedia.org/wiki/Tegns andhttp://en.wikipedia.org/wiki/Punctuation, the list of punctuation characters used in the pre-tokenizer is limited to the following: Table 5.1: Punctuation characters Character Description Code Variants ’ apostrophe 0027 ( bracket, round, opening ) bracket, round, closing [ bracket, square, opening ] bracket, square, closing { bracket, curly, opening 0028 0029 005B 005D 007B } bracket, curly, closing 007D : colon 003A , comma 002C - dash/hyphen 002D 2013 en dash: – 2014 em dash: — / slash 002F 005C backslash: \ Table continues on next page. . .
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:
Page 61 and 62:
3.3. Filling in the header 61 Value
Page 63 and 64: 3.3. Filling in the header 63 Legal
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 71 and 72: 3.3. Filling in the header 71 Value
Page 81 and 82: 3.3. Filling in the header 81 Value
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 113: 5.2. Header constructor:make-header
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?