The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

Chapter 5 Processing text Technical and end-user documentation of the DK-CLARIN WP 2.1 text conversion-services Deliverables concerned [...] Outline of this chapter 5.1 Implementation . . . . . . . . . . . . . . . . . . . . . . . 99 5.1.1 Web-services . . . . . . . . . . . . . . . . . . . . . 99 5.1.2 Web-services and Java . . . . . . . . . . . . . . . 101 5.2 Header constructor:make-header . . . . . . . . . . . . 103 5.2.1 Description . . . . . . . . . . . . . . . . . . . . . 103 5.2.2 Implementation . . . . . . . . . . . . . . . . . . . 103 5.2.3 Use . . . . . . . . . . . . . . . . . . . . . . . . . . 103 5.3 Pre-tokenizer:pretokenize . . . . . . . . . . . . . . . . 114 5.3.1 Description . . . . . . . . . . . . . . . . . . . . . 114 5.3.2 Implementation . . . . . . . . . . . . . . . . . . . 116 5.3.3 Use . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.4 Text id registry:register-text . . . . . . . . . . . . . . 119 5.4.1 Description . . . . . . . . . . . . . . . . . . . . . 119 5.4.2 Implementation . . . . . . . . . . . . . . . . . . . 119 5.4.3 Use . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.5 id dispatcher:make-id . . . . . . . . . . . . . . . . . . . 122 5.5.1 Description . . . . . . . . . . . . . . . . . . . . . 122 98
5.1. Implementation 99 5.5.2 Implementation . . . . . . . . . . . . . . . . . . . 122 5.5.3 Use . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.6 Word and paragraph counter:count-units . . . . . . . 124 5.1 Implementation The text-conversion services are implemented in part as standalone Java programs, web-services based on eXist-db/XQuery, 1 as well as a combination of both approaches. The following description only gives an account of DSL’s conversion software as DSN’s never has been documented. 5.1.1 Web-services Two equally popular web-service architectures are REST (Representational State Transfer) and SOAP (Simple Object Access Protocol). They each have their merits and drawbacks. A major advantage of SOAP is that it can satisfy a wide range of nonfunctional requirements, in particular Quality of Service (QoS) requirements like secure, reliable and protocol-independent messaging. For SOAP to work there must be an HTTP body in which to place the SOAP envelope (containing the payload of the message and its metadata). This means that SOAP web-services always rely on the POST method even for so-called idempotent operations (i.e. operations which do not change anything on the server, e.g. simple requests for information). A drawback of SOAP is, besides relying on the POST transfer method only, that it involves the use of a quite verbose XML format (literally hundreds of different specifications) which may introduce overhead and needless complexity. While REST does not allow for much QoS, its key merit is exactly its simplicity and transparency. According to the REST web-service design pattern, everything is considered a resource, and all resources are organized like a standard file system (which, in fact, resembles the structure of the early WWW). The operations which can be performed on resources are limited to the standard HTTP methods, i.e. POST, PUT, GET and DELETE. Since the eXist open source XML database system is already being used in DK-CLARIN as a text-bank platform, see , and since eXist features an integrated REST-style HTTP server interface, REST was selected as the architectural style for the CTB web-services. Another reason for avoiding SOAP is that QoS aspects are not an issue, so using SOAP and WSDL would only introduce needless complexity. 1 Services based on eXist-db will be gradually replaced by Java/Glassfish-based services in future development.
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 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: Part III Collecting 97
Page 101 and 102: 5.1. Implementation 101 [request c
Page 103 and 104: 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 149 and 150:
7.2. The ePOS tag set for Danish 14
Page 151 and 152:
7.2. The ePOS tag set for Danish 15
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?