This repository has been archived by the owner on Aug 30, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
/
teisimple.html
1009 lines (1002 loc) · 390 KB
/
teisimple.html
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
<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><!--THIS FILE IS GENERATED FROM AN XML MASTER. DO NOT EDIT (5)--><title>TEI Simple: An Introduction</title><meta name="author" content=""/><meta name="generator" content="Text Encoding Initiative Consortium XSLT stylesheets"/><meta charset="utf-8"/><link href="http://www.tei-c.org/release/xml/tei/stylesheet/tei.css" rel="stylesheet" type="text/css"/><link rel="stylesheet" media="print" type="text/css" href="http://www.tei-c.org/release/xml/tei/stylesheet/tei-print.css"/></head><body class="simple" id="TOP" itemscope="itemscope" itemtype="http://www.tei-c.org/ns/1.0/" itemprop="TEI"><!--TEI front--><div class="tei_front"><div class="titlePage"><div itemprop="docTitle" class="docTitle"><div itemprop="titlePart" class="titlePart">TEI Simple: An Introduction</div></div><div itemprop="docAuthor" class="docAuthor">Martin Mueller</div><div itemprop="docAuthor" class="docAuthor">Sebastian Rahtz</div><div itemprop="docAuthor" class="docAuthor">Brian Pytlik Zillig</div><div itemprop="docAuthor" class="docAuthor">James Cummings</div><div itemprop="docAuthor" class="docAuthor">Magdalena Turska</div><div itemprop="date" class="docDate">Version 0.9: August 2015</div></div></div><h2>Table of contents</h2><ul class="toc toc_body"><li class="toc"><span class="headingNumber">1. </span><a class="toc toc_0" href="#Simple-Background" title="Preface">Preface</a></li><li class="toc"><span class="headingNumber">2. </span><a class="toc toc_0" href="#Simple-very-gentle" title="A very gentle introduction to XML and TEI">A very gentle introduction to XML and TEI</a><ul class="toc"><li class="toc"><span class="headingNumber">2.1. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.1">Hierarchies and Metaphors in XML</a></li><li class="toc"><span class="headingNumber">2.2. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.2">Well-formed XML</a></li><li class="toc"><span class="headingNumber">2.3. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.3">Valid XML</a></li><li class="toc"><span class="headingNumber">2.4. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.4">XML as a declarative markup language</a></li><li class="toc"><span class="headingNumber">2.5. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.5">The Nature of XML rules</a></li><li class="toc"><span class="headingNumber">2.6. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.6">A simple example of the rules</a></li><li class="toc"><span class="headingNumber">2.7. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.7">About Namespaces</a></li><li class="toc"><span class="headingNumber">2.8. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.8">About Attributes</a></li><li class="toc"><span class="headingNumber">2.9. </span><a class="toc toc_1" href="#index.xml-body.1_div.2_div.9">Limitations of TEI as an XML Markup Language</a></li><li class="toc"><span class="headingNumber">2.10. </span><a class="toc toc_1" href="#tagabuse" title="Should Should Not and Tag Abuse">Should, Should Not, and Tag Abuse</a></li></ul></li><li class="toc"><span class="headingNumber">3. </span><a class="toc toc_0" href="#index.xml-body.1_div.3">A tour of TEI Simple from an encoding perspective</a><ul class="toc"><li class="toc"><span class="headingNumber">3.1. </span><a class="toc toc_1" href="#Simple-eg" title="A Short Example">A Short Example</a></li><li class="toc"><span class="headingNumber">3.2. </span><a class="toc toc_1" href="#Simple-struc" title="The Structure of a TEI Text">The Structure of a TEI Text</a></li><li class="toc"><span class="headingNumber">3.3. </span><a class="toc toc_1" href="#Simple-body" title="Encoding the Body">Encoding the Body</a><ul class="toc"><li class="toc"><span class="headingNumber">3.3.1. </span><a class="toc toc_2" href="#divs" title="Text Division Elements">Text Division Elements</a></li><li class="toc"><span class="headingNumber">3.3.2. </span><a class="toc toc_2" href="#h25" title="Headings and Closings">Headings and Closings</a></li><li class="toc"><span class="headingNumber">3.3.3. </span><a class="toc toc_2" href="#vedr" title="Prose Verse and Drama">Prose, Verse and Drama</a></li></ul></li><li class="toc"><span class="headingNumber">3.4. </span><a class="toc toc_1" href="#Simple-pln" title="Page and Line Numbers">Page and Line Numbers</a></li><li class="toc"><span class="headingNumber">3.5. </span><a class="toc toc_1" href="#Simple-hilites" title="Marking Highlighted Phrases">Marking Highlighted Phrases</a><ul class="toc"><li class="toc"><span class="headingNumber">3.5.1. </span><a class="toc toc_2" href="#faces" title="Changes of Typeface etc.">Changes of Typeface, etc.</a></li><li class="toc"><span class="headingNumber">3.5.2. </span><a class="toc toc_2" href="#z635" title="Quotations and Related Features">Quotations and Related Features</a></li><li class="toc"><span class="headingNumber">3.5.3. </span><a class="toc toc_2" href="#z636" title="Foreign Words or Expressions">Foreign Words or Expressions</a></li></ul></li><li class="toc"><span class="headingNumber">3.6. </span><a class="toc toc_1" href="#Simple-notes" title="Notes">Notes</a></li><li class="toc"><span class="headingNumber">3.7. </span><a class="toc toc_1" href="#Simple-ptrs" title="Cross References and Links">Cross References and Links</a><ul class="toc"><li class="toc"><span class="headingNumber">3.7.1. </span><a class="toc toc_2" href="#ptrs" title="Simple Cross References">Simple Cross References</a></li><li class="toc"><span class="headingNumber">3.7.2. </span><a class="toc toc_2" href="#xptrs" title="Pointing to other documents">Pointing to other documents</a></li><li class="toc"><span class="headingNumber">3.7.3. </span><a class="toc toc_2" href="#xatts" title="Special kinds of Linking">Special kinds of Linking</a></li><li class="toc"><span class="headingNumber">3.7.4. </span><a class="toc toc_2" href="#abseg" title="ab and seg as basic block and inline elements">ab and seg as basic block and inline elements</a></li></ul></li><li class="toc"><span class="headingNumber">3.8. </span><a class="toc toc_1" href="#Simple-edit1" title="Editorial Interventions">Editorial Interventions</a><ul class="toc"><li class="toc"><span class="headingNumber">3.8.1. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.8_div.1">Correction and Normalization</a></li><li class="toc"><span class="headingNumber">3.8.2. </span><a class="toc toc_2" href="#Simple-edit2" title="Omissions Deletions and Additions">Omissions, Deletions, and Additions</a></li><li class="toc"><span class="headingNumber">3.8.3. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.8_div.3">Abbreviations and their Expansion</a></li></ul></li><li class="toc"><span class="headingNumber">3.9. </span><a class="toc toc_1" href="#Simple-names" title="Names Dates and Numbers">Names, Dates, and Numbers</a><ul class="toc"><li class="toc"><span class="headingNumber">3.9.1. </span><a class="toc toc_2" href="#nomen" title="Names and Referring Strings">Names and Referring Strings</a></li><li class="toc"><span class="headingNumber">3.9.2. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.9_div.2">Dates and Times</a></li><li class="toc"><span class="headingNumber">3.9.3. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.9_div.3">Numbers </a></li></ul></li><li class="toc"><span class="headingNumber">3.10. </span><a class="toc toc_1" href="#Simple-lists" title="Lists">Lists</a></li><li class="toc"><span class="headingNumber">3.11. </span><a class="toc toc_1" href="#Simple-bibls" title="Bibliographic Citations">Bibliographic Citations</a></li><li class="toc"><span class="headingNumber">3.12. </span><a class="toc toc_1" href="#Simple-tables" title="Tables">Tables</a></li><li class="toc"><span class="headingNumber">3.13. </span><a class="toc toc_1" href="#Simple-figs" title="Figures and Graphics">Figures and Graphics</a></li><li class="toc"><span class="headingNumber">3.14. </span><a class="toc toc_1" href="#Simple-anal" title="Analysis">Analysis</a><ul class="toc"><li class="toc"><span class="headingNumber">3.14.1. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.14_div.1">Orthographic Sentences</a></li><li class="toc"><span class="headingNumber">3.14.2. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.14_div.2">Words and punctuation</a></li><li class="toc"><span class="headingNumber">3.14.3. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.14_div.3">General-Purpose Interpretation Elements</a></li></ul></li><li class="toc"><span class="headingNumber">3.15. </span><a class="toc toc_1" href="#Simple-composite" title="">15</a></li><li class="toc"><span class="headingNumber">3.16. </span><a class="toc toc_1" href="#Simple-fronbac" title="Front and Back Matter">Front and Back Matter</a><ul class="toc"><li class="toc"><span class="headingNumber">3.16.1. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.16_div.1">Front Matter</a><ul class="toc"><li class="toc"><span class="headingNumber">3.16.1.1. </span><a class="toc toc_3" href="#h51" title="Title Page">Title Page</a></li><li class="toc"><span class="headingNumber">3.16.1.2. </span><a class="toc toc_3" href="#h52" title="Prefatory Matter">Prefatory Matter</a></li></ul></li><li class="toc"><span class="headingNumber">3.16.2. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.16_div.2">Back Matter</a><ul class="toc"><li class="toc"><span class="headingNumber">3.16.2.1. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.16_div.2_div.1">Structural Divisions of Back Matter</a></li></ul></li></ul></li><li class="toc"><span class="headingNumber">3.17. </span><a class="toc toc_1" href="#Simple-header" title="The Electronic Title Page">The Electronic Title Page</a><ul class="toc"><li class="toc"><span class="headingNumber">3.17.1. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.17_div.1">The File Description</a><ul class="toc"><li class="toc"><span class="headingNumber">3.17.1.1. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.1">The Title Statement</a></li><li class="toc"><span class="headingNumber">3.17.1.2. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.2">The Edition Statement</a></li><li class="toc"><span class="headingNumber">3.17.1.3. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.3">The Extent Statement</a></li><li class="toc"><span class="headingNumber">3.17.1.4. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.4">The Publication Statement</a></li><li class="toc"><span class="headingNumber">3.17.1.5. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.5">Series and Notes Statements</a></li><li class="toc"><span class="headingNumber">3.17.1.6. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.1_div.6">The Source Description</a></li></ul></li><li class="toc"><span class="headingNumber">3.17.2. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.17_div.2">The Encoding Description</a><ul class="toc"><li class="toc"><span class="headingNumber">3.17.2.1. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.2_div.1">Project and Sampling Descriptions</a></li><li class="toc"><span class="headingNumber">3.17.2.2. </span><a class="toc toc_3" href="#index.xml-body.1_div.3_div.17_div.2_div.2">Editorial Declarations</a></li><li class="toc"><span class="headingNumber">3.17.2.3. </span><a class="toc toc_3" href="#refsdecl" title="Reference and Classification Declarations">Reference and Classification Declarations</a></li></ul></li><li class="toc"><span class="headingNumber">3.17.3. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.17_div.3">The Profile Description</a></li><li class="toc"><span class="headingNumber">3.17.4. </span><a class="toc toc_2" href="#index.xml-body.1_div.3_div.17_div.4">The Revision Description</a></li></ul></li></ul></li><li class="toc"><span class="headingNumber">4. </span><a class="toc toc_0" href="#processingmodel" title="A Short Tour of the Processing Model">A Short Tour of the Processing Model</a><ul class="toc"><li class="toc"><span class="headingNumber">4.1. </span><a class="toc toc_1" href="#index.xml-body.1_div.4_div.1">The <model> element with some of its attributes and children</a></li><li class="toc"><span class="headingNumber">4.2. </span><a class="toc toc_1" href="#index.xml-body.1_div.4_div.2">More about Behaviours</a></li><li class="toc"><span class="headingNumber">4.3. </span><a class="toc toc_1" href="#customization" title="Customizing the Processing Model">Customizing the Processing Model</a></li></ul></li><li class="toc"><span class="headingNumber">6. </span><a class="toc toc_0" href="#index.xml-body.1_div.6">The TEI Simple schema</a><ul class="toc"><li class="toc"><span class="headingNumber">6.1. </span><a lang="" class="toc toc_1" href="#index.xml-body.1_div.6_div.1">Summary</a></li><li class="toc"><span class="headingNumber">6.2. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.2">The TEI infrastructure</a></li><li class="toc"><span class="headingNumber">6.3. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.3">The header</a></li><li class="toc"><span class="headingNumber">6.4. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.4">Transcription</a></li><li class="toc"><span class="headingNumber">6.5. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.5">Attribute classes</a></li><li class="toc"><span class="headingNumber">6.6. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.6">Model classes</a></li><li class="toc"><span class="headingNumber">6.7. </span><a class="toc toc_1" href="#index.xml-body.1_div.6_div.7">Elements</a></li></ul></li></ul><!--TEI body--><div class="tei_body"><section class="teidiv0" id="Simple-Background"><header><h1><span class="headingNumber">1. </span><span class="head" itemprop="head">Preface</span></h1></header><p>The Text Encoding Initiative (TEI) has developed over 20 years into a key technology in text-centric humanities disciplines, with an extremely wide range of applications, from diplomatic editions to dictionaries, from prosopography to speech transcription and linguistic analysis. It has been able to achieve its range of use by adopting a <span class="term" itemprop="term">descriptive</span> rather than <span style="font-style:italic" itemprop="hi">prescriptive </span> approach , by recommending <span class="term" itemprop="term">customization</span> to suit particular projects, and by eschewing any attempt to dictate how the digital texts should be rendered or exchanged. However, this flexibility has come at the cost of relatively limited success in interoperability. In our view there is a distinct set of uses (primarily in the area of digitized ‘European’-style books) that would benefit from a <span style="font-style:italic" itemprop="hi">prescriptive</span> recipe for digital text; this will sit alongside other domain-specific, constrained TEI customizations, such as the very successful <span class="term" itemprop="term">Epidoc</span> in the epigraphic community. TEI Simple may become a prototype for a new family of constrained customizations. For instance, a TEI Simple MS for manuscript based work could be built on top of the ENRICH project, drawing on many of the lessons and some of the code for TEI Simple.</p><p>The TEI has long maintained an introductory subset (TEI Lite), and a constrained customization for use in outsourcing production to commercial vendors (TEI Tite), but both of these permit enormous variation, and have nothing to say about processing. The TEI Simple project can be viewed in some ways as a revision of TEI Lite. Leaving aside elements for the <span class="gi"><teiHeader></span>, TEI Lite and TEI Simple are customization of approximately the same scope, choosing respectively 91 and 105 out of the 552 TEI elements and sharing 80 of them. TEI Simple targets the area of <span class="term" itemprop="term">Letters</span> in the broad and old-fashioned sense of that term. Its choice of elements reflects the practices followed in the encoding of large-scale archives, notably the archives produced by the Text Creation Partnership, but also the German Text Archive and a variety of archives encoded according to Level 4 of the Best Practices for TEI in Libraries. It is simple only with regard to its <span class="gi"><text></span> element. The <span class="gi"><teiHeader></span> follows the same rules as TEI-All.</p><p>TEI Simple focuses on interoperability, machine generation, and low-cost integration. In earlier discussions this project was called "TEI Nudge" because it was offered in the spirit of Richard Thaler's and Cass Sunstein's <span class="titlem">Nudge</span> with its persuasive argument that in many walks of life people will make better choices if they are offered well-designed default solutions, as long as they are free to opt out of them. The TEI architecture facilitates customizations of many kinds; TEI Simple aims to produce a complete <span class="q" itemprop="q">‘out of the box’</span> customization which meets the needs of the many users for whom the task of creating a customization is daunting or seems irrelevant. TEI Simple in no way intends to constrain the expressive liberty of encoders who do not think that it is either possible or desirable to follow this path. It does, however, promise to make life easier for those who think there is some virtue in travelling that path as far as it will take you, which for quite a few projects will be far enough. Some users will never feel the need to move beyond it, others will outgrow it, and when they do they will have learned enough to do so.</p><p>The most distinctive feature of TEI Simple is a <span class="q" itemprop="q">‘cradle to grave’</span> processing model that associates the TEI Simple schema with explicit and standardized options for displaying and querying texts. This means being able to specify what a programmer should do with particular TEI elements when they are encountered, allowing programmers to build stylesheets that work for everybody and to query a corpus of documents reliably.</p><p>The modal case of a TEI project is a scholarly edition of some text that originated in a print or manuscript world. The edition may start from the fresh transcription of a source or it may start from the existing encoding of a text, e.g. a text from the EEBO TCP archive. Such projects call on a combination of skills that are not often found in the same person. The scholars care about the accuracy of the transcription and relevance of the encoding to their purpose and that of other users. If you have editorial responsibility for a TEI encoded text, you must know enough about TEI elements and practices to do this well. You need not know much about or be interested in the often very complex procedures required to turn the encoded text into something that users can work with. On the other hand the programmers and designers are very familiar with those procedures, but they may not have the time or inclination to become familiar with the intricacies of TEI encoding. </p><p>The processing model offers a bridge across that divide. The aim is to lower the access barriers to working with TEI-encoded texts in various web environments. Programmers familiar with a particular web environment, whether Django, Drupal, eXist, Ruby on Rails, or others will be able to integrate TEI Simple-based projects into their environment with moderate effort and with no more than their usual tools and skills. Scholars or other individuals who primarily care about getting the encoding right need not concern themselves with subsequent stages. If they can do their encoding within the limits of TEI Simple, they can be confident that the fruits of their en-coding are available to users. Users, in turn, can have greater confidence that the query poten-tial of encoded texts is in fact made available to them through appropriate query routines. This is conspicuously not the case with most TEI-encoded texts now: it is very difficult to write or train a search engine if you cannot make reasonably stable assumptions about the structure of the documents to be queried. </p><p>This introduction to TEI Simple consists of three parts. They address different audiences and make different assumptions about what the reader is likely to know. The first of these addresses readers who know little or nothing about XML and can safely be skipped by readers who are familiar with it. The second is a tour of the elements in TEI Simple from an encoder's perspective. This section is a revision of the excellent introduction to TEI Lite by Lou Burnard and Michael Sperberg-McQueen. It follows that document wherever it can while adding this or deleting that. The third part is a short tour of the Processing Model and is written for programmers who are familiar with Web technologies but new to TEI.</p></section><section class="teidiv0" id="Simple-very-gentle"><header><h1><span class="headingNumber">2. </span><span class="head" itemprop="head">A very gentle introduction to XML and TEI</span></h1></header><div class="teidiv1" id="index.xml-body.1_div.2_div.1"><h2><span class="headingNumber">2.1. </span><span class="head" itemprop="head">Hierarchies and Metaphors in XML</span></h2><p>The best full-scale introduction to the technologies that undergird TEI is found in Lou Buranrd's <a class="link_ref" itemprop="ref" href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SG.html">"Gentle Introduction to XML</a> in Chapter 5 of the <span class="titlem">TEI:P5 Guidelines</span>. " If you come from a History, Literature, or Philosophy department and have never worked with XML you may not find it quite so gentle, especially in its later chapters. This chapter addresses you and tries to lay out some basic facts about XML and TEI in language that stays as close to layman's language as possible. Examples are chosen from TEI Simple, but their point is to demonstrate general aspects of XML. Consult the "Tour of TEI Simple" for a detailed discussion of elements and their rules. The is some overlap in the discussions. If you are a novice, the repetition may be helpful. If you are an expert, you want to skip this section altogether.</p><p>A word of advice before proceeding any further. It is possible to use simple text editing software to work with XML, but if you value your time do not even think about doing it. Use an XML editor instead. An XML editor is a piece of software that "knows about" the general features of XML and the particular features of a distinct XML language such as TEI. It can save you countless hours by discovering (or even preventing) the many logical and typographical errors that are easy to make and hard to fix. Some XML editors are freeware. The software that will save you the most time is likely not to be free. There are several excellent XML editors. In the TEI world, oXygen is probably the most widely used. </p><p>XML stands for Extensible Markup Language. It is a set of rules for creating hierarchical data structures or Ordered Hierarchies of Content Objects (OHCO). You are familiar with such structures from the hard drive of your computer. It is a single container or "root" directory, which you can subdivide into an arbitrary number of subdirectories, each of which is "recursively" divisible into arbitrarily many subdirectories. Within the limits of the size of your hard drive each container is infinitely variable in size and adjusts to stuff that that you add or subtract.</p><p>The technical terms of XML make extensive use of <span class="term" itemprop="term">tree</span> and <span class="term" itemprop="term">family</span> metaphors. In XML parlance the root of a tree is envisaged as a single cell. In visualizations the tree is typically inverted so that the tree grows downwards from a root in the sky. Each branching of such a tree is called a <span class="term" itemprop="term">node</span>, and a node with no further branches is often called a <span class="term" itemprop="term">leaf node</span>. A good XML editor lets you present the outline or tree structure of your document in the form of a navigation panel.</p><p>As for the family metaphor, there is no sex in XML, and reproduction proceeds by parthenogenesis. A <span class="term" itemprop="term">parent</span> may have an indefinite number of <span class="term" itemprop="term">child</span> elements, but a <span class="term" itemprop="term">child</span> element has only one parent. It may have many <span class="term" itemprop="term">ancestors</span>, but at any level of the hierarchy there is only one of them. It is a defining feature of such hierarchical structures that for any <span class="term" itemprop="term">node</span> there is one and only <span class="term" itemprop="term">path</span> from the root to any node, or from any node to any other node. In XML the technical term for that path is XPath, which is both a name for such a path and a quite complicated computer language for getting from any "here" to any "there".</p><p>On your hard drive a container is known as a directory or folder. In an XML document, containers are known as <span class="term" itemprop="term">elements</span>. Container suggests volume and a three-dimensional structure, but the content of elements is text, which unfolds in a single temporal direction, envisaged from left to right in many, but by no means all, languages.</p><div class="p">The resemblances between your hard drive and an XML document in it are closer than you may think. XQuery is the name of a computer language that handles XML documents. In that language <pre class="pre_eg cdata">declare variable $collection := collection('/Users/martin/dropbox/speechdirectory');</pre> is a way of saying <div class="blockquote block" itemprop="q">Follow the Xpath that starts from the top container and follow it through its branchings (expressed by the <span class="term" itemprop="term">solidus</span> or forward slash) until you come to the container called "speechdirectory." Call it "collection" and identify it as an object on which further operations can be performed.</div> The dollar sign identifies a <span class="term" itemprop="term">variable</span> and its name. "speechdirectory" happens to be a directory on my computer with TEI documents that have a lot of speeches in them. Now consider the following piece of code: <pre class="pre_eg cdata">for $title in $collection//filesDesc/titleStmt/title return $title</pre> This is a <span class="term" itemprop="term">for statement</span> used in many computer languages. It loops through a set of files, in this case all the files defined as the variable $collection. For each of these files it follows any path that leads via the elements <span class="gi"><fileDesc></span> and <span class="gi"><titleStmt></span> to the element <span class="gi"><title></span>. It gives to that element the variable name $title and <span class="term" itemprop="term">returns</span>, i.e. produces as the result of its operation, the variable $title. The result is a long list with entries like the following. <div id="index.xml-egXML-d33e210" class="pre egXML_valid"><span class="element"><title></span>A dialogue between Sir R.L. Knight, and T.O.D<span class="element"></title></span>
<span class="element"><title></span>A new dialogue between some body and no body, or, The Observator observed<span class="element"></title></span></div> The XQuery chained together the hard drive's filepath and all the XPaths in the $collection variable that lead to <span class="gi"><title></span> children of <span class="gi"><titleStmt></span> elements. You might say that the root element of the XML document becomes a child element of your drive.</div><p>Why is the piece of code frame with a black border while its output is displayed in green field and with a green border? Anything that appears in green is a valid TEI XML fragment if it appears in the right context. Code framed in black makes no such claim.</p><p>As this example demonstrates, it takes a fair amount of prose to describe a very simple operation. Just about any individual operation with XML is quite simple, but there are a lot of them and they nest. Some of the most distinctive features and difficulties of XML are highlighted if you envisage the hierarchical structure as as one-dimensional stream. Imagine an XML document as a pair of parentheses with parentheses and nested parentheses within it. Nesting is a simple concept, but it is not easy for human minds or eyes to follow a nested structure beyond the third level. An interesting technical term in this regard is <span class="term" itemprop="term">serialize</span>. You don't need to know (I certainly don't) just how the data of an XML document are stored in the innards of a computer. But when they are produced by the machine for you in a manner that you can make sense of they are <span class="term" itemprop="term">serialized</span>. This serialization appears typically on the two dimensional space of a page, where the single text stream is broken into familiar lines. The typographical line has been a remarkably stable structure for millennia, with limits imposed by the capacities of the human eye. But it is helpful to remember that a line is a convenient construct of a longer discursive linear stream.</p><p>The parentheses that mark the boundaries of XML elements are more complicated things than round, square, or curly brackets. They are constructs enclosed in angle brackets, are known as <span class="term" itemprop="term">tags</span>, and have names. The opening tag of an element with the name "someElement" looks like <code itemprop="code"><someElement></code>, while the closing tag adds a <span class="term" itemprop="term">solidus</span> after the left angle brackets:<code itemprop="code"></someElement></code>. As with a directory on your computer, you can put as much stuff between those tags as your hard drive will hold. The following is a <span class="term" itemprop="term">well-formed</span> XML document</p><pre class="pre_eg cdata"><someELement>Mary had a little lamb</someELement></pre><p>But so is </p><pre class="pre_eg cdata"><someELement> In the beginning God created the heaven and the earth....The grace of our Lord Jesus Christ be with you all. Amen.</someELement></pre><p> with all the other words of the Bible in between.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.2"><h2><span class="headingNumber">2.2. </span><span class="head" itemprop="head">Well-formed XML</span></h2><p>The term <span class="term" itemprop="term">well-formed</span> has a very specific meaning in XML. An XML text must be <span class="term" itemprop="term">well-formed</span>, and it may be <span class="term" itemprop="term">valid</span>. For an XML document to be well-formed it only needs to meet the conditions that must be true of all XML documents. There are not many of them, but the two most important are that a) the document must be enclosed by a root element, and b) that the name of an element must be spelled exactly the same way in the opening and closing tag. Thus </p><pre class="pre_eg cdata"><someElement>Mary had a little lamb</someelement></pre><p>is not a well-formed XML document, because XML is <span class="term" itemprop="term">case-sensitive</span> and the spelling of the closing tag "someelement" does not match the spelling of the opening tag "someElement." Neither is </p><pre class="pre_eg"><line>Mary had a little lamb</line> <br itemprop="lb"/><line>Its fleece was white as snow</line></pre><p> But </p><pre class="pre_eg"><linegroup> <br itemprop="lb"/><line>Mary had a little lamb</line> <br itemprop="lb"/><line>Its fleece was white as snow</line> <br itemprop="lb"/></linegroup></pre><p> is well-formed XML because the two <line> elements are enclosed by the root element <linegroup> and the opening and closing tag names are spelled the same way.</p><p>These simple examples of well-formed XML consist of element wrappers that enclose text. From a reader's perspective XML has slightly awkward ways of referring to <span class="q" itemprop="q">‘just text’</span>. The software that processes an XML text is known as a <span class="term" itemprop="term">parser</span>, a term borrowed from traditional grammar. Just as you parse a sentence by determining where its different parts begin and end, so an XML parser goes through an XML file and inspects its parts. It looks for opening and closing tags of each element as well as the stuff enclosed by them, which consists either of other elements or of PCDATA or <span class="term" itemprop="term">parsed character data</span>, stuff that the XML Parser after examination has recognized as proper text.</p><p>Except for the left angle bracket (<) and the ampersand (&) any Unicode character can show up in PCDATA. Because the XML parser uses (<) to identify the beginning of an element tag, it cannot be used directly in plain text or PCDATA. Instead you use a <span class="term" itemprop="term">character entity</span> to represent them. A character entity is a periphrastic expression that is wrapped in an opening ampersand and a closing semicolon. Since there are no words that begin with the former and end with the latter they act as an unambiguous marker that their content refers to and retrieves something special, whether a single character or all of <span class="titlem">Hamlet</span>. The character entity for the left angle bracket is (&lt;), where <span class="q" itemprop="q">‘lt’</span> stands for <span class="q" itemprop="q">‘less than’</span> to reflect the common use of that character in mathematical notation.</p><p>Because the ampersand is used as the opening symbol for a character entity, it also must be <span class="term" itemprop="term">escaped</span> and cannot be used directly. Its character entity is "ampersand + amp + semicolon" (&amp;). These character entities are two of five <span class="term" itemprop="term">predefined entities</span> in the XML specifications that you can use without formally <span class="term" itemprop="term">declaring</span> them. The other three are the apostrophe ('), the double quotation mark ("), and the "greater-than" symbol or right angle bracket (>). Of these, the apostrophe entity is useful if you want to distinguish between the uses of the same character as the genitive marker and a single quotation mark.</p><p>Within the range of TEI Simple you probably will not need to know any more about character entities, but you can find out more about them at <a class="link_ref" itemprop="ref" href="http://www.w3.org/TR/xml-entity-names">XML Entity Definitions for Characters (2nd Edition)</a>.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.3"><h2><span class="headingNumber">2.3. </span><span class="head" itemprop="head">Valid XML</span></h2><p>The requirement that everything in a well-formed XML document must be enclosed by a root element does not take you very far. A well-formed directory structure on a hard drive can be, and often is, a complete mess. XML becomes interesting and useful only when it is <span class="term" itemprop="term">valid</span>. XML has rules for making rules that specify for any element </p><ul itemprop="list"><li class="item" itemprop="item">what elements it may or must contain or be contained by</li><li class="item" itemprop="item">how often it may appear in its parent elemtn</li><li class="item" itemprop="item">in what order it may or must appear</li></ul><p> A set of such rules is known as a <span class="term" itemprop="term">schema</span>. You can use these rules about rules to make up your own schema, but if you want to share your documents and make sure that others can use them you are better off using a schema that has been designed by others for general use in some domain, whether Chemistry, Mathematics, or whatever. TEI is such a schema, and its purpose is to facilitate the encoding of documents that fall under the category of <span class="term" itemprop="term">Letters</span> very broadly defined.</p><p>How does a machine know that a document is an XML document,whether with or without a schema? Any XML document must begin with one or more <span class="term" itemprop="term">processing instructions</span> that tell the machine what to do with it. The minimal processing instruction simply says <span class="q" itemprop="q">‘I am an XML document’</span> and does so with the line </p><pre class="pre_eg cdata"><?xml version="1.0" encoding="UTF-8"?></pre><p> at the top of the file. The statement <span class="q" itemprop="q">‘I am a TEI Simple document’</span> is a more elaborate affair:</p><pre class="pre_eg"><?xml-model href="http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> <br itemprop="lb"/><?xml-model href="http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?></pre><p>You can encode quite successfully in TEI Simple by just cutting and pasting this code. If you work with a program like oXygen, you can choose a new document as a TEI Simple document, and it will open with all the required processing instructions. It is, however, useful to hava rough idea of what is going on here. A processing instruction comes in a <? ...?> wrapper, which answers to the machine's question <span class="q" itemprop="q">‘What shall I do here?’</span> In our example there are two instructions. The first one says </p><div class="blockquote block" itemprop="q">Follow the instructions in the schema <span class="term" itemprop="term">teisimple.rng</span>. which you will find at the URL "http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng".</div><p> The second instruction, which is rather more cryptic, specifies that the rules for the <span class="gi"><teiHeader></span> element differ from the rules for the <span class="gi"><text></span> element.</p><p>A schema is a very technical document and can be expressed in various schema languages. In the TEI world Relax NG is the most popular schema language. You can mostly treat the TEI Simple schema (or any other schema) as a black box whose operations you trust. Until about a dozen years, working with XML texts was a painful exercise. XML texts are equally unforgiving when it comes to orthographic or logical errors. Both are very easy to make and very hard to find or fix in a document of any complexity. Modern editing software wil <span class="term" itemprop="term">validate</span> your document as you work on it. That is to say, it will read your document and check whether it complies with the rules declared in the schema. If it discovers an error, it will tell you about the what and where of that error right then and there. It is a good investment of your time to learn how to read such error messages.</p><p>Although working with XML is much less painful than it used to, you still have to understand the particular rules that are formulated in the arcane language of the schema. You also need to know something about the rule-making rules of XML in order to work with TEI documents. And it helps to remind yourself constantly of some basic facts about XML. An XML document is in principle human-readable. If the only surviving copies of Dante's <span class="titlem">Inferno</span>, Cervantes' <span class="titlem">Don Quixote</span>, or Shakespeare's <span class="titlem">Hamlet</span> were XML versions they could be read by humans who know Italian, Spanish, or English. But an XML document is not made to be read by a human. It is made to be processed by a machine for some purpose, whether displaying it on a screen, printing it out in some formating, or retrieving bits of information from it. An XML document is to a considerable extent agnostic about the purposes to which it may be put. It is not a single purpose version of its source. In particular, it is not designed as a reader-friendly document, although you may generate a reader-friendly version from it.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.4"><h2><span class="headingNumber">2.4. </span><span class="head" itemprop="head">XML as a declarative markup language</span></h2><div class="p">Like any other XML language, TEI is a <span class="term" itemprop="term">declarative markup language</span>. If in a printed book you come across the sentence <span class="q" itemprop="q">‘<span class="hi" itemprop="hi">Julius Caesar </span>was assassinated on March 15, 44 BCE’</span> and you see the string "Julius Caesar" in italics you may reasonably infer that the type setting program followed an "imperative" procedure that said something like <span class="q" itemprop="q">‘when you come to J start printing in italics and stop when you've done 'r'’</span>. Word processors work that way. In TEI that sentence might be encoded as <div id="index.xml-egXML-d33e424" class="pre egXML_valid"><span class="element"><s></span>
<span class="element"><name></span>Julius Caesar<span class="element"></name></span> was assassinated on <span class="element"><date></span>March 15, 44 BCE<span class="element"></date></span>
<span class="element"></s></span></div> This encoding has no imperatives, but is a sequence of declarations where <ul itemprop="list"><li class="item" itemprop="item">the <span class="gi"><s></span> element declares that "my content is a sentence"</li><li class="item" itemprop="item">the <span class="gi"><name></span> element declares that "my content is a name"</li><li class="item" itemprop="item">the<span class="gi"><date></span> element declares that "my content is a date"</li></ul></div><div class="p">These declarations include no instructions about what to do with them. They do allow a machine to retrieve the content of all elements that have the tags <span class="gi"><name></span>, <span class="gi"><date></span> or <span class="gi"><s></span>. If the sentence came from an Early Modern document in which names are frequently italicized, the encoding might go like <div id="index.xml-egXML-d33e460" class="pre egXML_valid"><span class="element"><s></span>
<span class="element"><name <span class="attribute">rendition</span>="<span class="attributevalue">#italics</span>"></span>Julius Caesar<span class="element"></name></span> was assassinated on <span class="element"><date></span>March 15, 44 BCE<span class="element"></date></span>
<span class="element"></s></span></div> The <span class="term" itemprop="term">attribute</span> <span xmlns="" class="att" itemprop="att">rendition</span> in this case declares that in the source document the name was italicized, but the encoding does not tell you what to do with that fact. What is true of this sentence is true of every TEI text. It is a set of declarations rather than a set of instructions.</div></div><div class="teidiv1" id="index.xml-body.1_div.2_div.5"><h2><span class="headingNumber">2.5. </span><span class="head" itemprop="head">The Nature of XML rules</span></h2><p>TEI is a specific markup language designed to encode texts that originated in a print or manuscript world. You can also use it to generate <span class="term" itemprop="term">born digital</span> documents, but you will understand its quirks more readily if you keep its original purpose in mind. The XML rules for specifying the TEI markup language have to do with </p><ul itemprop="list"><li class="item" itemprop="item">what elements may contain or are contained by other elements</li><li class="item" itemprop="item">the order of child elements within a particular parent element</li><li class="item" itemprop="item">the number of child elements that a parent element may contain</li></ul><p> The words <span class="term" itemprop="term">may</span>, <span class="term" itemprop="term">must</span> and <span class="term" itemprop="term">may not </span>are important technical terms that the machine can understand when it validates an encoding. There is also the ocasional <span class="term" itemprop="term">should</span>, but <span class="term" itemprop="term">should</span> is not a term the machine can make sense of. It involves conventions that it is helpful to observe, even though for one reason or another they cannot be expressed in terms of <span class="term" itemprop="term">may</span>, <span class="term" itemprop="term">must</span> or <span class="term" itemprop="term">may not</span>.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.6"><h2><span class="headingNumber">2.6. </span><span class="head" itemprop="head">A simple example of the rules</span></h2><p>The skeleton of a TEI document provides a good example for the ways in which the rule-making capabilities of XML are exercised. A TEI document MUST have one and only one root element, and it name is TEI. The element name TEI is a specific feature of the TEI schema. The requirement for a root element is a requirement of well-formed XML. </p><p>The TEI root element MUST have two child elements, <span class="gi"><teiHeader></span> and <span class="gi"><text></span>. There MUST be only one of each, and <span class="gi"><teiHeader></span> MUST come before <span class="gi"><text></span>. These are TEI specific rules, but they observe the rule-making rules of XML.</p><p><span class="gi"><teiHeader></span> and <span class="gi"><text></span> relate to each other as a catalogue record to the item it catalogues. <span class="gi"><teiHeader></span> consists of data about <span class="gi"><text></span> or <span class="term" itemprop="term">metadata</span>.</p><p>Encoding the header is a very different thing from encoding the text, and information from the header is never included in a representation of the text. We will leave the header alone, except for noting briefly what MUST be in it. Here is an example of a minimal header:</p><div id="index.xml-egXML-d33e553" class="pre egXML_valid"><span class="element"><teiHeader></span>
<span class="element"><fileDesc></span>
<span class="element"><titleStmt></span>
<span class="element"><title></span>My next book<span class="element"></title></span>
<span class="element"></titleStmt></span>
<span class="element"><publicationStmt></span>
<span class="element"><p></span>not yet published<span class="element"></p></span>
<span class="element"></publicationStmt></span>
<span class="element"><sourceDesc></span>
<span class="element"><p></span>original document<span class="element"></p></span>
<span class="element"></sourceDesc></span>
<span class="element"></fileDesc></span>
<span class="element"></teiHeader></span></div><p>The header MUST have a <span class="gi"><fileDesc></span> element or file description, which answers at least the following three questions: </p><ul itemprop="list"><li class="item" itemprop="item">What is my name? (<span class="gi"><titleStmt></span>)</li><li class="item" itemprop="item">Who published me? (<span class="gi"><pubStmt></span>)</li><li class="item" itemprop="item">Where do I come from? (<span class="gi"><sourceDesc></span>)</li></ul><p> The <span class="gi"><fileDesc></span> element MAY have a lot of other child elements, but it MUST have <span class="gi"><titleStmt></span>, <span class="gi"><pubStmt></span>, <span class="gi"><sourceDesc></span>, only one of each and in that order. This is a very simple example of XML rules codifying practices from some domain, here the world of published books. The normal case of a TEI document represents a file that has been digitized and published from a printed source. But this hypothetical example represents a digital file that has not been published and was <span class="term" itemprop="term">born digital</span>.</p><p>In this simple example, <span class="gi"><titleStmt></span>,<span class="gi"><pubStmt></span>,and <span class="gi"><sourceDesc></span> do not have text content, but their child elements <span class="gi"><p></span> and <span class="gi"><title></span> do. Some elements can only contain other elements, some elements can contain <span class="term" itemprop="term">mixed content</span>, i.e. <span class="term" itemprop="term">text nodes</span> and child elements. Some elements typically contain only text nodes, but TEI Simple has no element that MUST contain only a text node.</p><div class="p">If you work with TEI mainly as an encoder, mixed content is an easy concept to get used to. If you are in the business of processing encoded text it is the cause of many problems. Consider our earlier example: <div id="index.xml-egXML-d33e629" class="pre egXML_valid"><span class="element"><s></span>
<span class="element"><name <span class="attribute">rendition</span>="<span class="attributevalue">#italics</span>"></span>Julius Caesar<span class="element"></name></span> was assassinated on <span class="element"><date></span>March 15, 44 BCE<span class="element"></date></span>.
<span class="element"></s></span></div> For the machine this simple sentence exists as three separate text nodes that are children of different elements. A lot of thought has gone into writing software that will easily extract these different text nodes and combine them into a single utterance.</div><p>So much for the header, at least for now. Let us turn to <span class="gi"><text></span>, the container for encoding the actual document, including its title page if it has one. A <span class="term" itemprop="term">book</span> is a bibliographical unit, which may contain one or more <span class="term" itemprop="term">work(s)</span>. The second quarto of Hamlet is a book with one work. The Shakespeare Folio of 1623 contains three dozen separate works. While the TEI can handle both situations, we will focus here on the normal case of <span class="q" itemprop="q">‘one book, one work’</span>, but it is useful to acknowledge the fact that the relationship between <span class="term" itemprop="term">book</span> and <span class="term" itemprop="term">work</span> and be very complex and raises tricky encoding questions.</p><p>The <span class="gi"><text></span> element MUST contain one and only one <span class="gi"><body></span> element. It MAY contain a<span class="gi"><front></span> or <span class="gi"><back></span> element, or both of them, but only one of each. <span class="gi"><front></span> MUST precede and <span class="gi"><back></span> MUST follow <span class="gi"><body></span>. This is another example of perfectly obvious and sensible rules from some domain being codified in the rigid rules of the XML schema. Since you are very unlikely to encode the sequence <span class="gi"><back></span>, <span class="gi"><front></span>, <span class="gi"><body></span>, you will not benefit from the validator's telling you that this is not valid XML, but there are many other and less obvious cases where the validator is helpful.</p><div class="p">The <span class="gi"><body></span> element MUST have something in it. It will be happy with a single paragraph, as in <div id="index.xml-egXML-d33e698" class="pre egXML_valid"><span class="element"><body></span>
<span class="element"><p></span>This is all I have to say<span class="element"></p></span>
<span class="element"></body></span></div> but you are more likely to find more elaborate structures, such as <div id="index.xml-egXML-d33e703" class="pre egXML_valid"><span class="element"><body></span>
<span class="element"><div></span>
<span class="element"><head></span>Chapter One<span class="element"></head></span>
<span class="element"><p></span>It was a dark and stormy night<span class="element"></p></span>
<span class="element"></div></span>
<span class="element"><div></span>
<span class="element"><head></span>Chapter Two<span class="element"></head></span>
<span class="element"><p></span>more stuff about the weather...<span class="element"></p></span>
<span class="element"></div></span>
<span class="element"></body></span></div></div><p>The chapter or section level <span class="gi"><div></span> element is one of the TEI workhorses. You MAY have as many of them as you like in your <span class="gi"><front></span> <span class="gi"><body></span> or <span class="gi"><back></span> elements, and you MAY nest them as deeply as you like.</p><p>The paragraph level <span class="gi"><p></span> element is the other workhorse of the TEI. Any element that MAY contain <span class="gi"><p></span> elements MAY contain any number of them. Unlike <span class="gi"><div></span> elements, <span class="gi"><p></span> MAY contain plain text or PCDATA (and typically will consist mostly of it), but a <span class="gi"><p></span> element MAY NOT nest within another <span class="gi"><p></span> element. This is a perfectly sensible rule. The <span class="gi"><p></span> element is based on the model of the paragraph. Paragraphs divide into sentences; you don't expect them to divide into sub-paragraphs. Or, if there is a document with paragraphs and sub-paragraphs, you are probably in the world of lists and list items. The TEI has elements for lists and their items, and a list item MAY have a <span class="gi"><list></span> child element. But even though <span class="gi"><p></span> MAY NOT be a child of <span class="gi"><p></span>, it is possible that a valid child of <span class="gi"><p></span> could have a valid child element <span class="gi"><p></span>. Whether you SHOULD use such encoding is another question.</p><p>It is useful to think of most TEI elements as operating mainly at one of three levels: </p><ul itemprop="list"><li class="item" itemprop="item"><span class="term" itemprop="term">Text structure</span> elements elements articulate the macrostructure of your document, e.g. <span class="gi"><front></span>,<span class="gi"><body></span>,<span class="gi"><back></span>,<span class="gi"><div></span>. With some very specialized exceptions, such elements MAY NOT contain PCDATA.</li><li class="item" itemprop="item"><span class="term" itemprop="term">Block elements</span>, principally <span class="gi"><p></span> and <span class="gi"><l></span> contain stretches of plain text whose end is almost universally marked by a line break in print.</li><li class="item" itemprop="item"><span class="term" itemprop="term">Inline elements</span> operate at the microstructure of discourse. Printed text will often use italics or some other device to highlight a word or phrase. It is often, but not always possible to determine the reason. In TEI the <span class="gi"><hi></span> element is the all-purpose element to encode inline words or phrases that have been highlighted.</li></ul><p>But wherever one draws a line, there are phenomena that want to cross that line. In TEI there are several <span class="term" itemprop="term">inter</span> elements that can occur within paragraphs (inline) or between paragraphs (block). The most common of these is the versatile and slippery <span class="gi"><q></span> element. Paragraphs often end with a quotation in a pattern like the following:</p><div id="index.xml-egXML-d33e814" class="pre egXML_valid"><span class="element"><p></span>.....and wrote as follows:
<span class="element"><q></span>
<span class="element"><p></span>one paragraph<span class="element"></p></span>
<span class="element"><p></span>another paragraph<span class="element"></p></span>
<span class="element"><p></span>yet another paragraph<span class="element"></p></span>
<span class="element"></q></span>
<span class="element"></p></span></div><p>The fact that the paragraph does not end with a period but with a colon might lead you to think of the quotation as part of the previous paragraph. It does, however, lead to a deeply nested structure in which <span class="gi"><p></span> elements are the descendants of <span class="gi"><p></span> elements. If you like #5 of the Zen of Python (<span class="quote" itemprop="quote">‘flat is better than nested’</span>) you might decide that the paragraph is terminated by the colon and that <span class="gi"><q></span> should be the right sibling rather than child of <span class="gi"><p></span>:</p><div id="index.xml-egXML-d33e841" class="pre egXML_valid"><span class="element"><p></span>.....and wrote as follows:<span class="element"></p></span>
<span class="element"><q></span>
<span class="element"><p></span>one paragraph<span class="element"></p></span>
<span class="element"><p></span>another paragraph<span class="element"></p></span>
<span class="element"><p></span>yet another paragraph<span class="element"></p></span>
<span class="element"></q></span></div><p>That is a very different case from a quotation of two lines of verse in the middle of a sentence, as in </p><div id="index.xml-egXML-d33e853" class="pre egXML_valid"><span class="element"><p></span>.....when Hamlet says:
<span class="element"><q></span>
<span class="element"><l></span>But that the dread of something after death,<span class="element"></l></span>
<span class="element"><l></span>The undiscovered country from whose bourn<span class="element"></l></span>
<span class="element"><l></span>No traveller returns, puzzles the will<span class="element"></l></span>
<span class="element"></q></span>
he means that...<span class="element"></p></span></div><p>In the latter case there is no ambiguity or choice, and there is nothing strained about <span class="gi"><l></span> as a descendant of <span class="gi"><p></span> In the former case, there is ambiguity, and you may want to choose the option that avoids strained nesting. With nested structures it is useful to follow the advice <span class="q" itemprop="q">‘as much as necessary but as little as possible’</span>.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.7"><h2><span class="headingNumber">2.7. </span><span class="head" itemprop="head">About Namespaces</span></h2><p>Namespaces are a little like surnames, letting you distinguish between Miller, Henry and Smith, Henry. For instance, HTML and TEI both use elements with the names <span class="gi"><p></span> and <span class="gi"><div></span>. But these are "false friends" with very different meanings and operating rules. By convention a namespace takes the form of a URL. The full name of an element is known as its "qualified name" or QName, and in one conventional notation it is written by prefixing the element name with the namespace in curly braces Thus the namespace of TEI is http://www.tei-c.org/ns/1.0, and the full name of a TEI element such as <span class="gi"><p></span> is {http://www.tei-c.org/ns/1.0}p.</p><p>Because QNames are very clumsy things to manipulate, shortcuts have been invented. If you map the namespace to a prefix, tei:p will stand for {http://www.tei-c.org/ns/1.0}p, five instead of thirty characters. The choice of the prefix is arbitrary, but the prefix and element name must be connected by a colon. Unless you manipulate an XML text with XSLT, xquery, or some other language, you don't have to worry much about namespaces. But it is useful to know about them. If you do have to use them remember that they are fussy and a common source of error. </p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.8"><h2><span class="headingNumber">2.8. </span><span class="head" itemprop="head">About Attributes</span></h2><p>Elements can have attributes. The term is borrowed from grammar, and attributes relate to elements pretty much as adjectives relate to nouns. An attribute consists of a <span class="term" itemprop="term">key-value</span> pair, such as <span class="hi" itemprop="hi">type='act'</span>, where the term before the equal sign is the name of the attribute and the term after the equal sign is the value. The value must be in quotation marks,whether single or double, but <span class="hi" itemprop="hi">smart</span> quotation marks will raise an error message. Thus <div typ="act" n=3"> would be a way of specifying a particular <span class="gi"><div></span> as containing "Act III" of some play.</p><p>In well-formed XML, there are rules about the names of attributes, but no rules about what attributes to use with what elements or what values to associate with the attributes. In valid XML, the rules for attributes are specified in the schema. There are rules about what attributes may be used with with what elements and what kinds of data may, must, or may not appear in attribute values. In the TEI schema some attributes are <span class="term" itemprop="term">global</span> and can be used in the same manner for any element. Other attributes are specific to a particular set of elements.</p><p>A few of the global attributes in the TEI schema belong to the xml namespace. The two that you are likely to encounter often are xml:id and xml:lang. The former specifies an ID for an element that is unique within the document. The latter specifies the language in which the document (or part of it) is written. The rules for these two attributes are not TEI specific but follow the general rules for XML. That is why instead of <span class="hi" itemprop="hi">id</span> and <span class="hi" itemprop="hi">lang</span> these attributes always appear with their XML prefix <span class="hi" itemprop="hi">xml:id</span> and <span class="hi" itemprop="hi">xml:lang</span>.</p><p>In the TEI schema the value of an xml:id attribute must be a proper <span class="term" itemprop="term">XML Name</span>: it must begin with an alphabetic character; it may include digits, periods, hyphens, and underscores, but not commas, or semicolons. Because the colon required to link a namespace prefix to an attribute name you should only use it for that purpose. TEI has its own rules for what values may, may not, or must appear in different attributes.</p><p>The two most widely used global attributes in TEI are <span xmlns="" class="att" itemprop="att">n</span> and <span xmlns="" class="att" itemprop="att">rendition</span>. The name of the former is short for "number," and numbering of one kind or another is its most common, but not its only use. There are hardly any restrictions on what you can use for its attribute values. You can even, while you are working with a document, embed comments, as long as you remember to remove them in time. If n="5" is a proper value, so is n="5 check this again later." But you will be better off using the formal commenting protocol of XML, wrapping any kind of comment in <!-- [my comment] --></p><p>Other attributes values are much fussier. The <span class="gi"><l></span> supports a <span xmlns="" class="att" itemprop="att">part</span> attributed with a fixed list of values Y, N, I, M, F for <span class="term" itemprop="term">yes</span>, <span class="term" itemprop="term">no</span>, <span class="term" itemprop="term">initial</span>, <span class="term" itemprop="term">medial</span>, and <span class="term" itemprop="term">final</span>. The value for the <span xmlns="" class="att" itemprop="att">target</span> attributes for the linking element <span class="gi"><ref></span> may consist of one or more URL's separated by white space.</p><p>The <span xmlns="" class="att" itemprop="att">type</span> attribute, which is available for some but not all elements, is a very powerful device for making more granular distinctions among kinds of discourse, especially when it is combined with a <span class="term" itemprop="term">controlled vocabulary</span>. For instance, the TEI schema include a <span class="gi"><lg></span> element for encoding any kind of grouping of lines of verse. A controlled vocabulary for tagging stanzaic and metrical patterns is a great device for enhancing the query potential of a corpus of poems.</p></div><div class="teidiv1" id="index.xml-body.1_div.2_div.9"><h2><span class="headingNumber">2.9. </span><span class="head" itemprop="head">Limitations of TEI as an XML Markup Language</span></h2><p>As an XML markup language TEI is committed to two axioms: </p><ul itemprop="list"><li class="item" itemprop="item">A document is an OHCO or ordered hierarchy of content objects</li><li class="item" itemprop="item">The presentation of a document can be neatly separated from its structure</li></ul><p> Both of these axioms are deeply problematical when it comes to texts, but they are true often enough to be useful. Many texts divide neatly into single hierarchical structures, but others do not, and rhetorical effects frequently rely on the reader's or listener's effortless management of what in TEI parlance is called <span class="term" itemprop="term">overlapping</span> or <span class="term" itemprop="term">concurrent</span> hierarchies. Take the last two lines of Hamlet's soliloquy:</p><blockquote class="quote" itemprop="quote"><div class="l" itemprop="l">The fair Ophelia! Nymph, in thy orisons</div> <div class="l" itemprop="l">Be all my sins remembered.</div></blockquote><p>The prosodic structure of two lines of blank verse is counterpointed by a syntactic structure in which a sentence begins in the middle of one line and spills over without a break into the next line. You might be tempted to encode this as follows</p><div id="index.xml-egXML-d33e1009" class="pre egXML_valid"><span class="element"><quote></span>
<span class="element"><l></span>
<span class="element"><s></span>The fair Ophelia!<span class="element"></s></span> <s>Nymph, in thy orisons<span class="element"></l></span>
<span class="element"><l></span> Be all my sins remembered.</s><span class="element"></l></span>
<span class="element"></quote></span></div><div class="p">But this will generate the error message <span class="q" itemprop="q">‘The element type "s" must be terminated by the matching end-tag "s". ’</span> It is a cardinal rule of XML that no child element may have two parents. There are various workarounds. You can use milestones, as in <div id="index.xml-egXML-d33e1022" class="pre egXML_valid"><span class="element"><quote></span>
<span class="element"><l></span>
<span class="element"><milestone <span class="attribute">unit</span>="<span class="attributevalue">sentence</span>"/></span>.The fair Ophelia!
<span class="element"><milestone <span class="attribute">unit</span>="<span class="attributevalue">sentence</span>"/></span> Nymph, in thy orisons<span class="element"></l></span>
<span class="element"><l></span> Be all my sins remembered.<span class="element"></l></span>
<span class="element"></quote></span></div> Using the punctuation element <span class="gi"><pc></span> you would get a similar articulation: <div id="index.xml-egXML-d33e1035" class="pre egXML_valid"><span class="element"><quote></span>
<span class="element"><l></span>The fair Ophelia<span class="element"><pc <span class="attribute">unit</span>="<span class="attributevalue">sentence</span>"></span>!<span class="element"></pc></span>
<span class="element"><milestone <span class="attribute">unit</span>="<span class="attributevalue">sentence</span>"/></span> Nymph, in thy orisons<span class="element"></l></span>
<span class="element"><l></span> Be all my sins remembered<span class="element"><pc <span class="attribute">unit</span>="<span class="attributevalue">sentence</span>"></span>.<span class="element"></pc></span>
<span class="element"></l></span>
<span class="element"></quote></span></div> You could also use the <span xmlns="" class="att" itemprop="att">next</span> and <span xmlns="" class="att" itemprop="att">previous</span> attributes to tie the two <span class="gi"><s></span> elements together: <div id="index.xml-egXML-d33e1058" class="pre egXML_valid"><span class="element"><quote></span>
<span class="element"><l></span>The fair Ophelia!
<span class="element"><s <span class="attribute">xml:id</span>="<span class="attributevalue">s1</span>" <span class="attribute">next</span>="<span class="attributevalue">#s2</span>"></span>Nymph, in thy orisons<span class="element"></s></span>
<span class="element"></l></span>
<span class="element"><l></span>
<span class="element"><s <span class="attribute">xml:id</span>="<span class="attributevalue">s2</span>" <span class="attribute">previous</span>="<span class="attributevalue">#s1</span>"></span>Be all my sins remembered.<span class="element"></s></span>
<span class="element"></l></span>
<span class="element"></quote></span></div> These workarounds do a more or less adequate job at articulating a secondary structure in the face of a dominant structure, but they are workarounds. There are other and more powerful workarounds. Chapter 18 of the Guidelines discusses <span class="term" itemprop="term">feature structures</span>, and there is <span class="term" itemprop="term">stand-off markup</span>, where different forms of textual segmentation and annotation are kept in separate documents that point to individual tokens or token ranges in the text. Feature structures take you well beyond TEI Simple, and stand-off will also be most beyond its range.</div><p>The second axiom, that content is entirely separable from presentation, will rub most literary critics the wrong way. If you are used to reading a book printed in <span class="term" itemprop="term">Fraktur</span> you may feel that printing it in <span class="term" itemprop="term">Antiqua</span> robs it of its spirit. In Vergil's <span class="titlem">Eclogues</span> up or down things happen at oddly regular intervals. Vergil appears to have written these poems on page blocks with forty lines and knew when he was writing at the top of page (nice words about Maecenas) or at the bottom (bad things happening to bad guys). There are countless examples of playing with layout and typography, from George Herbert to concrete poetry.</p><p>If you make the physical layout of a text the organizing structure you can do that by using the <span class="gi"><surface ></span> element and its children. That is also beyond the scope of TEI Simple, but it is fully documented in Chapter 11 of the <span class="titlem">Guidelines</span></p><p>TEI is about <span class="term" itemprop="term">text</span>, and texts are written in <span class="term" itemprop="term">natural</span> languages. Natural Language Processing (NLP) is a very important part of computing. If you engage in it you will discover early on that human language is highly rule-bound, that you can write procedures that will allow a machine to capture many of these rules very accurately and at great speed, but there is always an algorithmically intractable residue. St. Jerome, the translator of the Bible into Latin, spoke of <span class="quote" lang="la" itemprop="quote">‘ipsum... suum et, ut ita dicam, vernaculum linguae genus’</span> (the distinct and as it were vernacular nature of each language) and the 16th-century French poet Du Bellay argued that literal translation destroys the <span class="quote" lang="la" itemprop="quote">‘je ne scay quoy’</span> of a language. Pope wrote of a <span class="quote" itemprop="quote">‘grace beyond the reach of art’</span>. Text encoding is a way of enabling a machine to process texts in ways that help human readers "make sense" of them. The machine can take you quite far, but it will only take you so far. In an encoding project of any complexity there will always be some moments when you remember this line from Wallace Stevens' <span class="titlem">Connoisseurs of Chaos:</span></p><div class="l" itemprop="l">The squirming facts exceed the squamous mind.</div></div><div class="teidiv1" id="tagabuse"><h2><span class="headingNumber">2.10. </span><span class="head" itemprop="head">Should, Should Not, and Tag Abuse</span></h2><p>Valid encoding is not necessarily good encoding, just as rigid compliance with the law does not always square with justice. Here we are in the realm of Aristotle's <span class="foreign" itemprop="foreign">epieikia</span> or equity as a principle that complements rigid compliance with a set of rules. The word lives in a space tenuously circumscribed by the probable, the reasonable, and the appropriate--very much like the space of the French twins <span class="term" itemprop="term">vraisemblance</span> and <span class="term" itemprop="term">bienséance</span>What SHOULD you do when confronted with a problem to which the schema offers no obvious solution? Do as your neighbours do is good advice when you live in a good neighbourhood, and as a TEI encoder you happen to live in a very friendly and helpful neighbourhood. Sign up for the <a class="link_ref" itemprop="ref" href="https://listserv.brown.edu/archives/cgi-bin/wa?A0=TEI-L">TEI listserv </a> and ask for advice. It will come to you from just about any continent, very promptly at any hour of the day or night, and it is nearly always relevant. Following the TEI list and pondering its advice is the best way of getting a feel for the discretionary space surrounds all rulles, and it will keep you from committing <span class="term" itemprop="term">tag abuse</span>, the TEI community's term for encoding practices that are valid but make no sense or worse.</p></div></section><section class="teidiv0" id="index.xml-body.1_div.3"><header><h1><span class="headingNumber">3. </span><span class="head" itemprop="head">A tour of TEI Simple from an encoding perspective</span></h1></header><div class="teidiv1" id="Simple-eg"><h2><span class="headingNumber">3.1. </span><span class="head" itemprop="head">A Short Example</span></h2><p>We begin with a short example, intended to show what happens when a passage of prose is typed into a computer by someone with little sense of the query potential of a digitally encoded text. In an ideal world, such output might be generated by a very accurate optical scanner. It attempts to be faithful to the appearance of the printed text, by retaining the original line breaks, by introducing blanks to represent the layout of the original headings and page breaks, and so forth. Where characters not available on the keyboard are needed (such as the accented letter <span class="mentioned" itemprop="mentioned">a</span> in <span class="mentioned" itemprop="mentioned">faàl</span> or the long dash), it attempts to mimic their appearance.</p><pre class="pre_eg cdata">
CHAPTER 38
READER, I married him. A quiet wedding we had: he and I, the par-
son and clerk, were alone present. When we got back from church, I
went into the kitchen of the manor-house, where Mary was cooking
the dinner, and John cleaning the knives, and I said --
'Mary, I have been married to Mr Rochester this morning.' The
housekeeper and her husband were of that decent, phlegmatic
order of people, to whom one may at any time safely communicate a
remarkable piece of news without incurring the danger of having
one's ears pierced by some shrill ejaculation and subsequently stunned
by a torrent of wordy wonderment. Mary did look up, and she did
stare at me; the ladle with which she was basting a pair of chickens
roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the
polishing process; but Mary, bending again over the roast, said only --
'Have you, miss? Well, for sure!'
A short time after she pursued, 'I seed you go out with the master,
but I didn't know you were gone to church to be wed'; and she
basted away. John, when I turned to him, was grinning from ear to
ear.
'I telled Mary how it would be,' he said: 'I knew what Mr Ed-
ward' (John was an old servant, and had known his master when he
was the cadet of the house, therefore he often gave him his Christian
name) -- 'I knew what Mr Edward would do; and I was certain he
would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!' and he politely pulled his forelock.
'Thank you, John. Mr Rochester told me to give you and Mary
this.'
I put into his hand a five-pound note. Without waiting to hear
more, I left the kitchen. In passing the door of that sanctum some time
after, I caught the words --
'She'll happen do better for him nor ony o' t' grand ladies.' And
again, 'If she ben't one o' th' handsomest, she's noan faa\l, and varry
good-natured; and i' his een she's fair beautiful, onybody may see
that.'
I wrote to Moor House and to Cambridge immediately, to say what
I had done: fully explaining also why I had thus acted. Diana and
474
JANE EYRE 475
Mary approved the step unreservedly. Diana announced that she
would just give me time to get over the honeymoon, and then she
would come and see me.
'She had better not wait till then, Jane,' said Mr Rochester, when I
read her letter to him; 'if she does, she will be too late, for our honey-
moon will shine our life long: its beams will only fade over your
grave or mine.'
How St John received the news I don't know: he never answered
the letter in which I communicated it: yet six months after he wrote
to me, without, however, mentioning Mr Rochester's name or allud-
ing to my marriage. His letter was then calm, and though very serious,
kind. He has maintained a regular, though not very frequent correspond-
ence ever since: he hopes I am happy, and trusts I am not of those who
live without God in the world, and only mind earthly things.
</pre><p>This transcription suffers from a number of shortcomings: </p><ul itemprop="list"><li class="item" itemprop="item">the page numbers and running titles are intermingled with the text in a way which makes it difficult for software to disentangle them;</li><li class="item" itemprop="item">no distinction is made between single quotation marks and apostrophe, so it is difficult to know exactly which passages are in direct speech;</li><li class="item" itemprop="item">the preservation of the copy text's hyphenation means that simple-minded search programs will not find the broken words;</li><li class="item" itemprop="item">the accented letter in <span class="mentioned" itemprop="mentioned">faàl</span> and the long dash have been rendered by ad hoc keying conventions which follow no standard pattern and will be processed correctly only if the transcriber remembers to mention them in the documentation;</li><li class="item" itemprop="item">paragraph divisions are marked only by the use of white space, and hard carriage returns have been introduced at the end of each line. Consequently, if the size of type used to print the text changes, reformatting will be problematic.</li></ul><div class="p">We now present the same passage, as it might be encoded in TEI Simple. As we shall see, there are many ways in which this encoding could be extended, but as a minimum, the TEI approach allows us to represent the following distinctions: <ul itemprop="list"><li class="item" itemprop="item">Paragraph and chapter divisions are now marked explicitly.</li><li class="item" itemprop="item">Apostrophes are distinguished from quotation marks; direct speech is explicitly marked.</li><li class="item" itemprop="item">The accented letter and the long dash are correctly represented.</li><li class="item" itemprop="item">Page divisions have been marked with an empty <span class="gi"><pb></span> element alone.</li><li class="item" itemprop="item">The lineation of the original has not been retained and words broken by typographic accident at the end of a line have been re-assembled without comment.</li><li class="item" itemprop="item">For convenience of proof reading, a new line has been introduced at the start of each paragraph, but the indentation is removed.</li></ul> <div id="index.xml-egXML-d33e1190" class="pre egXML_valid"><span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">474</span>"/></span>
<span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">chapter</span>" <span class="attribute">n</span>="<span class="attributevalue">38</span>"></span>
<span class="element"><p></span>Reader, I married him. A quiet wedding we had: he and I, the parson and clerk, were alone
present. When we got back from church, I went into the kitchen of the manor-house, where
Mary was cooking the dinner, and John cleaning the knives, and I said —<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>Mary, I have been married to Mr Rochester this morning.<span class="element"></q></span> The housekeeper and her
husband were of that decent, phlegmatic order of people, to whom one may at any time safely
communicate a remarkable piece of news without incurring the danger of having one's ears
pierced by some shrill ejaculation and subsequently stunned by a torrent of wordy
wonderment. Mary did look up, and she did stare at me; the ladle with which she was basting
a pair of chickens roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the polishing process; but
Mary, bending again over the roast, said only —<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>Have you, miss? Well, for sure!<span class="element"></q></span>
<span class="element"></p></span>
<span class="element"><p></span>A short time after she pursued, <span class="element"><q></span>I seed you go out with the master, but I didn't know
you were gone to church to be wed<span class="element"></q></span>; and she basted away. John, when I turned to him, was
grinning from ear to ear. <span class="element"><q></span>I telled Mary how it would be,<span class="element"></q></span> he said: <span class="element"><q></span>I knew what Mr
Edward<span class="element"></q></span> (John was an old servant, and had known his master when he was the cadet of the
house, therefore he often gave him his Christian name) — <span class="element"><q></span>I knew what Mr Edward would do;
and I was certain he would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!<span class="element"></q></span> and he politely pulled his forelock.<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>Thank you, John. Mr Rochester told me to give you and Mary this.<span class="element"></q></span>
<span class="element"></p></span>
<span class="element"><p></span>I put into his hand a five-pound note. Without waiting to hear more, I left the kitchen.
In passing the door of that sanctum some time after, I caught the words —<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>She'll happen do better for him nor ony o' t' grand ladies.<span class="element"></q></span> And again, <span class="element"><q></span>If she
ben't one o' th' handsomest, she's noan faàl, and varry good-natured; and i' his een she's
fair beautiful, onybody may see that.<span class="element"></q></span>
<span class="element"></p></span>
<span class="element"><p></span>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
explaining also why I had thus acted. Diana and <span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">475</span>"/></span> Mary approved the step
unreservedly. Diana announced that she would just give me time to get over the honeymoon,
and then she would come and see me.<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>She had better not wait till then, Jane,<span class="element"></q></span> said Mr Rochester, when I read her letter
to him; <span class="element"><q></span>if she does, she will be too late, for our honeymoon will shine our life long:
its beams will only fade over your grave or mine.<span class="element"></q></span>
<span class="element"></p></span>
<span class="element"><p></span>How St John received the news I don't know: he never answered the letter in which I
communicated it: yet six months after he wrote to me, without, however, mentioning Mr
Rochester's name or alluding to my marriage. His letter was then calm, and though very
serious, kind. He has maintained a regular, though not very frequent correspondence ever
since: he hopes I am happy, and trusts I am not of those who live without God in the world,
and only mind earthly things.<span class="element"></p></span>
<span class="element"></div></span></div></div><p>This particular encoding represents a set of choices or priorities. As a trivial example, note that in the second example, end-of-line hyphenation has been silently removed. Conceivably Brontë (or her printer) intended the word <span class="q" itemprop="q">‘honeymoon’</span> to appear as <span class="q" itemprop="q">‘honey-moon’</span> on its second appearance, though this seems unlikely: our decision to focus on Brontë's text, rather than on the printing of it in this particular edition, makes it impossible to be certain. This is an instance of the fundamental <span class="hi" itemprop="hi">selectivity</span> of any encoding. An encoding makes explicit only those textual features of importance to the encoder. It is not difficult to think of ways in which the encoding of even this short passage might readily be extended. For example: </p><ul itemprop="list"><li class="item" itemprop="item">a regularized form of the passages in dialect could be provided; </li><li class="item" itemprop="item">footnotes glossing or commenting on any passage could be added;</li><li class="item" itemprop="item">pointers linking parts of this text to others could be added;</li><li class="item" itemprop="item">proper names of various kinds could be distinguished from the surrounding text;</li><li class="item" itemprop="item">names could be classified as personal, geographical, or institutional</li><li class="item" itemprop="item">detailed bibliographic information about the text's provenance and context could be prefixed to it;</li><li class="item" itemprop="item">a linguistic analysis of the passage into sentences, clauses, words, etc., could be provided, each unit being associated with appropriate category codes;</li><li class="item" itemprop="item">the text could be segmented into narrative or discourse units;</li><li class="item" itemprop="item">systematic analysis or interpretation of the text could be included in the encoding, with potentially complex alignment or linkage between the text and the analysis, or between the text and one or more translations of it;</li><li class="item" itemprop="item">passages in the text could be linked to images or sound held on other media.</li></ul><p>TEI-recommended ways of carrying out most of these are described in the remainder of this document. Consult the full <span class="titlem">Guidelines</span> for more detail.</p></div><div class="teidiv1" id="Simple-struc"><h2><span class="headingNumber">3.2. </span><span class="head" itemprop="head">The Structure of a TEI Text</span></h2><p>Almost all TEI-conformant texts contain (a) a <span class="term" itemprop="term">TEI header</span> (marked up as a <span class="gi"><teiHeader></span> element) and (b) the transcription of the text proper (marked up as a <span class="gi"><text></span> element). These two elements are combined together to form a single <span class="gi"><TEI></span> element, which must be declared within the TEI namespace. The full name of the <span class="gi"><TEI></span> element is < xmlns="http://www.tei-c.org/ns/1.0"> .</p><p>The header is described in more detail in section <a class="link_ptr" itemprop="ptr" href="#Simple-header" title="The Electronic Title Page"><span class="headingNumber">3.17. </span>The Electronic Title Page</a>. The word "almost" in the paragraph above acknowledges the existence of a form of TEI encoding that seeks to capture what is often called the <span class="term" itemprop="term">materiality</span> of the text. Some of the relevant element names , <span class="gi"><facsimile></span>, <span class="gi"><surface></span>, <span class="gi"><zone></span>, give you a sense of this approach, where the content of element would be images or other media types rather than transcribed text. While this set of elements is outside the scope of TEI Simple, digital representations that combine transcription with facsimiles are likely to be more common in the future. The global <span xmlns="" class="att" itemprop="att">facs</span> attribute is the obvious device for linking pages or other chunks of transcribed TEI Simple text to facsimiles. For more information consult the section on <a class="link_ref" itemprop="ref" href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHFAX">Digital Facsimiles</a> in the <span class="titlem">Guidelines</span>.</p><p>A TEI text may be <span class="term" itemprop="term">unitary</span> (a single work) or <span class="term" itemprop="term">composite</span> (a collection of single works, such as an anthology). In either case, the text may have an optional <span class="term" itemprop="term">front</span> or <span class="term" itemprop="term">back</span>. In between is the <span class="term" itemprop="term">body</span> of the text, which, in the case of a composite text, may consist of <span class="term" itemprop="term">groups</span>, each containing more groups or texts.</p><div class="p">A unitary text will be encoded using an overall structure like this: <div id="index.xml-egXML-d33e1345" class="pre egXML_valid"><span class="element"><TEI xmlns="http://www.tei-c.org/ns/1.0"></span>
<span class="element"><teiHeader></span>
<span class="comment"><!-- [ TEI Header information ] --></span>
<span class="element"></teiHeader></span>
<span class="element"><text></span>
<span class="element"><front></span>
<span class="comment"><!-- [ front matter ... ] --></span>
<span class="element"></front></span>
<span class="element"><body></span>
<span class="comment"><!-- [ body of text ... ] --></span>
<span class="element"></body></span>
<span class="element"><back></span>
<span class="comment"><!-- [ back matter ... ] --></span>
<span class="element"></back></span>
<span class="element"></text></span>
<span class="element"></TEI></span></div></div><p>Note that in the example above the text between "<!--" and "-->" is a comment that is ignored by the XML parser. You can use the same convention for interspersing comments in your XML document, and it will be similarly ignored. Why then does it show up in the example? Everything in the example is wrapped in a special <egXML> element, which lets you display "raw" XML fragments without the XML parser acting on them.</p><p>In the remainder of this document, we discuss chiefly simple text structures, but composite texts are briefly discussed in <a class="link_ptr" itemprop="ptr" href="#Simple-composite" title=""><span class="headingNumber">3.15. </span></a> In each of the following sections we begin with a short list of relevant TEI <span class="term" itemprop="term">elements</span> and give their formal definition, followed by definitions for any <span class="term" itemprop="term">attributes</span> specific to that element. These references are linked to full specifications for each object, as given in the TEI <span class="titlem">Guidelines</span>. In most cases, short examples are also given.</p><p>For example, here are the elements discussed so far: </p></div><div class="teidiv1" id="Simple-body"><h2><span class="headingNumber">3.3. </span><span class="head" itemprop="head">Encoding the Body</span></h2><p>As indicated above, a simple TEI document at the textual level consists of the following elements: Elements specific to front and back matter are described below in section <a class="link_ptr" itemprop="ptr" href="#Simple-fronbac" title="Front and Back Matter"><span class="headingNumber">3.16. </span>Front and Back Matter</a>. In this section we discuss the elements making up the body of a text.</p><div class="teidiv2" id="divs"><h3><span class="headingNumber">3.3.1. </span><span class="head" itemprop="head">Text Division Elements</span></h3><p>The body of a prose text may be just a series of paragraphs, or these paragraphs may be grouped together into chapters, sections, subsections, etc. Each paragraph is tagged using the <span class="gi"><p></span> tag. The <span class="gi"><div></span> element is used to represent any such grouping of paragraphs. </p><p>The <span xmlns="" class="att" itemprop="att">type</span> attribute on the <span class="gi"><div></span> element may be used to supply a conventional name for this category of text division, or otherwise distinguish them. Typical values might be <span class="q" itemprop="q">‘book’</span>, <span class="q" itemprop="q">‘chapter’</span>, <span class="q" itemprop="q">‘section’</span>, <span class="q" itemprop="q">‘part’</span>, <span class="q" itemprop="q">‘poem’</span>, <span class="q" itemprop="q">‘song’</span>, etc. For a given project, it will usually be advisable to define and adhere to a specific list of such values.</p><p>A <span class="gi"><div></span> element may itself contain further, nested, <span class="gi"><div></span>s, thus mimicking the traditional structure of a book, which can be decomposed hierarchically into units such as parts, containing chapters, containing sections, and so on. TEI texts in general conform to this simple hierarchic model.</p><p>The <span xmlns="" class="att" itemprop="att">xml:id</span> attribute may be used to supply a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary, as further discussed in section <a class="link_ptr" itemprop="ptr" href="#Simple-ptrs" title="Cross References and Links"><span class="headingNumber">3.7. </span>Cross References and Links</a>. It is often useful to provide an <span xmlns="" class="att" itemprop="att">xml:id</span> attribute for every major structural unit in a text, and to derive its values in some systematic way, for example by appending a section number to a short code for the title of the work in question, as in the examples below. It is particularly useful to supply such identifiers if the resource concerned is to be made available over the web, since they make it much easier for other web-based applications to link directly to the corresponding parts of your text.</p><p>The <span xmlns="" class="att" itemprop="att">n</span> attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for a division, or any other element. If a conventional form of reference or abbreviation for the parts of a work already exists (such as the book/chapter/verse pattern of Biblical citations), the <span xmlns="" class="att" itemprop="att">n</span> attribute is the place to record it; unlike the identifier supplied by <span xmlns="" class="att" itemprop="att">xml:id</span>, it does not need to be unique.</p><p>The <span xmlns="" class="att" itemprop="att">xml:lang</span> attribute may be used to specify the language of the division. Languages are identified by an internationally defined code, as further discussed in section <a class="link_ptr" itemprop="ptr" href="#z636" title="Foreign Words or Expressions"><span class="headingNumber">3.5.3. </span>Foreign Words or Expressions</a> below.</p><p>The <span xmlns="" class="att" itemprop="att">rendition</span> attribute may be used to supply information about the rendition (appearance) of a division, or any other element, as further discussed in section <a class="link_ptr" itemprop="ptr" href="#Simple-hilites" title="Marking Highlighted Phrases"><span class="headingNumber">3.5. </span>Marking Highlighted Phrases</a> below. You should document your use of the possible values of <span xmlns="" class="att" itemprop="att">rendition</span> in the taggin declaration (<span class="gi"><tagsDecl></span> of your header.</p><p>These four attributes, <span xmlns="" class="att" itemprop="att">xml:id</span>, <span xmlns="" class="att" itemprop="att">n</span>, <span xmlns="" class="att" itemprop="att">xml:lang</span>, and <span xmlns="" class="att" itemprop="att">rend</span> are so widely useful that they are allowed on any element in any TEI schema: they are <span class="term" itemprop="term">global attributes</span>. Other global attributes defined in the TEI Simple schema are discussed in section <a class="link_ptr" itemprop="ptr" href="#xatts" title="Special kinds of Linking"><span class="headingNumber">3.7.3. </span>Special kinds of Linking</a>.</p><div class="p">The value of every <span xmlns="" class="att" itemprop="att">xml:id</span> attribute should be unique within a document or across a corpus, if your project spans many texts.. One simple way of ensuring that this is so is to make it reflect the hierarchic structure of the document. For example, Smith's <span class="titlem">Wealth of Nations</span> as first published consists of five books, each of which is divided into chapters, while some chapters are further subdivided into parts. We might define <span xmlns="" class="att" itemprop="att">xml:id</span> values for this structure as follows: <div id="index.xml-egXML-d33e1513" class="pre egXML_valid"><span class="element"><body></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN1</span>" <span class="attribute">n</span>="<span class="attributevalue">I</span>" <span class="attribute">type</span>="<span class="attributevalue">book</span>"></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN101</span>" <span class="attribute">n</span>="<span class="attributevalue">I.1</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN102</span>" <span class="attribute">n</span>="<span class="attributevalue">I.2</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="comment"><!-- ... --></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN110</span>" <span class="attribute">n</span>="<span class="attributevalue">I.10</span>"
<span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN1101</span>" <span class="attribute">n</span>="<span class="attributevalue">I.10.1</span>"
<span class="attribute">type</span>="<span class="attributevalue">part</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN1102</span>" <span class="attribute">n</span>="<span class="attributevalue">I.10.2</span>"
<span class="attribute">type</span>="<span class="attributevalue">part</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"></div></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">WN2</span>" <span class="attribute">n</span>="<span class="attributevalue">II</span>" <span class="attribute">type</span>="<span class="attributevalue">book</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"></body></span></div></div><div class="p">A different numbering scheme may be used for <span xmlns="" class="att" itemprop="att">xml:id</span> and <span xmlns="" class="att" itemprop="att">n</span> attributes: this is often useful where a canonical reference scheme is used which does not tally with the structure of the work. For example, in a novel divided into books each containing chapters, where the chapters are numbered sequentially through the whole work, rather than within each book, one might use a scheme such as the following: <div id="index.xml-egXML-d33e1537" class="pre egXML_valid"><span class="element"><body></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS01</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">volume</span>"></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS011</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS012</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS02</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>" <span class="attribute">type</span>="<span class="attributevalue">volume</span>"></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS021</span>" <span class="attribute">n</span>="<span class="attributevalue">3</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">TS022</span>" <span class="attribute">n</span>="<span class="attributevalue">4</span>" <span class="attribute">type</span>="<span class="attributevalue">chapter</span>"></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"></div></span>
<span class="element"></body></span></div> Here the work has two volumes, each containing two chapters. The chapters are numbered conventionally 1 to 4, but the <span xmlns="" class="att" itemprop="att">xml:id</span> values specified allow them to be regarded additionally as if they were numbered 1.1, 1.2, 2.1, 2.2.</div></div><div class="teidiv2" id="h25"><h3><span class="headingNumber">3.3.2. </span><span class="head" itemprop="head">Headings and Closings</span></h3><p>Every <span class="gi"><div></span> may have a title or heading at its start, and (less commonly) a trailer such as <span class="q" itemprop="q">‘End of Chapter 1’</span> at its end. The following elements may be used to transcribe them: Some other elements which may be necessary at the beginning or ending of text divisions are discussed below in section <a class="link_ptr" itemprop="ptr" href="#h52" title="Prefatory Matter"><span class="headingNumber">3.16.1.2. </span>Prefatory Matter</a>.</p><div class="p">Whether or not headings and trailers are included in a transcription is a matter for the individual transcriber to decide. Where a heading is completely regular (for example <span class="q" itemprop="q">‘Chapter 1’</span>) or may be automatically constructed from attribute values (e.g. <code itemprop="code"><div type="chapter" n="1"></code>), it may be omitted; where it contains otherwise unrecoverable text it should always be included. For example, the start of Hardy's <span class="titlem">Under the Greenwood Tree</span> might be encoded as follows: <div id="index.xml-egXML-d33e1581" class="pre egXML_valid"><span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">UGT1</span>" <span class="attribute">n</span>="<span class="attributevalue">Winter</span>" <span class="attribute">type</span>="<span class="attributevalue">Part</span>"></span>
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">UGT11</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>" <span class="attribute">type</span>="<span class="attributevalue">Chapter</span>"></span>
<span class="element"><head></span>Mellstock-Lane<span class="element"></head></span>
<span class="element"><p></span>To dwellers in a wood almost every species of tree ... <span class="element"></p></span>
<span class="element"></div></span>
<span class="element"></div></span></div></div></div><div class="teidiv2" id="vedr"><h3><span class="headingNumber">3.3.3. </span><span class="head" itemprop="head">Prose, Verse and Drama</span></h3><p>As in the Bronte example above, the paragraphs making up a textual division are tagged with the <span class="gi"><p></span> tag. In poetic or dramatic texts different tags are needed, to represent verse lines and stanzas in the first case, or individual speeches and stage directions in the second. : </p><div class="p">Here, for example, is the start of a poetic text in which verse lines and stanzas are tagged: <div id="index.xml-egXML-d33e1605" class="pre egXML_valid"><span class="element"><lg <span class="attribute">n</span>="<span class="attributevalue">I</span>"></span>
<span class="element"><l></span>I Sing the progresse of a
deathlesse soule,<span class="element"></l></span>
<span class="element"><l></span>Whom Fate, with God made, but doth not controule,<span class="element"></l></span>
<span class="element"><l></span>Plac'd in
most shapes; all times before the law<span class="element"></l></span>
<span class="element"><l></span>Yoak'd us, and when, and since, in this I
sing.<span class="element"></l></span>
<span class="element"><l></span>And the great world to his aged evening;<span class="element"></l></span>
<span class="element"><l></span>From infant morne, through manly
noone I draw.<span class="element"></l></span>
<span class="element"><l></span>What the gold Chaldee, of silver Persian saw,<span class="element"></l></span>
<span class="element"><l></span>Greeke brass, or
Roman iron, is in this one;<span class="element"></l></span>
<span class="element"><l></span>A worke t'out weare Seths pillars, bricke and
stone,<span class="element"></l></span>
<span class="element"><l></span>And (holy writs excepted) made to yeeld to none,<span class="element"></l></span>
<span class="element"></lg></span></div></div><p>Note that the <span class="gi"><l></span> element marks verse lines, not typographic lines: the original lineation of the first few lines above has not therefore been made explicit by this encoding, and may be lost. The <span class="gi"><lb></span> element described in section <a class="link_ptr" itemprop="ptr" href="#Simple-pln" title="Page and Line Numbers"><span class="headingNumber">3.4. </span>Page and Line Numbers</a> might additionally be used to mark typographic lines if so desired.</p><div class="p">Here is the end of a famous dramatic text, in which speeches and stage directions are marked: <div id="index.xml-egXML-d33e1639" class="pre egXML_valid"><span class="element"><sp></span>
<span class="element"><speaker></span>Vladimir<span class="element"></speaker></span>
<span class="element"><p></span>Pull on your trousers.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Estragon<span class="element"></speaker></span>
<span class="element"><p></span>You want me to pull off my trousers?<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Vladimir<span class="element"></speaker></span>
<span class="element"><p></span>Pull <span class="element"><emph></span>on<span class="element"></emph></span> your trousers.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Vladimir<span class="element"></speaker></span>
<span class="element"><p></span>
<span class="element"><stage></span>(realizing his trousers are down)<span class="element"></stage></span>.
True<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><stage></span>He pulls up his trousers<span class="element"></stage></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Vladimir<span class="element"></speaker></span>
<span class="element"><p></span>Well? Shall we go?<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Estragon<span class="element"></speaker></span>
<span class="element"><p></span>Yes, let's go.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><stage></span>They do not move.<span class="element"></stage></span></div></div><div class="p">Note that the <span class="gi"><stage></span> (stage direction) element can appear either within a speech or between speeches. The <span class="gi"><sp></span> ("speech") element contains, following an optional <span class="gi"><speaker></span> element indicating who is speaking, either paragraphs (if the speech is in prose) or verse lines or stanzas as in the next example. In this case, it is quite common to find that verse lines are split between speakers. The easiest way of encoding this is to use the <span xmlns="" class="att" itemprop="att">part</span> attribute to indicate that the lines so fragmented are incomplete : <div id="index.xml-egXML-d33e1694" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">Act</span>" <span class="attribute">n</span>="<span class="attributevalue">I</span>"></span>
<span class="element"><head></span>ACT I<span class="element"></head></span>
<span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">Scene</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>
<span class="element"><head></span>SCENE I<span class="element"></head></span>
<span class="element"><stage <span class="attribute">rendition</span>="<span class="attributevalue">#italic</span>"></span> Enter Barnardo and Francisco, two Sentinels, at several doors<span class="element"></stage></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Barn<span class="element"></speaker></span>
<span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">Y</span>"></span>Who's there?<span class="element"></l></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Fran<span class="element"></speaker></span>
<span class="element"><l></span>Nay, answer me. Stand and unfold yourself.<span class="element"></l></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Barn<span class="element"></speaker></span>
<span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">I</span>"></span>Long live the King!<span class="element"></l></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Fran<span class="element"></speaker></span>
<span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">M</span>"></span>Barnardo?<span class="element"></l></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Barn<span class="element"></speaker></span>
<span class="element"><l <span class="attribute">part</span>="<span class="attributevalue">F</span>"></span>He.<span class="element"></l></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Fran<span class="element"></speaker></span>
<span class="element"><l></span>You come most carefully upon your hour.<span class="element"></l></span>
<span class="element"></sp></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span>
<span class="element"></div></span></div></div><div class="p">The same mechanism may be applied to stanzas which are divided between two speakers: <div id="index.xml-egXML-d33e1736" class="pre egXML_valid"><span class="element"><div></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>First voice<span class="element"></speaker></span>
<span class="element"><lg <span class="attribute">type</span>="<span class="attributevalue">stanza</span>" <span class="attribute">part</span>="<span class="attributevalue">I</span>"></span>
<span class="element"><l></span>But why drives on that ship so fast<span class="element"></l></span>
<span class="element"><l></span>Withouten wave or wind?<span class="element"></l></span>
<span class="element"></lg></span>
<span class="element"></sp></span>
<span class="element"><sp></span>
<span class="element"><speaker></span>Second Voice<span class="element"></speaker></span>
<span class="element"><lg <span class="attribute">part</span>="<span class="attributevalue">F</span>"></span>
<span class="element"><l></span>The air is cut away before.<span class="element"></l></span>
<span class="element"><l></span>And closes from behind.<span class="element"></l></span>
<span class="element"></lg></span>
<span class="element"></sp></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span></div></div><div class="p">The <span class="gi"><sp></span> element can also be used for dialogue presented in a prose work as if it were drama, as in the next example, which also demonstrates the use of the <span xmlns="" class="att" itemprop="att">who</span> attribute to bear a code identifying the speaker of the piece of dialogue concerned: <div id="index.xml-egXML-d33e1764" class="pre egXML_valid"><span class="element"><div></span>
<span class="element"><sp <span class="attribute">who</span>="<span class="attributevalue">#OPI</span>"></span>
<span class="element"><speaker></span>The reverend Doctor Opimian<span class="element"></speaker></span>
<span class="element"><p></span>I do not think I have named a single unpresentable fish.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp <span class="attribute">who</span>="<span class="attributevalue">#GRM</span>"></span>
<span class="element"><speaker></span>Mr Gryll<span class="element"></speaker></span>
<span class="element"><p></span>Bream, Doctor: there is not much to be said for bream.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"><sp <span class="attribute">who</span>="<span class="attributevalue">#OPI</span>"></span>
<span class="element"><speaker></span>The Reverend Doctor Opimian<span class="element"></speaker></span>
<span class="element"><p></span>On the contrary, sir, I think there is much to be said for him. In the first
place....<span class="element"></p></span>
<span class="element"><p></span>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
will forbear.<span class="element"></p></span>
<span class="element"></sp></span>
<span class="element"></div></span></div> Here the <span xmlns="" class="att" itemprop="att">who</span> attribute values (<code itemprop="code">#OPI</code> etc.) are links, pointing to a list of the characters in the novel, each of which has an identifier: <div id="index.xml-egXML-d33e1791" class="pre egXML_valid"><span class="element"><list></span>
<span class="element"><head></span>Characters in the novel<span class="element"></head></span>
<span class="element"><item <span class="attribute">xml:id</span>="<span class="attributevalue">OPI</span>"></span>
<span class="element"><name></span>Dr Opimian<span class="element"></name></span> : named for the famous Roman fine wine<span class="element"></item></span>
<span class="element"><item <span class="attribute">xml:id</span>="<span class="attributevalue">GRM</span>"></span>
<span class="element"><name></span>Mr Gryll<span class="element"></name></span> : named for the mythical Gryllus, one of Ulysses'
sailors transformed by Circe into a pig, who argues that he was happier in that state than
as a man<span class="element"></item></span>
<span class="element"></list></span></div></div></div></div><div class="teidiv1" id="Simple-pln"><h2><span class="headingNumber">3.4. </span><span class="head" itemprop="head">Page and Line Numbers</span></h2><p>Page and line breaks etc. may be marked with the following elements. The <span class="gi"><pb></span> and <span class="gi"><lb></span> elements are special cases of the general class of <span class="term" itemprop="term">milestone</span> elements which mark reference points within a text. The generic <span class="gi"><milestone></span> element can mark any kind of reference point: for example, a column break, the start of a new kind of section not otherwise tagged, or in general any significant change in the text not marked by an XML element. Milestone elements have no content; whatever they have to say is contained in their attributes, most frequently a <span class="gi"><unit></span> attribute in combination with an <span xmlns="" class="att" itemprop="att">n</span> attribute. Their "empty" status is marked by the fact that their opening and closing tags are collapsed into one: the notation <milestone/> is a shortcut for <milestone></milestone>.</p><div class="p">The <span class="gi"><lb></span> and <span class="gi"><pb></span> elements are shortcuts or <span class="term" itemprop="term">syntactic sugar</span> for <div id="index.xml-egXML-d33e1843" class="pre egXML_valid"><span class="element"><milestone <span class="attribute">unit</span>="<span class="attributevalue">line</span>"/></span></div> or <div id="index.xml-egXML-d33e1846" class="pre egXML_valid"><span class="element"><milestone <span class="attribute">unit</span>="<span class="attributevalue">page</span>"/></span></div></div><div class="p">When working from a paginated original, it is often useful to record its pagination, if only to simplify later proof-reading. It is also useful for aligning an encoded text with a set of page images. The <span xmlns="" class="att" itemprop="att">facs</span> attribute helps with this alignment, which is not always straightforward. The numbering schemes of the printed pages and their image may, but often do not, correspond. The Text Creation Partnership transcriptions of Early English Books Online texts are a good example. The transcriptions were based on digital scans of double page microfilm images. Each double page image has an image number, which does not correspond to the page number, not to speak of the many printed pages that have no page numbers to begin with. Consider the following three examples: <div id="index.xml-egXML-d33e1854" class="pre egXML_valid"><span class="element"><pb <span class="attribute">facs</span>="<span class="attributevalue">page8</span>" <span class="attribute">n</span>="<span class="attributevalue">14</span>"/></span></div> <div id="index.xml-egXML-d33e1857" class="pre egXML_valid"><span class="element"><pb <span class="attribute">facs</span>="<span class="attributevalue">page8</span>" <span class="attribute">n</span>="<span class="attributevalue">15</span>"/></span></div> <div id="index.xml-egXML-d33e1860" class="pre egXML_valid"><span class="element"><pb <span class="attribute">facs</span>="<span class="attributevalue">page8</span>"/></span></div> In the first two examples, you have the printed page numbers for a double page image. The third example refers to a page image whose pages have no printed numbers. The value of the <span xmlns="" class="att" itemprop="att">facs</span> attribute could also be a complete URL to the site where the images are located, but if its first and longer part has been recorded once in the metadata, the simple image number will be sufficient to construct a link.</div><div class="p">The placement of <span class="gi"><pb></span> elements relative to their surrounding elements is a tricky matter of SHOULD. While TEI schema does not restrict their placement, it is recommended that milestone elements for lines, pages, or whatever should mark their beginning. Consider the case of a poem where two lines are split across different pages. All of the following encodings are valid TEI: <div id="index.xml-egXML-d33e1871" class="pre egXML_valid"><span class="element"><l></span>Mary had a little lamb<span class="element"></l></span>
<span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">13</span>" <span class="attribute">facs</span>="<span class="attributevalue">7</span>"/></span>
<span class="element"><l></span>Its fleece was white as snow<span class="element"></l></span></div> <div id="index.xml-egXML-d33e1878" class="pre egXML_valid"><span class="element"><l></span>Mary had a little lamb<span class="element"></l></span>
<span class="element"><l></span>
<span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">13</span>" <span class="attribute">facs</span>="<span class="attributevalue">7</span>"/></span>Its fleece was white as snow
<span class="element"></l></span></div> <div id="index.xml-egXML-d33e1885" class="pre egXML_valid"><span class="element"><l></span>Mary had a little lamb<span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">13</span>" <span class="attribute">facs</span>="<span class="attributevalue">7</span>"/></span>
<span class="element"></l></span>
<span class="element"><l></span>Its fleece was white as snow<span class="element"></l></span></div> While the third example is valid, it breaks the rule that you should put milestones at the beginning. The first and second examples observe that rule, but the first example is preferable on logical, aesthetic and practical grounds. The new page begins with the line rather than the first word in the line.The placement of the milestone before the line makes processing a little easier. It is also a little easier to read, and while XML documents are not created for readers, they are in principle readable, and greater readability is a marginal benefit.</div><p>Line breaks in prose are for the most part typographical accidents, and many encoders will rightly think of them as not worth their attention. But sometimes you do want to make the transcription mirror the physical layout of the written word on the page. This is especially true of manuscripts where the precise alignment of image and transcription makes things easier for the reader. </p><p>Digital transcriptions produced with optical character recognition (OCR) create special opportunities and challenges. They mimic the boundaries of characters, words, and lines on the page, and from their "whitespace XML" you can algorithmically infer much structural encoding, although the algorithmic constructs will always need some manual tweaking. OCR texts also require careful proofreading. This work will clearly benefit from the line-by-line correspondence of page image and transcription.</p><p>End-of-line (EOL) hyphens are a vexing problem for which there is no good solution. For many purposes it may be good enough to get rid of them tacitly. Given </p><pre class="pre_eg cdata">
I am not per-
suaded that EOL hyphens are worth keeping.
</pre><p> you can turn this into </p><pre class="pre_eg cdata">I am not persuaded that EOL hyphens are worth keeping.</pre><p> If you want to mark the line breaks of the printed source you could remove the EOL hyphen and keep the word on the line where it began, as in </p><pre class="pre_eg cdata">
I am not persuaded
<lb/> that EOL hyphens are worth keeping</pre><p> This is a perfectly acceptable solution, and few readers will object to it, especially if you document your practice in the relevant section of the header. The downside of both solutions is that you may accidentally delete what you think is an EOL hyphen when if fact it is a real hyphen. There are ways of protecting yourself against such an error. Check if that word occurs with a hyphen in line-medial position. If it does not, you are probably safe. In the unlikely event that it occurs in line-medial position both with and without a hyphen you would not know which it is in the line-terminal position. But relax: there is textual authority for whichever way you jump.</p><div class="p">Recording the presence of an EOL hyphen in a completely unambiguous manner turns out to be surprisingly difficult. First, while there are several Unicode characters that look like a hyphen, there is none that unambiguously declares: <span class="q" itemprop="q">‘I am an EOL hyphen’</span>. You can do something like <div id="index.xml-egXML-d33e1912" class="pre egXML_valid">I am not per-<span class="element"><lb/></span>suaded that EOL hyphens are worth keeping.</div> That leaves the status of your hyphen ambiguous but then it was ambiguous in the source as well. This solution (or other variants of it) makes it a little more difficult for the machine to figure out that 'per' and 'suaded' are a single token. In a cost benefit analysis you have to figure out whether the additional processing cost is worth the gain of typographical detail.</div><div class="note" itemprop="note" id="Note1"><span class="noteLabel">Note: </span><div class="p">If features such as pagination or lineation are marked for more than one edition, specify the edition in question using the <span xmlns="" class="att" itemprop="att">ed</span> attribute, and supply as many tags are necessary. For example, in the following passage we indicate where the page breaks occur in two different editions (ED1 and ED2) <div id="index.xml-egXML-d33e1930" class="pre egXML_valid"><span class="element"><p></span>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
explaining also why I had thus acted. Diana and <span class="element"><pb <span class="attribute">ed</span>="<span class="attributevalue">ED1</span>" <span class="attribute">n</span>="<span class="attributevalue">475</span>"/></span> Mary approved the step
unreservedly. Diana announced that she would <span class="element"><pb <span class="attribute">ed</span>="<span class="attributevalue">ED2</span>" <span class="attribute">n</span>="<span class="attributevalue">485</span>"/></span>just give me time to get
over the honeymoon, and then she would come and see me.<span class="element"></p></span></div></div></div></div><div class="teidiv1" id="Simple-hilites"><h2><span class="headingNumber">3.5. </span><span class="head" itemprop="head">Marking Highlighted Phrases</span></h2><div class="teidiv2" id="faces"><h3><span class="headingNumber">3.5.1. </span><span class="head" itemprop="head">Changes of Typeface, etc.</span></h3><p>Highlighted words or phrases are those made visibly different from the rest of the text, typically by a change of type font, handwriting style, ink colour etc., which is intended to draw the reader's attention to some associated change.</p><p>The global <span xmlns="" class="att" itemprop="att">rendition</span> attribute can be attached to any element, and used wherever necessary to specify details of the highlighting used for it in the source. For example, a heading rendered in bold might be tagged <code itemprop="code"><head rendition="#bold"></code>, and one in italic <code itemprop="code"><head rendition="#italic"></code>.</p><p>The values to be used for the <span xmlns="" class="att" itemprop="att">rendition</span> attribute are not specified by the TEI Guidelines, since they will depend entirely on the needs of the particular project. Some typical values might include <code itemprop="code">italic</code>, <code itemprop="code">bold</code> etc. for font variations; <code itemprop="code">center</code>, <code itemprop="code">right</code> etc. for alignment; <code itemprop="code">large</code>, <code itemprop="code">small</code> etc. for size; <code itemprop="code">smallcaps</code>, <code itemprop="code">allcaps</code> etc. for type variants and so on. </p><p>It is not always possible or desirable to interpret the reasons for such changes of rendering in a text. In such cases, the element <span class="gi"><hi></span> may be used to mark a sequence of highlighted text without making any claim as to its status. </p><div class="p">In the following example, the use of a distinct typeface for the subheading and for the included name are recorded but not interpreted: <div id="index.xml-egXML-d33e1999" class="pre egXML_valid"><span class="element"><p></span>
<span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#gothic</span>"></span>And this Indenture further
witnesseth<span class="element"></hi></span> that the said <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#italic</span>"></span>Walter Shandy<span class="element"></hi></span>, merchant, in
consideration of the said intended marriage ...
<span class="element"></p></span></div></div><p>Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available. </p><p>Some features (notably quotations {titles, and foreign words) may be found in a text either marked by highlighting, or with quotation marks. In either case, the element <span class="gi"><q></span> (as discussed in the following section) should be used. If the highlighting is to be recorded, use the global <span xmlns="" class="att" itemprop="att">rendition</span> attribute.</p><div class="p">As an example of the elements defined here, consider the following sentence: <span class="display" itemprop="q">On the one hand the <span class="it" itemprop="hi">Nibelungenlied</span> is associated with the new rise of romance of twelfth-century France, the <span class="it" itemprop="hi">romans d'antiquité</span>, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach.</span> Interpreting the role of the highlighting, the sentence might look like this: <div id="index.xml-egXML-d33e2040" class="pre egXML_valid"><span class="element"><p></span>On the one hand the <span class="element"><title></span>Nibelungenlied<span class="element"></title></span>
is associated with the new rise of romance of twelfth-century France, the <span class="element"><foreign></span>romans
d'antiquité<span class="element"></foreign></span>, the romances of Chrétien de Troyes, ...<span class="element"></p></span></div> Describing only the appearance of the original, it might look like this: <div id="index.xml-egXML-d33e2050" class="pre egXML_valid"><span class="element"><p></span>On the one hand the <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#italic</span>"></span>Nibelungenlied<span class="element"></hi></span> is associated with the new rise of romance of twelfth-century France,
the <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#italic</span>"></span>romans d'antiquité<span class="element"></hi></span>, the romances of Chrétien de Troyes,
...<span class="element"></p></span></div></div></div><div class="teidiv2" id="z635"><h3><span class="headingNumber">3.5.2. </span><span class="head" itemprop="head">Quotations and Related Features</span></h3><p>Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation. When possible, we recommend that the underlying feature be tagged, rather than the simple fact that quotation marks appear in the text, using the following elements: </p><div class="p">Here is a simple example of a quotation: <div id="index.xml-egXML-d33e2074" class="pre egXML_valid"><span class="element"><p></span>Few dictionary makers are likely to forget Dr. Johnson's description of the
lexicographer as <span class="element"><q></span>a harmless drudge.<span class="element"></q></span>
<span class="element"></p></span></div></div><p>To record how a quotation was printed (for example, <span class="term" itemprop="term">in-line</span> or set off as a <span class="hi" itemprop="hi">display</span> or <span class="hi" itemprop="hi">block quotation</span>), the <span xmlns="" class="att" itemprop="att">rendition</span> attribute should be used. This may also be used to indicate the kind of quotation marks used.</p><div class="p">Direct speech interrupted by a narrator can be represented simply by ending the quotation and beginning it again after the interruption, as in the following example: <div id="index.xml-egXML-d33e2096" class="pre egXML_valid"><span class="element"><p></span>
<span class="element"><q></span>Who-e debel you?<span class="element"></q></span> — he at last said —
<span class="element"><q></span>you no speak-e, damme, I kill-e.<span class="element"></q></span> And so saying, the lighted tomahawk began
flourishing about me in the dark.
<span class="element"></p></span></div> If it is important to convey the idea that the two <span class="gi"><q></span> elements together make up a single speech, the linking attributes <span xmlns="" class="att" itemprop="att">next</span> and <span xmlns="" class="att" itemprop="att">prev</span> may be used, as described in section <a class="link_ptr" itemprop="ptr" href="#xatts" title="Special kinds of Linking"><span class="headingNumber">3.7.3. </span>Special kinds of Linking</a>.</div><div class="p">Quotations may be accompanied by a reference to the source or speaker, using the <span xmlns="" class="att" itemprop="att">who</span> attribute, whether or not this is explicit in the text, as in the following example: <div id="index.xml-egXML-d33e2121" class="pre egXML_valid"><span class="element"><q <span class="attribute">who</span>="<span class="attributevalue">#Wilson</span>"></span>Spaulding, he came
down into the office just this day eight weeks with this very paper in his hand, and he
says:—<span class="element"><q <span class="attribute">who</span>="<span class="attributevalue">#Spaulding</span>"></span>I wish to the Lord, Mr. Wilson, that I was a red-headed
man.<span class="element"></q></span>
<span class="element"></q></span></div> This example also demonstrates how quotations may be embedded within other quotations: one speaker (Wilson) quotes another speaker (Spaulding).</div><p>The creator of the electronic text must decide whether quotation marks are replaced by the tags or whether the tags are added and the quotation marks kept. If the quotation marks are removed from the text, the <span xmlns="" class="att" itemprop="att">rend</span> attribute may be used to record the way in which they were rendered in the copy text.</p></div><div class="teidiv2" id="z636"><h3><span class="headingNumber">3.5.3. </span><span class="head" itemprop="head">Foreign Words or Expressions</span></h3><div class="p">Words phrases, or longer stretches of test that are not in the main language of the texts may be tagged as such in one of two ways. The global <span xmlns="" class="att" itemprop="att">xml:lang</span> attribute may be attached to any element to show that it uses some other language than that of the surrounding text. Where there is no applicable element, the element <span class="gi"><foreign></span> may be used, again using the <span xmlns="" class="att" itemprop="att">xml:lang</span> attribute. For example: <div id="index.xml-egXML-d33e2147" class="pre egXML_valid"><span class="element"><p></span>John has real <span class="element"><foreign <span class="attribute">xml:lang</span>="<span class="attributevalue">fr</span>"></span>savoir-faire<span class="element"></foreign></span>.<span class="element"></p></span>
<span class="element"><p></span>Have you read <span class="element"><title <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"></span>Die
Dreigroschenoper<span class="element"></title></span>?<span class="element"></p></span>
<span class="element"><div <span class="attribute">xml:lang</span>="<span class="attributevalue">la</span>"></span>{75 pages of Latin}<span class="element"></div></span></div></div><p>As these examples show, the <span class="gi"><foreign></span> element should not be used to tag foreign words if some other more specific element such as <span class="gi"><title></span>, or <span class="gi"><div></span> applies.</p><p>The codes used to identify languages, supplied on the <span xmlns="" class="att" itemprop="att">xml:lang</span> attribute, must be constructed in a particular way, and must conform to common Internet standards<span id="Note2_return"><a class="notelink" title="The relevant standard is Best Current Practice 47 (). The authoritative list of registered subtags is maintained by IANA and is available at . For a g…" href="#Note2"><sup>1</sup></a></span>, as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here: </p><div class="table"><table itemprop="table"><tr itemprop="row"><td>zh</td><td>Chinese</td><td>grc</td><td>Ancient Greek</td></tr><tr itemprop="row"><td>en</td><td>English</td><td>el</td><td>Greek</td></tr><tr itemprop="row"><td>enm</td><td>Middle English</td><td>ja</td><td>Japanese</td></tr><tr itemprop="row"><td>fr</td><td>French</td><td>la</td><td>Latin</td></tr><tr itemprop="row"><td>de</td><td>German</td><td>sa</td><td>Sanskrit</td></tr></table></div></div></div><div class="teidiv1" id="Simple-notes"><h2><span class="headingNumber">3.6. </span><span class="head" itemprop="head">Notes</span></h2><p>A note is any additional comment found in a text, marked in some way as being out of the main textual stream. It is a special and very common form of linking, because a note always targets some part of the text, whether implicitly or explicitly. All notes should be marked using the same tag, note, whether they appear as block notes in the main text area, at the foot of the page, at the end of the chapter or volume, in the margin, or in some other place: </p><p>Notes may be in a different hand or typeface, may be authorial or editorial, and may have been added later. Use <span xmlns="" class="att" itemprop="att">type</span> and <span xmlns="" class="att" itemprop="att">resp</span> attributes to distinguish between different kinds of notes or identify their authors.</p><p>A note is typically linked to a <span class="term" itemprop="term">point of attachment</span> that is represented by a siglum such as an alphanumerical or other character, typically in superscripted form. When encoding such a text, it is conventional to replace this siglum by the content of the annotation, duly marked up with a note element. This may not always be possible for example with marginal notes, which may not be anchored to an exact location. For ease of processing, it may be adequate to position marginal notes before the relevant paragraph or other element.</p><div class="p">An alternative method takes a "belt and suspenders" approach towards making sure that the relationship of a <span class="gi"><note></span> element to its point of attachment is always spelled out explicitly. In the following example, the source text marks the point of attachment with a superscripted "7". A failsafe way of encoding this may take the following form: <div id="index.xml-egXML-d33e2263" class="pre egXML_valid"><span class="element"><p></span>...some text <span class="element"><ref <span class="attribute">xml:id</span>="<span class="attributevalue">r7</span>" <span class="attribute">target</span>="<span class="attributevalue">n7</span>"
<span class="attribute">rendition</span>="<span class="attributevalue">#superscript</span>"></span>7<span class="element"></ref></span>
<span class="element"><note <span class="attribute">xml:id</span>="<span class="attributevalue">n7</span>" <span class="attribute">n</span>="<span class="attributevalue">7</span>"></span>a note about some text<span class="element"></note></span>
<span class="element"></p></span></div> This is a rather verbose representation of a simple note marker in a printed text. But it can usually be generated via a script, and it ensures that there is no uncertainty about the relationship between a <span class="gi"><ref></span> element in a stable location and a <span class="gi"><note></span> element whose physical location is a variable thing, whether in its original form, its encoding, or its display in some output of that encoding. With this notation it no longer matters whether you encode your notes in <span class="term" itemprop="term">inline</span> or in <span class="term" itemprop="term">standoff</span> manner, that is to say, keep them next to their place of attachment or in a separate place.</div><p>If the note lacks an explicit point of attachment in the text, which is often the case with marginal notes, you can use the pointer element <span class="gi"><ptr></span>, which differs from <span class="gi"><ref></span> in being empty.</p><div class="p">Marginal notes often are subject to different interpretations about their status. They are very common in Early Modern printed books, recede over the course of the 18th century, but are still an integral feature of Gibbon's <span class="titlem">Decline and Fall of the Roman Empire</span>. Many marginal notes are like footnotes, endnotes, or inline citations. A marginal note will very often provide the reference to an inline Biblical quotation. But some text in the margins is quite different in structure or purpose from notes that happen to be printed in the margin. In some Early Modern plays stage directions are routinely printed in the margin. <code itemprop="code"><stage place="margin"></code> would be the appropriate way of tagging them. Quite often the text in the margins operates more more like a summary or heading than a reference or explanatory note. In such cases <code itemprop="code"><label place="margin"></code> may be the most appropriate tag, but the boundary between heading and annotation may be blurry, as in the following case: <div id="index.xml-egXML-d33e2303" class="pre egXML_valid"><span class="element"><lg <span class="attribute">xml:id</span>="<span class="attributevalue">RAM609</span>"></span>
<span class="element"><note <span class="attribute">place</span>="<span class="attributevalue">margin</span>"></span>The
curse is finally expiated<span class="element"></note></span>
<span class="element"><l></span>And now this spell was snapt: once more<span class="element"></l></span>
<span class="element"><l></span>I viewed the ocean green,<span class="element"></l></span>
<span class="element"><l></span>And looked far forth, yet little saw<span class="element"></l></span>
<span class="element"><l></span>Of what had else been seen
—<span class="element"></l></span>
<span class="element"></lg></span></div> It is tempting to think of text in the margins as being notes by definition. On the other hand, if you ask yourself whether text in the margins provides additional information or is more like an abstract of what is to come, it may be quite easy to distinguish between <span class="gi"><note></span> and <span class="gi"><label></span> in most cases. As for stage directions in the margin, think of <code itemprop="code"><stage></code> as syntactic sugar for <code itemprop="code"><note type="stage"></code></div></div><div class="teidiv1" id="Simple-ptrs"><h2><span class="headingNumber">3.7. </span><span class="head" itemprop="head">Cross References and Links</span></h2><p>Explicit cross references or links from one point in a text to another in the same or another document may be encoded using the elements described in this section. Implicit links (such as the association between two parallel texts, or that between a text and its interpretation) may be encoded using the linking attributes discussed in section <a class="link_ptr" itemprop="ptr" href="#xatts" title="Special kinds of Linking"><span class="headingNumber">3.7.3. </span>Special kinds of Linking</a>.</p><div class="teidiv2" id="ptrs"><h3><span class="headingNumber">3.7.1. </span><span class="head" itemprop="head">Simple Cross References</span></h3><p>A cross reference from one point within a single document to another can be encoded by a tacit or explicit use of the <ref> element: </p><p>In the tacit use of the <ref> element you use it as as an <span class="term" itemprop="term">empty</span> element, simply marking a point from which a link is to be made, whereas in the explicit use the element may contain some text as well, typically identifying the target of the cross reference. You can use the element tacitly in a cross reference which is to be indicated by some non-verbal means such as a symbol or icon, or in an electronic text by a button. It is also useful in document production systems, where the formatter can generate the correct verbal form of the cross reference.</p><div class="p">The following two forms, for example, are logically equivalent : <div id="index.xml-egXML-d33e2351" class="pre egXML_valid">See especially <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#SEC12</span>"></span>section 12 on
page 34<span class="element"></ref></span>.</div> <div id="index.xml-egXML-d33e2357" class="pre egXML_valid">See especially <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#SEC12</span>"/></span>.</div> The value of the <span xmlns="" class="att" itemprop="att">target</span> attribute on either element may be the identifier of some other element within the current document. The passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a <span class="gi"><div></span> element: <div id="index.xml-egXML-d33e2368" class="pre egXML_valid"> ... see especially <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#SEC12</span>"/></span>. ...
<span class="element"><div <span class="attribute">xml:id</span>="<span class="attributevalue">SEC12</span>"></span>
<span class="element"><head></span>Concerning Identifiers<span class="element"></head></span>
<span class="comment"><!-- ... --></span>
<span class="element"></div></span></div></div><div class="p">Because the <span xmlns="" class="att" itemprop="att">xml:id</span> attribute is global, any element in a TEI document may be pointed to in this way. In the following example, a paragraph has been given an identifier so that it may be pointed at: <div id="index.xml-egXML-d33e2382" class="pre egXML_valid"> ... this is
discussed in <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#pspec</span>"></span>the paragraph on links<span class="element"></ref></span> ...
<span class="element"><p <span class="attribute">xml:id</span>="<span class="attributevalue">pspec</span>"></span>Links
may be made to any kind of element ...<span class="element"></p></span></div></div><p>Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an <span class="gi"><anchor></span> element at the appropriate spot. If the target is some sequence of words not otherwise tagged, the <span class="gi"><seg></span> element may be introduced to mark them. These two elements are described as follows: </p><div class="p">In the following (imaginary) example, <span class="gi"><ref></span> elements have been used to represent points in this text which are to be linked in some way to other parts of it; in the first case to a point, and in the second, to a sequence of words: <div id="index.xml-egXML-d33e2406" class="pre egXML_valid"> Returning to <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#ABCD</span>"></span>the point where I
dozed off<span class="element"></ref></span>, I noticed that <span class="element"><ref <span class="attribute">target</span>="<span class="attributevalue">#EFGH</span>"></span>three words<span class="element"></ref></span> had been circled in
red by a previous reader</div></div><div class="p">This encoding requires that elements with the specified identifiers (<code itemprop="code">ABCD</code> and <code itemprop="code">EFGH</code> in this example) are to be found somewhere else in the current document. Assuming that no element already exists to carry these identifiers, the <span class="gi"><anchor></span> and <span class="gi"><seg></span> elements may be used: <div id="index.xml-egXML-d33e2428" class="pre egXML_valid"> ....
<span class="element"><anchor <span class="attribute">type</span>="<span class="attributevalue">bookmark</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">ABCD</span>"/></span> .... ....<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">target</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">EFGH</span>"></span> ...
<span class="element"></seg></span> ...</div></div><p>The <span xmlns="" class="att" itemprop="att">type</span> attribute should be used (as above) to distinguish amongst different purposes for which these general purpose elements might be used in a text. Some other uses are discussed in section <a class="link_ptr" itemprop="ptr" href="#xatts" title="Special kinds of Linking"><span class="headingNumber">3.7.3. </span>Special kinds of Linking</a> below.</p></div><div class="teidiv2" id="xptrs"><h3><span class="headingNumber">3.7.2. </span><span class="head" itemprop="head">Pointing to other documents</span></h3><p>So far, we have shown how the <ref> element may be used for cross-references or links whose targets occur within the same document as their source. The element may also be used to refer to elements in any other XML document or resource, such as a document on the web, or a database component. This is possible because the value of the <span xmlns="" class="att" itemprop="att">target</span> attribute may be any valid <span class="term" itemprop="term">universal resource indicator</span> (URI)<span class="note" itemprop="note" id="Note3"><span class="noteLabel">Note: </span>A full definition of this term, defined by the W3C (the consortium which manages the development and maintenance of the World Wide Web), is beyond the scope of this tutorial: however, the most frequently encountered version of a URI is the familiar ‘URL’ used to indicate a web page, such as <code itemprop="code">http://www.tei-c.org/index.xml</code></span>.</p><p>A URI may reference a web page or just a part of one, for example <code itemprop="code">http://www.tei-c.org/index.xml#SEC2</code>. The hash sign indicates that what follows it is the identifier of an element to be located within the XML document identified by what precedes it: this example will therefore locate an element which has an <span xmlns="" class="att" itemprop="att">xml:id</span> attribute value of SEC2 within the document retrieved from <code itemprop="code">http://www.tei-c.org/index.xml</code>. In the examples we have discussed so far, the part to the left of the sharp sign has been omitted: this is understood to mean that the referenced element is to be located within the current document.</p><p>Parts of an XML document can be specified by means of other more sophisticated mechanisms using a special language called Xpath, also defined by the W3C. This is particularly useful where the elements to be linked to do not bear identifiers and must therefore be located by some other means. A full specification of the language is well beyond the scope of this document; here we provide only a flavour of its power. </p><p>In the XPath language, locations are defined as a series of <span class="term" itemprop="term">steps</span>, each one identifying some part of the document, often in terms of the locations identified by the previous step. For example, you would point to the third sentence of the second paragraph of chapter two by selecting chapter two in the first step, the second paragraph in the second step, and the third sentence in the last step. A step can be defined in terms of the document tree itself, using such concepts as parent, descendent, preceding, etc. or, more loosely, in terms of text patterns, word or character positions. This is not the document to describe in detail the powers of XPath. But unless you think of TEI encoding as just another form of typesetting—which emphatically is not its purpose—the decision to <span class="term" itemprop="term">encode</span> any part of a text this way rather than that way should always be guided by the sense that somebody at some time will want to <span class="term" itemprop="term">decode</span> or retrieve that part of the text for some purpose, about which you may not know very much at the point of encoding. XPath has been, and is likely to remain, the set of rules for <span class="term" itemprop="term">decoding</span> the <span class="term" itemprop="term">encoded</span>. A general understanding of what you can or cannot do with XPath is a useful thing to know in any encoding project.</p></div><div class="teidiv2" id="xatts"><h3><span class="headingNumber">3.7.3. </span><span class="head" itemprop="head">Special kinds of Linking</span></h3><p>The following special purpose <span class="term" itemprop="term">linking</span> attributes are defined for every element in the TEI Simple schema: </p><dl itemprop="list"><dt><span itemprop="label"><span xmlns="" class="att" itemprop="att">ana</span></span></dt><dd>links an element with its interpretation.</dd><dt><span itemprop="label"><span xmlns="" class="att" itemprop="att">corresp</span></span></dt><dd>links an element with one or more other corresponding elements.</dd><dt><span itemprop="label"><span xmlns="" class="att" itemprop="att">next</span></span></dt><dd>links an element to the next element in an aggregate.</dd><dt><span itemprop="label"><span xmlns="" class="att" itemprop="att">prev</span></span></dt><dd>links an element to the previous element in an aggregate.</dd></dl><div class="p">The <span xmlns="" class="att" itemprop="att">ana</span> (analysis) attribute is intended for use where a set of abstract analyses or interpretations have been defined somewhere within a document, as further discussed in section <a class="link_ptr" itemprop="ptr" href="#Simple-anal" title="Analysis"><span class="headingNumber">3.14. </span>Analysis</a>. For example, a linguistic analysis of the sentence <span class="q" itemprop="q">‘John loves Nancy’</span> might be encoded as follows: <div id="index.xml-egXML-d33e2543" class="pre egXML_valid"><span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">sentence</span>" <span class="attribute">ana</span>="<span class="attributevalue">SVO</span>"></span>
<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">lex</span>" <span class="attribute">ana</span>="<span class="attributevalue">#NP1</span>"></span>John<span class="element"></seg></span>
<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">lex</span>" <span class="attribute">ana</span>="<span class="attributevalue">#VVI</span>"></span>loves<span class="element"></seg></span>
<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">lex</span>" <span class="attribute">ana</span>="<span class="attributevalue">#NP1</span>"></span>Nancy<span class="element"></seg></span>
<span class="element"></seg></span></div> This encoding implies the existence elsewhere in the document of elements with identifiers SVO, NP1, and VV1 where the significance of these particular codes is explained. Note the use of the <span class="gi"><seg></span> element to mark particular components of the analysis, distinguished by the <span xmlns="" class="att" itemprop="att">type</span> attribute.</div><div class="p">The <span xmlns="" class="att" itemprop="att">corresp</span> (corresponding) attribute provides a simple way of representing some form of correspondence between two elements in a text. For example, in a multilingual text, it may be used to link translation equivalents, as in the following example <div id="index.xml-egXML-d33e2573" class="pre egXML_valid"><span class="element"><seg <span class="attribute">xml:lang</span>="<span class="attributevalue">fr</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">FR1</span>"
<span class="attribute">corresp</span>="<span class="attributevalue">#EN1</span>"></span>Jean
aime Nancy<span class="element"></seg></span>
<span class="element"><seg <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">EN1</span>"
<span class="attribute">corresp</span>="<span class="attributevalue">#FR1</span>"></span>John loves
Nancy<span class="element"></seg></span></div></div><div class="p">The same mechanism may be used for a variety of purposes. In the following example, it has been used to represent the correspondences between <span class="inline" itemprop="q">the show</span> and <span class="q" itemprop="q">‘Shirley’</span>, and between <span class="q" itemprop="q">‘NBC’</span> and <span class="q" itemprop="q">‘the network’</span>: <div id="index.xml-egXML-d33e2592" class="pre egXML_valid"><span class="element"><p></span>
<span class="element"><title <span class="attribute">xml:id</span>="<span class="attributevalue">shirley</span>"></span>Shirley<span class="element"></title></span>, which
made its Friday night debut only a month ago, was not listed on <span class="element"><name <span class="attribute">xml:id</span>="<span class="attributevalue">nbc</span>"></span>NBC<span class="element"></name></span>'s new schedule, although <span class="element"><seg <span class="attribute">xml:id</span>="<span class="attributevalue">network</span>" <span class="attribute">corresp</span>="<span class="attributevalue">#nbc</span>"></span>the network<span class="element"></seg></span>
says <span class="element"><seg <span class="attribute">xml:id</span>="<span class="attributevalue">show</span>" <span class="attribute">corresp</span>="<span class="attributevalue">#shirley</span>"></span>the show<span class="element"></seg></span> still is being
considered.
<span class="element"></p></span></div></div><div class="p">The <span xmlns="" class="att" itemprop="att">next</span> and <span xmlns="" class="att" itemprop="att">prev</span> attributes provide a simple way of linking together the components of a discontinuous element, as in the following example: <div id="index.xml-egXML-d33e2614" class="pre egXML_valid"><span class="element"><q <span class="attribute">xml:id</span>="<span class="attributevalue">Q1a</span>" <span class="attribute">next</span>="<span class="attributevalue">#Q1b</span>"></span>Who-e debel you?<span class="element"></q></span> —
he at last said — <span class="element"><q <span class="attribute">xml:id</span>="<span class="attributevalue">Q1b</span>" <span class="attribute">prev</span>="<span class="attributevalue">#Q1a</span>"></span>you no speak-e, damme, I kill-e.<span class="element"></q></span> And so
saying, the lighted tomahawk began flourishing about me in the dark.</div></div></div><div class="teidiv2" id="abseg"><h3><span class="headingNumber">3.7.4. </span><span class="head" itemprop="head"><span class="gi"><ab></span> and <span class="gi"><seg></span> as basic block and inline elements</span></h3><p>The <span class="gi"><seg></span> has been part of TEI from the very beginning. It is a purely formal <span class="term" itemprop="term">inline</span> element that operates at the level of words and phrases and below <span class="gi"><block></span> elements, such as paragraphs. You could say that other inline elements, such as <span class="gi"><hi></span>, <span class="gi"><w></span>, <span class="gi"><c></span>, <span class="gi"><foreign></span>, <span class="gi"><name></span>, etc. are merely <span class="term" itemprop="term">syntactic sugar </span> for <span class="gi"><seg></span> elements with appropriate type attributes such as <seg type="foreign">. The rules for its use are relatively straightforward. You may use it for any segmentation at the word or phrase level for which no explicit element exists. You should not use it where there is an appropriate element. <seg type="hi"> is valid but silly.</p><p>The <span class="gi"><ab></span> element was not part of the original element set, but was added in 1997. It is defined as an <span class="term" itemprop="term">anonymous block</span> that <span class="q" itemprop="q">‘contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3 Blocks, Segments, and Anchors]’</span>. Thus <span class="gi"><ab></span> is at one level opposed to seg (block vs. inline) and on another level to p (like <span class="gi"><p></span> but without its <span class="q" itemprop="q">‘semantic baggage’</span>).</p><p>By the time <span class="gi"><ab></span> was introduced encoders had been happily using <span class="gi"><p></span> not just for paragraphs but for any <span class="q" itemprop="q">‘chunk of prose’</span>, as one TEI veteran has put it. In practice TEI <span class="gi"><p></span> may not have been as different from HTML <span class="gi"><p></span> as it should have been. A lot of stuff inside <span class="gi"><p></span> has none of the semantic baggage associated with paragraphs.</p><p>That said, a recent survey (October 2015) produced a variety of use cases that may help encoders decide whether <span class="gi"><ab></span> or <span class="gi"><p></span> is more appropriate for a given <span class="q" itemprop="q">‘chunk of prose’</span>. The<span class="gi"><ab></span> element has been used for:</p><ul itemprop="list"><li class="item" itemprop="item">The canonical verses of the Bible, first produced in the Stephanus edition of 1571 </li><li class="item" itemprop="item">Greek inscriptions created in a world that had not yet invented paragraphs</li><li class="item" itemprop="item">Hieroglyphic texts, which have no semantic sense of a paragraph</li><li class="item" itemprop="item">Texts where the divisions into chunks are conventional (and differ between witnesses), and have been provided by medieval scribes</li><li class="item" itemprop="item">notebooks written by a contemporary artist, containing a lot of fragmentary and unstructured notes expressing thoughts and ideas (text and graphics) which are often just single words, unfinished sentences or sketches, and unrelated to previous or following entries.</li><li class="item" itemprop="item">rubrics or interspersed commentary in liturgical texts</li><li class="item" itemprop="item">The question and answer structure of catechisms as well as the alternating structures common in 17th century polemtical literature </li><li class="item" itemprop="item">table-like content that cannot be wrangled into a row/column structure and where <ab type="tabular" xml:space="preserve"> is the best you can do</li><li class="item" itemprop="item">machine-based encoding of PDF or OCR files</li></ul><p>Finally, <p> has been a useful element for identifying prose in dramatic dialogue, whether or not it is conducted in paragraphs, which it usually is not. Whether a speech in a play is in prose or verse is not always to tell. When Gertrude says <span class="q" itemprop="q">‘The lady does protest too much methinks’</span> her words happen to scan but are surrounded by prose.If you want avoid jumping off the fence you could use <ab>. The list could go on and certainly demonstrates that a lot of prose does not come in paragraphs with semantic baggage. The "Best Practices for TEI in Libraries" offers a somewhat off-beat use of <span class="gi"><ab></span> as an answer to the question how to encode asterisks or similar horizontally oriented symbols that mark some degree of separation between the stuff below and above. They recommend <ab type="typography"> * * * </ab> instead of <milestone type="separator" unit="undetermined" rend="stars"/> on the grounds that for many users this direct representation of asterisks will be more intuitive than representing them as attribute values.</p></div></div><div class="teidiv1" id="Simple-edit1"><h2><span class="headingNumber">3.8. </span><span class="head" itemprop="head">Editorial Interventions</span></h2><p>The process of encoding an electronic text has much in common with the process of editing a manuscript or other text for printed publication. In either case a conscientious editor may wish to record both the original state of the source and any editorial correction or other change made in it. The elements discussed in this and the next section provide some facilities for meeting these needs.</p><div class="teidiv2" id="index.xml-body.1_div.3_div.8_div.1"><h3><span class="headingNumber">3.8.1. </span><span class="head" itemprop="head">Correction and Normalization</span></h3><p>The following elements may be used to mark <span class="term" itemprop="term">correction</span>, that is editorial changes introduced where the editor believes the original to be erroneous: </p><p>The following elements may be used to mark <span class="term" itemprop="term">normalization</span>, that is editorial changes introduced for the sake of consistency or modernization of a text: </p><p>As an example, consider this extract from the quarto printing of Shakespeare's <span class="titlem">Henry V</span>. </p><pre class="pre_eg cdata">... for his nose was as sharp as a pen and a table of green feelds</pre><div class="p">A modern editor might wish to make a number of interventions here, specifically to modernize (or normalise) the Elizabethan spellings of <span class="mentioned" itemprop="mentioned">a'</span> and <span class="mentioned" itemprop="mentioned">feelds</span> for <span class="mentioned" itemprop="mentioned">he</span> and <span class="mentioned" itemprop="mentioned">fields</span> respectively. He or she might also want to emend <span class="mentioned" itemprop="mentioned">table</span> to <span class="mentioned" itemprop="mentioned">babbl'd</span>, following an editorial tradition that goes back to the 18th century Shakespearian scholar Lewis Theobald. The following encoding would then be appropriate: <div id="index.xml-egXML-d33e2799" class="pre egXML_valid">... for his nose was as sharp as
a pen and <span class="element"><reg></span>he<span class="element"></reg></span>
<span class="element"><corr <span class="attribute">resp</span>="<span class="attributevalue">#Theobald</span>"></span>babbl'd<span class="element"></corr></span> of green
<span class="element"><reg></span>fields<span class="element"></reg></span></div></div><div class="p">A more conservative or source-oriented editor, however, might want to retain the original, but at the same time signal that some of the readings it contains are in some sense anomalous: <div id="index.xml-egXML-d33e2810" class="pre egXML_valid">... for his nose was as sharp as a pen and
<span class="element"><orig></span>a<span class="element"></orig></span>
<span class="element"><sic></span>table<span class="element"></sic></span> of green
<span class="element"><orig></span>feelds<span class="element"></orig></span></div></div><div class="p">Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the <span class="gi"><choice></span> element. This allows an editor to mark where alternative readings are possible: <div id="index.xml-egXML-d33e2827" class="pre egXML_valid">... for his nose was as sharp as a pen and
<span class="element"><choice></span>
<span class="element"><orig></span>a<span class="element"></orig></span>
<span class="element"><reg></span>he<span class="element"></reg></span>
<span class="element"></choice></span>
<span class="element"><choice></span>
<span class="element"><corr <span class="attribute">resp</span>="<span class="attributevalue">#Theobald</span>"></span>babbl'd<span class="element"></corr></span>
<span class="element"><sic></span>table<span class="element"></sic></span>
<span class="element"></choice></span> of green
<span class="element"><choice></span>
<span class="element"><orig></span>feelds<span class="element"></orig></span>
<span class="element"><reg></span>fields<span class="element"></reg></span>
<span class="element"></choice></span></div></div></div><div class="teidiv2" id="Simple-edit2"><h3><span class="headingNumber">3.8.2. </span><span class="head" itemprop="head">Omissions, Deletions, and Additions</span></h3><p>In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena: </p><div class="p">These elements may be used to record changes made by an editor, by the transcriber, or (in manuscript material) by the author or scribe. For example, if the source for an electronic text read <span class="q" itemprop="q">‘The following elements are provided for for simple editorial interventions.’</span> then it might be felt desirable to correct the obvious error, but at the same time to record the deletion of the superfluous second <span class="mentioned" itemprop="mentioned">for</span>, thus: <div id="index.xml-egXML-d33e2864" class="pre egXML_valid">The following elements are provided for <span class="element"><del <span class="attribute">resp</span>="<span class="attributevalue">#LB</span>"></span>for<span class="element"></del></span> simple editorial interventions.</div> The attribute value <code itemprop="code">#LB</code> on the <span xmlns="" class="att" itemprop="att">resp</span> attribute is used to point to a fuller definition (typically in a <span class="gi"><respStmt></span> element) for the agency responsible for correcting the duplication of <span class="mentioned" itemprop="mentioned">for</span>.</div><div class="p">If the source read <span class="q" itemprop="q">‘The following elements provided for simple editorial interventions.’</span> (i.e. if the verb had been inadvertently dropped) then the corrected text might read: <div id="index.xml-egXML-d33e2888" class="pre egXML_valid">The following elements <span class="element"><add <span class="attribute">resp</span>="<span class="attributevalue">#LB</span>"></span>are<span class="element"></add></span> provided for simple editorial interventions.</div></div><div class="p">These elements are also used to record authorial changes in manuscripts. A manuscript in which the author has first written <span class="q" itemprop="q">‘How it galls me, what a galling shadow’</span>, then crossed out the word <span class="mentioned" itemprop="mentioned">galls</span> and inserted <span class="mentioned" itemprop="mentioned">dogs</span> might be encoded thus: <div id="index.xml-egXML-d33e2904" class="pre egXML_valid">How it <span class="element"><del <span class="attribute">hand</span>="<span class="attributevalue">#DHL</span>" <span class="attribute">type</span>="<span class="attributevalue">overstrike</span>"></span>galls<span class="element"></del></span>
<span class="element"><add <span class="attribute">hand</span>="<span class="attributevalue">#DHL</span>" <span class="attribute">place</span>="<span class="attributevalue">supralinear</span>"></span>dogs<span class="element"></add></span> me, what a galling shadow</div> Again, the code <code itemprop="code">#DHL</code> points to another location where more information about the hand concerned is to be found<span id="Note4_return"><a class="notelink" title="The full TEI provides a range of elements for encoding metadata about manuscript production and description, which are not however included in TEI Sim…" href="#Note4"><sup>2</sup></a></span>.</div><div class="p">Similarly, the <span class="gi"><unclear></span> and <span class="gi"><gap></span> elements may be used together to indicate the omission of illegible material; the following example also shows the use of <span class="gi"><add></span> for a conjectural emendation: <div id="index.xml-egXML-d33e2930" class="pre egXML_valid">One hundred
&amp; twenty good regulars joined to me <span class="element"><unclear></span>
<span class="element"><gap <span class="attribute">reason</span>="<span class="attributevalue">indecipherable</span>"/></span>
<span class="element"></unclear></span>
&amp; instantly, would aid me signally <span class="element"><add <span class="attribute">hand</span>="<span class="attributevalue">#ed</span>"></span>in?<span class="element"></add></span> an enterprise against
Wilmington.</div></div><div class="p">The <span class="gi"><del></span> element marks material which has been transcribed as part of the electronic text despite being marked as deleted, while <span class="gi"><gap></span> marks the location of material which is omitted from the electronic text, whether it is legible or not. A language corpus, for example, might omit long quotations in foreign languages: <div id="index.xml-egXML-d33e2946" class="pre egXML_valid"><span class="element"><p></span> ... An example of a list appearing in a fief
ledger of <span class="element"><name <span class="attribute">type</span>="<span class="attributevalue">place</span>"></span>Koldinghus<span class="element"></name></span>
<span class="element"><date></span>1611/12<span class="element"></date></span> is given below. It shows cash income from a sale of
honey.<span class="element"></p></span>
<span class="element"><gap></span>
<span class="element"><desc></span>quotation from ledger (in Danish)<span class="element"></desc></span>
<span class="element"></gap></span>
<span class="element"><p></span>A description of the
overall structure of the account is once again ... <span class="element"></p></span></div></div><div class="p">Other corpora (particular those constructed before the widespread use of scanners) systematically omit figures and mathematics: <div id="index.xml-egXML-d33e2961" class="pre egXML_valid"><span class="element"><p></span>At the bottom of your screen below the mode line is the <span class="element"><term></span>minibuffer<span class="element"></term></span>. This is
the area where Emacs echoes the commands you enter and where you specify filenames for Emacs
to find, values for search and replace, and so on. <span class="element"><gap <span class="attribute">reason</span>="<span class="attributevalue">graphic</span>"></span>
<span class="element"><desc></span>diagram of
Emacs screen<span class="element"></desc></span>
<span class="element"></gap></span>
<span class="element"></p></span></div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.8_div.3"><h3><span class="headingNumber">3.8.3. </span><span class="head" itemprop="head">Abbreviations and their Expansion</span></h3><p>Like names, dates, and numbers, abbreviations may be transcribed as they stand or expanded; they may be left unmarked, or encoded using the following elements: </p><div class="p">The <span class="gi"><abbr></span> element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon: <div id="index.xml-egXML-d33e2984" class="pre egXML_valid">We can sum up the above
discussion as follows: the identity of a <span class="element"><abbr></span>CC<span class="element"></abbr></span> is defined by that calibration of
values which motivates the elements of its <span class="element"><abbr></span>GSP<span class="element"></abbr></span>;</div> <div id="index.xml-egXML-d33e2993" class="pre egXML_valid">Every manufacturer of <span class="element"><abbr></span>3GL<span class="element"></abbr></span> or
<span class="element"><abbr></span>4GL<span class="element"></abbr></span> languages is currently nailing on <span class="element"><abbr></span>OOP<span class="element"></abbr></span> extensions</div></div><p>The <span xmlns="" class="att" itemprop="att">type</span> attribute may be used to distinguish types of abbreviation by their function.</p><div class="p">The <span class="gi"><expan></span> element is used to mark an expansion supplied by an encoder. This element is particularly useful in the transcription of manuscript materials. For example, the character p with a bar through its descender as a conventional representation for the word per is commonly encountered in Medieval European manuscripts. An encoder may choose to expand this as follows: <div id="index.xml-egXML-d33e3018" class="pre egXML_valid"><span class="element"><expan></span>per<span class="element"></expan></span></div></div><div class="p">To record both an abbreviation and its expansion, the <span class="gi"><choice></span> element mentioned above may be used to group the abbreviated form with its proposed expansion: <div id="index.xml-egXML-d33e3027" class="pre egXML_valid"><span class="element"><choice></span>
<span class="element"><abbr></span>wt<span class="element"></abbr></span>
<span class="element"><expan></span>with<span class="element"></expan></span>
<span class="element"></choice></span></div> For a fuller discussion of abbreviations and the intricacies of representing them consult the section on <a class="link_ref" itemprop="ref" href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHAB">Abbreviations and Expansion</a> in the <span class="titlem">Guidelines</span>.</div></div></div><div class="teidiv1" id="Simple-names"><h2><span class="headingNumber">3.9. </span><span class="head" itemprop="head">Names, Dates, and Numbers</span></h2><p>The TEI scheme defines elements for a large number of ‘data-like’ features which may appear almost anywhere within almost any kind of text. These features may be of particular interest in a range of disciplines; they all relate to objects external to the text itself, such as the names of persons and places, numbers and dates. They also pose particular problems for many natural language processing (NLP) applications because of the variety of ways in which they may be presented within a text. The elements described here, by making such features explicit, reduce the complexity of processing texts containing them.</p><div class="teidiv2" id="nomen"><h3><span class="headingNumber">3.9.1. </span><span class="head" itemprop="head">Names and Referring Strings</span></h3><p>A <span class="term" itemprop="term">referring string</span> is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings: </p><div class="p">The <span xmlns="" class="att" itemprop="att">type</span> attribute is used to distinguish amongst (for example) names of persons, places and organizations, where this is possible: <div id="index.xml-egXML-d33e3065" class="pre egXML_valid"><span class="element"><q></span>My dear <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>"></span>Mr. Bennet<span class="element"></rs></span>, <span class="element"></q></span>
said his lady to him one day,
<span class="element"><q></span>have you heard that <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">place</span>"></span>Netherfield Park<span class="element"></rs></span>
is let at last?<span class="element"></q></span></div> <div id="index.xml-egXML-d33e3078" class="pre egXML_valid">It being one of the principles of the <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">organization</span>"></span>Circumlocution Office<span class="element"></rs></span> never, on any account whatsoever, to give a
straightforward answer, <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>"></span>Mr Barnacle<span class="element"></rs></span> said,
<span class="element"><q></span>Possibly.<span class="element"></q></span></div></div><div class="p">As the following example shows, the <span class="gi"><rs></span> element may be used for any reference to a person, place, etc, not necessarily one in the form of a proper noun or noun phrase. <div id="index.xml-egXML-d33e3093" class="pre egXML_valid"><span class="element"><q></span>My dear <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>"></span>Mr. Bennet<span class="element"></rs></span>,<span class="element"></q></span>
said <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>"></span>his lady<span class="element"></rs></span> to him one day...</div></div><p>The <span class="gi"><name></span> element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the <span class="gi"><rs></span> element, or nested within it if a referring string contains a mixture of common and proper nouns.</p><p>Simply tagging something as a name is rarely enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name prefixes such as <span class="mentioned" itemprop="mentioned">van</span> or <span class="mentioned" itemprop="mentioned">de la</span>, may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.</p><div class="p">The <span xmlns="" class="att" itemprop="att">key</span> attribute provides an alternative normalized identifier for the object being named, like a database record key. It may thus be useful as a means of gathering together all references to the same individual or location scattered throughout a document: <div id="index.xml-egXML-d33e3124" class="pre egXML_valid"><span class="element"><q></span>My dear <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>" <span class="attribute">key</span>="<span class="attributevalue">BENM1</span>"></span>Mr.
Bennet<span class="element"></rs></span>, <span class="element"></q></span> said <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">person</span>" <span class="attribute">key</span>="<span class="attributevalue">BENM2</span>"></span>his lady<span class="element"></rs></span> to him one day,
<span class="element"><q></span>have
you heard that <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">place</span>" <span class="attribute">key</span>="<span class="attributevalue">NETP1</span>"></span>Netherfield Park<span class="element"></rs></span> is let at
last?<span class="element"></q></span></div></div><div class="p">This use should be distinguished from the case of the <span class="gi"><reg></span> (regularization) element, which provides a means of marking the standard form of a referencing string as demonstrated below: <div id="index.xml-egXML-d33e3144" class="pre egXML_valid"><span class="element"><name <span class="attribute">type</span>="<span class="attributevalue">person</span>" <span class="attribute">key</span>="<span class="attributevalue">WADLM1</span>"></span>
<span class="element"><choice></span>
<span class="element"><sic></span>Walter de la Mare<span class="element"></sic></span>
<span class="element"><reg></span>de la Mare, Walter<span class="element"></reg></span>
<span class="element"></choice></span>
<span class="element"></name></span> was
born at <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">Ch1</span>" <span class="attribute">type</span>="<span class="attributevalue">place</span>"></span>Charlton<span class="element"></name></span>, in <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">KT1</span>" <span class="attribute">type</span>="<span class="attributevalue">county</span>"></span>Kent<span class="element"></name></span>, in 1873.</div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.9_div.2"><h3><span class="headingNumber">3.9.2. </span><span class="head" itemprop="head">Dates and Times</span></h3><p>Tags for the more detailed encoding of times and dates include the following: </p><div class="p">These elements have a number of attributes which can be used to provide normalised versions of their values. The <span xmlns="" class="att" itemprop="att">when</span> attribute specifies a normalized form for the date or time, using one of the standard formats defined by ISO 8601. Partial dates or times (e.g. <span class="q" itemprop="q">‘1990’</span>, <span class="q" itemprop="q">‘September 1990’</span>, <span class="q" itemprop="q">‘twelvish’</span>) can be expressed by omitting a part of the value supplied, as in the following examples: <div id="index.xml-egXML-d33e3185" class="pre egXML_valid"><span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1980-02-21</span>"></span>21
Feb 1980<span class="element"></date></span>
<span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1990</span>"></span>1990<span class="element"></date></span>
<span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1990-09</span>"></span>September 1990<span class="element"></date></span>
<span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">--09</span>"></span>September<span class="element"></date></span>
<span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">2001-09-11T12:48:00</span>"></span>Sept 11th, 12 minutes before 9
am<span class="element"></date></span></div>Note in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the <span class="gi"><time></span> element.</div><div class="p"><div id="index.xml-egXML-d33e3202" class="pre egXML_valid">Given on the <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1977-06-12</span>"></span>Twelfth
Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the
Republic the Two Hundredth and first and of the University the Eighty-Sixth.<span class="element"></date></span></div> <div id="index.xml-egXML-d33e3207" class="pre egXML_valid"><span class="element"><l></span>specially when it's nine below zero<span class="element"></l></span>
<span class="element"><l></span>and <span class="element"><time <span class="attribute">when</span>="<span class="attributevalue">15:00:00</span>"></span>three o'clock in the afternoon<span class="element"></time></span>
<span class="element"></l></span></div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.9_div.3"><h3><span class="headingNumber">3.9.3. </span><span class="head" itemprop="head">Numbers </span></h3><p>Numbers can be written with either letters or digits (<code itemprop="code">twenty-one</code>, <code itemprop="code">xxi</code>, and <code itemprop="code">21</code>) and their presentation is language-dependent (e.g. English <span class="mentioned" itemprop="mentioned">5th</span> becomes Greek <span class="mentioned" itemprop="mentioned">5.</span>; English <span class="mentioned" itemprop="mentioned">123,456.78</span> equals French <span class="mentioned" itemprop="mentioned">123.456,78</span>). In natural-language processing or machine-translation applications, it is often helpful to distinguish them from other, more ‘lexical’ parts of the text. In other applications, the ability to record a number's value in standard notation is important. The <span class="gi"><num></span> element provides this possibility: </p><div class="p">For example: <div id="index.xml-egXML-d33e3253" class="pre egXML_valid"><span class="element"><num <span class="attribute">value</span>="<span class="attributevalue">33</span>"></span>xxxiii<span class="element"></num></span>
<span class="element"><num <span class="attribute">type</span>="<span class="attributevalue">cardinal</span>" <span class="attribute">value</span>="<span class="attributevalue">21</span>"></span>twenty-one<span class="element"></num></span>
<span class="element"><num <span class="attribute">type</span>="<span class="attributevalue">percentage</span>" <span class="attribute">value</span>="<span class="attributevalue">10</span>"></span>ten percent<span class="element"></num></span>
<span class="element"><num <span class="attribute">type</span>="<span class="attributevalue">percentage</span>" <span class="attribute">value</span>="<span class="attributevalue">10</span>"></span>10%<span class="element"></num></span>
<span class="element"><num <span class="attribute">type</span>="<span class="attributevalue">ordinal</span>" <span class="attribute">value</span>="<span class="attributevalue">5</span>"></span>5th<span class="element"></num></span></div></div></div></div><div class="teidiv1" id="Simple-lists"><h2><span class="headingNumber">3.10. </span><span class="head" itemprop="head">Lists</span></h2><p>The element <span class="gi"><list></span> is used to mark any kind of <span class="term" itemprop="term">list</span>. A list is a sequence of text items, which may be numbered, bulleted, or arranged as a glossary list. Each item may be preceded by an item label (in a glossary list, this label is the term being defined): </p><div class="p">Individual list items are tagged with <span class="gi"><item></span>. The first <span class="gi"><item></span> may optionally be preceded by a <span class="gi"><head></span>, which gives a heading for the list. The numbering of a list may be omitted, indicated using the <span xmlns="" class="att" itemprop="att">n</span> attribute on each item, or (rarely) tagged as content using the <span class="gi"><label></span> element. The following are all thus equivalent: <div id="index.xml-egXML-d33e3298" class="pre egXML_valid"><span class="element"><list></span>
<span class="element"><head></span>A short list<span class="element"></head></span>
<span class="element"><item></span>First item in list.<span class="element"></item></span>
<span class="element"><item></span>Second item in list.<span class="element"></item></span>
<span class="element"><item></span>Third item in list.<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"><list></span>
<span class="element"><head></span>A short list<span class="element"></head></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>First item in list.<span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">2</span>"></span>Second item in list.<span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">3</span>"></span>Third item in list.<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"><list></span>
<span class="element"><head></span>A short list<span class="element"></head></span>
<span class="element"><label></span>1<span class="element"></label></span>
<span class="element"><item></span>First item in list.<span class="element"></item></span>
<span class="element"><label></span>2<span class="element"></label></span>
<span class="element"><item></span>Second item in list.<span class="element"></item></span>
<span class="element"><label></span>3<span class="element"></label></span>
<span class="element"><item></span>Third item in list.<span class="element"></item></span>
<span class="element"></list></span></div> The styles should not be mixed in the same list.</div><div class="p">A simple two-column table may be treated as a <span class="term" itemprop="term">glossary list</span>, tagged <code itemprop="code"><list type="gloss"></code>. Here, each item comprises a <span class="term" itemprop="term">term</span> and a <span class="term" itemprop="term">gloss</span>, marked with <span class="gi"><label></span> and <span class="gi"><item></span> respectively. These correspond to the elements <span class="gi"><term></span> and <span class="gi"><gloss></span>, which can occur anywhere in prose text. <div id="index.xml-egXML-d33e3360" class="pre egXML_valid"><span class="element"><list <span class="attribute">type</span>="<span class="attributevalue">gloss</span>"></span>
<span class="element"><head></span>Vocabulary<span class="element"></head></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>nu<span class="element"></label></span>
<span class="element"><item></span>now<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>lhude<span class="element"></label></span>
<span class="element"><item></span>loudly<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>bloweth<span class="element"></label></span>
<span class="element"><item></span>blooms<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>med<span class="element"></label></span>
<span class="element"><item></span>meadow<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>wude<span class="element"></label></span>
<span class="element"><item></span>wood<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>awe<span class="element"></label></span>
<span class="element"><item></span>ewe<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>lhouth<span class="element"></label></span>
<span class="element"><item></span>lows<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>sterteth<span class="element"></label></span>
<span class="element"><item></span>bounds, frisks<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>verteth<span class="element"></label></span>
<span class="element"><item <span class="attribute">xml:lang</span>="<span class="attributevalue">la</span>"></span>pedit<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>murie<span class="element"></label></span>
<span class="element"><item></span>merrily<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>swik<span class="element"></label></span>
<span class="element"><item></span>cease<span class="element"></item></span>
<span class="element"><label <span class="attribute">xml:lang</span>="<span class="attributevalue">enm</span>"></span>naver<span class="element"></label></span>
<span class="element"><item></span>never<span class="element"></item></span>
<span class="element"></list></span></div></div><p>Where the internal structure of a list item is more complex, it may be preferable to regard the list as a <span class="term" itemprop="term">table</span>, for which special-purpose tagging is defined below (<a class="link_ptr" itemprop="ptr" href="#Simple-tables" title="Tables"><span class="headingNumber">3.12. </span>Tables</a>).</p><div class="p">Lists of whatever kind can, of course, nest within list items to any depth required. Here, for example, a glossary list contains two items, each of which is itself a simple list: <div id="index.xml-egXML-d33e3423" class="pre egXML_valid"><span class="element"><list <span class="attribute">type</span>="<span class="attributevalue">gloss</span>"></span>
<span class="element"><label></span>EVIL<span class="element"></label></span>
<span class="element"><item></span>
<span class="element"><list <span class="attribute">type</span>="<span class="attributevalue">simple</span>"></span>
<span class="element"><item></span>I am cast upon a horrible desolate island, void of all hope of recovery.<span class="element"></item></span>
<span class="element"><item></span>I am singled out and separated as it were from all the world to be miserable.<span class="element"></item></span>
<span class="element"><item></span>I am divided from mankind — a solitaire; one banished from human society.<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"></item></span>
<span class="element"><label></span>GOOD<span class="element"></label></span>
<span class="element"><item></span>
<span class="element"><list <span class="attribute">type</span>="<span class="attributevalue">simple</span>"></span>
<span class="element"><item></span>But I am alive; and not drowned, as all my ship's company were.<span class="element"></item></span>
<span class="element"><item></span>But I am singled out, too, from all the ship's crew, to be spared from
death...<span class="element"></item></span>
<span class="element"><item></span>But I am not starved, and perishing on a barren place, affording no
sustenances....<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"></item></span>
<span class="element"></list></span></div></div><div class="p">A list need not necessarily be displayed in list format. For example, <div id="index.xml-egXML-d33e3447" class="pre egXML_valid"><span class="element"><p></span>On those remote pages it is written that animals
are divided into <span class="element"><list <span class="attribute">rendition</span>="<span class="attributevalue">run-on</span>"></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">a</span>"></span>those that belong to the Emperor,<span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">b</span>"></span> embalmed ones, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">c</span>"></span> those that are trained, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">d</span>"></span> suckling pigs, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">e</span>"></span> mermaids, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">f</span>"></span> fabulous ones, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">g</span>"></span> stray dogs, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">h</span>"></span> those that are included in this classification, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">i</span>"></span> those that tremble as if they were mad, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">j</span>"></span> innumerable ones, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">k</span>"></span> those drawn with a very fine camel's-hair brush, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">l</span>"></span> others, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">m</span>"></span> those that have just broken a flower vase, <span class="element"></item></span>
<span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">n</span>"></span> those that resemble flies from a distance.<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"></p></span></div></div><p>Lists of bibliographic items should be tagged using the <span class="gi"><listBibl></span> element, described in the next section.</p></div><div class="teidiv1" id="Simple-bibls"><h2><span class="headingNumber">3.11. </span><span class="head" itemprop="head">Bibliographic Citations</span></h2><p>It is often useful to distinguish bibliographic citations where they occur within texts being transcribed for research, if only so that they will be properly formatted when the text is printed out. The element <span class="gi"><bibl></span> is provided for this purpose. Where the components of a bibliographic reference are to be distinguished, the following elements may be used as appropriate. It is generally useful to mark at least those parts (such as the titles of articles, books, and journals) which will need special formatting. The other elements are provided for cases where particular interest attaches to such details. </p><div class="p">For example, the following editorial note might be transcribed as shown: <span class="" itemprop="q">He was a member of Parliament for Warwickshire in 1445, and died March 14, 1470 (according to Kittredge, <span class="titlem">Harvard Studies</span> 5. 88ff).</span> <div id="index.xml-egXML-d33e3511" class="pre egXML_valid">He was a member of Parliament for Warwickshire
in 1445, and died March 14, 1470 (according to <span class="element"><bibl></span>
<span class="element"><author></span>Kittredge<span class="element"></author></span>,
<span class="element"><title></span>Harvard Studies<span class="element"></title></span> 5. 88ff
<span class="element"></bibl></span>).</div></div><p>For lists of bibliographic citations, the <span class="gi"><listBibl></span> element should be used; it may contain a series of <span class="gi"><bibl></span> elements.</p></div><div class="teidiv1" id="Simple-tables"><h2><span class="headingNumber">3.12. </span><span class="head" itemprop="head">Tables</span></h2><p>Tables represent a challenge for any text processing system, but simple tables, at least, appear in so many texts that even in the simplified TEI tag set presented here, markup for tables is necessary. The following elements are provided for this purpose: </p><div class="p">For example, Defoe uses mortality tables like the following in the <span class="titlem">Journal of the Plague Year</span> to show the rise and ebb of the epidemic:<div id="index.xml-egXML-d33e3543" class="pre egXML_valid"><span class="element"><p></span>It was indeed coming on amain, for the burials
that same week were in the next adjoining parishes thus:— <span class="element"><table <span class="attribute">rows</span>="<span class="attributevalue">5</span>" <span class="attribute">cols</span>="<span class="attributevalue">4</span>"></span>
<span class="element"><row <span class="attribute">role</span>="<span class="attributevalue">data</span>"></span>
<span class="element"><cell <span class="attribute">role</span>="<span class="attributevalue">label</span>"></span>St. Leonard's, Shoreditch<span class="element"></cell></span>
<span class="element"><cell></span>64<span class="element"></cell></span>
<span class="element"><cell></span>84<span class="element"></cell></span>
<span class="element"><cell></span>119<span class="element"></cell></span>
<span class="element"></row></span>
<span class="element"><row <span class="attribute">role</span>="<span class="attributevalue">data</span>"></span>
<span class="element"><cell <span class="attribute">role</span>="<span class="attributevalue">label</span>"></span>St. Botolph's, Bishopsgate<span class="element"></cell></span>
<span class="element"><cell></span>65<span class="element"></cell></span>
<span class="element"><cell></span>105<span class="element"></cell></span>
<span class="element"><cell></span>116<span class="element"></cell></span>
<span class="element"></row></span>
<span class="element"><row <span class="attribute">role</span>="<span class="attributevalue">data</span>"></span>
<span class="element"><cell <span class="attribute">role</span>="<span class="attributevalue">label</span>"></span>St. Giles's, Cripplegate<span class="element"></cell></span>
<span class="element"><cell></span>213<span class="element"></cell></span>
<span class="element"><cell></span>421<span class="element"></cell></span>
<span class="element"><cell></span>554<span class="element"></cell></span>
<span class="element"></row></span>
<span class="element"></table></span>
<span class="element"></p></span>
<span class="element"><p></span>This shutting up of houses was at first counted a very cruel and unchristian
method, and the poor people so confined made bitter lamentations. ... <span class="element"></p></span></div></div></div><div class="teidiv1" id="Simple-figs"><h2><span class="headingNumber">3.13. </span><span class="head" itemprop="head">Figures and Graphics</span></h2><p>Not all the components of a document are necessarily textual. The most straightforward text will often contain diagrams or illustrations, to say nothing of documents in which image and text are inextricably intertwined, or electronic resources in which the two are complementary. </p><p>The encoder may simply record the presence of a graphic within the text, possibly with a brief description of its content, and may also provide a link to a digitized version of the graphic, using the following elements: </p><p>Any textual information accompanying the graphic, such as a heading and/or caption, may be included within the <span class="gi"><figure></span> element itself, in a <span class="gi"><head></span> and one or more <span class="gi"><p></span> elements, as also may any text appearing within the graphic itself. It is strongly recommended that a prose description of the image be supplied, as the content of a <span class="gi"><figDesc></span> element, for the use of applications which are not able to render the graphic, and to render the document accessible to vision-impaired readers. (Such text is not normally considered part of the document proper.)</p><div class="p">The simplest use for these elements is to mark the position of a graphic and provide a link to it, as in this example; <div id="index.xml-egXML-d33e3603" class="pre egXML_valid"><span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">412</span>"/></span>
<span class="element"><figure></span>
<span class="element"><graphic <span class="attribute">url</span>="<span class="attributevalue">images/p412fig.png</span>"/></span>
<span class="element"></figure></span>
<span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">413</span>"/></span></div> This indicates that the graphic contained by the file <span class="ident">p412fig.png</span> appears between pages 412 and 413.</div><div class="p">The <span class="gi"><graphic></span> element can appear anywhere that textual content is permitted, within but not between paragraphs or headings. In the following example, the encoder has decided to treat a specific printer's ornament as a heading: <div id="index.xml-egXML-d33e3617" class="pre egXML_valid"><span class="element"><head></span>
<span class="element"><graphic <span class="attribute">url</span>="<span class="attributevalue">http://www.iath.virginia.edu/gants/Ornaments/Heads/hp-ral02.gif</span>"/></span>
<span class="element"></head></span></div></div><div class="p">More usually, a graphic will have at the least an identifying title, which may be encoded using the <span class="gi"><head></span> element, or a number of figures may be grouped together in a particular structure. It is also often convenient to include a brief description of the image. The <span class="gi"><figure></span> element provides a means of wrapping one or more such elements together as a kind of graphic ‘block’: <div id="index.xml-egXML-d33e3632" class="pre egXML_valid"><span class="element"><figure></span>
<span class="element"><graphic <span class="attribute">url</span>="<span class="attributevalue">images/fessipic.png</span>"/></span>
<span class="element"><head></span>Mr Fezziwig's Ball<span class="element"></head></span>
<span class="element"><figDesc></span>A Cruikshank
engraving showing Mr Fezziwig leading a group of revellers.<span class="element"></figDesc></span>
<span class="element"></figure></span></div></div><div class="p">These cases should be carefully distinguished from the case where an encoded text is complemented by a collection of digital images, maintained as a distinct resource. The <span xmlns="" class="att" itemprop="att">facs</span> attribute may be used to associate any element in an encoded text with a digital facsimile of it. In the simple case where only page images are available, the <span xmlns="" class="att" itemprop="att">facs</span> attribute on the <span class="gi"><pb></span> element may be used to associate each image with an appropriate point in the text: <div id="index.xml-egXML-d33e3650" class="pre egXML_valid"><span class="element"><text></span>
<span class="element"><pb <span class="attribute">facs</span>="<span class="attributevalue">page1.png</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>"/></span>
<span class="comment"><!-- text contained on page 1 is encoded here --></span>
<span class="element"><pb <span class="attribute">facs</span>="<span class="attributevalue">page2.png</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>"/></span>
<span class="comment"><!-- text contained on page 2 is encoded here --></span>
<span class="element"></text></span></div> This method is only appropriate in the simple case where each digital image file <span class="ident">page1.png</span> etc. corresponds with a single transcribed and encoded page. If more detailed alignment of image and transcription is required, for example because the image files actually represent double page spreads, more sophisticated mechanisms are provided in the full TEI Guidelines.</div></div><div class="teidiv1" id="Simple-anal"><h2><span class="headingNumber">3.14. </span><span class="head" itemprop="head">Analysis</span></h2><div class="teidiv2" id="index.xml-body.1_div.3_div.14_div.1"><h3><span class="headingNumber">3.14.1. </span><span class="head" itemprop="head">Orthographic Sentences</span></h3><p>Interpretation typically ranges across the whole of a text, with no particular respect to other structural units. A useful preliminary to intensive interpretation is therefore to segment the text into discrete and identifiable units, each of which can then bear a label for use as a sort of ‘canonical reference’. To facilitate such uses, these units may not cross each other, nor nest within each other. They may conveniently be represented using the following element: </p><div class="p">As the name suggests, the <span class="gi"><s></span> element is most commonly used (in linguistic applications at least) for marking <span class="term" itemprop="term">orthographic sentences</span>, that is, units defined by orthographic features such as punctuation. For example, the passage from <span class="titlem">Jane Eyre</span> discussed earlier might be divided into s-units as follows:<div id="index.xml-egXML-d33e3684" class="pre egXML_valid"><span class="element"><pb <span class="attribute">n</span>="<span class="attributevalue">474</span>"/></span>
<span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">chapter</span>" <span class="attribute">n</span>="<span class="attributevalue">38</span>"></span>
<span class="element"><p></span>
<span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">001</span>"></span>Reader, I married him.<span class="element"></s></span>
<span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">002</span>"></span>A quiet wedding we had:<span class="element"></s></span>
<span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">003</span>"></span>he
and I, the parson and clerk, were alone present.<span class="element"></s></span>
<span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">004</span>"></span>When we got back from
church, I went into the kitchen of the manor-house, where Mary was cooking the dinner, and
John cleaning the knives, and I said —<span class="element"></s></span>
<span class="element"></p></span>
<span class="element"><p></span>
<span class="element"><q></span>
<span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">005</span>"></span>Mary, I have been married to Mr Rochester this morning.<span class="element"></s></span>
<span class="element"></q></span> ... <span class="element"></p></span>
<span class="element"></div></span></div> Note that <span class="gi"><s></span> elements cannot nest: the beginning of one <span class="gi"><s></span> element implies that the previous one has finished. When s-units are tagged as shown above, it is advisable to tag the entire text end-to-end, so that every word in the text being analysed will be contained by exactly one <span class="gi"><s></span> element, whose identifier can then be used to specify a unique reference for it. If the identifiers used are unique within the document, then the <span xmlns="" class="att" itemprop="att">xml:id</span> attribute might be used in preference to the <span xmlns="" class="att" itemprop="att">n</span> attribute used in the above example.</div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.14_div.2"><h3><span class="headingNumber">3.14.2. </span><span class="head" itemprop="head">Words and punctuation</span></h3><p>Tokenization, that is, the identification of lexical or non-lexical tokens within a text, is a very common requirement for all kinds of textual analysis, and not an entirely trivial one. The decision as to whether, for example, <span class="q" itemprop="q">‘can't’</span> in English or <span class="q" itemprop="q">‘du’</span> in French should be treated as one word or two is not simple. Consequently it is often useful to make explicit the preferred tokenization in a marked up text. The following elements are available for this purpose: </p><div class="p">For example, the output from a part of speech tagger might be recorded in TEI Lite as follows: <div id="index.xml-egXML-d33e3734" class="pre egXML_valid"><span class="element"><s <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#NP0</span>"></span>Marley<span class="element"></w></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#VBD</span>"></span>was<span class="element"></w></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#AJ0</span>"></span>dead<span class="element"></w></span>
<span class="element"><pc></span>:<span class="element"></pc></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#TO0</span>"></span>to<span class="element"></w></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#VBB</span>"></span>begin<span class="element"></w></span>
<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#PRP</span>"></span>with<span class="element"></w></span>
<span class="element"><pc></span>. <span class="element"></pc></span>
<span class="element"></s></span></div></div><div class="p">In this example, each word has been decorated with an automatically generated part of speech code, using the <span xmlns="" class="att" itemprop="att">ana</span> attribute discussed in section <a class="link_ptr" itemprop="ptr" href="#xatts" title="Special kinds of Linking"><span class="headingNumber">3.7.3. </span>Special kinds of Linking</a> above. The <span class="gi"><w></span> also provides for each word to be associated with a root form or lemma, either explicitly using the <span xmlns="" class="att" itemprop="att">lemma</span> attribute, or by reference, using the <span xmlns="" class="att" itemprop="att">lemmaRef</span> attribute, as in this example: <div id="index.xml-egXML-d33e3770" class="pre egXML_valid">...<span class="element"><w <span class="attribute">ana</span>="<span class="attributevalue">#VBD</span>" <span class="attribute">lemma</span>="<span class="attributevalue">be</span>"
<span class="attribute">lemmaRef</span>="<span class="attributevalue">http://www.myLexicon.com/be</span>"></span>was<span class="element"></w></span> ... </div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.14_div.3"><h3><span class="headingNumber">3.14.3. </span><span class="head" itemprop="head">General-Purpose Interpretation Elements</span></h3><p>The <span class="gi"><w></span> element is a specialisation of the <span class="gi"><seg></span> element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section <a class="link_ptr" itemprop="ptr" href="#Simple-ptrs" title="Cross References and Links"><span class="headingNumber">3.7. </span>Cross References and Links</a>); it identifies some phrase-level portion of text to which the encoder may assign a user-specified <span xmlns="" class="att" itemprop="att">type</span>, as well as a unique identifier; it may thus be used to tag textual features for which there is no other provision in the published TEI Guidelines.</p><div class="p">For example, the Guidelines provide no ‘apostrophe’ element to mark parts of a literary text in which the narrator addresses the reader (or hearer) directly. One approach might be to regard these as instances of the <span class="gi"><q></span> element, distinguished from others by an appropriate value for the <span xmlns="" class="att" itemprop="att">who</span> attribute. A possibly simpler, and certainly more general, solution would however be to use the <span class="gi"><seg></span> element as follows: <div id="index.xml-egXML-d33e3806" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">chapter</span>" <span class="attribute">n</span>="<span class="attributevalue">38</span>"></span>
<span class="element"><p></span>
<span class="element"><seg <span class="attribute">type</span>="<span class="attributevalue">apostrophe</span>"></span>Reader, I married him.<span class="element"></seg></span> A quiet wedding we had: ...<span class="element"></p></span>
<span class="element"></div></span></div> The <span xmlns="" class="att" itemprop="att">type</span> attribute on the <span class="gi"><seg></span> element can take any value, and so can be used to record phrase-level phenomena of any kind; it is good practice to record the values used and their significance in the header.</div></div></div><div class="teidiv1" id="Simple-composite"><h2><span class="headingNumber">3.15. </span></h2><div class="p">A composite text also has an optional front and back. In between occur one or more groups of texts, each with its own optional front and back matter. A composite text will thus be encoded using an overall structure like this: <div id="index.xml-egXML-d33e3825" class="pre egXML_valid"><span class="element"><TEI xmlns="http://www.tei-c.org/ns/1.0"></span>
<span class="element"><teiHeader></span>
<span class="comment"><!--[ header information for the composite ]--></span>
<span class="element"></teiHeader></span>
<span class="element"><text></span>
<span class="element"><front></span>
<span class="comment"><!--[ front matter for the composite ]--></span>
<span class="element"></front></span>
<span class="element"><group></span>
<span class="element"><text></span>
<span class="element"><front></span>
<span class="comment"><!--[ front matter of first text ]--></span>
<span class="element"></front></span>
<span class="element"><body></span>
<span class="comment"><!--[ body of first text ]--></span>
<span class="element"></body></span>
<span class="element"><back></span>
<span class="comment"><!--[ back matter of first text ]--></span>
<span class="element"></back></span>
<span class="element"></text></span>
<span class="element"><text></span>
<span class="element"><front></span>
<span class="comment"><!--[ front matter of second text]--></span>
<span class="element"></front></span>
<span class="element"><body></span>
<span class="comment"><!--[ body of second text ]--></span>
<span class="element"></body></span>
<span class="element"><back></span>
<span class="comment"><!--[ back matter of second text ]--></span>
<span class="element"></back></span>
<span class="element"></text></span>
<span class="comment"><!--[ more texts or groups of texts here ]--></span>
<span class="element"></group></span>
<span class="element"><back></span>
<span class="comment"><!--[ back matter for the composite ]--></span>
<span class="element"></back></span>
<span class="element"></text></span>
<span class="element"></TEI></span></div></div><div class="p">It is also possible to define a composite of complete TEI texts, each with its own header. Such a collection is known as a <span class="term" itemprop="term">TEI corpus</span>, and must itself have a header: <div id="index.xml-egXML-d33e3855" class="pre egXML_valid"><span class="element"><teiCorpus xmlns="http://www.tei-c.org/ns/1.0"></span>
<span class="element"><teiHeader></span>
<span class="comment"><!--[header information for the corpus]--></span>
<span class="element"></teiHeader></span>
<span class="element"><TEI></span>
<span class="element"><teiHeader></span>
<span class="comment"><!--[header information for first text]--></span>
<span class="element"></teiHeader></span>
<span class="element"><text></span>
<span class="comment"><!--[first text in corpus]--></span>
<span class="element"></text></span>
<span class="element"></TEI></span>
<span class="element"><TEI></span>
<span class="element"><teiHeader></span>
<span class="comment"><!--[header information for second text]--></span>
<span class="element"></teiHeader></span>
<span class="element"><text></span>
<span class="comment"><!--[second text in corpus]--></span>
<span class="element"></text></span>
<span class="element"></TEI></span>
<span class="element"></teiCorpus></span></div> It is also possible to create a composite of corpora -- that is, one <span class="gi"><teiCorpus></span> element may contain many nested <span class="gi"><teiCorpus></span> elements rather than many nested <span class="gi"><TEI></span> elements, to any depth considered necessary.</div></div><div class="teidiv1" id="Simple-fronbac"><h2><span class="headingNumber">3.16. </span><span class="head" itemprop="head">Front and Back Matter</span></h2><div class="teidiv2" id="index.xml-body.1_div.3_div.16_div.1"><h3><span class="headingNumber">3.16.1. </span><span class="head" itemprop="head">Front Matter</span></h3><p>For many purposes, particularly in older texts, the preliminary material such as title pages, prefatory epistles, etc., may provide very useful additional linguistic or social information. P5 provides a set of recommendations for distinguishing the textual elements most commonly encountered in front matter, which are summarized here.</p><div class="teidiv3" id="h51"><h4><span class="headingNumber">3.16.1.1. </span><span class="head" itemprop="head">Title Page</span></h4><p>The start of a title page should be marked with the element <span class="gi"><titlePage></span>. All text contained on the page should be transcribed and tagged with the appropriate element from the following list: </p><p>Typeface distinctions should be marked with the <span xmlns="" class="att" itemprop="att">rendition </span> attribute when necessary, as described above. Very detailed description of the letter spacing and sizing used in ornamental titles is not as yet provided for by the Guidelines. Changes of language should be marked by appropriate use of the <span xmlns="" class="att" itemprop="att">xml:lang</span> attribute or the <span class="gi"><foreign></span> element, as necessary. Names of people, places, or organizations, may be tagged using the <span class="gi"><name></span> element wherever they appear if no other more specific element is available.</p><div class="p">Two example title pages follow: <div id="index.xml-egXML-d33e3921" class="pre egXML_valid"><span class="element"><titlePage <span class="attribute">rendition</span>="<span class="attributevalue">Roman</span>"></span>
<span class="element"><docTitle></span>
<span class="element"><titlePart <span class="attribute">type</span>="<span class="attributevalue">main</span>"></span> PARADISE REGAIN'D. A POEM In IV <span class="element"><hi></span>BOOKS<span class="element"></hi></span>. <span class="element"></titlePart></span>
<span class="element"><titlePart></span> To which is added <span class="element"><title></span>SAMSON AGONISTES<span class="element"></title></span>. <span class="element"></titlePart></span>
<span class="element"></docTitle></span>
<span class="element"><byline></span>The Author <span class="element"><docAuthor></span>JOHN MILTON<span class="element"></docAuthor></span>
<span class="element"></byline></span>
<span class="element"><docImprint></span>
<span class="element"><name></span>LONDON<span class="element"></name></span>, Printed by <span class="element"><name></span>J.M.<span class="element"></name></span> for <span class="element"><name></span>John Starkey<span class="element"></name></span>
at the <span class="element"><name></span>Mitre<span class="element"></name></span> in <span class="element"><name></span>Fleetstreet<span class="element"></name></span>, near
<span class="element"><name></span>Temple-Bar.<span class="element"></name></span>
<span class="element"></docImprint></span>
<span class="element"><docDate></span>MDCLXXI<span class="element"></docDate></span>
<span class="element"></titlePage></span></div><div id="index.xml-egXML-d33e3958" class="pre egXML_valid"><span class="element"><titlePage></span>
<span class="element"><docTitle></span>
<span class="element"><titlePart <span class="attribute">type</span>="<span class="attributevalue">main</span>"></span> Lives of the Queens of England, from the Norman
Conquest;<span class="element"></titlePart></span>
<span class="element"><titlePart <span class="attribute">type</span>="<span class="attributevalue">sub</span>"></span>with anecdotes of their courts. <span class="element"></titlePart></span>
<span class="element"></docTitle></span>
<span class="element"><titlePart></span>Now first published from Official Records and other authentic documents private
as well as public.<span class="element"></titlePart></span>
<span class="element"><docEdition></span>New edition, with corrections and additions<span class="element"></docEdition></span>
<span class="element"><byline></span>By <span class="element"><docAuthor></span>Agnes Strickland<span class="element"></docAuthor></span>
<span class="element"></byline></span>
<span class="element"><epigraph></span>
<span class="element"><q></span>The treasures of antiquity laid up in old historic rolls, I opened.<span class="element"></q></span>
<span class="element"><bibl></span>BEAUMONT<span class="element"></bibl></span>
<span class="element"></epigraph></span>
<span class="element"><docImprint></span>Philadelphia: Blanchard and Lea<span class="element"></docImprint></span>
<span class="element"><docDate></span>1860.<span class="element"></docDate></span>
<span class="element"></titlePage></span></div></div><div class="p">As elsewhere, the <span xmlns="" class="att" itemprop="att">ref</span> attribute may be used to link a name with a canonical definition of the entity being named. For example: <div id="index.xml-egXML-d33e3987" class="pre egXML_valid"><span class="element"><byline></span>By <span class="element"><docAuthor></span>
<span class="element"><name <span class="attribute">ref</span>="<span class="attributevalue">http://en.wikipedia.org/wiki/Agnes_Strickland</span>"></span>Agnes
Strickland<span class="element"></name></span>
<span class="element"></docAuthor></span>
<span class="element"></byline></span></div></div></div><div class="teidiv3" id="h52"><h4><span class="headingNumber">3.16.1.2. </span><span class="head" itemprop="head">Prefatory Matter</span></h4><p>Major blocks of text within the front matter should be marked using <span class="gi"><div></span> elements; the following suggested values for the <span xmlns="" class="att" itemprop="att">type</span> attribute may be used to distinguish various common types of prefatory matter: </p><dl itemprop="list"><dt><span itemprop="label">preface</span></dt><dd>A foreword or preface addressed to the reader in which the author or publisher explains the content, purpose, or origin of the text</dd><dt><span itemprop="label">dedication</span></dt><dd>A formal offering or dedication of a text to one or more persons or institutions by the author.</dd><dt><span itemprop="label">abstract</span></dt><dd>A summary of the content of a text as continuous prose</dd><dt><span itemprop="label">ack</span></dt><dd>A formal declaration of acknowledgment by the author in which persons and institutions are thanked for their part in the creation of a text</dd><dt><span itemprop="label">contents</span></dt><dd>A table of contents, specifying the structure of a work and listing its constituents. The <span class="gi"><list></span> element should be used to mark its structure.</dd><dt><span itemprop="label">frontispiece</span></dt><dd>A pictorial frontispiece, possibly including some text.</dd></dl><p>Where other kinds of prefatory matter are encountered, the encoder is at liberty to invent other values for the <span xmlns="" class="att" itemprop="att">type</span> attribute.</p><p>Like any text division, those in front matter may contain low level structural or non-structural elements as described elsewhere. They will generally begin with a heading or title of some kind which should be tagged using the <span class="gi"><head></span> element. Epistles will contain the following additional elements: </p><p>Epistles which appear elsewhere in a text will, of course, contain these same elements.</p><div class="p">As an example, the dedication at the start of Milton's <span class="titlem">Comus</span> should be marked up as follows: <div id="index.xml-egXML-d33e4060" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">dedication</span>"></span>
<span class="element"><head></span>To the Right Honourable <span class="element"><name></span>JOHN Lord Viscount BRACLY<span class="element"></name></span>, Son and Heir apparent
to the Earl of Bridgewater, &amp;c.<span class="element"></head></span>
<span class="element"><salute></span>MY LORD,<span class="element"></salute></span>
<span class="element"><p></span>THis <span class="element"><hi></span>Poem<span class="element"></hi></span>, which receiv'd its first occasion of Birth from your Self, and
others of your Noble Family .... and as in this representation your attendant
<span class="element"><name></span>Thyrsis<span class="element"></name></span>, so now in all reall expression<span class="element"></p></span>
<span class="element"><closer></span>
<span class="element"><salute></span>Your faithfull, and most humble servant<span class="element"></salute></span>
<span class="element"><signed></span>
<span class="element"><name></span>H. LAWES.<span class="element"></name></span>
<span class="element"></signed></span>
<span class="element"></closer></span>
<span class="element"></div></span></div></div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.16_div.2"><h3><span class="headingNumber">3.16.2. </span><span class="head" itemprop="head">Back Matter</span></h3><div class="teidiv3" id="index.xml-body.1_div.3_div.16_div.2_div.1"><h4><span class="headingNumber">3.16.2.1. </span><span class="head" itemprop="head">Structural Divisions of Back Matter</span></h4><p>Because of variations in publishing practice, back matter can contain virtually any of the elements listed above for front matter, and the same elements should be used where this is so. Additionally, back matter may contain the following types of matter within the <span class="gi"><back></span> element. Like the structural divisions of the body, these should be marked as <span class="gi"><div></span> elements, and distinguished by the following suggested values of the <span xmlns="" class="att" itemprop="att">type</span> attribute: </p><dl itemprop="list"><dt><span itemprop="label">appendix</span></dt><dd>An ancillary self-contained section of a work, often providing additional but in some sense extra-canonical text.</dd><dt><span itemprop="label">glossary</span></dt><dd>A list of terms associated with definition texts (‘glosses’): this should be encoded as a <list type="gloss"> element</dd><dt><span itemprop="label">notes</span></dt><dd>A section in which textual or other kinds of notes are gathered together.</dd><dt><span itemprop="label">bibliogr</span></dt><dd>A list of bibliographic citations: this should be encoded as a <span class="gi"><listBibl></span></dd><dt><span itemprop="label">index</span></dt><dd>Any form of pre-existing index to the work (An index may also be generated for a document by using the <span class="gi"><index></span> element described above).</dd><dt><span itemprop="label">colophon</span></dt><dd>A statement appearing at the end of a book describing the conditions of its physical production.</dd></dl></div></div></div><div class="teidiv1" id="Simple-header"><h2><span class="headingNumber">3.17. </span><span class="head" itemprop="head">The Electronic Title Page</span></h2><p>Every TEI text has a header which provides information analogous to that provided by the title page of printed text. The header is introduced by the element <span class="gi"><teiHeader></span> and has four major parts: </p><p>A corpus or collection of texts with many shared characteristics may have one header for the corpus and individual headers for each component of the corpus. In this case the <span xmlns="" class="att" itemprop="att">type</span> attribute indicates the type of header. <code itemprop="code"><teiHeader type="corpus"></code> introduces the header for corpus-level information.</p><p>Some of the header elements contain running prose which consists of one or more <span class="gi"><p></span>s. Others are grouped: </p><ul itemprop="list"><li class="item" itemprop="item">Elements whose names end in <span class="mentioned" itemprop="mentioned">Stmt</span> (for statement) usually enclose a group of elements recording some structured information.</li><li class="item" itemprop="item">Elements whose names end in <span class="mentioned" itemprop="mentioned">Decl</span> (for declaration) enclose information about specific encoding practices.</li><li class="item" itemprop="item">Elements whose names end in <span class="mentioned" itemprop="mentioned">Desc</span> (for description) contain a prose description.</li></ul><div class="teidiv2" id="index.xml-body.1_div.3_div.17_div.1"><h3><span class="headingNumber">3.17.1. </span><span class="head" itemprop="head">The File Description</span></h3><p>The <span class="gi"><fileDesc></span> element is mandatory. It contains a full bibliographic description of the file with the following elements: </p><div class="p">A minimal header has the following structure: <div id="index.xml-egXML-d33e4195" class="pre egXML_valid"><span class="element"><teiHeader></span>
<span class="element"><fileDesc></span>
<span class="element"><titleStmt></span>
<span class="comment"><!-- bibliographic description of the digital resource --></span>
<span class="element"></titleStmt></span>
<span class="element"><publicationStmt></span>
<span class="comment"><!-- information about how the resource is distributed --></span>
<span class="element"></publicationStmt></span>
<span class="element"><sourceDesc></span>
<span class="comment"><!-- information about the sources from which the digital resource is derived --></span>
<span class="element"></sourceDesc></span>
<span class="element"></fileDesc></span>
<span class="element"></teiHeader></span></div></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.1"><h4><span class="headingNumber">3.17.1.1. </span><span class="head" itemprop="head">The Title Statement</span></h4><p>The following elements can be used in the <span class="gi"><titleStmt></span>: </p><div class="p">The title of a digital resource derived from a non-digital one will obviously be similar. However, it is important to distinguish the title of the computer file from that of the source text, for example: <pre class="pre_eg cdata">[title of source]: a machine readable transcription [title of source]: electronic edition A machine readable version of: [title of source]</pre> The <span class="gi"><respStmt></span> element contains the following subcomponents: Example: <div id="index.xml-egXML-d33e4231" class="pre egXML_valid"><span class="element"><titleStmt></span>
<span class="element"><title></span>Two stories by Edgar Allen Poe: a machine readable transcription<span class="element"></title></span>
<span class="element"><author></span>Poe, Edgar Allen (1809-1849)<span class="element"></author></span>
<span class="element"><respStmt></span>
<span class="element"><resp></span>compiled by<span class="element"></resp></span>
<span class="element"><name></span>James D. Benson<span class="element"></name></span>
<span class="element"></respStmt></span>
<span class="element"></titleStmt></span></div></div></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.2"><h4><span class="headingNumber">3.17.1.2. </span><span class="head" itemprop="head">The Edition Statement</span></h4><p>The <span class="gi"><editionStmt></span> groups information relating to one edition of the digital resource (where <span class="mentioned" itemprop="mentioned">edition</span> is used as elsewhere in bibliography), and may include the following elements: </p><div class="p">Example: <div id="index.xml-egXML-d33e4258" class="pre egXML_valid"><span class="element"><editionStmt></span>
<span class="element"><edition <span class="attribute">n</span>="<span class="attributevalue">U2</span>"></span>Third
draft, substantially revised <span class="element"><date></span>1987<span class="element"></date></span>
<span class="element"></edition></span>
<span class="element"></editionStmt></span></div></div><p>Determining exactly what constitutes a new edition of an electronic text is left to the encoder.</p></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.3"><h4><span class="headingNumber">3.17.1.3. </span><span class="head" itemprop="head">The Extent Statement</span></h4><p>The <span class="gi"><extent></span> statement describes the approximate size of the digital resource.</p><div class="p">Example: <div id="index.xml-egXML-d33e4276" class="pre egXML_valid"><span class="element"><extent></span>4532
bytes<span class="element"></extent></span></div></div></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.4"><h4><span class="headingNumber">3.17.1.4. </span><span class="head" itemprop="head">The Publication Statement</span></h4><p>The <span class="gi"><publicationStmt></span> is mandatory. It may contain a simple prose description or groups of the elements described below: </p><p>At least one of these three elements must be present, unless the entire publication statement is in prose. The following elements may occur within them: </p><div class="p">Example: <div id="index.xml-egXML-d33e4302" class="pre egXML_valid"><span class="element"><publicationStmt></span>
<span class="element"><publisher></span>University of Victoria Humanities Computing and Media Centre<span class="element"></publisher></span>
<span class="element"><pubPlace></span>Victoria, BC<span class="element"></pubPlace></span>
<span class="element"><date></span>2011<span class="element"></date></span>
<span class="element"><availability <span class="attribute">status</span>="<span class="attributevalue">restricted</span>"></span>
<span class="element"><licence <span class="attribute">target</span>="<span class="attributevalue">http://creativecommons.org/licenses/by-sa/3.0/</span>"></span> Distributed under a
Creative Commons Attribution-ShareAlike 3.0 Unported License <span class="element"></licence></span>
<span class="element"></availability></span>
<span class="element"></publicationStmt></span></div></div></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.5"><h4><span class="headingNumber">3.17.1.5. </span><span class="head" itemprop="head">Series and Notes Statements</span></h4><p>The <span class="gi"><seriesStmt></span> element groups information about the series, if any, to which a publication belongs. It may contain <span class="gi"><title></span>, <span class="gi"><idno></span>, or <span class="gi"><respStmt></span> elements.</p><p>The <span class="gi"><notesStmt></span>, if used, contains one or more <span class="gi"><note></span> elements which contain a note or annotation. Some information found in the notes area in conventional bibliography has been assigned specific elements in the TEI scheme.</p></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.1_div.6"><h4><span class="headingNumber">3.17.1.6. </span><span class="head" itemprop="head">The Source Description</span></h4><p>The <span class="gi"><sourceDesc></span> is a mandatory element which records details of the source or sources from which the computer file is derived. It may contain simple prose or a bibliographic citation, using one or more of the following elements: </p><div class="p">Examples: <div id="index.xml-egXML-d33e4351" class="pre egXML_valid"><span class="element"><sourceDesc></span>
<span class="element"><bibl></span>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)<span class="element"></bibl></span>
<span class="element"></sourceDesc></span></div> <div id="index.xml-egXML-d33e4356" class="pre egXML_valid"><span class="element"><sourceDesc></span>
<span class="element"><bibl></span>
<span class="element"><author></span>CNN Network News<span class="element"></author></span>
<span class="element"><title></span>News headlines<span class="element"></title></span>
<span class="element"><date></span>12 Jun
1989<span class="element"></date></span>
<span class="element"></bibl></span>
<span class="element"></sourceDesc></span></div></div></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.17_div.2"><h3><span class="headingNumber">3.17.2. </span><span class="head" itemprop="head">The Encoding Description</span></h3><p>The <span class="gi"><encodingDesc></span> element specifies the methods and editorial principles which governed the transcription of the text. Its use is highly recommended. It may be prose description or may contain elements from the following list: </p><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.2_div.1"><h4><span class="headingNumber">3.17.2.1. </span><span class="head" itemprop="head">Project and Sampling Descriptions</span></h4><div class="p">Examples of <span class="gi"><projectDesc></span> and <span class="gi"><samplingDesc></span>: <div id="index.xml-egXML-d33e4390" class="pre egXML_valid"><span class="element"><encodingDesc></span>
<span class="element"><projectDesc></span>
<span class="element"><p></span>Texts collected for
use in the Claremont Shakespeare Clinic, June 1990.
<span class="element"></p></span>
<span class="element"></projectDesc></span>
<span class="element"></encodingDesc></span></div> <div id="index.xml-egXML-d33e4396" class="pre egXML_valid"><span class="element"><encodingDesc></span>
<span class="element"><samplingDecl></span>
<span class="element"><p></span>Samples of
2000 words taken from the beginning of the text<span class="element"></p></span>
<span class="element"></samplingDecl></span>
<span class="element"></encodingDesc></span></div></div></div><div class="teidiv3" id="index.xml-body.1_div.3_div.17_div.2_div.2"><h4><span class="headingNumber">3.17.2.2. </span><span class="head" itemprop="head">Editorial Declarations</span></h4><p>The <span class="gi"><editorialDecl></span> contains a prose description of the practices used when encoding the text. Typically this description should cover such topics as the following, each of which may conveniently be given as a separate paragraph. </p><dl itemprop="list"><dt><span itemprop="label">correction </span></dt><dd>how and under what circumstances corrections have been made in the text.</dd><dt><span itemprop="label">normalization</span></dt><dd>the extent to which the original source has been regularized or normalized.</dd><dt><span itemprop="label">quotation</span></dt><dd>what has been done with quotation marks in the original -- have they been retained or replaced by entity references, are opening and closing quotes distinguished, etc. </dd><dt><span itemprop="label">hyphenation</span></dt><dd>what has been done with hyphens (especially end-of-line hyphens) in the original -- have they been retained, replaced by entity references, etc.</dd><dt><span itemprop="label">segmentation</span></dt><dd>how has the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.</dd><dt><span itemprop="label">interpretation</span></dt><dd>what analytic or interpretive information has been added to the text. </dd></dl><div class="p">Example: <div id="index.xml-egXML-d33e4437" class="pre egXML_valid"><span class="element"><editorialDecl></span>
<span class="element"><p></span>The part of
speech analysis applied throughout section 4 was added by hand and has not been
checked.<span class="element"></p></span>
<span class="element"><p></span>Errors in transcription controlled by using the WordPerfect spelling
checker.<span class="element"></p></span>
<span class="element"><p></span>All words converted to Modern American spelling using Webster's 9th
Collegiate dictionary.<span class="element"></p></span>
<span class="element"></editorialDecl></span></div></div></div><div class="teidiv3" id="refsdecl"><h4><span class="headingNumber">3.17.2.3. </span><span class="head" itemprop="head">Reference and Classification Declarations</span></h4><p>The <span class="gi"><refsDecl></span> element is used to document the way in which any standard referencing scheme built into the encoding works. In its simplest form, it consists of prose description.</p><div class="p">Example: <div id="index.xml-egXML-d33e4455" class="pre egXML_valid"><span class="element"><refsDecl></span>
<span class="element"><p></span>The <span class="element"><att></span>n<span class="element"></att></span>
attribute on each <span class="element"><gi></span>div<span class="element"></gi></span> contains the canonical reference for each division in the
form XX.yyy where XX is the book number in roman numeral and yyy is the section number in
arabic.<span class="element"></p></span>
<span class="element"><p></span>Milestone tags refer to the edition of 1830 as E30 and that of 1850 as E50.
<span class="element"></p></span>
<span class="element"></refsDecl></span></div></div><p>The <span class="gi"><classDecl></span> element groups together definitions or sources for any descriptive classification schemes used by other parts of the header. At least one such scheme must be provided, encoded using the following elements: </p><div class="p">In the simplest case, the taxonomy may be defined by a bibliographic reference, as in the following example: <div id="index.xml-egXML-d33e4479" class="pre egXML_valid"><span class="element"><classDecl></span>
<span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">LC-SH</span>"></span>
<span class="element"><bibl></span>Library of Congress Subject Headings
<span class="element"></bibl></span>
<span class="element"></taxonomy></span>
<span class="element"></classDecl></span></div></div><div class="p">Alternatively, or in addition, the encoder may define a special purpose classification scheme, as in the following example: <div id="index.xml-egXML-d33e4486" class="pre egXML_valid"><span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">B</span>"></span>
<span class="element"><bibl></span>Brown Corpus<span class="element"></bibl></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A</span>"></span>
<span class="element"><catDesc></span>Press
Reportage<span class="element"></catDesc></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A1</span>"></span>
<span class="element"><catDesc></span>Daily<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A2</span>"></span>
<span class="element"><catDesc></span>Sunday<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A3</span>"></span>
<span class="element"><catDesc></span>National<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A4</span>"></span>
<span class="element"><catDesc></span>Provincial<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A5</span>"></span>
<span class="element"><catDesc></span>Political<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.A6</span>"></span>
<span class="element"><catDesc></span>Sports<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.D</span>"></span>
<span class="element"><catDesc></span>Religion<span class="element"></catDesc></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.D1</span>"></span>
<span class="element"><catDesc></span>Books<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">B.D2</span>"></span>
<span class="element"><catDesc></span>Periodicals and
tracts<span class="element"></catDesc></span>
<span class="element"></category></span>
<span class="element"></category></span>
<span class="element"></taxonomy></span></div></div><p>Linkage between a particular text and a category within such a taxonomy is made by means of the <span class="gi"><catRef></span> element within the <span class="gi"><textClass></span> element, as described in the next section below.</p></div></div><div class="teidiv2" id="index.xml-body.1_div.3_div.17_div.3"><h3><span class="headingNumber">3.17.3. </span><span class="head" itemprop="head">The Profile Description</span></h3><p>The <span class="gi"><profileDesc></span> element enables information characterizing various descriptive aspects of a text to be recorded within a single framework. It has three optional components: </p><p>The <span class="gi"><creation></span> element is useful for documenting where a work was created, even though it may not have been published or recorded there.</p><div class="p">Example: <div id="index.xml-egXML-d33e4547" class="pre egXML_valid"><span class="element"><creation></span>
<span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1992-08</span>"></span>August 1992<span class="element"></date></span>
<span class="element"><name <span class="attribute">type</span>="<span class="attributevalue">place</span>"></span>Taos, New Mexico<span class="element"></name></span>
<span class="element"></creation></span></div></div><div class="p">The <span class="gi"><langUsage></span> element is useful where a text contains many different languages. It may contain <span class="gi"><language></span> elements to document each particular language used: For example, a text containing predominantly text in French as spoken in Quebec, but also smaller amounts of British and Canadian English might be documented as follows: <div id="index.xml-egXML-d33e4564" class="pre egXML_valid"><span class="element"><langUsage></span>
<span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">fr-CA</span>" <span class="attribute">usage</span>="<span class="attributevalue">60</span>"></span>Québecois<span class="element"></language></span>
<span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">en-CA</span>" <span class="attribute">usage</span>="<span class="attributevalue">20</span>"></span>Canadian business English<span class="element"></language></span>
<span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">en-GB</span>" <span class="attribute">usage</span>="<span class="attributevalue">20</span>"></span>British English<span class="element"></language></span>
<span class="element"></langUsage></span></div></div><p>The <span class="gi"><textClass></span> element classifies a text. This may be done with reference to a classification system locally defined by means of the <span class="gi"><classDecl></span> element, or by reference to some externally defined established scheme such as the Universal Decimal Classification. Texts may also be classified using lists of keywords, which may themselves be drawn from locally or externally defined control lists. The following elements are used to supply such classifications: </p><div class="p">The simplest way of classifying a text is by means of the <span class="gi"><classCode></span> element. For example, a text with classification 410 in the Universal Decimal Classification might be documented as follows: <div id="index.xml-egXML-d33e4591" class="pre egXML_valid"><span class="element"><classCode <span class="attribute">scheme</span>="<span class="attributevalue">http://www.udc.org</span>"></span>410<span class="element"></classCode></span></div></div><div class="p">When a classification scheme has been locally defined using the <span class="gi"><taxonomy></span> element discussed in the preceding subsection, the <span class="gi"><catRef></span> element should be used to reference it. To continue the earlier example, a work classified in the Brown Corpus as <code itemprop="code">Press reportage - Sunday</code> and also as <code itemprop="code">Religion</code> might be documented as follows: <div id="index.xml-egXML-d33e4609" class="pre egXML_valid"><span class="element"><catRef <span class="attribute">target</span>="<span class="attributevalue">#B.A3 #B.D</span>"/></span></div></div><div class="p">The element <span class="gi"><keywords></span> contains a list of keywords or phrases identifying the topic or nature of a text. As usual, the attribute <span xmlns="" class="att" itemprop="att">scheme</span> identifies the source from which these terms are taken. For example, if the LC Subject Headings are used, following declaration of that classification system in a <span class="gi"><taxonomy></span> element as above : <div id="index.xml-egXML-d33e4623" class="pre egXML_valid"><span class="element"><textClass></span>
<span class="element"><keywords <span class="attribute">scheme</span>="<span class="attributevalue">#LCSH</span>"></span>
<span class="element"><list></span>
<span class="element"><item></span>English literature -- History and criticism -- Data processing.<span class="element"></item></span>
<span class="element"><item></span>English literature -- History and criticism -- Theory etc.<span class="element"></item></span>
<span class="element"><item></span>English language -- Style -- Data processing.<span class="element"></item></span>
<span class="element"></list></span>
<span class="element"></keywords></span>
<span class="element"></textClass></span></div></div><p>Multiple classifications may be supplied using any of the mechanisms described in this section.</p></div><div class="teidiv2" id="index.xml-body.1_div.3_div.17_div.4"><h3><span class="headingNumber">3.17.4. </span><span class="head" itemprop="head">The Revision Description</span></h3><p>The <span class="gi"><revisionDesc></span> element provides a change log in which each change made to a text may be recorded. The log may be recorded as a sequence of <span class="gi"><change></span> elements each of which contains a brief description of the change. The attributes <span xmlns="" class="att" itemprop="att">when</span> and <span xmlns="" class="att" itemprop="att">who</span> may be used to identify when the change was carried out and the agency responsible for it.</p><div class="p">Example: <div id="index.xml-egXML-d33e4654" class="pre egXML_valid"><span class="element"><revisionDesc></span>
<span class="element"><change <span class="attribute">when</span>="<span class="attributevalue">1991-03-06</span>" <span class="attribute">who</span>="<span class="attributevalue">#EMB</span>"></span>File format updated<span class="element"></change></span>
<span class="element"><change <span class="attribute">when</span>="<span class="attributevalue">1990-05-25</span>" <span class="attribute">who</span>="<span class="attributevalue">#EMB</span>"></span>Stuart's corrections entered<span class="element"></change></span>
<span class="element"></revisionDesc></span></div></div><p>In a production environment it will usually be found preferable to use some kind of automated system to track and record changes. Many such <span class="term" itemprop="term">version control systems</span>, as they are known, can also be configured to update the TEI Header of a file automatically.</p></div></div></section><section class="teidiv0" id="processingmodel"><header><h1><span class="headingNumber">4. </span><span class="head" itemprop="head">A Short Tour of the Processing Model</span></h1></header><p>The key feature of the Processing Model is a notation that allows each element to be assigned to a structural category, which in turn is mapped to a description of how to render it. This allows a processor to know whether to handle the element or not, and broadly speaking how to display or otherwise process it. Several projects that have used TEI Simple and its Processing Model report that it cuts the length of required code by two thirds, reduces its complexity, and makes it easier to maintain. The model and rendition instructions are part of the TEI ODD and can be customized. </p><p>ODD, short for <span class="q" itemprop="q">‘One Document Does it all’</span>, is the technology used by the TEI for maintaining its rules. An ODD is an XML document written in a <span class="term" itemprop="term">literate programming</span> style, mixing code and explanatory prose. From an ODD and with the use of an <span class="term" itemprop="term">ODD Processor</span> you can produce reference documentation as well as schemas. Support for the Processing Model is a significant extension of the TEI ODD and provides and answer to the question of what to do with a text once you have encoded it. Encoding is often the easy part. For a fuller account of ODD see the chapter on <a class="link_ref" itemprop="ref" href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html">Documentation Elements</a> in the Guidelines.</p><p>In principle there are a variety of ways in which a processor can use processing instructions encoded in the ODD to produce a readable text, whether a Web page, an epub, or a PDF. In practice <a class="link_ref" itemprop="ref" href="http://showcases.exist-db.org/exist/apps/tei-simple/index.html">Wolfgang Meier's XQuery based ODD processor</a> is the fullest and most thoroughly tested current implementation. From the instructions in the ODD it creates an XQuery Library module that relies heavily on XQuery's typeswitch, a switch or case statement whose structure lends itself to transforming each processing instruction in the ODD into an XQuery function. In a second step the XQuery Library module is used to transform the TEI Simple text.</p><div class="teidiv1" id="index.xml-body.1_div.4_div.1"><h2><span class="headingNumber">4.1. </span><span class="head" itemprop="head">The <model> element with some of its attributes and children</span></h2><div class="p">In the TEI ODD, the specifications for a particular element are recorded in an element called <span class="gi"><elementSpec></span>. The processing instructions for each element are kept in one or more <span class="gi"><model ></span> elements that are children of <elementSpec>. In the simplest and modal case the processing instruction is recorded as the value of a <span xmlns="" class="att" itemprop="att">behaviour</span> attribute: <div id="index.xml-egXML-d33e4704" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">back</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"/></span>
<span class="element"></elementSpec></span></div> This means <span class="q" itemprop="q">‘Apply the behaviour <span class="term" itemprop="term">block</span> to the element <back>’</span>.</div><div class="p">A slightly more complex processing instruction says that the rendering of the source document should be followed but specifies a rendition if there is nothing in the source: <div id="index.xml-egXML-d33e4716" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">l</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"
<span class="attribute">useSourceRendition</span>="<span class="attributevalue">true</span>"></span>
<span class="element"><outputRendition></span> margin-left: 1em; <span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"></elementSpec></span></div></div><div class="p">The <span class="term" itemprop="term">behaviour</span> of an element may depend on its attributes or place in the XML hierarchy. Here is the processing rule that distinguishes between a header row and an ordinary row in a table: <div id="index.xml-egXML-d33e4727" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">row</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">@role='label'</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">row</span>"></span>
<span class="element"><outputRendition></span>font-weight: bold;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">row</span>"></span>
<span class="element"><desc></span>Insert table row. <span class="element"></desc></span>
<span class="element"></model></span>
<span class="element"></elementSpec></span></div> The first <model> with its <span xmlns="" class="att" itemprop="att">predicate</span> attribute specifies the condition under which you use bold type for text in a table row. The second model specifies the default behaviour. The <span class="gi"><desc></span> element in the second model explains the meaning of <span class="term" itemprop="term">row</span> behaviour. It is optional. The next example shows the different treatment of <div>, depending on whether it contains a title-page, is a child element of <front>, <body>, or <back>, or a child element of <div>: <div id="index.xml-egXML-d33e4746" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">div</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">@type='title_page'</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"></span>
<span class="element"><outputRendition></span>border: 1px solid black; padding: 5px;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">section</span>"
<span class="attribute">predicate</span>="<span class="attributevalue">parent::body or parent::front or parent::back</span>"/></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"/></span>
<span class="element"></elementSpec></span></div></div><div class="p">The <span class="gi"><param></span> child of <model> associates a <span class="term" itemprop="term">behaviour</span> with the parameters or objects to which it applies. Thus the processing instruction for <list> tells you that the behaviour <span class="term" itemprop="term">list</span> targets items: <div id="index.xml-egXML-d33e4765" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">list</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">@rendition</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">list</span>" <span class="attribute">useSourceRendition</span>="<span class="attributevalue">true</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">content</span>"></span>item<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">not(@rendition)</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">list</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">content</span>"></span>item<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"></elementSpec></span></div></div></div><div class="teidiv1" id="index.xml-body.1_div.4_div.2"><h2><span class="headingNumber">4.2. </span><span class="head" itemprop="head">More about Behaviours</span></h2><p>The <span xmlns="" class="att" itemprop="att">behaviour</span> attribute has 26 different values, each of them describing what needs to be done to a TEI element for it to be transformed into part of a Web document, PDF file,or other output. We list them below, together with the names of the elements to which they apply, in descending order of the number of elements with which they are associated:</p><ul itemprop="list"><li class="item" itemprop="item"><span class="" itemprop="label">INLINE (49) </span><span class="hi" itemprop="hi">creates inline element out of content if there's something in <outputRendition>, use that formatting; otherwise just show text of selected content.: </span>abbr, actor, add, am author, bibl, c, choice, corr, date, del, desc, docAuthor, docDate, docEdition, docImprint, ex, expan, figDesc, figure, foreign, formula, formula, gap, handShift, hi, label, measure, milestone, name, note, num, orig, pc, ref, reg, rhyme, rs, s, salute, seg, sic, signed, space, subst, supplied, time, unclear, w, quote</li><li class="item" itemprop="item"><span class="" itemprop="label">BLOCK (35) </span><span class="hi" itemprop="hi">create a block structure: </span>address, addrLine, argument, back, body, byline, closer, dateline, div, doctitle, epigraph, figure, floatingText, formula, front, fw, group, head, imprimatur, l, lg, listBibl, note, opener, postscript, q, quote, role, roleDesc, salute, signed, sp, speaker, titlePage, titlePart, trailer</li><li class="item" itemprop="item"><span class="" itemprop="label">OMIT (10) </span><span class="hi" itemprop="hi">do nothing, do not process children: </span>author, docAuthor, docDate, docEdition, docImprint, docTitle, encodingDesc, profileDesc, publisher, pubPlace, revisionDesc</li><li class="item" itemprop="item"><span class="" itemprop="label">LIST (4) </span><span class="hi" itemprop="hi">create a list by following content: </span>castGroup, castList, list, listBibl</li><li class="item" itemprop="item"><span class="" itemprop="label">BREAK (3) </span><span class="hi" itemprop="hi">create a line, column, or page break according to type: </span>cb, lb, pb</li><li class="item" itemprop="item"><span class="" itemprop="label">LISTITEM (3) </span><span class="hi" itemprop="hi">create list item: </span>bibl, castItem, item</li><li class="item" itemprop="item"><span class="" itemprop="label">ALTERNATE (2) </span><span class="hi" itemprop="hi">: </span> <span class="hi" itemprop="hi">create a specialized display of alternating elements for displaying the preferred version and an alternative, both at once or by some method of toggling between the two:</span> date,choice</li><li class="item" itemprop="item"><span class="" itemprop="label">PARAGRAPH (2) </span><span class="hi" itemprop="hi">create a paragraph out of content.: </span>ab, p</li><li class="item" itemprop="item"><span class="" itemprop="label">ANCHOR </span><span class="hi" itemprop="hi">create an anchor with ID: </span>anchor</li><li class="item" itemprop="item"><span class="" itemprop="label">BODY </span><span class="hi" itemprop="hi">create the body of a document body: </span></li><li class="item" itemprop="item"><span class="" itemprop="label">CELL </span><span class="hi" itemprop="hi">create a table cell: </span>cit</li><li class="item" itemprop="item"><span class="" itemprop="label">CIT </span><span class="hi" itemprop="hi">show the content, with an indication of the source: </span>cit</li><li class="item" itemprop="item"><span class="" itemprop="label">DOCUMENT </span><span class="hi" itemprop="hi">start a new output document: </span> TEI</li><li class="item" itemprop="item"><span class="" itemprop="label">FIGURE </span><span class="hi" itemprop="hi">make a figure with the title as caption: </span> figure</li><li class="item" itemprop="item"><span class="" itemprop="label">GLYPH </span><span class="hi" itemprop="hi">show a character by looking up reference to a chardesc at the given URI: </span> g</li><li class="item" itemprop="item"><span class="" itemprop="label">GRAPHIC </span><span class="hi" itemprop="hi">if url is present, uses it to display graphic, else display a placeholder image. heading: </span> graphic</li><li class="item" itemprop="item"><span class="" itemprop="label">HEADING </span><span class="hi" itemprop="hi">creates a heading.: </span> head</li><li class="item" itemprop="item"><span class="" itemprop="label">INDEX </span><span class="hi" itemprop="hi">generate list according to type: </span> body</li><li class="item" itemprop="item"><span class="" itemprop="label">LINK</span><span class="hi" itemprop="hi">create hyperlink: </span> ref</li><li class="item" itemprop="item"><span class="" itemprop="label">METADATA </span><span class="hi" itemprop="hi">create metadata section: </span> teiHeader</li><li class="item" itemprop="item"><span class="" itemprop="label">NOTE </span><span class="hi" itemprop="hi">create an note, often out of line, depending on the value of place; could be margin, footnote, endnote, inline: </span>note</li><li class="item" itemprop="item"><span class="" itemprop="label">ROW </span><span class="hi" itemprop="hi">create a table row: </span> row</li><li class="item" itemprop="item"><span class="" itemprop="label">SECTION </span><span class="hi" itemprop="hi">create a new section of the output document: </span> div</li><li class="item" itemprop="item"><span class="" itemprop="label">TABLE </span><span class="hi" itemprop="hi">create a table: </span>table</li><li class="item" itemprop="item"><span class="" itemprop="label">TEXT </span><span class="hi" itemprop="hi">create literal text: </span>title</li><li class="item" itemprop="item"><span class="" itemprop="label">TITLE </span><span class="hi" itemprop="hi">create document title: </span>fileDesc</li></ul><p>There are several things to be said about this list. First, the names of the <span class="term" itemprop="term">behaviours</span> as well as their explanations, will be familiar to programmers who work with texts on the Web. Secondly, there are far fewer behaviours (26) than elements.</p><div class="p">Of the 106 elements in TEI Simple 76 have only one behaviour associated with them. Not quite two dozen elements have two behaviours associated with them. The <span class="term" itemprop="term">omit</span> behaviour is used to suppress the display of elements that can occur both in the <teiHeader> and the <text> element, as in the following example: <div id="index.xml-egXML-d33e4953" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">docDate</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">ancestor::teiHeader</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">omit</span>"></span>
<span class="element"><desc></span>Omit if located in teiHeader. <span class="element"></desc></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">inline</span>"/></span>
<span class="element"></elementSpec></span></div> Because the processor moves across <model> elements in the order of their occurrence, it is important to put the more specific condition first. In the following examples the alternatives are stated with equal degrees of explicitness, and the order does not matter: <div id="index.xml-egXML-d33e4960" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">list</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">@rendition</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">list</span>" <span class="attribute">useSourceRendition</span>="<span class="attributevalue">true</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">content</span>"></span>item<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">not(@rendition)</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">list</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">content</span>"></span>item<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"></elementSpec></span></div></div><div class="p">Half a dozen elements have more than two models, but <span class="hi" itemprop="hi">more </span>does not necessarily mean <span class="hi" itemprop="hi">more complex</span>. Take the <head> element, which can appear in a variety of environments and for which the Processing Model enumerates five explicit cases followed by a default case: <div id="index.xml-egXML-d33e4977" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">head</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">parent::figure</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"></span>
<span class="element"><outputRendition></span>font-style: italic;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">parent::table</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"></span>
<span class="element"><outputRendition></span>font-style: italic;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">parent::lg</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"></span>
<span class="element"><outputRendition></span>font-style: italic;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">parent::list</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"></span>
<span class="element"><outputRendition></span>font-weight: bold;<span class="element"></outputRendition></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">predicate</span>="<span class="attributevalue">parent::div</span>"
<span class="attribute">behaviour</span>="<span class="attributevalue">heading</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">level</span>"></span>count(ancestor::div)<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"/></span>
<span class="element"></elementSpec></span></div> Four of these models combine a predicate specifying the parent element with a simple CSS rendering instruction. The instruction for headings of <div> elements is a little more interesting: <code itemprop="code">count(ancestor::div)</code> is a little function that numbers the divs automatically.</div><p>A few processing instructions are quite complex. Take the behaviour <span class="term" itemprop="term">alternate</span>, which allows you to toggle between two different elements that are alternative child elements of <span class="gi"><choice></span> and lets you choose between </p><ul itemprop="list"><li class="item" itemprop="item">an abbreviation and its expansion (<span class="gi"><abbr></span> ad <span class="gi"><expan></span></li><li class="item" itemprop="item">an error in the text and its correction (<span class="gi"><sic></span> ad <span class="gi"><corr></span>)</li><li class="item" itemprop="item">an orthographic variant and its regular form (<span class="gi"><orig></span> ad <span class="gi"><reg></span>)</li></ul><div class="p">Two elements (<span class="gi"><body></span> and <span class="gi"><title></span> have processing instructions in which several model elements are chained together as a sequence and wrapped in a <span class="gi"><modelSequence></span>. The processing instruction for <span class="gi"><body></span> reads <div id="index.xml-egXML-d33e5046" class="pre egXML_valid"><span class="element"><elementSpec <span class="attribute">ident</span>="<span class="attributevalue">body</span>" <span class="attribute">mode</span>="<span class="attributevalue">change</span>"></span>
<span class="element"><modelSequence></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">index</span>"></span>
<span class="element"><param <span class="attribute">name</span>="<span class="attributevalue">type</span>"></span>'toc'<span class="element"></param></span>
<span class="element"></model></span>
<span class="element"><model <span class="attribute">behaviour</span>="<span class="attributevalue">block</span>"/></span>
<span class="element"></modelSequence></span>
<span class="element"></elementSpec></span></div> This sequence creates the framework for a display of the text together with a navigation panel that contains a table of context. The other (and rather daunting) <span class="gi"><modelSequence></span> works through all the options of displaying titles in various bibliographical environments.</div></div><div class="teidiv1" id="customization"><h2><span class="headingNumber">4.3. </span><span class="head" itemprop="head">Customizing the Processing Model</span></h2><div class="p">The point of the Processing Model is to reduce the time and effort it takes to publish a TEI text that meets scholarly standards. Its virtues are Spartan rather than Corinthian. If you can get acceptable results by staying within its rules you probably should. But modifications are possible and will sometimes be necessary. Some of them are easier to achieve than others. A processing instruction like <div id="index.xml-egXML-d33e5063" class="pre egXML_valid"><span class="element"><outputRendition></span>font-style: italic;<span class="element"></outputRendition></span></div> is just a specific form of the more general <div id="index.xml-egXML-d33e5067" class="pre egXML_valid"><span class="element"><outputRendition></span>{some CSS}<span class="element"></outputRendition></span></div> It is not hard to replace one set of CSS instructions with another. Changing the basic behaviour of a model is a different matter, and you need to think about unintended consequences. The following figure illustrates the general workflow of the Processing Model. Red and green are used as they are in traffic signals. Traveling along the green lines will be relatively easy. The red lines may cause trouble and will certainly involve a lot more work.</div><figure class="figure" itemprop="figure"><img src="images/SPM2.png" alt="Processing model workflow" class="graphic" itemprop="graphic"/><figcaption class="caption" itemprop="head">Figure 1. Processing model workflow</figcaption></figure></div></section><section class="teidiv0" id="index.xml-body.1_div.5"><h1><span class="headingNumber">5. </span></h1><figure class="figure" itemprop="figure"><img src="images/SPM2.png" alt="Processing model workflow" class="graphic" itemprop="graphic"/><figcaption class="caption" itemprop="head">Figure 2. Processing model workflow</figcaption></figure><p>This method of working assumes a workflow with three parts, and three distinct roles, to create a digital edition from a TEI text: </p><ol class="ordered" itemprop="list"><li class="item" itemprop="item">an <em itemprop="emph">editor</em> is responsible for the encoding and makes high-level output decisions. These fall into two parts <ol class="ordered" itemprop="list"><li class="item" itemprop="item"><em itemprop="emph">Structural</em> descriptions, eg <span class="ordered" itemprop="q">‘should the original or corrected version be displayed by default’</span>, or <span class="ordered" itemprop="q">‘is this a block level or inline component’</span></li><li class="item" itemprop="item">Indications of <em itemprop="emph">appearance</em> (<span class="ordered" itemprop="q">‘titles are in italics’</span>).</li></ol></li><li class="item" itemprop="item">a <em itemprop="emph">designer</em> creates the output envelope (for example, a book layout using InDesign or a web site using Drupal), making decisions in conjunction with the editor (<span class="ordered" itemprop="q">‘use Garamond font throughout’</span> or <span class="ordered" itemprop="q">‘every page must show the departmental logo’</span>)</li><li class="item" itemprop="item">a <em itemprop="emph">programmer</em> takes the <em itemprop="emph">editor</em>'s specification, and the TEI text(s), and creates the input for the <em itemprop="emph">designer</em> to make the output.</li></ol><p> It is crucial to understand here that neither the designer nor the programmer need have any understanding of the semantics of TEI elements, or the structure of a TEI document. The programmer, particularly, can use the processing model rules to extract material from the TEI text in a relatively simple way. The method works for a variety of output formats, as the programmer simply has to provide implementations for a small number of functions, and understand the well-documented features of CSS. The concepts addressed by the functions (eg <span class="q" itemprop="q">‘block’</span> and <span class="q" itemprop="q">‘inline’</span>) are in line with XSL FO, and HTML. Implementations of the processing model can be done in a variety or languages or environments, but any implementation must include an XPath 2.0 interpreter, as this is used in several places in the processing notation.</p></section><section class="teidiv0" id="index.xml-body.1_div.6"><header><h1><span class="headingNumber">6. </span><span class="head" itemprop="head">The TEI Simple schema</span></h1></header><p><b>Specification []</b></p><table class="border"/><div lang="" class="teidiv1" id="index.xml-body.1_div.6_div.1"><h2 lang=""><span class="headingNumber">6.1. </span><span class="head" itemprop="head">Summary</span></h2><p>A total of 105 elements are selected for use in the <span class="gi"><text></span> part of a document; an additional 44 elements are allowed for in the header. The following table shows the usage of all elements in six existing corpora, and classifies them 11 usage groups. There are 15 elements listed which are <em itemprop="emph">not</em> allowed in TEI Simple, but should be transformed to another element.</p><div class="table"><table itemprop="table"><tr itemprop="row" class="label"><td>Element</td><td>dbnl</td><td>obvil</td><td>cesr</td><td>ota</td><td>dta</td><td>TCP</td><td>Group</td><td>Use instead</td></tr><tr itemprop="row"><td>TEI</td><td class="right">10172</td><td class="right">126</td><td class="right">50</td><td class="right">457</td><td class="right">848</td><td class="right">61315</td><td>structure</td><td/></tr><tr itemprop="row"><td>ab</td><td class="right">0</td><td class="right">290</td><td class="right">1022</td><td class="right">60480</td><td class="right">0</td><td class="right">668</td><td>structure</td><td/></tr><tr itemprop="row"><td>abbr</td><td class="right">0</td><td class="right">0</td><td class="right">1482</td><td class="right">0</td><td class="right">69</td><td class="right">533814</td><td>editorial</td><td/></tr><tr itemprop="row"><td>actor</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">12</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>add</td><td class="right">0</td><td class="right">0</td><td class="right">71</td><td class="right">65</td><td class="right">0</td><td class="right">2441</td><td>editorial</td><td/></tr><tr itemprop="row"><td>addName</td><td class="right">0</td><td class="right">0</td><td class="right">7</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td/><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>addSpan</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">2</td><td class="right">0</td><td class="right">4</td><td>editorial</td><td/></tr><tr itemprop="row"><td>addrLine</td><td class="right">0</td><td class="right">0</td><td class="right">10</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>address</td><td class="right">0</td><td class="right">0</td><td class="right">5</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>am</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">166291</td><td>editorial</td><td/></tr><tr itemprop="row"><td>anchor</td><td class="right">0</td><td class="right">233</td><td class="right">0</td><td class="right">29</td><td class="right">0</td><td class="right">4</td><td>structure</td><td/></tr><tr itemprop="row"><td>argument</td><td class="right">0</td><td class="right">151</td><td class="right">0</td><td class="right">57</td><td class="right">2268</td><td class="right">71478</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>att</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>author</td><td class="right">0</td><td class="right">34</td><td class="right">83</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>back</td><td class="right">0</td><td class="right">1</td><td class="right">29</td><td class="right">77</td><td class="right">608</td><td class="right">24439</td><td>structure</td><td/></tr><tr itemprop="row"><td>bibl</td><td class="right">3187</td><td class="right">274</td><td class="right">155</td><td class="right">414</td><td class="right">4362</td><td class="right">296835</td><td>structure</td><td/></tr><tr itemprop="row"><td>biblFull</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>biblScope</td><td class="right">0</td><td class="right">0</td><td class="right">4</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>biblStruct</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>body</td><td class="right">10171</td><td class="right">126</td><td class="right">50</td><td class="right">688</td><td class="right">1155</td><td class="right">106968</td><td>structure</td><td/></tr><tr itemprop="row"><td>byline</td><td class="right">0</td><td class="right">17</td><td class="right">8</td><td class="right">619</td><td class="right">1028</td><td class="right">12525</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>c</td><td class="right">8966</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>linguistic</td><td/></tr><tr itemprop="row"><td>caesura</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">30299</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><milestone></span></td></tr><tr itemprop="row"><td>castGroup</td><td class="right">0</td><td class="right">0</td><td class="right">29</td><td class="right">0</td><td class="right">51</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>castItem</td><td class="right">0</td><td class="right">0</td><td class="right">63</td><td class="right">90</td><td class="right">744</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>castList</td><td class="right">0</td><td class="right">0</td><td class="right">28</td><td class="right">4</td><td class="right">74</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>cb</td><td class="right">0</td><td class="right">0</td><td class="right">66</td><td class="right">0</td><td class="right">26294</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>cell</td><td class="right">5895818</td><td class="right">242</td><td class="right">3218</td><td class="right">1282</td><td class="right">34153</td><td class="right">3455220</td><td>table</td><td/></tr><tr itemprop="row"><td>change</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>charDecl</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>charProp</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>choice</td><td class="right">0</td><td class="right">0</td><td class="right">61228</td><td class="right">770</td><td class="right">8799</td><td class="right">4106</td><td>editorial</td><td/></tr><tr itemprop="row"><td>cit</td><td class="right">3209</td><td class="right">12</td><td class="right">99</td><td class="right">155</td><td class="right">5431</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>closer</td><td class="right">0</td><td class="right">0</td><td class="right">35</td><td class="right">88</td><td class="right">1430</td><td class="right">122281</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>code</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><hi></span></td></tr><tr itemprop="row"><td>corr</td><td class="right">0</td><td class="right">0</td><td class="right">3103</td><td class="right">505</td><td class="right">5966</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>country</td><td class="right">0</td><td class="right">0</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>date</td><td class="right">7842</td><td class="right">47</td><td class="right">119</td><td class="right">61</td><td class="right">112</td><td class="right">64488</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>dateline</td><td class="right">0</td><td class="right">382</td><td class="right">1</td><td class="right">0</td><td class="right">2264</td><td class="right">53370</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>del</td><td class="right">0</td><td class="right">0</td><td class="right">62</td><td class="right">15</td><td class="right">0</td><td class="right">7</td><td>editorial</td><td/></tr><tr itemprop="row"><td>desc</td><td class="right">0</td><td class="right">186</td><td class="right">0</td><td class="right">241</td><td class="right">0</td><td class="right">6878050</td><td>editorial</td><td/></tr><tr itemprop="row"><td>div</td><td class="right">1856262</td><td class="right">4584</td><td class="right">2128</td><td class="right">16744</td><td class="right">104832</td><td class="right">1564908</td><td>structure</td><td/></tr><tr itemprop="row"><td>docAuthor</td><td class="right">0</td><td class="right">14</td><td class="right">0</td><td class="right">381</td><td class="right">823</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>docDate</td><td class="right">0</td><td class="right">388</td><td class="right">44</td><td class="right">6</td><td class="right">899</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>docEdition</td><td class="right">0</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td class="right">14</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>docImprint</td><td class="right">0</td><td class="right">0</td><td class="right">46</td><td class="right">223</td><td class="right">946</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>docTitle</td><td class="right">0</td><td class="right">1</td><td class="right">48</td><td class="right">349</td><td class="right">1156</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>editor</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>editorialDecl</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>email</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>emph</td><td class="right">0</td><td class="right">1090</td><td class="right">0</td><td class="right">6711</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><hi></span></td></tr><tr itemprop="row"><td>encodingDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>epigraph</td><td class="right">0</td><td class="right">2</td><td class="right">2</td><td class="right">487</td><td class="right">137</td><td class="right">45743</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>ex</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">166291</td><td>editorial</td><td/></tr><tr itemprop="row"><td>expan</td><td class="right">0</td><td class="right">0</td><td class="right">1837</td><td class="right">0</td><td class="right">69</td><td class="right">170397</td><td>editorial</td><td/></tr><tr itemprop="row"><td>extent</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>figDesc</td><td class="right">151116</td><td class="right">0</td><td class="right">55</td><td class="right">87</td><td class="right">0</td><td class="right">27314</td><td>pictures</td><td/></tr><tr itemprop="row"><td>figure</td><td class="right">329174</td><td class="right">206</td><td class="right">480</td><td class="right">227</td><td class="right">16866</td><td class="right">95853</td><td>pictures</td><td/></tr><tr itemprop="row"><td>fileDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>floatingText</td><td class="right">0</td><td class="right">1</td><td class="right">0</td><td class="right">61</td><td class="right">307</td><td class="right">40502</td><td>structure</td><td/></tr><tr itemprop="row"><td>foreign</td><td class="right">0</td><td class="right">46</td><td class="right">3348</td><td class="right">2365</td><td class="right">1929</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>forename</td><td class="right">0</td><td class="right">1</td><td class="right">35</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>formula</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">25670</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>front</td><td class="right">13</td><td class="right">25</td><td class="right">48</td><td class="right">380</td><td class="right">851</td><td class="right">49991</td><td>structure</td><td/></tr><tr itemprop="row"><td>fw</td><td class="right">0</td><td class="right">0</td><td class="right">20554</td><td class="right">15</td><td class="right">336239</td><td class="right">1268</td><td>structure</td><td/></tr><tr itemprop="row"><td>g</td><td class="right">0</td><td class="right">0</td><td class="right">1012</td><td class="right">489</td><td class="right">493</td><td class="right">915406</td><td>character</td><td/></tr><tr itemprop="row"><td>gap</td><td class="right">0</td><td class="right">0</td><td class="right">18</td><td class="right">293</td><td class="right">5731</td><td class="right">6878505</td><td>editorial</td><td/></tr><tr itemprop="row"><td>genName</td><td class="right">0</td><td class="right">0</td><td class="right">7</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>gi</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>glyph</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>glyphName</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>graphic</td><td class="right">0</td><td class="right">22</td><td class="right">362</td><td class="right">199</td><td class="right">0</td><td class="right">0</td><td>pictures</td><td/></tr><tr itemprop="row"><td>group</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">20</td><td class="right">0</td><td class="right">2789</td><td>structure</td><td/></tr><tr itemprop="row"><td>handShift</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>head</td><td class="right">1958142</td><td class="right">4961</td><td class="right">2526</td><td class="right">14508</td><td class="right">117506</td><td class="right">1811315</td><td>structure</td><td/></tr><tr itemprop="row"><td>hi</td><td class="right">21179130</td><td class="right">56953</td><td class="right">9424</td><td class="right">134872</td><td class="right">2367314</td><td class="right">57472111</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>idno</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>imprimatur</td><td class="right">0</td><td class="right">0</td><td class="right">25</td><td class="right">23</td><td class="right">63</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>imprint</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>item</td><td class="right">3125926</td><td class="right">2023</td><td class="right">1806</td><td class="right">12400</td><td class="right">187951</td><td class="right">3779020</td><td>structure</td><td/></tr><tr itemprop="row"><td>keywords</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>l</td><td class="right">11532201</td><td class="right">21004</td><td class="right">39828</td><td class="right">268768</td><td class="right">557846</td><td class="right">11307818</td><td>structure</td><td/></tr><tr itemprop="row"><td>label</td><td class="right">483377</td><td class="right">621</td><td class="right">469</td><td class="right">1712</td><td class="right">0</td><td class="right">618039</td><td>structure</td><td/></tr><tr itemprop="row"><td>lb</td><td class="right">1352720</td><td class="right">3008</td><td class="right">237202</td><td class="right">233546</td><td class="right">9689271</td><td class="right">24097</td><td>structure</td><td/></tr><tr itemprop="row"><td>lg</td><td class="right">528349</td><td class="right">316</td><td class="right">4481</td><td class="right">5790</td><td class="right">84157</td><td class="right">791590</td><td>structure</td><td/></tr><tr itemprop="row"><td>licence</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>list</td><td class="right">272365</td><td class="right">621</td><td class="right">115</td><td class="right">526</td><td class="right">24877</td><td class="right">407478</td><td>structure</td><td/></tr><tr itemprop="row"><td>listBibl</td><td class="right">0</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td class="right">26</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>listChange</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>listPerson</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>localName</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>measure</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>milestone</td><td class="right">0</td><td class="right">46</td><td class="right">13</td><td class="right">4881</td><td class="right">49313</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>monogr</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>msDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>msIdentifier</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>name</td><td class="right">536288</td><td class="right">12265</td><td class="right">32997</td><td class="right">2541</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>nameLink</td><td class="right">0</td><td class="right">0</td><td class="right">18</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>note</td><td class="right">2705214</td><td class="right">9451</td><td class="right">2874</td><td class="right">4965</td><td class="right">187675</td><td class="right">5710304</td><td>structure</td><td/></tr><tr itemprop="row"><td>num</td><td class="right">0</td><td class="right">862</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>opener</td><td class="right">0</td><td class="right">0</td><td class="right">2</td><td class="right">21</td><td class="right">513</td><td class="right">77640</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>orgName</td><td class="right">0</td><td class="right">30</td><td class="right">4607</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>orig</td><td class="right">0</td><td class="right">0</td><td class="right">57301</td><td class="right">274</td><td class="right">2769</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>p</td><td class="right">12413479</td><td class="right">68273</td><td class="right">4855</td><td class="right">391507</td><td class="right">607881</td><td class="right">11892546</td><td>structure</td><td/></tr><tr itemprop="row"><td>pb</td><td class="right">2814727</td><td class="right">6156</td><td class="right">9497</td><td class="right">22352</td><td class="right">311001</td><td class="right">5424219</td><td>structure</td><td/></tr><tr itemprop="row"><td>pc</td><td class="right">0</td><td class="right">0</td><td class="right">230</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>linguistic</td><td/></tr><tr itemprop="row"><td>persName</td><td class="right">0</td><td class="right">4045</td><td class="right">662</td><td class="right">0</td><td class="right">26217</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>person</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>physDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>placeName</td><td class="right">0</td><td class="right">386</td><td class="right">11646</td><td class="right">0</td><td class="right">18652</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>postscript</td><td class="right">0</td><td class="right">17</td><td class="right">0</td><td class="right">0</td><td class="right">133</td><td class="right">6142</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>profileDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>ptr</td><td class="right">376134</td><td class="right">0</td><td class="right">0</td><td class="right">180</td><td class="right">0</td><td class="right">635</td><td> </td><td><span class="gi"><ref></span></td></tr><tr itemprop="row"><td>pubPlace</td><td class="right">0</td><td class="right">0</td><td class="right">37</td><td class="right">2</td><td class="right">918</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>publicationStmt</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>publisher</td><td class="right">0</td><td class="right">2</td><td class="right">35</td><td class="right">0</td><td class="right">910</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>q</td><td class="right">212432</td><td class="right">4270</td><td class="right">29</td><td class="right">5829</td><td class="right">0</td><td class="right">695548</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>quote</td><td class="right">0</td><td class="right">5459</td><td class="right">270</td><td class="right">2597</td><td class="right">5744</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>ref</td><td class="right">537332</td><td class="right">240</td><td class="right">1119</td><td class="right">1240</td><td class="right">140328</td><td class="right">3541</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>reg</td><td class="right">442</td><td class="right">0</td><td class="right">57311</td><td class="right">274</td><td class="right">2765</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>relatedItem</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>repository</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>resp</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>respStmt</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>rhyme</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>role</td><td class="right">0</td><td class="right">0</td><td class="right">33</td><td class="right">31</td><td class="right">735</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>roleDesc</td><td class="right">0</td><td class="right">0</td><td class="right">9</td><td class="right">0</td><td class="right">70</td><td class="right">0</td><td>castlist</td><td/></tr><tr itemprop="row"><td>roleName</td><td class="right">0</td><td class="right">0</td><td class="right">70</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>row</td><td class="right">2064752</td><td class="right">70</td><td class="right">1311</td><td class="right">327</td><td class="right">12571</td><td class="right">799618</td><td>table</td><td/></tr><tr itemprop="row"><td>rs</td><td class="right">1</td><td class="right">5</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>s</td><td class="right">1</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>linguistic</td><td/></tr><tr itemprop="row"><td>salute</td><td class="right">0</td><td class="right">11</td><td class="right">10</td><td class="right">97</td><td class="right">2490</td><td class="right">64544</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>seg</td><td class="right">46611</td><td class="right">47</td><td class="right">0</td><td class="right">10304</td><td class="right">0</td><td class="right">148733</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>sic</td><td class="right">0</td><td class="right">0</td><td class="right">3707</td><td class="right">534</td><td class="right">5960</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>signed</td><td class="right">93</td><td class="right">33</td><td class="right">37</td><td class="right">118</td><td class="right">48</td><td class="right">106105</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>soCalled</td><td class="right">2</td><td class="right">0</td><td class="right">0</td><td class="right">12</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><q></span></td></tr><tr itemprop="row"><td>sourceDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>sp</td><td class="right">320117</td><td class="right">12</td><td class="right">1997</td><td class="right">76237</td><td class="right">42050</td><td class="right">1661335</td><td>structure</td><td/></tr><tr itemprop="row"><td>spGrp</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">35</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>space</td><td class="right">0</td><td class="right">1044</td><td class="right">19559</td><td class="right">0</td><td class="right">20962</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>speaker</td><td class="right">304183</td><td class="right">12</td><td class="right">1978</td><td class="right">76198</td><td class="right">42021</td><td class="right">1652394</td><td>structure</td><td/></tr><tr itemprop="row"><td>stage</td><td class="right">60645</td><td class="right">39</td><td class="right">17</td><td class="right">10195</td><td class="right">14041</td><td class="right">246384</td><td>structure</td><td/></tr><tr itemprop="row"><td>subst</td><td class="right">0</td><td class="right">0</td><td class="right">11</td><td class="right">0</td><td class="right">0</td><td class="right">2</td><td>editorial</td><td/></tr><tr itemprop="row"><td>supplied</td><td class="right">0</td><td class="right">0</td><td class="right">34</td><td class="right">0</td><td class="right">11095</td><td class="right">0</td><td>editorial</td><td/></tr><tr itemprop="row"><td>surname</td><td class="right">0</td><td class="right">490</td><td class="right">38</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td> </td><td><span class="gi"><name></span></td></tr><tr itemprop="row"><td>table</td><td class="right">164693</td><td class="right">7</td><td class="right">103</td><td class="right">19</td><td class="right">5219</td><td class="right">43935</td><td>table</td><td/></tr><tr itemprop="row"><td>tag</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>teiCorpus</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>teiHeader</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>term</td><td class="right">1451</td><td class="right">113</td><td class="right">181</td><td class="right">51</td><td class="right">0</td><td class="right">0</td><td>header</td><td><span class="gi"><seg></span></td></tr><tr itemprop="row"><td>text</td><td class="right">10171</td><td class="right">126</td><td class="right">50</td><td class="right">645</td><td class="right">848</td><td class="right">69238</td><td>structure</td><td/></tr><tr itemprop="row"><td>textClass</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>textDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>time</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>interpretation</td><td/></tr><tr itemprop="row"><td>title</td><td class="right">208735</td><td class="right">6583</td><td class="right">88</td><td class="right">265</td><td class="right">0</td><td class="right">0</td><td>structure</td><td/></tr><tr itemprop="row"><td>titlePage</td><td class="right">0</td><td class="right">1</td><td class="right">48</td><td class="right">359</td><td class="right">1097</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>titlePart</td><td class="right">0</td><td class="right">1</td><td class="right">85</td><td class="right">467</td><td class="right">2399</td><td class="right">0</td><td>titlepage</td><td/></tr><tr itemprop="row"><td>titleStmt</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>trailer</td><td class="right">0</td><td class="right">2</td><td class="right">104</td><td class="right">230</td><td class="right">363</td><td class="right">69313</td><td>wrapper</td><td/></tr><tr itemprop="row"><td>typeDesc</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>unclear</td><td class="right">0</td><td class="right">1</td><td class="right">117</td><td class="right">2658</td><td class="right">0</td><td class="right">4038</td><td>editorial</td><td/></tr><tr itemprop="row"><td>val</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>value</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>header</td><td/></tr><tr itemprop="row"><td>w</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td class="right">0</td><td>linguistic</td><td/></tr></table></div><dl itemprop="list"><dt><span itemprop="label">castlist</span></dt><dd><span class="gi"><actor></span> <span class="gi"><castGroup></span> <span class="gi"><castItem></span> <span class="gi"><castList></span> <span class="gi"><role></span> <span class="gi"><roleDesc></span></dd><dt><span itemprop="label">character</span></dt><dd><span class="gi"><g></span></dd><dt><span itemprop="label">editorial</span></dt><dd><span class="gi"><abbr></span> <span class="gi"><add></span> <span class="gi"><addSpan></span> <span class="gi"><am></span> <span class="gi"><choice></span> <span class="gi"><corr></span> <span class="gi"><del></span> <span class="gi"><desc></span> <span class="gi"><ex></span> <span class="gi"><expan></span> <span class="gi"><gap></span> <span class="gi"><handShift></span> <span class="gi"><orig></span> <span class="gi"><reg></span> <span class="gi"><sic></span> <span class="gi"><space></span> <span class="gi"><subst></span> <span class="gi"><supplied></span> <span class="gi"><unclear></span></dd><dt><span itemprop="label">header</span></dt><dd><span class="gi"><att></span> <span class="gi"><biblFull></span> <span class="gi"><biblScope></span> <span class="gi"><biblStruct></span> <span class="gi"><change></span> <span class="gi"><charDecl></span> <span class="gi"><charProp></span> <span class="gi"><editor></span> <span class="gi"><editorialDecl></span> <span class="gi"><email></span> <span class="gi"><encodingDesc></span> <span class="gi"><extent></span> <span class="gi"><fileDesc></span> <span class="gi"><gi></span> <span class="gi"><glyph></span> <span class="gi"><glyphName></span> <span class="gi"><idno></span> <span class="gi"><imprint></span> <span class="gi"><keywords></span> <span class="gi"><licence></span> <span class="gi"><listChange></span> <span class="gi"><listPerson></span> <span class="gi"><localName></span> <span class="gi"><monogr></span> <span class="gi"><msDesc></span> <span class="gi"><msIdentifier></span> <span class="gi"><person></span> <span class="gi"><physDesc></span> <span class="gi"><profileDesc></span> <span class="gi"><publicationStmt></span> <span class="gi"><relatedItem></span> <span class="gi"><repository></span> <span class="gi"><resp></span> <span class="gi"><respStmt></span> <span class="gi"><sourceDesc></span> <span class="gi"><tag></span> <span class="gi"><teiHeader></span> <span class="gi"><term></span> <span class="gi"><textClass></span> <span class="gi"><textDesc></span> <span class="gi"><titleStmt></span> <span class="gi"><typeDesc></span> <span class="gi"><val></span> <span class="gi"><value></span></dd><dt><span itemprop="label">interpretation</span></dt><dd><span class="gi"><author></span> <span class="gi"><date></span> <span class="gi"><foreign></span> <span class="gi"><hi></span> <span class="gi"><measure></span> <span class="gi"><name></span> <span class="gi"><num></span> <span class="gi"><q></span> <span class="gi"><quote></span> <span class="gi"><ref></span> <span class="gi"><rhyme></span> <span class="gi"><rs></span> <span class="gi"><seg></span> <span class="gi"><time></span></dd><dt><span itemprop="label">linguistic</span></dt><dd><span class="gi"><c></span> <span class="gi"><pc></span> <span class="gi"><s></span> <span class="gi"><w></span></dd><dt><span itemprop="label">pictures</span></dt><dd><span class="gi"><figDesc></span> <span class="gi"><figure></span> <span class="gi"><graphic></span></dd><dt><span itemprop="label">structure</span></dt><dd><span class="gi"><ab></span> <span class="gi"><address></span> <span class="gi"><addrLine></span> <span class="gi"><anchor></span> <span class="gi"><back></span> <span class="gi"><bibl></span> <span class="gi"><body></span> <span class="gi"><cb></span> <span class="gi"><cit></span> <span class="gi"><div></span> <span class="gi"><floatingText></span> <span class="gi"><formula></span> <span class="gi"><front></span> <span class="gi"><fw></span> <span class="gi"><group></span> <span class="gi"><head></span> <span class="gi"><item></span> <span class="gi"><l></span> <span class="gi"><label></span> <span class="gi"><lb></span> <span class="gi"><lg></span> <span class="gi"><list></span> <span class="gi"><listBibl></span> <span class="gi"><milestone></span> <span class="gi"><note></span> <span class="gi"><p></span> <span class="gi"><pb></span> <span class="gi"><sp></span> <span class="gi"><speaker></span> <span class="gi"><spGrp></span> <span class="gi"><stage></span> <span class="gi"><TEI></span> <span class="gi"><teiCorpus></span> <span class="gi"><text></span> <span class="gi"><title></span></dd><dt><span itemprop="label">table</span></dt><dd><span class="gi"><cell></span> <span class="gi"><row></span> <span class="gi"><table></span></dd><dt><span itemprop="label">titlepage</span></dt><dd><span class="gi"><docAuthor></span> <span class="gi"><docDate></span> <span class="gi"><docEdition></span> <span class="gi"><docImprint></span> <span class="gi"><docTitle></span> <span class="gi"><imprimatur></span> <span class="gi"><publisher></span> <span class="gi"><pubPlace></span> <span class="gi"><titlePage></span> <span class="gi"><titlePart></span></dd><dt><span itemprop="label">wrapper</span></dt><dd><span class="gi"><argument></span> <span class="gi"><byline></span> <span class="gi"><closer></span> <span class="gi"><dateline></span> <span class="gi"><epigraph></span> <span class="gi"><opener></span> <span class="gi"><postscript></span> <span class="gi"><salute></span> <span class="gi"><signed></span> <span class="gi"><trailer></span></dd></dl></div><div class="teidiv1" id="index.xml-body.1_div.6_div.2"><h2><span class="headingNumber">6.2. </span><span class="head" itemprop="head">The TEI infrastructure</span></h2><p><b>Specification group [base]</b></p><table class="border"><tr><td>Module: tei</td></tr></table></div><div class="teidiv1" id="index.xml-body.1_div.6_div.3"><h2><span class="headingNumber">6.3. </span><span class="head" itemprop="head">The header</span></h2><p>The default set of elements for the header are loaded using the <span class="term" itemprop="term">header</span> module. In addition, elements from other modules are loaded, if they are tagged in the classification as being needed for the header only.</p><p><b>Specification group [header]</b></p><table class="border"><tr><td>Module: header</td></tr><tr><td>+ <att></td></tr><tr><td>+ <biblFull></td></tr><tr><td>+ <biblScope></td></tr><tr><td>+ <biblStruct></td></tr><tr><td>+ <change></td></tr><tr><td>+ <charDecl></td></tr><tr><td>+ <charProp></td></tr><tr><td>+ <editor></td></tr><tr><td>+ <editorialDecl></td></tr><tr><td>+ <email></td></tr><tr><td>+ <encodingDesc></td></tr><tr><td>+ <extent></td></tr><tr><td>+ <fileDesc></td></tr><tr><td>+ <gi></td></tr><tr><td>+ <glyph></td></tr><tr><td>+ <glyphName></td></tr><tr><td>+ <idno></td></tr><tr><td>+ <imprint></td></tr><tr><td>+ <keywords></td></tr><tr><td>+ <licence></td></tr><tr><td>+ <listChange></td></tr><tr><td>+ <listPerson></td></tr><tr><td>+ <localName></td></tr><tr><td>+ <monogr></td></tr><tr><td>+ <msDesc></td></tr><tr><td>+ <msIdentifier></td></tr><tr><td>+ <person></td></tr><tr><td>+ <physDesc></td></tr><tr><td>+ <profileDesc></td></tr><tr><td>+ <publicationStmt></td></tr><tr><td>+ <relatedItem></td></tr><tr><td>+ <repository></td></tr><tr><td>+ <resp></td></tr><tr><td>+ <respStmt></td></tr><tr><td>+ <sourceDesc></td></tr><tr><td>+ <tag></td></tr><tr><td>+ <teiHeader></td></tr><tr><td>+ <term></td></tr><tr><td>+ <textClass></td></tr><tr><td>+ <textDesc></td></tr><tr><td>+ <titleStmt></td></tr><tr><td>+ <typeDesc></td></tr><tr><td>+ <val></td></tr><tr><td>+ <value></td></tr></table><p><b>Specification group [header2]</b></p><table class="border"><tr><td colspan="3" class="norules">Elements which are only intended to be used in the header are banned from the <span class="gi"><text></span>, using a Schematron rule.</td></tr><tr><td><<span class="orange">text</span>></td><td><table class="border"><tr><td>[#headeronlyelement]</td><td><div id="index.xml-egXML-d8271e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:rule <span class="attribute">context</span>="<span class="attributevalue">tei:att | tei:biblFull | tei:biblScope | tei:biblStruct | tei:change
| tei:charDecl | tei:charProp | tei:editor | tei:editorialDecl | tei:email
| tei:encodingDesc | tei:extent | tei:fileDesc | tei:gi | tei:glyph
| tei:glyphName | tei:idno | tei:imprint | tei:keywords | tei:licence
| tei:listChange | tei:listPerson | tei:localName | tei:monogr | tei:msDesc
| tei:msIdentifier | tei:person | tei:physDesc | tei:profileDesc |
tei:publicationStmt | tei:relatedItem | tei:repository | tei:resp
| tei:respStmt | tei:sourceDesc | tei:tag | tei:teiHeader | tei:term
| tei:textClass | tei:textDesc | tei:titleStmt | tei:typeDesc | tei:val
| tei:value</span>"></span>
<span class="element"><s:report <span class="attribute">test</span>="<span class="attributevalue">ancestor::tei:text</span>"></span>Error: The element <span class="element"><s:name/></span> is not permitted outside the header<span class="element"></s:report></span><span class="element"></s:rule></span><span class="element"></constraint></span></div></td></tr></table></td></tr></table></div><div class="teidiv1" id="index.xml-body.1_div.6_div.4"><h2><span class="headingNumber">6.4. </span><span class="head" itemprop="head">Transcription</span></h2><p>In order to support the <span class="gi"><sourcedoc></span> and <span class="gi"><facsimile></span> elements, the basic transcriptional elements are loaded, and two attribute classes.</p><p><b>Specification group [transcr]</b></p><table class="border"><tr><td>+ <damage></td></tr><tr><td>+ <damageSpan></td></tr><tr><td>+ <facsimile></td></tr><tr><td>+ <line></td></tr><tr><td>+ <listTranspose></td></tr><tr><td>+ <metamark></td></tr><tr><td>+ <mod></td></tr><tr><td>+ <redo></td></tr><tr><td>+ <restore></td></tr><tr><td>+ <retrace></td></tr><tr><td>+ <sourceDoc></td></tr><tr><td>+ <surface></td></tr><tr><td>+ <surfaceGrp></td></tr><tr><td>+ <surplus></td></tr><tr><td>+ <transpose></td></tr><tr><td>+ <undo></td></tr><tr><td>+ <zone></td></tr><tr><td>+ att.coordinated</td></tr><tr><td>+ att.global.change</td></tr></table></div><div class="teidiv1" id="index.xml-body.1_div.6_div.5"><h2><span class="headingNumber">6.5. </span><span class="head" itemprop="head">Attribute classes</span></h2><p><b>Specification group [attclasses]</b></p><table class="border"><tr><td colspan="3" class="norules">The <span class="term" itemprop="term">tei</span> module brings with it a default set of attribute classes. We need some more specialist ones from other modules, and to delete some default ones which we don't plan to use.</td></tr><tr><td>+ att.global.analytic</td></tr><tr><td>+ att.global.facs</td></tr><tr><td>+ att.milestoneUnit</td></tr><tr><td>+ att.global.linking</td></tr><tr><td><span class="red del">att.datcat</span></td><td/></tr><tr><td><span class="red del">att.declarable</span></td><td/></tr><tr><td><span class="red del">att.divLike</span></td><td/></tr><tr><td colspan="3" class="norules">Some uncommon attributes are removed from global linking.</td></tr><tr><td><span class="orange">att.global.linking</span></td><td><table class="border"><tr><td>@<span class="red del">synch</span></td><td/></tr><tr><td>@<span class="red del">copyOf</span></td><td/></tr><tr><td>@<span class="red del">exclude</span></td><td/></tr><tr><td>@<span class="red del">select</span></td><td/></tr></table></td></tr><tr><td colspan="3" class="norules">URLs have a constraint that a local pointer must have a corresponding ID.</td></tr><tr><td><span class="orange">att.pointing</span></td><td><table class="border"><tr><td>@<span class="orange">target</span></td><td><table class="border"><tr><td>[#validtarget]</td><td><div id="index.xml-egXML-d8334e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:rule <span class="attribute">context</span>="<span class="attributevalue">tei:*[@target]</span>"></span>
<span class="element"><s:let <span class="attribute">name</span>="<span class="attributevalue">results</span>"
<span class="attribute">value</span>="<span class="attributevalue">for $t in tokenize(normalize-space(@target),'\s+') return starts-with($t,'#')
and not(id(substring($t,2)))</span>"/></span>
<span class="element"><s:report <span class="attribute">test</span>="<span class="attributevalue">some $x in $results satisfies $x</span>"></span> Error: Every local pointer in "<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">@target</span>"/></span>" must point to an ID in this document (<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">$results</span>"/></span>)<span class="element"></s:report></span><span class="element"></s:rule></span><span class="element"></constraint></span></div></td></tr></table></td></tr></table></td></tr><tr><td colspan="3" class="norules">Constrained value lists are added to attribute classes where possible.</td></tr><tr><td><span class="orange">att.placement</span></td><td><table class="border"><tr><td>@<span class="orange">place</span></td><td><table class="border"><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">above</span></td><td>above the line</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">below</span></td><td>below the line</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">top</span></td><td>at the top of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">top-right</span></td><td>at the top right of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">top-left</span></td><td>at the top left of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">top-centre</span></td><td>at the top center of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">bottom-right</span></td><td>at the bottom right of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">bottom-left</span></td><td>at the bottom left of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">bottom-centre</span></td><td>at the bottom centre of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">bottom</span></td><td>at the foot of the page</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">tablebottom</span></td><td>underneath a table</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">margin-right</span></td><td>in the right-hand margin</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">margin</span></td><td>in the outer margin</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">margin-inner</span></td><td>in the inner margin</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">margin-left</span></td><td>in the left-hand margin</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">opposite</span></td><td>on the opposite, i.e. facing, page.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">overleaf</span></td><td>on the other side of the leaf.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">overstrike</span></td><td>superimposed on top of the current context</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">end</span></td><td>at the end of the volume.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">divend</span></td><td>at the end the current division.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">parend</span></td><td>at the end the current paragraph.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">inline</span></td><td>within the body of the text.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">inspace</span></td><td>in a predefined space, for example left by an earlier scribe.</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">block</span></td><td>formatted as an indented paragraph</td></tr></table></td></tr></table></td></tr><tr><td><span class="orange">att.dimensions</span></td><td><table class="border"><tr><td>@<span class="orange">unit</span></td><td><table class="border"><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">chars</span></td><td>characters</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">lines</span></td><td>lines</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">pages</span></td><td>pages</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">words</span></td><td>words</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">cm</span></td><td>centimetres</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">mm</span></td><td>millimetre</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">in</span></td><td>inches</td></tr></table></td></tr></table></td></tr><tr><td><span class="orange">att.global.rendition</span></td><td><table class="border"><tr><td>[#renditionpointer]</td><td><div id="index.xml-egXML-d8381e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:rule <span class="attribute">context</span>="<span class="attributevalue">tei:*[@rendition]</span>"></span>
<span class="element"><s:let <span class="attribute">name</span>="<span class="attributevalue">results</span>"
<span class="attribute">value</span>="<span class="attributevalue">for $val in tokenize(normalize-space(@rendition),'\s+') return
starts-with($val,'simple:') or (starts-with($val,'#')
and //tei:rendition[@xml:id=substring($val,2)])</span>"/></span>
<span class="element"><s:assert <span class="attribute">test</span>="<span class="attributevalue">every $x in $results satisfies $x</span>"></span> Error: Each of the rendition values in "<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">@rendition</span>"/></span>" must point to a local ID or to a token in the Simple scheme (<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">$results</span>"/></span>)<span class="element"></s:assert></span><span class="element"></s:rule></span><span class="element"></constraint></span></div></td></tr><tr><td>[#corresppointer]</td><td><div id="index.xml-egXML-d8428e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:rule <span class="attribute">context</span>="<span class="attributevalue">tei:*[@corresp]</span>"></span>
<span class="element"><s:let <span class="attribute">name</span>="<span class="attributevalue">results</span>"
<span class="attribute">value</span>="<span class="attributevalue">for $t in tokenize(normalize-space(@corresp),'\s+') return
starts-with($t,'#') and not(id(substring($t,2)))</span>"/></span>
<span class="element"><s:report <span class="attribute">test</span>="<span class="attributevalue">some $x in $results satisfies $x</span>"></span> Error: Every local pointer in "<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">@corresp</span>"/></span>" must point to an ID in this document (<span class="element"><s:value-of <span class="attribute">select</span>="<span class="attributevalue">$results</span>"/></span>)<span class="element"></s:report></span><span class="element"></s:rule></span><span class="element"></constraint></span></div></td></tr><tr><td>@<span class="red del">rend</span></td><td/></tr><tr><td>@<span class="red del">style</span></td><td/></tr><tr><td>@<span class="orange">rendition</span></td><td><table class="border"><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:allcaps</span></td><td>all capitals</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:blackletter</span></td><td>black letter or gothic typeface</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:bold</span></td><td>bold typeface</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:bottombraced</span></td><td>marked with a brace under the bottom of the text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:boxed</span></td><td>border around the text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:centre</span></td><td>centred</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:cursive</span></td><td>cursive typeface</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:display</span></td><td>block display</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:doublestrikethrough</span></td><td>strikethrough with double line</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:doubleunderline</span></td><td>underlined with double line</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:dropcap</span></td><td>initial letter larger or decorated</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:float</span></td><td>floated out of main flow</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:hyphen</span></td><td>with a hyphen here (eg in line break)</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:inline</span></td><td>inline rendering</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:justify</span></td><td>justified text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:italic</span></td><td>italic typeface</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:larger</span></td><td>larger type</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:left</span></td><td>aligned to the left or left-justified</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:leftbraced</span></td><td>marked with a brace on the left side of the text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:letterspace</span></td><td>larger-than-normal spacing between letters, usually for emphasis</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:literal</span></td><td>fixed-width typeface, spacing preserved</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:normalstyle</span></td><td>upright shape and default weight of typeface</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:normalweight</span></td><td>normal typeface weight</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:right</span></td><td>aligned to the right or right-justified</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:rightbraced</span></td><td>marked with a brace to the right of the text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:rotateleft</span></td><td>rotated to the left</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:rotateright</span></td><td>rotated to the right</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:smallcaps</span></td><td>small caps</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:smaller</span></td><td>smaller type</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:strikethrough</span></td><td>strike through</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:subscript</span></td><td>subscript</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:superscript</span></td><td>superscript</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:topbraced</span></td><td>marked with a brace above the text</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:typewriter</span></td><td>fixed-width typeface, like typewriter</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:underline</span></td><td>underlined with single line</td></tr><tr xmlns=""><td><span xmlns="http://www.w3.org/1999/xhtml" class="green">simple:wavyunderline</span></td><td>underlined with wavy line</td></tr></table></td></tr></table></td></tr></table></div><div class="teidiv1" id="index.xml-body.1_div.6_div.6"><h2><span class="headingNumber">6.6. </span><span class="head" itemprop="head">Model classes</span></h2><p><b>Specification group [modelclasses]</b></p><table class="border"><tr><td colspan="3" class="norules">A set of unused model classes are removed.</td></tr><tr><td><span class="red del">model.entryPart</span></td><td/></tr><tr><td><span class="red del">model.placeNamePart</span></td><td/></tr><tr><td><span class="red del">model.placeStateLike</span></td><td/></tr><tr><td><span class="red del">model.egLike</span></td><td/></tr><tr><td><span class="red del">model.offsetLike</span></td><td/></tr><tr><td><span class="red del">model.pPart.msdesc</span></td><td/></tr><tr><td><span class="red del">model.oddDecl</span></td><td/></tr><tr><td><span class="red del">model.specDescLike</span></td><td/></tr><tr><td><span class="red del">model.entryPart</span></td><td/></tr><tr><td><span class="red del">model.placeNamePart</span></td><td/></tr><tr><td><span class="red del">model.placeStateLike</span></td><td/></tr><tr><td><span class="red del">model.certLike</span></td><td/></tr><tr><td><span class="red del">model.glossLike</span></td><td/></tr></table></div><div class="teidiv1" id="index.xml-body.1_div.6_div.7"><h2><span class="headingNumber">6.7. </span><span class="head" itemprop="head">Elements</span></h2><p>The main part of Simple is the set of selected elements.</p><p><b>Specification group [simpleelements]</b></p><table class="border"><tr><td>+ <ab></td></tr><tr><td>+ <abbr></td></tr><tr><td>+ <actor></td></tr><tr><td>+ <add></td></tr><tr><td>+ <address></td></tr><tr><td>+ <addrLine></td></tr><tr><td>+ <addSpan></td></tr><tr><td>+ <am></td></tr><tr><td>+ <anchor></td></tr><tr><td>+ <argument></td></tr><tr><td>+ <author></td></tr><tr><td>+ <back></td></tr><tr><td>+ <bibl></td></tr><tr><td>+ <body></td></tr><tr><td>+ <byline></td></tr><tr><td>+ <c></td></tr><tr><td>+ <castGroup></td></tr><tr><td>+ <castItem></td></tr><tr><td>+ <castList></td></tr><tr><td>+ <cb></td></tr><tr><td>+ <cell></td></tr><tr><td>+ <choice></td></tr><tr><td>+ <cit></td></tr><tr><td>+ <closer></td></tr><tr><td>+ <corr></td></tr><tr><td>+ <date></td></tr><tr><td>+ <dateline></td></tr><tr><td>+ <del></td></tr><tr><td>+ <desc></td></tr><tr><td>+ <div></td></tr><tr><td>+ <docAuthor></td></tr><tr><td>+ <docDate></td></tr><tr><td>+ <docEdition></td></tr><tr><td>+ <docImprint></td></tr><tr><td>+ <docTitle></td></tr><tr><td>+ <epigraph></td></tr><tr><td>+ <ex></td></tr><tr><td>+ <expan></td></tr><tr><td>+ <figDesc></td></tr><tr><td>+ <figure></td></tr><tr><td>+ <floatingText></td></tr><tr><td>+ <foreign></td></tr><tr><td>+ <formula></td></tr><tr><td>+ <front></td></tr><tr><td>+ <fw></td></tr><tr><td>+ <g></td></tr><tr><td>+ <gap></td></tr><tr><td>+ <graphic></td></tr><tr><td>+ <group></td></tr><tr><td>+ <handShift></td></tr><tr><td>+ <head></td></tr><tr><td>+ <hi></td></tr><tr><td>+ <imprimatur></td></tr><tr><td>+ <item></td></tr><tr><td>+ <l></td></tr><tr><td>+ <label></td></tr><tr><td>+ <lb></td></tr><tr><td>+ <lg></td></tr><tr><td>+ <list></td></tr><tr><td>+ <listBibl></td></tr><tr><td>+ <measure></td></tr><tr><td>+ <milestone></td></tr><tr><td>+ <name></td></tr><tr><td>+ <note></td></tr><tr><td>+ <num></td></tr><tr><td>+ <opener></td></tr><tr><td>+ <orig></td></tr><tr><td>+ <p></td></tr><tr><td>+ <pb></td></tr><tr><td>+ <pc></td></tr><tr><td>+ <postscript></td></tr><tr><td>+ <publisher></td></tr><tr><td>+ <pubPlace></td></tr><tr><td>+ <q></td></tr><tr><td>+ <quote></td></tr><tr><td>+ <ref></td></tr><tr><td>+ <reg></td></tr><tr><td>+ <rhyme></td></tr><tr><td>+ <role></td></tr><tr><td>+ <roleDesc></td></tr><tr><td>+ <row></td></tr><tr><td>+ <rs></td></tr><tr><td>+ <s></td></tr><tr><td>+ <salute></td></tr><tr><td>+ <seg></td></tr><tr><td>+ <sic></td></tr><tr><td>+ <signed></td></tr><tr><td>+ <sp></td></tr><tr><td>+ <space></td></tr><tr><td>+ <speaker></td></tr><tr><td>+ <spGrp></td></tr><tr><td>+ <stage></td></tr><tr><td>+ <subst></td></tr><tr><td>+ <supplied></td></tr><tr><td>+ <table></td></tr><tr><td>+ <TEI></td></tr><tr><td>+ <teiCorpus></td></tr><tr><td>+ <text></td></tr><tr><td>+ <time></td></tr><tr><td>+ <title></td></tr><tr><td>+ <titlePage></td></tr><tr><td>+ <titlePart></td></tr><tr><td>+ <trailer></td></tr><tr><td>+ <unclear></td></tr><tr><td>+ <w></td></tr></table><p><b>Specification group [simpleelementspm]</b></p><table class="border"><tr><td><<span class="orange">ab</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>paragraph</td></tr></table></td></tr><tr><td><<span class="orange">abbr</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">actor</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">add</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">address</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">addrLine</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">addSpan</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>anchor</td></tr></table></td></tr><tr><td><<span class="orange">am</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">anchor</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>anchor</td></tr></table></td></tr><tr><td><<span class="orange">argument</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">author</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>ancestor::teiHeader ; omit</td></tr><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">back</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">bibl</span>></td><td><table class="border"><tr><td>[#noEmptyBibl]</td><td><div id="index.xml-egXML-d8506e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:assert <span class="attribute">test</span>="<span class="attributevalue">child::* or child::text()[normalize-space()]</span>"
<span class="attribute">role</span>="<span class="attributevalue">ERROR</span>"></span> Element "<span class="element"><s:name/></span>" may not be
empty. <span class="element"></s:assert></span><span class="element"></constraint></span></div></td></tr><tr><td>[model] <i/></td><td>parent::listBibl ; listItem</td></tr><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">body</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>index</td></tr> <tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">byline</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>block</td></tr></table></td></tr><tr><td><<span class="orange">c</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>inline</td></tr></table></td></tr><tr><td><<span class="orange">castGroup</span>></td><td><table class="border"><tr><td>[model] <i>Insert list. </i></td><td>child::* ; list</td></tr></table></td></tr><tr><td><<span class="orange">castItem</span>></td><td><table class="border"><tr><td>[model] <i>Insert item, rendered as described in parent list rendition. </i></td><td>listItem</td></tr></table></td></tr><tr><td><<span class="orange">castList</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>child::* ; list</td></tr></table></td></tr><tr><td><<span class="orange">cb</span>></td><td><table class="border"><tr><td>[model] <i/></td><td>break</td></tr></table></td></tr><tr><td><<span class="orange">cell</span>></td><td><table class="border"><tr><td>[model] <i>Insert table cell. </i></td><td>cell</td></tr></table></td></tr><tr><td><<span class="orange">choice</span>></td><td><table class="border"><tr><td>[#choiceSize]</td><td><div id="index.xml-egXML-d8531e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:assert <span class="attribute">test</span>="<span class="attributevalue">count(*) > 1</span>" <span class="attribute">role</span>="<span class="attributevalue">ERROR</span>"></span> Element
"<span class="element"><s:name/></span>" must have at least two child elements.<span class="element"></s:assert></span><span class="element"></constraint></span></div></td></tr><tr><td>[#choiceContent]</td><td><div id="index.xml-egXML-d8557e1" class="pre egXML_valid"><span class="element"><constraint></span>
<span class="element"><s:assert <span class="attribute">test</span>="<span class="attributevalue">(tei:corr or tei:sic or tei:expan or tei:abbr or tei:reg or tei:orig)
and ((tei:corr and tei:sic) or (tei:expan and tei:abbr) or (tei:reg
and tei:orig))</span>"