Encoding guidelines for the Averroes project
The collaborators of the Averroes project

Prefatory note

This is a living document, it is meant to be constantly updated though the life of the Averroes project to document the encoding guidelines used in past transcriptions and to be used for new transcriptions.

Table of contents

1. General remarks on the encoding guidelines

This document describes the encoding guidelines to be used when transcribing manuscripts for the Averroes project.

These guidelines have been created on the basis of real-life instances of transcription problems. While they aim at covering all the possible cases an editor may face, it is reasonable to expect that editors will continue stumbling upon cases or phenomena that have not yet been taken into account. Should you find cases that are not handled by the current guidelines, or handled suboptimally, please report them to the project mailing list.

2. Overview of the TEI-XML file

This section gives an overview of the structure of the XML-TEI files that are produced by the Averroes project.

2.1. One manuscript, multiple files

The transcription of a physical manuscript may be split over multiple files, each containing the transcription of a range of contiguous facsimiles. Each of these ranges is called a part.

None of the page ranges in which a manuscript is split overlap. In other words, a facsimile may not be included in two different parts.

The rules on how to name the various files that contain the parts of the transcription is given in section 2.3. File name conventions.

For example, the manuscript Or.Qu.812 (355 scanned facsimiles) may be divided in the following way:

Note: TODO: multiple works can coexist on the same manuscript (see division-in-works), partial/incremental transcriptions are supported (see gaps).

2.2. Metadata about the manuscript

The metadata of the manuscript comprises a set of data about its physical appearance, its bibliographic records, and information about its digital representation.

This metadata is not produced by the editors working on the transcription of the manuscript. Instead, it is provided by the DARE project, in the form of <teiHeader> elements in TEI files, so called shared metadata header files. Section 2.6. Shared metadata header (inclusion in transcription files) describes how to integrate these shared header files inside the transcription files.

Note: TODO: link to DARE documentation once available.

2.2.1. Facsimiles

One part of the metadata describes the facsimiles that have been used to transcribe the manuscript.

Each of these manuscripts is designated by a precise and unique ID.

The IDs of the facsimiles are generated according to the following template:

Note: TODO: use template from the DARE documentation.

Inside the transcription files, these IDs are referred to when pages are transcribed, see section 4.1. Pages.

2.3. File name conventions

The name of the each transcription file reflects its source manuscript. It is composed putting together various IDs and information about the parts of the manuscript it is are meant to represent.

An examples of correct file name is
BOOK-DARE-M-DE-BER-SB-Or.Qu.812_pp0018-0094.xml

The name of each transcription file is constructed as according to the following template.

[BILDERBERG-MS-ID]_pp[FIRST_PAGE_NUM]-[LAST_PAGE_NUM].xml

BILDERBERG-MS-ID
The Bilderberg ID, copied verbatim, for example BOOK-DARE-M-DE-BER-SB-Or.Qu.812;
FIRST_PAGE_NUM
The number of the first page that is included in the part of the manuscript represented by this file. The page numbers are those used by the Bilderberg, not those of the folio numeration system used inside the manuscript. The number, following the Bilderberg convention, is composed of four digits. Leading zeros must be added to pad the number to the correct length, for example 0002.
LAST_PAGE_NUM
The number of the last page that is included in the part of the manuscript represented by this file. All the requirements for LAST_PAGE_NUM apply to this field as well.

Please note that the manuscript identifier and the page range identifier are separated by an underscore, i.e. the character _, and not by an hyphen. The reason behind this choice is that Bilderberg IDs already contain hyphen. It would be hard (or impossible) to split and identify mechanically the fields that compose the file name if an hyphen were used as the field separator.

2.4. The machine-readable XML schema

These guidelines are also available as a machine-readable XML schema. When the transcription files are associated with this schema, the XML editor will make sure (to the best of its capabilities) that the transcription follows the encoding guidelines and that no invalid construct is used.

Each transcription file must contain the following two lines (xml-model processing instructions):

<?xml-model href="averroes-guidelines.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> <?xml-model href="averroes-guidelines.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>

These two processing instructions must appear before the root element, described in section 2.5. The root element.

In case the XML file is not stored in the same directory where the averroes-guidelines.rng file is, then a relative path must be used in the href attribute of the xml-model PI, for example ../schema/averroes-guidelines.rng.

2.5. The root element

Each transcription file has a <TEI> root element.

The namespace of the <TEI> element (i.e., its xmlns attribute) must be set to //tei-c.org/ns/1.0.

The attribute xml:lang must be set to the code of the language in which the editorial content is written (and not the main content), see section 3. Handling of languages and scripts. Normally it is set to en (English).

The first child of the <TEI> element must be a special XInclude <include> element, created following the guidelines described in 2.6. Shared metadata header (inclusion in transcription files).

The second and last child of the <TEI> element must be a <text> element, compiled following the guidelines described in section 2.7. Transcribed text.

Note: TODO: do we want to describe `facsimile` as well?

2.6. Shared metadata header (inclusion in transcription files)

The metadata about the manuscript (see section 2.2. Metadata about the manuscript) is stored in a separate file, shared among all the transcription files that are part of the same manuscript. This shared metadata file is transcluded in each transcription file via the XInclude mechanism.

To inform oXygen that the metadata is in an external file, the appropriate XInclude directive must be used.

Each trascription file must contain, as the first child of the <TEI> root element, the following line (the XInclude directive):

<include xmlns="http://www.w3.org/2001/XInclude" href="[BILDERBERG-MS-ID]-header.xml" xpointer="element(/1/1)"/>

The BILDERBERG-MS-ID field must be replaced with the Bilderberg ID of the manuscript, for example BOOK-DARE-M-DE-BER-SB-Or.Qu.812.

2.7. Transcribed text

The transcription of the manuscript is put inside the <text> element.

The text to be transcribed is divided in three sections, in the following order

The front matter and the back matter sections are optional; the main content section is compulsory.

2.7.1. Front matter

Note: TODO: Cover and front matter go in `front`.

2.7.2. Main content

The transcription of the text is put inside the <body> element.

The main content is logically divided in pages, each encoded following the guidelines described in sections 4.1. Pages and 4. Text layout (eg., pages, lines).

Inside the <body> element, the elements describing the pages are ordered following the foliation numbering system. If the manuscript contains no folio or page numbers, then the order of the elements should be the natural reading order of the main content.

2.7.3. Back matter

Note: TODO: Back cover and back matter go in `back`.

3. Handling of languages and scripts

This section describes in general how information about the languages of the manuscripts is treated and recorded.

Recording which language is used where is of fundamental importance, not much for the transcription itself, but for all the tools that will be used in conjunction with the transcription, in primis the editing applications.

Many technical aspects of the programs that manipulate TEI-XML files need to know which languages they are processing. In this way they can properly set up internal mechanisms (such as algorithms for word boundaries, character counting, Unicode tables etc.) and interface elements (fonts for specific scripts, different cursors and styles for right-to-left scripts, etc.). White it is true that languages can be guessed through heuristic algorithms, such guesses are often wrong and lead to hard-to-solve issues during editing or publication.

For all these reasons, it is strongly recommended to explicitly tag all the text with appropriate language information. Fortunately XML already defines a set of mechanisms to ease this task.

3.1. The languages of the edition

The Averroes project deals mainly with texts in three languages: Arabic, Hebrew and Latin. Other languages such as Greek may also appear in notes and quotes. In addition to these main languages there are two working languages: English and German.

This multitude of languages brings in also a multitude of scripts: Arabic, Hebrew, Latin and Greek.

In various places there is the need, both editorial and technical, to identify with precision the language and the script in which a piece of text is written.

This issue can be seen as composed of two separate problems: devising a machine-readable codename for each language/script combination and having a mechanism that allows the association of those codenames to a precise piece of text.

The following section 3.2. Language tags describes the language codenames used in the Averroes project. Section 3.3. Recording language data in XML describes how to associate XML elements with those language codenames.

3.2. Language tags

As of 2016, the current standard technique to identify languages with precise codes is documented in IETF BCP 47: Tags for Identifying Languages.

In BCP 47 parlance, the language of a resource is identified via its tag. A tag is a small string composed of a sequence of subtags separated by an hyphen.

In their basic form BCP 47 language tags are very simple: they only contain the first subtag, the main language identifier, for example ar for Arabic. More sophisticated tags can describe more complex situations, for example ar-Latn-SY for Syrian Arabic transliterated in Latin.

The first subtag describes roughly the macrolanguage. The possible values are the ISO 639 alphacodes. It is written in lowercase letters. This is the only compulsory subtag. Examples:

If needed, more sophisticated language tags can be created adding optional tags.

On optional subtag describes the script of the language. It is optional; if not specified, the usual script for the main language is implied. It is written with the initial letter capitalized. Examples:

Another optional subtag describes the regional variant. It must be written in capital letters. Examples:

Multiple subtags can be combined together, for example to construct ar-Latn-SY, i.e., Syrian Arabic transliterated in Latin.

This is the list of language tags currently allowed in the Averroes project (to be extended once other languages/scripts are encountered).

3.3. Recording language data in XML

In XML one describes the language of the marked up text via the xml:lang attribute, documented in the XML specifications, section 2.12 Language Identification.

When the xml:lang attribute of an XML element is set to a language tag (say, la), then all its textual content is considered to be in that language (in this example Latin).

The language declaration applies not only to the content of the element itself, but also to its children, as stated in the XML specifications:

The language specified by xml:lang applies to the element where it is specified (including the values of its attributes), and to all elements in its content unless overridden with another instance of xml:lang.

