The Medieval Anglo-Jewish Women Project: Schema and Documentation

Table of contents

The Medieval Anglo-Jewish Women Project: Schema and Documentation

Welcome to the Medieval Anglo-Jewish Women Project. Here you will find encoding instructions, administration details, and other information related to the project.

1. Getting started with encoding

First you will need to learn How to use Subversion (SVN) to check out the repository, update your local copy, and commit your changes.

If youʼre working as an encoder on this project, youʼll need to edit several different types of file:

2. Using the Subversion Repository

We keep all our XML files and related documents in a Subversion Repository. This is a version-control system that ensures that every version of every file can be retrieved if necessary, and prevents one person from inadvertently overwriting changes to a file made by someone else.

Subversion runs on one of our HCMC servers, which is at hcmc.uvic.ca/svn. In order to use it, you will need to install a Subversion client on your computer, and also learn a couple of simple command-line commands. Subversion is usually abbreviated to ‘svn’.

If you are working on a computer in HCMC, Subversion will already be installed. If you are working on a different computer, such as your own laptop, you will have to install it.

2.1. Installing a Subversion client

How you will do this depends on which operating system you are using.

2.1.1. Windows

Obtain a command-line client from SilkSVN. There is no cost to download the client. Make sure to download the correct version; there are versions for 32-bit and 64-bit Windows. Once the program is downloaded, install it by double-clicking the downloaded installer and following its instructions.

2.1.2. Macintosh

Installing svn on Mac has become slightly complicated recently because Apple have removed it from their XCode toolset. We now have to install it using Homebrew, which is a package manager for the Mac. Here are the steps:

  • Go to the Homebrew home page, https://brew.sh/.
  • Copy the long line of code under ‘Install Homebrew’ to the clipboard.
  • Open a terminal.
  • Paste that code into the terminal (Command-V)
  • Press return.
  • Supply your password when required.

The Homebrew install process takes a little while. When it completes, go back to the terminal and type this:

brew install svn

When svn is installed, test it by typing:

svn --version

in the terminal. You should see lots of mysterious information, but the first thing should be the svn version number which is now installed on your machine.

2.1.3. Linux

Subversion is installed as part of a regular desktop on most Linux distributions. If it is not, you can simply type sudo apt install subversion or the equivalent command for your Linux distribution.

2.2. Checking out the repository for the first time

Once your subversion client is installed, the first thing we need to do is to check out the repository. To do this, you need to open a terminal window:

  • On Windows, click on the Start menu and type cmd into the search box.
  • On a Mac, select Terminal from the Utilities folder in Applications.
  • On Linux, press Control + Alt + T.

Now we'll check that svn is installed and working. Type svn checkout and press return. If the terminal responses that there are Not enough arguments provided, then svn is working OK.

And now we'll check out the files from the repository into our home directory, using this command:

svn checkout https://hcmc.uvic.ca/svn/majw

Then the server should ask for your netlink user name and password. After that, you should see the files download to your drive.

2.3. Using SVN in your daily work

These are the basic rules when you're working with svn:

Before you start work, update your local files:

  • Open a terminal
  • cd majw
  • svn update

You can leave the terminal open while you work. Then, when you're ready to commit your changes:

  • svn update
    (again, just in case anything else has been committed by someone else)
  • svn commit data -m "A message explaining the changes you have made"

(Aside: we include ‘content’ after the word ‘commit’ to specify that we only want to commit any changes that are in the content folder. That way, if we've accidentally made changes to program code or other files in the repo, those changes won't be committed.)

That's basically it. If you see any warnings or error messages from svn, check that you're in the right folder in your terminal. You may also see error messages if two people have been editing the same file at the same time, and Subversion needs you to make a decision about whose changes should be kept.

2.4. Tips for using the terminal

Finding out where you are right now:

pwd

Moving up the tree one level:

cd ../

List files in a folder:

ls

List files in a folder with full information:

ls -al

3. Working with Oxygen to encode content

Your encoding work will all be done in the Oxygen XML Editor. When you install Oxygen, there are lots of applications that come with it: Oxygen Author, Oxygen Developer, Compare Files, Compare Directories and others. But the one you want to work with is always Oxygen XML Editor, which has the blue icon with the red cross on it. Here's how to get started:

  1. Open the Oxygen XML Editor.
  2. Click on Project / Open Project...
  3. Navigate to the majw folder in your home directory.
  4. Choose the file majw.xpr.

You should see a tree of folders and files down the left of your Oxygen editor. This includes all the files in the project. You can ignore most of them. The folder that matters is the data folder, where all the main XML documents are kept.

3.1. Oxygen code templates for editing: helpful shortcuts

Our Oxygen project file has a number of useful keyboard shortcuts built into it, which you can use to speed up your encoding. Generally speaking, to use these, you select some text in the editor, then press the keystroke shortcut shown in the table below. The table uses the following key names:

M1 represents the Command key on MacOS X, and the Ctrl key on other platforms.
M2 represents the Shift key.
M3 represents the Option key on MacOS X, and the Alt key on other platforms.
M4 represents the Ctrl key on MacOS X, and is undefined on other platforms.

The following table shows keyboard shortcuts available when the majw.xpr project file is loaded.

Name Description Result Keystroke
Analytic (article or poem) title Wrap in title element with level="a" <title level="a">${xpath_eval(replace('${selection}', '[“”]+', ''))}</title>${caret} M1 M2 A
Curly apostrophe ʼ M1 M2 QUOTE
En dash En dash, used between digits ctrl shift MINUS
Enter comment on merging events. <!-- MDH ${xpath_eval(format-date(current-date(), '[Y0001]-[M01]-[D01]'))}: merged ev_ into ev_ per AB/JP. --> M1 M3 M2 SLASH
Journal title <title level="j">${selection}</title>${caret} M1 M2 J
Link to person Link selected text to a person record <ref target="pros:${ask('Please type the id of the person (abcd1, wxyz12, etc.)', generic, '')}">${selection}</ref>${caret} M1 M2 P
Monograph (book or play) title <title level="m">${selection}</title>${caret} M1 M2 M
New event record Add a new event element with placeholder content. <event xml:id="ev_" resp="pers:[your own id]" notBefore="[year]" notAfter="[year]" period="tm:[period id if relevant, or delete the attribute]" ana="ht:[id]"> <desc> <placeName corresp="plc:[place id]">[place name]</placeName> </desc> <listPerson> <person corresp="pros:"/> </listPerson> <linkGrp type="businesses"> <ptr target="bs:[business id]"/> </linkGrp> <bibl corresp="msd:[msDesc id]"> <biblScope unit="srcMemFol">[membrane or folio num]</biblScope> <textLang mainLang="[en or fr or la or he]"/> </bibl> <bibl corresp="bib:[bibl id]"> <biblScope unit="page">[page num(s)]</biblScope> </bibl> </event> ctrl alt shift E
New person record Add a new person element with placeholder content <person xml:id="" sex="[M or F]"> <persName> <forename>[forename]</forename> </persName> <persName type="displayName">[descriptive display name]</persName> <trait type="relation"> <label>relationships</label> <desc>[description of person in terms of key relationship(s)]</desc> </trait> <note type="relation">[any note you need to add, or delete the element]</note> </person> M1 M3 M2 P
Simple quotation Removes existing quote marks and wraps selection in <q> <q>${xpath_eval(replace('${selection}', '[“”]+', ''))}</q> M1 M2 Q

3.2. Claiming and asserting responsibility

The TEI attribute resp is global; that means it can appear on any element in our XML. The value of the resp attribute is constrained to one or more pointers representing people on our team. Here is an example:
<event xml:id="ev_1200_66notBefore="1200"  notAfter="1200resp="pers:pett1"> [...] </event>
The value pers:pett1 points to a <person> element with xml:id=pett1, which is found in our personography.xml file, and is the person entry for Dayne B. Pettyjohn. This means that this person created or edited the entry and believes it to be correct. The resp attribute can be used anywhere, but it is essential to add it to <person> elements in the prosopography files and <event> elements in the events files. The attribute permits more than one value, so when Dr. Williams-Boyarin has proofed and confirmed an item, she may add her own resp value to confirm that the item has been checked:
<event xml:id="ev_1200_66notBefore="1200"  notAfter="1200resp="pers:pett1 pers:will1"> [...] </event>

4. Suggested workflow (a work in progress)

We are just getting started with a pure-XML dataset, so it will be a little while before we can settle on a reliable and robust workflow. This section provides initial suggestions for entering new data, and will be continually amended as we try this out and settle on best practices.

4.1. Stage 1: Bibliographical records

Before entering records (<event>s) or people (<person>s), itʼs important to make sure all the required bibliographical records are present in the bibliography.xml file. This file is in two main sections: primary sources (manuscripts, encoded using <msDesc> elements), and secondary sources (print publications, encoded as <bibl> elements).

4.1.1. Primary sources

Each <msDesc> element represents a single manuscript source, encoded in a very simple and rudimentary way. Here is an example:
<msDesc xml:id="msd_tna_e_9_21">  <msIdentifier>   <settlement> Kew   </settlement>   <repository n="TNA"> The National Archives   </repository>   <idno>E 9/21</idno>  </msIdentifier> </msDesc>
Key points to note are the repository location (in the <settlement> element), the repository name and its abbreviation in the <repository> element, and the exact manuscript designation in the <idno> element. Also note that the xml:id attribute is entirely predictable from the content of the manuscript description. Normally, before starting work on a collection we would create all the required <msDesc> elements ahead of time, so that when entering events and people we can just point to them in the manner described below.

4.1.2. Secondary sources

Each <bibl> element represents a single print source volume, encoded in conventional way:
<bibl xml:id="bib_PREJ_3n="1_3">  <author>Great Britain</author>. <title level="m">Calendar of the Plea Rolls of the    Exchequer of the Jews Preserved in the Public Record Office.    Vol. 3, Edward I, 1275-1277</title>, edited and translated by <editor>Hilary Jenkinson</editor>. Published for the <editor>Jewish Historical Society of England</editor> by Spottiswoode, Ballantyne and Co. Ltd., Colchester. <date>1929</date>. </bibl>
Notice that the information is presented in exactly the sequence we would want to see it in a bibliography or reference list, but that individual items are tagged to identify them as e.g. a title or an author. This tagging helps with downstream processing; for example, a <title level="m">, which is a monograph title, can be presented in italics in the output.

Unlike the manuscripts, the xml:id attributes of print sources are not necessarily predictable from their content; instead they follow two different conventions, one based on the original relational database abbreviations (such as PREJ), and a second which creates an id based on the author name and date.

4.2. Stage 2: Entering events

Events are organized into separate files by year, so open the appropriate file and move to the end before adding an event. (Note that events which run over more than one year are grouped under their starting year.)

4.2.1. Creating a new event

Place your cursor after the closing tag of the final event, add a couple of linebreaks, and then press Control + Alt + Shift + E on your keyboard to insert a new event. Then:

  • Complete the xml:id attribute of the event, based on the preceding one. For example, if the preceding event is ev_1231_20, then your new event will be ev_1231_21. If you events have got out of order in the file, then Oxygen will warn you about this, and can increment the number at the end of the id until you get a valid new id.
  • In the resp attribute, add your own personal id to signify that you created this entry.
  • Enter the appropriate starting and ending year (usually the same) in the notBefore and notAfter attributes.
  • In the <desc> element, add the appropriate place id in the <placeName>/corresp attribute. If there are multiple places associated with the record, you can add as many <placeName> elements as you need. For the text inside the <placeName> element, you can supply the standard name for this place in the project, or some other more appropriate text if you like.
  • Leave the ‘People’ section alone for the moment. Weʼll deal with that last of all.
  • In the <linkGrp> with type=businesses, provide a <ptr> element for each distinct business which is mentioned; for example:
    <linkGrp type="businesses">  <ptr target="bs:bs_inheritanceEstate"/>  <ptr target="bs:bs_debt"/>  <ptr target="bs:bs_property"/> </linkGrp>
    The values for target can be found by looking at the listings page businesses.html on the Jenkins site (which is linked from the bottom of the About page.
  • Next, we record the primary and secondary sources from which the information was derived. The primary source is in the form of a pointer to a manuscript description, along with the precise membrane/folio/page identifier:
    <bibl corresp="msd:msd_tna_pat_66_68">  <biblScope unit="srcMemFol">5d</biblScope>  <textLang mainLang="la"/> </bibl>
    The main language of the original manuscript should be included in the form of the appropriate two-letter code. The id for the manuscript can be found from the sources.html on the Jenkins site. A similar process is used to encode the secondary source, providing a pointer to the source itself (found on the sources.html page) and the relevant page number(s):
    <bibl corresp="bib:bib_CPR_1247">  <biblScope unit="page">58</biblScope> </bibl>

4.2.2. Linking people into events

Finally, the people mentioned in the case must be encoded in the <linkGrp> with type=people, along with any relationships which are attested in this event.

4.2.2.1. Listing the people mentioned in an event

The focus of this project is women, so any woman mentioned in the record will be added. Generally, men are only added to our event records when they are explicitly mentioned as relatives of women who appear in the record. However, occasionally, where their presence in records aids in reconstructing the family network of a featured woman, attested relationships between men may be added to an event record, and inferred relationships involving men based on existing data may be added to the dataset.

First, we create a simple <listPerson> of <person> elements pointing to each of the women mentioned, and each of the men who are mentioned in relation to any of the women. In the simplest case, all the people involved are already in our prosopography, and there is no ambiguity about their identity. In that case, they can simply be listed:
<listPerson>  <person corresp="pros:gent8">   <persName>Genta</persName>  </person>  <person corresp="pros:bone16">   <persName>Bonenfant</persName>  </person> </listPerson>
Person records are found in the data/prosopography folder, and all that is required is to supply their id in the corresp attribute with the pros: prefix. If any of the people mentioned do not yet have records, and/or if the event attests to relationships between people, then records will have to be created or updated in the prosopography; this is the subject of a section below.

Note the use of <persName> element: this records the exact form the personʼs name takes in the text of the event you are encoding. If multiple variants of the personʼs name are used, then include one <persName> element for each variant. This enables us to track all the variants used for each individual and for each distinct name.

There is one more crucial component in encoding pointers to people. If a person in the record is specifically said to be deceased at the time of the record, then we record this fact by adding an ana attribute like this:
<person corresp="pros:cher12"  ana="state:deceased">  <persName>Chera</persName> </person>
Similarly, if a person is mentioned only as a relative of someone in the case, not as an actual participant in the case, then we use the same attribute to record that:
<person corresp="pros:mayd1"  ana="trait:relational">  <persName>Maydin</persName> </person>
And finally, if both are true, then we add both values to the attribute:
<person corresp="pros:cher12"  ana="state:deceased trait:relational">  <persName>Chera</persName> </person>

If multiple languages are used for a name, then those variants must also be encoded. For example, if a name appears in Latin rather than, or as well as, English, then we follow these rules:

  1. If the name is in the nominative case, just record it with the xml:lang attribute to indicate it is Latin:
    <persName xml:lang="la">Bona</persName>
  2. If the name also appears in any non-nominative cases, then first work out the nominative (get help if you need to), and record the nominative first, followed by every actual form that occurs (as well as the English version(s) if any):
    <!-- Latin versions of names:--> <!-- Nominative; not found in the text.--><persName xml:lang="la">Diai</persName> <!-- Latin non-nominative form; found in the Latin text.--> <persName xml:lang="la">Diaie</persName> <!-- Anglicized; found in the English translation of the text--> <persName>Diaia</persName>

4.2.2.2. Encoding relationships on events

The second thing we need to do on an event is to encode all the individual relationships between the people mentioned. We only encode relationships which are clearly attested in the source document; we do not add inferred relationships. Relationships are encoded in a <listRelation> element inside the <listPerson>, like this:
<listPerson>  <person corresp="pros:ivet9">   <persName>Ivette</persName>  </person>  <person corresp="pros:bene3">   <persName>Benedict</persName>  </person>  <listRelation>   <relation name="father"    active="pros:bene3passive="pros:ivet9"/>  </listRelation> </listPerson>
This means that bene3 (in active) is the father of ivet9 (in passive). Note that this relationship could also be encoded in reverse, with ivet9 as the daughter of bene3. However, we have a single canonical method of encoding relationships to avoid ambiguity: we place the id which comes first alphabetically in the active attribute. If you try to encode the relationship in the wrong orientation, a Schematron rule should warn you of the error.

Add all the relationships attested by this event into the <listRelation> element.

4.2.3. A complete example event

Here is a complete encoded event as a full example.

<event xml:id="ev_1275_150"  resp="pers:burn1notBefore="1275notAfter="1275"  period="tm:tm_Hilary">  <desc>   <placeName corresp="plc:pl_herefordshire">Herefordshire (Heref)</placeName>  </desc>  <listPerson>   <person corresp="pros:cont6">    <persName>Contessa</persName>   </person>   <person corresp="pros:mokk1"    ana="trait:relational">    <persName>Mokka</persName>   </person>   <person corresp="pros:bela13">    <persName>Belaset</persName>   </person>   <person corresp="pros:leof2">    <persName>Leo</persName>   </person>   <person corresp="pros:bona11">    <persName>Bona</persName>   </person>   <person corresp="pros:beli32">    <persName>Belia</persName>   </person>   <person corresp="pros:aaro13">    <persName>Aaron</persName>   </person>   <listRelation>    <relation active="pros:cont6"     passive="pros:mokk1name="daughter"/>    <relation active="pros:bela13"     passive="pros:leof2name="daughter"/>    <relation active="pros:beli32"     passive="pros:aaro13name="daughter"/>   </listRelation>  </listPerson>  <linkGrp type="businesses">   <ptr target="bs:bs_donumTallage"/>  </linkGrp>  <bibl corresp="msd:msd_tna_e_101_249_19">   <biblScope unit="srcMemFol">6</biblScope>   <textLang mainLang="la"/>  </bibl>  <bibl corresp="bib:bib_PREJ_4">   <biblScope unit="page">33</biblScope>  </bibl> </event>

4.3. Stage 3: People

You will be doing two kinds of edits to the prosopography: adding new people, and adding assertions that two person records may in fact be the same person, signifying that further research is needed.

4.3.1. Adding a new person

The prosopography is organized by initial alphabetical letter, so first open the file for the first letter in the personʼs name. Within the file, there is no need for further organization; just add your new person at the end. Put your cursor after the closing tag of the final person, add a couple of linebreaks, and then press Control + Alt + Shift + P. A new person template will be inserted.

  • First add the new personʼs id. Insert the first four letters of the personʼs name, and then look at the bottom of the screen; a Schematron rule will tell you what the next available id is for that four-letter combination.
  • Next, complete the role and sex attributes. In the TEI dataset, all women are primary and all men are relatives, so the appropriate values may be selected in each case. We maintain both attributes because we may still have some records which are women but were entered in the old database as relatives. Once all those cases have been resolved, we will be able to dispense with the role attribute.
  • Enter the forename in the <forename> element. Note that if there are many possible forms or spellings of the forename, you can enter multiple <persName> elements in order to provide them all. If the person also happens to have a surname, then add a <surname> element alongside the <forename>, leaving a space or a linebreak between them.
  • Complete the <persName> with type=displayName. This is a longer version of the name which includes information about relatives or location, designed to distinguish this person from anyone else who might have the same name.
  • The following two elements, <trait> (type=relation) and <note> (type=relation), are available if there is additional information that may help distinguish or describe the person. These are usually repetitions of information already included in the preceding elements, derived from the original relational database elements. If you do not have anything new worth recording in those elements, simply delete them.

4.3.2. Editing an existing person

Obviously, if a person already exists in the prosopography, then the only thing you need to do is to edit that personʼs record to add any newly-attested relationships that arise out of the event you are currently editing. FOR THE MOMENT, every case where a relationship is attested by an event requires a new <relation> element to be added to one of the participants, even if the same relationship is already attested by other events. In other words, FOR THE MOMENT, you can only add a single event pointer in the <relation>/source attribute. However, for people appearing in many records, this results in a large number of <relation> elements attesting to the same relationship, which is obviously not ideal, so we will probably move to a system where the source attribute can contain multiple event pointers.

4.3.3. Asserting that two person records may or may not be the same person

It is frequently the case that two mentions of the same name are plausibly the same person, but there is not enough other evidence to support collapsing the two records into one. This is handled by adding a new <item> containing a <linkGrp> element to the list in the data/prosopography/prosopographyLinks.xml file:
<item>  <linkGrp type="possiblySamePerson">   <ptr target="pros:milk1"/>   <ptr target="pros:milk5"/>  </linkGrp> </item>
This asserts that the person elements with the ids milk1 and milk5 may in fact be the same person.
Conversely, it often appears that two people may be the same person, but further research has determined that they are not. This can be attested in a similar manner:
<item>  <linkGrp type="notSamePerson">   <ptr target="pros:fred1"/>   <ptr target="pros:fred2"/>  </linkGrp> </item>

5. Inferred/unattested people and relations

5.1. Inferred people

Sometimes it is important for our dataset to include individuals who are not directly attested in primary source documents. For example, if we know of a father/daughter relationship, but we have no information about the mother, we may infer that a mother must have existed, and must have been the wife of the father. We occasionally do this in order to support work on the family trees of featured women, for instance.

To add an inferred person, follow the standard practice outlined in Adding a new person, but add an additional source attribute to the person element like this:
<person xml:id="xxxx1sex="F"  source="inferred"> [...] </person>
Use descriptors similar to those used elsewhere such as ‘Unnamed wife of ...’ or ‘Unnamed sister of...’ to characterize the person as best you can, and add information in a note element to explain how/why the existence of the person was inferred. Then you can add relation elements for this person to the Unattested relations file.

5.2. Inferred relations

Just as we may often infer the existence of people, we may also infer relationships between such people and attested people, or between attested people. For example, if a man and a woman have the same parents, we can obviously infer that they are brother and sister. It is often helpful to explicitly record relationships which we can infer from the evidence but which are not explicitly mentioned anywhere, because that enables us to build richer networks and in particular to fill out the family trees of featured women.

Inferred relations are encoded in the data/relations_unattested.xml file. You can add any relation you have confidence in to this file. You may also want to provide some explanation in the form of an XML comment to say how you decided that this relationship existed.

6. Featured women and biographies

A growing number of women in the dataset are designated as ‘Featured women’, being prominent and interesting characters about whom some information is known. Making a woman ‘featured’ requires two components:
  • Their <person> element in the prosopography must have the attribute ana=ht:ht_FeaturedWoman.
  • They must have a biography in the bios.xml file.
A biography looks like this (truncated for simplicity):
<div type="biocorresp="pros:rach1">  <figure>   <graphic url="img:images/names/rachel.png"    width="179pxheight="105px"/>  </figure>  <p>Rachel was the daughter of <ref target="pros:davi3">David Lumbard</ref>, chirographer    of Nottingham from 1230–1231 and later its <foreign>ballivus</foreign> (bailiff or royal    official, head of the Nottingham Jewish community).[...]</p>  <p>[...]</p>  <div>   <head>Further reading</head>   <listBibl>    <bibl corresp="bib:bib_hill1_2015">s.v. <title level="a">The English Medieval Jewry,          c.1075–1290: The Impoverishment of the Jewry, 1241–55</title> and <title level="a">Nottingham: David Lumbard and Family, 1230–55,</title> pp. <biblScope unit="page">7–9</biblScope> and <biblScope unit="page">291</biblScope>    </bibl>    <bibl corresp="bib:bib_HHLD_1">nos. 13, 46, and 55</bibl>    <bibl corresp="bib:bib_HHLD_2">no. 155</bibl>    <bibl>The National Archives of the UK (TNA), DL 25/2381, DL 25/2382/2068, and E        40/14957.</bibl>   </listBibl>  </div> </div>
The corresp attribute points to the id of the woman in the prosopography. The prose description includes links to other people, created using the <ref> element, and may use other TEI elements that are appropriate. The reference list contains some entries pointing to items already in our bibliography, with the addition of some specific information such as page numbers. When the biography is rendered on the personʼs page, the full bibliographical entry will be completed.

Appendix A Schema Specification

Appendix A.1

Appendix A.1.1 Elements

Appendix A.1.1.1 <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure
Attributes
version specifies the version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype teidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Contained by
textstructure: TEI
May contain
header: teiHeader
linking: standOff
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<sch:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/> <sch:ns prefix="rna"  uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Schematron
<sch:ns prefix="sch"  uri="http://purl.oclc.org/dsdl/schematron"/> <sch:ns prefix="sch1x"  uri="http://www.ascc.net/xml/schematron"/>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <alternate>
   <sequence>
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   att.global.attributes,
   att.typed.attributes,
   attribute version { text }?,
   ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}

Appendix A.1.1.2 <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Module core
Attributes
type (type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   att.global.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   macro.phraseSeq
}

Appendix A.1.1.3 <addName>

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Frederick</forename>  <addName type="epithet">the Great</addName>  <roleName>Emperor of Prussia</roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

Appendix A.1.1.4 <affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.

Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for    the Humanities</name> </affiliation>
Example This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"  notBefore="1957-02-28">Paid up member of the <orgName>Australian Journalists Association</orgName> </affiliation>
Example This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.
<affiliation from="1902-01-01"  to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element affiliation
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.5 <age>

<age> (age) specifies the age of a person. [13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
value supplies a numeric code representing the age or age group
Status Optional
Datatype teidata.count
Note

This attribute may be used to complement a more detailed discussion of a person's age in the content of the element

Member of
Contained by
namesdates: person
May contain
Note

As with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text.

Example
<age value="2notAfter="1986">under 20 in the early eighties</age>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element age
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.typed.attribute.subtype,
   att.dimensions.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute value { text }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.6 <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
May contain
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author
{
   att.global.attributes,
   att.naming.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.7 <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header
Attributes
Member of
Contained by
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq.limited
}

Appendix A.1.1.8 <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Module textstructure
Attributes
Contained by
textstructure: text
May contain
Note

Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   att.global.attributes,
   att.declaring.attributes,
   (
      (
         model.frontPartmodel.pLike.frontmodel.pLikemodel.listLikemodel.global
      )*,
      (
         (
            model.div1Like,
            ( model.frontPart | model.div1Like | model.global )*
         )
       | ( model.divLike, ( model.frontPart | model.divLike | model.global )* )
      )?,
      ( ( model.divBottomPart, ( model.divBottomPart | model.global )* )? )
   )
}

