The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

Kapitel 10 Working with corpora Some usage sceanrios (Tidligere titler: Brugsscenarier og funktionaliteter, Arbejde med korpora, Korpus-workflow) DK-CLARIN WP 5.1-arbejdspapir Jørg Asmussen med input fra WP 5.1, WP 5.2, WP 2.1 og WP 2.2 Latest revision: 29.01.2009 Resumé This chapter describes an ideal scenario for working with monolingual corpora in a DK-CLARIN context and its implications on the technical infrastructure of DK-CLARIN. Two primary DK-CLARIN user groups can be identified: Linguists and Experts working with Language Technology – each with specific needs. As it is impossible to implement a complete solution suiting everybody’s needs – limited resources taken into account – the expected needs of the linguists group are prioritised. 10.1 Introduction This chapter describes an ideal scenario for working with corpora in a DK- CLARIN context and its demands on DK-CLARIN’s technical infrastructure. A quite extensive model is outlined which hardly can be fully implemented within the framework of the ongoing DK-CLARIN project. Therefore, the features of the model are prioritised in order to sketch a minimal solution. The following work scenario may serve as a starting point: 1. A user selects a group of specified texts (i.e. a user-defined corpus) on DK-CLARIN’s portal. 162
10.2. Funktionaliteter 163 2. The user annotates his group of texts by applying a self-defined annotational system. 3. The user saves his corpus together with his own annotations, thus giving other users access to his work. Selvom scenariet synes ligetil, viste en udmøntning af det sig at være mere kompleks end umiddelbart antaget. Hvis scenariet skal realiseres, kræves i princippet alle de under afsnit 10.2 beskrevne funktionaliteter implementeret i infrastrukturen – en opgave, som DK-CLARIN’s nuværende WP 5resurser næppe står mål med. Derfor blev det nødvendigt at underkaste de enkelte funktionaliteter en relevansvurdering i relation til de begrænsede resurser, WP 5 faktisk råder over. Papiret begrænser beskrivelsen til monolingvale, ikke-parallelle, ikkealignerede skriftsprogskorpora. Håndtering af multilingvale, parallelle, alignerede korpora stiller særlige krav til konkordansinterfaces m.v., og det er uvist, hvorvidt de umiddelbart vil kunne håndteres af de samme konkordansværktøjer som de monolingvale korpora. 1 Endelig udgør talesprogskorpora en yderligere kategori med særlige kravsspecfikationer, som heller ikke er genstand for dette arbejdspapir. En nærmere beskrivelse af den anvendte korpus-terminologi i dette dokument findes i ?. 10.2 Funktionaliteter DK-CLARIN’s portalsite bør ideelt tilbyde følgende funktionaliteter for arbejdet med tekstkorpora. Brugerne skal have mulighed for at 1. få et overblik over tilgængelige tekstsamlinger og tekstmaterialet heri via de karakteristika (metadata), der er knyttet til både samlingerne som helhed og hver enkelt tekstenhed i dem. Dette skal være muligt, uanset om tekstmaterialet fysisk befinder sig i DK-CLARIN’s centrale repository eller lokalt hos en eller flere af DK-CLARIN’s partnere 2. sammensætte et udvalg af tekster (tekstenheder) på baggrund af bestemte tekstkarakteristika (metadata) og få adgang til dem, gerne i deres helhed og uanset deres fysiske placering i DK-CLARIN’s infrastruktur (centralt og/eller distribueret) 3. arkivere et sådant udvalg af tekster »virtuelt« (som en række pointere til de egentlige tekstenheder) på portalsitet sammen med en beskrivelse (metadata), så også andre (gennem rettighedsstyring) kan få adgang til netop dette udvalg af tekster. Et sådant udvalg af tekster udgør 1 Det henstilles til WP 2.6 at udarbejde et særligt arbejdspapir med vurderinger og anbe- falinger.
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:
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 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
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 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112: 5.2. Header constructor:make-header
Page 113 and 114: 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: 9.2. Text material 161 Type Source
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?