In the case of the Averroes project, each manuscript has two main languages: that of the editorial content (usually English), and that of the manuscript's content (Arabic, Hebrew or Latin).

The language of the editorial content is specified in two places: in the root element and in every editorial annotation. In practical terms this means that the xml:lang attribute must be set in the root <TEI> element (see section 2.5. The root element) and in <note> elements of type editorial (see section 10. Editorial annotations).

The language of the manuscript content, instead, can be specified in many different places.

As a rule of thumb, the language of the content should be specified in the xml:lang attribute of the outermost element (e.g., <text>) and the languages used in "exceptional cases", such as editorial notes or foreign words, are specified in the xml:lang attribute of those smaller elements.

Good places where to specify the language of the main content are:

4. Text layout (eg., pages, lines)

This section describes how to encode the layout of the text, mostly the division in pages and lines.

4.1. Pages

Each page of a transcribed manuscript is encoded using a <div> element.

The attribute type must be set to page.

The attribute facs must point to the ID of the <facsimile> element that represents the digital facsimile of the manuscript page, see section 2.2.1. Facsimiles.

The attribute n may be set to the foliation number, if available. If the foliation number is physically written on the page, it must also be encoded as described in section 7.3. Page and folio numbers.

4.1.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.812-0201n="98r"> <!-- Here goes all the content appearing on the surface of the page: --> <!-- e.g., lines, margin notes, page numbers, catchwords. --> [...] </div>

4.2. Columns

Each column of text in a page is encoded using a <div> element

The attribute type must be set to column.

The <div> element that represents a column must be a direct child of the <div> element that represents the page in which the column appears.

4.2.1. Examples

<!-- TODO: use text from the illustration --><div type="page"  facs="#facsimile-BOOK-DARE-M-FR-PAR-BNF-lat.14385-0350">  <div type="column">   <l>[...]</l>   <l>[...]</l>    [...]  </div>  <div type="column">   <l>[...]</l>   <l>[...]</l>  </div> </div>

4.3. Non-transcribed columns

Columns that are present in a document but are not transcribed are encoded using an empty <gap> element.

The attribute reason must be set to pending-transcription.

The attribute quantity must be set to the number of non-transcribed lines.

The attribute unit must be set to column.

The <gap> element that represents a non-transcribed column must be a direct child of the <div> element that represents the page in which the non-transcribed column appears.

4.3.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-FR-PAR-BNF-lat.14385-0354">  <gap reason="pending-transcription"   quantity="1unit="column"/>  <div type="column">   <l>    <hi rend="initial">I</hi>n corde autem fuit [...]   </l>    [...]  </div> </div>

4.4. Lines (in single-column pages)

Each line in a single-column page is encoded using an <l> element.

The <l> element that represents a line in a single-column page must be a direct child of the <div> element that represents the page on which the line appears.

The content of the <l> element is the text of the central content. Pieces of text outside the central content must be encoded in other ways (usually using margin notes, see 7.1. Marginal annotations).

Note: TODO: find a better name for "central content"

4.4.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.811-0362n="176v"> <!-- [previous lines…] -->  <l>זה האבר וקטנותו כאשר היה יותר מעט ויותר חלוש ולזה יקרה זה המקרה לעוף ולדג ר"ל</l>  <l>שבם מה שאין לו טחול או אם יש לו טחול הוא קטן לפי שהמותר הארציי אשר בדם זה הב"ח</l>  <l>יוציא אותו הטבע סנוצה וקשקשת ולזה ימצא מה שהוא קטן הטחול קטן הריאה שותה המים</l> <!-- [following lines…] --> </div>

4.5. Lines (in multiple-columns pages)

Each line in a multiple-columns page is encoded using an <l> element.

The <l> element that represents a line in a multiple-columns page must be a direct child of the <div> element that represents the column in which the line appears.

The content of the <l> element is the text of the central content. Pieces of text outside the central content must be encoded in other ways (usually using margin notes, see 7.1. Marginal annotations).

Note: TODO: find a better name for "central content"

4.5.1. Examples

<!-- TODO: use text from illustration --><div type="pagefacs="dare-lat14385-0356"  n="168r">  <div type="column"> <!-- [previous lines…] -->   <l>[...]</l> <!-- [following lines…] -->  </div>  <div type="column"> <!-- [previous lines…] -->   <l>[...]</l> <!-- [following lines…] -->  </div> </div>

4.6. Non-transcribed lines (in single-column pages)

Lines that are present in a simple-column page but are not transcribed are encoded using an empty <gap> element.

The attribute reason must be set to pending-transcription.

The attribute quantity must be set to the number of non-transcribed lines.

The attribute unit must be set to line.

The <gap> element that represents non-transcribed lines in a single-column page must be a direct child of the <div> element that represents the page in which the lines appear.

4.6.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.811-0504n="247v">  <gap reason="pending-transcription"   quantity="15unit="line"/>  <l>   <hi type="division-starter">והקול</hi>    מתחלף בב"ח בכבדות וחדות וקטנות וגודל והשווי בין אלו הקצוות ההפכיות</l>  <l>ולפעמים יהיה הקול טוב ולפעמים יהיה מגונה וסבת התחלפות אלו הקולות</l> <!-- [following lines…] --> </div>

4.7. Non-transcribed lines (in multiple-columns pages)

Lines that are present in a multiple-columns page but are not transcribed are encoded using an empty <gap> element.

The attribute reason must be set to pending-transcription.

The attribute quantity must be set to the number of non-transcribed lines.

The attribute unit must be set to line.

The <gap> element that represents non-transcribed lines in a multi-columns page must be a direct child of the <div> element that represents the column in which the lines appear.

4.7.1. Examples

Note: TODO: add an image to illustrate non-transcribed lines in multiple-columns pages. Note: TODO: add an example to illustrate non-transcribed lines in multiple-columns pages.

5. Text structure (eg., heading, sections)

This section describes how to encode the structure of the text, i.e., its division into separate logical units.

5.1. Headings

Headings are sentences that signal and describe an upcoming significant textual division. Most of the times they contain the title of the work that is beginning.

Headings are separated from the flow of the main content, they usually appear at the beginning of the page or in the top margin. Almost always they are written bigger than the normal text.

Each heading is encoded using a <head> element.

5.1.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.811-0323n="157r">  <fw type="pageNum">157</fw>  <head xml:lang="la">Historia Animalium</head>  <head>"ספר בעלי חיים לארסטו "המאמר הראשון </head>  <l>   <hi type="rubric">אמר ארסטו</hi>    מקצת הב"ח מימיי ומקצתו גדולו מן היבשה והמימיי שני מינים יש  </l>  <l>ממנו מה שיקבל המים ומזונו בו וכשיערר אותו לא יוכל לחיות כרוב </l> </div>

5.2. Rubrics

Rubrics are used to signal the beginning of a new secondary text division.

In Hebrew manuscripts, the beginning of a new section or of a new argument is marked, often but not always, by writing the initial words in a different, bigger style.

Each division marker is encoded using a <hi> element.

The attribute type must be set to rubric.

5.2.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.812-0009n="2r">  <l>ואם היה מציאותם בו בפועל והוא אחד בהרכבה הנה הם יותר ראויים שיהיו התחלה לו</l>  <l>ויותר ראוי שיהיו קודמים לו בטבע  <hi type="rubric">הנה</hi>    כבר התבאר מדה המאמ דיעות הקדמונים  </l>  <l>והשתנות ומי חייב שרשיו בהכרעו ביניהם ומי לך חייב אותו  <hi type="rubric">הכלל</hi>  </l>  <l>   <hi type="rubric">השלשי</hi>    וזה הכלל בו שלושה פרקים  <hi type="rubric">הראשון</hi>    ‘ יגיד בו הדברי  </l>  <l>אשר ראוי שיודעו מעניין ההויה המוחלטת וההפסד</l>  <l>המוחלט. ומעניין התנועות האחרות כמו הצמיחה וההשתנות ושאר הדברי המשותפים לאילו</l> </div>

6. Corrections (e.g., additions, deletions)

This section describes how to encode corrections made to the main content.

Corrections should not be confused with glosses. Corrections provide simple, actionable instructions about how to change the text. Glosses, in contrast, provide explanations about the text, or more verbose and non directly actionable editing instructions. The encoding of glosses and of other annotations is discussed in section 7. Textual annotations (eg., margin notes, page numbers).

Corrections have three fundamental properties, all of which must be specified in every encoded correction:

The edit operation is reflected in the names of the XML element used to encode the correction, for example <add> for addition.

The technique and the position of the correction are, instead, encoded in attributes of the XML element that represents the correction itself.

Note: TODO: hands

6.1. Additions

This guideline describes the case in which the addition is part of the main content.

Each addition is encoded using an <add> element.

The attribute place must be set to one of the values described in section 6.7. Position of the correction.

6.1.1. Examples

Note: TODO: add an image to illustrate addition above line
<!-- TODO: add text from the illustration --><l>[...] <add place="above">[...]</add> [...] </l>

6.2. Additions (outside the flow of the text)

This guideline describes the case in which the text of the addition is detached from the flow of the text of the main content.

Each addition is encoded using a <add> element for the text to be added and a <metamark> milestone for the mark in the main content that signals where the text is meant to be added.

The attribute xml:id of the <metamark> element must be set according to the nomenclature rules for metamarks.

The attribute target must point to the XML ID of a metamark milestone.

Note: TODO: create a section about placement of marginal elements, share with "Marginal annotations"

The attribute place must contain two values: margin and one positional value chosen among top, bottom, left, right.