Appendix A.1.1.9 <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
msd:msd_bcl_256_307191
(Birmingham Central Library , DV 256/307191)
msd:msd_bl_add_7218
(British Library , Additional 7218)
msd:msd_bl_add_Ch_1250
(British Library , Additional Charter 1250)
msd:msd_bl_add_Roll_19299
(British Library , Additional Roll 19299)
msd:msd_bl_cot_Nero_C_III
(British Library , Cotton Nero C. III)
msd:msd_bl_harl_Ch_43_A_54
(British Library , Harley Ch 43 A 54)
msd:msd_bl_harl_Ch_43_A_56
(British Library , Harley Ch 43 A 56)
msd:msd_bl_harl_Ch_84D
(British Library , Harley Charter 84D)
msd:msd_bl_harl_Chart_43A
(British Library , Harley Chart. 43A)
msd:msd_bl_harl_Chart_43A_59A
(British Library , Harley Chart. 43A, 59A)
msd:msd_bl_lans_Ch_665
(British Library , Lansdowne Charter 665)
msd:msd_bl_lans_Ch_666
(British Library , Lansdowne Charter 666)
msd:msd_bl_lans_Ch_667
(British Library , Lansdowne Charter 667)
msd:msd_bl_lans_Ch_668
(British Library , Lansdowne Charter 668)
msd:msd_bl_lans_Ch_669
(British Library , Lansdowne Charter 669)
msd:msd_magd_ald_34
(Magdalen College Muniments Room, Oxford , St Aldates 34)
msd:msd_mert_14_D_I_58_i
(Merton College, Oxford , Merton College Archives D I.58 (i))
msd:msd_mert_mcr_188
(Merton College, Oxford , MCR 188)
msd:msd_tna_13_Item_98
(The National Archives , Davis, Hebrew Deeds of English Jews Before 1290 Item #98)
msd:msd_tna_15_27_189
(The National Archives , DL 27/189)
msd:msd_tna_9_26_115B
(The National Archives , KB 26/115B)
msd:msd_tna_9_26_35
(The National Archives , KB 26/35)
msd:msd_tna_c_143_10_14
(The National Archives , C 143/10/14)
msd:msd_tna_c_145_17_3
(The National Archives , C 145/17/3)
msd:msd_tna_c_145_35_56
(The National Archives , C 145/35/56)
msd:msd_tna_c_255_18_5B
(The National Archives , C 255/18/5B)
msd:msd_tna_c_53_13
(The National Archives , C 53/13)
msd:msd_tna_c_53_2
(The National Archives , C 53/2)
msd:msd_tna_c_53_20
(The National Archives , C 53/20)
msd:msd_tna_c_53_26
(The National Archives , C 53/26)
msd:msd_tna_c_53_29
(The National Archives , C 53/29)
msd:msd_tna_c_53_44
(The National Archives , C 53/44)
msd:msd_tna_c_53_47
(The National Archives , C 53/47)
msd:msd_tna_c_53_64
(The National Archives , C 53/64)
msd:msd_tna_c_53_68
(The National Archives , C 53/68)
msd:msd_tna_c_53_69
(The National Archives , C 53/69)
msd:msd_tna_c_53_70
(The National Archives , C 53/70)
msd:msd_tna_c_53_78
(The National Archives , C 53/78)
msd:msd_tna_c_54_101
(The National Archives , C 54/101)
msd:msd_tna_c_54_105
(The National Archives , C 54/105)
msd:msd_tna_c_54_106
(The National Archives , C 54/106)
msd:msd_tna_c_54_107
(The National Archives , C 54/107)
msd:msd_tna_c_54_114
(The National Archives , C 54/114)
msd:msd_tna_c_54_117
(The National Archives , C 54/117)
msd:msd_tna_c_54_38
(The National Archives , C 54/38)
msd:msd_tna_c_54_41
(The National Archives , C 54/41)
msd:msd_tna_c_54_42
(The National Archives , C 54/42)
msd:msd_tna_c_54_43
(The National Archives , C 54/43)
msd:msd_tna_c_54_44
(The National Archives , C 54/44)
msd:msd_tna_c_54_45
(The National Archives , C 54/45)
msd:msd_tna_c_54_46
(The National Archives , C 54/46)
msd:msd_tna_c_54_47
(The National Archives , C 54/47)
msd:msd_tna_c_54_48
(The National Archives , C 54/48)
msd:msd_tna_c_54_49
(The National Archives , C 54/49)
msd:msd_tna_c_54_51
(The National Archives , C 54/51)
msd:msd_tna_c_54_52
(The National Archives , C 54/52)
msd:msd_tna_c_54_53
(The National Archives , C 54/53)
msd:msd_tna_c_54_57
(The National Archives , C 54/57)
msd:msd_tna_c_54_59
(The National Archives , C 54/59)
msd:msd_tna_c_54_60
(The National Archives , C 54/60)
msd:msd_tna_c_54_61
(The National Archives , C 54/61)
msd:msd_tna_c_54_62
(The National Archives , C 54/62)
msd:msd_tna_c_54_63
(The National Archives , C 54/63)
msd:msd_tna_c_54_64
(The National Archives , C 54/64)
msd:msd_tna_c_54_68
(The National Archives , C 54/68)
msd:msd_tna_c_54_69
(The National Archives , C 54/69)
msd:msd_tna_c_54_70
(The National Archives , C 54/70)
msd:msd_tna_c_54_71
(The National Archives , C 54/71)
msd:msd_tna_c_54_72
(The National Archives , C 54/72)
msd:msd_tna_c_54_73
(The National Archives , C 54/73)
msd:msd_tna_c_54_74
(The National Archives , C 54/74)
msd:msd_tna_c_54_75
(The National Archives , C 54/75)
msd:msd_tna_c_54_76
(The National Archives , C 54/76)
msd:msd_tna_c_54_77
(The National Archives , C 54/77)
msd:msd_tna_c_54_78
(The National Archives , C 54/78)
msd:msd_tna_c_54_82
(The National Archives , C 54/82)
msd:msd_tna_c_54_83
(The National Archives , C 54/83)
msd:msd_tna_c_54_84
(The National Archives , C 54/84)
msd:msd_tna_c_54_85
(The National Archives , C 54/85)
msd:msd_tna_c_54_86
(The National Archives , C 54/86)
msd:msd_tna_c_54_87
(The National Archives , C 54/87)
msd:msd_tna_c_54_88
(The National Archives , C 54/88)
msd:msd_tna_c_54_89
(The National Archives , C 54/89)
msd:msd_tna_c_54_91
(The National Archives , C 54/91)
msd:msd_tna_c_54_92
(The National Archives , C 54/92)
msd:msd_tna_c_54_93
(The National Archives , C 54/93)
msd:msd_tna_c_54_94
(The National Archives , C 54/94)
msd:msd_tna_c_54_95
(The National Archives , C 54/95)
msd:msd_tna_c_54_96
(The National Archives , C 54/96)
msd:msd_tna_c_54_97
(The National Archives , C 54/97)
msd:msd_tna_c_54_98
(The National Archives , C 54/98)
msd:msd_tna_c_54_99
(The National Archives , C 54/99)
msd:msd_tna_c_60_16
(The National Archives , C 60/16)
msd:msd_tna_c_60_24
(The National Archives , C 60/24)
msd:msd_tna_c_60_27
(The National Archives , C 60/27)
msd:msd_tna_c_60_28
(The National Archives , C 60/28)
msd:msd_tna_c_60_29
(The National Archives , C 60/29)
msd:msd_tna_c_60_31
(The National Archives , C 60/31)
msd:msd_tna_c_60_32
(The National Archives , C 60/32)
msd:msd_tna_c_60_34
(The National Archives , C 60/34)
msd:msd_tna_c_60_35
(The National Archives , C 60/35)
msd:msd_tna_c_60_36
(The National Archives , C 60/36)
msd:msd_tna_c_60_37
(The National Archives , C 60/37)
msd:msd_tna_c_60_40
(The National Archives , C 60/40)
msd:msd_tna_c_60_40A
(The National Archives , C 60/40A)
msd:msd_tna_c_60_41
(The National Archives , C 60/41)
msd:msd_tna_c_60_46
(The National Archives , C 60/46)
msd:msd_tna_c_60_47
(The National Archives , C 60/47)
msd:msd_tna_c_60_48
(The National Archives , C 60/48)
msd:msd_tna_c_60_49
(The National Archives , C 60/49)
msd:msd_tna_c_60_50
(The National Archives , C 60/50)
msd:msd_tna_c_60_52
(The National Archives , C 60/52)
msd:msd_tna_c_60_53
(The National Archives , C 60/53)
msd:msd_tna_c_60_54
(The National Archives , C 60/54)
msd:msd_tna_c_60_55
(The National Archives , C 60/55)
msd:msd_tna_c_60_56
(The National Archives , C 60/56)
msd:msd_tna_c_60_58
(The National Archives , C 60/58)
msd:msd_tna_c_60_59
(The National Archives , C 60/59)
msd:msd_tna_c_60_80
(The National Archives , C 60/80)
msd:msd_tna_c_60_82
(The National Archives , C 60/82)
msd:msd_tna_c_60_83
(The National Archives , C 60/83)
msd:msd_tna_c_60_9
(The National Archives , C 60/9)
msd:msd_tna_c_67_4
(The National Archives , C 67/4)
msd:msd_tna_c_85_170
(The National Archives , C 85/170)
msd:msd_tna_c_85_3_71
(The National Archives , C 85/3/71)
msd:msd_tna_c_85_99
(The National Archives , C 85/99)
msd:msd_tna_e_101_13_8_
(The National Archives , E 101/13 (8))
msd:msd_tna_e_101_249
(The National Archives , E 101/249)
msd:msd_tna_e_101_249_19
(The National Archives , E 101/249/19)
msd:msd_tna_e_101_249_20
(The National Archives , E 101/249/20)
msd:msd_tna_e_101_249_22
(The National Archives , E 101/249/22)
msd:msd_tna_e_101_249_8
(The National Archives , E 101/249/8)
msd:msd_tna_e_101_250
(The National Archives , E 101/250)
msd:msd_tna_e_159_41
(The National Archives , E 159/41)
msd:msd_tna_e_159_42
(The National Archives , E 159/42)
msd:msd_tna_e_159_43
(The National Archives , E 159/43)
msd:msd_tna_e_159_44
(The National Archives , E 159/44)
msd:msd_tna_e_159_45
(The National Archives , E 159/45)
msd:msd_tna_e_159_46
(The National Archives , E 159/46)
msd:msd_tna_e_159_47
(The National Archives , E 159/47)
msd:msd_tna_e_159_48
(The National Archives , E 159/48)
msd:msd_tna_e_159_49
(The National Archives , E 159/49)
msd:msd_tna_e_159_50
(The National Archives , E 159/50)
msd:msd_tna_e_159_51
(The National Archives , E 159/51)
msd:msd_tna_e_159_52
(The National Archives , E 159/52)
msd:msd_tna_e_159_53
(The National Archives , E 159/53)
msd:msd_tna_e_159_54
(The National Archives , E 159/54)
msd:msd_tna_e_159_55
(The National Archives , E 159/55)
msd:msd_tna_e_159_56
(The National Archives , E 159/56)
msd:msd_tna_e_159_57
(The National Archives , E 159/57)
msd:msd_tna_e_159_58
(The National Archives , E 159/58)
msd:msd_tna_e_159_59
(The National Archives , E 159/59)
msd:msd_tna_e_159_60
(The National Archives , E 159/60)
msd:msd_tna_e_159_61
(The National Archives , E 159/61)
msd:msd_tna_e_159_62
(The National Archives , E 159/62)
msd:msd_tna_e_159_63
(The National Archives , E 159/63)
msd:msd_tna_e_159_64
(The National Archives , E 159/64)
msd:msd_tna_e_159_65
(The National Archives , E 159/65)
msd:msd_tna_e_159_66
(The National Archives , E 159/66)
msd:msd_tna_e_199_39
(The National Archives , E 199/39)
msd:msd_tna_e_32_12
(The National Archives , E 32/12)
msd:msd_tna_e_368_41
(The National Archives , E 368/41)
msd:msd_tna_e_368_42
(The National Archives , E 368/42)
msd:msd_tna_e_368_43
(The National Archives , E 368/43)
msd:msd_tna_e_368_44
(The National Archives , E 368/44)
msd:msd_tna_e_368_45
(The National Archives , E 368/45)
msd:msd_tna_e_368_46
(The National Archives , E 368/46)
msd:msd_tna_e_368_47
(The National Archives , E 368/47)
msd:msd_tna_e_368_48
(The National Archives , E 368/48)
msd:msd_tna_e_368_49
(The National Archives , E 368/49)
msd:msd_tna_e_368_50
(The National Archives , E 368/50)
msd:msd_tna_e_368_51
(The National Archives , E 368/51)
msd:msd_tna_e_368_52
(The National Archives , E 368/52)
msd:msd_tna_e_368_53
(The National Archives , E 368/53)
msd:msd_tna_e_368_54
(The National Archives , E 368/54)
msd:msd_tna_e_368_55
(The National Archives , E 368/55)
msd:msd_tna_e_368_56
(The National Archives , E 368/56)
msd:msd_tna_e_368_57
(The National Archives , E 368/57)
msd:msd_tna_e_368_58
(The National Archives , E 368/58)
msd:msd_tna_e_368_59
(The National Archives , E 368/59)
msd:msd_tna_e_368_60
(The National Archives , E 368/60)
msd:msd_tna_e_368_61
(The National Archives , E 368/61)
msd:msd_tna_e_368_62
(The National Archives , E 368/62)
msd:msd_tna_e_368_63
(The National Archives , E 368/63)
msd:msd_tna_e_368_64
(The National Archives , E 368/64)
msd:msd_tna_e_370_2
(The National Archives , E 370/2)
msd:msd_tna_e_371_3
(The National Archives , E 371/3)
msd:msd_tna_e_371_4
(The National Archives , E 371/4)
msd:msd_tna_e_371_7
(The National Archives , E 371/7)
msd:msd_tna_e_401_1564
(The National Archives , E 401/1564)
msd:msd_tna_e_401_1565
(The National Archives , E 401/1565)
msd:msd_tna_e_401_1573
(The National Archives , E 401/1573)
msd:msd_tna_e_401_1574
(The National Archives , E 401/1574)
msd:msd_tna_e_401_1576
(The National Archives , E 401/1576)
msd:msd_tna_e_401_1586
(The National Archives , E 401/1586)
msd:msd_tna_e_401_1590
(The National Archives , E 401/1590)
msd:msd_tna_e_401_4
(The National Archives , E 401/4)
msd:msd_tna_e_402_3A
(The National Archives , E 402/3A)
msd:msd_tna_e_402_3B
(The National Archives , E 402/3B)
msd:msd_tna_e_40_1478
(The National Archives , E 40/1478)
msd:msd_tna_e_9_1
(The National Archives , E 9/1)
msd:msd_tna_e_9_10
(The National Archives , E 9/10)
msd:msd_tna_e_9_11
(The National Archives , E 9/11)
msd:msd_tna_e_9_12
(The National Archives , E 9/12)
msd:msd_tna_e_9_13
(The National Archives , E 9/13)
msd:msd_tna_e_9_14
(The National Archives , E 9/14)
msd:msd_tna_e_9_15
(The National Archives , E 9/15)
msd:msd_tna_e_9_16
(The National Archives , E 9/16)
msd:msd_tna_e_9_17
(The National Archives , E 9/17)
msd:msd_tna_e_9_18
(The National Archives , E 9/18)
msd:msd_tna_e_9_183
(The National Archives , E 9/183)
msd:msd_tna_e_9_19
(The National Archives , E 9/19)
msd:msd_tna_e_9_2
(The National Archives , E 9/2)
msd:msd_tna_e_9_20
(The National Archives , E 9/20)
msd:msd_tna_e_9_21
(The National Archives , E 9/21)
msd:msd_tna_e_9_22
(The National Archives , E 9/22)
msd:msd_tna_e_9_23
(The National Archives , E 9/23)
msd:msd_tna_e_9_24
(The National Archives , E 9/24)
msd:msd_tna_e_9_25
(The National Archives , E 9/25)
msd:msd_tna_e_9_26
(The National Archives , E 9/26)
msd:msd_tna_e_9_27
(The National Archives , E 9/27)
msd:msd_tna_e_9_28
(The National Archives , E 9/28)
msd:msd_tna_e_9_29
(The National Archives , E 9/29)
msd:msd_tna_e_9_3
(The National Archives , E 9/3)
msd:msd_tna_e_9_30
(The National Archives , E 9/30)
msd:msd_tna_e_9_31_and_70
(The National Archives , E 9/31 and 70)
msd:msd_tna_e_9_32
(The National Archives , E 9/32)
msd:msd_tna_e_9_32_and_64
(The National Archives , E 9/32 and 64)
msd:msd_tna_e_9_33
(The National Archives , E 9/33)
msd:msd_tna_e_9_34_and_65
(The National Archives , E 9/34 and 65)
msd:msd_tna_e_9_35
(The National Archives , E 9/35)
msd:msd_tna_e_9_36
(The National Archives , E 9/36)
msd:msd_tna_e_9_37
(The National Archives , E 9/37)
msd:msd_tna_e_9_38
(The National Archives , E 9/38)
msd:msd_tna_e_9_39
(The National Archives , E 9/39)
msd:msd_tna_e_9_4
(The National Archives , E 9/4)
msd:msd_tna_e_9_40
(The National Archives , E 9/40)
msd:msd_tna_e_9_41
(The National Archives , E 9/41)
msd:msd_tna_e_9_42
(The National Archives , E 9/42)
msd:msd_tna_e_9_43
(The National Archives , E 9/43)
msd:msd_tna_e_9_45
(The National Archives , E 9/45)
msd:msd_tna_e_9_49
(The National Archives , E 9/49)
msd:msd_tna_e_9_5
(The National Archives , E 9/5)
msd:msd_tna_e_9_52
(The National Archives , E 9/52)
msd:msd_tna_e_9_53
(The National Archives , E 9/53)
msd:msd_tna_e_9_54
(The National Archives , E 9/54)
msd:msd_tna_e_9_6
(The National Archives , E 9/6)
msd:msd_tna_e_9_62
(The National Archives , E 9/62)
msd:msd_tna_e_9_66
(The National Archives , E 9/66)
msd:msd_tna_e_9_7
(The National Archives , E 9/7)
msd:msd_tna_e_9_8
(The National Archives , E 9/8)
msd:msd_tna_e_9_9
(The National Archives , E 9/9)
msd:msd_tna_pat_66_1
(The National Archives , C 66/1)
msd:msd_tna_pat_66_10
(The National Archives , C 66/10)
msd:msd_tna_pat_66_100
(The National Archives , C 66/100)
msd:msd_tna_pat_66_101
(The National Archives , C 66/101)
msd:msd_tna_pat_66_102
(The National Archives , C 66/102)
msd:msd_tna_pat_66_103
(The National Archives , C 66/103)
msd:msd_tna_pat_66_104
(The National Archives , C 66/104)
msd:msd_tna_pat_66_105
(The National Archives , C 66/105)
msd:msd_tna_pat_66_105A
(The National Archives , C 66/105A)
msd:msd_tna_pat_66_106
(The National Archives , C 66/106)
msd:msd_tna_pat_66_106A
(The National Archives , C 66/106A)
msd:msd_tna_pat_66_107
(The National Archives , C 66/107)
msd:msd_tna_pat_66_108
(The National Archives , C 66/108)
msd:msd_tna_pat_66_109
(The National Archives , C 66/109)
msd:msd_tna_pat_66_11
(The National Archives , C 66/11)
msd:msd_tna_pat_66_110
(The National Archives , C 66/110)
msd:msd_tna_pat_66_111
(The National Archives , C 66/111)
msd:msd_tna_pat_66_112
(The National Archives , C 66/112)
msd:msd_tna_pat_66_113
(The National Archives , C 66/113)
msd:msd_tna_pat_66_114
(The National Archives , C 66/114)
msd:msd_tna_pat_66_115
(The National Archives , C 66/115)
msd:msd_tna_pat_66_116
(The National Archives , C 66/116)
msd:msd_tna_pat_66_117
(The National Archives , C 66/117)
msd:msd_tna_pat_66_118
(The National Archives , C 66/118)
msd:msd_tna_pat_66_119
(The National Archives , C 66/119)
msd:msd_tna_pat_66_12
(The National Archives , C 66/12)
msd:msd_tna_pat_66_120
(The National Archives , C 66/120)
msd:msd_tna_pat_66_121
(The National Archives , C 66/121)
msd:msd_tna_pat_66_122
(The National Archives , C 66/122)
msd:msd_tna_pat_66_123
(The National Archives , C 66/123)
msd:msd_tna_pat_66_124
(The National Archives , C 66/124)
msd:msd_tna_pat_66_125
(The National Archives , C 66/125)
msd:msd_tna_pat_66_126
(The National Archives , C 66/126)
msd:msd_tna_pat_66_127
(The National Archives , C 66/127)
msd:msd_tna_pat_66_128
(The National Archives , C 66/128)
msd:msd_tna_pat_66_129
(The National Archives , C 66/129)
msd:msd_tna_pat_66_13
(The National Archives , C 66/13)
msd:msd_tna_pat_66_130
(The National Archives , C 66/130)
msd:msd_tna_pat_66_14
(The National Archives , C 66/14)
msd:msd_tna_pat_66_15
(The National Archives , C 66/15)
msd:msd_tna_pat_66_16
(The National Archives , C 66/16)
msd:msd_tna_pat_66_17
(The National Archives , C 66/17)
msd:msd_tna_pat_66_18
(The National Archives , C 66/18)
msd:msd_tna_pat_66_19
(The National Archives , C 66/19)
msd:msd_tna_pat_66_2
(The National Archives , C 66/2)
msd:msd_tna_pat_66_20
(The National Archives , C 66/20)
msd:msd_tna_pat_66_21
(The National Archives , C 66/21)
msd:msd_tna_pat_66_22
(The National Archives , C 66/22)
msd:msd_tna_pat_66_23
(The National Archives , C 66/23)
msd:msd_tna_pat_66_24
(The National Archives , C 66/24)
msd:msd_tna_pat_66_25
(The National Archives , C 66/25)
msd:msd_tna_pat_66_26
(The National Archives , C 66/26)
msd:msd_tna_pat_66_27
(The National Archives , C 66/27)
msd:msd_tna_pat_66_28
(The National Archives , C 66/28)
msd:msd_tna_pat_66_29
(The National Archives , C 66/29)
msd:msd_tna_pat_66_3
(The National Archives , C 66/3)
msd:msd_tna_pat_66_30
(The National Archives , C 66/30)
msd:msd_tna_pat_66_31
(The National Archives , C 66/31)
msd:msd_tna_pat_66_32
(The National Archives , C 66/32)
msd:msd_tna_pat_66_33
(The National Archives , C 66/33)
msd:msd_tna_pat_66_34
(The National Archives , C 66/34)
msd:msd_tna_pat_66_35
(The National Archives , C 66/35)
msd:msd_tna_pat_66_36
(The National Archives , C 66/36)
msd:msd_tna_pat_66_37
(The National Archives , C 66/37)
msd:msd_tna_pat_66_38
(The National Archives , C 66/38)
msd:msd_tna_pat_66_39
(The National Archives , C 66/39)
msd:msd_tna_pat_66_4
(The National Archives , C 66/4)
msd:msd_tna_pat_66_40
(The National Archives , C 66/40)
msd:msd_tna_pat_66_41
(The National Archives , C 66/41)
msd:msd_tna_pat_66_42
(The National Archives , C 66/42)
msd:msd_tna_pat_66_43
(The National Archives , C 66/43)
msd:msd_tna_pat_66_44
(The National Archives , C 66/44)
msd:msd_tna_pat_66_45
(The National Archives , C 66/45)
msd:msd_tna_pat_66_46
(The National Archives , C 66/46)
msd:msd_tna_pat_66_47
(The National Archives , C 66/47)
msd:msd_tna_pat_66_48
(The National Archives , C 66/48)
msd:msd_tna_pat_66_49
(The National Archives , C 66/49)
msd:msd_tna_pat_66_5
(The National Archives , C 66/5)
msd:msd_tna_pat_66_50
(The National Archives , C 66/50)
msd:msd_tna_pat_66_51
(The National Archives , C 66/51)
msd:msd_tna_pat_66_52
(The National Archives , C 66/52)
msd:msd_tna_pat_66_53
(The National Archives , C 66/53)
msd:msd_tna_pat_66_54
(The National Archives , C 66/54)
msd:msd_tna_pat_66_55
(The National Archives , C 66/55)
msd:msd_tna_pat_66_56
(The National Archives , C 66/56)
msd:msd_tna_pat_66_57
(The National Archives , C 66/57)
msd:msd_tna_pat_66_58
(The National Archives , C 66/58)
msd:msd_tna_pat_66_59
(The National Archives , C 66/59)
msd:msd_tna_pat_66_6
(The National Archives , C 66/6)
msd:msd_tna_pat_66_60
(The National Archives , C 66/60)
msd:msd_tna_pat_66_61
(The National Archives , C 66/61)
msd:msd_tna_pat_66_62
(The National Archives , C 66/62)
msd:msd_tna_pat_66_63
(The National Archives , C 66/63)
msd:msd_tna_pat_66_64
(The National Archives , C 66/64)
msd:msd_tna_pat_66_65
(The National Archives , C 66/65)
msd:msd_tna_pat_66_66
(The National Archives , C 66/66)
msd:msd_tna_pat_66_67
(The National Archives , C 66/67)
msd:msd_tna_pat_66_68
(The National Archives , C 66/68)
msd:msd_tna_pat_66_69
(The National Archives , C 66/69)
msd:msd_tna_pat_66_7
(The National Archives , C 66/7)
msd:msd_tna_pat_66_70
(The National Archives , C 66/70)
msd:msd_tna_pat_66_71
(The National Archives , C 66/71)
msd:msd_tna_pat_66_72
(The National Archives , C 66/72)
msd:msd_tna_pat_66_73
(The National Archives , C 66/73)
msd:msd_tna_pat_66_74
(The National Archives , C 66/74)
msd:msd_tna_pat_66_75
(The National Archives , C 66/75)
msd:msd_tna_pat_66_76
(The National Archives , C 66/76)
msd:msd_tna_pat_66_77
(The National Archives , C 66/77)
msd:msd_tna_pat_66_78
(The National Archives , C 66/78)
msd:msd_tna_pat_66_79
(The National Archives , C 66/79)
msd:msd_tna_pat_66_8
(The National Archives , C 66/8)
msd:msd_tna_pat_66_80
(The National Archives , C 66/80)
msd:msd_tna_pat_66_81
(The National Archives , C 66/81)
msd:msd_tna_pat_66_82
(The National Archives , C 66/82)
msd:msd_tna_pat_66_83
(The National Archives , C 66/83)
msd:msd_tna_pat_66_84
(The National Archives , C 66/84)
msd:msd_tna_pat_66_85
(The National Archives , C 66/85)
msd:msd_tna_pat_66_86
(The National Archives , C 66/86)
msd:msd_tna_pat_66_87
(The National Archives , C 66/87)
msd:msd_tna_pat_66_88
(The National Archives , C 66/88)
msd:msd_tna_pat_66_89
(The National Archives , C 66/89)
msd:msd_tna_pat_66_9
(The National Archives , C 66/9)
msd:msd_tna_pat_66_90
(The National Archives , C 66/90)
msd:msd_tna_pat_66_91
(The National Archives , C 66/91)
msd:msd_tna_pat_66_92
(The National Archives , C 66/92)
msd:msd_tna_pat_66_93
(The National Archives , C 66/93)
msd:msd_tna_pat_66_94
(The National Archives , C 66/94)
msd:msd_tna_pat_66_95
(The National Archives , C 66/95)
msd:msd_tna_pat_66_96
(The National Archives , C 66/96)
msd:msd_tna_pat_66_97
(The National Archives , C 66/97)
msd:msd_tna_pat_66_98
(The National Archives , C 66/98)
msd:msd_tna_pat_66_99
(The National Archives , C 66/99)
msd:msd_tna_sc_1_14
(The National Archives , SC 1/14)
msd:msd_tna_sc_8_180
(The National Archives , SC 8/180)
msd:msd_wam_10
(Westminster Abbey Muniments Room , WAM)
msd:msd_wam_6075B
(Westminster Abbey Muniments Room , WAM 6075B)
msd:msd_wam_6690
(Westminster Abbey Muniments Room , WAM 6690)
msd:msd_wam_6703
(Westminster Abbey Muniments Room , WAM 6703)
msd:msd_wam_6726
(Westminster Abbey Muniments Room , WAM 6726)
msd:msd_wam_6733
(Westminster Abbey Muniments Room , WAM 6733)
msd:msd_wam_6745
(Westminster Abbey Muniments Room , WAM 6745)
msd:msd_wam_6746
(Westminster Abbey Muniments Room , WAM 6746)
msd:msd_wam_6754
(Westminster Abbey Muniments Room , WAM 6754)
msd:msd_wam_6757
(Westminster Abbey Muniments Room , WAM 6757)
msd:msd_wam_6771
(Westminster Abbey Muniments Room , WAM 6771)
msd:msd_wam_6781
(Westminster Abbey Muniments Room , WAM 6781)
msd:msd_wam_6787
(Westminster Abbey Muniments Room , WAM 6787)
msd:msd_wam_6788
(Westminster Abbey Muniments Room , WAM 6788)
msd:msd_wam_6789
(Westminster Abbey Muniments Room , WAM 6789)
msd:msd_wam_6791
(Westminster Abbey Muniments Room , WAM 6791)
msd:msd_wam_6792
(Westminster Abbey Muniments Room , WAM 6792)
msd:msd_wam_6793
(Westminster Abbey Muniments Room , WAM 6793)
msd:msd_wam_6796
(Westminster Abbey Muniments Room , WAM 6796)
msd:msd_wam_6797
(Westminster Abbey Muniments Room , WAM 6797)
msd:msd_wam_6799
(Westminster Abbey Muniments Room , WAM 6799)
msd:msd_wam_6800
(Westminster Abbey Muniments Room , WAM 6800)
msd:msd_wam_6801
(Westminster Abbey Muniments Room , WAM 6801)
msd:msd_wam_6802
(Westminster Abbey Muniments Room , WAM 6802)
msd:msd_wam_6804
(Westminster Abbey Muniments Room , WAM 6804)
msd:msd_wam_6805
(Westminster Abbey Muniments Room , WAM 6805)
msd:msd_wam_6806
(Westminster Abbey Muniments Room , WAM 6806)
msd:msd_wam_6807
(Westminster Abbey Muniments Room , WAM 6807)
msd:msd_wam_6808
(Westminster Abbey Muniments Room , WAM 6808)
msd:msd_wam_6810
(Westminster Abbey Muniments Room , WAM 6810)
msd:msd_wam_6812
(Westminster Abbey Muniments Room , WAM 6812)
msd:msd_wam_6814
(Westminster Abbey Muniments Room , WAM 6814)
msd:msd_wam_6815
(Westminster Abbey Muniments Room , WAM 6815)
msd:msd_wam_6817
(Westminster Abbey Muniments Room , WAM 6817)
msd:msd_wam_6818
(Westminster Abbey Muniments Room , WAM 6818)
msd:msd_wam_6819
(Westminster Abbey Muniments Room , WAM 6819)
msd:msd_wam_6820
(Westminster Abbey Muniments Room , WAM 6820)
msd:msd_wam_6821
(Westminster Abbey Muniments Room , WAM 6821)
msd:msd_wam_6822
(Westminster Abbey Muniments Room , WAM 6822)
msd:msd_wam_6823
(Westminster Abbey Muniments Room , WAM 6823)
msd:msd_wam_6824
(Westminster Abbey Muniments Room , WAM 6824)
msd:msd_wam_6827
(Westminster Abbey Muniments Room , WAM 6827)
msd:msd_wam_6829
(Westminster Abbey Muniments Room , WAM 6829)
msd:msd_wam_6832
(Westminster Abbey Muniments Room , WAM 6832)
msd:msd_wam_6835
(Westminster Abbey Muniments Room , WAM 6835)
msd:msd_wam_6836
(Westminster Abbey Muniments Room , WAM 6836)
msd:msd_wam_6838
(Westminster Abbey Muniments Room , WAM 6838)
msd:msd_wam_6841
(Westminster Abbey Muniments Room , WAM 6841)
msd:msd_wam_6846
(Westminster Abbey Muniments Room , WAM 6846)
msd:msd_wam_6847
(Westminster Abbey Muniments Room , WAM 6847)
msd:msd_wam_6848
(Westminster Abbey Muniments Room , WAM 6848)
msd:msd_wam_6855
(Westminster Abbey Muniments Room , WAM 6855)
msd:msd_wam_6857
(Westminster Abbey Muniments Room , WAM 6857)
msd:msd_wam_6861
(Westminster Abbey Muniments Room , WAM 6861)
msd:msd_wam_6862
(Westminster Abbey Muniments Room , WAM 6862)
msd:msd_wam_6866
(Westminster Abbey Muniments Room , WAM 6866)
msd:msd_wam_6869
(Westminster Abbey Muniments Room , WAM 6869)
msd:msd_wam_6871
(Westminster Abbey Muniments Room , WAM 6871)
msd:msd_wam_6875
(Westminster Abbey Muniments Room , WAM 6875)
msd:msd_wam_6879
(Westminster Abbey Muniments Room , WAM 6879)
msd:msd_wam_6888
(Westminster Abbey Muniments Room , WAM 6888)
msd:msd_wam_6889
(Westminster Abbey Muniments Room , WAM 6889)
msd:msd_wam_6893
(Westminster Abbey Muniments Room , WAM 6893)
msd:msd_wam_6898
(Westminster Abbey Muniments Room , WAM 6898)
msd:msd_wam_6899
(Westminster Abbey Muniments Room , WAM 6899)
msd:msd_wam_6901
(Westminster Abbey Muniments Room , WAM 6901)
msd:msd_wam_6904
(Westminster Abbey Muniments Room , WAM 6904)
msd:msd_wam_6908
(Westminster Abbey Muniments Room , WAM 6908)
msd:msd_wam_6934
(Westminster Abbey Muniments Room , WAM 6934)
msd:msd_wam_6935
(Westminster Abbey Muniments Room , WAM 6935)
msd:msd_wam_6936
(Westminster Abbey Muniments Room , WAM 6936)
msd:msd_wam_6939
(Westminster Abbey Muniments Room , WAM 6939)
msd:msd_wam_6955
(Westminster Abbey Muniments Room , WAM 6955)
msd:msd_wam_6982
(Westminster Abbey Muniments Room , WAM 6982)
msd:msd_wam_6989
(Westminster Abbey Muniments Room , WAM 6989)
msd:msd_wam_6995
(Westminster Abbey Muniments Room , WAM 6995)
msd:msd_wam_9006
(Westminster Abbey Muniments Room , WAM 9006)
msd:msd_wam_9007
(Westminster Abbey Muniments Room , WAM 9007)
msd:msd_wam_9007d
(Westminster Abbey Muniments Room , WAM 9007d)
msd:msd_wam_9025
(Westminster Abbey Muniments Room , WAM 9025)
msd:msd_wam_9029
(Westminster Abbey Muniments Room , WAM 9029)
msd:msd_wam_9036
(Westminster Abbey Muniments Room , WAM 9036)
msd:msd_wam_9049
(Westminster Abbey Muniments Room , WAM 9049)
msd:msd_wam_9072
(Westminster Abbey Muniments Room , WAM 9072)
msd:msd_wam_9079
(Westminster Abbey Muniments Room , WAM 9079)
msd:msd_wam_9080
(Westminster Abbey Muniments Room , WAM 9080)
msd:msd_wam_9094
(Westminster Abbey Muniments Room , WAM 9094)
msd:msd_wam_9127
(Westminster Abbey Muniments Room , WAM 9127)
msd:msd_wam_9131
(Westminster Abbey Muniments Room , WAM 9131)
msd:msd_wam_9139
(Westminster Abbey Muniments Room , WAM 9139)
msd:msd_wam_9146
(Westminster Abbey Muniments Room , WAM 9146)
msd:msd_wam_9173
(Westminster Abbey Muniments Room , WAM 9173)
bib:bib_SJC
(Abrahams, Israel, H. P. Stokes, H. Loewe, Fredman Ashe Lincoln, William Searle Holdsworth, William Page, and Archibald Jackson. Starrs and Jewish Charters Preserved in the British Museum. Volume 1. Printed for the Society at the University Press. 1930-1932.)
bib:bib_abra1_2022
(Abrams, Rebecca, Licoricia of Winchester, Power and Prejudice in Medieval England. Unicorn. 2022.)
bib:bib_adle1_1939
(Adler, Michael, The Jews of Medieval England, London: Jewish Historical Society of England, 1939.)
bib:bib_bart1_2015
(Bartlet, Suzanne, Licoricia of Winchester: Marriage, Motherhood, and Murder in the Medieval Anglo-Jewish Community Vallentine Mitchell. 2015.)
bib:bib_bart1_2000
(Bartlet, Suzanne, Three Jewish Business Women in Thirteenth-Century Winchester, Jewish Culture and History 3, no. 2 (2000): 31–54.)
bib:bib_bran1_2004
(Brand, Paul, Menahem, Elijah [known as Master Elias], Oxford Dictionary of National Biography, 2004. .)
bib:bib_brow1_2019
(Brown, Reva Berman, and Sean McCartney, David of Oxford and Licoricia of Winchester: Glimpses into a Jewish Family in Thirteenth-Century England, Jewish Historical Studies 39 (2004): 1–34.)
bib:bib_butl1_nd
(Butler, Sara, Who Killed Licoricia of Winchester? A Medieval Murder Mystery, Legal History Miscellany. n.d. .)
bib:bib_Causton
(Causton, Ann. Medieval Jewish Documents in Westminster Abbey. London: Jewish Historical Society of England. 2007.)
bib:bib_chew1_1927
(Chew, Helena M. A Jewish Aid to Marry, A.D. 1221, Transactions of the Jewish Historical Society of England 11 (1924–1927), pp. 92–111.)
bib:bib_dace1_2007
(Dace, Richard, The Jews of Warwick c.1180–c.1280, Local Historian, 37 (2007), 243–49. https://www.hastang.co.uk/pdf/Local%20Historian%2037%204.pdf.)
bib:bib_Davis
(Davis, M. D.. Hebrew Deeds of English Jews Before 1290. Gregg International. 1969.)
bib:bib_elij_1956
(Elijah Menahem ben Moses, The Writings of Rabbi Elijah of London, edited from MSS with an introduction and notes by Rabbi M.Y.L. Sacks and biography of the author by Prof. Cecil Roth. Jerusalem: Mossad Rav Kook. 1956.)
bib:bib_cave1_2021
(Emma Cavell, The Measure of Her Actions: A Quantitative Assessment of Anglo-Jewish Women’s Litigation at the Exchequer of the Jews, 1219–81, Law and History Review 39.1 (2021): 135–72.)
bib:bib_fogl1_2019
(Fogle, Lauren, The King’s Converts: Conversion in Medieval London. Lexington Books. 2019.)
bib:bib_fria1_1907
(Friaries: The house of White Friars, in A History of the County of Oxford: Volume 2, ed. William Page (London, 1907), pp.137–143, accessible at British History Online http://www.british-history.ac.uk/vch/oxon/vol2/pp137-143.)
bib:bib_frie1_1987
(Friedenberg, Daniel M., Medieval Jewish Seals from Europe. Wayne State UP. 1987.)
bib:bib_gold1_2012
(Goldy, Charlotte Newman, Muriel, a Jew of Oxford: Using the Dramatic to Understand the Mundane in Anglo-Norman Towns, in Writing Medieval Women’s Lives, ed. Charlotte Newman Goldy and Amy Livingstone (New York: Palgrave Macmillan, 2012), pp.227–245.)
bib:bib_CChR_1199
(Great Britain. Calendar of Charter Rolls Preserved in the Public Record Office (Rotuli Chartarum in Turri Londinensi Asservati), edited by Thomas Duffus Hardy. Volume 1, part 1, 1199-1216. 1837.)
bib:bib_CChR_1226
(Great Britain. Calendar of Charter Rolls Preserved in the Public Record Office. Volume 1, Henry III, 1226-1257. 1903.)
bib:bib_CChR_1257
(Great Britain. Calendar of Charter Rolls Preserved in the Public Record Office. Volume 2, Henry III-Edward I, 1257-1300. 1906.)
bib:bib_CFR_1272
(Great Britain. Calendar of fine rolls preserved in the Public Record Office. Vol. 1, Edward I, 1272-1307. London: H.M. Stationery Office, 1911.)
bib:bib_CCR_1272
(Great Britain. Calendar of the Close Rolls Preserved in the Public Record Office. Edward I, 1272-1279. London: Public Record Office, 1900.)
bib:bib_CCR_1279
(Great Britain. Calendar of the Close Rolls Preserved in the Public Record Office. Edward I, 1279-1288. London: H.M. Stationery Office, 1902.)
bib:bib_CCR_1288
(Great Britain. Calendar of the Close Rolls Preserved in the Public Record Office. Edward I, 1288-1296. London: H.M. Stationery Office, 1904.)
bib:bib_CCR_1296
(Great Britain. Calendar of the Close Rolls Preserved in the Public Record Office. Edward I, 1296-1302. London: H.M. Stationery Office, 1906.)
bib:bib_CCR_1227
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 1, 1227-1231. London: H.M. Stationery Office, 1902.)
bib:bib_CCR_1256
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 10, 1256-1259. London: Public Record Office, 1932.)
bib:bib_CCR_1259
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 11, 1259-1261. London: Public Record Office, 1934.)
bib:bib_CCR_1261
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 12, 1261-1264. London: Public Record Office, 1936.)
bib:bib_CCR_1264
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 13, 1264-1268. London: Public Record Office, 1937.)
bib:bib_CCR_1268
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 14, 1268-1272. London: Public Record Office, 1938.)
bib:bib_CCR_1231
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 2, 1231-1234. London: H.M. Stationery Office, 1905.)
bib:bib_CCR_1234
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 3, 1234-1237. London: H.M. Stationery Office, 1908.)
bib:bib_CCR_1237
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 4, 1237-1242. London: H.M. Stationery Office, 1911.)
bib:bib_CCR_1242
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 5, 1242-1247. London: Public Record Office, 1916.)
bib:bib_CCR_1247
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 6, 1247-1251. London: Public Record Office, 1922.)
bib:bib_CCR_1251
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 7, 1251-1253. London: Public Record Office, 1927.)
bib:bib_CCR_1253
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 8, 1253-1254. London: Public Record Office, 1929.)
bib:bib_CCR_1254
(Great Britain. Calendar of the Close Rolls of Henry III, Preserved in the Public Record Office. Volume 9, 1254-1256. London: Public Record Office, 1931.)
bib:bib_CPR_1201
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office (Rotuli Litterarum Patentium in Turri Londinensi Asservati), edited by Thomas Duffus Hardy. Volume 1, part 1, 1201-1216. 1835.)
bib:bib_CPR_1216
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1216-1225. London: H.M. Stationery Office, 1901.)
bib:bib_CPR_1225
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1225-1232. London: H.M. Stationery Office, 1903.)
bib:bib_CPR_1232
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1232-1247. London: H.M. Stationery Office, 1906.)
bib:bib_CPR_1247
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1247-1258. London: H.M. Stationery Office, 1908.)
bib:bib_CPR_1258
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1258-1266. London: H.M. Stationery Office, 1910.)
bib:bib_CPR_1266
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1266-1272. London: H.M. Stationery Office, 1913.)
bib:bib_CPR_1272a
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1272-1273. Appendix 3 in the Forty-Second Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1881.)
bib:bib_CPR_1272b
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1272-1281. London: H.M. Stationery Office, 1901.)
bib:bib_CPR_1273
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1273-1274. Appendix 1 in the Forty-Third Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1882.)
bib:bib_CPR_1274
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1274-1275. Appendix 1 in the Forty-Fourth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1883.)
bib:bib_CPR_1275
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1275-1276. Appendix 2 in the Forty-Fifth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1885.)
bib:bib_CPR_1276
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1276-1277. Appendix 2 in the Forty-Sixth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1886.)
bib:bib_CPR_1277
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1277-1278. Appendix 7 in the Forty-Seventh Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1886.)
bib:bib_CPR_1278
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1278-1279. Appendix 1 in the Forty-Eighth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1887.)
bib:bib_CPR_1279
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1279-1280. Appendix 1 in the Forty-Ninth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1888.)
bib:bib_CPR_1280
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1280-1281. Appendix 1 in the Fiftieth Annual Report of the Deputy Keeper of the Public Records, London, Eyre and Spottiswoode, 1889.)
bib:bib_CPR_1281
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1281-1292. London: H.M. Stationery Office, 1893.)
bib:bib_CPR_1292
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1292-1301. London: H.M. Stationery Office, 1895.)
bib:bib_CPR_1301
(Great Britain. Calendar of the Patent Rolls Preserved in the Public Record Office. 1301-1307. London: H.M. Stationery Office, 1898.)
bib:bib_PREJ_1
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 1, Henry III, A.D., 1218-1272, edited by J. M. Rigg. Published for the Jewish Historical Society of England by Macmillan & Co., London. 1905. .)
bib:bib_PREJ_2
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 2, Edward I, 1273-1275, edited and translated by Hilary Jenkinson. Published for the Jewish Historical Society of England by Ballantyne, Edinburgh. 1910.)
bib:bib_PREJ_3
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 3, Edward I, 1275-1277, edited and translated by Hilary Jenkinson. Published for the Jewish Historical Society of England by Spottiswoode, Ballantyne and Co. Ltd., Colchester. 1929.)
bib:bib_PREJ_4
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 4, Henry III, 1272; Edward I, 1275-1277, edited and translated by H. G. Richardson. Published for the Jewish Historical Society of England by Spottiswoode, Colchester. 1972.)
bib:bib_PREJ_5
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 5, Edward I, 1277-79, edited by Sarah Cohen and Paul Brand. London: Jewish Historical Society of England. 1992.)
bib:bib_PREJ_6
(Great Britain. Calendar of the Plea Rolls of the Exchequer of the Jews Preserved in the Public Record Office. Vol. 6, Edward I, 1279-1281, edited and translated by Paul Brand. London: Jewish Historical Society of England. 2005.)
bib:bib_FRH3
(Great Britain. Calendar of the fine rolls of the reign of Henry III : preserved in the National Archives, edited by Paul Dryburgh, Beth Hartland, Arianna Ciula, et al. The National Archives and Kingʼs College London, 2009. https://finerollshenry3.org.uk/home.html.)
bib:bib_PAT_1
(Great Britain. Court of Chancery. Calendar of the Patent Rolls Preserved in the Public Record Office Henry III, AD 1247-1258. London: H.M. Stationery Office, 1908.)
bib:bib_SPC
(Great Britain. Select Pleas of the Crown, Volume I, A.D. 1200-1225, edited by F. W. Maitland for the Selden Society. 1888.)
bib:bib_Rigg
(Great Britain. Select Pleas, Starrs, and Other Records from the Rolls of the Exchequer of the Jews, A.D. 1220–1284, edited by J.M. Rigg. London: Bernard Quaritch 1902.)
bib:bib_hill2_2001
(Hillaby Joe, Testimony from the Margin: The Gloucester Jewry and Its Neighbours, c.1159–1290, Jewish Historical Studies 37 (2001): 41–112.)
bib:bib_hill1_2015
(Hillaby, J. and C. Hillaby, The Palgrave Dictionary of Medieval Anglo-Jewish History. London: Palgrave. 2015.)
bib:bib_towr1_2022
(Historical Royal Palaces, The Jewish History of the Medieval Tower of London. 2022. https://www.hrp.org.uk/about-us/research/the-jewish-history-of-the-medieval-tower-of-london/#outputs.)
bib:bib_hoyl1_2008
(Hoyle, Victoria, The Bonds that Bind: Moneylending between Anglo-Jewish and Christian Women in the Plea Rolls of the Exchequer of the Jews, 1218–1280, Journal of Medieval History 38 (2008), pp.119–129.)
bib:bib_irwi1_2023
(Irwin, Dean A., Social Hierarchies and Networks in the Thirteenth-Century London Jewry, in Thirteenth Century England 18: Proceedings of the Cambridge Conference, 2019, ed. Andrew Spencer and Carl Watkins (Woodbridge: Boydell, 2023), pp. 189–207.)
bib:bib_Lipman
(Lipman, V. D. The Jews of Medieval Norwich. London: Jewish Historical Society of England. 1967.)
bib:bib_Logan
(Logan, F. Donald. Thirteen London Jews and Conversion to Christianity: Problems of Apostasy in the 1280s. Historical Research 45(112): 214–229. 2007.)
bib:bib_macl1_nd
(MacLellan, Rory, Jewish History of the Medieval Tower of London, https://www.hrp.org.uk/about-us/research/the-jewish-history-of-the-medieval-tower-of-london/#outputs.)
bib:bib_meye1_nd
(Meyer, Hannah, Licoricia of Winchester (d. 1277), ODNB. n.d. .)
bib:bib_mund1_1998
(Mundill, Robin R., England’s Jewish Solution: Experiment and Expulsion, 1262–1290, Cambridge: Cambridge UP, 1998.)
bib:bib_mund1_1992
(Mundill, Robin R., The Jewish Entries from the Patent Rolls, 1272–1292, Jewish Historical Studies 32 (1990–1992).)
bib:bib_HHLD_1
(Olszowy-Schlanger, J., ed. Hebrew and Hebrew-Latin Documents from Medieval England: A Diplomatic and Palaeographical Study. Volume 1. Turnhout: Brepols. 2015.)
bib:bib_HHLD_2
(Olszowy-Schlanger, J., ed. Hebrew and Hebrew-Latin Documents from Medieval England: A Diplomatic and Palaeographical Study. Volume 2. Turnhout: Brepols. 2015.)
bib:bib_park1_1992
(Parkes, Malcolm, The Provision of Books, in The History of the University of Oxford, vol. 2, Late Medieval Oxford, ed. J.I. Catto and T.A.R. Evans (Oxford: Clarendon, 1992), pp.407–483.)
bib:bib_roke1_1992a
(Rokéah, Zefira Entin, Money and the Hangman in Late-13th-Century England: Jews, Christians and Coinage Offenses Alleged and Real (Part I), Jewish Historical Studies 31 (1988-1990): 83–109.)
bib:bib_roke1_1992b
(Rokéah, Zefira Entin, Money and the Hangman in Late-13th-Century England: Jews, Christians and Coinage Offenses Alleged and Real (Part II), Jewish Historical Studies 32 (1990-1992): 159–218.)
bib:bib_roke1_2000
(Rokéah, Zefira Entin. Medieval English Jews and Royal Officials: Entries of Jewish Interest in the English Memoranda Rolls, 1266-1293. The Hebrew University Magnes Press, Jerusalem, 2000.)
bib:bib_sira1_2004
(Sirat, Colette, Looking at Latin Books, Understanding Latin Texts: Different Attitudes in Different Jewish Communities, in Hebrew to Latin, Latin to Hebrew: The Mirroring of the Two Cultures in the Age of Humanism, ed. Giulio Busi (Berlin: Institut für Judaistik, Freie Universität Berlin, 2004), pp.7–22.)
bib:bib_will1_2021
(Williams Boyarin, Adrienne, The Christian Jew and the Unmarked Jewess: The Polemics of Sameness in Medieval English Anti-Judaism. The Middle Ages Series. University of Pennsylvania Press. 2021.)
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   attribute corresp
   {
      list
      {
         (
            "msd:msd_bcl_256_307191"
          | "msd:msd_bl_add_7218"
          | "msd:msd_bl_add_Ch_1250"
          | "msd:msd_bl_add_Roll_19299"
          | "msd:msd_bl_cot_Nero_C_III"
          | "msd:msd_bl_harl_Ch_43_A_54"
          | "msd:msd_bl_harl_Ch_43_A_56"
          | "msd:msd_bl_harl_Ch_84D"
          | "msd:msd_bl_harl_Chart_43A"
          | "msd:msd_bl_harl_Chart_43A_59A"
          | "msd:msd_bl_lans_Ch_665"
          | "msd:msd_bl_lans_Ch_666"
          | "msd:msd_bl_lans_Ch_667"
          | "msd:msd_bl_lans_Ch_668"
          | "msd:msd_bl_lans_Ch_669"
          | "msd:msd_magd_ald_34"
          | "msd:msd_mert_14_D_I_58_i"
          | "msd:msd_mert_mcr_188"
          | "msd:msd_tna_13_Item_98"
          | "msd:msd_tna_15_27_189"
          | "msd:msd_tna_9_26_115B"
          | "msd:msd_tna_9_26_35"
          | "msd:msd_tna_c_143_10_14"
          | "msd:msd_tna_c_145_17_3"
          | "msd:msd_tna_c_145_35_56"
          | "msd:msd_tna_c_255_18_5B"
          | "msd:msd_tna_c_53_13"
          | "msd:msd_tna_c_53_2"
          | "msd:msd_tna_c_53_20"
          | "msd:msd_tna_c_53_26"
          | "msd:msd_tna_c_53_29"
          | "msd:msd_tna_c_53_44"
          | "msd:msd_tna_c_53_47"
          | "msd:msd_tna_c_53_64"
          | "msd:msd_tna_c_53_68"
          | "msd:msd_tna_c_53_69"
          | "msd:msd_tna_c_53_70"
          | "msd:msd_tna_c_53_78"
          | "msd:msd_tna_c_54_101"
          | "msd:msd_tna_c_54_105"
          | "msd:msd_tna_c_54_106"
          | "msd:msd_tna_c_54_107"
          | "msd:msd_tna_c_54_114"
          | "msd:msd_tna_c_54_117"
          | "msd:msd_tna_c_54_38"
          | "msd:msd_tna_c_54_41"
          | "msd:msd_tna_c_54_42"
          | "msd:msd_tna_c_54_43"
          | "msd:msd_tna_c_54_44"
          | "msd:msd_tna_c_54_45"
          | "msd:msd_tna_c_54_46"
          | "msd:msd_tna_c_54_47"
          | "msd:msd_tna_c_54_48"
          | "msd:msd_tna_c_54_49"
          | "msd:msd_tna_c_54_51"
          | "msd:msd_tna_c_54_52"
          | "msd:msd_tna_c_54_53"
          | "msd:msd_tna_c_54_57"
          | "msd:msd_tna_c_54_59"
          | "msd:msd_tna_c_54_60"
          | "msd:msd_tna_c_54_61"
          | "msd:msd_tna_c_54_62"
          | "msd:msd_tna_c_54_63"
          | "msd:msd_tna_c_54_64"
          | "msd:msd_tna_c_54_68"
          | "msd:msd_tna_c_54_69"
          | "msd:msd_tna_c_54_70"
          | "msd:msd_tna_c_54_71"
          | "msd:msd_tna_c_54_72"
          | "msd:msd_tna_c_54_73"
          | "msd:msd_tna_c_54_74"
          | "msd:msd_tna_c_54_75"
          | "msd:msd_tna_c_54_76"
          | "msd:msd_tna_c_54_77"
          | "msd:msd_tna_c_54_78"
          | "msd:msd_tna_c_54_82"
          | "msd:msd_tna_c_54_83"
          | "msd:msd_tna_c_54_84"
          | "msd:msd_tna_c_54_85"
          | "msd:msd_tna_c_54_86"
          | "msd:msd_tna_c_54_87"
          | "msd:msd_tna_c_54_88"
          | "msd:msd_tna_c_54_89"
          | "msd:msd_tna_c_54_91"
          | "msd:msd_tna_c_54_92"
          | "msd:msd_tna_c_54_93"
          | "msd:msd_tna_c_54_94"
          | "msd:msd_tna_c_54_95"
          | "msd:msd_tna_c_54_96"
          | "msd:msd_tna_c_54_97"
          | "msd:msd_tna_c_54_98"
          | "msd:msd_tna_c_54_99"
          | "msd:msd_tna_c_60_16"
          | "msd:msd_tna_c_60_24"
          | "msd:msd_tna_c_60_27"
          | "msd:msd_tna_c_60_28"
          | "msd:msd_tna_c_60_29"
          | "msd:msd_tna_c_60_31"
          | "msd:msd_tna_c_60_32"
          | "msd:msd_tna_c_60_34"
          | "msd:msd_tna_c_60_35"
          | "msd:msd_tna_c_60_36"
          | "msd:msd_tna_c_60_37"
          | "msd:msd_tna_c_60_40"
          | "msd:msd_tna_c_60_40A"
          | "msd:msd_tna_c_60_41"
          | "msd:msd_tna_c_60_46"
          | "msd:msd_tna_c_60_47"
          | "msd:msd_tna_c_60_48"
          | "msd:msd_tna_c_60_49"
          | "msd:msd_tna_c_60_50"
          | "msd:msd_tna_c_60_52"
          | "msd:msd_tna_c_60_53"
          | "msd:msd_tna_c_60_54"
          | "msd:msd_tna_c_60_55"
          | "msd:msd_tna_c_60_56"
          | "msd:msd_tna_c_60_58"
          | "msd:msd_tna_c_60_59"
          | "msd:msd_tna_c_60_80"
          | "msd:msd_tna_c_60_82"
          | "msd:msd_tna_c_60_83"
          | "msd:msd_tna_c_60_9"
          | "msd:msd_tna_c_67_4"
          | "msd:msd_tna_c_85_170"
          | "msd:msd_tna_c_85_3_71"
          | "msd:msd_tna_c_85_99"
          | "msd:msd_tna_e_101_13_8_"
          | "msd:msd_tna_e_101_249"
          | "msd:msd_tna_e_101_249_19"
          | "msd:msd_tna_e_101_249_20"
          | "msd:msd_tna_e_101_249_22"
          | "msd:msd_tna_e_101_249_8"
          | "msd:msd_tna_e_101_250"
          | "msd:msd_tna_e_159_41"
          | "msd:msd_tna_e_159_42"
          | "msd:msd_tna_e_159_43"
          | "msd:msd_tna_e_159_44"
          | "msd:msd_tna_e_159_45"
          | "msd:msd_tna_e_159_46"
          | "msd:msd_tna_e_159_47"
          | "msd:msd_tna_e_159_48"
          | "msd:msd_tna_e_159_49"
          | "msd:msd_tna_e_159_50"
          | "msd:msd_tna_e_159_51"
          | "msd:msd_tna_e_159_52"
          | "msd:msd_tna_e_159_53"
          | "msd:msd_tna_e_159_54"
          | "msd:msd_tna_e_159_55"
          | "msd:msd_tna_e_159_56"
          | "msd:msd_tna_e_159_57"
          | "msd:msd_tna_e_159_58"
          | "msd:msd_tna_e_159_59"
          | "msd:msd_tna_e_159_60"
          | "msd:msd_tna_e_159_61"
          | "msd:msd_tna_e_159_62"
          | "msd:msd_tna_e_159_63"
          | "msd:msd_tna_e_159_64"
          | "msd:msd_tna_e_159_65"
          | "msd:msd_tna_e_159_66"
          | "msd:msd_tna_e_199_39"
          | "msd:msd_tna_e_32_12"
          | "msd:msd_tna_e_368_41"
          | "msd:msd_tna_e_368_42"
          | "msd:msd_tna_e_368_43"
          | "msd:msd_tna_e_368_44"
          | "msd:msd_tna_e_368_45"
          | "msd:msd_tna_e_368_46"
          | "msd:msd_tna_e_368_47"
          | "msd:msd_tna_e_368_48"
          | "msd:msd_tna_e_368_49"
          | "msd:msd_tna_e_368_50"
          | "msd:msd_tna_e_368_51"
          | "msd:msd_tna_e_368_52"
          | "msd:msd_tna_e_368_53"
          | "msd:msd_tna_e_368_54"
          | "msd:msd_tna_e_368_55"
          | "msd:msd_tna_e_368_56"
          | "msd:msd_tna_e_368_57"
          | "msd:msd_tna_e_368_58"
          | "msd:msd_tna_e_368_59"
          | "msd:msd_tna_e_368_60"
          | "msd:msd_tna_e_368_61"
          | "msd:msd_tna_e_368_62"
          | "msd:msd_tna_e_368_63"
          | "msd:msd_tna_e_368_64"
          | "msd:msd_tna_e_370_2"
          | "msd:msd_tna_e_371_3"
          | "msd:msd_tna_e_371_4"
          | "msd:msd_tna_e_371_7"
          | "msd:msd_tna_e_401_1564"
          | "msd:msd_tna_e_401_1565"
          | "msd:msd_tna_e_401_1573"
          | "msd:msd_tna_e_401_1574"
          | "msd:msd_tna_e_401_1576"
          | "msd:msd_tna_e_401_1586"
          | "msd:msd_tna_e_401_1590"
          | "msd:msd_tna_e_401_4"
          | "msd:msd_tna_e_402_3A"
          | "msd:msd_tna_e_402_3B"
          | "msd:msd_tna_e_40_1478"
          | "msd:msd_tna_e_9_1"
          | "msd:msd_tna_e_9_10"
          | "msd:msd_tna_e_9_11"
          | "msd:msd_tna_e_9_12"
          | "msd:msd_tna_e_9_13"
          | "msd:msd_tna_e_9_14"
          | "msd:msd_tna_e_9_15"
          | "msd:msd_tna_e_9_16"
          | "msd:msd_tna_e_9_17"
          | "msd:msd_tna_e_9_18"
          | "msd:msd_tna_e_9_183"
          | "msd:msd_tna_e_9_19"
          | "msd:msd_tna_e_9_2"
          | "msd:msd_tna_e_9_20"
          | "msd:msd_tna_e_9_21"
          | "msd:msd_tna_e_9_22"
          | "msd:msd_tna_e_9_23"
          | "msd:msd_tna_e_9_24"
          | "msd:msd_tna_e_9_25"
          | "msd:msd_tna_e_9_26"
          | "msd:msd_tna_e_9_27"
          | "msd:msd_tna_e_9_28"
          | "msd:msd_tna_e_9_29"
          | "msd:msd_tna_e_9_3"
          | "msd:msd_tna_e_9_30"
          | "msd:msd_tna_e_9_31_and_70"
          | "msd:msd_tna_e_9_32"
          | "msd:msd_tna_e_9_32_and_64"
          | "msd:msd_tna_e_9_33"
          | "msd:msd_tna_e_9_34_and_65"
          | "msd:msd_tna_e_9_35"
          | "msd:msd_tna_e_9_36"
          | "msd:msd_tna_e_9_37"
          | "msd:msd_tna_e_9_38"
          | "msd:msd_tna_e_9_39"
          | "msd:msd_tna_e_9_4"
          | "msd:msd_tna_e_9_40"
          | "msd:msd_tna_e_9_41"
          | "msd:msd_tna_e_9_42"
          | "msd:msd_tna_e_9_43"
          | "msd:msd_tna_e_9_45"
          | "msd:msd_tna_e_9_49"
          | "msd:msd_tna_e_9_5"
          | "msd:msd_tna_e_9_52"
          | "msd:msd_tna_e_9_53"
          | "msd:msd_tna_e_9_54"
          | "msd:msd_tna_e_9_6"
          | "msd:msd_tna_e_9_62"
          | "msd:msd_tna_e_9_66"
          | "msd:msd_tna_e_9_7"
          | "msd:msd_tna_e_9_8"
          | "msd:msd_tna_e_9_9"
          | "msd:msd_tna_pat_66_1"
          | "msd:msd_tna_pat_66_10"
          | "msd:msd_tna_pat_66_100"
          | "msd:msd_tna_pat_66_101"
          | "msd:msd_tna_pat_66_102"
          | "msd:msd_tna_pat_66_103"
          | "msd:msd_tna_pat_66_104"
          | "msd:msd_tna_pat_66_105"
          | "msd:msd_tna_pat_66_105A"
          | "msd:msd_tna_pat_66_106"
          | "msd:msd_tna_pat_66_106A"
          | "msd:msd_tna_pat_66_107"
          | "msd:msd_tna_pat_66_108"
          | "msd:msd_tna_pat_66_109"
          | "msd:msd_tna_pat_66_11"
          | "msd:msd_tna_pat_66_110"
          | "msd:msd_tna_pat_66_111"
          | "msd:msd_tna_pat_66_112"
          | "msd:msd_tna_pat_66_113"
          | "msd:msd_tna_pat_66_114"
          | "msd:msd_tna_pat_66_115"
          | "msd:msd_tna_pat_66_116"
          | "msd:msd_tna_pat_66_117"
          | "msd:msd_tna_pat_66_118"
          | "msd:msd_tna_pat_66_119"
          | "msd:msd_tna_pat_66_12"
          | "msd:msd_tna_pat_66_120"
          | "msd:msd_tna_pat_66_121"
          | "msd:msd_tna_pat_66_122"
          | "msd:msd_tna_pat_66_123"
          | "msd:msd_tna_pat_66_124"
          | "msd:msd_tna_pat_66_125"
          | "msd:msd_tna_pat_66_126"
          | "msd:msd_tna_pat_66_127"
          | "msd:msd_tna_pat_66_128"
          | "msd:msd_tna_pat_66_129"
          | "msd:msd_tna_pat_66_13"
          | "msd:msd_tna_pat_66_130"
          | "msd:msd_tna_pat_66_14"
          | "msd:msd_tna_pat_66_15"
          | "msd:msd_tna_pat_66_16"
          | "msd:msd_tna_pat_66_17"
          | "msd:msd_tna_pat_66_18"
          | "msd:msd_tna_pat_66_19"
          | "msd:msd_tna_pat_66_2"
          | "msd:msd_tna_pat_66_20"
          | "msd:msd_tna_pat_66_21"
          | "msd:msd_tna_pat_66_22"
          | "msd:msd_tna_pat_66_23"
          | "msd:msd_tna_pat_66_24"
          | "msd:msd_tna_pat_66_25"
          | "msd:msd_tna_pat_66_26"
          | "msd:msd_tna_pat_66_27"
          | "msd:msd_tna_pat_66_28"
          | "msd:msd_tna_pat_66_29"
          | "msd:msd_tna_pat_66_3"
          | "msd:msd_tna_pat_66_30"
          | "msd:msd_tna_pat_66_31"
          | "msd:msd_tna_pat_66_32"
          | "msd:msd_tna_pat_66_33"
          | "msd:msd_tna_pat_66_34"
          | "msd:msd_tna_pat_66_35"
          | "msd:msd_tna_pat_66_36"
          | "msd:msd_tna_pat_66_37"
          | "msd:msd_tna_pat_66_38"
          | "msd:msd_tna_pat_66_39"
          | "msd:msd_tna_pat_66_4"
          | "msd:msd_tna_pat_66_40"
          | "msd:msd_tna_pat_66_41"
          | "msd:msd_tna_pat_66_42"
          | "msd:msd_tna_pat_66_43"
          | "msd:msd_tna_pat_66_44"
          | "msd:msd_tna_pat_66_45"
          | "msd:msd_tna_pat_66_46"
          | "msd:msd_tna_pat_66_47"
          | "msd:msd_tna_pat_66_48"
          | "msd:msd_tna_pat_66_49"
          | "msd:msd_tna_pat_66_5"
          | "msd:msd_tna_pat_66_50"
          | "msd:msd_tna_pat_66_51"
          | "msd:msd_tna_pat_66_52"
          | "msd:msd_tna_pat_66_53"
          | "msd:msd_tna_pat_66_54"
          | "msd:msd_tna_pat_66_55"
          | "msd:msd_tna_pat_66_56"
          | "msd:msd_tna_pat_66_57"
          | "msd:msd_tna_pat_66_58"
          | "msd:msd_tna_pat_66_59"
          | "msd:msd_tna_pat_66_6"
          | "msd:msd_tna_pat_66_60"
          | "msd:msd_tna_pat_66_61"
          | "msd:msd_tna_pat_66_62"
          | "msd:msd_tna_pat_66_63"
          | "msd:msd_tna_pat_66_64"
          | "msd:msd_tna_pat_66_65"
          | "msd:msd_tna_pat_66_66"
          | "msd:msd_tna_pat_66_67"
          | "msd:msd_tna_pat_66_68"
          | "msd:msd_tna_pat_66_69"
          | "msd:msd_tna_pat_66_7"
          | "msd:msd_tna_pat_66_70"
          | "msd:msd_tna_pat_66_71"
          | "msd:msd_tna_pat_66_72"
          | "msd:msd_tna_pat_66_73"
          | "msd:msd_tna_pat_66_74"
          | "msd:msd_tna_pat_66_75"
          | "msd:msd_tna_pat_66_76"
          | "msd:msd_tna_pat_66_77"
          | "msd:msd_tna_pat_66_78"
          | "msd:msd_tna_pat_66_79"
          | "msd:msd_tna_pat_66_8"
          | "msd:msd_tna_pat_66_80"
          | "msd:msd_tna_pat_66_81"
          | "msd:msd_tna_pat_66_82"
          | "msd:msd_tna_pat_66_83"
          | "msd:msd_tna_pat_66_84"
          | "msd:msd_tna_pat_66_85"
          | "msd:msd_tna_pat_66_86"
          | "msd:msd_tna_pat_66_87"
          | "msd:msd_tna_pat_66_88"
          | "msd:msd_tna_pat_66_89"
          | "msd:msd_tna_pat_66_9"
          | "msd:msd_tna_pat_66_90"
          | "msd:msd_tna_pat_66_91"
          | "msd:msd_tna_pat_66_92"
          | "msd:msd_tna_pat_66_93"
          | "msd:msd_tna_pat_66_94"
          | "msd:msd_tna_pat_66_95"
          | "msd:msd_tna_pat_66_96"
          | "msd:msd_tna_pat_66_97"
          | "msd:msd_tna_pat_66_98"
          | "msd:msd_tna_pat_66_99"
          | "msd:msd_tna_sc_1_14"
          | "msd:msd_tna_sc_8_180"
          | "msd:msd_wam_10"
          | "msd:msd_wam_6075B"
          | "msd:msd_wam_6690"
          | "msd:msd_wam_6703"
          | "msd:msd_wam_6726"
          | "msd:msd_wam_6733"
          | "msd:msd_wam_6745"
          | "msd:msd_wam_6746"
          | "msd:msd_wam_6754"
          | "msd:msd_wam_6757"
          | "msd:msd_wam_6771"
          | "msd:msd_wam_6781"
          | "msd:msd_wam_6787"
          | "msd:msd_wam_6788"
          | "msd:msd_wam_6789"
          | "msd:msd_wam_6791"
          | "msd:msd_wam_6792"
          | "msd:msd_wam_6793"
          | "msd:msd_wam_6796"
          | "msd:msd_wam_6797"
          | "msd:msd_wam_6799"
          | "msd:msd_wam_6800"
          | "msd:msd_wam_6801"
          | "msd:msd_wam_6802"
          | "msd:msd_wam_6804"
          | "msd:msd_wam_6805"
          | "msd:msd_wam_6806"
          | "msd:msd_wam_6807"
          | "msd:msd_wam_6808"
          | "msd:msd_wam_6810"
          | "msd:msd_wam_6812"
          | "msd:msd_wam_6814"
          | "msd:msd_wam_6815"
          | "msd:msd_wam_6817"
          | "msd:msd_wam_6818"
          | "msd:msd_wam_6819"
          | "msd:msd_wam_6820"
          | "msd:msd_wam_6821"
          | "msd:msd_wam_6822"
          | "msd:msd_wam_6823"
          | "msd:msd_wam_6824"
          | "msd:msd_wam_6827"
          | "msd:msd_wam_6829"
          | "msd:msd_wam_6832"
          | "msd:msd_wam_6835"
          | "msd:msd_wam_6836"
          | "msd:msd_wam_6838"
          | "msd:msd_wam_6841"
          | "msd:msd_wam_6846"
          | "msd:msd_wam_6847"
          | "msd:msd_wam_6848"
          | "msd:msd_wam_6855"
          | "msd:msd_wam_6857"
          | "msd:msd_wam_6861"
          | "msd:msd_wam_6862"
          | "msd:msd_wam_6866"
          | "msd:msd_wam_6869"
          | "msd:msd_wam_6871"
          | "msd:msd_wam_6875"
          | "msd:msd_wam_6879"
          | "msd:msd_wam_6888"
          | "msd:msd_wam_6889"
          | "msd:msd_wam_6893"
          | "msd:msd_wam_6898"
          | "msd:msd_wam_6899"
          | "msd:msd_wam_6901"
          | "msd:msd_wam_6904"
          | "msd:msd_wam_6908"
          | "msd:msd_wam_6934"
          | "msd:msd_wam_6935"
          | "msd:msd_wam_6936"
          | "msd:msd_wam_6939"
          | "msd:msd_wam_6955"
          | "msd:msd_wam_6982"
          | "msd:msd_wam_6989"
          | "msd:msd_wam_6995"
          | "msd:msd_wam_9006"
          | "msd:msd_wam_9007"
          | "msd:msd_wam_9007d"
          | "msd:msd_wam_9025"
          | "msd:msd_wam_9029"
          | "msd:msd_wam_9036"
          | "msd:msd_wam_9049"
          | "msd:msd_wam_9072"
          | "msd:msd_wam_9079"
          | "msd:msd_wam_9080"
          | "msd:msd_wam_9094"
          | "msd:msd_wam_9127"
          | "msd:msd_wam_9131"
          | "msd:msd_wam_9139"
          | "msd:msd_wam_9146"
          | "msd:msd_wam_9173"
          | "bib:bib_SJC"
          | "bib:bib_abra1_2022"
          | "bib:bib_adle1_1939"
          | "bib:bib_bart1_2015"
          | "bib:bib_bart1_2000"
          | "bib:bib_bran1_2004"
          | "bib:bib_brow1_2019"
          | "bib:bib_butl1_nd"
          | "bib:bib_Causton"
          | "bib:bib_chew1_1927"
          | "bib:bib_dace1_2007"
          | "bib:bib_Davis"
          | "bib:bib_elij_1956"
          | "bib:bib_cave1_2021"
          | "bib:bib_fogl1_2019"
          | "bib:bib_fria1_1907"
          | "bib:bib_frie1_1987"
          | "bib:bib_gold1_2012"
          | "bib:bib_CChR_1199"
          | "bib:bib_CChR_1226"
          | "bib:bib_CChR_1257"
          | "bib:bib_CFR_1272"
          | "bib:bib_CCR_1272"
          | "bib:bib_CCR_1279"
          | "bib:bib_CCR_1288"
          | "bib:bib_CCR_1296"
          | "bib:bib_CCR_1227"
          | "bib:bib_CCR_1256"
          | "bib:bib_CCR_1259"
          | "bib:bib_CCR_1261"
          | "bib:bib_CCR_1264"
          | "bib:bib_CCR_1268"
          | "bib:bib_CCR_1231"
          | "bib:bib_CCR_1234"
          | "bib:bib_CCR_1237"
          | "bib:bib_CCR_1242"
          | "bib:bib_CCR_1247"
          | "bib:bib_CCR_1251"
          | "bib:bib_CCR_1253"
          | "bib:bib_CCR_1254"
          | "bib:bib_CPR_1201"
          | "bib:bib_CPR_1216"
          | "bib:bib_CPR_1225"
          | "bib:bib_CPR_1232"
          | "bib:bib_CPR_1247"
          | "bib:bib_CPR_1258"
          | "bib:bib_CPR_1266"
          | "bib:bib_CPR_1272a"
          | "bib:bib_CPR_1272b"
          | "bib:bib_CPR_1273"
          | "bib:bib_CPR_1274"
          | "bib:bib_CPR_1275"
          | "bib:bib_CPR_1276"
          | "bib:bib_CPR_1277"
          | "bib:bib_CPR_1278"
          | "bib:bib_CPR_1279"
          | "bib:bib_CPR_1280"
          | "bib:bib_CPR_1281"
          | "bib:bib_CPR_1292"
          | "bib:bib_CPR_1301"
          | "bib:bib_PREJ_1"
          | "bib:bib_PREJ_2"
          | "bib:bib_PREJ_3"
          | "bib:bib_PREJ_4"
          | "bib:bib_PREJ_5"
          | "bib:bib_PREJ_6"
          | "bib:bib_FRH3"
          | "bib:bib_PAT_1"
          | "bib:bib_SPC"
          | "bib:bib_Rigg"
          | "bib:bib_hill2_2001"
          | "bib:bib_hill1_2015"
          | "bib:bib_towr1_2022"
          | "bib:bib_hoyl1_2008"
          | "bib:bib_irwi1_2023"
          | "bib:bib_Lipman"
          | "bib:bib_Logan"
          | "bib:bib_macl1_nd"
          | "bib:bib_meye1_nd"
          | "bib:bib_mund1_1998"
          | "bib:bib_mund1_1992"
          | "bib:bib_HHLD_1"
          | "bib:bib_HHLD_2"
          | "bib:bib_park1_1992"
          | "bib:bib_roke1_1992a"
          | "bib:bib_roke1_1992b"
          | "bib:bib_roke1_2000"
          | "bib:bib_sira1_2004"
          | "bib:bib_will1_2021"
         )+
      }
   }?,
   (
      text
    | model.gLike
    | model.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}

Appendix A.1.1.10 <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core
Attributes
unit identifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived from att.citing
Status Optional
Datatype teidata.enumerated
Legal values are:
issue
(issue (of a journal))
page
(page number or page-range)
item
(item number in a print or online source (starts with #))
srcMemFol
(The membrane or folio number in a primary source)
srcNum
(The number of a charter or other primary source document)
Member of
Contained by
core: bibl series
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   att.global.attributes,
   att.citing.attribute.from,
   att.citing.attribute.to,
   attribute unit { "issue" | "page" | "item" | "srcMemFol" | "srcNum" }?,
   macro.phraseSeq
}

Appendix A.1.1.11 <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element birth
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.dimensions.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.12 <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Module textstructure
Attributes
Contained by
textstructure: text
May contain
figures: figure table
linking: link linkGrp
msdescription: msDesc
textstructure: div
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   att.global.attributes,
   att.declaring.attributes,
   (
      model.global*,
      ( ( model.divTop, ( model.global | model.divTop )* )? ),
      ( ( model.divGenLike, ( model.global | model.divGenLike )* )? ),
      (
         ( ( model.divLike, ( model.global | model.divGenLike )* )+ )
       | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ )
       | (
            ( ( ( schemaSpec | model.common ), model.global* )+ ),
            (
               ( ( model.divLike, ( model.global | model.divGenLike )* )+ )
             | ( ( model.div1Like, ( model.global | model.divGenLike )* )+ )
            )?
         )
      ),
      ( ( model.divBottom, model.global* )* )
   )
}

Appendix A.1.1.13 <c>

<c> (character) represents a character. [17.1. Linguistic Segment Categories]
Module analysis
Attributes
Member of
Contained by
May contain Character data only
Note

Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc.

Example
<phr>  <c>M</c>  <c>O</c>  <c>A</c>  <c>I</c>  <w>doth</w>  <w>sway</w>  <w>my</w>  <w>life</w> </phr>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element c
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.notated.attributes,
   macro.xtext
}

Appendix A.1.1.14 <calendar>

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Module header
Attributes
Contained by
header: calendarDesc
May contain
core: p
Example
<calendarDesc>  <calendar xml:id="julianEngland">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendar
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   model.pLike+
}

