-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathdifdepo-en.odd
More file actions
574 lines (569 loc) · 32.9 KB
/
difdepo-en.odd
File metadata and controls
574 lines (569 loc) · 32.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:svg="http://www.w3.org/2000/svg"
xmlns:math="http://www.w3.org/1998/Math/MathML" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>DifDePo Encoding Schema</title>
</titleStmt>
<publicationStmt>
<p>For publication on the website</p>
</publicationStmt>
<sourceDesc>
<p>Original source</p>
</sourceDesc>
</fileDesc>
<revisionDesc>
<change when="2017-06-01">First version (in English)</change>
</revisionDesc>
</teiHeader>
<text>
<body>
<div>
<head>Introduction</head>
<p>This document describes the TEI encoding schema used for the <ref
target="http://difdepo.hypotheses.org/le-projet/le-projet-archives-de-loulipo">Oulipo
Archives transcription project</ref>. It contains informal discussion and
exemplification of the TEI elements which are present in each transcribed texts, with a
formal statement of the way in which this markup language derives from the <ref
target="http://www.tei-c.org/Guidelines">TEI Guidelines</ref>. </p>
<p>The Oulipo transcriptions are archived in a TEI XML format, which uses specific XML tags
as a means of organization. The tags used are derived from those defined in the TEI
Guidelines (http://www.tei-c.org/Guidelines), but only a small subset of the elements
defined by those Guidelines are used, and their application is specialised in various ways
described by this document. This document also serves as a means of producing a formal XML
Schema which can be used to validate correct application of the TEI tags selected.</p>
<p>In what follows, we first discuss the basic tagging applied to structure the text of each
document (<ptr target="#textStruc"/>); next we discuss the specialised tagging used for
names of persons, places, works, etc. (<ptr target="#namedEnts"/>; finally we discuss the
organization of the TEI Header given for each file, which contains metadata describing the
document (<ptr target="#theHdr"/>). The last section of this document contains reference
material describing each element and its usage in a standardised TEI format. </p>
<p>Some awareness of basic concepts of TEI XML is assumed. </p>
</div>
<div xml:id="textStruc">
<head>Text structure</head>
<p>Each distinct document transcribed by the project is represented by a single <gi>TEI</gi>
element, which has two parts: a <gi>teiHeader</gi> containing metadata describing the
document, and a <gi>text</gi> containing its transcription. We describe the components of
the <gi>teiHeader</gi> below in section <ptr target="#theHdr"/>. The scanned image of each
<q>document</q> has an identifying number derived from the catalogue number of the
original source allocated by the Bibliotheque de l'Arsenal, whether it contains one page
or many. Most of the documents relate to one of the regular meetings of the Oulipo, and we
therefore include the date of that meeting as part of the document's identifier. Documents
are of four possible types: <list type="vals">
<label>CR</label>
<item>document contains the minutes (compte rendu) of a meeting </item>
<label>OJ</label>
<item>document contains the agenda (ordre du jour) of a meeting </item>
<label>CV</label>
<item>document contains an invitation (convocation) to a meeting </item>
<label>AUTRE</label>
<item>document is of some other type </item>
</list>
</p>
<p>The attribute <att>xml:id</att> is used on the <gi>TEI</gi> element to supply a unique
identifier for the document it represents. This identifier combines the scan number, the
date of the meeting concerned, and one of the above document type codes, as shown in the
example below. This type code is also supplied as the value of the <att>type</att>
attribute on the <gi>text</gi> element.</p>
<p>Here for example is the structure of the document containing the minutes of the meeting
held in January 1961, which corresponds with scan number T10010004: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<TEI xml:id="t10010004-1961-01-cr-v">
<teiHeader>
<!-- ... -->
</teiHeader>
<text type="CR">
<body>
<!-- ... -->
</body>
</text>
</TEI>
</egXML>
</p>
<p>Note that the <gi>text</gi> element always contains a <gi>body</gi> element which is used
to enclose all the text transcribed from the document. </p>
<p>
<specList>
<specDesc key="text" atts="type"/>
<specDesc key="body"/>
</specList>
</p>
<p>The TEI encoding scheme allows for hierarchic divisions of the <gi>body</gi> element to
be indicated by <gi>div</gi> elements, although this has not yet been used by the majority
of transcribed documents. Where it is used, and where a division has one or more distinct
headings, the <gi>head</gi> element may be used to mark these.<specList>
<specDesc key="div"/>
<specDesc key="head"/>
</specList>
</p>
<div>
<head>Page and line breaks </head>
<p>Within the body of a transcription, an empty <gi>pb</gi> element appears at the start
of each new page. Its <att>n</att> attribute may be used to provide a page number if
this is present. Its <att>facs</att> attribute provides a link to the digital facsimile
of the page being transcribed. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<p>
<term ref="#oulipo">OuLiPo</term> : Organisme qui se propose d’examiner en quoi et
par quel moyen, étant donnée une théorie scientifique concernant éventuellement le
langage (donc : l’anthropologie), on peut y introduire du plaisir esthétique
(affectivité et fantaisie).</p>
<pb facs="difdepo:T10010007-1961-04-17-cr-03" n="3"/>
<p>
<term ref="#oulipiens">Oulipiens</term> : Rats qui ont à construire le <term
ref="#labyrinthe">labyrinthe</term> dont ils se proposent de sortir. </p>
</egXML>
<!-- t10010007-1961-04-17-cr.xml -->
</p>
<p>The empty <gi>lb</gi> element is also used on occasion to mark particularly significant
line breaks in the text. More usually however, the line breaks of the original source
are not considered to be of significance and are not preserved since the main purpose of
the encoding is not to capture the physical appearance of each document: this is better
done by the scanned images. Instead, the encoding aims to capture the basic rhetorical
structure of each document, and to flag some significant features within it, notably the
presence of technical terms, references to named entities such as people or places,
titles of works, etc. </p>
<p>
<specList>
<specDesc key="pb"/>
<specDesc key="lb"/>
</specList></p>
</div>
<div>
<head>Paragraphs and lists</head>
<p>The transcribed texts use the TEI <gi>p</gi> element for any block of text, including
some list items and (occasionally) headings. A number of other elements are available
within the <gi>p</gi> element in addition to plain text (in this and the following
example, the elements <gi>term</gi> and <gi>persName</gi> appear, for example; ): we
discuss these further below. </p>
<p>Note that the initial paragraphs in a document, which typically contain metadata such
as its function, place, etc., are marked with the special <att>rend</att> value
<val>incipit</val>. Their content is duplicated in the TEI Header. </p>
<p>A list of items, particularly a numbered list, should for preference be marked up using
the standard <gi>list</gi> and <gi>item</gi> elements as in the following example:
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<p>Les absents s’étant excusés eux-mêmes, le <persName ref="#president"
>Président</persName> se donne la parole assez facilement, pour constater que
:</p>
<list type="ordered">
<item>le point (a) de l’ordre du jour (les <term>monosyllabes</term>
d’<persName>Amédée Pommier</persName>) est, en l’absence d’<persName>A.M.
Schmidt</persName>, exclu du dit ordre ;</item>
<item>qu’il en est de même du point (c), en l’absence de <persName>S. Exc.
Q.B</persName>. ;</item>
<item>qu’en l’absence des mathématiciens, le point (b) doit être reporté à une date
ultérieure</item>
</list></egXML>
</p>
<p>
<specList>
<specDesc key="p"/>
<specDesc key="list"/>
<specDesc key="item"/>
</specList>
</p>
<p>It may not always be possible to capture the structure of text presented as lists
exactly : the markup in such cases will simply show each item as a new <gi>p</gi>
element. </p>
</div>
<div>
<head>Rubrics and Headings</head>
<p>It is also often difficult to represent the organisation of a document with multiple
headings and subheadings using the traditional TEI <gi>div</gi> and <gi>head</gi>
approach mentioned above. Instead, where a paragraph (or a part of one) seems to be
functioning as a rubric or heading, the <gi>label</gi> element may be used, as in the
following example: </p>
<p>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<p><label type="rubrique">3) Bibliothèque oulipienne</label></p>
<list type="unordered">
<item>Bilan <persName>Marcel</persName> Diffusion, distribution et dépôt.</item>
<item>Calcul du prix <persName>Marcel</persName> et <persName>Paul</persName></item>
<item>Phynance <persName>Marcel B</persName></item>
</list>
<p><label type="rubrique">4) Phynances</label></p>
<list type="unordered">
<item><persName>Mme Brun</persName> - <persName>Dominique</persName></item>
<item>Appel secrétariat. <persName>Fournel</persName></item>
</list>
<!-- t100110205-1978-04-oj -->
</egXML>
</p>
<p>The <att>type</att> attribute on <gi>label</gi> usually has the value
<val>rubrique</val> when it has this function. It can also take the value
<val>locuteur</val>, to indicate that the label indicates the person speaking (as in a
conventional drama). </p>
<p><specList>
<specDesc key="label" atts="type"/>
</specList></p>
<!--<p>The <gi>lb</gi> is available to mark places where lineation is considered important. <specList>
<specDesc key="pb"/>
<specDesc key="lb"/>
</specList></p>
<p>Lineation is retained in the following example <egXML
xmlns="http://www.tei-c.org/ns/Examples"><p rend="incipit">Excusés: <persName ref="#JB"
>Bens</persName>, <persName ref="#AB">Blavier</persName>, <persName ref="#JQ"
>Queval</persName> et <unclear>paulets?? <persName ref="#matheny"
>Matheny</persName></unclear>
<lb/>Esperé: <persName ref="#JR">Roubaud</persName>, <persName ref="#PB"
>Braffort</persName>
<lb/>Retard: <persName ref="#JR">Jacques Roubaud</persName></p>
</egXML></p>-->
</div>
<div>
<head>Transcriptional issues</head>
<p>Although the intention of the project is not to produce a full critical edition, there
are occasional passages where some editorial mark up is necessary, for example where the
transcription is uncertain, or discontinuous, or where it is desired to record that
something was deleted in the original. </p>
<p>In the following example, the transcriber is uncertain as to whether the word
<mentioned>miquerel</mentioned> has been correctly transcribed, and indicates this
with the <gi>unclear</gi> tag. <egXML xmlns="http://www.tei-c.org/ns/Examples"><p>
<label type="rubrique">Arrivée de <persName>Calvino</persName> (qui passe ce soir à
<name type="manif">Apostrophes</name> et qui est un peu
<unclear>miqurel</unclear>).</label></p>
</egXML>
</p>
<p>In the following example, the transcriber is unable to make a guess as to what the
reading might be, and has therefore used a <gi>gap</gi> element to indicate that there
is something missing from the transcription: <egXML
xmlns="http://www.tei-c.org/ns/Examples"><p>... <persName>PF</persName> propose de
traduire <title>Mein Kampf</title> qui est sans doute la <gap/> de « La
Recherche ».</p>
</egXML>
<!-- T10010246-1982-01-CR.xml --></p>
<p>In the following example, the transcriber wishes to indicate that the word
<q>Compléments</q> is present but has been crossed out in the source : <egXML
xmlns="http://www.tei-c.org/ns/Examples"><p>
<label type="rubrique">Création</label>
</p>
<list type="unordered">
<item><persName>Marcel Bénabou</persName> : les <del>Compléments</del> la Poésie
paronynymiques</item>
<item><persName>François Caradec</persName> : Défi de Roubaud</item>
</list></egXML>
</p>
<p><specList>
<specDesc key="unclear"/>
<specDesc key="gap"/>
<specDesc key="del"/>
</specList></p>
<!-- <p>For passages whose visual salience is considered of particular importance: <specList>
<specDesc key="hi"/>
</specList> In practice, this is used only for (some) superscripted passages, with its
<att>rend</att> attribute taking the value <val>sup</val>. </p>-->
</div>
<div>
<head>Terms, Names, and Notes</head>
<p>Words and phrases representing particular concepts or themes of Oulipian significance
are marked using the <gi>term</gi> element, to facilitate construction of a thematic
index of these items. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<p>
<persName>LE</persName> : système de la <term>contrainte provisoire</term> :
construire le texte sur une contrainte, puis le traduire en langage normal </p>
</egXML>
</p>
<p>Words or phrases containing the name of some external event such as a conference or
exhibition are identified and marked up using the <gi>name</gi> element, with its
<att>type</att> value set to <val>manif</val>, as in the following example. <egXML
xmlns="http://www.tei-c.org/ns/Examples"><p>
<persName>Paul Braffort</persName> fait une communication sur le récent <name
type="manif">colloque de Besançon</name> sur la <term>lexicographie</term>.</p>
</egXML>
<!-- t10010009-1961-06-27-cr-->
</p>
<p>Note that the <gi>name</gi> element is also used to mark the name of an encoder or
editor recorded as part of the Header metadata. Names of people, places, organizations,
or works appearing in the text are marked up using the specialised <gi>persName</gi>
etc. elements discussed in section <ptr target="#namedEnts"/> below. </p>
<p>Where possible, foot notes or end notes are marked up using the <gi>note</gi> element.
This element replaces the siglum indicating the presence of a footnote, and contains the
text of the foot note itself. The attribute <att>n</att> holds the footnote siglum, and
the attribute <att>place</att>, with values <val>foot</val> or <val>end</val>, indicates
the position of the note text in the original source. In this example, the text
<q>D'autres alexandrins...</q> appears at the foot of the page. </p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"><p> ... on salua gravement Lady Godiva,
puis on siffla des kirs correctement dosés<note n="1" place="foot">
<p>D’autres <term>alexandrins</term> seront dissimulés. Cherchez-les ! C’est un jeu
de vacances. (Aucun prix ne sera décerné.)</p>
</note>.</p><!-- t10010010-1961-08-cr--></egXML>
<p><specList>
<specDesc key="term"/>
<specDesc key="name" atts="type"/>
<specDesc key="note" atts="n place"/>
</specList></p>
</div>
<div xml:id="namedEnts">
<head>Proper names</head>
<p>Within the transcription, the names of persons, places, organizations, and works are
marked using the appropriate element chosen from the following list: <specList>
<specDesc key="persName"/>
<specDesc key="placeName"/>
<specDesc key="orgName"/>
<specDesc key="title"/>
</specList></p>
<p> In each case, the <att>ref</att> attribute may be supplied in order to provide a code
which identifies the entity (the person, place, organisation, or work) being referred to
by this name. This is used so that different forms of a name can be resolved to indicate
a single named entity. For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
<persName ref="#RQ">Raymond Queneau</persName> ..... <persName ref="#RQ">RQ</persName>
... Le <persName ref="#RQ">Satrape Queneau</persName>... </egXML> The same code
(<code>RQ</code>) is used for each of the various forms of the name here. It supplies
the identifier of a <gi>person</gi> element elsewhere in the corpus, which groups
information about the person being referred to. </p>
<p>The <gi>placeName</gi> and <gi>orgName</gi>elements can be used in the same way: <egXML
xmlns="http://www.tei-c.org/ns/Examples"><placeName ref="#restoLaborderie">restaurant
Laborderie</placeName></egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples"><p>Le président parla d’abord, pour
faire part d’une lettre de M. <persName ref="#jeancocteau">Jean Cocteau</persName>
(de l’<orgName ref="#acadFrancaise">Acadéfraise</orgName>)....</p>
</egXML>
</p>
<p>The values used for the <att>ref</att> attribute here and elsewhere are arbitrary
codes, originally generated automatically during processing, and then refined manually
to eliminate duplicates and resolve ambiguities. This is however a work in progress.
</p>
</div>
</div>
<div>
<head>The entity database</head>
<p>Corresponding with these <q>entity reference</q> tags, the project maintains an <q>entity
database</q>. This is a separate TEI document containing lists of persons, places,
organizations, events, and works referenced by the corpus. The following elements are used
in this document : <specList>
<specDesc key="listPerson"/>
<specDesc key="person"/>
<specDesc key="listPlace"/>
<specDesc key="place"/>
<specDesc key="listOrg"/>
<specDesc key="org"/>
<specDesc key="listBibl"/>
<specDesc key="bibl"/>
<specDesc key="listEvent"/>
<specDesc key="event"/>
</specList></p>
<div>
<head>People</head>
<p>The <gi>listPerson</gi> element contains several <gi>person</gi> elements, within each
of which the following elements may be used: <specList>
<specDesc key="persName"/>
<specDesc key="birth"/>
<specDesc key="death"/>
<specDesc key="affiliation"/>
</specList></p>
<p>Each of these elements can carry dating attributes to indicate the period during which
they are considered applicable to the person concerned. These attributes include
<att>when</att> to indicate an exact date, and <att>notBefore</att> and
<att>notAfter</att> to indicate a range of possible dates. It is thus possible to
indicate each of person's (possibly many) names or affiliations at different times in
their life. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<person xml:id="MD" n="15">
<persName>Marcel Duchamp</persName>
<birth when="1887"/>
<death when="1968-10-02">Excusé depuis le 2 octobre 1968</death>
<affiliation when="1962-03-16">Entré à l'Oulipo le 16 mars 1962 </affiliation>
</person>
</egXML>
</p>
</div>
<div>
<head>Places and organizations</head>
<p>A list of places referenced is held in a <gi>listPlace</gi> element, which contains
several <gi>place</gi> elements, within each of which the following elements may be
used: <specList>
<specDesc key="placeName"/>
</specList>
</p>
<p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples"><listPlace>
<place xml:id="#restaurantlaborderie">
<placeName>restaurant Laborderie</placeName>
</place></listPlace></egXML>
</p>
<p>A list of organisations referenced is held in a <gi>listOrg</gi> element, which
contains several <gi>org</gi> elements, within each of which the following elements may
be used: <specList>
<specDesc key="orgName"/>
</specList></p>
<p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
<listOrg>
<org xml:id="myam">
<orgName>M Y A M</orgName>
</org>
<org xml:id="acadFran">
<orgName>Académie Francaise</orgName>
<orgName>Acadéfraise</orgName>
</org><!--...--></listOrg>
</egXML>
</p>
</div>
<div>
<head>Works and Events</head>
<p>A list of books, songs, films etc. referenced is held in a <gi>listBibl</gi> element,
which contains several <gi>bibl</gi> elements, within each of which the following
elements may be used: <specList>
<specDesc key="title"/>
</specList></p>
<p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
<bibl xml:id="leducationsentimentale">Gustave Flaubert : <title>L’Education
sentimentale</title></bibl>
</egXML>
</p>
<p>A list of events, manifestations, etc referenced is held in a <gi>listEvent</gi>
element, which contains several <gi>event</gi> elements, within each of which the
following elements may be used: <specList>
<specDesc key="desc"/>
<specDesc key="label"/>
</specList></p>
<p>For example: <egXML xmlns="http://www.tei-c.org/ns/Examples">
<event xml:id="concoursdesartistes">
<label>Concours des Artistes</label>
<desc><!-- description du concours a fournir --></desc>
</event>
</egXML>
</p>
</div>
</div>
<div>
<head>The TEI Header</head>
<p>Every document is prefixed by a TEI Header, providing minimal metadata information. The
data initially stored in the header is automatically generated from data captured by a
Word template. As with every TEI document, the header is represented by a
<gi>teiHeader</gi> element, containing a <gi>fileDesc</gi> element, followed by a
<gi>revisionDesc</gi> element. </p>
<p>The <gi>fileDesc</gi> for a difDepo document uses the following standard TEI components: <specList>
<specDesc key="titleStmt"/>
<specDesc key="publicationStmt"/>
<specDesc key="sourceDesc"/>
</specList>
</p>
<p>The <gi>titleStmt</gi> always contains a <gi>title</gi> element followed by at least one
<gi>respStmt</gi> element. The <gi>title</gi> contains a formulaic title for the
document in the following form: <eg>Transcription du scan [number of scan] pp. [first page
number] à [second page number] ([document type]) : version TEI</eg>. The [number of
scan] is also used to identify the file name containing the document and is allocated by ?
. The first and second page numbers are always given even if they are the same, and even
if they are both 1. The document type is the two letter code used also as the value for
the <att>type</att> attribute on the associated <gi>text</gi> element (see <ptr
target="#textType"/>). </p>
<p>The <gi>respStmt</gi> element is used to indicate responsibility for the content of the
document, and has two components: a <gi>resp</gi> element indicating the type of
responsibility (for example <code>transcription</code>) and a <gi>name</gi> element
providing the name of the person concerned. For example: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<respStmt>
<resp>transcription</resp>
<name>Susie Cronin</name>
</respStmt></egXML>
</p>
<p>The <gi>publicationStmt</gi> always contains the same formulaic text indicating the
distributor of the document: <eg> Edition numérique distribué par le projet ANR DifDePo
</eg></p>
<p>The <gi>sourceDesc</gi> element always contains a single <gi>bibl</gi> element, which
also has a comparatively restricted structure. In a difDepo document, the <gi>bibl</gi>
element must contain either a string of text without any tagging, or at least one
<gi>idno</gi> element, followed by one of the following elements: <specList>
<specDesc key="meeting"/>
<specDesc key="title"/>
</specList></p>
<p>The <gi>idno</gi> element contains an identifier for the document being described. The
<att>type</att> attribute is used to distinguish amongst various kinds of identifier
used, and may have the following values: <list type="labelled">
<label>ark</label>
<item>BNF "ark" archival identifier</item>
<label>ead</label>
<item>BNF EAD format identifier</item>
<label>[none]</label>
<item>Difdepo identifier (the identifier for the meeting followed by the code for the
type of meeting)</item>
</list></p>
<p>The <gi>meeting</gi> element is used only when the document contains a compte rendu, in
which case the corresponding <gi>text</gi> element will have a <att>type</att> of
<val>CR</val>. The <gi>meeting</gi> element should have an <att>xml:id</att> attribute,
supplying the identifier of the meeting, which will usually be the same as the identifier
of the document, without the suffix indicating the type (CR., CV etc.) It must contain a
<gi>date</gi> element, giving the date of the meeting, which may be followed by a
<gi>placeName</gi> element giving the place of the meeting, if this is specified. A
<gi>list</gi> element, with <att>type</att> of <val>present</val> completes the element
and supplies a list of those attending the meeting, as in the following example: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<bibl>
<idno type="ark">12148/btv1b10010018z</idno>
<idno type="ead">d0e408</idno>
<idno>t10010018-1962-04-cr</idno>
<meeting xml:id="t10010018-1962-04">
<date when="1962-04-12"/>
<list type="present">
<item>
<persName ref="#RQ"/>
</item>
<!-- ... -->
<item>
<persName ref="#JB"/>
</item>
<item>
<persName role="président" ref="#JL"/>
</item>
</list>
</meeting>
</bibl>
</egXML>
</p>
<p>In the header, the <gi>title</gi> element is used for any other kind of documents (OJ,
for ordres du jour; CV for convocations). It contains a formulaic characterization of the
kind of document concerned, including a <gi>ref</gi> element which points to the
<gi>meeting</gi> element concerned, and (optionally) a <gi>date</gi> indicating the date
of the document itself. Here is a typical ordre du jour <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<title>Ordre de jour de <ref target="#T10010007-1961-05-03">la réunion Oulipo</ref> du
<date when="1961-05-03">mai 1961</date></title></egXML>
</p>
<p>Here is a typical convocation <egXML xmlns="http://www.tei-c.org/ns/Examples">
<title>Convocation à <ref target="#T10010273-1984-07">une réunion Oulipo</ref>, envoyée
le <date when="1984-07-01"/> par <persName role="expéditeur">PF</persName>
Destinataire : <persName role="destinataire">XX</persName></title>
</egXML>
</p>
<p>When, as in the above example, the title contains names or dates, these will usually be
tagged using the <gi>date</gi> or <gi>persName</gi> element. The <att>when</att> attribute
on <gi>date</gi> supplies a normalised form of the date: it must always be provided
whether or not the date is provided as content of the <gi>date</gi> element. The
<att>role</att> attribute on <gi>persName</gi> is used to indicate the role of the
person referenced: in the above example, Fournel issued the invitation, but the person to
whom it was sent is not known. The <att>role</att> attribute can take the following
values: <list type="gloss">
<label>invité</label>
<item>person invited to a meeting</item>
<label>président</label>
<item>president or chair of a meeting</item>
<label>secrétaire</label>
<item>secretary or note taker of a meeting</item>
<label>expéditeur</label>
<item>person responsible for sending an invitation</item>
<label>destinataire</label>
<item>person to whom an invitation is sent</item>
</list>
</p>
<!-- <p>A <gi>bibl</gi> element may occasionally be used to document a non-archival document, for
example </p>
-->
<p>The <gi>revisionDesc</gi> element for a difDepo document uses the following standard TEI
components: <specList>
<specDesc key="revisionDesc"/>
<specDesc key="listChange"/>
<specDesc key="change"/>
</specList>
</p>
<p>A revision description contains a list of significant changes to the document, in reverse
chronological order (most recent first). Each change is indicated by a <gi>change</gi>
element. The date of the change is given by its <att>when</att> attribute, and the nature
of the change by its content. The person responsible for the change may be indicated by
its <att>who</att> attribute. <!-- or @resp --></p>
<p>For this project, every document contains one <gi>change</gi> element created at the time
the document was first created in TEI XML form. Additional <gi>change</gi> elements may be
automatically created and inserted for later stages of the development of the archive.</p>
</div>
<xi:include href="difdepo.odd"/>
</body>
</text>
</TEI>