The <add> element that represents the addition must be placed outside the <l> element that represents the line where it approximately appears. The <add> element must appear before or after the related <l> element, following the reading direction of that line of text. In other words, the <add> element for the notes on the left margin are placed before the main <l> element when working with left-to-right languages but after the main <l> element when working with right-to-left languages.

6.2.1. Examples

Note: TODO: add an image to illustrate addition on the margin with target
<div type="page"  facs="BOOK-DARE-EXAMPLE-403n="218r"> <!-- TODO: use text from the illustration -->  <l>[...]  <metamark xml:id="page-403-add-1"/>    [...]  </l>  <add place="margin left"   target="page-403-add-1">[...]  </add>  <l>[...]</l> </div>

6.3. Deletions

Each deletion is encoded using a <del> element.

The attribute rend must be set to one of the values described in section 6.6. Deletion techniques.

6.3.1. Examples

Note: TODO: add an image to illustrate deletion with strikeover
<!-- TODO: use text from the illustration --><l>[...] <del rend="strikeover">[...]</del> [...] </l>

6.4. Replacements

The replacement of a piece of text with another is seen as a sequence of deletions and additions. This guideline describes the case in which both the deletions and the additions are part of the main content.

Each replacement is encoded using a <mod> element. Inside this element a deletion is recorded, using the encoding described in section 6.3. Deletions, followed by an addition encoded according to section 6.1. Additions.

The attribute type of the <mod> element must be set to subst.

6.4.1. Examples

<!-- TODO: use text from the illustration --><l>[...] <mod type="subst">   <del rend="strikeover">[...]</del>   <add place="above">[...]</add>  </mod> [...] </l>

6.5. Replacements (addition outside the flow of the text)

The replacement of a piece of text with another is seen as a sequence of deletions and additions. This guideline describes the case in which both the addition is not part of the main content, for example being in the margin.

Each replacement is encoded using a <mod> element. Inside this element a deletion is recorded, using the encoding described in section 6.3. Deletions.

The additions are encoded according to the guidelines in section 6.1. Additions.

The attribute xml:id of the <mod> element must be set according to the nomenclature rules for replacements.

The attribute type of the <mod> element must be set to subst.

The attribute target of the <add> elements that represent the additions must point to the XML ID of the <mod> element.

6.5.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.812-0228n="111v"> <!-- TODO: use text from the illustration -->  <l>[...]  <mod type="subst"    xml:id="page-0228-mod-1">    <del rend="dots-above">[...]</del>   </mod>    [...]  </l>  <add target="#page-0228-mod-1"   place="margin right">[...]</add>  <l>[...]</l> </div>

6.6. Deletion techniques

Many different techniques have been used by copyists through the centuries to mark letters, words and whose sections to be deleted.

What follows is a list of values to be used to identify which kind of technique has been used to perform a certain deletion.

These values are meant used in the rend attribute of <del> and <delSpan> elements.

dot-above

For single letters that have been deleted placing one dot above them.

dot-above-dot-under

For single letters that have been deleted placing one dot above and one dot underneath them.

dots-above

For words that have been deleted placing two or more dots above them.

strikeout

For letters and words that have been deleted by writing a line over them.

Note: TODO: add an image to illustrate a deletion with strikeout

6.7. Position of the correction

Corrections, in particular additions, can appear in various places and be even completely detached from the text they are correcting.

What follows is a list of values to be used to identify the position of a correction with respect to the text it is correcting.

above

The correction has been placed above the line in which the text to be corrected is written.

margin

The correction appears in one of the margins. This value requires an additional locator such as left or right.

top

The correction is placed on the top something (to be used in conjunction with another value, e.g., margin top).

left

The correction is placed on the left something (to be used in conjunction with another value, e.g., margin left).

bottom

The correction is placed on the bottom something (to be used in conjunction with another value, e.g., margin bottom).

right

The correction is placed on the right something (to be used in conjunction with another value, e.g., margin right).

overflow

The correction has been written as a continuation of the text but outside the normal borders.

inline

The correction has been done within the flow of the text, probably squeezing a letter or a word between the existing characters.

Note: TODO: add image to illustrate inline corrections
inspace

The correction has been placed in a predefined space, for example a blank left by an earlier scribe.

6.8. Corrections spread over multiple lines

7. Textual annotations (eg., margin notes, page numbers)

This section describes how to encode the various kinds of annotations that may appear on a page.

Annotations are pieces of texts that appear on a page but do not belong to the main content of that page.

7.1. Marginal annotations

Commentaries and annotations on the margin are encoded using the <note> element.

The attribute type must be set to gloss.

The attribute place must contain two values: margin and one positional value chosen among top, bottom, left, right.

The <note> elements that represent the margin notes must be placed outside the <l> elements that represent the line where they appear. The <note> elements must appear before or after the related <l> element, following the reading direction of that line of text. In other words, the <note> element for the notes on the left margin are placed before the main <l> element when working with left-to-right languages but after the main <l> element when working with right-to-left languages.

7.1.1. Examples

Note: TODO: add an image to illustrate margin notes LTR
<div type="page"  facs="#facsimile-BOOK-DARE-EXAMPLE-29n="10r"> <!-- TODO: add text from the illustration -->  <l>[...]</l>  <note type="gloss"   placement="margin right">[...]</note>  <l>[...]</l> </div>

Note: TODO: add an image to illustrate margin notes RTL Note: TODO: add an example to illustrate margin notes RTL

7.2. Custodes

Each custos is encoded using a <fw> element.

The attribute type must be set to catch (abbreviation of catchword).

7.2.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.812-0228n="111v">  <l>יקראו [...] החוש</l>  <fw type="catch">והתנעה</fw> </div>

7.3. Page and folio numbers

Each page or folio number is encoded using a <fw> element.

The attribute type must be set to pageNum.

7.3.1. Examples

<div type="page"  facs="#facsimile-BOOK-DARE-M-DE-BER-SB-Or.Qu.811-0361n="176v">  <fw type="pageNum">176</fw>  <l>[…]</l>  <l>[…]</l> </div>

8. Ornaments (eg., initials, drawings)

8.1. Decorative initials

Decorative initials are single letters at the beginning of a passage that are larger than the rest of the text.

There are various kinds of initials: drop caps, rubricated, figurated, historiated, etc. The transcriptions in the Averroes project do not distinguish between these different styles and treat all the decorative initials in the same way.

Each decorative initial is encoded using a <hi> element.

The attribute rend must be set to initial.

8.1.1. Examples

<l>  <hi rend="initial">I</hi>n corde autem fuit [...] </l>

8.2. Drawings (recurrent)

Each recurrent drawing is encoded using a <figure> element.

The attribute type must be set to one of the values described in section 8.2.2. Categories of recurring drawings.

8.2.1. Examples

Note: TODO: add an image to illustrate recurring drawings. Note: TODO: add an example to illustrate recurring drawings.

8.2.2. Categories of recurring drawings

What follows is a list of values to be used to identify to which class of recurring drawings a certain drawing belongs to.

These values are meant to be used in the type type attributes of <figure> elements.

pointing-hand

For hands in which one finger points to a certain word or line.

9. Editor-supplied readings (eg., unreadable texts, abbreviations)

This section describes how to encode parts of a manuscript whose transcription is not perfectly clear or, in general cases that require an active act of interpretation from the editor.

9.1. Abbreviations

Common and unambiguous abbreviations are not recorded. In the transcription they are simply replaced with their expansions.

Peculiar, unclear and ambiguous abbreviations are recorded, together with the expansion supplied by the editor. This guideline describes how to encode these non-obvious abbreviations.

Each abbreviation is encoded using a <choice> element. This element must contain two other elements:

9.1.1. Examples

Note: TODO: add an image to illustrate abbreviations
<!-- TODO: use text from the illustration --><l>[...] <choice>   <abbr>[...]</abbr>   <expan>[...]</expan>  </choice> [...] </l>

9.2. Words broken over multiple lines

Words at the end of a line may be split abruptly, with the first part of the word in one line and the second part in the following line. These split words are identified by the editor, so that it will be possible to treat these words differently during the processing of the transcriptions.

Each word broken over multiple lines is encoded adding a <lb> element after the broken word.

The attribute break must be set to no.

The <lb> element should be the last element of the parent <l> element.

9.2.1. Examples

<l>[…] principium omnium di<lb break="no"/> </l> <l>xit esse cor.[…]</l>

9.3. Exact transcriptions of apparent mistakes

Sometimes words that appear in archaic or uncommon forms may be mistaken for misspellings. When transcribing such words, the editor may want to draw attention to the fact that those spellings are faithful to what is present in the manuscript and are not transcription mistakes.

Each apparent mistake is encoded wrapping the apparent mistake in a <sic> element.

9.3.1. Examples

Note: TODO: add image
<l>[...] שהאש מבואר מענינו שלא <sic>יהוה</sic> הב"ח </l>

9.4. Obvious mistakes

The texts to be transcribed may contain passages that are in need of correction. In some cases it is clear what the correction should be. At the same time, the editor cannot just replace the mistake with a correction, for this would not be faithful to the content of the manuscript. Mistakes are thus transcribed as they appear, identified as mistakes and a correction is provided.

Each mistake is encoded using a <choice> element. This element must contain two other elements:

9.4.1. Examples

<l>[...] הראשונה <choice>   <sic>והזנה הראשונה והזנה הראשונה   </sic>   <supplied>והזנה הראשונה   </supplied>  </choice> אמנם </l>

9.5. Unknown glyphs

Sometimes glyphs of unclear meaning appear in manuscripts. These glyphs may be anything: from unknown abbreviation signs to letters in forgotten alphabets.