Appendix A.1.1.15 <calendarDesc>

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
Module header
Attributes
Member of
Contained by
header: profileDesc
May contain
header: calendar
Note

In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <elementRef key="calendar" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendarDesc { att.global.attributes, calendar+ }

Appendix A.1.1.16 <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
Module header
Attributes
Contained by
header: category
May contain
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc> </catDesc>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
    
Schema Declaration
element catDesc
{
   att.global.attributes,
   att.canonical.attributes,
   ( text | model.limitedPhrase | model.catDescPart )*
}

Appendix A.1.1.17 <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Module header
Attributes
scheme identifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
Status Optional
Datatype teidata.pointer
Contained by
header: textClass
May contain Empty element
Note

The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

Example
<catRef scheme="#myTopics"  target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics">  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   att.global.attributes,
   att.pointing.attributes,
   attribute scheme { text }?,
   empty
}

Appendix A.1.1.18 <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Module header
Attributes
Contained by
May contain
core: desc gloss
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   att.global.attributes,
   att.datcat.attributes,
   ( ( catDesc+ | ( model.descLike | equiv | gloss )* ), category* )
}

Appendix A.1.1.19 <cell>

<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
Module figures
Attributes
Contained by
figures: row
May contain
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element cell
{
   att.global.attributes,
   att.tableDecoration.attributes,
   macro.specialPara
}

