The Corpus Thread - Det Danske Sprog- og Litteraturselskab

More documents

Recommendations

Info

3.2. Header structure 30 edPages textUri textFileName relatedTitle relatedId According to the TEI guidelines, [in] common library practice a clear distinction is usually made between an individual item within a larger collection and a freestanding book, journal, or collection. Similarly a book in a series is distinguished sharply from the series within which it appears. An article forming part of a collection which itself appears in a series thus has a bibliographic description with three quite distinct levels of information: the analytic level, giving the title, author, etc. of the article; the monographic level, giving the title, editor, etc. of the collection; the series level, giving the title of the series, possibly the names of its editors, etc. and the number of the volume within that series. 12 The aim of the bibliographic information for texts which are intended to be included in a corpus, that is the type of texts collected in the Corpus Text Bank, is not to imitate the precision of a librarian but to give an easy way of referring to texts and to probably use bibliographic information in some corpus searches as well. This requires a rather fixed and to some extent rigid structure of the bibliographic part of the header which is the reason why the structure is used here and not one of the other (less structured) possibilities of TEI. The structure can be used to distinguish between the three information levels discussed above in the TEI guideline snippet. Here, only two of the levels are used, namely the analytic and the monographic level. The element in the structure is obligatory. According to TEI, it seems that in the case of a text being monographic, the part of the structure should be left out and the text title and author information should be given within the part of the structure. However, in the CTB headers, the part is considered obligatory, no matter whether 12 Seehttp://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html.
3.2. Header structure 31 the text is part of a collection of some kind, i.e. analytic, or a stand-alone publication, i.e. monographic. This is to ensure that all elements in CTB headers have the same structure, that text title and author information is always found in the same place, that is in the obligatory part of the structure. Within the structure, always gives the title of the text. If the text is part of a collection, e.g. a newspaper article which is part of a newspaper, the level attribute of is set to “a” which means analytic, whereas the element in gives the title of the collection, e.g. the name of a newspaper. If the text is a free-standing book, e.g. a novel, the level attribute is set to “m” meaning monographic; in such cases the element in the part is left empty. All elements carry the obligatory attribute xml:lang indicating the language of the title. The author of a text is always given in in the part of . There is one element for each author who has contributed to the document. The name of the author is given in a element. If the name has been decomposed into forename and surname, the information is given as surname, forename(s), otherwise the comma is left out. If the name of the author is unknown, the element is filled in with an unknown symbol (see Section 3.3), if it for some reason is anonymous, the element is filled in with the string “anonymous”. A element should have a ref attribute giving an XML reference to a corresponding element in the part of the header where additional info concerning the author(s) is given, see Section 3.2.3.5. 13 PAROLE has no participant description as part of the profile description. Instead, PAROLE augments TEI by adding two arguments (gender and born) to the element. In contrast to PAROLE, the CTB header defers from altering the TEI proposal. The element is followed by a with an obligatory attribute n carrying the constant value “translators” that contains the name(s) of the person(s) who has/have translated this text if it is a translation, otherwise is filled in with the empty symbol, see Section 3.3. The element contains an obligatory element with the fixed string “Translated by” and a subsequent element of type “translator” gives the name of the translator. If there is more than 13 It may seem odd that the ref attribute is given on the element and not on the element which would have been an option. However, as ref attributes also are used with translators and editors and neither the element used for translators nor the element are allowed to carry a ref attribute, it is instead attached to the element in all these cases.
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 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: 3.2. Header structure 29 deprecated
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 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 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
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 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
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?