Each unknown glyph is encoded with a <g> element.

If the unknown glyph has a close-enough representation as a Unicode character, that character should be placed inside the <g> element.

An editorial note (see section 10.1. Notes about the content) with an explanation of the editor understanding of the glyph should be added inside the <g> element.

9.5.1. Examples

<l>  <g>ו  <note type="editorialxml:lang="en">strange letter at the      beginning of the line: it looks like the first letter      of the line but it is not part of the text and      its function is unclear.</note>  </g> ויאמר שאם […] </l> <l>  <g>ב  </g> בשאר האברים […] </l>

9.6. Unclear passages (only one supplied reading)

An unclear passage is a word or a sequence of words which cannot be transcribed with certainty because it is physically illegible. This guideline describes the cases in which only one plausible reading is provided by the editor.

Each unclear passage with one supplied reading is encoded wrapping the supplied reading in an <unclear> element.

9.6.1. Examples

Note: TODO: add an image to illustrate unclear passages (one reading) Note: TODO: add an example to illustrate unclear passages (one reading)

9.7. Unclear passages (more than one supplied reading)

An unclear passage is a word or a sequence of words which cannot be transcribed with certainty because it is physically illegible. This guideline describes the cases in which multiple plausible readings are provided by the editor.

Each unclear passage with multiple supplied readings is encoded with an <unclear> element. Inside this element a <choice> element is added. Finally one <unclear> element is added inside the <choice> element for each supplied reading.

Editorial notes (see section 10.1. Notes about the content) can be added after the <choice> element, to provide notes that apply too all the supplied readings, or inside the nested <unclear> elements, to explain that particular supplied reading.

9.7.1. Examples

<l> המניע גובר לאויר המתנועע ממנו באברי הקול יהיה קולו חד בהכרח לפי שתנועת האויר <unclear>   <choice>    <unclear>        בחלל    </unclear>    <unclear>        כדלי    </unclear>   </choice>   <note type="editorialxml:lang="en">the shape      of Het is very different from the usual one      in this manuscript; is it a combination of other      letters, eg. Zayin and Waw?</note>  </unclear> </l>

9.8. Unclear passages (no supplied readings)

An unclear passage is a word or a sequence of words which cannot be transcribed with certainty because it is physically illegible. This guideline describes the cases in which no plausible readings are provided by the editor.

Each unclear passage with no supplied readings is encoded with an <unclear> element. Inside this element a <gap> element is added.

The attribute reason of the <gap> element must be set to illegible.

The attribute quantity of the <gap> element must be set to the (approximate) number of unclear characters.

The attribute unit of the <gap> element must be set to character.

9.8.1. Examples

Note: TODO: add an image to illustrate unclear passages (no readings) Note: TODO: add an example to illustrate unclear passages (no readings)

9.9. Damaged parts (no supplied readings)

A damaged part is a region of a line which a physical damage prevents the editor from reading the text that was originally present in that region. This guideline describes the case in the editor is unable or unwilling to provide to supply a reading of the damaged text.

Each damaged part of a line is encoded using a <damage> element. Inside this element a <gap> element is added.

The attribute reason of the <gap> element must be set to damaged.

The attribute quantity of the <gap> element must be set to the (approximate) length of the damage in millimeters.

The attribute unit of the <gap> element must be set to mm.

9.9.1. Examples

Note: TODO: add an image to illustrate damaged parts with no supplied readings. Note: TODO: add an example to illustrate damaged parts with no supplied readings.

9.10. Damaged parts (unclear reading)

A damaged part is a region of a line which a physical damage prevents the editor from reading the text that was originally present in that region. This guideline describes the case in the editor supplies a reading of the damaged text based on some legible parts of the text.

Each damaged part of a line is encoded using a <damage> element. Inside this element an the unclear text is encoded according to the guidelines described in 9.6. Unclear passages (only one supplied reading), 9.7. Unclear passages (more than one supplied reading) and 9.8. Unclear passages (no supplied readings).

9.10.1. Examples

Note: TODO: add an image to illustrate damaged parts with supplied readings. Note: TODO: add an example to illustrate damaged parts with supplied readings.

10. Editorial annotations

This section describes how to encode notes from the editors transcribing the manuscripts.

10.1. Notes about the content

Each editorial note about the content is encoded using a <note> element.

The attribute type must be set to editorial.

The attribute xml:lang must be set to the language in which the note is written, see section 3. Handling of languages and scripts.

10.1.1. Examples

<l>וגאלינוס מסכים עם ארסטו" על שהתחלת <note type="editorialxml:lang="en">   <p>Here a piece of text may be missing, probably      due to homoteleuton.</p>  </note> והעוקרים אשר בו הדם ראוי שיהיה אחד ושזה האבר </l>

10.2. Notes about the XML encoding

Note: TODO: describe encoding of notes about XML tags: use XML comments.

11. Division in chunks

This section describes how to mark part of the text as being related to a certain work, or chunk of a work.

11.1. Segmentation mechanism

The segmentation mechanism is used to divide the text in segments. These segments can then be associated to other texts or abstract works.

A segment is identified by a pair of points: the initial point and the final point.

The initial point of a segment is encoded using an empty <span> element.

The attribute xml:id of the span of the initial point must be set according to the nomenclature rules for initial segment points.

The attribute to of the span of the initial point must point to the XML ID of the corresponding final point.

The attribute corresp of the span of the initial point must point one or more work identifiers. For possible work identifiers see section 11.2. Linking segments to DARE chunks.

The final point of a segment is encoded using an empty <span> element.

The attribute xml:id of the span of the final point must be set according to the nomenclature rules for final segment points.

The attribute from of the span of the final point must point to the XML ID of the corresponding initial point.

Different segments cannot share points. For example, it is not possible for the initial point of segment to be also the initial point of another subsequent segment.

11.1.1. Examples

Note: TODO: add image to illustrate segmentation
<!-- TODO: use text from the illustration --><div type="page"  facs="#facsimile-BOOK-DARE-EXAMPLE-0234">[...] <l>[...]  <span xml:id="page-0234-seg-1"    to="#page-0235-seg-1corresp="DARE-Averroes-DeAnimalibus-12"/>    [...]  </l>  <l>[...]</l>  <l>[...]</l> </div> <div type="page"  facs="#facsimile-BOOK-DARE-EXAMPLE-0235">  <l>[...]</l>  <l>[...]</l>  <l>[...]  <span xml:id="page-0235-seg-1"    from="#page-0234-seg-1"/>    [...]  </l> [...] </div>

11.2. Linking segments to DARE chunks

The main use case for segments is to link transcription to the abstract DARE chunk identifiers.

To link a segment to a certain DARE chunk one must add the chunk ID to the corresp attribute of the <span> element of the initial segment point. The encoding of the segments and of the initial segment points is described in detail in the previous section, 11.1. Segmentation mechanism.

The complete list of available DARE chunk IDs is available at Note: TODO: add link to the list of DARE chunk IDs.

11.3. Overlapping segments

A single pieces of text may belong to more than one segments. In this case one say that those segments are overlapping.

Technically speaking, one says that two segments are overlapping if the final point of a segment is placed between the initial and the final point of the other segment.

Overlapping segments are allowed.

The most common case in which overlapping segments are needed is when text contain citations: the cited segments will encompass the citing segments. The way segments are implements allows both segments to be independently identified and linked to different abstract works.

12. Style recommendation for the XML markup

This section describes how to organize the XML markup so to make the XML files consistent and, in turn, simplifying the job of the editors and the developers.

12.1. One script per line

Each line in the XML transcription files should be composed of characters belonging to one script only.

This rule prevents many editing difficulties, especially when transcribing right-to-left languages. For instance, in lines where left-to-right and right-to-left languages are mixed, it becomes very hard to navigate the text using the keyboard arrows or the Home/End keys. Pressing the Return key has also surprising effects often.

Practically speaking, in the transcriptions of non-Latin manuscripts, markup tags should almost always appear on their own lines.

For example, instead of
<div type="page"  face="#facsimile-DARE-EXAMPLE-0001">  <l>זה האבר וקטנותו כאשר היה יותר מעט ויותר חלוש ולזה יקרה זה המקרה לעוף ולדג ר"ל</l> </div>
one should use
<div type="page"  face="#facsimile-DARE-EXAMPLE-0001">  <l>    זה האבר וקטנותו כאשר היה יותר מעט ויותר חלוש ולזה יקרה זה המקרה לעוף ולדג ר"ל  </l> </div>
A more complex example, in which the advantages of this recommendation should be more evident, is the following, in many words are marked up. Instead of writing
<l>  <mod type="subst">   <del rend="dots-over">זמן</del>    מדת שלמות יצירתו  <del rend="strikeover">וגם</del>   <add rend="abovehand="#2">וזה</add>  </mod> ישוב אל מזגו וגודל גופו וכן הזמנים שיש לו חוץ הרחם ימצאו </l> <l>הגדול הגוף <!-- so MS New York, JTS 2249, fol. 107v too, but MS Berlin Or. qu. 811, fol. 242v: ומי שגופו גדול זמנו יותר ארוך --> כמו שזמן התהוותו יותר ארוך מזמן התהוות כח הקטן הגוף כן חייו יותר ארוכים</l> <l>מחיי קטן הגוף ואולם היה זה כן בעבור הח<add rend="abovehand="#2">ו</add>ם והלחות הגובר על מזגם אבל אין כל מה </l>
one should use
<l>  <mod type="subst">   <del rend="dots-over">      זמן   </del>    מדת שלמות יצירתו  <del rend="strikeover">      וגם   </del>   <add rend="abovehand="#2">      וזה   </add>  </mod> ישוב אל מזגו וגודל גופו וכן הזמנים שיש לו חוץ הרחם ימצאו </l> <l> הגדול הגוף <!-- so MS New York, JTS 2249, fol. 107v too, but MS Berlin Or. qu. 811, fol. 242v: ומי שגופו גדול זמנו יותר ארוך --> כמו שזמן התהוותו יותר ארוך מזמן התהוות כח הקטן הגוף כן חייו יותר ארוכים </l> <l> מחיי קטן הגוף ואולם היה זה כן בעבור הח<lb break="no"/>  <add rend="abovehand="#2xml:space="">    ו  <lb break="no"/>  </add> ם והלחות הגובר על מזגם אבל אין כל מה </l>
Note: TODO: discuss whitespace implications