Appendix A.1.1.20 <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Module header
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
target (target) points to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute target { list { + } }?,
   macro.specialPara
}

Appendix A.1.1.21 <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Module core
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

Example An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate minOccurs="2"
  maxOccurs="unbounded">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   att.global.attributes,
   ( model.choicePart | choice ),
   ( model.choicePart | choice ),
   ( model.choicePart | choice )*
}

Appendix A.1.1.22 <cit>

<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]
Module core
Attributes
Member of
Contained by
May contain
figures: figure
linking: link linkGrp
msdescription: msDesc
Example
<cit>  <quote>and the breath of the whale is frequently attended with such an insupportable smell,    as to bring on disorder of the brain.</quote>  <bibl>Ulloa's South America</bibl> </cit>
Example
<entry>  <form>   <orth>horrifier</orth>  </form>  <cit type="translationxml:lang="en">   <quote>to horrify</quote>  </cit>  <cit type="example">   <quote>elle était horrifiée par la dépense</quote>   <cit type="translationxml:lang="en">    <quote>she was horrified at the expense.</quote>   </cit>  </cit> </entry>
Example
<cit type="example">  <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>  <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"   mimeType="audio/wav"/>  <cit type="translation">   <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>  </cit>  <cit type="translation">   <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>  </cit> </cit>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.biblLike
    | model.egLike
    | model.entryPart
    | model.globalmodel.graphicLikemodel.ptrLikemodel.attributablepcq
   )+
}

Appendix A.1.1.23 <cl>

<cl> (clause) represents a grammatical clause. [17.1. Linguistic Segment Categories]
Module analysis
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to indicate the type of clause, taking values such as finite, nonfinite, declarative, interrogative, relative etc. as appropriate.

Example
<l>  <cl type="relative"   function="clause_modifier">Which frightened    both the heroes so,</cl> </l> <l>  <cl>They quite forgot their quarrel.</cl> </l>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element cl
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.notated.attributes,
   macro.phraseSeq
}

Appendix A.1.1.24 <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Module header
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { att.global.attributes, taxonomy+ }

Appendix A.1.1.25 <code>

<code> contains literal code from some formal language such as a programming language. [22.1.1. Phrase Level Terms]
Module tagdocs
Attributes
lang (formal language) a name identifying the formal language in which the code is expressed
Status Optional
Datatype teidata.word
Member of
Contained by
May contain Character data only
Example
<code lang="JAVA"> Size fCheckbox1Size = new Size(); fCheckbox1Size.Height = 500; fCheckbox1Size.Width = 500; xCheckbox1.setSize(fCheckbox1Size); </code>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element code { att.global.attributes, attribute lang { text }?, text }

Appendix A.1.1.26 <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Module core
Attributes
Member of
Contained by
May contain
Example If all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
Example It is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}

Appendix A.1.1.27 <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Module core
Attributes
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">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.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   att.calendarSystem.attributes,
   att.editLike.attributes,
   att.dimensions.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}

Appendix A.1.1.28 <death>

<death> (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Note

This attribute is not intended to express the cause of death.

calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element death
{
   att.datable.attributes,
   att.dimensions.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.29 <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
<dataSpec module="tei"  ident="teidata.point"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
Contained by
May contain
Note

When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

Example Example of a <desc> element inside a documentation element.
<dataSpec module="tei"  ident="teidata.point">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
Example Example of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
Schematron A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   att.global.attributes,
   att.translatable.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   macro.limitedContent
}

Appendix A.1.1.30 <district>

<district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <district type="ward">Jericho</district>  <settlement>Oxford</settlement> </placeName>
Example
<placeName>  <district type="area">South Side</district>  <settlement>Chicago</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element district
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.31 <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Module textstructure
Attributes
Member of
Contained by
textstructure: back body div front
May contain
figures: figure table
linking: link linkGrp
msdescription: msDesc
textstructure: div
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report>
Schematron
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   att.global.attributes,
   att.divLike.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.written.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            (
               ( ( ( model.divLike | model.divGenLike ), model.global* )+ )
             | (
                  ( ( ( schemaSpec | model.common ), model.global* )+ ),
                  ( ( ( model.divLike | model.divGenLike ), model.global* )* )
               )
            ),
            ( ( model.divBottom, model.global* )* )
         )?
      )
   )
}

Appendix A.1.1.32 <divGen>

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
Module core
Attributes
type specifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Note

Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

Member of
Contained by
textstructure: back body div front
May contain
core: head
Note

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

Example One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on <index> elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:
<back>  <div1 type="backmat">   <head>Bibliography</head> <!-- ... -->  </div1>  <div1 type="backmat">   <head>Indices</head>   <divGen n="Index Nominumtype="NAMES"/>   <divGen n="Index Rerumtype="THINGS"/>  </div1> </back>
Example Another use for <divGen> is to specify the location of an automatically produced table of contents:
<front> <!--<titlePage>...</titlePage>-->  <divGen type="toc"/>  <div>   <head>Preface</head>   <p> ... </p>  </div> </front>
Content model
<content>
 <classRef key="model.headLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element divGen
{
   att.global.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   model.headLike*
}

