-
Notifications
You must be signed in to change notification settings - Fork 7
/
msdesc.odd
5299 lines (5099 loc) · 370 KB
/
msdesc.odd
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
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!--<?xml-model href="http://jenkins.tei-c.org/job/TEIP5/lastSuccessfulBuild/artifact/P5/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://jenkins.tei-c.org/job/TEIP5/lastSuccessfulBuild/artifact/P5/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>-->
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en"
xmlns:sch="http://purl.oclc.org/dsdl/schematron">
<teiHeader>
<fileDesc>
<titleStmt>
<title>TEI P5 Customization and Encoding Guidelines for Manuscript Description</title>
</titleStmt>
<editionStmt>
<edition>1.0 (April 2020)</edition>
</editionStmt>
<publicationStmt>
<publisher>Bodleian Library, Oxford</publisher>
<availability status="free">
<licence target="https://creativecommons.org/licenses/by/4.0/">Creative Commons
Attribution 4.0 International</licence>
</availability>
</publicationStmt>
<notesStmt>
<note>Medieval manuscript guidelines written by James Freeman and Matthew Holford
and encoded by Matthew Holford</note>
<note>Medieval manuscript guidelines owe a debt to and incorporate some material from
those created by Patrick Granholm and Eva Nyström for <ref
target="https://www.manuscripta.se/"><title>Manuscripta</title></ref> and
licenced CC BY 4.0</note>
<note>Additional guidelines for non-medieval manuscripts added from <ref
target="https://github.com/fihristorg/fihrist-mss/raw/master/archive/old_manual.pdf"
>Fihrist Cataloguing Manual</ref></note>
</notesStmt>
<sourceDesc>
<p>Born digital</p>
</sourceDesc>
</fileDesc>
<revisionDesc>
<change when="2020-04-03" who="#MLH">Add opener; new attribute for handNote: @execution; add attribute values for handNote and decoNote; make layout part of att.typed; allow biblStruct and associated elements; add guidance on extracts; add guidance on collation vocabulary; use measure rather than num for better TEI compliance.</change>
</revisionDesc>
</teiHeader>
<text>
<body>
<opener>These guidelines represent a community effort to develop uniform good practice in the cataloguing manuscripts using TEI. They are currently used by cataloguers at a number of institutions including the British Library, the Bodleian Libraries, Cambridge University Library, the John Rylands Library, and the Wellcome Trust. They remain under development and contributions are welcome via pull requests or issues submitted to the <ref target="https://github.com/msDesc/consolidated-tei-schema">GitHub repository</ref>.</opener>
<divGen type="toc" xml:id="toc"/>
<div xml:id="documentation">
<head>Encoding guidelines</head>
<div xml:id="introduction">
<head>Introduction</head>
<p>TEI P5 ODD Customization for <title>Manuscripts in Oxford Libaries and the
Fihrist and Senmai union catalogues</title>
<!--was created by Patrik Granholm and Eva Nyström, and is released under a <ref target="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license</ref>.--></p>
</div>
<!-- todo: general intro, principles, differences from usual TEI, camelCase for attributes -->
<div xml:id="acknowledgements">
<head>Acknowledgements</head>
<p>These draft guidelines are currently based on two main sources - the encoding
guidelines for the Fihrist project [<ref
target="https://github.com/fihristorg/fihrist-mss/raw/master/archive/old_manual.pdf"
>pdf</ref>], and encoding guidelines for medieval manuscripts jointly
created by Cambridge University Library (James Freeman, with Suzanne Paul)
and the Bodleian Library (Matthew Holford) with contributions by Andrew
Dunning (formerly British Library). The medieval guidelines in turn draw in
places on the guidelines created by Patrick Granholm and Eva Nyström for
<ref target="https://www.manuscripta.se/"
><title>manuscripta.se</title></ref>.</p>
</div>
<div xml:id="phraselevel">
<head>General principles</head>
<div xml:id="foreign">
<head>Foreign Phrases and Words</head>
<p>Phrases or words in other languages than English may be tagged by adding
the <att>xml:lang</att> attribute to the element enclosing the text, or
where no other element is available with a <gi>foreign</gi> element and
a <att>xml:lang</att> attribute. By default this text displays in italic
when rendered in the online catalogue.
<!--<egXML xmlns="http://www.tei-c.org/ns/Examples"> The total amount paid for the two volumes was 84 <foreign xml:lang="sv">Daler kopparmynt</foreign>. </egXML>-->
</p>
</div>
<div xml:id="locus">
<head>References to Locations within a Manuscript</head>
<p>References to a specific location or range within a manuscripts should be
given in a <gi>locus</gi> element. The <att>from</att> and <att>to</att>
attributes are optional but recommended, as they enable links to images
to be generated and allow calculation of the length of manuscript
items.</p>
<p>If <att>from</att> and <att>to</att> attributes are used to refer to a
specific folio or page they should be used with identical values. The
foliation scheme should be specified in the <att>scheme</att> attribute
with the value <val>folios</val> or <val>pages</val> (the default is
assumed to be <val>folios</val>. Lines and/or columns may be specified,
e.g. fol. 1r, col. a, line 10 to fol. 2v, column b, line 5. </p>
<p>If reference to columns of text is necessary, use lower-case letters: a,
b, c, etc. The lettering should begin with the first column on the left,
and move across to the right. The sequence should begin afresh on each
page (i.e. the letters do not run concurrently from recto to verso, or
across an opening). </p>
<p>To identify columns / lines in the <att>from</att> or <att>to</att>
attributes, use (for example): <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<locus from="1ra10" to="2vb5">(fols. 1ra, line 10 - 2vb, line
5)</locus>
</egXML></p>
<p>Text in margins: <egXML xmlns="http://www.tei-c.org/ns/Examples">
<locus from="1r" to="10r">(fols. 1r-10r, margins)</locus>
</egXML>
</p>
<p>For texts scattered over more than one location in the manuscript the
<gi>locusGrp</gi> element should be used. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<locusGrp>
<locus from="356rb" to="356vb">Fols 356<hi rend="superscript"
>rb-vb</hi>,</locus>
<locus from="374ra" to="374rb">374<hi rend="superscript"
>rab</hi></locus>
</locusGrp>
</egXML>
</p>
<!-- todo: attribute for marginal text? -->
</div>
<div xml:id="personalnames">
<head>Personal Names</head>
<p>Persons, if not in an <gi>author</gi> or <gi>editor</gi> element, should be tagged using the
<gi>persName</gi> element. For indexing to function correctly this
MUST be linked to the persons authority file using the <att>key</att>
attribute. The role of the person referred to should be indicated using
the <att>role</att> attribute. Values should correspond to the Library
of Congress relator term list (<ref
target="http://www.loc.gov/marc//relators/relaterm.html"
>http://www.loc.gov/marc//relators/relaterm.html</ref>). The most
commonly occurring roles are: "aut" (author), "bnd" (binder), "scr" (scribe), "art"
(artist; NB this is preferred to illustrator), "fmo" (former
owner),"sgn" (signer), "pat" (patron). If necessary, multiple roles can
be separated with whitespace. <egXML
xmlns="http://www.tei-c.org/ns/Examples"> Common-place book of
<persName role="scr fmo" key="person_697">John
Curteys</persName> of Winchester College and New College, Oxford
</egXML>
</p>
<p>To record alternative names for a person in such contexts, use nested <gi>persName</gi>
elements, for example:
<egXML
xmlns="http://www.tei-c.org/ns/Examples">
<persName key="person_f6124" role="scr">
<persName xml:lang="fa-Latn-x-lc">ʿAbd al-Raḥmān</persName>
(<persName xml:lang="fa">عبد الرحمان</persName>)
</persName>
</egXML>
</p>
<p>Use "fmo" where there is evidence that a person owned an item. Use "sgn"
where the person is only associated with the item by a signature or an
inscription which does not necessarily imply ownership. "dnr" (donor)
may be used where the person gave the manuscript to an institution but
evidence of ownership before the gift is lacking; i.e. to describe
manuscripts apparently bought or made with the intention of being
directly presented, or manuscripts may have been purchased with money
given by a donor rather than directly presented.</p>
<!-- TODO: query whether this is actually a useful and maintainable distinction -->
</div>
<div xml:id="orgnames">
<head>Corporate / Organization Names</head>
<p>Corporate entities should be tagged using the <gi>orgName</gi> element.
For indexing to function correctly this MUST be linked to the persons
authority file using the <att>key</att> attribute. The role of the
organization referred to should be indicated using the <att>role</att>
attribute. Values should correspond to the Library of Congress relator
term list (<ref target="http://www.loc.gov/marc//relators/relaterm.html"
>http://www.loc.gov/marc//relators/relaterm.html</ref>). Separate
multiple roles with whitespace. <egXML
xmlns="http://www.tei-c.org/ns/Examples"><orgName role="fmo"
key="org_148998848">Würzburg, Domstift St Kilian</orgName>,
12th-century ex libris, fol. 1r, and 15th-century shelfmark, fol.
2r.</egXML>
</p>
</div>
<div xml:id="placenames">
<head>Placenames</head>
<p>In sections relating to manuscript contents, physical description and
provenance, placenames should be tagged using the <gi>placeName</gi>.
For indexing to function correctly this MUST be linked to the places
authority file using the <att>key</att> attribute. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<placeName key="place_1234">Bologna</placeName>
</egXML>
<specList>
<specDesc key="placeName" atts="key"/>
</specList>
</p>
<p>In the <gi>origPlace</gi> element, placenames should be tagged using (as
appropriate) <gi>country</gi>, <gi>region</gi> and <gi>settlement</gi>.
Again, for indexing to function correctly these MUST be linked to the
places authority file using the <att>key</att> attribute. See under <ref
target="#origPlace">origPlace</ref>.</p>
<p>To accommodate geodata in legacy data, or for use by other systems,
<gi>geo</gi> elements are permitted. But they are not displayed in
catalogue web sites. For example, from the International Dunhuang
Project:</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<origPlace>DHMG.(Dunhuang Mogao) DHMG.17. <geo n="min"
>94.80388888888889198 40.03638888888888658</geo>
<geo n="max">95.9375 40.04833333333333201</geo>
</origPlace>
</egXML>
<p>In other cataloguing projects geodata should be given in the places
authority file.</p>
</div>
<div xml:id="hyperlinks">
<head>Hyperlinks</head>
<p>Hyperlinks may be created using the <gi>ref</gi> element with the URL as
the value of the <att>target</att> attribute. This can be used to
provide links to relevant electronic resources.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"><ref
target="http://www.dimev.net/record.php?recID=4633">DIMEV
4633</ref></egXML>
</div>
<div xml:id="formatting">
<head>Formatting</head>
<p>In general, where possible, formatting should be carried out using
semantic markup rather than using the <gi>hi</gi> element.</p>
<p>However, where use of the <gi>hi</gi> element is unavoidable, it should
be used with the following values on <att>rend</att>: <list>
<item><val>superscript</val></item>
<item><val>subscript</val></item>
<item><val>underline</val></item>
<!-- ... ? todo finish-->
</list></p>
<p>Multiple values may be separated by whitespace.</p>
<p>If correct formatting is not possible using these values, raise an issue
on GitHub to add further values.</p>
</div>
<div xml:id="attributeValues">
<head>Attribute values</head>
<p>Attribute values forming more than one word in natural language should be
given in camelCase.</p>
</div>
<div xml:id="transcription">
<head>Transcription</head>
<p>Transcriptions from the manuscript in the <gi>rubric</gi>,
<gi>incipit</gi>, <gi>explicit</gi>, etc. elements, or in the
provenance section, should be made diplomatically.
<!-- todo: check re. &, et --> Expand standard abbreviations silently.
If the abbreviation can be expanded with some but not complete
confidence, enclose the expansion in the <gi>ex</gi> element. Denote
uncertain or ambiguous abbreviations with the character ’ [U0146], e.g.
Westm’</p>
<p>Use capital letters only when they appear in the manuscript.</p>
<p>Transcription of special characters: e-caudata should be transcribed
using U+0119: Latin Small Letter E With Ogonek</p>
<p>The relevant elements from the TEI transcription module should be used
(see especially 11.3.3.2,
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHCOMB) </p>
<p>For retroconversion, reproduce the text as given in the printed
catalogue. Where abbreviation is indicated typographically, e.g. with
italic font or between parentheses, indicate this using the <gi>ex</gi>
element. Typographic indications of insertion, deletion, omission,
supplied text, etc., using symbols such as [], \/, should be replaced
with the relevant elements from the TEI transcription module.</p>
<p>Manuscript punctuation may be simplified by replacing the punctus versus
and punctus elevatus with a point (.).</p>
<!-- todo: check? -->
<p>Indicate damage using the <gi>damage</gi> element.</p>
<p>Errors in the manuscript may be indicated using the <gi>sic</gi> and
<gi>corr</gi> and <gi>choice</gi> elements. <gi>sic</gi> by itself
simply signals the presence of an error, <gi>corr</gi> provides the
correction. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<!-- MS. Add. C. 145 --> Explicit <sic>loica</sic> magistri pauli de
Venetijs </egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<!-- MS. Add. C. 145 --> Explicit
<choice><sic>loica</sic><corr>logica</corr></choice>
magistri pauli de Venetijs </egXML>
</p>
<p>The <gi>supplied</gi> element should be used for editorial additions,
with the <att>reason</att> attribute (sample values: <val>omitted</val>,
<val>illegible</val>, <val>damage</val>, or <val>unknown</val>). <specList>
<specDesc key="supplied" atts="reason"/>
<specDesc key="ex"/>
<specDesc key="sic"/>
</specList>
</p>
<p>Deletions by the scribe or later annotators should be recorded using the
<gi>del</gi> element. The <att>rend</att> attribute may be used to
indicate the manner of erasure: suggested values include
<val>strikethrough</val> (the text has a line through it),
<val>erasure</val> (the text has been scraped off),
<val>expunction</val>. <!-- todo: more? -->
<specList>
<specDesc key="del" atts="rend"/>
</specList>
</p>
<p>Additions by the scribe or later annotators should be recorded using the
<gi>add</gi> element, with the <att>place</att> attribute. The
values of the place attribute should be one of the values specified in
the <ref target="http://www.stoa.org/epidoc/gl/latest/ref-add.html"
>EpiDoc guidelines</ref>, e.g: <list>
<item><val>above</val>: written above the line</item>
<item><val>below</val>: written below the line</item>
<item><val>top</val>: written in the top margin</item>
<item><val>bottom</val>: written in the top margin</item>
<item><val>margin</val>: written in an unspecified margin</item>
<item><val>unspecified</val>: written in an unspecified
location</item>
</list>
<specList>
<specDesc key="add" atts="place"/>
</specList>
</p>
<p>Corrections by the scribe or later annotators should be recorded using a
combination of the <gi>add</gi> and <gi>del</gi> elements with the
<gi>subst</gi> or <gi>mod</gi> element. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<incipit>Theodocius dicit De coniugationibus apud grecos iii sunt
coniugationes uerborum
qu<subst><del>a</del><add>o</add></subst>rum prima
positione</incipit>
</egXML>
</p>
<p>Gaps should be marked with <gi>gap</gi> element, using the
<att>reason</att> attribute to described the nature of the gap, and
the <att>unit</att> attribute, in combination with <att>quantity</att>, and if necessary
<att>precision</att>, to specify its extent. This extent should be
indicated in characters if possible with the value <val>char</val> on the <att>unit</att> attribute. The
<att>atMost</att>, <att>atLeast</att> may be used instead of <att>quantity</att> but these will
be rendered as an ellipsis rather than a specific number of dots.
<list>
<head>Suggested values for <att>reason</att></head>
<item><val>damage</val>: text has been omitted due to damage to the
manuscript</item>
<item><val>illegible</val>: text has been omitted because it is
illegible (but the manuscript is not otherwise damaged)</item>
<item><val>editorial</val>: text (e.g. the formulaic ending of an
explicit) has been omitted for brevity</item>
<item><val>space</val>: the gap in the transcription represents
space that has been left in the manuscript itself, usually with
the intention of text being supplied at a later stage. (Note: do
not use this to transcribe initial letters which have been
omitted: these should be transcribed using the <gi>supplied</gi>
element.</item>
<item><val>lacuna</val>: there is no gap in the text being
transcribed, but the text is not complete (e.g. words or lines
have been omitted from an exemplar).</item>
</list>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<gap unit="char" quantity="5" reason="damage"/>
</egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<gap reason="illegible" atLeast="4" atMost="6" unit="char"/>
</egXML>
<!-- <specList>
<specDesc key="gap" atts="extent reason unit"/>
<specDesc key="unclear" atts="extent reason unit"/>
</specList>-->
</p>
<p>Questionable or partly legible readings should be marked with
<gi>unclear</gi> (generates a ‘(?)’ after the text in html)</p>
<p>Line beginnings should be indicated with empty <gi>lb</gi> elements,
column beginnings with empty <gi>cb</gi> elements</p>
</div>
<div xml:id="quotesFromMS">
<head>Quotations from the manuscript</head>
<p>Quotations from the manuscript, outside of elements such as
<gi>incipit</gi>, <gi>explicit</gi> and so on, should be enclosed in
the <gi>q</gi> element. This may have attribute <att>type</att> with
sample values: <list>
<item><val>pressmark</val>: the quotation is a pressmark, shelfmark
or similar</item>
<item><val>exLibris</val>: the quotation is an ex libris
inscription</item>
<item><val>inscription</val>: the quotation is the inscription of a
signer or reader</item>
<!-- todo: more? and check re quote element-->
</list></p>
</div>
<div xml:id="refsToMSS">
<head>References to other manuscripts</head>
<p>References in the description to other manuscripts should be enclosed in
<gi>bibl</gi> tags with <att>type</att> of value <val>MS</val>. The
<att>subtype</att> may be used to indicate if the manuscript is held
by the same institution that holds the manuscript being catalogued
(value <val>interal</val>) or by another institution (value
<val>external)</val>. In the former case, the shelfmark should not
include the location or institution name; in the latter case, location
and institution should be included.</p>
<p> The <gi>ref</gi> element may be used to provide a link to an online
catalogue or digital fascimile. <egXML
xmlns="http://www.tei-c.org/ns/Examples"> Eberbach, Cistercian abbey
(?): ‘modern’ chapter numbers added in boxes in the margin, as in
<bibl type="MS" subtype="internal">MS. Laud Lat. 107</bibl>. </egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples"> This scribe was also
responsible for most of the Simeon manuscript (<bibl type="MS"
subtype="external"><ref
target="http://www.bl.uk/manuscripts/FullDisplay.aspx?ref=Add_MS_22283"
>London, British Library, Add. MS. 22283</ref></bibl>) but
has not yet been identified in any other manuscripts or documents.
</egXML>
</p>
</div>
</div>
<div xml:id="header">
<head>The TEI Header</head>
<p>The TEI root element must always contain a declaration of the TEI namespace,
<!--a <att>version</att> attribute with the value <val>5.0</val>,--> and an
<att>xml:id</att> with the manuscripts unique identifier in the form
<val>manuscript_1234</val>.</p>
<p>The TEI element must have a <gi>teiHeader</gi> element and a
<gi>facsimile</gi> element, and may have a <gi>text</gi> element. The
<gi>teiHeader</gi> element in turn must have an <att>xml:lang</att>
attribute defining the language of the description, and a <gi>fileDesc</gi>
and <gi>revisionDesc</gi> element. The <gi>TEI</gi> element itself MUST have
an <att>xml:id</att> attribute whose value is the unique identifier for the
manuscript. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<TEI xml:id="manuscript_110">
<teiHeader xml:lang="en">
<fileDesc>
<titleStmt>
<!-- Title information -->
</titleStmt>
<publicationStmt>
<!-- Information about the publication -->
</publicationStmt>
<sourceDesc>
<!-- The MS description -->
</sourceDesc>
</fileDesc>
<revisionDesc>
<!-- Revision history -->
</revisionDesc>
</teiHeader>
<text>
<!-- Optional text -->
</text>
<facsimile>
<!-- Image information -->
</facsimile>
</TEI>
</egXML>
<!-- <specList>
<specDesc key="TEI" atts="version xml:id"/>
<specDesc key="fileDesc"/>
<specDesc key="facsimile"/>
</specList>-->
</p>
<div xml:id="filedescription">
<head>File Description</head>
<p>The <gi>fileDesc</gi> element contains a <gi>titleStmt</gi>,
<gi>publicationStmt</gi>, and <gi>sourceDesc</gi>
element.<!-- <specList>
<specDesc key="titleStmt"/>
<specDesc key="publicationStmt"/>
<specDesc key="sourceDesc"/>
</specList>-->
</p>
<div xml:id="titlestatement">
<head>Title Statement</head>
<!-- TODO: add title type="collection" and explain -->
<p>The <gi>titleStmt</gi> element summarizes the scope and authorship of
the TEI file, and the cataloguing project of which it is a part,
rather than for the manuscript itself (which is described in the
<gi>sourceDesc</gi>). It must contain (1) a <gi>title</gi>
element containing the manuscript shelfmark, (2) [for the medieval
catalogue] a <gi>title</gi> element with <att>type</att> attribute
of value <val>collection</val> describing the collection of which
the manuscript is a part, and (3) one or more <gi>respStmt</gi>
elements listing the person(s) responsible for the cataloguing and
encoding. The <gi>respStmt</gi> element must have a
<att>xml:id</att> attribute containing an identifier for the
person(s) responsible for the cataloguing and/or encoding. The name
should be recorded in a persName element (see <ptr
target="#personalnames"/>) and the role of the person
responsible in <gi>resp</gi> elements. If known, the date should be
given in the <att>when</att> attribute of <gi>resp</gi>
</p>
<!-- TODO: new example -->
<!-- todo: fix values for resp? -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<titleStmt>
<title>MS. Laud Misc. 108</title>
<title type="collection">MSS. Laud Misc. (Laud
miscellaneous)</title>
<respStmt xml:id="MLH">
<resp when="2018">Cataloguer</resp>
<resp when="2018">Encoding and markup</resp>
<persName>Matthew Holford</persName>
</respStmt>
</titleStmt>
</egXML>
<p>The <gi>titleStmt</gi> is also the place to record any funding bodies which
contributed to the cost of cataloguing. The <gi>funder</gi> element can
contain a plain text statement or <gi>orgName</gi> elements. The websites
of sponsors, and their logos, can be included. For example:</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<funder>
<orgName>
<ref target="https://www.yee.org.tr/">Yunus Emre Institute</ref>
<graphic url="https://www.yee.org.tr/sites/default/files/kurumsal/yunus_emre_enstitasa_logo-01.png"/>
</orgName>
</funder>
</egXML>
<p>Ideally the @url attribute of the <gi>graphic</gi> element should point to an
image hosted by the funding organization. The <gi>graphic</gi> element cannot
be a child of the <gi>funder</gi> element, but must be enclosed in a <gi>persName</gi>
or <gi>orgName</gi> element.</p>
<p>Contributions to the cost of purchasing the manuscript should be recorded
as part of the <ref target="#acquisition">Acquisition</ref> section of its history.</p>
<!-- <specList>
<specDesc key="titleStmt"/>
<specDesc key="title"/>
<specDesc key="funder"/>
<specDesc key="respStmt" atts="xml:id"/>
<specDesc key="persName" atts="ref"/>
<specDesc key="resp" atts="key"/>
</specList>-->
</div>
<div xml:id="responsibility">
<head>Responsibility</head>
<p>Where a description has been compiled from multiple sources, each
source should be listed in the <gi>respStmt</gi>, and the elements
of the description for which they are responsible should be
identified using the <att>resp</att> attribute with value equivalent
to that source's <att>xml:id</att>.</p>
<p>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<respStmt xml:id="PA">
<resp when="1973">Cataloguer</resp>
<persName>Otto Pächt</persName>
<persName>J. J. G. Alexander</persName>
</respStmt>
<respStmt xml:id="MH">
<resp when="2017">Encoding and markup</resp>
<persName>Matthew Holford</persName>
</respStmt>
<respStmt xml:id="SC">
<resp when="1897">Cataloguer</resp>
<persName>Falconer Madan</persName>
</respStmt>
<respStmt xml:id="DL">
<resp when="1984">Cataloguer</resp>
<persName>A. de la Mare</persName>
</respStmt>
<respStmt xml:id="DD">
<resp when="1984">Cataloguer</resp>
<persName>A. G. Watson</persName>
</respStmt>
</egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<provenance resp="#DL"><persName role="fmo" key="person_2854"
>William Wilson</persName>, F.S.A., of the Minories, his
sale, Christie's, 31 Jan.-1 Feb. 1833, lot 56 on 1 Feb.;
bought by Thorpe for £53. 11s.</provenance>
<provenance resp="#DL">Purchased from Thorpe by <persName
key="person_69848690" role="fmo">Douce</persName>, Feb.
1833.</provenance>
</egXML>
</p>
</div>
<div xml:id="publicationstatement">
<head>Publication Statement</head>
<p>The <gi>publicationStmt</gi> summarizes the publication of the TEI
document, rather than the manuscript itself (which is described in
the <gi>sourceDesc</gi>). For union catalogues such as Fihrist, it
should contain an <gi>email</gi> containing the address to which
enquiries should be sent, and an <gi>idno</gi> of <att>type</att>
<val>marcOrg</val> containing the MARC Organization Code of the
institution (e.g. "UkCu" for University of Cambridge).</p>
<p>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<publicationStmt>
<publisher>Special Collections, Bodleian
Libraries</publisher>
<address>
<orgName type="department">Special Collections</orgName>
<orgName type="unit">Bodleian Libraries</orgName>
<orgName type="institution">University of
Oxford</orgName>
<street>Weston Library, Broad Street</street>
<settlement key="place_7011931">Oxford</settlement>
<postCode>OX1 3BG</postCode>
<country>United Kingdom</country>
</address>
<distributor>
<email>[email protected]</email>
</distributor>
<!--Availability statement will be added here-->
<idno type="msID">MS_Laud_Misc_108</idno>
<idno type="collection">Laud Misc</idno>
<idno type="catalogue">Western</idno>
</publicationStmt>
<!-- TODO: availability statement -->
</egXML>
<!-- <specList>
<specDesc key="publicationStmt"/>
<specDesc key="publisher"/>
<specDesc key="date" atts="when"/>
<specDesc key="availability" atts="status"/>
<specDesc key="email"/>
</specList>-->
</p>
</div>
</div>
<div xml:id="revisiondescription">
<head>Revision Description</head>
<p>The <gi>revisionDesc</gi> element records ONLY major changes to the
catalogue entry, such as re-dating or re-location, addition of
provenance information, new identification of contents, etc. It must
contain at least one change element, which must have the <att>when</att>
attribute and may have the <att>who</att> attribute (which may be linked
to the xml:id of the person in the <gi>respStmt</gi> element in <ptr
target="#header"/>). The changes should be recorded in a reverse
chronological order with the most recent change first.</p>
<p><!-- TODO: change example -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<revisionDesc>
<change when="2018-06-15" xml:id="MMM"><persName>Mitch
Fraas/Mapping Manuscript Migrations</persName>
Provenance and acquisition information added using <ref
target="https://github.com/littlegustv/oxfordupdates/blob/master/test_case_for_oxford_prov.rb"
>https://github.com/littlegustv/oxfordupdates/blob/master/test_case_for_oxford_prov.rb</ref>
in collaboration with the <ref
target="http://mappingmanuscriptmigrations.org/">Mapping
Manuscript Migrations</ref> project.'</change>
<change when="2017-07-01">First online publication.</change>
</revisionDesc>
</egXML>
<!-- <specList>
<specDesc key="revisionDesc"/>
<specDesc key="change" atts="when who"/>
</specList>-->
</p>
</div>
</div>
<div xml:id="subjectclass">
<head>Subject Classifications</head>
<p>In some catalogues, the fourth button in the header is "Subjects" rather than
"Places". This is an index of subject classifications, using the Library of
Congress subject heading and name authorities.</p>
<p/>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<encodingDesc>
<classDecl>
<taxonomy xml:id="LCSH">
<bibl>
<ref target="http://id.loc.gov/authorities/about.html#lcsh"
>Library of Congress Subject Headings</ref>
</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<keywords scheme="#LCSH">
<list>
<item>
<term key="subject_sh2008111606">Shafiites--Early works
to 1800</term>
</item>
<item>
<term key="subject_sh85072984">Koran--Recitation</term>
</item>
</list>
</keywords>
</textClass>
</profileDesc>
</egXML>
<p>Keywords apply to the manuscript as a whole. You can associate each with one
or more specific works by enclosing the <gi>term</gi> in a <gi>ref</gi>
whose <att>target</att> attribute is a space-separated list of pointers to
the <att>xml:id</att> values of <gi>msItem</gi> elements, prefixed with
#.</p>
<p>Each <gi>term</gi> must have a key attribute containing the LoC authority
entry identifier prefixed with "subject_". The text within the <gi>term</gi>
element is also required, as this is what is displayed on the manuscript's
page on the web site. It can be a variant of LoC's preferred term, if you
think that more appropriate. If the term hasn't been used before, it will be
automatically added to the web site the next time it is re-indexed.</p>
</div>
<div xml:id="msdescription">
<head>Manuscript Description</head>
<p>The <gi>sourceDesc</gi> element contains a single child element, the
<gi>msDesc</gi>. Within that is all the information about the manuscript
as a physical object, its constituent parts, and intellectual works
represented within.</p>
<p>All manuscript descriptions must be informed by attention to codicological
units. In other words, whether the manuscript was created in one place, over
one period of time, or is a composite of parts from multiple sources,
assembled at a later date.</p>
<p>If the manuscript forms a single codicological unit, its intellectual
content, physical description, and history should be described directly
under the <gi>msDesc</gi> element. Individual works can vary in date or
hands while still being of a single source. In such cases, add <gi>note</gi>
elements to the <gi>msItem</gi> for each work, and an overview for the whole
manuscript in <gi>physDesc</gi>, <gi>history</gi>, etc. Do not simply enter
information (dates, dimensions, etc) as lists of <gi>ref</gi> elements.</p>
<p>If the manuscript comprises <ref target="#msPart">multiple codicological
units</ref>, each should be described in its own <gi>msPart</gi>
element, and only information common to the whole manuscript should be
described directly under the <gi>msDesc</gi> element. This will typically
include aspects of the physical description (e.g. extent, foliation,
binding), aspects of history (notably provenance and acquisition), but
possibly also some intellectual content (for example, if a table of contents
for the whole volume was added by a later owner, or if the manuscript has
replacement leaves). Conversely information relevant to each unit should be
described in separate <gi>msPart</gi> elements. </p>
<p> In each case the following elements are used: <!--<specList>
<specDesc key="msIdentifier"/>
<specDesc key="head"/>
<specDesc key="msContents"/>
<specDesc key="physDesc"/>
<specDesc key="history"/>
<specDesc key="additional"/>
</specList>-->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<msDesc>
<!-- Common information -->
<msPart>
<!-- Codicological unit 1 -->
</msPart>
<msPart>
<!-- Codicological unit 2 -->
</msPart>
</msDesc>
</egXML>
</p>
<div xml:id="msidentifier">
<head>The Manuscript Identifier</head>
<p>Information about the current location and shelfmark of the manuscript
should be given in the <gi>msIdentifier</gi> element using the following
elements in the following order: <gi>country</gi>, <gi>settlement</gi>,
<gi>institution</gi>, <gi>repository</gi>, and <gi>idno</gi> which
must have <att>type</att> with value <val>shelfmark</val>.</p>
<p>If the manuscript is well-known by a another name this should be recorded
in a <gi>msName</gi> element. Former shelfmarks may be given inside an
<gi>altIdentifier</gi> element in an <gi>idno</gi> element
(<att>type</att> attribute with value <val>former</val>). If the
manuscript has a reference number in another catalogue or reference
work, this should be given inside an <gi>altIdentifier</gi> element in
an <gi>idno</gi> element. The following values are currently used in the
medieval catalogue: <list>
<item><val>SCN</val> - Summary catalogue number</item>
<item><val>TM</val> - identifier in Trismegistos</item>
<item><val>PR</val> - papyrological reference</item>
<item><val>diktyon</val> - Dikyton number</item>
<!-- todo: others? -->
</list>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<msIdentifier>
<country>United Kingdom</country>
<region type="county">Oxfordshire</region>
<settlement>Oxford</settlement>
<institution>University of Oxford</institution>
<repository>Bodleian Library</repository>
<idno type="shelfmark">MS. Gr. class. b. 7 (P)</idno>
<altIdentifier type="internal">
<idno type="SCN">36946</idno>
</altIdentifier>
<altIdentifier type="external">
<idno type="PR">P. Oxy. VII 1032</idno>
</altIdentifier>
<altIdentifier type="external">
<idno type="PR">P. Oxy. VII 1049</idno>
</altIdentifier>
<altIdentifier type="external">
<idno type="TM">20328</idno>
</altIdentifier>
<altIdentifier type="external">
<idno type="TM">28329</idno>
</altIdentifier>
</msIdentifier>
</egXML>
<!-- <specList>
<specDesc key="msIdentifier"/>
<specDesc key="country"/>
<specDesc key="settlement"/>
<specDesc key="institution"/>
<specDesc key="repository"/>
<specDesc key="idno" atts="type"/>
<specDesc key="msName"/>
<specDesc key="altIdentifier"/>
</specList>-->
</p>
</div>
<div xml:id="heading">
<head>The Heading</head>
<p>For manuscripts described in detail, and/or containing more than one
item, the <gi>head</gi> element should provide (1) a brief descriptive
title (2) place of origin if known (3) date of origin. If the latter two
are unknown, use the <gi>summary</gi> element within <gi>msContents</gi>
instead. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<head>Ovid; England, 12th century</head>
</egXML>
<!-- <specList>
<specDesc key="head"/>
</specList>-->
</p>
</div>
<div xml:id="mscontents">
<head>Intellectual Content</head>
<p>The intellectual content of the manuscript or codicological unit should
be listed in the <gi>msContents</gi> element.
<!--<specList>
<specDesc key="summary"/>
<specDesc key="textLang"/>
<specDesc key="msItem"/>
</specList>-->
</p>
<div xml:id="summary">
<head>Summary (optional)</head>
<p>The <gi>summary</gi> element can be used to provide a brief prose
account of a manuscript's contents and significance, unless this has
already been covered by the <gi>head</gi>.</p>
</div>
<div xml:id="textlanguage">
<head>Language(s) of the manuscript as a whole (optional)</head>
<p>Give the text language for the codicological unit in the
<gi>textLang</gi>element , as a child of <gi>msContents</gi>,
immediately after <gi>summary</gi> (if used), with the
<att>mainLang</att> attribute. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<textLang mainLang="grc">Greek</textLang>
</egXML>
</p>
<p>For bilingual or multilingual units give the other languages in the
<att>otherLangs</att> attribute, as a space-separated list.
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<textLang mainLang="grc" otherLangs="la enm">Greek with some
Latin and Middle English</textLang>
</egXML>
</p>
<p>In some cases the decision of which language is ‘main’ and which
is/are ‘other’ may be rather arbitrary.</p>
<p>The attributes values used should conform to the BCP 47 standard
(<ref target="http://www.rfc-editor.org/rfc/bcp/bcp47.txt"
>http://www.rfc-editor.org/rfc/bcp/bcp47.txt</ref>) which start
with two-or-three-letter ISO 639 codes for languages, then an ISO
15924 code for the script, and finally IANA language subtags (<ref
target="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry"
>https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry</ref>)
for other information, such as methods of transliteration.</p>
<p>If the unit contains multiple works, in different languages or
scripts, the <gi>textLang</gi> element should be used in the
<gi>msItem</gi> instead, q.v.</p>
<p>According to the conventions of the catalogue, languages may be
encoded at a high or low level of granularity - for example, Middle
English may be encoded as "enm" or as "en", Anglo-Norman French may
be encoded as "fr" or "xno".</p>
<p>Current recommendations (July 2023) for cataloguers at Oxford and Cambridge are to encode languages to as granular a level as possible using the following codes:
<table>
<row>
<cell>Latin</cell><cell>la</cell>
</row>
<row>
<cell>Ancient Greek</cell><cell>grc</cell>
</row>
<row>
<cell>Modern Greek</cell><cell>el</cell>
</row>
<row>
<cell>Old English</cell><cell>ang</cell>
</row>
<row>
<cell>Middle English</cell><cell>enm</cell>
</row>
<row>
<cell>English (after c. 1500); do not encode "Early Modern English"</cell><cell>en</cell>
</row>
<row>
<cell>Old French</cell><cell>fro</cell>
</row>
<row>
<cell>Middle French</cell><cell>frm</cell>
</row>
<row>
<cell>Anglo-Norman</cell><cell>xno</cell>
</row>
<row>
<cell>French</cell><cell>fr</cell>
</row>
</table>
Guidance for other vernacular languages is under development.
</p>
<!-- todo: check! -->
</div>
<div xml:id="msitem">
<head>Manuscript Item</head>
<p>The <gi>msItem</gi> element may be used: <list>
<item>To describe an item of intellectual content (including
blank leaves if necessary)</item>
<item>To provide various notes about the manuscript's contents
(e.g. to compare items and their order with the contents of
other manuscripts, or to provide a note of content now
missing that was formerly present.)</item>
</list>
</p>
<!-- todo: expand on the following -->
<p>As a general rule, each distinct item in the manuscript should be
descibed in a distinct <gi>msItem</gi> tag.</p>
<p>The items should be numbered with the <att>n</att> attribute. (This
is particularly useful when the <gi>msItem</gi> element is nested,
say to describe sections within works, or works in collections of
works.) For retroconversion, follow the numbering system used in the
original catalogue. For new cataloguing, use arabic numbers, using a
decimal point when <gi>msItem</gi> is nested. For example, for the
second section of the first work: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<msItem n="1.2">
<!-- ... -->
</msItem>
</egXML>
<!--If the manuscript item is incomplete through loss or damage use the <att>defective</att> attribute with value <val>true</val> (default value is <val>false</val>).--></p>
<p>Just as the <att>n</att> attribute provides a way for readers to
reference and locate items, <att>xml:id</att> attributes do the same
for computers. So these ideally should be added too: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
<msItem n="1.2" xml:id="Add_1056-item1-item2">
<!-- ... -->
</msItem>
</egXML>
</p>
<p>Blank pages may be recorded as part of the item they follow, in a
separate <gi>note</gi> element.
<!--For new cataloguing, note whether or not a blank page has been
prepared for writing by pricking or ruling.-->
The <gi>locus</gi> element may be used to encode the folio(s).
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<note><locus from="187v" to="187v">Fol. 187v</locus>
blank.</note>
</egXML></p>
<p> More extensive streches of blank pages can be placed in a separate
<gi>msItem</gi>. <egXML xmlns="http://www.tei-c.org/ns/Examples">
<msItem>
<locus from="187v" to="189v">(fols. 187v-189v)</locus>
<note>Blank.</note></msItem>
</egXML>
</p>
<p>Pages containing short notes or scribbles by later hands should be
recorded in the <gi>additions</gi> element, see <ptr
target="#additions"/>.</p>
<div xml:id="whatIsMsItem">
<head>What is a manuscript item?</head>
<p>The Guidelines offer the following definitions: ‘each discrete
item in a manuscript’; ‘an individual work or item within the
intellectual content of a manuscript’. Often the identification
of these works or items does not pose difficulties, but many
more complex cases do occur.</p>
<p>A more helpful definition of a manuscript item may be ‘a complete
work or item, or a self-contained part of a larger work with
(potentially) independent circulation’. A ‘self-contained part
of a larger work’ could be a letter in a letter-collection, or a
sermon in a homiliary; it could also represent the biblical text
or the commentary in a glossed biblical manuscript.</p>
<p>As a guiding principle, where possible and practicable the
<gi>msItem</gi> element should be used to markup up the work
as a whole, and its self-contained parts, and the nesting of the
different <gi>msItem</gi> elements should express the
relationship between part and whole.</p>
<p>However, it is recognised that it may not be practical (for
example) to markup every letter in a letter-collection as an
<gi>msItem</gi>, and that the contents and order of a
collection may simply be recorded in a <gi>note</gi> element.
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<author key="person_95147024">Jerome</author>
<title key="work_2426">112 letters</title>
<note>
<title>Epist.</title> 57 (38), 73 (44), 129 (57), 35
(1), 36 (2; as 3 items, dividing in sects. 10-15), 62
(3), 19 (4), 20 (5), 15 (6), 16 (7), 18B (8), 18A (9),