13. Directions on how to process the transcription files

This section describes some details to be taken into account when processing the transcription files.

Note: The moment in which XML files are processed, regardless of which application is processing them, is referred to as process-time.

13.1. Normalization of whitespaces

Note: TODO: use `normalize-string()` everywhere.
Note: TODO: remove space before/after certain elements (list + ref).

13.2. Words broken over multiple lines

As explained in section 9.2. Words broken over multiple lines, in certain manuscripts, words at the end of a line may be split abruptly, with the first part of the word in one line and the second part in the following line.

Given the way in which lines are encoded, i.e. using <l> elements (see sections 4.4. Lines (in single-column pages) and 4.5. Lines (in multiple-columns pages)) it is not possible without some indications from the editor to understand at process-time whether the last word at the end of the line should be attached to the first one on the next line. The <lb> elements place by the editor allow the applications to find the words to be joined.

When an application encounters a <lb> element with break set to no, it should:

The last word is the last independent word found in the first non-empty text node along the preceding or preceding-sibling XPath axis.

The next word is the first independent word found in the first non-empty text node along the following or following-sibling XPath axis of the main content. Please note that this means that elements used to encode glosses or custodes should not be included in the elements where the next word is searched.

The meaning of "independent word" is language dependent, so the value of the xml:lang attribute should be taken into account. In general, however, independent words are just space-separated tokens.

Appendix A Detailed list of elements

What follows is the complete schema.

Appendix A.1 Elements

Appendix A.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.resourceLike class. Multiple TEI elements may be combined to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
AttributesAttributes att.typed (@type) att.global (xml:lang, @xml:id, @n, @xml:base, @xml:space) att.global.rendition (@rend) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.responsibility (@cert, @resp)
xml:lang(language) indicates the language of the editorial content using a tag generated according to BCP 47. See sections 2.5. The root element and 3. Handling of languages and scripts.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
versionspecifies the major version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
NoteThe major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the <schemaSpec> element. The current version is P5.
Contained by
core: teiCorpus
May contain
header: teiHeader
textstructure: text
NoteThis element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.
Example
<TEI version="5.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 name space.</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="5.0" xmlns="//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
<s:ns prefix="tei"  uri="//tei-c.org/ns/1.0"/> <s:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<s:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/>
Content model
<content>
 <elementRef key="teiHeader"/>
 <elementRef key="text"/>
</content>
    
Schema Declaration
element TEI
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   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.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.typed.attributes,
   attribute xml:lang { text },
   attribute version { text }?,
   teiHeader,
   text
}

Appendix A.1.2 <ab>

<ab> (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. Blocks, Segments, and Anchors]
Modulelinking
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
Member of
Contained by
May contain
NoteThe <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined.
Example
<div type="bookn="Genesis">  <div type="chaptern="1">   <ab>In the beginning God created the heaven and the earth.</ab>   <ab>And the earth was without form, and void; and      darkness was upon the face of the deep. And the      spirit of God moved upon the face of the waters.</ab>   <ab>And God said, Let there be light: and there was light.</ab> <!-- ...-->  </div> </div>
Schematron
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(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: ab may not contain paragraphs or other ab elements. </s:report>
Schematron
<s:report test="ancestor::tei:l or ancestor::tei:lg"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab. </s:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ab
{
   att.global.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.fragmentable.attributes,
   att.written.attributes,
   macro.paraContent
}

Appendix A.1.3 <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.source (@source)
typeallows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
suspension
the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
the abbreviation includes writing above the line.
acronym
the abbreviation comprises the initial letters of the words of a phrase.
title
the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
the abbreviation is for the name of an organization.
geographic
the abbreviation is for a geographic name.
NoteThe 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 [[undefined PETTY]]
Member of
Contained by
May contain
NoteThe <abbr> tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate.
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.source.attributes,
   attribute type { text }?,
   macro.phraseSeq
}

Appendix A.1.4 <abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.source (@source)
Member of
Contained by
header: profileDesc
May contain
core: list p
linking: ab
NoteThis element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a <div> within the <front>, as it should for a born-digital document.
Example
<profileDesc>  <abstract resp="#LB">   <p>Good database design involves the acquisition and deployment of      skills which have a wider relevance to the educational process. From      a set of more or less instinctive rules of thumb a formal discipline      or "methodology" of database design has evolved. Applying that      methodology can be of great benefit to a very wide range of academic      subjects: it requires fundamental skills of abstraction and      generalisation and it provides a simple mechanism whereby complex      ideas and information structures can be represented and manipulated,      even without the use of a computer. </p>  </abstract> </profileDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
 </alternate>
</content>
    
Schema Declaration
element abstract
{
   att.global.attributes,
   att.source.attributes,
   ( model.pLike | model.listLike )+
}

Appendix A.1.5 <accMat>

<accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript being described, such as non-contemporaneous documents or fragments bound in with the manuscript at some earlier historical period. [10.7.3.3. Accompanying Material]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
msdescription: physDesc
May contain
Example
<accMat>A copy of a tax form from 1947 is included in the envelope with the letter. It is not catalogued separately.</accMat>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element accMat
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}

Appendix A.1.6 <acquisition>

<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. History]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Contained by
msdescription: history
May contain
Example
<acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element acquisition
{
   att.global.attributes,
   att.datable.attributes,
   macro.specialPara
}

Appendix A.1.7 <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.typed (@type) att.pointing (targetLang, evaluate, @target)
placespecifies where this item is placed.
Derived fromatt.placement
StatusRequired
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
above
above the line.
margin
in the margin.
top
on the top (to use in conjunction with another value, e.g., margin left).
left
on the left (to use in conjunction with another value, e.g., margin left).
bottom
on the bottom (to use in conjunction with another value, e.g., margin bottom).
right
on the right (to use in conjunction with another value, e.g., margin right).
overflow
as a continuation of the text but outside the normal borders.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
Member of
Contained by
May contain
NoteThe Averroes project uses this element in an idiosyncratic way.In the TEI guidelines, this element cannot appear directly under <div> elements and has no target attribute.
Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
SchematronAn addition must refer to a local metamark or a replacement site
<sch:rule context="tei:add[@target]"> <sch:assert test="substring(@target, 1, 1) = '#'">The attribute target must point to a local ID.</sch:assert> </sch:rule> <sch:rule context="tei:add[@target][substring(@target, 1, 1) = '#']"> <sch:let name="target-id"  value="substring-after(@target, '#')"/> <sch:assert test="//tei:*[self::tei:metamark or self::tei:mod][@xml:id = $target-id]">The attribute target must point to the ID of a metamark or a mod element.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   attribute place
   {
      list
      {
         (
            "above"
          | "margin"
          | "top"
          | "left"
          | "bottom"
          | "right"
          | "overflow"
          | "inline"
          | "inspace"
         )+
      }
   },
   att.pointing.attribute.target,
   macro.paraContent
}

Appendix A.1.8 <addSpan>

<addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [11.3.1.4. Additions and Deletions]
Moduletranscr
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.placement (@place) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
NoteBoth the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute.
Example
<handNote xml:id="HEOL"  scribe="HelgiÓlafsson"/> <!-- ... --> <body>  <div> <!-- text here -->  </div>  <addSpan n="added gatheringhand="#HEOL"   spanTo="#P025"/>  <div> <!-- text of first added poem here -->  </div>  <div> <!-- text of second added poem here -->  </div>  <div> <!-- text of third added poem here -->  </div>  <div> <!-- text of fourth added poem here -->  </div>  <anchor xml:id="P025"/>  <div> <!-- more text here -->  </div> </body>
Schematron
<sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
Schematron
<sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
Content model
<content>
</content>
    
Schema Declaration
element addSpan
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.placement.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}

Appendix A.1.9 <additional>

<additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. Additional Information]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msFrag msPart
May contain
core: listBibl
msdescription: adminInfo surrogates
Example
<additional>  <adminInfo>   <recordHist>    <p> <!-- record history here -->    </p>   </recordHist>   <custodialHist>    <p> <!-- custodial history here -->    </p>   </custodialHist>  </adminInfo>  <surrogates>   <p> <!-- information about surrogates here -->   </p>  </surrogates>  <listBibl>   <bibl> <!-- ... -->   </bibl> <!-- full bibliography here -->  </listBibl> </additional>
Content model
<content>
 <sequence>
  <elementRef key="adminInfo" minOccurs="0"/>
  <elementRef key="surrogates"
   minOccurs="0"/>
  <elementRef key="listBibl" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element additional
{
   att.global.attributes,
   ( adminInfo?, surrogates?, listBibl? )
}

Appendix A.1.10 <additions>