Appendix A.1.1.33 <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Module header
Attributes
Member of
Contained by
core: bibl
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { att.global.attributes, macro.phraseSeq }

Appendix A.1.1.34 <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Module header
Attributes
Contained by
header: fileDesc
May contain
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   att.global.attributes,
   ( model.pLike+ | ( edition, model.respLike* ) )
}

Appendix A.1.1.35 <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Module core
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

Example
<editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element editor
{
   att.global.attributes,
   att.naming.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.36 <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.editorialDeclPart"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl
{
   att.global.attributes,
   att.declarable.attributes,
   ( model.pLike | model.editorialDeclPart )+
}

Appendix A.1.1.37 <education>

<education> (education) contains a description of the educational experience of a person. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01"  to="1990-06-30">Attended <name>Cherwell School</name> </education>
Example
<education notBefore="1685-07"  notAfter="1690-06">Anthony Hammond smuggled her into the University of Cambridge, where she was disguised as his male cousin, Jack. She remained there for some months learning grammar, logic, rhetoric, and ethics</education>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element education
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.38 <email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Module core
Attributes
Member of
Contained by
May contain
Note

The format of a modern Internet email address is defined in RFC 2822

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email { att.global.attributes, macro.phraseSeq }

Appendix A.1.1.39 <emph>

<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Module core
Attributes
Member of
Contained by
May contain
Example
You took the car and did <emph>what</emph>?!!
Example
<q>What it all comes to is this,</q> he said. <q>  <emph>What    does Christopher Robin do in the morning nowadays?</emph> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element emph { att.global.attributes, macro.paraContent }

Appendix A.1.1.40 <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
Member of
Contained by
header: teiHeader
May contain
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element encodingDesc
{
   att.global.attributes,
   ( model.encodingDescPart | model.pLike )+
}

Appendix A.1.1.41 <event>

<event> (event) contains data relating to anything of significance that happens in time. [13.3.1. Basic Principles]
Module namesdates
Attributes
period supplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s or <event>s) within which the datable item is understood to have occurred.
Derived from att.datable
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
tm:tm_Easter
(Easter term)
tm:tm_Hilary
(Hilary term)
tm:tm_Michaelmas
(Michaelmas term)
tm:tm_Trinity
(Trinity term)
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
header: idno
linking: link linkGrp
msdescription: msDesc
namesdates: listPerson
Example
<listEvent>  <event when="1618-05-23"   xml:id="SecondDefPraguewhere="#Prague">   <eventName>1618 Defenestration of Prague</eventName>   <idno>https://www.wikidata.org/wiki/Q13365740</idno>   <listPerson type="defenstrated">    <person>     <persName>Jaroslav Bořita z Martinic</persName>     <idno type="GND">https://d-nb.info/gnd/116810998</idno>    </person>    <person>     <persName>Vilém Slavata z Chlumu a Košumberka</persName>     <idno type="GND">https://d-nb.info/gnd/1018376615</idno>    </person>    <person>     <persName>Filip Fabricius</persName>     <idno type="GND">https://d-nb.info/gnd/133946118</idno>    </person>   </listPerson>   <place xml:id="Prague">    <placeName>Prague</placeName>   </place>  </event>  <event from="1618to="1648"   xml:id="ThirtyYearsWar">   <eventName>Thirty Years’ War</eventName>   <idno>https://www.wikidata.org/wiki/Q2487</idno>   <event when="1643-03-19"    xml:id="BattleofRocroiwhere="#Rocroi">    <eventName>Battle of Rocroi</eventName>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>    <idno type="GND">https://d-nb.info/gnd/4202901-6</idno>    <place xml:id="Rocroi">     <placeName>Rocroi</placeName>     <location>      <geo decls="#WGS">49.926111 4.522222</geo>     </location>    </place>   </event>  </event> </listEvent>
Example
<person>  <event type="matwhen="1972-10-12">   <label>matriculation</label>  </event>  <event type="gradwhen="1975-06-23">   <label>graduation</label>  </event> </person>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="listPerson"/>
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element event
{
   att.global.attributes,
   att.datable.w3c.attribute.when,
   att.datable.w3c.attribute.notBefore,
   att.datable.w3c.attribute.notAfter,
   att.datable.w3c.attribute.from,
   att.datable.w3c.attribute.to,
   att.datable.iso.attribute.when-iso,
   att.datable.iso.attribute.notBefore-iso,
   att.datable.iso.attribute.notAfter-iso,
   att.datable.iso.attribute.from-iso,
   att.datable.iso.attribute.to-iso,
   att.datable.custom.attribute.when-custom,
   att.datable.custom.attribute.notBefore-custom,
   att.datable.custom.attribute.notAfter-custom,
   att.datable.custom.attribute.from-custom,
   att.datable.custom.attribute.to-custom,
   att.datable.custom.attribute.datingPoint,
   att.datable.custom.attribute.datingMethod,
   att.editLike.attributes,
   att.locatable.attributes,
   att.naming.attributes,
   att.sortable.attributes,
   att.typed.attributes,
   attribute period
   {
      list
      {
         (
            "tm:tm_Easter"
          | "tm:tm_Hilary"
          | "tm:tm_Michaelmas"
          | "tm:tm_Trinity"
         )+
      }
   }?,
   attribute calendar { list { + } }?,
   (
      idno*,
      model.headLike*,
      ( model.pLike+ | model.labelLike+ ),
      (
         listPersonmodel.noteLikemodel.biblLikelinkGrplinkidnoptr
      )*
   )
}

Appendix A.1.1.42 <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Module core
Attributes
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<choice xml:lang="la">  <abbr>Imp</abbr>  <expan>Imp<ex>erator</ex>  </expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan
{
   att.global.attributes,
   att.editLike.attributes,
   macro.phraseSeq
}

Appendix A.1.1.43 <faith>

<faith> (faith) specifies the faith, religion, or belief set of a person. [13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element faith
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.canonical.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.44 <figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
Module figures
Attributes
Contained by
figures: figure
May contain
Note

This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Example
<figure>  <graphic url="emblem1.png"/>  <head>Emblemi d'Amore</head>  <figDesc>A pair of naked winged cupids, each holding a    flaming torch, in a rural setting.</figDesc> </figure>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element figDesc { att.global.attributes, macro.limitedContent }

Appendix A.1.1.45 <figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
Module figures
Attributes
Member of
Contained by
May contain
Example
<figure>  <head>The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc>  <graphic url="http://www.example.org/fig1.png"   scale="0.5"/> </figure>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
    
Schema Declaration
element figure
{
   att.global.attributes,
   att.placement.attributes,
   att.typed.attributes,
   att.written.attributes,
   (
      model.headLikemodel.commonfigDescmodel.graphicLikemodel.globalmodel.divBottom
   )*
}

Appendix A.1.1.46 <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
Contained by
header: teiHeader
May contain
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   att.global.attributes,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt*,
         notesStmt?
      ),
      sourceDesc+
   )
}

Appendix A.1.1.47 <floruit>

<floruit> (floruit) contains information about a person's period of activity. [13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<floruit notBefore="1066notAfter="1100"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element floruit
{
   att.global.attributes,
   att.datable.attributes,
   att.dimensions.attributes,
   att.editLike.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.48 <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Module core
Attributes
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign { att.global.attributes, macro.phraseSeq }

Appendix A.1.1.49 <forename>

<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element forename
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

Appendix A.1.1.50 <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Module textstructure
Attributes
Contained by
textstructure: text
May contain
figures: figure
linking: link linkGrp
textstructure: div
Note

Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla      pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί        θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently. ...</p>  </div> </front>
Example
<front>  <div type="abstract">   <div>    <head> BACKGROUND:</head>    <p>Food insecurity can put children at greater risk of obesity because        of altered food choices and nonuniform consumption patterns.</p>   </div>   <div>    <head> OBJECTIVE:</head>    <p>We examined the association between obesity and both child-level        food insecurity and personal food insecurity in US children.</p>   </div>   <div>    <head> DESIGN:</head>    <p>Data from 9,701 participants in the National Health and Nutrition        Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.        Child-level food insecurity was assessed with the US Department of        Agriculture's Food Security Survey Module based on eight        child-specific questions. Personal food insecurity was assessed with        five additional questions. Obesity was defined, using physical        measurements, as body mass index (calculated as kg/m2) greater than        or equal to the age- and sex-specific 95th percentile of the Centers        for Disease Control and Prevention growth charts. Logistic        regressions adjusted for sex, race/ethnic group, poverty level, and        survey year were conducted to describe associations between obesity        and food insecurity.</p>   </div>   <div>    <head> RESULTS:</head>    <p>Obesity was significantly associated with personal food insecurity        for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to        2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%        CI 0.51 to 1.51). Child-level food insecurity was not associated        with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>   </div>   <div>    <head> CONCLUSIONS:</head>    <p>Personal food insecurity is associated with an increased risk of        obesity only in children aged 6 to 11 years. Personal        food-insecurity measures may give different results than aggregate        food-insecurity measures in children.</p>   </div>  </div> </front>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence>
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence>
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   att.global.attributes,
   att.declaring.attributes,
   (
      ( model.frontPart | model.pLike | model.pLike.front | model.global )*,
      (
         (
            (
               (
                  model.div1Like,
                  ( model.div1Like | model.frontPart | model.global )*
               )
             | (
                  model.divLike,
                  ( model.divLike | model.frontPart | model.global )*
               )
            ),
            ( ( model.divBottom, ( model.divBottom | model.global )* )? )
         )?
      )
   )
}

Appendix A.1.1.51 <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Module header
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
core: bibl
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.52 <genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Charles</forename>  <genName>II</genName> </persName>
Example
<persName>  <surname>Pitt</surname>  <genName>the Younger</genName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element genName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

Appendix A.1.1.53 <gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
value supplies a coded value for gender identity
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
namesdates: person
May contain
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gender
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.54 <geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
Module namesdates
Attributes
Member of
Contained by
May contain Character data only
Note

Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Example
<geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl> <!-- ... --> <location>  <desc>A tombstone plus six lines of    Anglo-Saxon text, built into the west tower (on the south side    of the archway, at 8 ft. above the ground) of the    Church of St. Mary-le-Wigford in Lincoln.</desc>  <geo decls="#WGS">53.226658 -0.541254</geo>  <geo decls="#OS">SK 97481 70947</geo> </location>
Example
<geo>41.687142 -74.870109</geo>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element geo { att.global.attributes, att.declaring.attributes, text }

Appendix A.1.1.55 <gloss>

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components]
Module core
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gloss
{
   att.global.attributes,
   att.declaring.attributes,
   att.translatable.attributes,
   att.typed.attributes,
   att.pointing.attributes,
   att.cReferencing.attributes,
   macro.phraseSeq
}

Appendix A.1.1.56 <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
Module core
Attributes
Member of
Contained by
May contain
core: desc
Note

The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded.

Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<facsimile>  <surfaceGrp n="leaf1">   <surface>    <graphic url="page1.png"/>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>   </surface>  </surfaceGrp> </facsimile>
Example
<facsimile>  <surfaceGrp n="leaf1xml:id="spi001">   <surface xml:id="spi001r">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001r.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001r.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001v.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001v.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic type="normal"      subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>     <graphic type="normal"      subtype="low-res"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic type="normal"      subtype="high-res"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="low-res"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="high-res"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element graphic
{
   att.global.attributes,
   att.media.attributes,
   att.resourced.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   model.descLike*
}

Appendix A.1.1.57 <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Module core
Attributes
Member of
Contained by
May contain
Note

The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

Example The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
Example When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
Example The <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   att.written.attributes,
   (
      text
    | lg
    | model.gLike
    | model.phrasemodel.inter
    | model.lLike
    | model.global
   )*
}

Appendix A.1.1.58 <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Module core
Attributes
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi { att.global.attributes, att.written.attributes, macro.paraContent }

Appendix A.1.1.59 <ident>

<ident> (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. Phrase Level Terms]
Module tagdocs
Attributes
Member of
Contained by
May contain Character data only
Note

In running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements <gi> and <att> are provided.

Example
<ident type="ns">http://www.tei-c.org/ns/Examples</ident>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element ident { att.global.attributes, att.typed.attributes, text }

Appendix A.1.1.60 <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module header
Attributes
type categorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
header: idno
character data
Note

<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   att.global.attributes,
   att.sortable.attributes,
   att.datable.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   ( text | model.gLike | idno )*
}

Appendix A.1.1.61 <interp>

<interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations]
Module analysis
Attributes
Member of
Contained by
May contain
core: desc
character data
Note

Generally, each <interp> element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an <interp> with any textual element through its ana attribute.

Alternatively (or, in addition) an <interp> may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the <interp> applies.

Example
<interp type="structuralunit"  xml:id="ana_am">aftermath</interp>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element interp
{
   att.global.attributes,
   att.interpLike.attributes,
   ( text | model.gLike | model.descLike | model.certLike )*
}

Appendix A.1.1.62 <interpGrp>

<interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations]
Module analysis
Attributes
Member of
Contained by
May contain
analysis: interp
core: desc
Note

Any number of <interp> elements.

Example
<interpGrp resp="#TMA"  type="structuralunit">  <desc>basic structural organization</desc>  <interp xml:id="I1">introduction</interp>  <interp xml:id="I2">conflict</interp>  <interp xml:id="I3">climax</interp>  <interp xml:id="I4">revenge</interp>  <interp xml:id="I5">reconciliation</interp>  <interp xml:id="I6">aftermath</interp> </interpGrp> <bibl xml:id="TMA"> <!-- bibliographic citation for source of this interpretive framework --> </bibl>
Content model
<content>
 <sequence>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="interp" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element interpGrp
{
   att.global.attributes,
   att.interpLike.attributes,
   ( model.descLike*, interp+ )
}

Appendix A.1.1.63 <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Module core
Attributes
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   att.global.attributes,
   att.sortable.attributes,
   macro.specialPara
}

Appendix A.1.1.64 <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Module core
Attributes
Member of
Contained by
May contain
Example Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
Example Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
Example Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
Example Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   att.written.attributes,
   macro.phraseSeq
}

Appendix A.1.1.65 <langKnown>

<langKnown> (language known) summarizes the state of a person's linguistic competence, i.e., knowledge of a single language. [15.2.2. The Participant Description]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
tag supplies a valid language tag for the language concerned.
Status Required
Datatype teidata.language
Note

The value for this attribute should be a language ‘tag’ as defined in BCP 47.

level a code indicating the person's level of knowledge for this language
Status Optional
Datatype teidata.word
Contained by
May contain
Example
<langKnown tag="en-GBlevel="H">British English</langKnown> <langKnown tag="frlevel="M">French</langKnown>
Example
<person sex="mrole="speaker collaborator"> <!-- other details omitted -->  <langKnowledge>   <langKnown tag="mix">Mixtepec-Mixtec</langKnown>   <langKnown tag="en">English</langKnown>   <langKnown tag="es">Spanish</langKnown>  </langKnowledge> </person>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element langKnown
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   attribute calendar { list { + } }?,
   attribute tag { text },
   attribute level { text }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.66 <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
Module header
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   att.global.attributes,
   att.declarable.attributes,
   ( model.pLike+ | language+ )
}

Appendix A.1.1.67 <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Module header
Attributes
ident (identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
Status Required
Datatype teidata.language
usage specifies the approximate percentage of the text which uses this language.
Status Optional
Datatype nonNegativeInteger
Contained by
header: langUsage
May contain
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   att.global.attributes,
   attribute ident { text },
   attribute usage { text }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.68 <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
May contain
Note

A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence
{
   att.global.attributes,
   att.pointing.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.specialPara
}

Appendix A.1.1.70 <linkGrp>

<linkGrp> (link group) defines a collection of associations or hypertextual links. [16.1. Links]
Module linking
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
possiblySamePerson
(Asserts that two or more person records may in fact be for the same person.) It is frequently the case that two or more person records are most likely referring to the same person, but there is no way to confirm this. For such cases, we create a <linkGrp> with type=possiblySamePerson and add <ptr> elements for each of the person records.
notSamePerson
(Asserts that two or more person records are definitely for different people.) Sometimes it appears that two or more people have the same name and similar details, and readers might assume they are the same person, but further research has determined that they are definitely not the same. For such cases, we create a <linkGrp> with type=notSamePerson and add <ptr> elements for each of the person records.
businesses
(Which types of business are involved in a case.)
Member of
Contained by
May contain
core: desc ptr
linking: link
Note

May contain one or more <link> or <ptr> elements.

A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

Example
<linkGrp type="translation">  <link target="#CCS1 #SW1"/>  <link target="#CCS2 #SW2"/>  <link target="#CCS #SW"/> </linkGrp> <div type="volumexml:id="CCS"  xml:lang="fr">  <p>   <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>   <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>  </p> <!-- ... --> </div> <div type="volumexml:id="SWxml:lang="en">  <p>   <s xml:id="SW1">For a long time I used to go to bed early.</s>   <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>  </p> <!-- ... --> </div>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element linkGrp
{
   att.global.attributes,
   att.pointing.group.attribute.domains,
   att.pointing.group.attribute.targFunc,
   att.pointing.attribute.targetLang,
   att.pointing.attribute.target,
   att.pointing.attribute.evaluate,
   att.typed.attribute.subtype,
   attribute type { "possiblySamePerson" | "notSamePerson" | "businesses" }?,
   ( model.descLike*, ( link | ptr )+ )
}

Appendix A.1.1.71 <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Module core
Attributes
type (type) describes the nature of the items in the list.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Note

Previous versions of these Guidelines recommended the use of type on <list> to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

The formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

Member of
Contained by
May contain
figures: figure
linking: link linkGrp
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
Example The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   att.global.attributes,
   att.sortable.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   (
      ( model.divTop | model.global | desc* )*,
      (
         ( ( item, model.global* )+ )
       | (
            headLabel?,
            headItem?,
            ( ( label, model.global*, item, model.global* )+ )
         )
      ),
      ( ( model.divBottom, model.global* )* )
   )
}

Appendix A.1.1.72 <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core
Attributes
Member of
Contained by
May contain
msdescription: msDesc
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   att.global.attributes,
   att.sortable.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   (
      model.headLike*,
      desc*,
      ( model.milestoneLike | relation | listRelation )*,
      (
         (
            model.biblLike+,
            ( model.milestoneLike | relation | listRelation )*
         )+
      )
   )
}

Appendix A.1.1.73 <listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [13.3.1. Basic Principles]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <head>Battles of the American Civil War: Kentucky</head>  <event xml:id="event01when="1861-09-19">   <label>Barbourville</label>   <desc>The Battle of Barbourville was one of the early engagements of      the American Civil War. It occurred September 19, 1861, in Knox      County, Kentucky during the campaign known as the Kentucky Confederate      Offensive. The battle is considered the first Confederate victory in      the commonwealth, and threw a scare into Federal commanders, who      rushed troops to central Kentucky in an effort to repel the invasion,      which was finally thwarted at the <ref target="#event02">Battle of        Camp Wildcat</ref> in October.</desc>  </event>  <event xml:id="event02when="1861-10-21">   <label>Camp Wild Cat</label>   <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp      Wild Cat) was one of the early engagements of the American Civil      War. It occurred October 21, 1861, in northern Laurel County, Kentucky      during the campaign known as the Kentucky Confederate Offensive. The      battle is considered one of the very first Union victories, and marked      the first engagement of troops in the commonwealth of Kentucky.</desc>  </event>  <event xml:id="event03from="1864-06-11"   to="1864-06-12">   <label>Cynthiana</label>   <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement      during the American Civil War that was fought on June 11 and 12, 1864,      in Harrison County, Kentucky, near the town of Cynthiana. A part of      Confederate Brigadier General John Hunt Morgan's 1864 Raid into      Kentucky, the battle resulted in a victory by Union forces over the      raiders and saved the town from capture.</desc>  </event> </listEvent>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.eventLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listEvent
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      desc*,
      ( relation | listRelation )*,
      ( ( model.eventLike+, ( relation | listRelation )* )+ )
   )
}

Appendix A.1.1.74 <listOrg>

<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [13.2.2. Organizational Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of organizations of a particular type if convenient.

Example
<listOrg>  <head>Libyans</head>  <org>   <orgName>Adyrmachidae</orgName>   <desc>These people have, in most points, the same customs as the Egyptians, but      use the costume of the Libyans. Their women wear on each leg a ring made of      bronze [...]</desc>  </org>  <org>   <orgName>Nasamonians</orgName>   <desc>In summer they leave their flocks and herds upon the sea-shore, and go up      the country to a place called Augila, where they gather the dates from the      palms [...]</desc>  </org>  <org>   <orgName>Garamantians</orgName>   <desc>[...] avoid all society or intercourse with their fellow-men, have no      weapon of war, and do not know how to defend themselves. [...]</desc> <!-- ... -->  </org> </listOrg>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="org" minOccurs="1"
     maxOccurs="1"/>
    <elementRef key="listOrg" minOccurs="1"
     maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listOrg
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      desc*,
      ( relation | listRelation )*,
      ( ( ( org | listOrg )+, ( relation | listRelation )* )+ )
   )
}

Appendix A.1.1.75 <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements]
Module namesdates
Attributes
Member of
Contained by
May contain
core: desc head
namesdates: listRelation org person
Note

The type attribute may be used to distinguish lists of people of a particular type if convenient.

Example
<listPerson type="respondents">  <personGrp xml:id="PXXX"/>  <person xml:id="P1234sex="2age="mid"/>  <person xml:id="P4332sex="1age="mid"/>  <listRelation>   <relation type="personalname="spouse"    mutual="#P1234 #P4332"/>  </listRelation> </listPerson>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.personLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="listRelation"
   minOccurs="0" maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element listPerson
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   ( model.headLike*, desc*, model.personLike+, listRelation? )
}

Appendix A.1.1.76 <listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<listPlace type="offshoreIslands">  <place>   <placeName>La roche qui pleure</placeName>  </place>  <place>   <placeName>Ile aux cerfs</placeName>  </place> </listPlace>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.placeLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPlace"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPlace
{
   att.global.attributes,
   att.typed.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      desc*,
      ( relation | listRelation )*,
      ( ( ( model.placeLike | listPlace )+, ( relation | listRelation )* )+ )
   )
}

Appendix A.1.1.77 <listPrefixDef>

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Module header
Attributes
Member of
Contained by
May contain
core: desc
Example In this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psn"   matchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="bibl"   matchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="prefixDef"/>
   <elementRef key="listPrefixDef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listPrefixDef
{
   att.global.attributes,
   ( desc*, ( prefixDef | listPrefixDef )+ )
}

Appendix A.1.1.78 <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
Module namesdates
Attributes
Member of
Contained by
May contain
core: desc head p
Note

May contain a prose description organized as paragraphs, or a sequence of <relation> elements.

Example
<listPerson>  <person xml:id="pp1"> <!-- data about person pp1 -->  </person>  <person xml:id="pp2"> <!-- data about person pp1 -->  </person> <!-- more person (pp3, pp4) elements here -->  <listRelation type="personal">   <relation name="parent"    active="#pp1 #pp2passive="#pp3 #pp4"/>   <relation name="spouse"    mutual="#pp1 #pp2"/>  </listRelation>  <listRelation type="social">   <relation name="employeractive="#pp1"    passive="#pp3 #pp5 #pp6 #pp7"/>  </listRelation> </listPerson>
The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.
Example
<listPerson>  <person xml:id="en_pp1"> <!-- data about person en_pp1 -->  </person>  <person xml:id="en_pp2"> <!-- data about person en_pp2 -->  </person> <!-- more person (en_pp3, en_pp4) elements here --> </listPerson> <listPlace>  <place xml:id="en_pl1"> <!-- data about place en_pl1 -->  </place> <!-- more place (en_pl2, en_pl3) elements here --> </listPlace> <listRelation>  <relation name="residence"   active="#en_pp1 #en_pp2passive="#en_pl1"/> </listRelation>
The persons with identifiers en_pp1 and en_pp2 live in en_pl1.
Example
<listRelation>  <p>All speakers are members of the Ceruli family, born in Naples.</p> </listRelation>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listRelation
{
   att.global.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   ( model.headLike*, desc*, ( model.pLike | ( relation | listRelation )+ ) )
}

Appendix A.1.1.79 <location>

<location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [13.3.4. Places]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<place>  <placeName>Abbey Dore</placeName>  <location>   <geo>51.969604 -2.893146</geo>  </location> </place>
Example
<place xml:id="BGbuildingtype="building">  <placeName>Brasserie Georges</placeName>  <location>   <country key="FR"/>   <settlement type="city">Lyon</settlement>   <district type="arrondissement">IIème</district>   <district type="quartier">Perrache</district>   <placeName type="street">    <num>30</num>, Cours de Verdun</placeName>  </location> </place>
Example
<place type="imaginary">  <placeName>Atlantis</placeName>  <location>   <offset>beyond</offset>   <placeName>The Pillars of <persName>Hercules</persName>   </placeName>  </location> </place>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="precision"/>
  <classRef key="model.labelLike"/>
  <classRef key="model.placeNamePart"/>
  <classRef key="model.offsetLike"/>
  <classRef key="model.measureLike"/>
  <classRef key="model.addressLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.biblLike"/>
 </alternate>
</content>
    
Schema Declaration
element location
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   attribute calendar { list { + } }?,
   (
      precision
    | model.labelLikemodel.placeNamePart
    | model.offsetLike
    | model.measureLikemodel.addressLikemodel.noteLikemodel.biblLike
   )*
}

Appendix A.1.1.80 <m>

<m> (morpheme) represents a grammatical morpheme. [17.1. Linguistic Segment Categories]
Module analysis
Attributes
baseForm supplies the morpheme's base form.
Status Optional
Datatype teidata.word
Member of
Contained by
May contain
core: hi note q
figures: figure
linking: link linkGrp
character data
Note

The type attribute may be used to indicate the type of morpheme, taking values such as clitic, prefix, stem, etc. as appropriate.

Example
<w type="adjective">  <w type="noun">   <m type="prefixbaseForm="con">com</m>   <m type="root">fort</m>  </w>  <m type="suffix">able</m> </w>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.hiLike"/>
  <elementRef key="seg"/>
  <elementRef key="m"/>
  <elementRef key="c"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element m
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.notated.attributes,
   attribute baseForm { text }?,
   ( text | model.gLike | model.hiLike | seg | m | c | model.global )*
}

Appendix A.1.1.81 <mentioned>

<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
Module core
Attributes
Member of
Contained by
May contain
Example
There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mentioned { att.global.attributes, macro.phraseSeq }

Appendix A.1.1.82 <msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Module msdescription
Attributes
Contained by
msdescription: msDesc
May contain
core: p textLang
Note

Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema.

Example
<msContents class="#sermons">  <p>A collection of Lollard sermons</p> </msContents>
Example
<msContents>  <msItem n="1">   <locus>fols. 5r-7v</locus>   <title>An ABC</title>   <bibl>    <title>IMEV</title>    <biblScope>239</biblScope>   </bibl>  </msItem>  <msItem n="2">   <locus>fols. 7v-8v</locus>   <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>   <bibl>    <title>IMEV</title>    <biblScope>3747</biblScope>   </bibl>  </msItem>  <msItem n="3">   <locus>fol. 8v</locus>   <title>Truth</title>   <bibl>    <title>IMEV</title>    <biblScope>809</biblScope>   </bibl>  </msItem>  <msItem n="4">   <locus>fols. 8v-10v</locus>   <title>Birds Praise of Love</title>   <bibl>    <title>IMEV</title>    <biblScope>1506</biblScope>   </bibl>  </msItem>  <msItem n="5">   <locus>fols. 10v-11v</locus>   <title xml:lang="la">De amico ad amicam</title>   <title xml:lang="la">Responcio</title>   <bibl>    <title>IMEV</title>    <biblScope>16 &amp; 19</biblScope>   </bibl>  </msItem>  <msItem n="6">   <locus>fols. 14r-126v</locus>   <title>Troilus and Criseyde</title>   <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>  </msItem> </msContents>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="textLang" minOccurs="0"/>
   <elementRef key="titlePage"
    minOccurs="0"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msItem"/>
    <elementRef key="msItemStruct"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element msContents
{
   att.global.attributes,
   att.msExcerpt.attributes,
   att.msClass.attributes,
   (
      model.pLike+
    | ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* )
   )
}