<additions> contains a description of any significant additions found within a manuscript, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
Example
<additions>  <p>There are several marginalia in this manuscript. Some consist of    single characters and others are figurative. On 8v is to be found a drawing of    a mans head wearing a hat. At times sentences occurs: On 5v:  <q xml:lang="is">Her er skrif andres isslendin</q>,    on 19r: <q xml:lang="is">þeim go</q>,    on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad      batar þad mælgi ok mal</q>,    On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p> </additions>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element additions { att.global.attributes, macro.specialPara }

Appendix A.1.11 <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: address
May contain
NoteAddresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { att.global.attributes, macro.phraseSeq }

Appendix A.1.12 <address>

<address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
NoteThis element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.
Example
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name n="I">Italy</name> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   att.global.attributes,
   ( model.global*, ( model.addrPart, model.global* )+ )
}

Appendix A.1.13 <adminInfo>

<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript, and also about the record description itself. [10.9.1. Administrative Information]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: additional
May contain
core: note
header: availability
msdescription: custodialHist recordHist
Example
<adminInfo>  <recordHist>   <source>Record created <date>1 Aug 2004</date>   </source>  </recordHist>  <availability>   <p>Until 2015 permission to photocopy some materials from this      collection has been limited at the request of the donor. Please ask repository staff for details      if you are interested in obtaining photocopies from Series 1:      Correspondence.</p>  </availability>  <custodialHist>   <p>Collection donated to the Manuscript Library by the Estate of      Edgar Holden in 1993. Donor number: 1993-034.</p>  </custodialHist> </adminInfo>
Content model
<content>
 <sequence>
  <elementRef key="recordHist"
   minOccurs="0"/>
  <elementRef key="availability"
   minOccurs="0"/>
  <elementRef key="custodialHist"
   minOccurs="0"/>
  <classRef key="model.noteLike"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element adminInfo
{
   att.global.attributes,
   ( recordHist?, availability?, custodialHist?, model.noteLike? )
}

Appendix A.1.14 <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
msdescription: msFrag msIdentifier msPart
May contain
core: note
header: idno
NoteAn identifying number of some kind must be supplied if known; if it is not known, this should be stated.
Example
<altIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </altIdentifier>
Content model
<content>
 <sequence>
  <classRef key="model.placeNamePart"
   expand="sequenceOptional"/>
  <elementRef key="institution"
   minOccurs="0"/>
  <elementRef key="repository"
   minOccurs="0"/>
  <elementRef key="collection"
   minOccurs="0"/>
  <elementRef key="idno"/>
  <elementRef key="note" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element altIdentifier
{
   att.global.attributes,
   att.typed.attributes,
   ( institution?, repository?, collection?, idno, note? )
}

Appendix A.1.15 <am>

<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
Moduletranscr
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
May contain
Example
do you <abbr>Mr<am>.</am> </abbr> Jones?
Example
<expan>  <abbr>Aug<am>g</am>  </abbr>  <ex>ustorum duo</ex> </expan>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.pPart.transcriptional"/>
 </alternate>
</content>
    
Schema Declaration
element am
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   ( text | model.gLike | model.pPart.transcriptional )*
}

Appendix A.1.16 <analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.11.2.1. Analytic, Monographic, and Series Levels]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
NoteMay contain titles and statements of responsibility (author, editor, or other), in any order.The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item.
Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <biblScope>25.6</biblScope>    <date when="1991-12">(December, 1991):</date>    <biblScope>377–380</biblScope>   </imprint>  </monogr> </biblStruct>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   att.global.attributes,
   (
      authoreditorrespStmttitlemodel.ptrLikedatetextLangidnoavailability
   )*
}

Appendix A.1.17 <anchor>

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.4. Correspondence and Alignment]
Modulelinking
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May containEmpty element
NoteOn this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.
Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s> <s>Help me find it.<ptr target="#A234"/> </s>
Content model
<content>
</content>
    
Schema Declaration
element anchor { att.global.attributes, att.typed.attributes, empty }

Appendix A.1.18 <appInfo>

<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.10. The Application Information Element]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>  <application version="1.24ident="Xaira">   <label>XAIRA Indexer</label>   <ptr target="#P1"/>  </application> </appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element appInfo { att.global.attributes, model.applicationLike+ }

Appendix A.1.19 <application>

<application> provides information about an application which has acted upon the document. [2.3.10. The Application Information Element]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
linking: ab
Example
<appInfo>  <application version="1.5"   ident="ImageMarkupTool1notAfter="2006-06-01">   <label>Image Markup Tool</label>   <ptr target="#P1"/>   <ptr target="#P2"/>  </application> </appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.
Content model
<content>
 <sequence>
  <classRef key="model.labelLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.ptrLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element application
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute ident { text },
   attribute version { text },
   ( model.labelLike+, ( model.ptrLike* | model.pLike* ) )
}

Appendix A.1.20 <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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
May contain
NoteParticularly 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,
   macro.phraseSeq
}

Appendix A.1.21 <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.]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: monogr
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority { att.global.attributes, macro.phraseSeq.limited }

Appendix A.1.22 <availability>

<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
statussupplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
the text is freely available.
unknown
the status of the text is unknown.[Default]
restricted
the text is not freely available.
Member of
Contained by
msdescription: adminInfo
May contain
core: p
header: licence
linking: ab
NoteA consistent format should be adopted
Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   att.global.attributes,
   att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( model.availabilityPart | model.pLike )+
}

Appendix A.1.23 <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls)
Contained by
textstructure: text
transcr: facsimile
May contain
NoteBecause 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>  <div1 type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>To shew the Depravity of human Nature </p>  </div1>  <div1 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>  </div1>  <div1 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>  </div1>  <div1 type="advert">   <head>    <hi rend="center">By the KING's Royal Patent,</hi> 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>  </div1> </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.24 <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
NoteContains phrase-level elements, together with any combination of elements from the 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.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      text
    | model.gLikemodel.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}

Appendix A.1.25 <biblFull>

<biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 15.3.2. Declarable Elements]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Example
<biblFull>  <titleStmt>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>  </titleStmt>  <editionStmt>   <edition>UK edition</edition>  </editionStmt>  <extent>1231 pp</extent>  <publicationStmt>   <publisher>Yale University Press</publisher>   <pubPlace>New Haven and London</pubPlace>   <date>1990</date>  </publicationStmt>  <sourceDesc>   <p>No source: this is an original work</p>  </sourceDesc> </biblFull>
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"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element biblFull
{
   att.global.attributes,
   att.declarable.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt?,
         notesStmt?
      ),
      sourceDesc*
   )
}

Appendix A.1.26 <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.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.citing (@unit, @from, @to)
Member of
Contained by
May contain
NoteWhen 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 should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.
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.attributes,
   macro.phraseSeq
}

Appendix A.1.27 <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
SchematronThe use of an <idno> element as a direct child of <biblStruct> is deprecated. Rather, <idno> should appear as a child of a <monogr>, <analytic>, or <series>.
<sch:report test="child::tei:idno"  role="nonfatal">WARNING: use of deprecated method — the use of the idno element as a direct child of the biblStruct element will be removed from the TEI on 2016-09-18</sch:report>
Content model
<content>
 <sequence>
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <elementRef key="idno"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      analytic*,
      ( monogr, series* )+,
      ( model.noteLike | idno | model.ptrLike | relatedItem | citedRange )*
   )
}

Appendix A.1.28 <binding>

<binding> contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript. [10.7.3.1. Binding Descriptions]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
contemporaryspecifies whether or not the binding is contemporary with the majority of its contents
StatusOptional
Datatypeteidata.xTruthValue
NoteThe value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown
Contained by
msdescription: bindingDesc
May contain
core: p
linking: ab
msdescription: condition decoNote
Example
<binding contemporary="true">  <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp    closing to the back cover.</p> </binding>
Example
<bindingDesc>  <binding contemporary="false">   <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front      pastedown.</p>  </binding>  <binding contemporary="false">   <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>  </binding> </bindingDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <elementRef key="condition"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
    
Schema Declaration
element binding
{
   att.global.attributes,
   att.datable.attributes,
   attribute contemporary { text }?,
   ( model.pLike | condition | decoNote )+
}

Appendix A.1.29 <bindingDesc>

<bindingDesc> (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
msdescription: binding condition decoNote
Example
<bindingDesc>  <p>Sewing not visible; tightly rebound over    19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with    gilt tooling à la fanfare, Paris c. 1580-90, the centre of each    cover inlaid with a 17th-cent. oval medallion of red morocco tooled in    gilt (perhaps replacing the identifying mark of a previous owner); the    spine similarly tooled, without raised bands or title-piece; coloured    endbands; the edges of the leaves and boards gilt.Boxed.</p> </bindingDesc>
Content model
<content>
 <alternate>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.pLike"/>
   <elementRef key="decoNote"/>
   <elementRef key="condition"/>
  </alternate>
  <elementRef key="binding" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element bindingDesc
{
   att.global.attributes,
   ( ( model.pLike | decoNote | condition )+ | binding+ )
}

Appendix A.1.30 <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls)
Contained by
textstructure: text
May contain
textstructure: div
SchematronThe body of the transcription is composed only of pages.
<sch:rule context="tei:body/tei:div"> <sch:assert test="@type='page'">Only div elements of type page are allowed in the body element.</sch:assert> </sch:rule>
Content model
<content>
 <elementRef key="div" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element body { att.global.attributes, att.declaring.attributes, div* }

Appendix A.1.31 <byline>

<byline> contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: lg list
msdescription: msItem
May contain
NoteThe byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docAuthor> element.
Example
<byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline>
Example
<byline>Written from her own MEMORANDUMS</byline>
Example
<byline>By George Jones, Political Editor, in Washington</byline>
Example
<byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="docAuthor"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element byline
{
   att.global.attributes,
   ( text | model.gLike | model.phrase | docAuthor | model.global )*
}

Appendix A.1.32 <cRefPattern>

<cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.patternReplacement (@matchPattern, @replacementPattern)
Contained by
header: refsDecl
May contain
core: p
linking: ab
NoteThe result of the substitution may be 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 cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.
Example
<cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"  replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element cRefPattern
{
   att.global.attributes,
   att.patternReplacement.attributes,
   model.pLike*
}

Appendix A.1.33 <calendar>

<calendar> describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate)
Contained by
header: calendarDesc
May contain
core: p
linking: ab
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,
   model.pLike+
}

Appendix A.1.34 <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]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: profileDesc
May contain
header: calendar
NoteIn 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.35 <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]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
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,
   ( text | model.limitedPhrase | model.catDescPart )*
}

Appendix A.1.36 <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate)
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May containEmpty element
NoteThe scheme attribute need 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>
</content>
    
Schema Declaration
element catRef
{
   att.global.attributes,
   att.pointing.attributes,
   attribute scheme { text }?,
   empty
}

Appendix A.1.37 <catchwords>

<catchwords> describes the system used to ensure correct ordering of the quires making up a codex or incunable, typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Example
<catchwords>Vertical catchwords in the hand of the scribe placed along the inner bounding line, reading from top to bottom.</catchwords>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element catchwords { att.global.attributes, macro.phraseSeq }

Appendix A.1.38 <category>

<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
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"/>
    <classRef key="model.glossLike"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   att.global.attributes,
   ( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* )
}

Appendix A.1.39 <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]
Moduleheader
AttributesAttributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
targetpoints to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
msdescription: recordHist
May contain
NoteThe 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 target { list { + } }?,
   macro.specialPara
}

Appendix A.1.40 <char>

<char> (character) provides descriptive information about a character. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
gaiji: charDecl
May contain
Example
<char xml:id="circledU4EBA">  <charName>CIRCLED IDEOGRAPH 4EBA</charName>  <charProp>   <unicodeName>character-decomposition-mapping</unicodeName>   <value>circle</value>  </charProp>  <charProp>   <localName>daikanwa</localName>   <value>36</value>  </charProp>  <mapping type="standard"></mapping> </char>
Content model
<content>
 <sequence>
  <elementRef key="charName" minOccurs="0"/>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="charProp" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="mapping" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="figure" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.graphicLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element char
{
   att.global.attributes,
   (
      charName?,
      model.descLike*,
      charProp*,
      mapping*,
      figure*,
      model.graphicLike*,
      model.noteLike*
   )
}

Appendix A.1.41 <charDecl>

<charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: encodingDesc
May contain
core: desc
gaiji: char glyph
Example
<charDecl>  <char xml:id="aENL">   <charName>LATIN LETTER ENLARGED SMALL A</charName>   <mapping type="standard">a</mapping>  </char> </charDecl>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="char"/>
   <elementRef key="glyph"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) }

Appendix A.1.42 <charName>

<charName> (character name) contains the name of a character, expressed following Unicode conventions. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
gaiji: char
May containCharacter data only
NoteThe name must follow Unicode conventions for character naming. Projects working in similar fields are recommended to coordinate and publish their list of <charName>s to facilitate data exchange.
Example
<charName>CIRCLED IDEOGRAPH 4EBA</charName>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element charName { att.global.attributes, text }

Appendix A.1.43 <charProp>

<charProp> (character property) provides a name and value for some property of the parent character or glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Contained by
gaiji: char glyph
May contain
NoteIf the property is a Unicode Normative Property, then its <unicodeName> must be supplied. Otherwise, its name must be specied by means of a <localName>.At a later release, additional constraints will be defined on possible value/name combinations using Schematron rules
Example
<charProp>  <unicodeName>character-decomposition-mapping</unicodeName>  <value>circle</value> </charProp> <charProp>  <localName>daikanwa</localName>  <value>36</value> </charProp>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="unicodeName"/>
   <elementRef key="localName"/>
  </alternate>
  <elementRef key="value"/>
 </sequence>
</content>
    
Schema Declaration
element charProp
{
   att.global.attributes,
   att.typed.attributes,
   ( ( unicodeName | localName ), value )
}

Appendix A.1.44 <choice>

<choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
NoteBecause 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.
ExampleAn 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="1" maxOccurs="1">
  <elementRef key="unclear" minOccurs="2"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="abbr"/>
   <elementRef key="expan"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="sic"/>
   <elementRef key="corr"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   att.global.attributes,
   ( unclear+ | unclear+ | ( abbr, expan ) | ( sic, corr ) )
}

Appendix A.1.45 <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]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May contain
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>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.qLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.global"/>
  <classRef key="model.entryPart"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.qLike
    | model.egLike
    | model.biblLikemodel.ptrLikemodel.global
    | model.entryPart
   )+
}

Appendix A.1.46 <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
Member of
Contained by
May contain
NoteWhen the range cited consists of a single page or other unit, use the from and to attributes with an identical value. When no clear endpoint is given the from attribute should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.
Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   att.global.attributes,
   att.pointing.attributes,
   att.citing.attributes,
   macro.phraseSeq
}

Appendix A.1.47 <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
schemeidentifies the classification system in use, as defined by for example by a <taxonomy> element, or some other resource.
StatusRequired
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May contain
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element classCode
{
   att.global.attributes,
   attribute scheme { text },
   macro.phraseSeq.limited
}

Appendix A.1.48 <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]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
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.49 <closer>

<closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.written (@hand)
Member of
Contained by
core: lg list
textstructure: back div front group postscript
May contain
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   att.global.attributes,
   att.written.attributes,
   (
      text
    | model.gLikesigneddatelinesalutemodel.phrasemodel.global
   )*
}

Appendix A.1.50 <collation>

<collation> contains a description of how the leaves or bifolia are physically arranged. [10.7.1. Object Description]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: supportDesc
May contain
Example
<collation>The written leaves preceded by an original flyleaf, conjoint with the pastedown.</collation>
Example
<collation>  <p>   <formula>1-5.8 6.6 (catchword, f. 46, does not match following text)      7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>   <catchwords>Catchwords are written horizontally in center      or towards the right lower margin in various manners:      in red ink for quires 1-6 (which are also signed in red      ink with letters of the alphabet and arabic numerals);      quires 7-9 in ink of text within yellow decorated frames;      quire 10 in red decorated frame; quire 12 in ink of text;      quire 13 with red decorative slashes; quire 14 added in      cursive hand.</catchwords>  </p> </collation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element collation { att.global.attributes, macro.specialPara }

Appendix A.1.51 <collection>

<collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type)
Contained by
May contain
gaiji: g
Example
<msIdentifier>  <country>USA</country>  <region>California</region>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <collection>Ellesmere</collection>  <idno>El 26 C 9</idno>  <msName>The Ellesmere Chaucer</msName> </msIdentifier>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element collection
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.xtext
}

Appendix A.1.52 <colophon>

<colophon> contains the colophon of a manuscript item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript. [10.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<colophon>Ricardus Franciscus Scripsit Anno Domini 1447.</colophon>
Example
<colophon>Explicit expliceat/scriptor ludere eat.</colophon>
Example
<colophon>Explicit venenum viciorum domini illius, qui comparavit Anno domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo sancte Marthe virginis gloriose. Laus tibi criste quia finitur libellus iste.</colophon>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element colophon { att.global.attributes, macro.phraseSeq }

Appendix A.1.53 <condition>

<condition> contains a description of the physical condition of the manuscript. [10.7.1.5. Condition]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
Example
<condition>  <p>There are lacunae in three places in this    manuscript. After 14v two    leaves has been cut out and narrow strips leaves remains in the spine. After    68v one gathering is missing and after 101v at least one gathering of 8 leaves    has been lost. </p>  <p>Several leaves are damaged with tears or holes or have a    irregular shape. Some of the damages do not allow the lines to be of full    length and they are apparently older than the script. There are tears on fol.    2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,    37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,    74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98    the corner has been torn off. Several leaves are in a bad condition due to    moist and wear, and have become dark, bleached or    wrinkled. </p>  <p>The script has been    touched up in the 17th century with black ink. The touching up on the following    fols. was done by  <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,    6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An    AM-note says according to the lawman  <name>Sigurður Björnsson</name> that the rest of the    touching up was done by himself and another lawman  <name>Sigurður Jónsson</name>.  <name>Sigurður Björnsson</name> did the touching up    on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.  <name>Sigurður Jónsson</name> did the rest of the    touching up in the section 36r-59r containing  <title>Bretasögur</title>  </p> </condition>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element condition { att.global.attributes, macro.specialPara }

Appendix A.1.54 <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
Member of
Contained by
May contain
ExampleIf 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?
ExampleIt 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.55 <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.[Default]
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
linking: ab
NoteMay be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.4. Simple Editorial Changes.
Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correction
{
   att.global.attributes,
   att.declarable.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   model.pLike+
}

Appendix A.1.56 <correspAction>

<correspAction> contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence [2.4.6. Correspondence Description]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
typedescribes the nature of the action.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message
received
information concerning the receipt of a message
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
Contained by
header: correspDesc
May contain
header: idno
linking: ab
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type
   {
      "sent" | "received" | "transmitted" | "redirected" | "forwarded"
   }?,
   ( model.correspActionPart+ | model.pLike+ )
}