Appendix A.1.1.83 <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview]
Module msdescription
Attributes
Member of
Contained by
May contain
core: head p
msdescription: msContents msIdentifier
Note

Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable.

Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>
Schematron
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
    <elementRef key="msFrag"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msDesc
{
   att.global.attributes,
   att.sortable.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.docStatus.attributes,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents | physDesc | history | additional | msPart | msFrag )*
      )
   )
}

Appendix A.1.1.84 <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
Module msdescription
Attributes
Member of
Contained by
core: bibl
msdescription: msDesc
May contain
header: idno
msdescription: msName repository
Example
<msIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </msIdentifier>
Schematron
<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report>
Content model
<content>
 <sequence>
  <sequence>
   <classRef key="model.placeNamePart"
    expand="sequenceOptional"/>
   <elementRef key="institution"
    minOccurs="0"/>
   <elementRef key="repository"
    minOccurs="0"/>
   <elementRef key="collection"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="idno" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msIdentifier
{
   att.global.attributes,
   (
      (
         placeName?,
         region?,
         settlement?,
         district?,
         institution?,
         repository?,
         collection*,
         idno*
      ),
      ( msName | objectName | altIdentifier )*
   )
}

Appendix A.1.1.85 <msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
Module msdescription
Attributes
Contained by
msdescription: msIdentifier
May contain
core: name rs
character data
Example
<msName>The Vercelli Book</msName>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="rs"/>
  <elementRef key="name"/>
 </alternate>
</content>
    
Schema Declaration
element msName
{
   att.global.attributes,
   att.typed.attributes,
   ( text | model.gLike | rs | name )*
}

Appendix A.1.1.86 <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Module core
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   att.global.attributes,
   att.personal.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.87 <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
dev
(A note only for developers/editors in the project.)
public
(A public note that will be rendered on the website.)
relation
(A public note relating to familial relations, usually used to identify someone by their relationship[s] to other people.)
attestedRelations
(DO NOT USE. This value is only used by the build process, when enumerating all relationships for a person which are attested in the primary sources.)
inferredRelations
(DO NOT USE. This value is only used by the build process, when enumerating all relationships for a person which have been inferred in some way.)
Member of
Contained by
May contain
Example In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="gloss"  resp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
Example The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element note
{
   att.global.attributes,
   att.placement.attributes,
   att.pointing.attributes,
   att.typed.attribute.subtype,
   att.written.attributes,
   att.anchoring.attributes,
   attribute type
   {
      "dev" | "public" | "relation" | "attestedRelations" | "inferredRelations"
   }?,
   macro.specialPara
}

Appendix A.1.1.88 <occupation>

<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
scheme indicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
Status Optional
Datatype teidata.pointer
code identifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
Status Optional
Datatype teidata.pointer
Member of
Contained by
namesdates: person
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomy"  code="#acc">accountant</occupation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element occupation
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute scheme { text }?,
   attribute code { text }?,
   macro.specialPara
}

Appendix A.1.1.89 <org>

<org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [13.3.3. Organizational Data]
Module namesdates
Attributes
role specifies a primary role or classification for the organization.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, familyGroup, or politicalParty, each of which should be associated with a definition. Such local definitions will typically be provided by a <desc> for each <valItem> element in the schema specification of the project's customization.

Member of
Contained by
namesdates: listOrg listPerson org
May contain
Example
<org xml:id="JAMs">  <orgName>Justified Ancients of Mummu</orgName>  <desc>An underground anarchist collective spearheaded by  <persName>Hagbard Celine</persName>, who fight the Illuminati    from a golden submarine, the <name>Leif Ericson</name>  </desc>  <bibl>   <author>Robert Shea</author>   <author>Robert Anton Wilson</author>   <title>The Illuminatus! Trilogy</title>  </bibl> </org>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.nameLike"/>
    <classRef key="model.placeLike"/>
    <classRef key="model.orgPart"/>
    <classRef key="model.milestoneLike"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.personLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element org
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   attribute role { list { + } }?,
   (
      model.headLike*,
      (
         model.pLike*
       | (
            model.labelLikemodel.nameLikemodel.placeLikemodel.orgPart
          | model.milestoneLike
         )*
      ),
      ( model.noteLike | model.biblLike | linkGrp | link | ptr )*,
      model.personLike*
   )
}

Appendix A.1.1.90 <orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.91 <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core
Attributes
Member of
Contained by
May contain
Example If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
Example More usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig { att.global.attributes, macro.paraContent }

Appendix A.1.1.92 <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Module core
Attributes
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report>
Schematron
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText |parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p
{
   att.global.attributes,
   att.declaring.attributes,
   att.fragmentable.attributes,
   att.written.attributes,
   macro.paraContent
}

Appendix A.1.1.93 <pc>

<pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]
Module analysis
Attributes
force indicates the extent to which this punctuation mark conventionally separates words or phrases
Status Optional
Datatype teidata.enumerated
Legal values are:
strong
the punctuation mark is a word separator
weak
the punctuation mark is not a word separator
inter
the punctuation mark may or may not be a word separator
unit provides a name for the kind of unit delimited by this punctuation mark.
Status Optional
Datatype teidata.enumerated
pre indicates whether this punctuation mark precedes or follows the unit it delimits.
Status Optional
Datatype teidata.truthValue
Member of
Contained by
May contain
analysis: c
character data
Example
<phr>  <w>do</w>  <w>you</w>  <w>understand</w>  <pc type="interrogative">?</pc> </phr>
Example Example encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [[undefined AILALW]].
<s>  <w pos="PPERmsd="1.Pl.*.Nom">Wir</w>  <w pos="VVFINmsd="1.Pl.Pres.Ind">fahren</w>  <w pos="APPRmsd="--">in</w>  <w pos="ARTmsd="Def.Masc.Akk.Sg.">den</w>  <w pos="NNmsd="Masc.Akk.Sg.">Urlaub</w>  <pc pos="$.msd="--join="left">.</pc> </s>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="c"/>
  <classRef key="model.pPart.edit"/>
 </alternate>
</content>
    
Schema Declaration
element pc
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.linguistic.attributes,
   attribute force { "strong" | "weak" | "inter" }?,
   attribute unit { text }?,
   attribute pre { text }?,
   ( text | model.gLike | c | model.pPart.edit )*
}

Appendix A.1.1.94 <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.95 <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
Module namesdates
Attributes
source specifies the source from which some aspect of this element is drawn.
Derived from att.global.source
Status Optional
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
inferred
(A person whose existence is inferred based on indirect evidence.)
role specifies a primary role or classification for the person.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sex specifies the sex of the person.
Status Optional
Datatype 1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

gender specifies the gender of the person.
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

age specifies an age group for the person.
Status Optional
Datatype teidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
namesdates: listPerson org
May contain
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example
<person sex="Fage="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersexrole="god"  age="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01sex="Mrole="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
Example The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="arielgender="U">  <persName>Ariel</persName>  <note>Character in <title level="m">The Tempest</title>.</note> </person>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <elementRef key="ptr"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element person
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.editLike.attributes,
   att.sortable.attributes,
   attribute source { list { "inferred"+ } }?,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   ( model.pLike+ | ( model.personPart | model.global | ptr )* )
}

Appendix A.1.1.96 <phr>

<phr> (phrase) represents a grammatical phrase. [17.1. Linguistic Segment Categories]
Module analysis
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to indicate the type of phrase, taking values such as noun, verb, preposition, etc. as appropriate.

Example
<phr type="verb"  function="extraposted_modifier">To talk <phr type="preposition"   function="complement">of  <phr type="nounfunction="object">many things</phr>  </phr> </phr>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element phr
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.notated.attributes,
   macro.phraseSeq
}

Appendix A.1.1.97 <place>

<place> (place) contains data about a geographic location [13.3.4. Places]
Module namesdates
Attributes
Member of
Contained by
namesdates: listPlace org place
May contain
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.placeStateLike"/>
    <classRef key="model.eventLike"/>
    <elementRef key="name"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element place
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      (
         model.pLike*
       | ( model.labelLike | model.placeStateLike | model.eventLike | name )*
      ),
      ( model.noteLike | model.biblLike | idno | ptr | linkGrp | link )*,
      ( model.placeLike | listPlace )*
   )
}

Appendix A.1.1.98 <placeName>

<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
Module namesdates
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
plc:pl_bedfordshire
(Bedfordshire)
plc:pl_berkshire
(Berkshire)
plc:pl_buckinghamshire
(Buckinghamshire)
plc:pl_cambridgeshire
(Cambridgeshire)
plc:pl_cheshire
(Cheshire)
plc:pl_cornwall
(Cornwall)
plc:pl_cumberland
(Cumberland)
plc:pl_derbyshire
(Derbyshire)
plc:pl_devon
(Devon)
plc:pl_dorset
(Dorset)
plc:pl_durham
(Durham)
plc:pl_essex
(Essex)
plc:pl_gloucestershire
(Gloucestershire)
plc:pl_hampshire
(Hampshire)
plc:pl_herefordshire
(Herefordshire)
plc:pl_hertfordshire
(Hertfordshire)
plc:pl_huntingdonshire
(Huntingdonshire)
plc:pl_kent
(Kent)
plc:pl_lancashire
(Lancashire)
plc:pl_leicestershire
(Leicestershire)
plc:pl_lincolnshire
(Lincolnshire)
plc:pl_london
(London)
plc:pl_middlesex
(Middlesex)
plc:pl_norfolk
(Norfolk)
plc:pl_northamptonshire
(Northamptonshire)
plc:pl_northumberland
(Northumberland)
plc:pl_nottinghamshire
(Nottinghamshire)
plc:pl_oxfordshire
(Oxfordshire)
plc:pl_rutland
(Rutland)
plc:pl_shropshire
(Shropshire)
plc:pl_somerset
(Somerset)
plc:pl_staffordshire
(Staffordshire)
plc:pl_stamford
(Stamford)
plc:pl_suffolk
(Suffolk)
plc:pl_surrey
(Surrey)
plc:pl_sussex
(Sussex)
plc:pl_warwickshire
(Warwickshire)
plc:pl_westmoreland
(Westmoreland)
plc:pl_wiltshire
(Wiltshire)
plc:pl_yorkshire
(Yorkshire)
plc:pl_bristol
(Bristol)
plc:pl_worcestershire
(Worcestershire)
plc:pl_southampton
(Southampton)
plc:pl_MISSING
([Missing])
type (What kind of event or action took place in the location)
Status Optional
Schematron
<sch:pattern> <sch:rule context="tei:placeName[@type=('abbr', 'missing')]">  <sch:assert test="ancestor::tei:place"> ERROR: The value <sch:value-of select="@type"/> can only be used in a placeName element    which is inside a place element in the placeography file, not in    an event record.  </sch:assert> </sch:rule> </sch:pattern>
Schematron
<sch:pattern> <sch:rule context="tei:placeName[@type[not(.=('abbr', 'missing'))]]">  <sch:assert test="ancestor::tei:event"> ERROR: The value <sch:value-of select="@type"/> can only be used in a placeName element    which is inside an event record, not in the placeography file.  </sch:assert> </sch:rule> </sch:pattern>
Legal values are:
witness
(Where the order is witnessed or issued)
jurisdiction
(Where the order applies)
property
(Where the Jewish business or property is located)
abbr
(Abbreviation of place name; use only in placeography place element, not in event records.)
missing
(Special value used to signify the absence of place information; use only in placeography place element, not in event records.)
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.personal.attributes,
   att.typed.attribute.subtype,
   attribute corresp
   {
      list
      {
         (
            "plc:pl_bedfordshire"
          | "plc:pl_berkshire"
          | "plc:pl_buckinghamshire"
          | "plc:pl_cambridgeshire"
          | "plc:pl_cheshire"
          | "plc:pl_cornwall"
          | "plc:pl_cumberland"
          | "plc:pl_derbyshire"
          | "plc:pl_devon"
          | "plc:pl_dorset"
          | "plc:pl_durham"
          | "plc:pl_essex"
          | "plc:pl_gloucestershire"
          | "plc:pl_hampshire"
          | "plc:pl_herefordshire"
          | "plc:pl_hertfordshire"
          | "plc:pl_huntingdonshire"
          | "plc:pl_kent"
          | "plc:pl_lancashire"
          | "plc:pl_leicestershire"
          | "plc:pl_lincolnshire"
          | "plc:pl_london"
          | "plc:pl_middlesex"
          | "plc:pl_norfolk"
          | "plc:pl_northamptonshire"
          | "plc:pl_northumberland"
          | "plc:pl_nottinghamshire"
          | "plc:pl_oxfordshire"
          | "plc:pl_rutland"
          | "plc:pl_shropshire"
          | "plc:pl_somerset"
          | "plc:pl_staffordshire"
          | "plc:pl_stamford"
          | "plc:pl_suffolk"
          | "plc:pl_surrey"
          | "plc:pl_sussex"
          | "plc:pl_warwickshire"
          | "plc:pl_westmoreland"
          | "plc:pl_wiltshire"
          | "plc:pl_yorkshire"
          | "plc:pl_bristol"
          | "plc:pl_worcestershire"
          | "plc:pl_southampton"
          | "plc:pl_MISSING"
         )+
      }
   }?,
   attribute type
   {
      "witness" | "jurisdiction" | "property" | "abbr" | "missing"
   }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.99 <population>

<population> (population) contains information about the population of a place. [13.3.4.3. States, Traits, and Events]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
msdescription: msDesc
namesdates: population
Example
<population when="2001-04resp="#UKCensus">  <population type="white">   <desc>54153898</desc>  </population>  <population type="asian">   <desc>11811423</desc>  </population>  <population type="black">   <desc>1148738</desc>  </population>  <population type="mixed">   <desc>677117</desc>  </population>  <population type="chinese">   <desc>247403</desc>  </population>  <population type="other">   <desc>230615</desc>  </population> </population>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <alternate>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <classRef key="model.labelLike"
     minOccurs="1" maxOccurs="unbounded"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </sequence>
  <elementRef key="population"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element population
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      model.headLike*,
      (
         (
            ( model.pLike+ | model.labelLike+ ),
            ( model.noteLike | model.biblLike )*
         )?
      ),
      population*
   )
}

Appendix A.1.1.100 <prefixDef>

<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Module header
Attributes
ident supplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
Status Required
Datatype teidata.prefix
Note

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

Contained by
May contain
core: p
Note

The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<prefixDef ident="ref"  matchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element prefixDef
{
   att.global.attributes,
   att.patternReplacement.attributes,
   attribute ident { text },
   model.pLike*
}

Appendix A.1.1.101 <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
Member of
Contained by
header: teiHeader
May contain
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { att.global.attributes, model.profileDescPart* }

Appendix A.1.1.102 <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}

Appendix A.1.1.103 <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Module core
Attributes
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived from att.global.analytic
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
state:deceased
(Person was deceased at the time the record was created.)
trait:relational
(Person is mentioned solely as the relation of another person; she is not present or involved in any business.)
rel:wife
(wife)
rel:father
(father)
rel:brother
(brother)
rel:attorney
(attorney)
rel:son
(son)
rel:mother
(mother)
rel:daughter
(daughter)
rel:sister
(sister)
rel:grandmother
(grandmother)
rel:grandfather
(grandfather)
rel:granddaughter
(granddaughter)
rel:grandson
(grandson)
rel:mother_in_law
(mother_in_law)
rel:father_in_law
(father_in_law)
rel:sister_in_law
(sister_in_law)
rel:brother_in_law
(brother_in_law)
rel:son_in_law
(son_in_law)
rel:daughter_in_law
(daughter_in_law)
rel:niece
(niece)
rel:nephew
(nephew)
rel:child_gender_unknown_
(child_gender_unknown_)
rel:aunt
(aunt)
rel:uncle
(uncle)
rel:cousin
(cousin)
rel:husband
(husband)
rel:parent_gender_unknown_
(parent_gender_unknown_)
rel:related_to
(related_to)
rel:spouse
(spouse)
Member of
Contained by
May contain Empty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   att.cReferencing.attributes,
   att.declaring.attributes,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.internetMedia.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   attribute ana
   {
      list
      {
         (
            "state:deceased"
          | "trait:relational"
          | "rel:wife"
          | "rel:father"
          | "rel:brother"
          | "rel:attorney"
          | "rel:son"
          | "rel:mother"
          | "rel:daughter"
          | "rel:sister"
          | "rel:grandmother"
          | "rel:grandfather"
          | "rel:granddaughter"
          | "rel:grandson"
          | "rel:mother_in_law"
          | "rel:father_in_law"
          | "rel:sister_in_law"
          | "rel:brother_in_law"
          | "rel:son_in_law"
          | "rel:daughter_in_law"
          | "rel:niece"
          | "rel:nephew"
          | "rel:child_gender_unknown_"
          | "rel:aunt"
          | "rel:uncle"
          | "rel:cousin"
          | "rel:husband"
          | "rel:parent_gender_unknown_"
          | "rel:related_to"
          | "rel:spouse"
         )+
      }
   }?,
   empty
}

Appendix A.1.1.104 <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core
Attributes
Member of
Contained by
core: bibl
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

Appendix A.1.1.105 <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Module header
Attributes
Contained by
header: fileDesc
May contain
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
Content model
<content>
 <alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   att.global.attributes,
   (
      (
         (
            model.publicationStmtPart.agency,
            model.publicationStmtPart.detail*
         )+
      )
    | model.pLike+
   )
}

Appendix A.1.1.106 <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Module core
Attributes
Member of
Contained by
core: bibl
May contain
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element publisher
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}

Appendix A.1.1.107 <q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Module core
Attributes
type (type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
Status Optional
Datatype teidata.enumerated
Suggested values include:
spoken
(spoken) representation of speech
thought
(thought) representation of thought, e.g. internal monologue
written
(written) quotation from a written source
soCalled
(so called) authorial distance
foreign
(foreign) foreign words
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(mentioned) refering to itself, not its normal referent
Member of
Contained by
May contain
Note

May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.

Example
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element q
{
   att.global.attributes,
   att.ascribed.directed.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   macro.specialPara
}

Appendix A.1.1.108 <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Module core
Attributes
Member of
Contained by
May contain
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   att.notated.attributes,
   macro.specialPara
}

Appendix A.1.1.109 <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Module core
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   att.cReferencing.attributes,
   att.declaring.attributes,
   att.global.attributes,
   att.internetMedia.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   macro.paraContent
}

Appendix A.1.1.110 <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core
Attributes
Member of
Contained by
May contain
Example If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
Example It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}

Appendix A.1.1.111 <region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element region
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.112 <relatedItem>

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Module core
Attributes
target points to the related bibliographic element by means of an absolute or relative URI reference
Status Optional
Datatype teidata.pointer
Member of
Contained by
core: bibl
May contain
msdescription: msDesc
Note

If the target attribute is used to reference the related bibliographic item, the element must be empty.

Example
<biblStruct>  <monogr>   <author>Shirley, James</author>   <title type="main">The gentlemen of Venice</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Readex Microprint</publisher>    <date>1953</date>   </imprint>   <extent>1 microprint card, 23 x 15 cm.</extent>  </monogr>  <series>   <title>Three centuries of drama: English, 1642–1700</title>  </series>  <relatedItem type="otherForm">   <biblStruct>    <monogr>     <author>Shirley, James</author>     <title type="main">The gentlemen of Venice</title>     <title type="sub">a tragi-comedie presented at the private house in Salisbury          Court by Her Majesties servants</title>     <imprint>      <pubPlace>London</pubPlace>      <publisher>H. Moseley</publisher>      <date>1655</date>     </imprint>     <extent>78 p.</extent>    </monogr>   </biblStruct>  </relatedItem> </biblStruct>
Schematron
<sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the relatedItem element must be empty</sch:report> <sch:assert test="@target or child::*">A relatedItem element should have either a 'target' attribute or a child element to indicate the related bibliographic item</sch:assert>
Content model
<content>
 <alternate minOccurs="0">
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
    
Schema Declaration
element relatedItem
{
   att.global.attributes,
   att.typed.attributes,
   attribute target { text }?,
   ( model.biblLike | model.ptrLike )?
}

Appendix A.1.1.113 <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
Module namesdates
Attributes
active identifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
mutual supplies a list of participants amongst all of whom the relationship holds equally.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
name supplies a name for the kind of relationship of which this is an instance.
Status Required
Datatype teidata.enumerated
Legal values are:
wife
(wife)
sister
(sister)
grandmother
(grandmother)
grandfather
(grandfather)
granddaughter
(granddaughter)
grandson
(grandson)
mother_in_law
(mother_in_law)
father_in_law
(father_in_law)
sister_in_law
(sister_in_law)
brother_in_law
(brother_in_law)
father
(father)
son_in_law
(son_in_law)
daughter_in_law
(daughter_in_law)
niece
(niece)
nephew
(nephew)
child_gender_unknown_
(child_gender_unknown_)
aunt
(aunt)
uncle
(uncle)
cousin
(cousin)
brother
(brother)
husband
(husband)
parent_gender_unknown_
(parent_gender_unknown_)
related_to
(related_to)
spouse
(spouse)
attorney
(attorney)
son
(son)
mother
(mother)
daughter
(daughter)
passive identifies the ‘passive’ participants in a non-mutual relationship.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
core: desc
Note

Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

Example
<relation type="socialname="supervisor"  active="#p1passive="#p2 #p3 #p4"/>
This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.
Example
<relation type="personalname="friends"  mutual="#p2 #p3 #p4"/>
This indicates that p2, p3, and p4 are all friends.
Example
<relation type="CRM"  name="P89_falls_within"  active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"  passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.
Example
<relation resp="http://viaf.org/viaf/44335536/"  ref="http://purl.org/saws/ontology#isVariantOf"  active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"  passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
<sch:rule context="tei:relation[ancestor::tei:event or ancestor::tei:TEI[@xml:id='relations_unattested']]"> <sch:assert test="@active lt @passive"> ERROR: The content of the @active attribute must come before the @passive attribute alphabetically. Please invert this relationship to use the canonical format. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:assert test="@active and matches(@active, '^pros:[a-z]{4,4}\d+(_((spouse)|(child)))?$')"> ERROR: The @active attribute must contain a pointer to a prosopography entry in the form: pros:abcd12. </sch:assert> </sch:rule> <sch:rule context="tei:relation"> <sch:assert test="@passive and matches(@passive, '^pros:[a-z]{4,4}\d+$')"> ERROR: The @passive attribute must contain a pointer to a prosopography entry in the form: pros:abcd12. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:let name="strRendering"  value="concat(@name, '|', @active, '|', @passive)"/> <sch:assert test="not(preceding-sibling::tei:relation[concat(@name, '|', @active, '|', @passive) = $strRendering])"> ERROR: A relation element encoding this relationship already exists. </sch:assert> </sch:rule>
Schematron
<sch:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</sch:assert>
Schematron
<sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report>
Schematron
<sch:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</sch:report>
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Content model
<content>
 <elementRef key="desc" minOccurs="0"/>
</content>
    
Schema Declaration
element relation
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.canonical.attributes,
   att.sortable.attributes,
   att.typed.attributes,
   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
   attribute calendar { list { + } }?,
   attribute name
   {
      "wife"
    | "sister"
    | "grandmother"
    | "grandfather"
    | "granddaughter"
    | "grandson"
    | "mother_in_law"
    | "father_in_law"
    | "sister_in_law"
    | "brother_in_law"
    | "father"
    | "son_in_law"
    | "daughter_in_law"
    | "niece"
    | "nephew"
    | "child_gender_unknown_"
    | "aunt"
    | "uncle"
    | "cousin"
    | "brother"
    | "husband"
    | "parent_gender_unknown_"
    | "related_to"
    | "spouse"
    | "attorney"
    | "son"
    | "mother"
    | "daughter"
   },
   attribute passive { list { + } }?,
   desc?
}

Appendix A.1.1.114 <repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Module msdescription
Attributes
Contained by
msdescription: msIdentifier
May contain
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element repository
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq.limited
}

Appendix A.1.1.115 <residence>

<residence> (residence) describes a person's present or past places of residence. [15.2.2. The Participant Description]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
namesdates: person
May contain
Example
<residence>Childhood in East Africa and long term resident of Glasgow, Scotland.</residence>
Example
<residence notAfter="1997">Mbeni estate, Dzukumura region, Matabele land</residence> <residence notBefore="1903notAfter="1996">  <placeName>   <settlement>Glasgow</settlement>   <region>Scotland</region>  </placeName> </residence>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element residence
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.116 <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
core: respStmt
May contain
Note

The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element resp
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.117 <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Attributes
Member of
Contained by
May contain
core: name note resp
namesdates: orgName persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence>
  <alternate>
   <sequence>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   att.global.attributes,
   att.canonical.attributes,
   (
      ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
      note*
   )
}

Appendix A.1.1.118 <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
Contained by
header: teiHeader
May contain
core: list
header: change
Note

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="listChange"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   att.global.attributes,
   att.docStatus.attributes,
   ( list+ | listChange+ | change+ )
}

Appendix A.1.1.119 <roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Note

A <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder.

Example
<persName>  <forename>William</forename>  <surname>Poulteny</surname>  <roleName>Earl of Bath</roleName> </persName>
Example
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official, including the Supreme Court justices, required by statute to be “learned in the law.”</p>
Example
<p>  <persName ref="#NJF">   <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>, representing the administration, asserted in rebuttal that there was nothing to disavow (...) <persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations alike, have repeatedly said they must honor. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element roleName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

Appendix A.1.1.120 <row>

<row> (row) contains one row of a table. [14.1.1. TEI Tables]
Module figures
Attributes
Contained by
figures: table
May contain
figures: cell
Example
<row role="data">  <cell role="label">Classics</cell>  <cell>Idle listless and unimproving</cell> </row>
Content model
<content>
 <elementRef key="cell" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }

Appendix A.1.1.121 <rs>

<rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings]
Module core
Member of
Contained by
msdescription: msName
namesdates: person
May contain
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs { macro.phraseSeq }

Appendix A.1.1.122 <s>

<s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]
Module analysis
Attributes
Member of
Contained by
May contain
Note

The <s> element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the <seg> should be used instead.

The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

Example
<head>  <s>A short affair</s> </head> <s>When are you leaving?</s> <s>Tomorrow.</s>
Schematron
<sch:report test="tei:s">You may not nest one s element within another: use seg instead</sch:report>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element s
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.notated.attributes,
   macro.phraseSeq
}

Appendix A.1.1.123 <samplingDecl>

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}

Appendix A.1.1.124 <series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core
Attributes
Member of
Contained by
core: bibl
May contain
figures: figure
header: idno
linking: link linkGrp
character data
Example
<series xml:lang="de">  <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>  <respStmt>   <resp>Herausgegeben von</resp>   <name type="person">Manfred Thaller</name>   <name type="org">Max-Planck-Institut für Geschichte</name>  </respStmt>  <title level="s">Serie A: Historische Quellenkunden</title>  <biblScope>Band 11</biblScope> </series>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   att.global.attributes,
   (
      text
    | model.gLike
    | titlemodel.ptrLikeeditorrespStmtbiblScopeidnotextLangmodel.global
    | availability
   )*
}

Appendix A.1.1.125 <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.126 <sex>

<sex> (sex) specifies the sex of an organism. [13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
value supplies a coded value for sex
Status Optional
Datatype 1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
namesdates: person
May contain
Note

As with other culturally-constructed traits such as age and gender, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<sex value="F">female</sex>
Example
<sex value="I">Intersex</sex>
Example
<sex value="TG F">Female (TransWoman)</sex>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element sex
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   macro.phraseSeq
}