Appendix A.1.57 <correspContext>

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: correspDesc
May contain
core: note p ptr ref
linking: ab
Example
<correspContext>  <ptr type="nextsubtype="toAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>  <ptr type="prevsubtype="fromAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/> </correspContext>
Example
<correspContext>  <ref type="prev"   target="http://weber-gesamtausgabe.de/A040962"> Previous letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1816-12-30">December 30, 1816</date>  </ref>  <ref type="next"   target="http://weber-gesamtausgabe.de/A041003"> Next letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1817-01-05">January 5, 1817</date>  </ref> </correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correspContext { att.global.attributes, model.correspContextPart+ }

Appendix A.1.58 <correspDesc>

<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Moduleheader
AttributesAttributes att.declarable (@default) att.canonical (@key, @ref) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
header: profileDesc
May contain
core: note p
linking: ab
Example
<correspDesc>  <correspAction type="sent">   <persName>Carl Maria von Weber</persName>   <settlement>Dresden</settlement>   <date when="1817-06-23">23 June 1817</date>  </correspAction>  <correspAction type="received">   <persName>Caroline Brandt</persName>   <settlement>Prag</settlement>  </correspAction>  <correspContext>   <ref type="prev"    target="http://www.weber-gesamtausgabe.de/A041209">Previous letter of   <persName>Carl Maria von Weber</persName>      to <persName>Caroline Brandt</persName>:   <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>   </ref>   <ref type="next"    target="http://www.weber-gesamtausgabe.de/A041217">Next letter of   <persName>Carl Maria von Weber</persName> to   <persName>Caroline Brandt</persName>:   <date when="1817-06-27">June 27, 1817</date>   </ref>  </correspContext> </correspDesc>
Content model
<content>
 <alternate>
  <classRef key="model.correspDescPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspDesc
{
   att.declarable.attributes,
   att.canonical.attributes,
   att.global.attributes,
   att.typed.attributes,
   ( model.correspDescPart+ | model.pLike+ )
}

Appendix A.1.59 <creation>

<creation> contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
Contained by
header: profileDesc
May contain
NoteThe <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication.
Example
<creation>  <date>Before 1987</date> </creation>
Example
<creation>  <date when="1988-07-10">10 July 1988</date> </creation>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <elementRef key="listChange"/>
 </alternate>
</content>
    
Schema Declaration
element creation
{
   att.global.attributes,
   att.datable.attributes,
   ( text | model.limitedPhrase | listChange )*
}

Appendix A.1.60 <custEvent>

<custEvent> (custodial event) describes a single event during the custodial history of a manuscript. [10.9.1.2. Availability and Custodial History]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.typed (@type)
Contained by
msdescription: custodialHist
May contain
Example
<custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date> </custEvent>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element custEvent
{
   att.global.attributes,
   att.datable.attributes,
   att.typed.attributes,
   macro.specialPara
}

Appendix A.1.61 <custodialHist>

<custodialHist> (custodial history) contains a description of a manuscript's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: adminInfo
May contain
core: p
linking: ab
msdescription: custEvent
Example
<custodialHist>  <custEvent type="conservation"   notBefore="1961-03notAfter="1963-02">Conserved between March 1961 and February 1963 at    Birgitte Dalls Konserveringsværksted.</custEvent>  <custEvent type="photography"   notBefore="1988-05-01notAfter="1988-05-30">Photographed in    May 1988 by AMI/FA.</custEvent>  <custEvent type="transfer-dispatch"   notBefore="1989-11-13notAfter="1989-11-13">Dispatched to Iceland    13 November 1989.</custEvent> </custodialHist>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="custEvent" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }

Appendix A.1.62 <damage>

<damage> contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.damaged (@agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.written (@hand))
Member of
Contained by
May contain
NoteSince damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.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.
Example
<l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l> <l>Moves <damage agent="watergroup="1">   <supplied>on: nor all your</supplied>  </damage> Piety nor Wit</l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element damage
{
   att.global.attributes,
   att.typed.attributes,
   att.damaged.attributes,
   macro.paraContent
}

Appendix A.1.63 <damageSpan>

<damageSpan> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.damaged (@agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.written (@hand)) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
NoteBoth the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor> element may be used for this purpose.The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 11.3.3.1. Damage, Illegibility, and Supplied Text and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.
Example
<p>Paragraph partially damaged. This is the undamaged portion <damageSpan spanTo="#a34"/>and this the damaged portion of the paragraph.</p> <p>This paragraph is entirely damaged.</p> <p>Paragraph partially damaged; in the middle of this paragraph the damage ends and the anchor point marks the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p>
Schematron
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Content model
<content>
</content>
    
Schema Declaration
element damageSpan
{
   att.global.attributes,
   att.damaged.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}

Appendix A.1.64 <date>

<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type)
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.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}

Appendix A.1.65 <dateline>

<dateline> contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: lg list
textstructure: closer div front group opener
May contain
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
  <elementRef key="docDate"/>
 </alternate>
</content>
    
Schema Declaration
element dateline
{
   att.global.attributes,
   ( text | model.gLike | model.phrase | model.global | docDate )*
}

Appendix A.1.66 <decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements. [10.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
linking: ab
msdescription: decoNote summary
Example
<decoDesc>  <p>The start of each book of the Bible with a 10-line historiated    illuminated initial; prefaces decorated with 6-line blue initials with red    penwork flourishing; chapters marked by 3-line plain red initials; verses    with 1-line initials, alternately blue or red.</p> </decoDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="decoNote" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element decoDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, decoNote+ ) )
}

Appendix A.1.67 <decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
Member of
Contained by
May contain
Example
<decoDesc>  <decoNote type="initial">   <p>The start of each book of the Bible with      a 10-line historiated illuminated initial;      prefaces decorated with 6-line blue initials      with red penwork flourishing; chapters marked by      3-line plain red initials; verses with 1-line initials,      alternately blue or red.</p>  </decoNote> </decoDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element decoNote
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}

Appendix A.1.68 <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore
AttributesAttributes att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.typed (@type) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.responsibility (@cert, @resp)
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
dot-above
one dot has been placed above the letter to be deleted.
dot-above-dot-under
one dot has been placed above and another one underneath the letter to be deleted.
dots-above
two or more dots have been place above the word to be deleted.
strikeout
a line has been written over the letters or words to be deleted.
Member of
Contained by
May contain
NoteThis element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.
Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21. Certainty, Precision, and Responsibility).
There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.
Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegiblequantity="5"   unit="character"/> </del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   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.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.transcriptional.attributes,
   att.typed.attributes,
   attribute rend
   {
      list
      {
         ( "dot-above" | "dot-above-dot-under" | "dots-above" | "strikeout" )+
      }
   },
   macro.paraContent
}

Appendix A.1.69 <delSpan>

<delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. Additions and Deletions]
Moduletranscr
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.typed (@type) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
NoteBoth the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan> element, the ending by the target of the spanTo attribute.The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <delSpan> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the <delSpan> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.
The <delSpan> tag should not be used for deletions made by editors or encoders. In these cases, either the <corr> tag or the <gap> tag should be used.
Example
<p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p>
Schematron
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Content model
<content>
</content>
    
Schema Declaration
element delSpan
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   att.spanning.attributes,
   empty
}

Appendix A.1.70 <depth>

<depth> contains a measurement measured across the spine of a book or codex, or (for other text-bearing objects) perpendicular to the measurement given by the ‘width’ element. [10.3.4. Dimensions]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain
gaiji: g
NoteIf used to specify the width of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘width’ axis.
Example
<depth unit="inquantity="4"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element depth { att.global.attributes, att.dimensions.attributes, macro.xtext }

Appendix A.1.71 <desc>

<desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.1. Description of Components]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.translatable (@versionDate) att.typed (@type)
Member of
Contained by
May contain
NoteTEI convention requires that this be expressed as a finite clause, begining with an active verb.
Example
<desc>contains a brief description of the purpose and application for an element, attribute, attribute value, class, or entity.</desc>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   att.global.attributes,
   att.translatable.attributes,
   att.typed.attributes,
   macro.limitedContent
}

Appendix A.1.72 <dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.typed (@type) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain
gaiji: g
NoteThe specific elements <width>, <height>, and <depth> should be used in preference to this generic element wherever appropriate.
Example
<dim type="circumferenceextent="4.67 in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element dim
{
   att.global.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.xtext
}

Appendix A.1.73 <dimensions>

<dimensions> contains a dimensional specification. [10.3.4. Dimensions]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
typeindicates which aspect of the object is being measured.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
leaves
dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)
ruled
dimensions relate to the area of a leaf which has been ruled in preparation for writing.
pricked
dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable).
written
dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.
miniatures
dimensions relate to the miniatures within the manuscript
binding
dimensions relate to the binding in which the codex or manuscript is contained
box
dimensions relate to the box or other container in which the manuscript is stored.
Member of
Contained by
May contain
msdescription: depth dim height width
NoteContains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.
Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
ExampleThis element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="reliefunit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
ExampleWhen simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height unit="cmscope="most"   quantity="90"/>  <width unit="cmscope="mostquantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
Schematron
<s:report test="count(tei:width)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only </s:report>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="dim"/>
  <classRef key="model.dimLike"/>
 </alternate>
</content>
    
Schema Declaration
element dimensions
{
   att.global.attributes,
   att.dimensions.attributes,
   attribute type { text }?,
   ( dim | model.dimLike )*
}

Appendix A.1.74 <distributor>

<distributor> supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Example