Appendix A.1.1.127 <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Module core
Attributes
Member of
Contained by
May contain
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
Example If all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
Example It is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic { att.global.attributes, macro.paraContent }

Appendix A.1.1.128 <soCalled>

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
Module core
Attributes
Member of
Contained by
May contain
Example
To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call <soCalled>nuts</soCalled> to Scrooge.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element soCalled { att.global.attributes, macro.phraseSeq }

Appendix A.1.1.129 <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Module header
Attributes
Contained by
header: fileDesc
May contain
figures: table
msdescription: msDesc
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   att.global.attributes,
   att.declarable.attributes,
   (
      model.pLike+
    | ( model.biblLike | model.sourceDescPart | model.listLike )+
   )
}

Appendix A.1.1.130 <span>

<span> associates an interpretative annotation directly with a span of text. [17.3. Spans and Interpretations]
Module analysis
Attributes
from gives the identifier of the node which is the starting point of the span of text being annotated; if not accompanied by a to attribute, gives the identifier of the node of the entire span of text being annotated.
Status Optional
Datatype teidata.pointer
to gives the identifier of the node which is the end-point of the span of text being annotated.
Status Optional
Datatype teidata.pointer
Member of
Contained by
May contain
Example
<p xml:id="para2">(The "aftermath" starts here)</p> <p xml:id="para3">(The "aftermath" continues here)</p> <p xml:id="para4">(The "aftermath" ends in this paragraph)</p> <!-- ... --> <span type="structurefrom="#para2"  to="#para4">aftermath</span>
Schematron
<sch:report test="@from and @target">Only one of the attributes @target and @from may be supplied on <sch:name/> </sch:report>
Schematron
<sch:report test="@to and @target">Only one of the attributes @target and @to may be supplied on <sch:name/> </sch:report>
Schematron
<sch:report test="@to and not(@from)">If @to is supplied on <sch:name/>, @from must be supplied as well</sch:report>
Schematron
<sch:report test="contains(normalize-space(@to),' ') or contains(normalize-space(@from),' ')">The attributes @to and @from on <sch:name/> may each contain only a single value</sch:report>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element span
{
   att.global.attributes,
   att.interpLike.attributes,
   att.pointing.attributes,
   attribute from { text }?,
   attribute to { text }?,
   macro.phraseSeq.limited
}

Appendix A.1.1.131 <spanGrp>

<spanGrp> (span group) collects together span tags. [17.3. Spans and Interpretations]
Module analysis
Attributes
Member of
Contained by
May contain
analysis: span
core: desc
Example
<u xml:id="UU1">Can I have ten oranges and a kilo of bananas please?</u> <u xml:id="UU2">Yes, anything else?</u> <u xml:id="UU3">No thanks.</u> <u xml:id="UU4">That'll be dollar forty.</u> <u xml:id="UU5">Two dollars</u> <u xml:id="UU6">Sixty, eighty, two dollars. <anchor xml:id="UU6e"/>Thank you.<anchor xml:id="UU6f"/> </u> <spanGrp type="transactions">  <span from="#UU1">sale request</span>  <span from="#UU2to="#UU3">sale compliance</span>  <span from="#UU4">sale</span>  <span from="#UU5to="#UU6">purchase</span>  <span from="#UU6eto="#UU6f">purchase closure</span> </spanGrp>
Content model
<content>
 <sequence>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="span" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element spanGrp
{
   att.global.attributes,
   att.interpLike.attributes,
   ( model.descLike*, span* )
}

Appendix A.1.1.132 <standOff>

<standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container]
Module linking
Attributes
Member of
Contained by
textstructure: TEI
May contain
figures: table
linking: link linkGrp
msdescription: msDesc
transcr: zone
Example This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- ... -->  </teiHeader>  <text>   <body> <!-- ... -->    <p>     <w xml:id="w51">I</w>     <w xml:id="w52">wanna</w>     <w xml:id="w53">put</w>     <w xml:id="w54">up</w>     <w xml:id="w55">new</w>     <w xml:id="w56">wallpaper</w>     <pc>.</pc>    </p> <!-- ... -->   </body>  </text>  <standOff type="morphosyntax">   <spanGrp type="wordForm">    <span target="#w51ana="#fs01"/>    <span target="#w52ana="#fs02"/>    <span target="#w52ana="#fs03"/>    <span target="#w53 #w54ana="#fs04"/>    <span target="#w55ana="#fs05"/>    <span target="#w56ana="#fs06"/>   </spanGrp>   <fs xml:id="fs01">    <f name="lemma">     <string>I</string>    </f>    <f name="pos">     <symbol value="PP"/>    </f>   </fs>   <fs xml:id="fs02">    <f name="lemma">     <string>want</string>    </f>    <f name="pos">     <symbol value="VBP"/>    </f>   </fs>   <fs xml:id="fs03">    <f name="lemma">     <string>to</string>    </f>    <f name="pos">     <symbol value="TO"/>    </f>   </fs>   <fs xml:id="fs04">    <f name="lemma">     <string>put up</string>    </f>    <f name="pos">     <symbol value="VB"/>    </f>   </fs>   <fs xml:id="fs05">    <f name="lemma">     <string>new</string>    </f>    <f name="pos">     <symbol value="JJ"/>    </f>   </fs>   <fs xml:id="fs06">    <f name="lemma">     <string>wallpaper</string>    </f>    <f name="pos">     <symbol value="NN"/>    </f>   </fs>  </standOff> </TEI>
Example This example shows an encoding of contextual information which is referred to from the main text.
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- ... -->  </teiHeader>  <standOff>   <listPlace>    <place xml:id="LATL">     <placeName>Atlanta</placeName>     <location>      <region key="US-GA">Georgia</region>      <country key="USA">United States of America</country>      <geo>33.755 -84.39</geo>     </location>     <population when="1963"      type="interpolatedCensusquantity="489359"      source="https://www.biggestuscities.com/city/atlanta-georgia"/>    </place>    <place xml:id="LBHM">     <placeName>Birmingham</placeName>     <location>      <region key="US-AL">Alabama</region>      <country key="USA">United States of America</country>      <geo>33.653333 -86.808889</geo>     </location>     <population when="1963"      type="interpolatedCensusquantity="332891"      source="https://www.biggestuscities.com/city/birmingham-alabama"/>    </place>   </listPlace>  </standOff>  <text>   <body> <!-- ... -->    <p>Moreover, I am <choice>      <sic>congnizant</sic>      <corr>cognizant</corr>     </choice> of the interrelatedness of all communities and    <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens    <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We    <lb/>are caught in an inescapable network of mutuality, tied in a single garment    <lb/>of destiny. Whatever affects one directly affects all indirectly. Never    <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>     <lb/>idea. Anyone who lives inside the United States can never be considered    <lb/>an outsider anywhere in this country.</p> <!-- ... -->   </body>  </text> </TEI>
Schematron
<sch:assert test="@type or not(ancestor::tei:standOff)">This <sch:name/> element must have a @type attribute, since it is nested inside a <sch:name/> </sch:assert>
Content model
<content>
 <classRef key="model.standOffPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element standOff
{
   att.global.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   model.standOffPart+
}

Appendix A.1.1.133 <state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
msdescription: msDesc
namesdates: state
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<state ref="#SCHOLtype="status">  <label>scholar</label> </state>
Example
<org>  <orgName notAfter="1960">The Silver Beetles</orgName>  <orgName notBefore="1960">The Beatles</orgName>  <state type="membershipfrom="1960-08"   to="1962-05">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Stuart Sutcliffe</persName>    <persName>Pete Best</persName>   </desc>  </state>  <state type="membershipnotBefore="1963">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Ringo Starr</persName>   </desc>  </state> </org>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="state" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence>
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element state
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   att.naming.attributes,
   att.dimensions.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      (
         state+
       | (
            model.headLike*,
            model.pLike+,
            ( model.noteLike | model.biblLike )*
         )
       | ( model.labelLike | model.noteLike | model.biblLike )*
      )
   )
}

Appendix A.1.1.134 <surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and, when using an embedded transcription approach, transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Module transcr
Attributes
attachment describes the method by which this surface is or was connected to the main surface
Status Optional
Datatype teidata.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flipping indicates whether the surface is attached and folded in such a way as to provide two writing surfaces
Status Optional
Datatype teidata.truthValue
Contained by
transcr: surface zone
May contain
figures: figure
linking: link linkGrp
transcr: surface zone
Note

The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> element.

Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <alternate>
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element surface
{
   att.global.attributes,
   att.coordinated.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   attribute attachment { text }?,
   attribute flipping { text }?,
   (
      ( model.global | model.labelLike | model.graphicLike )*,
      ( ( ( zone | line | path | surface | surfaceGrp ), model.global* )* )
   )
}

Appendix A.1.1.135 <surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Module namesdates
Attributes
Member of
Contained by
May contain
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element surname
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

Appendix A.1.1.136 <table>

<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
Module figures
Attributes
rows (rows) indicates the number of rows in the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of rows.

Rows should be presented from top to bottom.

cols (columns) indicates the number of columns in each row of the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of columns.

Within each row, columns should be presented left to right.

Member of
Contained by
May contain
figures: figure row
linking: link linkGrp
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Example
<table rows="4cols="4">  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>  <row role="label">   <cell role="data"/>   <cell role="data">Dossing Cribs or Lodging Houses</cell>   <cell role="data">Beds</cell>   <cell role="data">Needys or Nightly Lodgers</cell>  </row>  <row role="data">   <cell role="label">Bury St Edmund's</cell>   <cell role="data">5</cell>   <cell role="data">8</cell>   <cell role="data">128</cell>  </row>  <row role="data">   <cell role="label">Thetford</cell>   <cell role="data">3</cell>   <cell role="data">6</cell>   <cell role="data">36</cell>  </row>  <row role="data">   <cell role="label">Attleboro'</cell>   <cell role="data">3</cell>   <cell role="data">5</cell>   <cell role="data">20</cell>  </row>  <row role="data">   <cell role="label">Wymondham</cell>   <cell role="data">1</cell>   <cell role="data">11</cell>   <cell role="data">22</cell>  </row> </table>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="row"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element table
{
   att.global.attributes,
   att.typed.attributes,
   attribute rows { text }?,
   attribute cols { text }?,
   (
      ( model.headLike | model.global )*,
      (
         ( ( row, model.global* )+ )
       | ( ( model.graphicLike, model.global* )+ )
      ),
      ( ( model.divBottom, model.global* )* )
   )
}

Appendix A.1.1.137 <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Module header
Attributes
partial indicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
Status Recommended
Datatype teidata.truthValue
Note

TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Member of
Contained by
header: encodingDesc
May contain Empty element
Example
<tagsDecl partial="true">  <rendition xml:id="rend-itscheme="css"   selector="emph, hi, name, title">font-style: italic;</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467"/>   <tagUsage gi="titleoccurs="45"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>
If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.
Content model
<content>
 <sequence>
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   att.global.attributes,
   attribute partial { text }?,
   ( rendition*, namespace* )
}

Appendix A.1.1.138 <taxonomy>

<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Module header
Attributes
Contained by
May contain
msdescription: msDesc
Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Example
<taxonomy xml:id="tax.b">  <bibl>Brown Corpus</bibl>  <category xml:id="tax.b.a">   <catDesc>Press Reportage</catDesc>   <category xml:id="tax.b.a1">    <catDesc>Daily</catDesc>   </category>   <category xml:id="tax.b.a2">    <catDesc>Sunday</catDesc>   </category>   <category xml:id="tax.b.a3">    <catDesc>National</catDesc>   </category>   <category xml:id="tax.b.a4">    <catDesc>Provincial</catDesc>   </category>   <category xml:id="tax.b.a5">    <catDesc>Political</catDesc>   </category>   <category xml:id="tax.b.a6">    <catDesc>Sports</catDesc>   </category>  </category>  <category xml:id="tax.b.d">   <catDesc>Religion</catDesc>   <category xml:id="tax.b.d1">    <catDesc>Books</catDesc>   </category>   <category xml:id="tax.b.d2">    <catDesc>Periodicals and tracts</catDesc>   </category>  </category> </taxonomy>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>
Content model
<content>
 <alternate>
  <alternate>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.descLike"
      minOccurs="1" maxOccurs="1"/>
     <elementRef key="equiv" minOccurs="1"
      maxOccurs="1"/>
     <elementRef key="gloss" minOccurs="1"
      maxOccurs="1"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence>
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element taxonomy
{
   att.global.attributes,
   att.datcat.attributes,
   (
      (
         ( category | taxonomy )+
       | ( ( model.descLike | equiv | gloss )+, ( category | taxonomy )* )
      )
    | ( model.biblLike, ( category | taxonomy )* )
   )
}

Appendix A.1.1.139 <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Module header
Attributes
Contained by
textstructure: TEI
May contain
Note

One of the few elements unconditionally required in any TEI document.

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
Content model
<content>
 <sequence>
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   att.global.attributes,
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}

Appendix A.1.1.140 <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Module core
Attributes
Member of
Contained by
May contain
Note

When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term xml:id="TDPV1rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element term
{
   att.global.attributes,
   att.declaring.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   att.canonical.attributes,
   att.sortable.attributes,
   att.cReferencing.attributes,
   macro.phraseSeq
}

Appendix A.1.1.141 <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure
Attributes
Member of
Contained by
textstructure: TEI
May contain
core: note
figures: figure
linking: link linkGrp
textstructure: back body front
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
Example The body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>  <front> <!-- front matter for the whole group -->  </front>  <group>   <text> <!-- first text -->   </text>   <text> <!-- second text -->   </text>  </group> </text>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   att.written.attributes,
   (
      model.global*,
      ( ( front, model.global* )? ),
      ( body | group ),
      model.global*,
      ( ( back, model.global* )? )
   )
}

Appendix A.1.1.142 <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Module header
Attributes
Member of
Contained by
header: profileDesc
May contain
header: catRef
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   att.global.attributes,
   att.declarable.attributes,
   ( classCode | catRef | keywords )*
}

Appendix A.1.1.143 <textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
Module core
Attributes
mainLang (main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Optional
Datatype teidata.language
otherLangs (other languages) one or more codes identifying any other languages used in the bibliographic work.
Status Optional
Datatype 0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
core: bibl series
msdescription: msContents
May contain
Note

This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   att.global.attributes,
   attribute mainLang { text }?,
   attribute otherLangs { list { * } }?,
   macro.specialPara
}

Appendix A.1.1.144 <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Module core
Attributes
type classifies the title according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.

calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
level indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Datatype teidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   att.global.attributes,
   att.typed.attribute.subtype,
   att.canonical.attributes,
   att.datable.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   macro.paraContent
}

Appendix A.1.1.145 <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Module header
Attributes
Contained by
header: fileDesc
May contain
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence>
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <classRef key="model.respLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt { att.global.attributes, ( title+, model.respLike* ) }

Appendix A.1.1.146 <trait>

<trait> (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Module namesdates
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
msdescription: msDesc
namesdates: trait
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<trait type="physical">  <label>Eye colour</label>  <desc>Blue</desc> </trait>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="trait" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence>
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element trait
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      (
         trait+
       | (
            model.headLike*,
            model.pLike+,
            ( model.noteLike | model.biblLike )*
         )
       | ( model.labelLike | model.noteLike | model.biblLike )*
      )
   )
}

Appendix A.1.1.147 <unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Module core
Attributes
reason indicates why the material is hard to transcribe.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
illegible
(illegible)
inaudible
(inaudible)
faded
(faded)
background_noise
(background noise)
eccentric_ductus
(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
<div>  <head>Rx</head>  <p>500 mg <unclear reason="illegible">placebo</unclear>  </p> </div>
Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agent Where the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
Status Optional
Datatype teidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear
{
   att.global.attributes,
   att.editLike.attributes,
   att.dimensions.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
         )+
      }
   }?,
   attribute agent { text }?,
   macro.paraContent
}

Appendix A.1.1.148 <w>

<w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation]
Module analysis
Attributes
Member of
Contained by
May contain
figures: figure
linking: link linkGrp
character data
Example This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant.
<l>  <w lemma="itpos="pn"   xml:id="A19883-003-a-0100">IT</w>  <w lemma="havepos="vvz"   xml:id="A19883-003-a-0110">hath</w>  <w lemma="bepos="vvn"   xml:id="A19883-003-a-0120">been</w>  <w lemma="saypos="vvn"   xml:id="A19883-003-a-0130">said</w>  <w lemma="ofpos="acp-p"   xml:id="A19883-003-a-0140">of</w>  <w lemma="oldpos="j"   xml:id="A19883-003-a-0150">old</w>  <pc xml:id="A19883-003-a-0160">,</pc>  <w lemma="thatpos="cs"   xml:id="A19883-003-a-0170">that</w>  <w lemma="playpos="vvz"   xml:id="A19883-003-a-0180">   <choice>    <orig>Playes</orig>    <reg>Plays</reg>   </choice>  </w>  <w lemma="bepos="vvb"   xml:id="A19883-003-a-0190">are</w>  <w lemma="feastpos="n2"   xml:id="A19883-003-a-0200">Feasts</w>  <pc xml:id="A19883-003-a-0210">,</pc> </l> <l xml:id="A19883-e100220">  <w lemma="poetpos="n2"   xml:id="A19883-003-a-0220">Poets</w>  <w lemma="thepos="d"   xml:id="A19883-003-a-0230">the</w>  <w lemma="cookpos="n2"   xml:id="A19883-003-a-0240">   <choice>    <orig>Cookes</orig>    <reg>Cooks</reg>   </choice>  </w>  <pc xml:id="A19883-003-a-0250">,</pc>  <w lemma="andpos="cc"   xml:id="A19883-003-a-0260">and</w>  <w lemma="thepos="d"   xml:id="A19883-003-a-0270">the</w>  <w lemma="spectatorpos="n2"   xml:id="A19883-003-a-0280">Spectators</w>  <w lemma="guestpos="n2"   xml:id="A19883-003-a-0290">Guests</w>  <pc xml:id="A19883-003-a-0300">,</pc> </l> <l xml:id="A19883-e100230">  <w lemma="thepos="d"   xml:id="A19883-003-a-0310">The</w>  <w lemma="actorpos="n2"   xml:id="A19883-003-a-0320">Actors</w>  <w lemma="waiterpos="n2"   xml:id="A19883-003-a-0330">Waiters</w>  <pc xml:id="A19883-003-a-0340">:</pc> <!-- ... --> </l>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="seg"/>
  <elementRef key="w"/>
  <elementRef key="m"/>
  <elementRef key="c"/>
  <elementRef key="pc"/>
  <classRef key="model.global"/>
  <classRef key="model.lPart"/>
  <classRef key="model.hiLike"/>
  <classRef key="model.pPart.edit"/>
 </alternate>
</content>
    
Schema Declaration
element w
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.linguistic.attributes,
   att.notated.attributes,
   (
      text
    | model.gLike
    | seg
    | wmcpcmodel.global
    | model.lPart
    | model.hiLikemodel.pPart.edit
   )*
}

Appendix A.1.1.149 <zone>

<zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Module transcr
Attributes
rotate indicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent <surface> element as implied by the dimensions given in the <msDesc> element or by the coordinates of the <surface> itself. The orientation is expressed in arc degrees.
Status Optional
Datatype teidata.count
Default 0
Member of
Contained by
linking: standOff
transcr: surface zone
May contain
figures: figure
linking: link linkGrp
transcr: surface zone
character data
Note

The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

A graphic element contained by a zone represents the whole of the zone.

A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element.

Example
<surface ulx="14.54uly="16.14lrx="0"  lry="0">  <graphic url="stone.jpg"/>  <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/> </surface>
This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]].
Example
<facsimile>  <surface ulx="50uly="20lrx="400"   lry="280">   <zone ulx="0uly="0lrx="500lry="321">    <graphic url="graphic.png"/>   </zone>  </surface> </facsimile>
This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element zone
{
   att.global.attributes,
   att.coordinated.attributes,
   att.typed.attributes,
   att.written.attributes,
   attribute rotate { text }?,
   (
      text
    | model.gLike
    | model.graphicLikemodel.globalsurfacemodel.linePart
   )*
}

Appendix A.1.2 Model classes

Appendix A.1.2.1 model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Module tei
Used by
Members affiliation email

Appendix A.1.2.2 model.annotationLike

model.annotationLike groups elements used to represent annotations. [16.10. The standOff Container]
Module tei
Used by
Members note

Appendix A.1.2.3 model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Module tei
Used by
Members model.quoteLike[cit quote]

Appendix A.1.2.4 model.biblLike

Appendix A.1.2.5 model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei
Used by
Members model.imprintPart[biblScope pubPlace publisher] model.respLike[author editor funder respStmt] bibl edition listRelation msIdentifier relatedItem series textLang

Appendix A.1.2.6 model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.5. Simple Editorial Changes]
Module tei
Used by
Members abbr corr expan orig reg sic unclear

Appendix A.1.2.7 model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Module tei
Used by
Members model.divPart[model.lLike model.pLike[p]] model.inter[model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike] q
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

Appendix A.1.2.8 model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Used by
Members date

Appendix A.1.2.9 model.descLike

model.descLike groups elements which contain a description of their function.
Module tei
Used by
Members desc

Appendix A.1.2.10 model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Module tei
Used by
Members model.divBottomPart model.divWrapper

Appendix A.1.2.11 model.divGenLike

model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
Module tei
Used by
Members divGen

Appendix A.1.2.12 model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Module tei
Used by
Members div

Appendix A.1.2.13 model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Module tei
Used by
Members model.lLike model.pLike[p]
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

Appendix A.1.2.14 model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Module tei
Used by
Members model.divTopPart[model.headLike[head]] model.divWrapper

Appendix A.1.2.15 model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Module tei
Used by
Members model.headLike[head]

Appendix A.1.2.16 model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei
Used by
Members code emph foreign gloss ident mentioned soCalled term title

Appendix A.1.2.17 model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Module tei
Used by
Members classDecl editorialDecl listPrefixDef projectDesc samplingDecl tagsDecl

Appendix A.1.2.18 model.eventLike

model.eventLike groups elements which describe events.
Module tei
Used by
Members event listEvent

Appendix A.1.2.19 model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]
Module tei
Used by
Members model.frontPart.drama divGen listBibl

Appendix A.1.2.20 model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Module tei
Used by
Members model.global.edit model.global.meta[interp interpGrp link linkGrp span spanGrp] model.milestoneLike model.noteLike[note] figure

Appendix A.1.2.21 model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Module tei
Used by
Members interp interpGrp link linkGrp span spanGrp
Note

Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

Appendix A.1.2.22 model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Module tei
Used by
Members graphic

Appendix A.1.2.23 model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Module tei
Used by
Members head

Appendix A.1.2.24 model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei
Used by
Members hi q

Appendix A.1.2.25 model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Module tei
Used by
Members model.emphLike[code emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q]

Appendix A.1.2.26 model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Module tei
Used by
Members biblScope pubPlace publisher

Appendix A.1.2.27 model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Module tei
Used by
Members model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike

Appendix A.1.2.28 model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Module tei
Used by
Members desc label

Appendix A.1.2.30 model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Module tei
Used by
Members model.hiLike[hi q] c choice pc unclear w zone

Appendix A.1.2.31 model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Module tei
Used by
Members list listEvent listOrg listPerson listPlace listRelation table

Appendix A.1.2.32 model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Module tei
Used by
Members geo

Appendix A.1.2.33 model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Module tei
Used by
Members model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName roleName surname] model.placeStateLike[model.placeNamePart[district placeName region settlement] location population state trait] idno
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

Appendix A.1.2.34 model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei
Used by
Members name orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

Appendix A.1.2.35 model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Module tei
Used by
Members note

Appendix A.1.2.36 model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Module tei
Used by
Members model.eventLike[event listEvent] listOrg listPerson listPlace

Appendix A.1.2.38 model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
Module tei
Used by
Members head

Appendix A.1.2.40 model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Module tei
Used by
Members model.pPart.editorial[abbr choice expan] model.pPart.transcriptional[corr orig reg sic unclear]

Appendix A.1.2.41 model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Module tei
Used by
Members abbr choice expan

Appendix A.1.2.42 model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Module tei
Used by
Members corr orig reg sic unclear

Appendix A.1.2.44 model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Module namesdates
Used by
Members addName forename genName roleName surname

Appendix A.1.2.45 model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Module tei
Used by
Members affiliation age education faith floruit gender occupation persName residence sex state trait
Note

These characteristics of an individual are typically a consequence of their own action or that of others.

Appendix A.1.2.46 model.personLike

model.personLike groups elements which provide information about people and their relationships.
Module tei
Used by
Members org person

Appendix A.1.2.47 model.personPart

Appendix A.1.2.49 model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Module tei
Used by
Members place

Appendix A.1.2.50 model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Module tei
Used by
Members district placeName region settlement

Appendix A.1.2.51 model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Module tei
Used by
Members model.placeNamePart[district placeName region settlement] location population state trait

Appendix A.1.2.52 model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Module tei
Used by
Members calendarDesc langUsage textClass

Appendix A.1.2.53 model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Module tei
Used by
Members ptr ref

Appendix A.1.2.54 model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei
Used by
Members authority publisher
Note

The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

See also model.publicationStmtPart.detail.

Appendix A.1.2.55 model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei
Used by
Members model.ptrLike[ptr ref] date idno pubPlace
Note

A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

See also model.publicationStmtPart.agency.

Appendix A.1.2.56 model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Module tei
Used by
Members cit quote

Appendix A.1.2.57 model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Module tei
Used by
Members standOff text

Appendix A.1.2.58 model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Module tei
Used by
Members author editor funder respStmt

Appendix A.1.2.59 model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Module tei
Used by
Members c cl m pc phr s w
Note

The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

Appendix A.1.2.60 model.standOffPart

Appendix A.1.2.61 model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Module tei
Used by
Members encodingDesc profileDesc

Appendix A.1.3 Attribute classes

Appendix A.1.3.1 att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Module tei
Members note
Attributes
anchored (anchored) indicates whether the copy text shows the exact place of reference for the note.
Status Optional
Datatype teidata.truthValue
Default true
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd (target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234">  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.  </note>  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.  </note> </noteGrp>

Appendix A.1.3.2 att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Module tei
Members att.ascribed.directed[q] change
Attributes
who indicates the person, or group of people, to whom the element content is ascribed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <role> elements in the <castList> using the who attribute.
<castItem type="role">  <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role">  <role xml:id="Francisco">Francisco</role>  <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo">  <speaker>Bernardo</speaker>  <l n="1">Who's there?</l> </sp> <sp who="#Francisco">  <speaker>Francisco</speaker>  <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

Appendix A.1.3.3 att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Module tei
Members q
Attributes
toWhom indicates the person, or group of people, to whom a speech act or action is directed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.
<castItem type="role">  <role xml:id="emil">Emilius.</role> </castItem> <castItem type="role">  <role xml:id="lov">Lovisa</role> </castItem> <castItem type="role">  <role xml:id="serv">A servant</role> </castItem> <!-- ... --> <sp who="#emil"  toWhom="#lov">  <speaker>Emil.</speaker>  <l n="1">My love!</l> </sp> <sp who="#lov"  toWhom="#emil">  <speaker>Lov.</speaker>  <l n="2">I have no Witness of my Noble Birth</l>  <stage who="emil"   toWhom="#serv">Pointing to her Woman.</stage>  <l>But that poor helpless wretch——</l> </sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

Appendix A.1.3.4 att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Module tei
Members gloss ptr ref term
Attributes
cRef (canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
Status Optional
Datatype teidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

Appendix A.1.3.5 att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Members date
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

Appendix A.1.3.6 att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Module tei
Members att.naming[att.personal[addName forename genName name orgName persName placeName roleName surname] affiliation author birth death district editor education event occupation population pubPlace region repository residence settlement state trait] authority catDesc date faith funder publisher relation resp respStmt term title
Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project.

ref (reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

Example In this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange.

These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange.

Appendix A.1.3.7 att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Module transcr
Members surface zone
Attributes
start indicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
Status Optional
Datatype teidata.pointer
ulx gives the x coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
uly gives the y coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrx gives the x coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lry gives the y coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
points identifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
Status Optional
Datatype 3–∞ occurrences of teidata.point separated by whitespace

Appendix A.1.3.8 att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Members affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait
Attributes
  • att.datable.w3c
    • @when
    • @notBefore
    • @notAfter
    • @from
    • @to
  • att.datable.iso
    • @when-iso
    • @notBefore-iso
    • @notAfter-iso
    • @from-iso
    • @to-iso
  • att.datable.custom
    • @when-custom
    • @notBefore-custom
    • @notAfter-custom
    • @from-custom
    • @to-custom
    • @datingPoint
    • @datingMethod
period supplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s or <event>s) within which the datable item is understood to have occurred.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

Appendix A.1.3.9 att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
Module namesdates
Members att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait]
Attributes
when-custom supplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06"   when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH  </date>.</p> <p>The current world will end at the <date when="2012-12-21"   when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> </p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-custom specifies the earliest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
notAfter-custom specifies the latest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
from-custom indicates the starting point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<event xml:id="FIRE1"  datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05">  <head>The Great Fire of London</head>  <p>The Great Fire of London burned through a large part    of the city of London.</p> </event>
to-custom indicates the ending point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
datingPoint supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Status Optional
Datatype teidata.pointer
datingMethod supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Datatype teidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date when-custom="1598"  calendar="#julian"  datingMethod="#julian">1598</date>. by Iohn Stow Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> </date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

Appendix A.1.3.10 att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Module namesdates
Members att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait]
Attributes
when-iso supplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> <time when-iso="03:00">3 A.M.</time> <time when-iso="14">around two</time> <time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>  <time when-iso="12">around noon</time> </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-iso specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
notAfter-iso specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-iso indicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-iso indicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

Appendix A.1.3.11 att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Members att.datable[affiliation age author birth change date death district editor education event faith floruit funder gender idno langKnown licence location name occupation orgName persName placeName population region relation residence resp settlement sex state title trait]
Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
from indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
to indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

Appendix A.1.3.12 att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
Module tei
Members att.segLike[c cl m pc phr s w] category taxonomy
Attributes
datcat provides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcat provides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcat provides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </f> <!-- ... --> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f name="POSfVal="#commonNoun"/> <!-- ... --> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol xml:id="commonNounvalue="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNounvalue="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
Example In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true"> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...-->  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> <!--...--> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.
Example The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
Example The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... -->   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
Example The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

Appendix A.1.3.13 att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
Module tei
Members bibl editorialDecl langUsage listBibl listEvent listOrg listPerson listPlace projectDesc samplingDecl sourceDesc textClass
Attributes
default indicates whether or not this element is selected by default when its parent is selected.
Status Optional
Datatype teidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

Appendix A.1.3.14 att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text]
Module tei
Members back body div front geo gloss graphic msDesc p ptr ref standOff surface term text
Attributes
decls (declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

Appendix A.1.3.15 att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module tei
Members age birth date death floruit population state trait unclear
Attributes
unit names the unit used for the measurement
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantity specifies the length in the units specified
Status Optional
Datatype teidata.numeric
extent indicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Status Optional
Datatype teidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precision characterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scope where the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Datatype teidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

Appendix A.1.3.16 att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Module tei
Members div
Attributes
org (organization) specifies how the content of the division is organized.
Status Optional
Datatype teidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sample indicates whether this division is a sample of the original source and if so, from which part.
Status Optional
Datatype teidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

Appendix A.1.3.17 att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Module tei
Members bibl change msDesc revisionDesc
Attributes
status describes the status of a document either currently or, when associated with a dated element, at the time indicated.
Status Optional
Datatype teidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21"   status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01status="frozen"   who="#MSM"/>  <change when="2010-03-01status="draft"   who="#LB"/> </revisionDesc>

Appendix A.1.3.18 att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Module tei
Members affiliation age birth corr date death education event expan faith floruit gender langKnown location name occupation org orgName persName person place placeName population reg relation residence sex state trait unclear
Attributes
evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instant indicates whether this is an instant revision or not.
Status Optional
Datatype teidata.xTruthValue
Default false
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

Appendix A.1.3.19 att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Module tei
Members att.divLike[div] att.segLike[c cl m pc phr s w] p
Attributes
part specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Datatype teidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

Appendix A.1.3.20 att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Module tei
Members TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype ID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Datatype teidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:base provides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Status Optional
Datatype teidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:space signals an intention about how white space should be managed by applications.
Status Optional
Datatype teidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

Appendix A.1.3.21 att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
Module analysis
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

Appendix A.1.3.22 att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Module transcr
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
change points to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

Appendix A.1.3.23 att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
Module transcr
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
facs (facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

Appendix A.1.3.24 att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Module linking
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<group>  <text xml:id="t1-g1-t1"   xml:lang="mi">   <body xml:id="t1-g1-t1-body1">    <div type="chapter">     <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>     <p></p>    </div>   </body>  </text>  <text xml:id="t1-g1-t2"   xml:lang="en">   <body xml:id="t1-g1-t2-body1"    corresp="#t1-g1-t1-body1">    <div type="chapter">     <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>     <p></p>    </div>   </body>  </text> </group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
<!-- In a placeography called "places.xml" --><place xml:id="LOND1"  corresp="people.xml#LOND2 people.xml#GENI1">  <placeName>London</placeName>  <desc>The city of London...</desc> </place> <!-- In a literary personography called "people.xml" --> <person xml:id="LOND2"  corresp="places.xml#LOND1 #GENI1">  <persName type="lit">London</persName>  <note>   <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>  </note> </person> <person xml:id="GENI1"  corresp="places.xml#LOND1 #LOND2">  <persName type="lit">London’s Genius</persName>  <note>   <p>Personification of London’s genius. Appears as an      allegorical character in mayoral shows.   </p>  </note> </person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
synch (synchronous) points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAs points to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOf points to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

next points to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev (previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

exclude points to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
select selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

Appendix A.1.3.25 att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Module tei
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

style contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
Status Optional
Datatype teidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

rendition points to a description of the rendering or presentation used for this element in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rendition="#normal">New Blazing-World</hi>. </head> <!-- elsewhere... --> <rendition xml:id="sc"  scheme="css">font-variant: small-caps</rendition> <rendition xml:id="normal"  scheme="css">font-variant: normal</rendition> <rendition xml:id="ac"  scheme="css">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

Appendix A.1.3.26 att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Module tei
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp (Identifies the team member responsible for entering the information in the element or proofing it.) Wherever a team member needs to assert, claim or acknowledge responsibility for something, this attribute should be used, and this attribute can also be used to track proofing by Adrienne, which she can assert by adding her own pointer to the team-member's pointer.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
pers:arca1
(Monika Arcadi Monika Arcadi)
pers:arne1
(Stewart Arneil Stewart Arneil)
pers:ashr1
(Babak Ashrafkhani Babak Ashrafkhani)
pers:aydi1
(Deniz Aydin Deniz Aydin)
pers:broo1
(Alex Brooks Alex Brooks)
pers:burn1
(Isabelle Burnip-Gerhardt Isabelle Burnip-Gerhardt)
pers:cadi1
(Pascale Cadieux-Johnson Pascale Cadieux-Johnson)
pers:elha1
(Tracey El Hajj Tracey El Hajj)
pers:holm1
(Martin Holmes Martin Holmes)
pers:keli1
(Kerri Li Kerri Li)
pers:maha1
(Sameera Mahara Sameera Mahara)
pers:mann1
(Lauren Mannix Lauren Mannix)
pers:parh1
(Tanvir Parhar Tanvir Parhar)
pers:pett1
(Dayne B. Pettyjohn Dayne B. Pettyjohn)
pers:pote1
(James Potechnykh James Potechnykh)
pers:smit1
(Emma Smith-Carrier Emma Smith-Carrier)
pers:szpa1
(Pat Szpak Pat Szpak)
pers:will1
(Adrienne Williams Boyarin Adrienne Williams Boyarin)
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr resp="#editorcert="high">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<!-- in the <text> ... --><lg> <!-- ... -->  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

Appendix A.1.3.27 att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Module tei
Members att.global[TEI abbr addName affiliation age author authority back bibl biblScope birth body c calendar calendarDesc catDesc catRef category cell change choice cit cl classDecl code corr date death desc district div divGen edition editionStmt editor editorialDecl education email emph encodingDesc event expan faith figDesc figure fileDesc floruit foreign forename front funder genName gender geo gloss graphic head hi ident idno interp interpGrp item label langKnown langUsage language licence link linkGrp list listBibl listEvent listOrg listPerson listPlace listPrefixDef listRelation location m mentioned msContents msDesc msIdentifier msName name note occupation org orgName orig p pc persName person phr place placeName population prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref reg region relatedItem relation repository residence resp respStmt revisionDesc roleName row s samplingDecl series settlement sex sic soCalled sourceDesc span spanGrp standOff state surface surname table tagsDecl taxonomy teiHeader term text textClass textLang title titleStmt trait unclear w zone]
Attributes
source specifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

Appendix A.1.3.28 att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Module tei
Members att.media[graphic] ptr ref
Attributes
mimeType (MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Example In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

Appendix A.1.3.29 att.interpLike

att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses]
Module tei
Members interp interpGrp span spanGrp
Attributes
type indicates what kind of phenomenon is being noted in the passage.
Status Recommended
Datatype teidata.enumerated
Sample values include:
image
identifies an image in the passage.
character
identifies a character associated with the passage.
theme
identifies a theme in the passage.
allusion
identifies an allusion to another text.
subtype (subtype) provides a sub-categorization of the phenomenon is being noted in the passage, if needed
Status Optional
Datatype teidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

inst (instances) points to instances of the analysis or interpretation represented by the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The current element should be an analytic one. The element pointed at should be a textual one.

Appendix A.1.3.30 att.lexicographic.normalized

att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.
Module analysis
Members att.linguistic[pc w]
Attributes
norm (normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form
Status Optional
Datatype teidata.text
Normalization of part-of-speech information within a dictionary entry.
<gramGrp>  <pos norm="noun">n</pos> </gramGrp>
Normalization of a source form in a tokenized historical corpus.
<s>  <w>for</w>  <w norm="virtue's">vertues</w>  <w>sake</w> </s>
<s>  <w norm="persuasion">perswasion</w>  <w>of</w>  <w norm="Unity">Vnitie</w> </s>
Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.
<s>  <w norm="freiwillig">freywillig</w>  <pc norm=","   join="left">/</pc>  <w norm="unbedrängt">vnbedraͤngt</w>  <w norm="und">vnd</w>  <w norm="unverhindert">vnuerhindert</w> </s>
<w norm="Teil">Theyll</w>
<w norm="Freude">Frewde</w>
orig (original) gives the original string or is the empty string when the element does not appear in the source text.
Status Optional
Datatype teidata.text
Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:
<w orig="ntsa sia'i">ntsasia'i</w>
Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:
<w lemma="he"  pos="pns"  xml:id="b1afj-003-a-0950">he</w> <w lemma="have"  pos="vvz"  xml:id="b1afj-003-a-0960">hath</w> <w lemma="bring"  pos="vvn"  xml:id="b1afj-003-a-0970">brought</w> <w lemma="forth"  pos="av"  xml:id="b1afj-003-a-0980"  orig="sorth">forth</w>
An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:
<w lemma="commandment"  pos="n1"  norm="commandment"  xml:id="b9avr-018-a-7720"  orig="commandemēt">commandement</w>
Note

It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, <orig>, and <reg> needs to be employed.

Appendix A.1.3.31 att.linguistic

att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically <w> and <pc> in the analysis module. [17.4.2. Lightweight Linguistic Annotation]
Module analysis
Members pc w
Attributes
lemma provides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
Status Optional
Datatype teidata.text
<w lemma="wife">wives</w>
<w lemma="Arznei">Artzeneyen</w>
lemmaRef provides a pointer to a definition of the lemma for the word, for example in an online lexicon.
Status Optional
Datatype teidata.pointer
<w type="verb"  lemma="hit"  lemmaRef="http://www.example.com/lexicon/hitvb.xml">hitt<m type="suffix">ing</m> </w>
pos (part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.).
Status Optional
Datatype teidata.text
The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).
<s>  <w pos="PPER">Wir</w>  <w pos="VVFIN">fahren</w>  <w pos="APPR">in</w>  <w pos="ART">den</w>  <w pos="NN">Urlaub</w>  <w pos="$.">.</w> </s>
The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).
<p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p>         
The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.
<p>  <w pos="PPIS2">We</w>  <w pos="VBR">'re</w>  <w pos="VVG">going</w>  <w pos="II">on</w>  <w pos="NN1">vacation</w>  <w pos="II">to</w>  <w pos="NP1">Brazil</w>  <w pos="IF">for</w>  <w pos="AT1">a</w>  <w pos="NNT1">month</w>  <pc pos="!">!</pc> </p>
msd (morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features).
Status Optional
Datatype teidata.text
<ab>  <w pos="PPER"   msd="1.Pl.*.Nom">Wir</w>  <w pos="VVFIN"   msd="1.Pl.Pres.Ind">fahren</w>  <w pos="APPR"   msd="--">in</w>  <w pos="ART"   msd="Def.Masc.Akk.Sg">den</w>  <w pos="NN"   msd="Masc.Akk.Sg">Urlaub</w>  <pc pos="$."   msd="--">.</pc> </ab>
join when present, provides information on whether the token in question is adjacent to another, and if so, on which side.
Status Optional
Datatype teidata.text
Legal values are:
no
the token is not adjacent to another
left
there is no whitespace on the left side of the token
right
there is no whitespace on the right side of the token
both
there is no whitespace on either side of the token
overlap
the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream
The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.
<s>  <pc join="right">"</pc>  <w join="left">Friends</w>  <w>will</w>  <w>be</w>  <w join="right">friends</w>  <pc join="both">.</pc>  <pc join="left">"</pc> </s>
Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.
The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.
<p>  <w pos="PNP">We</w>  <w pos="VBB"   join="left">'re</w>  <w pos="VVG">going</w>  <w pos="PRP">on</w>  <w pos="NN1">vacation</w>  <pc pos="PUN"   join="left">.</pc> </p>
Note

The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.

Note

These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion.

Appendix A.1.3.32 att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 13.3.4.3. States, Traits, and Events]
Module tei
Members event
Attributes
where indicates one or more locations by pointing to a <place> element or other canonical description.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

Appendix A.1.3.33 att.media

att.media provides attributes for specifying display and related properties of external media.
Module tei
Members graphic
Attributes
width Where the media are displayed, indicates the display width
Status Optional
Datatype teidata.outputMeasurement
height Where the media are displayed, indicates the display height
Status Optional
Datatype teidata.outputMeasurement
scale Where the media are displayed, indicates a scale factor to be applied when generating the desired display size
Status Optional
Datatype teidata.numeric

Appendix A.1.3.34 att.msClass

att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements]
Module msdescription
Members msContents
Attributes
class identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

Appendix A.1.3.35 att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
Module msdescription
Members msContents quote
Attributes
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Status Optional
Datatype teidata.xTruthValue
Note

In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

Appendix A.1.3.36 att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms]
Module tei
Members att.personal[addName forename genName name orgName persName placeName roleName surname] affiliation author birth death district editor education event occupation population pubPlace region repository residence settlement state trait
Attributes
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef (reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

Appendix A.1.3.37 att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Module tei
Members c cl m phr quote s w
Attributes
notation names the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

Appendix A.1.3.38 att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Module header
Members prefixDef
Attributes
matchPattern specifies a regular expression against which the values of other attributes can be matched.
Status Required
Datatype teidata.pattern
Note

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.

replacementPattern specifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
Status Required
Datatype teidata.replacement
Note

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

Appendix A.1.3.39 att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
Module tei
Members addName forename genName name orgName persName placeName roleName surname
Attributes
full indicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Datatype teidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort (sort) specifies the sort order of the name component in relation to others within the name.
Status Optional
Datatype teidata.count

Appendix A.1.3.40 att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]
Module tei
Members figure head label note
Attributes
place specifies where this item is placed.
Status Recommended
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

Appendix A.1.3.41 att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Module tei
Members att.pointing.group[linkGrp] calendar catRef gloss licence link note ptr ref span term
Attributes
targetLang specifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

target specifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate (evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
Status Optional
Datatype teidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

Appendix A.1.3.42 att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei
Members att.dimensions[age birth date death floruit population state trait unclear]
Attributes
atLeast gives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMost gives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.numeric
confidence specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
Status Optional
Datatype teidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegible"   extent="one or two lettersatLeast="1atMost="2unit="chars"/> </del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern Europe since 1986, and since 1992 has provided <measure atLeast="120000000unit="USD"  commodity="currency">more than $120m</measure> in aid to Ukrainians.

Appendix A.1.3.43 att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Module tei
Members graphic
Attributes
url (uniform resource locator) specifies the URL from which the media concerned may be obtained.
Status Required
Datatype teidata.pointer

Appendix A.1.3.44 att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Module tei
Members c cl m pc phr s w
Attributes
function (function) characterizes the function of the segment.
Status Optional
Datatype teidata.enumerated
Note

Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

Appendix A.1.3.45 att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
Module tei
Members bibl event idno item list listBibl listEvent listOrg listPerson listPlace listRelation msDesc org person place relation term
Attributes
sortKey supplies the sort key for this element in an index, list or group which contains it.
Status Optional
Datatype teidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

Appendix A.1.3.46 att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music]
Module figures
Members cell row
Attributes
role (role) indicates the kind of information held in this cell or in each cell of this row.
Status Optional
Datatype teidata.enumerated
Suggested values include:
label
labelling or descriptive information only.
data
data values.[Default]
Note

When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent <row> element.

rows (rows) indicates the number of rows occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.

cols (columns) indicates the number of columns occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

Appendix A.1.3.47 att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Module tagdocs
Members desc gloss
Attributes
versionDate specifies the date on which the source text was extracted and sent to the translator
Status Optional
Datatype teidata.temporal.working
Note

The versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

Appendix A.1.3.48 att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
Module tei
Members att.pointing.group[linkGrp] TEI abbr addName affiliation age bibl birth c calendar change cit cl corr date death desc district div divGen education event faith figure forename genName gender gloss graphic head ident idno label link list listBibl listEvent listOrg listPerson listPlace listRelation location m msDesc msName name note occupation org orgName pc persName phr place placeName population ptr quote ref reg region relatedItem relation residence roleName s settlement sex standOff state surface surname table term text title trait w zone
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype teidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype (subtype) provides a sub-categorization of the element, if needed
Status Optional
Datatype teidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

Appendix A.1.3.49 att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Module tei
Members div figure head hi label note p text zone
Attributes
hand points to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Status Optional
Datatype teidata.pointer

Appendix A.1.4 Macros

Appendix A.1.4.1 macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

Appendix A.1.4.2 macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
macro.paraContent = ( text | model.paraPart )*

Appendix A.1.4.3 macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
macro.phraseSeq =
   ( text | model.gLike | model.attributable | model.phrase | model.global )*

Appendix A.1.4.4 macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

Appendix A.1.4.5 macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
macro.specialPara =
   (
      text
    | model.gLike
    | model.phrasemodel.intermodel.divPartmodel.global
   )*

Appendix A.1.4.6 macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Module tei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    
Declaration
macro.xtext = ( text | model.gLike )*

Appendix A.1.5 Datatypes

Appendix A.1.5.1 teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Module tei
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

Appendix A.1.5.2 teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

Appendix A.1.5.3 teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
    
Declaration
teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

Appendix A.1.5.4 teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Module tei
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
    
Declaration
teidata.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

Appendix A.1.5.5 teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Module tei
Used by
teidata.gender teidata.sexElement:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

Appendix A.1.5.6 teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Module tei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
teidata.gender = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms).

Appendix A.1.5.7 teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Module tei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

Appendix A.1.5.8 teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Module tei
Used by
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

Appendix A.1.5.9 teidata.namespace

teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Module tei
Used by
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
teidata.namespace = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

Appendix A.1.5.10 teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

Appendix A.1.5.11 teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
    
Declaration
teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
   }
Example
<figure>  <head>The TEI Logo</head>  <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in    between and <mentioned>text encoding initiative</mentioned> underneath, all on a white    background.</figDesc>  <graphic height="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

Appendix A.1.5.12 teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Module tei
Used by
Content model
<content>
 <dataRef name="token"/>
</content>
    
Declaration
teidata.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

Appendix A.1.5.13 teidata.point

teidata.point defines the data type used to express a point in cartesian space.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
    
Declaration
teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>  <surface ulx="0uly="0lrx="400lry="280">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png"/>   </zone>  </surface> </facsimile>
Note

A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

Appendix A.1.5.14 teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Module tei
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

Appendix A.1.5.15 teidata.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
Note

This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

Appendix A.1.5.16 teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
teidata.probCert = teidata.probability | teidata.certainty

Appendix A.1.5.17 teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Module tei
Used by
Content model
<content>
 <dataRef name="double">
  <dataFacet name="minInclusive" value="0"/>
  <dataFacet name="maxInclusive" value="1"/>
 </dataRef>
</content>
    
Declaration
teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

Appendix A.1.5.18 teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Module tei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
teidata.replacement = text

Appendix A.1.5.19 teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Module tei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
teidata.sex = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Appendix A.1.5.20 teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </alternate>
</content>
    
Declaration
teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

Appendix A.1.5.21 teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

Appendix A.1.5.22 teidata.temporal.working

teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
  <dataRef name="dateTime"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
 </alternate>
</content>
    
Declaration
teidata.temporal.working =
   xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
 | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z.

Appendix A.1.5.23 teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Module tei
Used by
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

Appendix A.1.5.24 teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

Appendix A.1.5.25 teidata.unboundedCount

teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="nonNegativeInteger"/>
  <valList type="closed">
   <valItem ident="unbounded"/>
  </valList>
 </alternate>
</content>
    
Declaration
teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )

Appendix A.1.5.26 teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

Appendix A.1.5.27 teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
    
Declaration
teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

Appendix A.1.5.28 teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Module tei
Used by
teidata.enumeratedElement:
Content model
<content>
 <dataRef name="token"
  restriction="[^\p{C}\p{Z}]+"/>
</content>
    
Declaration
teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Appendix A.1.5.29 teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
    
Declaration
teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

Appendix A.1.5.30 teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Module tei
Used by
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Declaration
teidata.xmlName = xsd:NCName
Note

The rules defining an XML name form a part of the XML Specification.

Appendix A.1.5.31 teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Module tei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Appendix A.1.6 Constraints

Schematron
<sch:rule context="tei:linkGrp[@type='businesses']/tei:ptr"> <sch:let name="taxDoc"  value="if (doc-available('../taxonomies.xml')) then doc('../taxonomies.xml') else if (doc-available('../data/taxonomies.xml')) then doc('../data/taxonomies.xml') else doc('taxonomies.xml')"/> <sch:let name="businesses"  value="for $c in $taxDoc//tei:taxonomy[@xml:id='businesses']/descendant::tei:category return concat('bs:', $c/@xml:id)"/> <sch:assert test="@target = $businesses"> ERROR: the value of @target must be one of <sch:value-of select="string-join($businesses, ', ')"/>. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:event[not(@xml:id) or not(matches(@xml:id, '^ev_\d\d\d\d_\d+$'))]"> <sch:let name="year"  value="tokenize(ancestor::tei:TEI/@xml:id, '_')[2]"/> <sch:let name="maxId"  value="max((for $i in //tei:event[@xml:id][matches(xs:string(@xml:id), '^ev_\d+_\d+$')]/@xml:id return xs:integer(tokenize($i, '_')[3])))"/> <sch:let name="nextId"  value="'ev_' || $year || '_' || xs:string($maxId + 1)"/> <sch:assert test="@xml:id and matches(@xml:id, '^ev_\d\d\d\d_\d+$')"> ERROR: event elements must have a unique xml:id. The next available id is <sch:value-of select="$nextId"/> </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:TEI"> <sch:let name="fname"  value="concat(@xml:id, '.xml')"/> <sch:assert test="ends-with(document-uri(/), $fname)"> ERROR: The @xml:id of your document (<sch:value-of select="@xml:idid"/>) does not match the document file name (<sch:value-of select="document-uri(/)"/>). </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:listPerson/tei:person[@corresp]"> <sch:let name="ptr" value="@corresp"/> <sch:assert test="not(following-sibling::tei:person[@corresp = $ptr])"> ERROR: The person element pointing to <sch:value-of select="$ptr"/> is duplicated. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:*[text()][not(ancestor-or-self::tei:code or ancestor::tei:TEI[@xml:id='search'])]"> <sch:assert test="not(text()[matches(., $straightQuotes)])"> Do not use straight quotes in text. Use the q or title elements wherever possible; for apostrophes, use the smart version (’). </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:event/tei:listPerson/tei:person[@corresp]/tei:persName"> <sch:assert test="xs:string(.) = normalize-space(.)"> ERROR: Avoid leading, trailing, and multiple spaces in persNames. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:biblScope[@unit='page']"> <sch:assert test="matches(., '^[ivxlcA-Z\d\s–;,]+$')"> ERROR: page ranges should contain only digits, en dashes, and optionally semicolons or commas and spaces for disjoint ranges. </sch:assert> <sch:let name="ranges"  value="tokenize(., ';\s+')"/> <sch:assert test="every $r in $ranges satisfies matches($r, '^[ivxlcA-Z\d–]+$')"> ERROR: This page range does not seem to conform to our conventions. Use semi-colons to separate distinct pages or ranges. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:person[@xml:id]"> <sch:assert test="matches(@xml:id, '^[a-z]{4,4}\d+$')"> ERROR: The @xml:id attribute of a person element should conform to the pattern xxxx1 (four lower-case letters + a number). </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:person[not(@xml:id) and not(@corresp)]"> <sch:assert test="@xml:id"> ERROR: person elements must have a unique xml:id. Please type the first four letters of the id you need, and the next available id will be shown. </sch:assert> </sch:rule> <sch:rule context="tei:person[matches(@xml:id, '^[a-z]{4,4}$')]"> <sch:let name="letters"  value="xs:string(@xml:id)"/> <sch:let name="maxId"  value="max((0, for $i in //tei:person[@xml:id][matches(xs:string(@xml:id), '^' || $letters || '\d+$')]/@xml:id return xs:integer(substring($i, 5))))"/> <sch:let name="nextId"  value="$letters || xs:string($maxId + 1)"/> <sch:assert test="@xml:id[string-length(.) gt 4]"> NOTE: <sch:value-of select="$nextId"/> is the next available id for the letter prefix <sch:value-of select="$letters"/>. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:event/tei:listPerson/tei:listRelation/tei:relation"> <sch:assert test="starts-with(@active, 'pros:') and starts-with(@passive, 'pros:')"> ERROR: @passive and @active ids must start with the pros: prefix. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:event/tei:listPerson/tei:listRelation/tei:relation"> <sch:let name="personPtrs"  value="distinct-values(ancestor::tei:listPerson/tei:person/@corresp)"/> <sch:assert test="xs:string(@active) = $personPtrs and xs:string(@passive = $personPtrs)"> ERROR: A relation element has a pointer to <sch:value-of select="."/>, but there is no corresponding person element in the listPerson. </sch:assert> </sch:rule>
Schematron
<sch:ns uri="http://www.w3.org/1999/xhtml"  prefix="xh"/> <sch:ns uri="http://hcmc.uvic.ca/ns"  prefix="hcmc"/> <sch:pattern> <sch:let name="smartDouble" value="'[“”]'"/> <sch:let name="smartSingle" value="'[‘’]'"/> <sch:let name="straightDouble" value="'"'"/> <sch:let name="straightApos" value="''''"/> <sch:let name="straightQuotes"  value="concat('[', $straightDouble, $straightApos, ']')"/> </sch:pattern>
Date: 2022-11-24