https://github.com/TEIC/TEI
Tip revision: 347c64fac3fa1a64ade0d8d1842813d4b8f7acec authored by Hugh Cayless on 12 May 2017, 16:57:59 UTC
Updates.
Updates.
Tip revision: 347c64f
HD.html
<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><!--THIS FILE IS GENERATED FROM AN XML MASTER. DO NOT EDIT (4)--><title>2 The TEI Header - The TEI Guidelines</title><meta property="Language" content="en" /><meta property="DC.Title" content="2 The TEI Header - The TEI Guidelines" /><meta property="DC.Language" content="SCHEME=iso639 en" /><meta property="DC.Creator.Address" content="tei@oucs.ox.ac.uk" /><meta charset="utf-8" /><link href="guidelines.css" rel="stylesheet" type="text/css" /><link href="odd.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" media="print" type="text/css" href="guidelines-print.css" /><script type="text/javascript" src="jquery-1.2.6.min.js"></script><script type="text/javascript" src="columnlist.js"></script><script type="text/javascript" src="popupFootnotes.js"></script><script type="text/javascript">
$(function() {
$('ul.attrefs-class').columnizeList({cols:3,width:30,unit:'%'});
$('ul.attrefs-element').columnizeList({cols:3,width:30,unit:'%'});
$(".displayRelaxButton").click(function() {
$(this).parent().find('.RNG_XML').toggle();
$(this).parent().find('.RNG_Compact').toggle();
});
$(".tocTree .showhide").click(function() {
$(this).find(".tocShow,.tocHide").toggle();
$(this).parent().find("ul.continuedtoc").toggle();
});
})
</script><script type="text/javascript"><!--
var displayXML=0;
states=new Array()
states[0]="element-a"
states[1]="element-b"
states[2]="element-c"
states[3]="element-d"
states[4]="element-e"
states[5]="element-f"
states[6]="element-g"
states[7]="element-h"
states[8]="element-i"
states[9]="element-j"
states[10]="element-k"
states[11]="element-l"
states[12]="element-m"
states[13]="element-n"
states[14]="element-o"
states[15]="element-p"
states[16]="element-q"
states[17]="element-r"
states[18]="element-s"
states[19]="element-t"
states[20]="element-u"
states[21]="element-v"
states[22]="element-w"
states[23]="element-x"
states[24]="element-y"
states[25]="element-z"
function startUp() {
}
function hideallExcept(elm) {
for (var i = 0; i < states.length; i++) {
var layer;
if (layer = document.getElementById(states[i]) ) {
if (states[i] != elm) {
layer.style.display = "none";
}
else {
layer.style.display = "block";
}
}
}
var mod;
if ( mod = document.getElementById('byMod') ) {
mod.style.display = "none";
}
}
function showall() {
for (var i = 0; i < states.length; i++) {
var layer;
if (layer = document.getElementById(states[i]) ) {
layer.style.display = "block";
}
}
}
function showByMod() {
hideallExcept('');
var mod;
if (mod = document.getElementById('byMod') ) {
mod.style.display = "block";
}
}
--></script></head><body><div id="container"><div id="banner"><img src="Images/banner.jpg" alt="Text Encoding Initiative logo and banner" /></div></div><div class="mainhead"><h1>P5:
Guidelines for Electronic Text Encoding and Interchange</h1><p>Version 3.1.1a. Last updated on
10th May 2017, revision bd8dda3</p></div><div id="onecol" class="main-content"><h2><span class="headingNumber">2 </span>The TEI Header</h2><div class="div1" id="HD"><div class="miniTOC miniTOC_left"><p><span class="subtochead">Table of contents</span></p><div class="subtoc"><ul class="subtoc"><li class="subtoc"><a class="subtoc" href="HD.html#HD1" title="Organization of the TEI Header">2.1 Organization of the TEI Header</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD2" title="The File Description">2.2 The File Description</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD5" title="The Encoding Description">2.3 The Encoding Description</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD4" title="The Profile Description">2.4 The Profile Description</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD9" title="NonTEI Metadata">2.5 Non-TEI Metadata</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD6" title="The Revision Description">2.6 The Revision Description</a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD7" title="Minimal and Recommended Headers">2.7 Minimal and Recommended Headers </a></li><li class="subtoc"><a class="subtoc" href="HD.html#HD8" title="Note for Library Cataloguers">2.8 Note for Library Cataloguers</a></li><li class="subtoc"><a class="subtoc" href="HD.html#index-body.1_div.2_div.9">2.9 The TEI Header Module</a></li></ul></div><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html"><span class="headingNumber">1 </span>The TEI Infrastructure</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="CO.html"><span class="headingNumber">3 </span>Elements Available in All TEI Documents</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><p>This chapter addresses the problems of describing an encoded work so that the text itself, its source, its encoding, and its revisions are all thoroughly documented. Such documentation is equally necessary for scholars using the texts, for software processing them, and for cataloguers in libraries and archives. Together these descriptions and declarations provide an electronic analogue to the title page attached to a printed work. They also constitute an equivalent for the content of the code books or introductory manuals customarily accompanying electronic data sets.</p><p>Every TEI-conformant text must carry such a set of descriptions, prefixed to it and encoded as described in this chapter. The set is known as the <span class="term">TEI header</span>, tagged <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a>, and has five major parts: </p><ol class="numbered"><li class="item">a <span class="term">file description</span>, tagged <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a>, containing a full bibliographical description of the computer file itself, from which a user of the text could derive a proper bibliographic citation, or which a librarian or archivist could use in creating a catalogue entry recording its presence within a library or archive. The term <span class="term">computer file</span> here is to be understood as referring to the whole entity or document described by the header, even when this is stored in several distinct operating system files. The file description also includes information about the source or sources from which the electronic document was derived. The TEI elements used to encode the file description are described in section <a class="link_ptr" href="HD.html#HD2" title="The File Description"><span class="headingNumber">2.2 </span>The File Description</a> below.</li><li class="item">an <span class="term">encoding description</span>, tagged <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a>, which describes the relationship between an electronic text and its source or sources. It allows for detailed description of whether (or how) the text was normalized during transcription, how the encoder resolved ambiguities in the source, what levels of encoding or analysis were applied, and similar matters. The TEI elements used to encode the encoding description are described in section <a class="link_ptr" href="HD.html#HD5" title="The Encoding Description"><span class="headingNumber">2.3 </span>The Encoding Description</a> below.</li><li class="item">a <span class="term">text profile</span>, tagged <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a>, containing classificatory and contextual information about the text, such as its subject matter, the situation in which it was produced, the individuals described by or participating in producing it, and so forth. Such a text profile is of particular use in highly structured composite texts such as corpora or language collections, where it is often highly desirable to enforce a controlled descriptive vocabulary or to perform retrievals from a body of text in terms of text type or origin. The text profile may however be of use in any form of automatic text processing. The TEI elements used to encode the profile description are described in section <a class="link_ptr" href="HD.html#HD4" title="The Profile Description"><span class="headingNumber">2.4 </span>The Profile Description</a> below.</li><li class="item">a container element, tagged <a class="gi" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a>, which allows easy inclusion of metadata from non-TEI schemes (i.e., other than elements in the TEI namespace). For example, the MARC record for the encoded document might be included using MARCXML or MODS. A simple set of metadata for harvesting might be included encoded in Dublin Core.</li><li class="item">a <span class="term">revision history</span>, tagged <a class="gi" title="(revision description) summarizes the revision history for a file." href="ref-revisionDesc.html">revisionDesc</a>, which allows the encoder to provide a history of changes made during the development of the electronic text. The revision history is important for <span class="term">version control</span> and for resolving questions about the history of a file. The TEI elements used to encode the revision description are described in section <a class="link_ptr" href="HD.html#HD6" title="The Revision Description"><span class="headingNumber">2.6 </span>The Revision Description</a> below.</li></ol><p>A TEI header can be a very large and complex object, or it may be a very simple one. Some application areas (for example, the construction of language corpora and the transcription of spoken texts) may require more specialized and detailed information than others. The present proposals therefore define both a <span class="term">core</span> set of elements (all of which may be used without formality in any TEI header) and some additional elements which become available within the header as the result of including additional specialized modules within the schema. When the module for language corpora (described in chapter <a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a>) is in use, for example, several additional elements are available, as further detailed in that chapter.</p><p>The next section of the present chapter briefly introduces the overall structure of the header and the kinds of data it may contain. This is followed by a detailed description of all the constituent elements which may be used in the core header. Section <a class="link_ptr" href="HD.html#HD7" title="Minimal and Recommended Headers"><span class="headingNumber">2.7 </span>Minimal and Recommended Headers </a>, at the end of the present chapter, discusses the recommended content of a minimal TEI header and its relation to standard library cataloguing practices.</p><div class="div2" id="HD1"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD2"><span class="headingNumber">2.2 </span>The File Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD1" title="link to this section "><span class="invisible">TEI: Organization of the TEI Header</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.1 </span><span class="head">Organization of the TEI Header</span></h3><div class="div3" id="HD11"><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD11" title="link to this section "><span class="invisible">TEI: The TEI Header and Its Components</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.1.1 </span><span class="head">The TEI Header and Its Components</span></h4><p>The <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> element should be clearly distinguished from the <span class="term">front matter</span> of the text itself (for which see section <a class="link_ptr" href="DS.html#DSFRONT" title="Front Matter"><span class="headingNumber">4.5 </span>Front Matter</a>). A composite text, such as a corpus or collection, may contain several headers, as further discussed below. In the general case, however, a TEI-conformant text will contain a single <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> element, followed by a single <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a> or <a class="gi" title="contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text." href="ref-facsimile.html">facsimile</a> element, or both.</p><p>The header element has the following description: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-teiHeader.html">teiHeader</a></span> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources.</li></ul><p>As discussed above, the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> element has five principal components: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-fileDesc.html">fileDesc</a></span> (file description) contains a full bibliographic description of an electronic file.</li><li><span class="specList-elementSpec"><a href="ref-encodingDesc.html">encodingDesc</a></span> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.</li><li><span class="specList-elementSpec"><a href="ref-profileDesc.html">profileDesc</a></span> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting.</li><li><span class="specList-elementSpec"><a href="ref-xenoData.html">xenoData</a></span> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed.</li><li><span class="specList-elementSpec"><a href="ref-revisionDesc.html">revisionDesc</a></span> (revision description) summarizes the revision history for a file.</li></ul><div class="p">Of these, only the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element is required in all TEI headers; the others are optional. That is, only one of the five components of the TEI header (the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a>) is mandatory, and it also has some mandatory components, as further discussed in <a class="link_ptr" href="HD.html#HD2" title="The File Description"><span class="headingNumber">2.2 </span>The File Description</a> below. The smallest possible valid TEI Header thus looks like this: <div id="index-egXML-d52e18801" class="pre egXML_valid"><span class="element"><teiHeader></span><br /> <span class="element"><fileDesc></span><br /> <span class="element"><titleStmt></span><br /> <span class="element"><title></span><br /><span class="comment"><!-- title of the resource --></span><br /> <span class="element"></title></span><br /> <span class="element"></titleStmt></span><br /> <span class="element"><publicationStmt></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- Information about distribution of the resource --></span><br /> <span class="element"></p></span><br /> <span class="element"></publicationStmt></span><br /> <span class="element"><sourceDesc></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- Information about source from which the resource derives --></span><br /> <span class="element"></p></span><br /> <span class="element"></sourceDesc></span><br /> <span class="element"></fileDesc></span><br /><span class="element"></teiHeader></span></div></div><div class="p">The content of the elements making up a TEI header may be given in any language, not necessarily that of the text to which the header applies, and not necessarily English. As elsewhere, the <span class="att">xml:lang</span> attribute should be used at an appropriate level to specify the language. For example, in the following schematic example, an English text has been given a French header: <div id="index-egXML-d52e18818" class="pre egXML_feasible"><span class="element"><TEI xmlns="http://www.tei-c.org/ns/1.0"></span><br /> <span class="element"><teiHeader <span class="attribute">xml:lang</span>="<span class="attributevalue">fr</span>"></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></teiHeader></span><br /> <span class="element"><text <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></text></span><br /><span class="element"></TEI></span></div></div><div class="p">In the case of language corpora or collections, it may be desirable to record header information either at the level of the individual components in the corpus or collection, or at the level of the corpus or collection itself (more details concerning the tagging of composite texts are given in section <a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a>, which should be read in conjunction with the current chapter). A corpus may thus take the form: <div id="index-egXML-d52e18829" class="pre egXML_feasible"><span class="element"><teiCorpus xmlns="http://www.tei-c.org/ns/1.0"></span><br /> <span class="element"><teiHeader></span><br /><span class="comment"><!-- corpus-level metadata here --></span><br /> <span class="element"></teiHeader></span><br /> <span class="element"><TEI></span><br /> <span class="element"><teiHeader></span><br /><span class="comment"><!-- metadata specific to this text here --></span><br /> <span class="element"></teiHeader></span><br /> <span class="element"><text></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></text></span><br /> <span class="element"></TEI></span><br /> <span class="element"><TEI></span><br /> <span class="element"><teiHeader></span><br /><span class="comment"><!-- metadata specific to this text here --></span><br /> <span class="element"></teiHeader></span><br /> <span class="element"><text></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></text></span><br /> <span class="element"></TEI></span><br /><span class="element"></teiCorpus></span></div> </div></div><div class="div3" id="HD12"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD11"><span class="headingNumber">2.1.1 </span>The TEI Header and Its Components</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#index-body.1_div.2_div.1_div.3"><span class="headingNumber">2.1.3 </span>Model Classes in the TEI Header</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD12" title="link to this section "><span class="invisible">TEI: Types of Content in the TEI Header</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.1.2 </span><span class="head">Types of Content in the TEI Header</span></h4><p>The elements occurring within the TEI header may contain several types of content; the following list indicates how these types of content are described in the following sections: </p><dl><dt><span>free prose</span></dt><dd>Most elements contain simple running prose at some level. Many elements may contain either prose (possibly organized into paragraphs) or more specific elements, which themselves contain prose. In this chapter's descriptions of element content, the phrase <span class="mentioned">prose description</span> should be understood to imply a series of paragraphs, each marked as a <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a> element. The word <span class="mentioned">phrase</span>, by contrast, should be understood to imply character data, interspersed as need be with phrase-level elements, but not organized into paragraphs. For more information on paragraphs, highlighted phrases, lists, etc., see section <a class="link_ptr" href="CO.html#COPA" title="Paragraphs"><span class="headingNumber">3.1 </span>Paragraphs</a>.</dd><dt><span>grouping elements</span></dt><dd>Elements whose names end with the suffix <span class="mentioned">Stmt</span> (e.g. <a class="gi" title="(edition statement) groups information relating to one edition of a text." href="ref-editionStmt.html">editionStmt</a>, <a class="gi" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a>) and the <a class="gi" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a> element enclose a group of specialized elements recording some structured information. In the case of the bibliographic elements, the suffix <span class="mentioned">Stmt</span> is used in names of elements corresponding to the ‘areas’ of the International Standard Bibliographic Description.<span id="Note42_return"><a class="notelink" title="For more information on this highly influential family of standards, first proposed in 1969 by the International Federation of Library Associations, s…" href="#Note42"><sup>5</sup></a></span> In the case of the <a class="gi" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a> element, the specialized elements are not TEI elements, but rather come from some other metadata scheme. In most cases grouping elements may contain prose descriptions as an alternative to the set of specialized elements, thus allowing the encoder to choose whether or not the information concerned should be presented in a structured form or in prose.</dd><dt><span>declarations</span></dt><dd>Elements whose names end with the suffix <span class="mentioned">Decl</span> (e.g. <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a>, <a class="gi" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a>) enclose information about specific encoding practices applied in the electronic text; often these practices are described in coded form. Typically, such information takes the form of a series of declarations, identifying a code with some more complex structure or description. A declaration which applies to more than one text or division of a text need not be repeated in the header of each such text or subdivision. Instead, the <span class="att">decls</span> attribute of each text (or subdivision of the text) to which the declaration applies may be used to supply a cross-reference to it, as further described in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a>.</dd><dt><span>descriptions</span></dt><dd>Elements whose names end with the suffix <span class="mentioned">Desc</span> (e.g. <a class="gi" title="(setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata." href="ref-settingDesc.html">settingDesc</a>, <a class="gi" title="(project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected." href="ref-projectDesc.html">projectDesc</a>) contain a prose description, possibly, but not necessarily, organized under some specific headings by suggested sub-elements.</dd></dl></div><div class="teidiv2" id="index-body.1_div.2_div.1_div.3"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD12"><span class="headingNumber">2.1.2 </span>Types of Content in the TEI Header</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#index-body.1_div.2_div.1_div.3" title="link to this section "><span class="invisible">TEI: Model Classes in the TEI Header</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.1.3 </span><span class="head">Model Classes in the TEI Header</span></h4><p>The TEI header provides a very rich collection of metadata categories, but makes no claim to be exhaustive. It is certainly the case that individual projects may wish to record specialized metadata which either does not fit within one of the predefined categories identified by the TEI header or requires a more specialized element structure than is proposed here. To overcome this problem, the encoder may elect to define additional elements using the customization methods discussed in <a class="link_ptr" href="USE.html#MD" title="Customization"><span class="headingNumber">23.3 </span>Customization</a>. The TEI class system makes such customizations simpler to effect and easier to use in interchange.</p><p>These classes are specific to parts of the header: </p><ul class="specList"><li><span class="specList-classSpec"><a href="ref-model.applicationLike.html">model.applicationLike</a></span> groups elements used to record application-specific information about a document in its header.<table class="elementList"><tr><td class="odd_label"><a href="ref-application.html">application</a></td><td class="odd_value">provides information about an application which has acted upon the document.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.availabilityPart.html">model.availabilityPart</a></span> groups elements such as licences and paragraphs of text which may appear as part of an availability statement<table class="elementList"><tr><td class="odd_label"><a href="ref-licence.html">licence</a></td><td class="odd_value">contains information about a licence or other legal agreement applicable to the text.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.catDescPart.html">model.catDescPart</a></span> groups component elements of the TEI header Category Description.<table class="elementList"><tr><td class="odd_label"><a href="ref-textDesc.html">textDesc</a></td><td class="odd_value">(text description) provides a description of a text in terms of its situational parameters.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.editorialDeclPart.html">model.editorialDeclPart</a></span> groups elements which may be used inside <a class="gi" title="(editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text." href="ref-editorialDecl.html">editorialDecl</a> and appear multiple times.<table class="elementList"><tr><td class="odd_label"><a href="ref-correction.html">correction</a></td><td class="odd_value">(correction principles) states how and under what circumstances corrections have been made in the text.</td></tr><tr><td class="odd_label"><a href="ref-hyphenation.html">hyphenation</a></td><td class="odd_value">summarizes the way in which hyphenation in a source text has been treated in an encoded version of it.</td></tr><tr><td class="odd_label"><a href="ref-interpretation.html">interpretation</a></td><td class="odd_value">describes the scope of any analytic or interpretive information added to the text in addition to the transcription.</td></tr><tr><td class="odd_label"><a href="ref-normalization.html">normalization</a></td><td class="odd_value">indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form.</td></tr><tr><td class="odd_label"><a href="ref-punctuation.html">punctuation</a></td><td class="odd_value">specifies editorial practice adopted with respect to punctuation marks in the original.</td></tr><tr><td class="odd_label"><a href="ref-quotation.html">quotation</a></td><td class="odd_value">specifies editorial practice adopted with respect to quotation marks in the original.</td></tr><tr><td class="odd_label"><a href="ref-segmentation.html">segmentation</a></td><td class="odd_value">describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.</td></tr><tr><td class="odd_label"><a href="ref-stdVals.html">stdVals</a></td><td class="odd_value">(standard values) specifies the format used when standardized date or number values are supplied.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.encodingDescPart.html">model.encodingDescPart</a></span> groups elements which may be used inside <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> and appear multiple times.<table class="elementList"><tr><td class="odd_label"><a href="ref-appInfo.html">appInfo</a></td><td class="odd_value">(application information) records information about an application which has edited the TEI file.</td></tr><tr><td class="odd_label"><a href="ref-charDecl.html">charDecl</a></td><td class="odd_value">(character declarations) provides information about nonstandard characters and glyphs.</td></tr><tr><td class="odd_label"><a href="ref-classDecl.html">classDecl</a></td><td class="odd_value">(classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.</td></tr><tr><td class="odd_label"><a href="ref-editorialDecl.html">editorialDecl</a></td><td class="odd_value">(editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.</td></tr><tr><td class="odd_label"><a href="ref-fsdDecl.html">fsdDecl</a></td><td class="odd_value">(feature system declaration) provides a feature system declaration comprising one or more feature structure declarations or feature structure declaration links.</td></tr><tr><td class="odd_label"><a href="ref-geoDecl.html">geoDecl</a></td><td class="odd_value">(geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <a class="gi" title="(geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation." href="ref-geo.html">geo</a> element elsewhere within the document.</td></tr><tr><td class="odd_label"><a href="ref-listPrefixDef.html">listPrefixDef</a></td><td class="odd_value">(list of prefix definitions) contains a list of definitions of prefixing schemes used in <span class="ident-datatype">data.pointer</span> values, showing how abbreviated URIs using each scheme may be expanded into full URIs.</td></tr><tr><td class="odd_label"><a href="ref-metDecl.html">metDecl</a></td><td class="odd_value">(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a <span class="att">met</span>, <span class="att">real</span>, or <span class="att">rhyme</span> attribute on any structural element of a metrical text (e.g. <a class="gi" title="(line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc." href="ref-lg.html">lg</a>, <a class="gi" title="(verse line) contains a single, possibly incomplete, line of verse." href="ref-l.html">l</a>, or <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a>).</td></tr><tr><td class="odd_label"><a href="ref-projectDesc.html">projectDesc</a></td><td class="odd_value">(project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.</td></tr><tr><td class="odd_label"><a href="ref-refsDecl.html">refsDecl</a></td><td class="odd_value">(references declaration) specifies how canonical references are constructed for this text.</td></tr><tr><td class="odd_label"><a href="ref-samplingDecl.html">samplingDecl</a></td><td class="odd_value">(sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.</td></tr><tr><td class="odd_label"><a href="ref-schemaRef.html">schemaRef</a></td><td class="odd_value">(schema reference) describes or points to a related customization or schema file</td></tr><tr><td class="odd_label"><a href="ref-schemaSpec.html">schemaSpec</a></td><td class="odd_value">(schema specification) generates a TEI-conformant schema and documentation for it.</td></tr><tr><td class="odd_label"><a href="ref-styleDefDecl.html">styleDefDecl</a></td><td class="odd_value">(style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied.</td></tr><tr><td class="odd_label"><a href="ref-tagsDecl.html">tagsDecl</a></td><td class="odd_value">(tagging declaration) provides detailed information about the tagging applied to a document.</td></tr><tr><td class="odd_label"><a href="ref-transcriptionDesc.html">transcriptionDesc</a></td><td class="odd_value">describes the set of transcription conventions used, particularly for spoken material.</td></tr><tr><td class="odd_label"><a href="ref-variantEncoding.html">variantEncoding</a></td><td class="odd_value">declares the method used to encode text-critical variants.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.profileDescPart.html">model.profileDescPart</a></span> groups elements which may be used inside <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> and appear multiple times.<table class="elementList"><tr><td class="odd_label"><a href="ref-abstract.html">abstract</a></td><td class="odd_value">contains a summary or formal abstract prefixed to an existing source document by the encoder.</td></tr><tr><td class="odd_label"><a href="ref-calendarDesc.html">calendarDesc</a></td><td class="odd_value">(calendar description) contains a description of the calendar system used in any dating expression found in the text.</td></tr><tr><td class="odd_label"><a href="ref-correspDesc.html">correspDesc</a></td><td class="odd_value">(correspondence
description) contains a description of the actions related to one act of correspondence.</td></tr><tr><td class="odd_label"><a href="ref-creation.html">creation</a></td><td class="odd_value">contains information about the creation of a text.</td></tr><tr><td class="odd_label"><a href="ref-handNotes.html">handNotes</a></td><td class="odd_value">contains one or more <a class="gi" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> elements documenting the different hands identified within the source texts.</td></tr><tr><td class="odd_label"><a href="ref-langUsage.html">langUsage</a></td><td class="odd_value">(language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.</td></tr><tr><td class="odd_label"><a href="ref-listTranspose.html">listTranspose</a></td><td class="odd_value">supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks.</td></tr><tr><td class="odd_label"><a href="ref-particDesc.html">particDesc</a></td><td class="odd_value">(participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata.</td></tr><tr><td class="odd_label"><a href="ref-settingDesc.html">settingDesc</a></td><td class="odd_value">(setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata.</td></tr><tr><td class="odd_label"><a href="ref-textClass.html">textClass</a></td><td class="odd_value">(text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.</td></tr><tr><td class="odd_label"><a href="ref-textDesc.html">textDesc</a></td><td class="odd_value">(text description) provides a description of a text in terms of its situational parameters.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.teiHeaderPart.html">model.teiHeaderPart</a></span> groups high level elements which may appear more than once in a TEI header.<table class="elementList"><tr><td class="odd_label"><a href="ref-encodingDesc.html">encodingDesc</a></td><td class="odd_value">(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.</td></tr><tr><td class="odd_label"><a href="ref-profileDesc.html">profileDesc</a></td><td class="odd_value">(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting.</td></tr><tr><td class="odd_label"><a href="ref-xenoData.html">xenoData</a></td><td class="odd_value">(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.sourceDescPart.html">model.sourceDescPart</a></span> groups elements which may be used inside <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> and appear multiple times.<table class="elementList"><tr><td class="odd_label"><a href="ref-recordingStmt.html">recordingStmt</a></td><td class="odd_value">(recording statement) describes a set of recordings used as the basis for transcription of a spoken text.</td></tr><tr><td class="odd_label"><a href="ref-scriptStmt.html">scriptStmt</a></td><td class="odd_value">(script statement) contains a citation giving details of the script used for a spoken text.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.textDescPart.html">model.textDescPart</a></span> groups elements used to categorize a text for example in terms of its situational parameters.<table class="elementList"><tr><td class="odd_label"><a href="ref-channel.html">channel</a></td><td class="odd_value">(primary channel) describes the medium or channel by which a text is delivered or experienced. For a written text, this might be print, manuscript, email, etc.; for a spoken one, radio, telephone, face-to-face, etc.</td></tr><tr><td class="odd_label"><a href="ref-constitution.html">constitution</a></td><td class="odd_value">describes the internal composition of a text or text sample, for example as fragmentary, complete, etc.</td></tr><tr><td class="odd_label"><a href="ref-derivation.html">derivation</a></td><td class="odd_value">describes the nature and extent of originality of this text.</td></tr><tr><td class="odd_label"><a href="ref-domain.html">domain</a></td><td class="odd_value">(domain of use) describes the most important social context in which the text was realized or for which it is intended, for example private vs. public, education, religion, etc.</td></tr><tr><td class="odd_label"><a href="ref-factuality.html">factuality</a></td><td class="odd_value">describes the extent to which the text may be regarded as imaginative or non-imaginative, that is, as describing a fictional or a non-fictional world.</td></tr><tr><td class="odd_label"><a href="ref-interaction.html">interaction</a></td><td class="odd_value">describes the extent, cardinality and nature of any interaction among those producing and experiencing the text, for example in the form of response or interjection, commentary, etc.</td></tr><tr><td class="odd_label"><a href="ref-preparedness.html">preparedness</a></td><td class="odd_value">describes the extent to which a text may be regarded as prepared or spontaneous.</td></tr></table></li></ul></div></div><div class="div2" id="HD2"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD1"><span class="headingNumber">2.1 </span>Organization of the TEI Header</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD5"><span class="headingNumber">2.3 </span>The Encoding Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD2" title="link to this section "><span class="invisible">TEI: The File Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2 </span><span class="head">The File Description</span></h3><p>This section describes the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element, which is the first component of the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> element.</p><p>The bibliographic description of a machine-readable or digital text resembles in structure that of a book, an article, or any other kind of textual object. The file description element of the TEI header has therefore been closely modelled on existing standards in library cataloguing; it should thus provide enough information to allow users to give standard bibliographic references to the electronic text, and to allow cataloguers to catalogue it. Bibliographic citations occurring elsewhere in the header, and also in the text itself, are derived from the same model (on bibliographic citations in general, see further section <a class="link_ptr" href="CO.html#COBI" title="Bibliographic Citations and References"><span class="headingNumber">3.11 </span>Bibliographic Citations and References</a>). See further section <a class="link_ptr" href="HD.html#HD8" title="Note for Library Cataloguers"><span class="headingNumber">2.8 </span>Note for Library Cataloguers</a>.</p><p>The bibliographic description of an electronic text should be supplied by the mandatory <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-fileDesc.html">fileDesc</a></span> (file description) contains a full bibliographic description of an electronic file.</li></ul><p>The <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element contains three mandatory elements and four optional elements, each of which is described in more detail in sections <a class="link_ptr" href="HD.html#HD21" title="The Title Statement"><span class="headingNumber">2.2.1 </span>The Title Statement</a> to <a class="link_ptr" href="HD.html#HD27" title="The Notes Statement"><span class="headingNumber">2.2.6 </span>The Notes Statement</a> below. These elements are listed below in the order in which they must be given within the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-titleStmt.html">titleStmt</a></span> (title statement) groups information about the title of a work and those responsible for its content.</li><li><span class="specList-elementSpec"><a href="ref-editionStmt.html">editionStmt</a></span> (edition statement) groups information relating to one edition of a text.</li><li><span class="specList-elementSpec"><a href="ref-extent.html">extent</a></span> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units.</li><li><span class="specList-elementSpec"><a href="ref-publicationStmt.html">publicationStmt</a></span> (publication statement) groups information concerning the publication or distribution of an electronic or other text.</li><li><span class="specList-elementSpec"><a href="ref-seriesStmt.html">seriesStmt</a></span> (series statement) groups information about the series, if any, to which a publication belongs.</li><li><span class="specList-elementSpec"><a href="ref-notesStmt.html">notesStmt</a></span> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description.</li><li><span class="specList-elementSpec"><a href="ref-sourceDesc.html">sourceDesc</a></span> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence.</li></ul><div class="p">A complete file description containing all possible sub-elements might look like this: <div id="index-egXML-d52e19244" class="pre egXML_valid"><span class="element"><teiHeader></span><br /> <span class="element"><fileDesc></span><br /> <span class="element"><titleStmt></span><br /> <span class="element"><title></span><br /><span class="comment"><!-- title of the resource --></span><br /> <span class="element"></title></span><br /> <span class="element"></titleStmt></span><br /> <span class="element"><editionStmt></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- information about the edition of the
resource --></span><br /> <span class="element"></p></span><br /> <span class="element"></editionStmt></span><br /> <span class="element"><extent></span><br /><span class="comment"><!-- description of the size of the resource --></span><br /> <span class="element"></extent></span><br /> <span class="element"><publicationStmt></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- information about the distribution
of the resource --></span><br /> <span class="element"></p></span><br /> <span class="element"></publicationStmt></span><br /> <span class="element"><seriesStmt></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- information about any series to which
the resource belongs --></span><br /> <span class="element"></p></span><br /> <span class="element"></seriesStmt></span><br /> <span class="element"><notesStmt></span><br /> <span class="element"><note></span><br /><span class="comment"><!-- notes on other aspects of the resource --></span><br /> <span class="element"></note></span><br /> <span class="element"></notesStmt></span><br /> <span class="element"><sourceDesc></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- information about the source from which
the resource was derived --></span><br /> <span class="element"></p></span><br /> <span class="element"></sourceDesc></span><br /> <span class="element"></fileDesc></span><br /><span class="element"></teiHeader></span></div> Of these elements, only the <a class="gi" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a>, <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a>, and <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> are required; the others may be omitted unless considered useful.</div><div class="div3" id="HD21"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD22"><span class="headingNumber">2.2.2 </span>The Edition Statement</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD21" title="link to this section "><span class="invisible">TEI: The Title Statement</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.1 </span><span class="head">The Title Statement</span></h4><p>The <a class="gi" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a> element is the first component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element, and is mandatory: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-titleStmt.html">titleStmt</a></span> (title statement) groups information about the title of a work and those responsible for its content.</li></ul><p> It contains the title given to the electronic work, together with one or more optional <span class="term">statements of responsibility</span> which identify the encoder, editor, author, compiler, or other parties responsible for it: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-title.html">title</a></span> contains a title for any kind of work.</li><li><span class="specList-elementSpec"><a href="ref-author.html">author</a></span> 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.</li><li><span class="specList-elementSpec"><a href="ref-editor.html">editor</a></span> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc.</li><li><span class="specList-elementSpec"><a href="ref-sponsor.html">sponsor</a></span> specifies the name of a sponsoring organization or institution.</li><li><span class="specList-elementSpec"><a href="ref-funder.html">funder</a></span> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text.</li><li><span class="specList-elementSpec"><a href="ref-principal.html">principal</a></span> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text.</li><li><span class="specList-elementSpec"><a href="ref-respStmt.html">respStmt</a></span> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.</li><li><span class="specList-elementSpec"><a href="ref-resp.html">resp</a></span> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work.</li><li><span class="specList-elementSpec"><a href="ref-name.html">name</a></span> (name, proper noun) contains a proper noun or noun phrase.</li></ul><p>The <a class="gi" title="contains a title for any kind of work." href="ref-title.html">title</a> element contains the chief name of the electronic work, including any alternative title or subtitles it may have. It may be repeated, if the work has more than one title (perhaps in different languages) and takes whatever form is considered appropriate by its creator. Where the electronic work is derived from an existing source text, it is strongly recommended that the title for the former should be derived from the latter, but clearly distinguishable from it, for example by the addition of a phrase such as <span class="q">‘: an electronic transcription’</span> or <span class="q">‘a digital edition’</span>. This will distinguish the electronic work from the source text in citations and in catalogues which contain descriptions of both types of material.</p><p>The electronic work will also have an external name (its ‘filename’ or ‘data set name’) or reference number on the computer system where it resides at any time. This name is likely to change frequently, as new copies of the file are made on the computer system. Its form is entirely dependent on the particular computer system in use and thus cannot always easily be transferred from one system to another. Moreover, a given work may be composed of many files. For these reasons, these Guidelines strongly recommend that such names should <em>not</em> be used as the <a class="gi" title="contains a title for any kind of work." href="ref-title.html">title</a> for any electronic work.</p><p>Helpful guidance on the formulation of useful descriptive titles in difficult cases may be found in chapter 25 of <a class="link_ptr" href="BIB.html#HD-BIBL-1" title="AngloAmerican Cataloguing RulesSecond Edition 2002 revision 2005 updateChicagoAmerican Library AssociationOttawaCanadian Librar...">Anglo-American Cataloguing Rules (2002–2005)</a>) or another national cataloguing code.</p><p>The elements <a class="gi" title="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." href="ref-author.html">author</a>, <a class="gi" title="contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc." href="ref-editor.html">editor</a>, <a class="gi" title="specifies the name of a sponsoring organization or institution." href="ref-sponsor.html">sponsor</a>, <a class="gi" title="(funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text." href="ref-funder.html">funder</a>, and <a class="gi" title="(principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text." href="ref-principal.html">principal</a>, are specializations of the more general <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> element. These elements are used to provide the <span class="term">statements of responsibility</span> which identify the person(s) responsible for the intellectual or artistic content of an item and any corporate bodies from which it emanates.</p><p>Any number of such statements may occur within the title statement. At a minimum, identify the author of the text and (where appropriate) the creator of the file. If the bibliographic description is for a corpus, identify the creator of the corpus. Optionally include also names of others involved in the transcription or elaboration of the text, sponsors, and funding agencies. The name of the person responsible for physical data input need not normally be recorded, unless that person is also intellectually responsible for some aspect of the creation of the file.</p><p>Where the person whose responsibility is to be documented is not an author, sponsor, funding body, or principal researcher, the <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> element should be used. This has two subcomponents: a <a class="gi" title="(name, proper noun) contains a proper noun or noun phrase." href="ref-name.html">name</a> element identifying a responsible individual or organization, and a <a class="gi" title="(responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work." href="ref-resp.html">resp</a> element indicating the nature of the responsibility. No specific recommendations are made at this time as to appropriate content for the <a class="gi" title="(responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work." href="ref-resp.html">resp</a>: it should make clear the nature of the responsibility concerned, as in the examples below.</p><p>Names given may be personal names or corporate names. Give all names in the form in which the persons or bodies wish to be publicly cited. This would usually be the fullest form of the name, including first names.<span id="Note43_return"><a class="notelink" title="Agencies compiling catalogues of machine-readable files are recommended to use available authority lists, such as the Library of Congress Name Authori…" href="#Note43"><sup>6</sup></a></span></p><div class="p">Examples: <div id="index-egXML-d52e19494" class="pre egXML_valid"><span class="element"><titleStmt></span><br /> <span class="element"><title></span>Capgrave's Life of St. John Norbert: a<br /> machine-readable transcription<span class="element"></title></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>compiled by<span class="element"></resp></span><br /> <span class="element"><name></span>P.J. Lucas<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /><span class="element"></titleStmt></span></div> <div id="index-egXML-d52e19504" class="pre egXML_valid"><span class="element"><titleStmt></span><br /> <span class="element"><title></span>Two stories by Edgar Allen Poe: electronic version<span class="element"></title></span><br /> <span class="element"><author></span>Poe, Edgar Allen (1809-1849)<span class="element"></author></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>compiled by<span class="element"></resp></span><br /> <span class="element"><name></span>James D. Benson<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /><span class="element"></titleStmt></span></div> <div id="index-egXML-d52e19516" class="pre egXML_valid"><span class="element"><titleStmt></span><br /> <span class="element"><title></span>Yogadarśanam (arthāt<br /> yogasūtrapūṭhaḥ):<br /> a digital edition.<span class="element"></title></span><br /> <span class="element"><title></span>The Yogasūtras of Patañjali:<br /> a digital edition.<span class="element"></title></span><br /> <span class="element"><funder></span>Wellcome Institute for the History of Medicine<span class="element"></funder></span><br /> <span class="element"><principal></span>Dominik Wujastyk<span class="element"></principal></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><name></span>Wieslaw Mical<span class="element"></name></span><br /> <span class="element"><resp></span>data entry and proof correction<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><name></span>Jan Hajic<span class="element"></name></span><br /> <span class="element"><resp></span>conversion to TEI-conformant markup<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /><span class="element"></titleStmt></span></div></div></div><div class="div3" id="HD22"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD21"><span class="headingNumber">2.2.1 </span>The Title Statement</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD23"><span class="headingNumber">2.2.3 </span>Type and Extent of File</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD22" title="link to this section "><span class="invisible">TEI: The Edition Statement</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.2 </span><span class="head">The Edition Statement</span></h4><p>The <a class="gi" title="(edition statement) groups information relating to one edition of a text." href="ref-editionStmt.html">editionStmt</a> element is the second component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element. It is optional but recommended. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-editionStmt.html">editionStmt</a></span> (edition statement) groups information relating to one edition of a text.</li></ul><p> It contains either phrases or more specialized elements identifying the edition and those responsible for it: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-edition.html">edition</a></span> describes the particularities of one edition of a text.</li><li><span class="specList-elementSpec"><a href="ref-respStmt.html">respStmt</a></span> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.</li><li><span class="specList-elementSpec"><a href="ref-name.html">name</a></span> (name, proper noun) contains a proper noun or noun phrase.</li><li><span class="specList-elementSpec"><a href="ref-resp.html">resp</a></span> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work.</li></ul><p>For printed texts, the word <span class="mentioned">edition</span> applies to the set of all the identical copies of an item produced from one master copy and issued by a particular publishing agency or a group of such agencies. A change in the identity of the distributing body or bodies does not normally constitute a change of edition, while a change in the master copy does.</p><p>For electronic texts, the notion of a ‘master copy’ is not entirely appropriate, since they are far more easily copied and modified than printed ones; nonetheless the term <span class="mentioned">edition</span> may be used for a particular state of a machine-readable text at which substantive changes are made and fixed. Synonymous terms used in these Guidelines are <span class="mentioned">version</span>, <span class="mentioned">level</span>, and <span class="mentioned">release</span>. The words <span class="mentioned">revision</span> and <span class="mentioned">update</span>, by contrast, are used for minor changes to a file which do not amount to a new edition.</p><p>No simple rule can specify how ‘substantive’ changes have to be before they are regarded as producing a new edition, rather than a simple update. The general principle proposed here is that the production of a new edition entails a significant change in the intellectual content of the file, rather than its encoding or appearance. The addition of analytic coding to a text would thus constitute a new edition, while automatic conversion from one coded representation to another would not. Changes relating to the character code or physical storage details, corrections of misspellings, simple changes in the arrangement of the contents and changes in the output format do not normally constitute a new edition, whereas the addition of new information (e.g. a linguistic analysis expressed in part-of-speech tagging, sound or graphics, referential links to external data sets) almost always does.</p><p>Clearly, there will always be borderline cases and the matter is somewhat arbitrary. The simplest rule is: if you think that your file is a new edition, then call it such. An edition statement is optional for the first release of a computer file; it is mandatory for each later release, though this requirement cannot be enforced by the parser. </p><p>Note that <em>all</em> changes in a file considered significant, whether or not they are regarded as constituting a new edition or simply a new revision, should be independently noted in the revision description section of the file header (see section <a class="link_ptr" href="HD.html#HD6" title="The Revision Description"><span class="headingNumber">2.6 </span>The Revision Description</a>).</p><p>The <a class="gi" title="describes the particularities of one edition of a text." href="ref-edition.html">edition</a> element should contain phrases describing the edition or version, including the word <span class="mentioned">edition</span>, <span class="mentioned">version</span>, or equivalent, together with a number or date, or terms indicating difference from other editions such as <span class="mentioned">new edition</span>, <span class="mentioned">revised edition</span> etc. Any dates that occur within the edition statement should be marked with the <a class="gi" title="contains a date in any format." href="ref-date.html">date</a> element. The <span class="att">n</span> attribute of the <a class="gi" title="describes the particularities of one edition of a text." href="ref-edition.html">edition</a> element may be used as elsewhere to supply any formal identification (such as a version number) for the edition.</p><p>One or more <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> elements may also be used to supply statements of responsibility for the edition in question. These may refer to individuals or corporate bodies and can indicate functions such as that of a reviser, or can name the person or body responsible for the provision of supplementary matter, of appendices, etc., in a new edition. For further detail on the <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> element, see section <a class="link_ptr" href="CO.html#COBI" title="Bibliographic Citations and References"><span class="headingNumber">3.11 </span>Bibliographic Citations and References</a>.</p><div class="p">Some examples follow: <div id="index-egXML-d52e19986" class="pre egXML_valid"><span class="element"><editionStmt></span><br /> <span class="element"><edition <span class="attribute">n</span>="<span class="attributevalue">P2</span>"></span>Second draft, substantially<br /> extended, revised, and corrected.<span class="element"></edition></span><br /><span class="element"></editionStmt></span></div> <div id="index-egXML-d52e19991" class="pre egXML_valid"><span class="element"><editionStmt></span><br /> <span class="element"><edition></span>Student's edition, <span class="element"><date></span>June 1987<span class="element"></date></span><span class="element"></edition></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>New annotations by<span class="element"></resp></span><br /> <span class="element"><name></span>George Brown<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /><span class="element"></editionStmt></span></div></div></div><div class="div3" id="HD23"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD22"><span class="headingNumber">2.2.2 </span>The Edition Statement</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD24"><span class="headingNumber">2.2.4 </span>Publication, Distribution, Licensing, etc.</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD23" title="link to this section "><span class="invisible">TEI: Type and Extent of File</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.3 </span><span class="head">Type and Extent of File</span></h4><p>The <a class="gi" title="describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units." href="ref-extent.html">extent</a> element is the third component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element. It is optional. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-extent.html">extent</a></span> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units.</li></ul><p>For printed books, information about the carrier, such as the kind of medium used and its size, are of great importance in cataloguing procedures. The print-oriented rules for bibliographic description of an item's medium and extent need some re-interpretation when applied to electronic media. An electronic file exists as a distinct entity quite independently of its carrier and remains the same intellectual object whether it is stored on a magnetic tape, a CD-ROM, a set of floppy disks, or as a file on a mainframe computer. Since, moreover, these Guidelines are specifically aimed at facilitating transparent document storage and interchange, any purely machine-dependent information should be irrelevant as far as the file header is concerned. </p><p>This is particularly true of information about <span class="term">file-type</span> although library-oriented rules for cataloguing often distinguish two types of computer file: <span class="q">‘data’</span> and <span class="q">‘programs’</span>. This distinction is quite difficult to draw in some cases, for example, hypermedia or texts with built in search and retrieval software.</p><p>Although it is equally system-dependent, some measure of the size of the computer file may be of use for cataloguing and other practical purposes. Because the measurement and expression of file size is fraught with difficulties, only very general recommendations are possible; the element <a class="gi" title="describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units." href="ref-extent.html">extent</a> is provided for this purpose. It contains a phrase indicating the size or approximate size of the computer file in one of the following ways: </p><ul class="bulleted"><li class="item">in bytes of a specified length (e.g. <span class="bulleted">‘4000 16-bit bytes’</span>)</li><li class="item">as falling within a range of categories, for example: <ul class="bulleted"><li class="item">less than 1 Mb</li><li class="item">between 1 Mb and 5 Mb</li><li class="item">between 6 Mb and 10 Mb</li><li class="item">over 10 Mb</li></ul></li><li class="item">in terms of any convenient logical units (for example, words or sentences, citations, paragraphs)</li><li class="item">in terms of any convenient physical units (for example, blocks, disks, tapes)</li></ul><p>The use of standard abbreviations for units of quantity is recommended where applicable, here as elsewhere (see <a class="link_ptr" href="http://physics.nist.gov/cuu/Units/binary.html"><span>http://physics.nist.gov/cuu/Units/binary.html</span></a>).</p><div class="p">Examples: <div id="index-egXML-d52e20234" class="pre egXML_valid"><span class="element"><extent></span>between 1 and<br /> 2 Mb<span class="element"></extent></span><br /><span class="element"><extent></span>4.2 MiB<span class="element"></extent></span><br /><span class="element"><extent></span>4532 bytes<span class="element"></extent></span><br /><span class="element"><extent></span>3200 sentences<span class="element"></extent></span><br /><span class="element"><extent></span>Five 90 mm High Density Diskettes<span class="element"></extent></span></div></div><div class="p">The <a class="gi" title="contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name." href="ref-measure.html">measure</a> element and its attributes may be used to supply machine-tractable or normalised versions of the size or sizes given, as in the following example: <div id="index-egXML-d52e20251" class="pre egXML_valid"><span class="element"><extent></span><br /> <span class="element"><measure <span class="attribute">unit</span>="<span class="attributevalue">MiB</span>" <span class="attribute">quantity</span>="<span class="attributevalue">4.2</span>"></span>About four megabytes<span class="element"></measure></span><br /> <span class="element"><measure <span class="attribute">unit</span>="<span class="attributevalue">pages</span>" <span class="attribute">quantity</span>="<span class="attributevalue">245</span>"></span>245 pages of source<br /> material<span class="element"></measure></span><br /><span class="element"></extent></span></div> Note that when more than one <a class="gi" title="contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name." href="ref-measure.html">measure</a> is supplied in a single <a class="gi" title="describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units." href="ref-extent.html">extent</a>, the implication is that all the measurements apply to the whole resource.</div></div><div class="div3" id="HD24"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD23"><span class="headingNumber">2.2.3 </span>Type and Extent of File</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD26"><span class="headingNumber">2.2.5 </span>The Series Statement</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD24" title="link to this section "><span class="invisible">TEI: Publication, Distribution, Licensing, etc.</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.4 </span><span class="head">Publication, Distribution, Licensing, etc.</span></h4><p>The <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a> element is the fourth component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element and is mandatory. Its function is to name the agency by which a resource is made available (for example, a publisher or distributor) and to supply any additional information about the way in which it is made available such as licensing conditions, identifying numbers, etc. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-publicationStmt.html">publicationStmt</a></span> (publication statement) groups information concerning the publication or distribution of an electronic or other text.</li></ul><p> It may contain either a simple prose description organized as one or more paragraphs, or the more specialised elements described below.</p><p>A structured publication statement must begin with one of the following elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-publisher.html">publisher</a></span> provides the name of the organization responsible for the publication or distribution of a bibliographic item.</li><li><span class="specList-elementSpec"><a href="ref-distributor.html">distributor</a></span> supplies the name of a person or other agency responsible for the distribution of a text.</li><li><span class="specList-elementSpec"><a href="ref-authority.html">authority</a></span> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor.</li></ul><p> These elements form the <a class="link_odd" title="groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent." href="ref-model.publicationStmtPart.agency.html">model.publicationStmtPart.agency</a> class; if the agency making the resource available is unknown, but other structured information about it is available, an explicit statement such as ‘publisher unknown’ should be used.</p><p>The <span class="term">publisher</span> is the person or institution by whose authority a given edition of the file is made public. The <span class="term">distributor</span> is the person or institution from whom copies of the text may be obtained. Where a text is not considered formally published, but is nevertheless made available for circulation by some individual or organization, this person or institution is termed the <span class="term">release authority</span>.</p><p>Whichever of these elements is chosen, it may be followed by one or more of the following elements, which together form the <a class="link_odd" title="groups the agency-specific child elements of the <publicationStmt> element of the TEI header." href="ref-model.publicationStmtPart.detail.html">model.publicationStmtPart.detail</a> class </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-pubPlace.html">pubPlace</a></span> (publication place) contains the name of the place where a bibliographic item was published.</li><li><span class="specList-elementSpec"><a href="ref-address.html">address</a></span> contains a postal address, for example of a publisher, an organization, or an individual.</li><li><span class="specList-elementSpec"><a href="ref-idno.html">idno</a></span> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.<table class="specDesc"><tr><td class="Attribute"><span class="att">type</span></td><td>categorizes the identifier, for example as an ISBN, Social Security number, etc.
Suggested values include: 1] ISBN; 2] ISSN; 3] DOI; 4] URI; 5] VIAF; 6] ESTC; 7] OCLC</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-availability.html">availability</a></span> 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.<table class="specDesc"><tr><td class="Attribute"><span class="att">status</span></td><td>supplies a code identifying the current availability of the text.</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-date.html">date</a></span> contains a date in any format.</li><li><span class="specList-elementSpec"><a href="ref-licence.html">licence</a></span> contains information about a licence or other legal agreement applicable to the text.</li></ul><div class="p">Here is a simple example: <div id="index-egXML-d52e20399" class="pre egXML_valid"><span class="element"><publicationStmt></span><br /> <span class="element"><publisher></span>Oxford University Press<span class="element"></publisher></span><br /> <span class="element"><pubPlace></span>Oxford<span class="element"></pubPlace></span><br /> <span class="element"><date></span>1989<span class="element"></date></span><br /> <span class="element"><idno <span class="attribute">type</span>="<span class="attributevalue">ISBN</span>"></span>0-19-254705-4<span class="element"></idno></span><br /> <span class="element"><availability></span><br /> <span class="element"><p></span>Copyright 1989, Oxford University Press<span class="element"></p></span><br /> <span class="element"></availability></span><br /><span class="element"></publicationStmt></span></div></div><div class="p">The <a class="link_odd" title="groups the agency-specific child elements of the <publicationStmt> element of the TEI header." href="ref-model.publicationStmtPart.detail.html">model.publicationStmtPart.detail</a> elements all supply additional information relating to the the publisher, distributor, or release authority immediately preceding them. In the following example, Benson is identified as responsible for distribution of some resource at the date and place cited: <div id="index-egXML-d52e20418" class="pre egXML_valid"><span class="element"><publicationStmt></span><br /> <span class="element"><authority></span>James D. Benson<span class="element"></authority></span><br /> <span class="element"><pubPlace></span>London<span class="element"></pubPlace></span><br /> <span class="element"><date></span>1994<span class="element"></date></span><br /><span class="element"></publicationStmt></span></div></div><p>A resource may have (for example) both a publisher and a distributor, or more than one publisher each using different identifiers for the same resource, and so on. For this reason, the sequence of at least one <a class="link_odd" title="groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent." href="ref-model.publicationStmtPart.agency.html">model.publicationStmtPart.agency</a> element followed by zero or more <a class="link_odd" title="groups the agency-specific child elements of the <publicationStmt> element of the TEI header." href="ref-model.publicationStmtPart.detail.html">model.publicationStmtPart.detail</a> elements may be repeated as often as necessary.</p><div class="p">The following example shows a resource published by one agency (Sigma Press) at one address and date, which is also distributed by another (Oxford Text Archive), with a specified identifier and a different date: <div id="index-egXML-d52e20437" class="pre egXML_valid"><span class="element"><publicationStmt></span><br /> <span class="element"><publisher></span>Sigma Press<span class="element"></publisher></span><br /> <span class="element"><address></span><br /> <span class="element"><addrLine></span>21 High Street,<span class="element"></addrLine></span><br /> <span class="element"><addrLine></span>Wilmslow,<span class="element"></addrLine></span><br /> <span class="element"><addrLine></span>Cheshire M24 3DF<span class="element"></addrLine></span><br /> <span class="element"></address></span><br /> <span class="element"><date></span>1991<span class="element"></date></span><br /> <span class="element"><distributor></span>Oxford Text Archive<span class="element"></distributor></span><br /> <span class="element"><idno <span class="attribute">type</span>="<span class="attributevalue">OTA</span>"></span>1256<span class="element"></idno></span><br /> <span class="element"><availability></span><br /> <span class="element"><p></span>Available with prior consent of depositor for<br /> purposes of academic research and teaching only.<span class="element"></p></span><br /> <span class="element"></availability></span><br /> <span class="element"><date></span>1994<span class="element"></date></span><br /><span class="element"></publicationStmt></span></div></div><p>The <a class="gi" title="contains a date in any format." href="ref-date.html">date</a> element used within <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a> always refers to the date of publication, first distribution, or initial release. If the text was created at some other date, this may be recorded using the <a class="gi" title="contains information about the creation of a text." href="ref-creation.html">creation</a> element within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element. Other useful dates (such as dates of collection of data) may be given using a note in the <a class="gi" title="(notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description." href="ref-notesStmt.html">notesStmt</a> element.</p><div class="p">The <a class="gi" title="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." href="ref-availability.html">availability</a> element may be used, as above, to provide a simple prose statement of any restrictions concerning the distribution of the resource. Alternatively, a more formal statement of the licensing conditions applicable may be provided using the <a class="gi" title="contains information about a licence or other legal agreement applicable to the text." href="ref-licence.html">licence</a> element: <div id="index-egXML-d52e20485" class="pre egXML_valid"><span class="element"><publicationStmt></span><br /> <span class="element"><publisher></span>University of Victoria Humanities Computing and Media Centre<span class="element"></publisher></span><br /> <span class="element"><pubPlace></span>Victoria, BC<span class="element"></pubPlace></span><br /> <span class="element"><date></span>2011<span class="element"></date></span><br /> <span class="element"><availability <span class="attribute">status</span>="<span class="attributevalue">restricted</span>"></span><br /> <span class="element"><licence <span class="attribute">target</span>="<span class="attributevalue">http://creativecommons.org/licenses/by-sa/3.0/</span>"></span> Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License<br /> <span class="element"></licence></span><br /> <span class="element"></availability></span><br /><span class="element"></publicationStmt></span></div> Note here the use of the <span class="att">target</span> attribute to point to a location from which the licence document itself may be obtained. Alternatively, the licence document may simply be contained within the <a class="gi" title="contains information about a licence or other legal agreement applicable to the text." href="ref-licence.html">licence</a> element.</div></div><div class="div3" id="HD26"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD24"><span class="headingNumber">2.2.4 </span>Publication, Distribution, Licensing, etc.</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD27"><span class="headingNumber">2.2.6 </span>The Notes Statement</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD26" title="link to this section "><span class="invisible">TEI: The Series Statement</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.5 </span><span class="head">The Series Statement</span></h4><p>The <a class="gi" title="(series statement) groups information about the series, if any, to which a publication belongs." href="ref-seriesStmt.html">seriesStmt</a> element is the fifth component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element and is optional. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-seriesStmt.html">seriesStmt</a></span> (series statement) groups information about the series, if any, to which a publication belongs.</li></ul><p>In bibliographic parlance, a <span class="term">series</span> may be defined in one of the following ways: </p><ul class="bulleted"><li class="item">A group of separate items related to one another by the fact that each item bears, in addition to its own title proper, a collective title applying to the group as a whole. The individual items may or may not be numbered.</li><li class="item">Each of two or more volumes of essays, lectures, articles, or other items, similar in character and issued in sequence.</li><li class="item">A separately numbered sequence of volumes within a series or serial.</li></ul><p> The <a class="gi" title="(series statement) groups information about the series, if any, to which a publication belongs." href="ref-seriesStmt.html">seriesStmt</a> element may contain a prose description or one or more of the following more specific elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-title.html">title</a></span> contains a title for any kind of work.</li><li><span class="specList-elementSpec"><a href="ref-idno.html">idno</a></span> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.</li><li><span class="specList-elementSpec"><a href="ref-respStmt.html">respStmt</a></span> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.</li><li><span class="specList-elementSpec"><a href="ref-resp.html">resp</a></span> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work.</li><li><span class="specList-elementSpec"><a href="ref-name.html">name</a></span> (name, proper noun) contains a proper noun or noun phrase.</li></ul><p>The <a class="gi" title="(identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way." href="ref-idno.html">idno</a> may be used to supply any identifying number associated with the item, including both standard numbers such as an ISSN and particular issue numbers. (Arabic numerals separated by punctuation are recommended for this purpose: <span class="val">6.19.33</span>, for example, rather than <span class="val">VI/xix:33</span>). Its <span class="att">type</span> attribute is used to categorize the number further, taking the value <span class="val">ISSN</span> for an ISSN for example.</p><div class="p">Examples: <div id="index-egXML-d52e21266" class="pre egXML_valid"><span class="element"><seriesStmt></span><br /> <span class="element"><title <span class="attribute">level</span>="<span class="attributevalue">s</span>"></span>Machine-Readable Texts for the Study of<br /> Indian Literature<span class="element"></title></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>ed. by<span class="element"></resp></span><br /> <span class="element"><name></span>Jan Gonda<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /> <span class="element"><biblScope <span class="attribute">unit</span>="<span class="attributevalue">vol</span>"></span>1.2<span class="element"></biblScope></span><br /> <span class="element"><idno <span class="attribute">type</span>="<span class="attributevalue">ISSN</span>"></span>0 345 6789<span class="element"></idno></span><br /><span class="element"></seriesStmt></span></div> </div></div><div class="div3" id="HD27"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD26"><span class="headingNumber">2.2.5 </span>The Series Statement</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD3"><span class="headingNumber">2.2.7 </span>The Source Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD27" title="link to this section "><span class="invisible">TEI: The Notes Statement</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.6 </span><span class="head">The Notes Statement</span></h4><p>The <a class="gi" title="(notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description." href="ref-notesStmt.html">notesStmt</a> element is the sixth component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element and is optional. If used, it contains one or more <a class="gi" title="contains a note or annotation." href="ref-note.html">note</a> elements, each containing a single piece of descriptive information of the kind treated as ‘general notes’ in traditional bibliographic descriptions. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-notesStmt.html">notesStmt</a></span> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description.</li><li><span class="specList-elementSpec"><a href="ref-note.html">note</a></span> contains a note or annotation.</li></ul><p>Some information found in the notes area in conventional bibliography has been assigned specific elements in these Guidelines; in particular the following items should be tagged as indicated, rather than as general notes: </p><ul class="bulleted"><li class="item">the nature, scope, artistic form, or purpose of the file; also the genre or other intellectual category to which it may belong: e.g. <span class="bulleted">‘Text types: newspaper editorials and reportage, science fiction, westerns, and detective stories’</span>. These should be formally described within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element (section <a class="link_ptr" href="HD.html#HD4" title="The Profile Description"><span class="headingNumber">2.4 </span>The Profile Description</a>).</li><li class="item">an abstract or summary of the content of a document which has been supplied by the encoder because no such abstract forms part of the content of the source. This should be supplied in the <a class="gi" title="contains a summary or formal abstract prefixed to an existing source document by the encoder." href="ref-abstract.html">abstract</a> element within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element (section <a class="link_ptr" href="HD.html#HD4" title="The Profile Description"><span class="headingNumber">2.4 </span>The Profile Description</a>).</li><li class="item">summary description providing a factual, non-evaluative account of the subject content of the file: e.g. <span class="bulleted">‘Transcribes interviews on general topics with native speakers of English in 17 cities during the spring and summer of 1963.’</span> These should also be formally described within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element (section <a class="link_ptr" href="HD.html#HD4" title="The Profile Description"><span class="headingNumber">2.4 </span>The Profile Description</a>).</li><li class="item">bibliographic details relating to the source or sources of an electronic text: e.g. <span class="bulleted">‘Transcribed from the Norton facsimile of the 1623 Folio’</span>. These should be formally described in the <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element (section <a class="link_ptr" href="HD.html#HD3" title="The Source Description"><span class="headingNumber">2.2.7 </span>The Source Description</a>).</li><li class="item">further information relating to publication, distribution, or release of the text, including sources from which the text may be obtained, any restrictions on its use or formal terms on its availability. These should be placed in the appropriate division of the <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a> element (section <a class="link_ptr" href="HD.html#HD24" title="Publication Distribution Licensing etc."><span class="headingNumber">2.2.4 </span>Publication, Distribution, Licensing, etc.</a>).</li><li class="item">publicly documented numbers associated with the file: e.g. <span class="bulleted">‘ICPSR study number 1803’</span> or <span class="bulleted">‘Oxford Text Archive text number 1243’</span>. These should be placed in an <a class="gi" title="(identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way." href="ref-idno.html">idno</a> element within the appropriate division of the <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a> element. International Standard Serial Numbers (ISSN), International Standard Book Numbers (ISBN), and other internationally agreed upon standard numbers that uniquely identify an item, should be treated in the same way, rather than as specialized bibliographic notes.</li></ul><p>Nevertheless, the <a class="gi" title="(notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description." href="ref-notesStmt.html">notesStmt</a> element may be used to record potentially significant details about the file and its features, e.g.: </p><ul class="bulleted"><li class="item">dates, when they are relevant to the content or condition of the computer file: e.g. <span class="bulleted">‘manual dated 1983’</span>, <span class="bulleted">‘Interview wave I: Apr. 1989; wave II: Jan. 1990’</span></li><li class="item">names of persons or bodies connected with the technical production, administration, or consulting functions of the effort which produced the file, if these are not named in statements of responsibility in the title or edition statements of the file description: e.g. <span class="bulleted">‘Historical commentary provided by Mark Cohen’</span></li><li class="item">availability of the file in an additional medium or information not already recorded about the availability of documentation: e.g. <span class="bulleted">‘User manual is loose-leaf in eleven paginated sections’</span></li><li class="item">language of work and abstract, if not encoded in the <a class="gi" title="(language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text." href="ref-langUsage.html">langUsage</a> element, e.g. <span class="bulleted">‘Text in English with summaries in French and German’</span></li><li class="item">The unique name assigned to a serial by the International Serials Data System (ISDS), if not encoded in an <a class="gi" title="(identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way." href="ref-idno.html">idno</a></li><li class="item">lists of related publications, either describing the source itself, or concerned with the creation or use of the electronic work, e.g. <span class="bulleted">‘Texts used in <a class="citlink" href="BIB.html#HD-BIBL-2">Burrows (1987)</a>’</span></li></ul><div class="p">Each such item of information may be tagged using the general-purpose <a class="gi" title="contains a note or annotation." href="ref-note.html">note</a> element, which is described in section <a class="link_ptr" href="CO.html#CONO" title="Notes Annotation and Indexing"><span class="headingNumber">3.8 </span>Notes, Annotation, and Indexing</a>. Groups of notes are contained within the <a class="gi" title="(notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description." href="ref-notesStmt.html">notesStmt</a> element, as in the following example: <div id="index-egXML-d52e21523" class="pre egXML_valid"><span class="element"><notesStmt></span><br /> <span class="element"><note></span>Historical commentary provided by Mark Cohen.<span class="element"></note></span><br /> <span class="element"><note></span>OCR scanning done at University of Toronto.<span class="element"></note></span><br /><span class="element"></notesStmt></span></div> There are advantages, however, to encoding such information with more precise elements elsewhere in the TEI header, when such elements are available. For example, the notes above might be encoded as follows: <div id="index-egXML-d52e21530" class="pre egXML_valid"><span class="element"><titleStmt></span><br /> <span class="element"><title></span>…<span class="element"></title></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><persName></span>Mark Cohen<span class="element"></persName></span><br /> <span class="element"><resp></span>historical commentary<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><orgName></span>University of Toronto<span class="element"></orgName></span><br /> <span class="element"><resp></span>OCR scanning<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /><span class="element"></titleStmt></span></div> </div></div><div class="div3" id="HD3"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD27"><span class="headingNumber">2.2.6 </span>The Notes Statement</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD31"><span class="headingNumber">2.2.8 </span>Computer Files Derived from Other Computer Files</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD3" title="link to this section "><span class="invisible">TEI: The Source Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.7 </span><span class="head">The Source Description</span></h4><p>The <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element is the seventh and final component of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element. It is a mandatory element and is used to record details of the source or sources from which a computer file is derived. This might be a printed text or manuscript, another computer file, an audio or video recording of some kind, or a combination of these. An electronic file may also have no source, if what is being catalogued is an original text created in electronic form. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-sourceDesc.html">sourceDesc</a></span> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence.</li></ul><div class="p">The <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element may contain little more than a simple prose description, or a brief note stating that the document has no source: <div id="index-egXML-d52e21649" class="pre egXML_valid"><span class="element"><sourceDesc></span><br /> <span class="element"><p></span>Born digital.<span class="element"></p></span><br /><span class="element"></sourceDesc></span></div></div><p>Alternatively, it may contain elements drawn from the following three classes: </p><ul class="specList"><li><span class="specList-classSpec"><a href="ref-model.biblLike.html">model.biblLike</a></span> groups elements containing a bibliographic description.<table class="elementList"><tr><td class="odd_label"><a href="ref-bibl.html">bibl</a></td><td class="odd_value">(bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.</td></tr><tr><td class="odd_label"><a href="ref-biblFull.html">biblFull</a></td><td class="odd_value">(fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present.</td></tr><tr><td class="odd_label"><a href="ref-biblStruct.html">biblStruct</a></td><td class="odd_value">(structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order.</td></tr><tr><td class="odd_label"><a href="ref-listBibl.html">listBibl</a></td><td class="odd_value">(citation list) contains a list of bibliographic citations of any kind.</td></tr><tr><td class="odd_label"><a href="ref-msDesc.html">msDesc</a></td><td class="odd_value">(manuscript description) contains a description of a single identifiable manuscript or other text-bearing object.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.sourceDescPart.html">model.sourceDescPart</a></span> groups elements which may be used inside <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> and appear multiple times.<table class="elementList"><tr><td class="odd_label"><a href="ref-recordingStmt.html">recordingStmt</a></td><td class="odd_value">(recording statement) describes a set of recordings used as the basis for transcription of a spoken text.</td></tr><tr><td class="odd_label"><a href="ref-scriptStmt.html">scriptStmt</a></td><td class="odd_value">(script statement) contains a citation giving details of the script used for a spoken text.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-model.listLike.html">model.listLike</a></span> groups list-like elements.<table class="elementList"><tr><td class="odd_label"><a href="ref-list.html">list</a></td><td class="odd_value">contains any sequence of items organized as a list.</td></tr><tr><td class="odd_label"><a href="ref-listApp.html">listApp</a></td><td class="odd_value">(list of apparatus entries) contains a list of apparatus entries.</td></tr><tr><td class="odd_label"><a href="ref-listEvent.html">listEvent</a></td><td class="odd_value">(list of events) contains a list of descriptions, each of which provides information about an identifiable event.</td></tr><tr><td class="odd_label"><a href="ref-listNym.html">listNym</a></td><td class="odd_value">(list of canonical names) contains a list of nyms, that is, standardized names for any thing.</td></tr><tr><td class="odd_label"><a href="ref-listOrg.html">listOrg</a></td><td class="odd_value">(list of organizations) contains a list of elements, each of which provides information about an identifiable organization.</td></tr><tr><td class="odd_label"><a href="ref-listPerson.html">listPerson</a></td><td class="odd_value">(list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source.</td></tr><tr><td class="odd_label"><a href="ref-listPlace.html">listPlace</a></td><td class="odd_value">(list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them.</td></tr><tr><td class="odd_label"><a href="ref-listWit.html">listWit</a></td><td class="odd_value">(witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically.</td></tr><tr><td class="odd_label"><a href="ref-table.html">table</a></td><td class="odd_value">contains text displayed in tabular form, in rows and columns.</td></tr></table></li></ul><div class="p">These classes make available by default a range of ways of providing bibliographic citations which specify the provenance of the text. For written or printed sources, the source may be described in the same way as any other bibliographic citation, using one of the following elements: <ul class="specList"><li><span class="specList-elementSpec"><a href="ref-bibl.html">bibl</a></span> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.</li><li><span class="specList-elementSpec"><a href="ref-biblStruct.html">biblStruct</a></span> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order.</li><li><span class="specList-elementSpec"><a href="ref-listBibl.html">listBibl</a></span> (citation list) contains a list of bibliographic citations of any kind.</li></ul> These elements are described in more detail in section <a class="link_ptr" href="CO.html#COBI" title="Bibliographic Citations and References"><span class="headingNumber">3.11 </span>Bibliographic Citations and References</a>. Using them, a source might be described in very simple terms: <div id="index-egXML-d52e21670" class="pre egXML_valid"><span class="element"><sourceDesc></span><br /> <span class="element"><bibl></span>The first folio of Shakespeare, prepared by<br /> Charlton Hinman (The Norton Facsimile, 1968)<span class="element"></bibl></span><br /><span class="element"></sourceDesc></span></div> or with more elaboration: <div id="index-egXML-d52e21675" class="pre egXML_valid"><span class="element"><sourceDesc></span><br /> <span class="element"><biblStruct <span class="attribute">xml:lang</span>="<span class="attributevalue">fr</span>"></span><br /> <span class="element"><monogr></span><br /> <span class="element"><author></span>Eugène Sue<span class="element"></author></span><br /> <span class="element"><title></span>Martin, l'enfant trouvé<span class="element"></title></span><br /> <span class="element"><title <span class="attribute">type</span>="<span class="attributevalue">sub</span>"></span>Mémoires d'un valet de chambre<span class="element"></title></span><br /> <span class="element"><imprint></span><br /> <span class="element"><pubPlace></span>Bruxelles et Leipzig<span class="element"></pubPlace></span><br /> <span class="element"><publisher></span>C. Muquardt<span class="element"></publisher></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1846</span>"></span>1846<span class="element"></date></span><br /> <span class="element"></imprint></span><br /> <span class="element"></monogr></span><br /> <span class="element"></biblStruct></span><br /><span class="element"></sourceDesc></span></div></div><p>When the header describes a text derived from some pre-existing TEI-conformant or other digital document, it may be simpler to use the following element, which is designed specifically for documents derived from texts which were ‘born digital’: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-biblFull.html">biblFull</a></span> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present.</li></ul><p> For further discussion see section <a class="link_ptr" href="HD.html#HD31" title="Computer Files Derived from Other Computer Files"><span class="headingNumber">2.2.8 </span>Computer Files Derived from Other Computer Files</a>.</p><p>When the module for manuscript description is included in a schema, this class also makes available the following element: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-msDesc.html">msDesc</a></span> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object.</li></ul><p> This element enables the encoder to record very detailed information about one or more manuscript or analogous sources, as further discussed in <a class="link_ptr" href="MS.html" title="Manuscript Description"><span class="headingNumber">10 </span>Manuscript Description</a>.</p><p>The <a class="link_odd" title="groups elements which may be used inside <sourceDesc> and appear multiple times." href="ref-model.sourceDescPart.html">model.sourceDescPart</a> class also makes available additional elements when additional modules are included. For example, when the <span class="ident-module">spoken</span> module is included, the <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element may also include the following special-purpose elements, intended for cases where an electronic text is derived from a spoken text rather than a written one: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-scriptStmt.html">scriptStmt</a></span> (script statement) contains a citation giving details of the script used for a spoken text.</li><li><span class="specList-elementSpec"><a href="ref-recordingStmt.html">recordingStmt</a></span> (recording statement) describes a set of recordings used as the basis for transcription of a spoken text.</li></ul><p> Full descriptions of these elements and their contents are given in section <a class="link_ptr" href="TS.html#HD32" title="Documenting the Source of Transcribed Speech"><span class="headingNumber">8.2 </span>Documenting the Source of Transcribed Speech</a>.</p><p>A single electronic text may be derived from multiple source documents, in whole or in part. The <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> may therefore contain a <a class="gi" title="(citation list) contains a list of bibliographic citations of any kind." href="ref-listBibl.html">listBibl</a> element grouping together <a class="gi" title="(bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged." href="ref-bibl.html">bibl</a>, <a class="gi" title="(structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order." href="ref-biblStruct.html">biblStruct</a>, or <a class="gi" title="(manuscript description) contains a description of a single identifiable manuscript or other text-bearing object." href="ref-msDesc.html">msDesc</a> elements for each of the sources concerned. It is also possible to repeat the <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element in such a case. The <span class="att">decls</span> attribute described in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a> may be used to associate parts of the encoded text with the bibliographic element from which it derives in either case.</p><p>The source description may also include lists of names, persons, places, etc. when these are considered to form part of the source for an encoded document. When such information is recorded using the specialized elements discussed in the <span class="ident-module">namesdates</span> module (<a class="link_ptr" href="ND.html" title="20"><span class="headingNumber">13 </span>Names, Dates, People, and Places</a>), the class <a class="link_odd" title="groups list-like elements." href="ref-model.listLike.html">model.listLike</a> makes available the following elements to hold such information: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-listNym.html">listNym</a></span> (list of canonical names) contains a list of nyms, that is, standardized names for any thing.</li><li><span class="specList-elementSpec"><a href="ref-listOrg.html">listOrg</a></span> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization.</li><li><span class="specList-elementSpec"><a href="ref-listPerson.html">listPerson</a></span> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source.</li><li><span class="specList-elementSpec"><a href="ref-listPlace.html">listPlace</a></span> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them.</li></ul></div><div class="div3" id="HD31"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD3"><span class="headingNumber">2.2.7 </span>The Source Description</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD31" title="link to this section "><span class="invisible">TEI: Computer Files Derived from Other Computer Files</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.2.8 </span><span class="head">Computer Files Derived from Other Computer Files</span></h4><p>If a computer file (call it B) is derived not from a printed source but from another computer file (call it A) which includes a TEI header, then the source text of computer file B is another computer file, A. The five sections of A's file header will need to be incorporated into the new header for B in slightly differing ways, as listed below: </p><dl><dt><span>fileDesc</span></dt><dd>A's file description should be copied into the <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> section of B's file description, enclosed within a <a class="gi" title="(fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present." href="ref-biblFull.html">biblFull</a> element</dd><dt><span>profileDesc</span></dt><dd>A's <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> should be copied into B's, in principle unchanged; it may however be expanded by project-specific information relating to B.</dd><dt><span>encodingDesc</span></dt><dd>A's encoding practice may or (more likely) may not be the same as B's. Since the object of the encoding description is to define the relationship between the current file and its source, in principle only changes in encoding practice between A and B need be documented in B. The relationship between A and its source(s) is then only recoverable from the original header of A. In practice it may be more convenient to create a new complete <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> for B based on A's.</dd><dt><span>xenoData</span></dt><dd>B is a new computer file, with a different source than A's source (namely, A). Thus it is unlikely that metadata from other schemes about A or its source can be copied wholesale to B, although there may be similarities.</dd><dt><span>revisionDesc</span></dt><dd>B is a new computer file, and should therefore have a new revision description. If, however, it is felt useful to include some information from A's <a class="gi" title="(revision description) summarizes the revision history for a file." href="ref-revisionDesc.html">revisionDesc</a>, for example dates of major updates or versions, such information must be clearly marked as relating to A rather than to B.</dd></dl><p> This concludes the discussion of the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element and its contents.</p></div></div><div class="div2" id="HD5"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD2"><span class="headingNumber">2.2 </span>The File Description</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD4"><span class="headingNumber">2.4 </span>The Profile Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD5" title="link to this section "><span class="invisible">TEI: The Encoding Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3 </span><span class="head">The Encoding Description</span></h3><p>The <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> element is the second major subdivision of the TEI header. It specifies the methods and editorial principles which governed the transcription or encoding of the text in hand and may also include sets of coded definitions used by other components of the header. Though not formally required, its use is highly recommended. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-encodingDesc.html">encodingDesc</a></span> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.</li></ul><p> The encoding description may contain any combination of paragraphs of text, marked up using the <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a> element, along with more specialized elements taken from the <a class="link_odd" title="groups elements which may be used inside <encodingDesc> and appear multiple times." href="ref-model.encodingDescPart.html">model.encodingDescPart</a> class. By default, this class makes available the following elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-projectDesc.html">projectDesc</a></span> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.</li><li><span class="specList-elementSpec"><a href="ref-samplingDecl.html">samplingDecl</a></span> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.</li><li><span class="specList-elementSpec"><a href="ref-editorialDecl.html">editorialDecl</a></span> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.</li><li><span class="specList-elementSpec"><a href="ref-tagsDecl.html">tagsDecl</a></span> (tagging declaration) provides detailed information about the tagging applied to a document.</li><li><span class="specList-elementSpec"><a href="ref-styleDefDecl.html">styleDefDecl</a></span> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied.</li><li><span class="specList-elementSpec"><a href="ref-refsDecl.html">refsDecl</a></span> (references declaration) specifies how canonical references are constructed for this text.</li><li><span class="specList-elementSpec"><a href="ref-classDecl.html">classDecl</a></span> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.</li><li><span class="specList-elementSpec"><a href="ref-geoDecl.html">geoDecl</a></span> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <a class="gi" title="(geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation." href="ref-geo.html">geo</a> element elsewhere within the document.</li><li><span class="specList-elementSpec"><a href="ref-schemaSpec.html">schemaSpec</a></span> (schema specification) generates a TEI-conformant schema and documentation for it.</li><li><span class="specList-elementSpec"><a href="ref-schemaRef.html">schemaRef</a></span> (schema reference) describes or points to a related customization or schema file</li></ul><p>Each of these elements is further described in the appropriate section below. Other modules have the ability to extend this class; examples are noted in section <a class="link_ptr" href="HD.html#HDENCOTH" title="ModuleSpecific Declarations"><span class="headingNumber">2.3.11 </span>Module-Specific Declarations</a></p><div class="div3" id="HD51"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD52"><span class="headingNumber">2.3.2 </span>The Sampling Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD51" title="link to this section "><span class="invisible">TEI: The Project Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.1 </span><span class="head">The Project Description</span></h4><p>The <a class="gi" title="(project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected." href="ref-projectDesc.html">projectDesc</a> element may be used to describe, in prose, the purpose for which a digital resource was created, together with any other relevant information concerning the process by which it was assembled or collected. This is of particular importance for corpora or miscellaneous collections, but may be of use for any text, for example to explain why one kind of encoding practice has been followed rather than another. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-projectDesc.html">projectDesc</a></span> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.</li></ul><div class="p">For example: <div id="index-egXML-d52e22192" class="pre egXML_valid"><span class="element"><encodingDesc></span><br /> <span class="element"><projectDesc></span><br /> <span class="element"><p></span>Texts collected for use in the<br /> Claremont Shakespeare Clinic, June 1990.<span class="element"></p></span><br /> <span class="element"></projectDesc></span><br /><span class="element"></encodingDesc></span></div></div></div><div class="div3" id="HD52"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD51"><span class="headingNumber">2.3.1 </span>The Project Description</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD53"><span class="headingNumber">2.3.3 </span>The Editorial Practices Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD52" title="link to this section "><span class="invisible">TEI: The Sampling Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.2 </span><span class="head">The Sampling Declaration</span></h4><div class="p">The <a class="gi" title="(sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection." href="ref-samplingDecl.html">samplingDecl</a> element may be used to describe, in prose, the rationale and methods used in selecting texts, or parts of text, for inclusion in the resource. <ul class="specList"><li><span class="specList-elementSpec"><a href="ref-samplingDecl.html">samplingDecl</a></span> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.</li></ul> It should include information about such matters as <ul class="bulleted"><li class="item">the size of individual samples</li><li class="item">the method or methods by which they were selected</li><li class="item">the underlying population being sampled</li><li class="item">the object of the sampling procedure used</li></ul> but is not restricted to these. <div id="index-egXML-d52e22296" class="pre egXML_valid"><span class="element"><samplingDecl></span><br /> <span class="element"><p></span>Samples of 2000 words taken from the beginning of the text.<span class="element"></p></span><br /><span class="element"></samplingDecl></span></div></div><div class="p">It may also include a simple description of any parts of the source text included or excluded. <div id="index-egXML-d52e22302" class="pre egXML_valid"><span class="element"><samplingDecl></span><br /> <span class="element"><p></span>Text of stories only has been transcribed. Pull quotes, captions,<br /> and advertisements have been silently omitted. Any mathematical<br /> expressions requiring symbols not present in the ISOnum or ISOpub<br /> entity sets have been omitted, and their place marked with a GAP<br /> element.<span class="element"></p></span><br /><span class="element"></samplingDecl></span></div></div><p>A sampling declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the <span class="att">decls</span> attribute of each text (or subdivision of the text) to which the sampling declaration applies may be used to supply a cross-reference to it, as further described in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a>.</p></div><div class="div3" id="HD53"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD52"><span class="headingNumber">2.3.2 </span>The Sampling Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD57"><span class="headingNumber">2.3.4 </span>The Tagging Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD53" title="link to this section "><span class="invisible">TEI: The Editorial Practices Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.3 </span><span class="head">The Editorial Practices Declaration</span></h4><p>The <a class="gi" title="(editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text." href="ref-editorialDecl.html">editorialDecl</a> element is used to provide details of the editorial practices applied during the encoding of a text. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-editorialDecl.html">editorialDecl</a></span> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.</li></ul><p>It may contain a prose description only, or one or more of a set of specialized elements, members of the TEI <a class="link_odd" title="groups elements which may be used inside <editorialDecl> and appear multiple times." href="ref-model.editorialDeclPart.html">model.editorialDeclPart</a> class. Where an encoder wishes to record an editorial policy not specified above, this may be done by adding a new element to this class, using the mechanisms discussed in chapter <a class="link_ptr" href="USE.html#MD" title="Customization"><span class="headingNumber">23.3 </span>Customization</a>.</p><p>Some of these policy elements carry attributes to support automated processing of certain well-defined editorial decisions; all of them contain a prose description of the editorial principles adopted with respect to the particular feature concerned. Examples of the kinds of questions which these descriptions are intended to answer are given in the list below.</p><dl><dt><span><a class="gi" title="(correction principles) states how and under what circumstances corrections have been made in the text." href="ref-correction.html">correction</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-correction.html">correction</a></span> (correction principles) states how and under what circumstances corrections have been made in the text.<table class="specDesc"><tr><td class="Attribute"><span class="att">status</span></td><td>indicates the degree of correction applied to the text.</td></tr><tr><td class="Attribute"><span class="att">method</span></td><td>indicates the method adopted to indicate corrections within the text.</td></tr></table></li></ul> <p>Was the text corrected during or after data capture? If so, were corrections made silently or are they marked using the tags described in section <a class="link_ptr" href="CO.html#COED" title="Simple Editorial Changes"><span class="headingNumber">3.4 </span>Simple Editorial Changes</a>? What principles have been adopted with respect to omissions, truncations, dubious corrections, alternate readings, false starts, repetitions, etc.?</p></dd><dt><span><a class="gi" title="indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form." href="ref-normalization.html">normalization</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-normalization.html">normalization</a></span> indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form.<table class="specDesc"><tr><td class="Attribute"><span class="att">source [att.global.source]</span></td><td>specifies the source from which some aspect of this element is drawn.</td></tr><tr><td class="Attribute"><span class="att">method</span></td><td>indicates the method adopted to indicate normalizations within the text.</td></tr></table></li></ul> <p>Was the text normalized, for example by regularizing any non-standard spellings, dialect forms, etc.? If so, were normalizations performed silently or are they marked using the tags described in section <a class="link_ptr" href="CO.html#COED" title="Simple Editorial Changes"><span class="headingNumber">3.4 </span>Simple Editorial Changes</a>? What authority was used for the regularization? Also, what principles were used when normalizing numbers to provide the standard values for the <span class="att">value</span> attribute described in section <a class="link_ptr" href="CO.html#CONANU" title="Numbers and Measures"><span class="headingNumber">3.5.3 </span>Numbers and Measures</a> and what format used for them?</p></dd><dt><span><a class="gi" title="specifies editorial practice adopted with respect to quotation marks in the original." href="ref-quotation.html">quotation</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-quotation.html">quotation</a></span> specifies editorial practice adopted with respect to quotation marks in the original.<table class="specDesc"><tr><td class="Attribute"><span class="att">marks</span></td><td>(quotation marks) indicates whether or not quotation marks have been retained as content within the text.</td></tr></table></li></ul> <p>How were quotation marks processed? Are apostrophes and quotation marks distinguished? How? Are quotation marks retained as content in the text or replaced by markup? Are there any special conventions regarding for example the use of single or double quotation marks when nested? Is the file consistent in its practice or has this not been checked? See section <a class="link_ptr" href="CO.html#COHQQ" title="Quotation"><span class="headingNumber">3.3.3 </span>Quotation</a> for discussion of ways in which quotation marks may be encoded.</p></dd><dt><span><a class="gi" title="summarizes the way in which hyphenation in a source text has been treated in an encoded version of it." href="ref-hyphenation.html">hyphenation</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-hyphenation.html">hyphenation</a></span> summarizes the way in which hyphenation in a source text has been treated in an encoded version of it.<table class="specDesc"><tr><td class="Attribute"><span class="att">eol</span></td><td>(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.</td></tr></table></li></ul> <p>Does the encoding distinguish ‘soft’ and ‘hard’ hyphens? What principle has been adopted with respect to end-of-line hyphenation where source lineation has not been retained? Have soft hyphens been silently removed, and if so what is the effect on lineation and pagination? See section <a class="link_ptr" href="CO.html#COPU-2" title="Hyphenation"><span class="headingNumber">3.2.2 </span>Hyphenation</a> for discussion of ways in which hyphenation may be encoded.</p></dd><dt><span><a class="gi" title="describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc." href="ref-segmentation.html">segmentation</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-segmentation.html">segmentation</a></span> describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.</li></ul> <p>How is the text segmented? If <a class="gi" title="(s-unit) contains a sentence-like division of a text." href="ref-s.html">s</a> or <a class="gi" title="(arbitrary segment) represents any segmentation of text below the ‘chunk’ level." href="ref-seg.html">seg</a> segmentation units have been used to divide up the text for analysis, how are they marked and how was the segmentation arrived at?</p></dd><dt><span><a class="gi" title="(standard values) specifies the format used when standardized date or number values are supplied." href="ref-stdVals.html">stdVals</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-stdVals.html">stdVals</a></span> (standard values) specifies the format used when standardized date or number values are supplied.</li></ul> <p>In most cases, attributes bearing standardized values (such as the <span class="att">when</span> or <span class="att">when-iso</span> attribute on dates) should conform to a defined W3C or ISO datatype. In cases where this is not appropriate, this element may be used to describe the standardization methods underlying the values supplied. </p></dd><dt><span><a class="gi" title="describes the scope of any analytic or interpretive information added to the text in addition to the transcription." href="ref-interpretation.html">interpretation</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-interpretation.html">interpretation</a></span> describes the scope of any analytic or interpretive information added to the text in addition to the transcription.</li></ul> <p>Has any analytic or ‘interpretive’ information been provided—that is, information which is felt to be non-obvious, or potentially contentious? If so, how was it generated? How was it encoded? If feature-structure analysis has been used, are <a class="gi" title="(feature system declaration) provides a feature system declaration comprising one or more feature structure declarations or feature structure declaration links." href="ref-fsdDecl.html">fsdDecl</a> elements (section <a class="link_ptr" href="FS.html#FD" title="26"><span class="headingNumber">18.11 </span>Feature System Declaration</a>) present?</p></dd><dt><span><a class="gi" title="specifies editorial practice adopted with respect to punctuation marks in the original." href="ref-punctuation.html">punctuation</a></span></dt><dd><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-punctuation.html">punctuation</a></span> specifies editorial practice adopted with respect to punctuation marks in the original.</li></ul> <p>How has the encoding of punctuation marks present in the original source been treated? For example, has it been normalised, or suppressed in favour of descriptive markup? If it has been retained, is it located within or around elements such as <a class="gi" title="(quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text." href="ref-quote.html">quote</a> which are normally associuated with quotations?</p></dd></dl><div class="p">Any information about the editorial principles applied not falling under one of the above headings should be recorded in a distinct list of items. Experience shows that a full record should be kept of decisions relating to editorial principles and encoding practice, both for future users of the text and for the project which produced the text in the first instance. Some simple examples follow: <div id="index-egXML-d52e22530" class="pre egXML_valid"><span class="element"><editorialDecl></span><br /> <span class="element"><segmentation></span><br /> <span class="element"><p></span><br /> <span class="element"><gi></span>s<span class="element"></gi></span> elements mark orthographic sentences and<br /> are numbered sequentially<br /> within their parent <span class="element"><gi></span>div<span class="element"></gi></span> element<br /> <span class="element"></p></span><br /> <span class="element"></segmentation></span><br /> <span class="element"><interpretation></span><br /> <span class="element"><p></span>The part of speech analysis applied throughout section 4 was<br /> added by hand and has not been checked.<span class="element"></p></span><br /> <span class="element"></interpretation></span><br /> <span class="element"><correction></span><br /> <span class="element"><p></span>Errors in transcription controlled by using the<br /> WordPerfect spelling checker.<span class="element"></p></span><br /> <span class="element"></correction></span><br /> <span class="element"><normalization <span class="attribute">source</span>="<span class="attributevalue">http://szotar.sztaki.hu/webster/</span>"></span><br /> <span class="element"><p></span>All words converted to Modern American spelling following<br /> Websters 9th Collegiate dictionary.<span class="element"></p></span><br /> <span class="element"></normalization></span><br /> <span class="element"><quotation <span class="attribute">marks</span>="<span class="attributevalue">all</span>"></span><br /> <span class="element"><p></span>All opening quotation marks represented by entity reference<br /> <span class="element"><ident <span class="attribute">type</span>="<span class="attributevalue">ge</span>"></span>odq<span class="element"></ident></span>; all closing quotation marks<br /> represented by entity reference <span class="element"><ident <span class="attribute">type</span>="<span class="attributevalue">ge</span>"></span>cdq<span class="element"></ident></span>.<span class="element"></p></span><br /> <span class="element"></quotation></span><br /><span class="element"></editorialDecl></span></div></div><p>An editorial practices declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the <span class="att">decls</span> attribute of each text (or subdivision of the text) to which it applies may be used to supply a cross-reference to it, as further described in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a>.</p></div><div class="div3" id="HD57"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD53"><span class="headingNumber">2.3.3 </span>The Editorial Practices Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD57-1a"><span class="headingNumber">2.3.5 </span>The Default Style Definition Language Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD57" title="link to this section "><span class="invisible">TEI: The Tagging Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.4 </span><span class="head">The Tagging Declaration</span></h4><p>The <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> element is used to record the following information about the tagging used within a particular document: </p><ul class="bulleted"><li class="item">the namespace to which elements appearing within the transcribed text belong.</li><li class="item">how often particular elements appear within the text, so that a recipient can validate the integrity of a text during interchange.</li><li class="item">any comment relating to the usage of particular elements not specified elsewhere in the header.</li><li class="item">a default rendition applicable to all instances of an element.</li></ul><p>This information is conveyed by the following elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-rendition.html">rendition</a></span> supplies information about the rendition or appearance of one or more elements in the source text.<table class="specDesc"><tr><td class="Attribute"><span class="att">selector</span></td><td>contains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the <span class="att">scheme</span> attribute.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-att.styleDef.html">att.styleDef</a></span> provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.<table class="specDesc"><tr><td class="Attribute"><span class="att">scheme</span></td><td>identifies the language used to describe the rendition.</td></tr><tr><td class="Attribute"><span class="att">schemeVersion</span></td><td>supplies a version number for the style language provided in <span class="att">scheme</span>.</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-namespace.html">namespace</a></span> supplies the formal name of the namespace to which the elements documented by its children belong.</li><li><span class="specList-elementSpec"><a href="ref-tagUsage.html">tagUsage</a></span> documents the usage of a specific element within a specified document.</li></ul><p>The <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> element is descriptive, rather than prescriptive: if used, it simply documents practice in the TEI document containing it. The elements constituting a TEI customization file (discussed in chapter <a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a>) by contrast document expected practice in a number of documents, and may thus be used prescriptively. If there is an inconsistency between the actual state of a document and what is documented by its <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a>, then the latter should be corrected. If there is an inconsistency between a document and what is required by the customization file, or a schema derived from it, then it will usually be the document that requires correction.</p><p>The <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> element consists of an optional sequence of <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> elements, each of which must bear a unique identifier, followed by an optional sequence of one or more <a class="gi" title="supplies the formal name of the namespace to which the elements documented by its children belong." href="ref-namespace.html">namespace</a> elements, each of which contains a series of <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> elements, up to one for each element type from that namespace occurring within the associated <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a> element. Note that these <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> elements must be nested within a <a class="gi" title="supplies the formal name of the namespace to which the elements documented by its children belong." href="ref-namespace.html">namespace</a> element, and cannot appear directly within the <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> element.</p><div class="teidiv3" id="HD57-1"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD57-2"><span class="headingNumber">2.3.4.2 </span>Tag Usage</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h5><span class="bookmarklink"><a class="bookmarklink" href="#HD57-1" title="link to this section "><span class="invisible">TEI: Rendition</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.4.1 </span><span class="head">Rendition</span></h5><p>The <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> element allows the encoder to specify how one or more elements are rendered in the original source in any of the following ways: </p><ul class="bulleted"><li class="item">using an informal prose description</li><li class="item">using a standard stylesheet language such as CSS or XSL-FO</li><li class="item">using a project-defined formal language</li></ul><p>One or more such specifications may be associated with elements of a document in two ways: </p><ul class="bulleted"><li class="item">the <span class="att">selector</span> attribute on any <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> element may be used to select a collection of elements to which it applies</li><li class="item">the global <span class="att">rendition</span> attribute may be used on any element to indicate its rendition, overriding or complementing any supplied default value</li></ul><p> The global <span class="att">rend</span> and <span class="att">style</span> attributes may also be used to describe the rendering of an element. See further <a class="link_ptr" href="ST.html#STGAre" title="Rendition Indicators"><span class="headingNumber">1.3.1.1.3 </span>Rendition Indicators</a>.</p><p>The content of a <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> element may describe the appearance of the source material using prose, a project-defined formal language, or any standard languages such as the Cascading Stylesheet Language (<a class="link_ptr" href="BIB.html#CSS21" title="Bert Bos Tantek Çelik Ian Hickson Håkon Wium Lie Cascading Style Sheets Level 2 Revision 1W3C7 June 2011">Bos et al. (eds.) (2011)</a>) or the XML vocabulary for specifying formatting semantics which forms a part of the W3C's Extensible Stylesheet Language (<a class="link_ptr" href="BIB.html#XSL11" title="Anders Berglund Extensible Stylesheet Language (XSL) Version 1.1W3C5 December 2006">Berglund (ed.) (2006)</a>). A <a class="gi" title="(style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied." href="ref-styleDefDecl.html">styleDefDecl</a> element (<a class="link_ptr" href="HD.html#HD57-1a" title="The Default Style Definition Language Declaration"><span class="headingNumber">2.3.5 </span>The Default Style Definition Language Declaration</a>) may be supplied within the <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> to specify which of these applies by default, and it may be overridden for one or more specific <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> elements using the <span class="att">scheme</span> attribute.</p><div class="p">The recommended way to indicate a default rendition on one or more elements is to use the <span class="att">selector</span> attribute together with the <span class="att">scheme</span> attribute on <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a>. For example, suppose that all paragraphs in the <a class="gi" title="(front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body." href="ref-front.html">front</a> of a text appear in a large font, with significant top and bottom margins, while paragraphs in the main <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> are in regular font size and have no top and bottom margins. The use of <span class="att">selector</span> together with <span class="att">scheme</span> provides an efficient way to specify the distinct styling for distinct contexts of the paragraph by means of CSS selectors: <div id="index-egXML-d52e23713" class="pre egXML_valid"><span class="element"><rendition <span class="attribute">scheme</span>="<span class="attributevalue">css</span>" <span class="attribute">selector</span>="<span class="attributevalue">front p</span>"></span> <br /> font-size: 110%;<br /> margin-top: 0.5em;<br /> margin-bottom: 0.5em;<br /> <span class="element"></rendition></span></div> <div id="index-egXML-d52e23717" class="pre egXML_valid"><span class="element"><rendition <span class="attribute">scheme</span>="<span class="attributevalue">css</span>" <span class="attribute">selector</span>="<span class="attributevalue">body p</span>"></span> <br /> font-size: 100%;<br /> margin-top: 0;<br /> margin-bottom: 0;<br /> <span class="element"></rendition></span></div></div><p>In the following extended example we consider how to capture the appearance of a typical early 20th century titlepage, such as that in the following figure: </p><figure class="figure"><div style="float: right;"><a href="BIB.html#HD-eg-swinb">bibliography</a></div><img src="Images/HDswinburne.jpg" alt="" class="graphic" style=" height:400px;" /></figure><p> Elements for the encoding of the information on a titlepage are presented in <a class="link_ptr" href="DS.html#DSTITL" title="Title Pages"><span class="headingNumber">4.6 </span>Title Pages</a>; here we consider how we might go about encoding some of the visual information as well, using the <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> element and its corresponding attributes.</p><div class="p">First we define a rendition element for each aspect of the source page rendition that we wish to retain. Details of CSS are given in <a class="link_ptr" href="BIB.html#CSS21" title="Bert Bos Tantek Çelik Ian Hickson Håkon Wium Lie Cascading Style Sheets Level 2 Revision 1W3C7 June 2011">Bos et al. (eds.) (2011)</a>; we use it here simply to provide a vocabulary with which to describe such aspects as font size and style, letter and line spacing, colour, etc. Note that the purpose of this encoding is to describe the original, rather than specify how it should be reproduced, although the two are obviously closely linked. <div id="index-egXML-d52e23735" class="pre egXML_valid"><span class="element"><styleDefDecl <span class="attribute">scheme</span>="<span class="attributevalue">css</span>"<br /> <span class="attribute">schemeVersion</span>="<span class="attributevalue">2.1</span>"/></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><tagsDecl></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">center</span>"></span>text-align: center;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">small</span>"></span>font-size: small;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">large</span>"></span>font-size: large;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">x-large</span>"></span>font-size: x-large;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">xx-large</span>"></span>font-size: xx-large<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">expanded</span>"></span>letter-spacing: +3pt;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">x-space</span>"></span>line-height: 150%;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">xx-space</span>"></span>line-height: 200%;<span class="element"></rendition></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">red</span>"></span>color: red;<span class="element"></rendition></span><br /><span class="element"></tagsDecl></span></div></div><div class="p">The global <span class="att">rendition</span> attribute can now be used to specify on any element which of the above rendition features apply to it. For example, a title page might be encoded as follows: <div id="index-egXML-d52e23763" class="pre egXML_valid"><span class="element"><titlePage></span><br /> <span class="element"><docTitle <span class="attribute">rendition</span>="<span class="attributevalue">#center #x-space</span>"></span><br /> <span class="element"><titlePart></span><br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#x-large</span>"></span>THE POEMS<span class="element"></hi></span><br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#small</span>"></span>OF<span class="element"></hi></span><br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#red #xx-large</span>"></span>ALGERNON CHARLES SWINBURNE<span class="element"></hi></span><br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#large #xx-space</span>"></span>IN SIX VOLUMES<span class="element"></hi></span><br /> <span class="element"></titlePart></span><br /> <span class="element"><titlePart <span class="attribute">rendition</span>="<span class="attributevalue">#xx-space</span>"></span><br /> <span class="element"><lb/></span> VOLUME I.<br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#red #x-large</span>"></span>POEMS AND BALLADS<span class="element"></hi></span><br /> <span class="element"><lb/></span><br /> <span class="element"><hi <span class="attribute">rendition</span>="<span class="attributevalue">#x-space</span>"></span>FIRST SERIES<span class="element"></hi></span><span class="element"></titlePart></span><br /> <span class="element"></docTitle></span><br /> <span class="element"><docImprint <span class="attribute">rendition</span>="<span class="attributevalue">#center</span>"></span><br /> <span class="element"><lb/></span><br /> <span class="element"><pubPlace <span class="attribute">rendition</span>="<span class="attributevalue">#xx-space</span>"></span>LONDON<span class="element"></pubPlace></span><br /> <span class="element"><lb/></span><br /> <span class="element"><publisher <span class="attribute">rendition</span>="<span class="attributevalue">#red #expanded</span>"></span>CHATTO &amp; WINDUS<span class="element"></publisher></span><br /> <span class="element"><lb/></span><br /> <span class="element"><docDate <span class="attribute">when</span>="<span class="attributevalue">1904</span>" <span class="attribute">rendition</span>="<span class="attributevalue">#small</span>"></span>1904<span class="element"></docDate></span><br /> <span class="element"></docImprint></span><br /><span class="element"></titlePage></span><div style="float: right;"><a href="BIB.html#HD-eg-swinb">bibliography</a> </div></div></div><p>When CSS is used as the style definition language, the <span class="att">scope</span> attribute may be used to specify CSS pseudo-elements. These pseudo-elements are used to specify styling applicable to only a portion of the given text. For example, the <code>first-letter</code> pseudo-element defines styling to be applied to the first letter in the targeted element, while the <code>before</code> and <code>after</code> pseudo-elements can be used often in conjunction with the "content" property to add additional characters which need to be added before or after the element content to make it more closely resemble the appearance of the source.</p><div class="p">For example, assuming that a text has been encoded using the <a class="gi" title="(quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used." href="ref-q.html">q</a> element to enclose passages in quotation marks, but the quotation marks themselves have been routinely omitted from the encoding, a set of renditions such as the following: <div id="index-egXML-d52e23817" class="pre egXML_valid"><span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">quoteBefore</span>"<br /> <span class="attribute">scheme</span>="<span class="attributevalue">css</span>" <span class="attribute">scope</span>="<span class="attributevalue">before</span>"></span>content:<br /> '“';<span class="element"></rendition></span><br /><span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">quoteAfter</span>" <span class="attribute">scheme</span>="<span class="attributevalue">css</span>"<br /> <span class="attribute">scope</span>="<span class="attributevalue">after</span>"></span>content:<br /> '”';<span class="element"></rendition></span></div> might be used to predefine pseudo-elements <code>quoteBefore</code> and <code>quoteAfter</code>. Where a <a class="gi" title="(quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used." href="ref-q.html">q</a> element is actually rendered in the source with initial and final quotation marks, it may then be encoded as follows: <div id="index-egXML-d52e23833" class="pre egXML_valid"><span class="element"><q <span class="attribute">rendition</span>="<span class="attributevalue">#quoteBefore #quoteAfter</span>"></span>Four score and seven years<br /> ago...<span class="element"></q></span></div></div></div><div class="teidiv3" id="HD57-2"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD57-1"><span class="headingNumber">2.3.4.1 </span>Rendition</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h5><span class="bookmarklink"><a class="bookmarklink" href="#HD57-2" title="link to this section "><span class="invisible">TEI: Tag Usage</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.4.2 </span><span class="head">Tag Usage</span></h5><p>As noted above, each <a class="gi" title="supplies the formal name of the namespace to which the elements documented by its children belong." href="ref-namespace.html">namespace</a> element, if present, should contain up to one occurrence of a <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> element for each element type from the given namespace that occurs within the outermost <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a> element associated with the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> in which it appears.<span id="Note44_return"><a class="notelink" title="In the case of a TEI corpus (), a tagsDecl in a corpus header will describe tag usage across the whole corpus, while one in an individual text header …" href="#Note44"><sup>7</sup></a></span> The <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> element may be used to supply a count of the number of occurrences of this element within the text, which is given as the value of its <span class="att">occurs</span> attribute. It may also be used to hold any additional usage information, which is supplied as running prose within the element itself.</p><div class="p">For example: <div id="index-egXML-d52e23871" class="pre egXML_valid"><span class="element"><tagUsage <span class="attribute">gi</span>="<span class="attributevalue">hi</span>" <span class="attribute">occurs</span>="<span class="attributevalue">28</span>"></span> Used only to mark English words italicised in the copy text.<br /> <span class="element"></tagUsage></span></div> This indicates that the <a class="gi" title="(highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made." href="ref-hi.html">hi</a> element appears a total of 28 times in the <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a> element in question, and that the encoder has used it to mark italicised English words only.</div><div class="p">The <span class="att">withId</span> attribute may optionally be used to specify how many of the occurrences of the element in question bear a value for the global <span class="att">xml:id</span> attribute, as in the following example: <div id="index-egXML-d52e23889" class="pre egXML_valid"><span class="element"><tagUsage <span class="attribute">gi</span>="<span class="attributevalue">pb</span>" <span class="attribute">occurs</span>="<span class="attributevalue">321</span>" <span class="attribute">withId</span>="<span class="attributevalue">321</span>"></span> Marks page breaks in the York<br /> (1734) edition only <span class="element"></tagUsage></span></div> This indicates that the <a class="gi" title="(page break) marks the start of a new page in a paginated document." href="ref-pb.html">pb</a> element occurs 321 times, on each of which an identifier is provided.</div><p>The content of the <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> element is not susceptible of automatic processing. It should not therefore be used to hold information for which provision is already made by other components of the encoding description. A TEI-conformant document is not required to provide any <a class="gi" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> elements or <span class="att">occurs</span> attributes, but if it does, then the counts provided must correspond with the number of such elements present in the associated <a class="gi" title="contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample." href="ref-text.html">text</a>. </p></div></div><div class="teidiv2" id="HD57-1a"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD57"><span class="headingNumber">2.3.4 </span>The Tagging Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD54"><span class="headingNumber">2.3.6 </span>The Reference System Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD57-1a" title="link to this section "><span class="invisible">TEI: The Default Style Definition Language Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.5 </span><span class="head">The Default Style Definition Language Declaration</span></h4><p>The content of the <a class="gi" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> element, the value of its <span class="att">selector</span> attribute, and the value of the <span class="att">style</span> attribute are expressed using one of a small number of formally defined style definition languages. For ease of processing, it is strongly recommended to use a single such language throughout an encoding project, although the TEI system permits a mixture.</p><p>The element <a class="gi" title="(style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied." href="ref-styleDefDecl.html">styleDefDecl</a>, a sibling of the <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> element, is used to supply the name of the default style definition language. The name is supplied as the value of the <span class="att">scheme</span> attribute and may take any of the following values: </p><dl><dt><span>free</span></dt><dd>Informal free text description</dd><dt><span>css</span></dt><dd>Cascading Stylesheet Language</dd><dt><span>xslfo</span></dt><dd>Extensible Stylesheet Language Formatting Objects</dd><dt><span>other</span></dt><dd>A user-defined formal description language</dd></dl><p>. The <span class="att">schemeVersion</span> attribute may be used to supply the precise version of the style definition language used, and the content of this element, if any, may supply additional information.</p><p>When the <span class="att">style</span> attribute is used, its value must always be expressed using whichever default style definition language is in force. If more than one occurrence of the <a class="gi" title="(style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied." href="ref-styleDefDecl.html">styleDefDecl</a> is provided, there will be more than one default available, and the <span class="att">decls</span> attribute must be used to select which is applicable in a given context, as discussed in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a>.</p></div><div class="div3" id="HD54"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD57-1a"><span class="headingNumber">2.3.5 </span>The Default Style Definition Language Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD55"><span class="headingNumber">2.3.7 </span>The Classification Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD54" title="link to this section "><span class="invisible">TEI: The Reference System Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.6 </span><span class="head">The Reference System Declaration</span></h4><p>The <a class="gi" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a> element is used to document the way in which any standard referencing scheme built into the encoding works. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-refsDecl.html">refsDecl</a></span> (references declaration) specifies how canonical references are constructed for this text.</li></ul><p> It may contain either a series of prose paragraphs or the following specialized elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-cRefPattern.html">cRefPattern</a></span> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI.</li><li><span class="specList-elementSpec"><a href="ref-refState.html">refState</a></span> (reference state) specifies one component of a canonical reference defined by the milestone method.</li><li><span class="specList-classSpec"><a href="ref-att.patternReplacement.html">att.patternReplacement</a></span> provides attributes for regular-expression matching and replacement.<table class="specDesc"><tr><td class="Attribute"><span class="att">matchPattern</span></td><td>specifies a regular expression against which the values of other attributes can be matched.</td></tr><tr><td class="Attribute"><span class="att">replacementPattern</span></td><td>specifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the <span class="att">matchPattern</span> which, once subpattern substitution has been performed, complete the URI.</td></tr></table></li></ul><p> Note that not all possible referencing schemes are equally easily supported by current software systems. A choice must be made between the convenience of the encoder and the likely efficiency of the particular software applications envisaged, in this context as in many others. For a more detailed discussion of referencing systems supported by these Guidelines, see section <a class="link_ptr" href="CO.html#CORS" title="Reference Systems"><span class="headingNumber">3.10 </span>Reference Systems</a> below.</p><p>A referencing scheme may be described in one of three ways using this element: </p><ul class="bulleted"><li class="item">as a prose description</li><li class="item">as a series of pairs of regular expressions and XPaths</li><li class="item">as a concatenation of sequentially organized <span class="term">milestone</span>s</li></ul><p> Each method is described in more detail below. Only one method can be used within a single <a class="gi" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a> element.</p><p>More than one <a class="gi" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a> element can be included in the header if more than one canonical reference scheme is to be used in the same document, but the current proposals do not check for mutual inconsistency.</p><div class="div4" id="HD54P"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD54S"><span class="headingNumber">2.3.6.2 </span>Search-and-Replace Method</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h5><span class="bookmarklink"><a class="bookmarklink" href="#HD54P" title="link to this section "><span class="invisible">TEI: Prose Method</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.6.1 </span><span class="head">Prose Method</span></h5><p>The referencing scheme may be specified within the <a class="gi" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a> by a simple prose description. Such a description should indicate which elements carry identifying information, and whether this information is represented as attribute values or as content. Any special rules about how the information is to be interpreted when reading or generating a reference string should also be specified here. Such a prose description cannot be processed automatically, and this method of specifying the structure of a canonical reference system is therefore not recommended for automatic processing.</p><div class="p">For example: <div id="index-egXML-d52e24489" class="pre egXML_valid"><span class="element"><refsDecl></span><br /> <span class="element"><p></span>The <span class="element"><att></span>n<span class="element"></att></span> attribute of each text in this corpus carries a<br /> unique identifying code for the whole text. The title of the text is<br /> held as the content of the first <span class="element"><gi></span>head<span class="element"></gi></span> element within each<br /> text. The <span class="element"><att></span>n<span class="element"></att></span> attribute on each <span class="element"><gi></span>div1<span class="element"></gi></span> and<br /> <span class="element"><gi></span>div2<span class="element"></gi></span> contains the canonical reference for each such<br /> division, in the form 'XX.yyy', where XX is the book number in Roman<br /> numerals, and yyy the section number in arabic. Line breaks are<br /> marked by empty <span class="element"><gi></span>lb<span class="element"></gi></span> elements, each of which includes the<br /> through line number in Casaubon's edition as the value of its<br /> <span class="element"><gi></span>n<span class="element"></gi></span> attribute.<span class="element"></p></span><br /> <span class="element"><p></span>The through line number and the text identifier uniquely identify<br /> any line. A canonical reference may be made up by concatenating the<br /> <span class="element"><gi></span>n<span class="element"></gi></span> values from the <span class="element"><gi></span>text<span class="element"></gi></span>, <span class="element"><gi></span>div1<span class="element"></gi></span>, or<br /> <span class="element"><gi></span>div2<span class="element"></gi></span> and calculating the line number within each part.<span class="element"></p></span><br /><span class="element"></refsDecl></span></div></div></div><div class="div4" id="HD54S"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD54P"><span class="headingNumber">2.3.6.1 </span>Prose Method</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD54M"><span class="headingNumber">2.3.6.3 </span>Milestone Method</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h5><span class="bookmarklink"><a class="bookmarklink" href="#HD54S" title="link to this section "><span class="invisible">TEI: Search-and-Replace Method</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.6.2 </span><span class="head">Search-and-Replace Method</span></h5><p>This method often requires a significant investment of effort initially, but permits extremely flexible addressing. For details, see section <a class="link_ptr" href="SA.html#SACR" title="Canonical References"><span class="headingNumber">16.2.5 </span>Canonical References</a>. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-cRefPattern.html">cRefPattern</a></span> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI.</li></ul></div><div class="div4" id="HD54M"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD54S"><span class="headingNumber">2.3.6.2 </span>Search-and-Replace Method</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h5><span class="bookmarklink"><a class="bookmarklink" href="#HD54M" title="link to this section "><span class="invisible">TEI: Milestone Method</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.6.3 </span><span class="head">Milestone Method</span></h5><p>This method is appropriate when only ‘milestone’ tags (see section <a class="link_ptr" href="CO.html#CORS5" title="Milestone Elements"><span class="headingNumber">3.10.3 </span>Milestone Elements</a>) are available to provide the required referencing information. It does not provide any abilities which cannot be mimicked by the search-and-replace referencing method discussed in the previous section, but in the cases where it applies, it provides a somewhat simpler notation.</p><p>A reference based on milestone tags concatenates the values specified by one or more such tags. Since each tag marks the point at which a value changes, it may be regarded as specifying the <span class="term">refState</span> of a variable. A reference declaration using this method therefore specifies the individual components of the canonical reference as a sequence of <a class="gi" title="(reference state) specifies one component of a canonical reference defined by the milestone method." href="ref-refState.html">refState</a> elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-refState.html">refState</a></span> (reference state) specifies one component of a canonical reference defined by the milestone method.<table class="specDesc"><tr><td class="Attribute"><span class="att">delim</span></td><td>(delimiter) supplies a delimiting string following the reference component.</td></tr><tr><td class="Attribute"><span class="att">length</span></td><td>specifies the fixed length of the reference component.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-att.milestoneUnit.html">att.milestoneUnit</a></span> provides an attribute to indicate the type of section which is changing at a specific milestone.<table class="specDesc"><tr><td class="Attribute"><span class="att">unit</span></td><td>provides a conventional name for the kind of section changing at this milestone.
Suggested values include: 1] page; 2] column; 3] line; 4] book; 5] poem; 6] canto; 7] speaker; 8] stanza; 9] act; 10] scene; 11] section; 12] absent; 13] unnumbered</td></tr></table></li></ul><p>For example, the reference <span class="q">‘Matthew 12:34’</span> might be thought of as representing the state of three variables: the <span class="ident">book</span> variable is in state <span class="q">‘Matthew’</span>; the <span class="ident">chapter</span> variable is in state <span class="q">‘12’</span>, and the <span class="ident">verse</span> variable is in state <span class="q">‘34’</span>. If milestone tagging has been used, there should be a tag marking the point in the text at which each of the above ‘variables’ changes its state.<span id="Note45_return"><a class="notelink" title="On the milestone tag itself, what are here referred to as variables are identified by the combination of the ed and unit attributes." href="#Note45"><sup>8</sup></a></span> To find <span class="q">‘Matthew 12:34’</span> therefore an application must scan left to right through the text, monitoring changes in the state of each of these three variables as it does so. When all three are simultaneously in the required state, the desired point will have been reached. There may of course be several such points.</p><p>The <span class="att">delim</span> and <span class="att">length</span> attributes are used to specify components of a canonical reference using this method in exactly the same way as for the stepwise method described in the preceding section. The other attributes are used to determine which instances of <a class="gi" title="marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element." href="ref-milestone.html">milestone</a> tags in the text are to be checked for state-changes. A state-change is signalled whenever a new <a class="gi" title="marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element." href="ref-milestone.html">milestone</a> tag is found with <span class="att">unit</span> and, optionally, <span class="att">ed</span> attributes identical to those of the <a class="gi" title="(reference state) specifies one component of a canonical reference defined by the milestone method." href="ref-refState.html">refState</a> element in question. The value for the new state may be given explicitly by the <span class="att">n</span> attribute on the <a class="gi" title="marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element." href="ref-milestone.html">milestone</a> element, or it may be implied, if the <span class="att">n</span> attribute is not specified.</p><div class="p">For example, for canonical references in the form <span class="mentioned">xx.yyy</span> where the <span class="mentioned">xx</span> represents the page number in the first edition, and <span class="mentioned">yyy</span> the line number within this page, a reference system declaration such as the following would be appropriate: <div id="index-egXML-d52e24651" class="pre egXML_valid"><span class="element"><refsDecl></span><br /> <span class="element"><refState <span class="attribute">ed</span>="<span class="attributevalue">first</span>" <span class="attribute">unit</span>="<span class="attributevalue">page</span>" <span class="attribute">length</span>="<span class="attributevalue">2</span>"<br /> <span class="attribute">delim</span>="<span class="attributevalue">.</span>"/></span><br /> <span class="element"><refState <span class="attribute">ed</span>="<span class="attributevalue">first</span>" <span class="attribute">unit</span>="<span class="attributevalue">line</span>" <span class="attribute">length</span>="<span class="attributevalue">3</span>"/></span><br /><span class="element"></refsDecl></span></div> This implies that milestone tags of the form <div id="index-egXML-d52e24656" class="pre egXML_valid"><span class="element"><milestone <span class="attribute">n</span>="<span class="attributevalue">II</span>" <span class="attribute">ed</span>="<span class="attributevalue">first</span>" <span class="attribute">unit</span>="<span class="attributevalue">page</span>"/></span><br /><span class="element"><milestone <span class="attribute">ed</span>="<span class="attributevalue">first</span>" <span class="attribute">unit</span>="<span class="attributevalue">line</span>"/></span></div> will be found throughout the text, marking the positions at which page and line numbers change. Note that no value has been specified for the <span class="att">n</span> attribute on the second milestone tag above; this implies that its value at each state change is monotonically increased. For more detail on the use of milestone tags, see section <a class="link_ptr" href="CO.html#CORS5" title="Milestone Elements"><span class="headingNumber">3.10.3 </span>Milestone Elements</a>. </div><p>The milestone referencing scheme, though conceptually simple, is not supported by a generic XML parser. Its use places a correspondingly greater burden of verification and accuracy on the encoder.</p><p>A reference system declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the <span class="att">decls</span> attribute of each text (or subdivision of the text) to which the declaration applies may be used to supply a cross-reference to it, as further described in section <a class="link_ptr" href="CC.html#CCAS" title="Associating Contextual Information with a Text"><span class="headingNumber">15.3 </span>Associating Contextual Information with a Text</a>.</p></div></div><div class="div3" id="HD55"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD54"><span class="headingNumber">2.3.6 </span>The Reference System Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HDGDECL"><span class="headingNumber">2.3.8 </span>The Geographic Coordinates Declaration</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD55" title="link to this section "><span class="invisible">TEI: The Classification Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.7 </span><span class="head">The Classification Declaration</span></h4><div class="p">The <a class="gi" title="(classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text." href="ref-classDecl.html">classDecl</a> element is used to group together definitions or sources for any descriptive classification schemes used by other parts of the header or elsewhere in the document. Each such scheme is represented by a <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element, which may contain either a simple bibliographic citation, or a definition of the descriptive typology concerned; the following elements are used in defining a descriptive classification scheme: <ul class="specList"><li><span class="specList-elementSpec"><a href="ref-classDecl.html">classDecl</a></span> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.</li><li><span class="specList-elementSpec"><a href="ref-taxonomy.html">taxonomy</a></span> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.</li><li><span class="specList-elementSpec"><a href="ref-category.html">category</a></span> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.</li><li><span class="specList-elementSpec"><a href="ref-catDesc.html">catDesc</a></span> (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 <a class="gi" title="(text description) provides a description of a text in terms of its situational parameters." href="ref-textDesc.html">textDesc</a>.</li></ul> The <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element has two slightly different, but related, functions. For well-recognized and documented public classification schemes, such as Dewey or other published descriptive thesauri, it contains simply a bibliographic citation indicating where a full description of a particular taxonomy may be found. <div id="index-egXML-d52e25286" class="pre egXML_valid"><span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">DDC12</span>"></span><br /> <span class="element"><bibl></span><br /> <span class="element"><title></span>Dewey Decimal Classification<span class="element"></title></span><br /> <span class="element"><edition></span>Abridged Edition 12<span class="element"></edition></span><br /> <span class="element"></bibl></span><br /><span class="element"></taxonomy></span></div> For less easily accessible schemes, the <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element contains a description of the taxonomy itself as well as an optional bibliographic citation. The description consists of a number of <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> elements, each defining a single category within the given typology. The category is defined by the contents of a nested <a class="gi" title="(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>." href="ref-catDesc.html">catDesc</a> element, which may contain either a phrase describing the category, or any number of elements from the <a class="link_odd" title="groups component elements of the TEI header Category Description." href="ref-model.catDescPart.html">model.catDescPart</a> class. When the corpus module is included in a schema, this class provides the <a class="gi" title="(text description) provides a description of a text in terms of its situational parameters." href="ref-textDesc.html">textDesc</a> element whose components allow the definition of a text type in terms of a set of ‘situational parameters’ (see further section <a class="link_ptr" href="CC.html#CCAHTD" title="The Text Description"><span class="headingNumber">15.2.1 </span>The Text Description</a>; if the corpus module is not included in a schema, this class is empty and the <a class="gi" title="(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>." href="ref-catDesc.html">catDesc</a> element may contain only plain text.</div><div class="p">If the category is subdivided, each subdivision is represented by a nested <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> element, having the same structure. Categories may be nested to an arbitrary depth in order to reflect the hierarchical structure of the taxonomy. Each <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> element bears a unique <span class="att">xml:id</span> attribute, which is used as the target for <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> elements referring to it. <div id="index-egXML-d52e25333" class="pre egXML_valid"><span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">b</span>"></span><br /> <span class="element"><bibl></span>Brown Corpus<span class="element"></bibl></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a</span>"></span><br /> <span class="element"><catDesc></span>Press Reportage<span class="element"></catDesc></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a1</span>"></span><br /> <span class="element"><catDesc></span>Daily<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a2</span>"></span><br /> <span class="element"><catDesc></span>Sunday<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a3</span>"></span><br /> <span class="element"><catDesc></span>National<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a4</span>"></span><br /> <span class="element"><catDesc></span>Provincial<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a5</span>"></span><br /> <span class="element"><catDesc></span>Political<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.a6</span>"></span><br /> <span class="element"><catDesc></span>Sports<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.d</span>"></span><br /> <span class="element"><catDesc></span>Religion<span class="element"></catDesc></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.d1</span>"></span><br /> <span class="element"><catDesc></span>Books<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">b.d2</span>"></span><br /> <span class="element"><catDesc></span>Periodicals and tracts<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"></category></span><br /><span class="element"></taxonomy></span></div></div><div class="p">Linkage between a particular text and a category within such a taxonomy is made by means of the <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> element within the <a class="gi" title="(text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc." href="ref-textClass.html">textClass</a> element, as described in section <a class="link_ptr" href="HD.html#HD43" title="The Text Classification"><span class="headingNumber">2.4.3 </span>The Text Classification</a>. Where finer-grained analysis is desired, a <span class="att">ana</span> attribute on an element in the text could point to a category. Where the taxonomy permits of classification along more than one dimension, more than one category will be referenced by a particular <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a>, as in the following example, which identifies a text with the sub-categories <span class="q">‘Daily’</span>, <span class="q">‘National’</span>, and <span class="q">‘Political’</span> within the category <span class="q">‘Press Reportage’</span> as defined above. <div id="index-egXML-d52e25396" class="pre egXML_valid"><span class="element"><catRef <span class="attribute">target</span>="<span class="attributevalue">#b.a1 #b.a3 #b.a5</span>"/></span></div></div><div class="p">A single <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> may contain more than one <a class="gi" title="(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>." href="ref-catDesc.html">catDesc</a> child, when for example the category is described in more than one language, as in the following example: <div id="index-egXML-d52e25406" class="pre egXML_valid"><span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">lit</span>"></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">pl</span>"></span>literatura piękna<span class="element"></catDesc></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span>fiction<span class="element"></catDesc></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">litProza</span>"></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">pl</span>"></span>proza<span class="element"></catDesc></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span>prose<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">litPoezja</span>"></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">pl</span>"></span>poezja<span class="element"></catDesc></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span>poetry<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /> <span class="element"><category <span class="attribute">xml:id</span>="<span class="attributevalue">litDramat</span>"></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">pl</span>"></span>dramat<span class="element"></catDesc></span><br /> <span class="element"><catDesc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span>drama<span class="element"></catDesc></span><br /> <span class="element"></category></span><br /><span class="element"></category></span></div></div></div><div class="div3" id="HDGDECL"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD55"><span class="headingNumber">2.3.7 </span>The Classification Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HDSCHSPEC"><span class="headingNumber">2.3.9 </span>The Schema Specification</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HDGDECL" title="link to this section "><span class="invisible">TEI: The Geographic Coordinates Declaration</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.8 </span><span class="head">The Geographic Coordinates Declaration</span></h4><p>The following element is provided to indicate (within the header of a document, or in an external location) that a particular coordinate notation, or a particular datum, has been employed in a text. The default notation is a string containing two real numbers separated by whitespace, of which the first indicates latitude and the second longitude according to the 1984 World Geodetic System (WGS84). </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-geoDecl.html">geoDecl</a></span> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <a class="gi" title="(geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation." href="ref-geo.html">geo</a> element elsewhere within the document.<table class="specDesc"><tr><td class="Attribute"><span class="att">datum</span></td><td>supplies a commonly used code name for the datum employed.
Suggested values include: 1] WGS84(World Geodetic System) ; 2] MGRS(Military Grid Reference System) ; 3] OSGB36(ordnance survey great britain) ; 4] ED50(European Datum coordinate system) </td></tr></table></li></ul></div><div class="div3" id="HDSCHSPEC"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HDGDECL"><span class="headingNumber">2.3.8 </span>The Geographic Coordinates Declaration</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HDAPP"><span class="headingNumber">2.3.10 </span>The Application Information Element</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HDSCHSPEC" title="link to this section "><span class="invisible">TEI: The Schema Specification</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.9 </span><span class="head">The Schema Specification</span></h4><p>The <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> element contains a schema specification. When this element appears inside <a class="gi" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a>, it allows embedding of a TEI ODD customization file inside a TEI header; alternatively, this element may be used in the <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> of an ODD document. The use of ODD files, and their relationship to schemas, is described in detail in <a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a>.</p><div class="p">A <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> element contains all the information needed to generate schemas for a particular TEI customization, and the ODD documentation elements, by reference to the TEI, are more succinct than the schemas derived from them. Therefore you may find it convenient to make a copy of the <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> from your project's ODD document inside the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> itself, in addition to supplying an external schema and/or ODD file; if the XML file becomes separated from its schema, the schema can be regenerated at any time using the information in the <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> element. For example: <div id="index-egXML-d52e26185" class="pre egXML_valid"><span class="element"><encodingDesc></span><br /><span class="comment"><!-- Other encoding description elements... --></span><br /> <span class="element"><schemaSpec <span class="attribute">ident</span>="<span class="attributevalue">myTEICustomization</span>"<br /> <span class="attribute">docLang</span>="<span class="attributevalue">en</span>" <span class="attribute">prefix</span>="<span class="attributevalue">tei_</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">core</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">tei</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">header</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">textstructure</span>"/></span><br /> <span class="element"></schemaSpec></span><br /><span class="element"></encodingDesc></span></div></div><div class="p">Alternatively, it is possible to point to an external ODD customization file or schema through use of the <a class="gi" title="(schema reference) describes or points to a related customization or schema file" href="ref-schemaRef.html">schemaRef</a> element. More than one <a class="gi" title="(schema reference) describes or points to a related customization or schema file" href="ref-schemaRef.html">schemaRef</a> element may be provided for different sources, stages in a workflow, or formats. <div id="index-egXML-d52e26202" class="pre egXML_valid"><span class="element"><schemaRef <span class="attribute">type</span>="<span class="attributevalue">interchangeODD</span>"<br /> <span class="attribute">url</span>="<span class="attributevalue">http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd</span>"/></span><br /><span class="element"><schemaRef <span class="attribute">type</span>="<span class="attributevalue">interchangeRNG</span>"<br /> <span class="attribute">url</span>="<span class="attributevalue">http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng</span>"/></span><br /><span class="element"><schemaRef <span class="attribute">type</span>="<span class="attributevalue">projectODD</span>"<br /> <span class="attribute">url</span>="<span class="attributevalue">file:///schema/project.odd</span>"/></span></div> The <span class="att">url</span> attribute may be any form of URI pointer including a private URI syntax documented by a <a class="gi" title="(prefix definition) defines a prefixing scheme used in data.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs." href="ref-prefixDef.html">prefixDef</a>.</div></div><div class="div3" id="HDAPP"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HDSCHSPEC"><span class="headingNumber">2.3.9 </span>The Schema Specification</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HDENCOTH"><span class="headingNumber">2.3.11 </span>Module-Specific Declarations</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HDAPP" title="link to this section "><span class="invisible">TEI: The Application Information Element</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.10 </span><span class="head">The Application Information Element</span></h4><p>It is sometimes convenient to store information relating to the processing of an encoded resource within its header. Typical uses for such information might be: </p><ul class="bulleted"><li class="item">to allow an application to discover that it has previously opened or edited a file, and what version of itself was used to do that;</li><li class="item">to show (through a date) which application last edited the file to allow for diagnosis of any problems that might have been caused by that application;</li><li class="item">to allow users to discover information about an application used to edit the file</li><li class="item">to allow the application to declare an interest in elements of the file which it has edited, so that other applications or human editors may be more wary of making changes to those sections of the file.</li></ul><p>The class <a class="link_odd" title="groups elements used to record application-specific information about a document in its header." href="ref-model.applicationLike.html">model.applicationLike</a> provides an element, <a class="gi" title="provides information about an application which has acted upon the document." href="ref-application.html">application</a>, which may be used to record such information within the <a class="gi" title="(application information) records information about an application which has edited the TEI file." href="ref-appInfo.html">appInfo</a> element.</p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-appInfo.html">appInfo</a></span> (application information) records information about an application which has edited the TEI file.</li><li><span class="specList-elementSpec"><a href="ref-application.html">application</a></span> provides information about an application which has acted upon the document.<table class="specDesc"><tr><td class="Attribute"><span class="att">ident</span></td><td>supplies an identifier for the application, independent of its version number or display name.</td></tr><tr><td class="Attribute"><span class="att">version</span></td><td>supplies a version number for the application, independent of its identifier or display name.</td></tr></table></li></ul><p>Each <a class="gi" title="provides information about an application which has acted upon the document." href="ref-application.html">application</a> element identifies the current state of one software application with regard to the current file. This element is a member of the <a class="link_odd" title="provides attributes for normalization of elements that contain dates, times, or datable events." href="ref-att.datable.html">att.datable</a> class, which provides a variety of attributes for associating this state with a date and time, or a temporal range. The <span class="att">ident</span> and <span class="att">version</span> attributes should be used to uniquely identify the application and its major version number (for example, <span class="val">ImageMarkupTool 1.5</span>). It is not intended that an application should add a new <a class="gi" title="provides information about an application which has acted upon the document." href="ref-application.html">application</a> each time it touches the file.</p><div class="p">The following example shows how these elements might be used to document the fact that version 1.5 of an application called ‘Image Markup Tool’ 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 <a class="gi" title="(pointer) defines a pointer to another location." href="ref-ptr.html">ptr</a> elements. <div id="index-egXML-d52e26272" class="pre egXML_valid"><span class="element"><appInfo></span><br /> <span class="element"><application <span class="attribute">version</span>="<span class="attributevalue">1.5</span>"<br /> <span class="attribute">ident</span>="<span class="attributevalue">ImageMarkupTool</span>" <span class="attribute">notAfter</span>="<span class="attributevalue">2006-06-01</span>"></span><br /> <span class="element"><label></span>Image Markup Tool<span class="element"></label></span><br /> <span class="element"><ptr <span class="attribute">target</span>="<span class="attributevalue">#P1</span>"/></span><br /> <span class="element"><ptr <span class="attribute">target</span>="<span class="attributevalue">#P2</span>"/></span><br /> <span class="element"></application></span><br /><span class="element"></appInfo></span></div></div></div><div class="teidiv2" id="HDENCOTH"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HDAPP"><span class="headingNumber">2.3.10 </span>The Application Information Element</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HDENCOTH" title="link to this section "><span class="invisible">TEI: Module-Specific Declarations</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.3.11 </span><span class="head">Module-Specific Declarations</span></h4><p>The elements discussed so far are available to any schema. When the schema in use includes some of the more specialized TEI modules, these make available other more module-specific components of the encoding description. These are discussed fully in the documentation for the module in question, but are also noted briefly here for convenience. </p><p>The <a class="gi" title="(feature system declaration) provides a feature system declaration comprising one or more feature structure declarations or feature structure declaration links." href="ref-fsdDecl.html">fsdDecl</a> element is available only when the <span class="ident-module">iso-fs</span> module is included in a schema. Its purpose is to document the <span class="term">feature system declaration</span> (as defined in chapter <a class="link_ptr" href="FS.html#FD" title="26"><span class="headingNumber">18.11 </span>Feature System Declaration</a>) underlying any analytic <span class="term">feature structures</span> (as defined in chapter <a class="link_ptr" href="FS.html" title="16"><span class="headingNumber">18 </span>Feature Structures</a>) present in the text documented by this header.</p><p>The <a class="gi" title="(metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a @met, @real, or @rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>)." href="ref-metDecl.html">metDecl</a> element is available only when the <span class="ident-module">verse</span> module is included in a schema. Its purpose is to document any metrical notation scheme used in the text, as further discussed in section <a class="link_ptr" href="VE.html#VEME" title="Rhyme and Metrical Analysis"><span class="headingNumber">6.4 </span>Rhyme and Metrical Analysis</a>. It consists either of a prose description or a series of <a class="gi" title="(metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>." href="ref-metSym.html">metSym</a> elements.</p><p>The <a class="gi" title="declares the method used to encode text-critical variants." href="ref-variantEncoding.html">variantEncoding</a> element is available only when the <span class="ident-module">textcrit</span> module is included in a schema. Its purpose is to document the method used to encode textual variants in the text, as discussed in section <a class="link_ptr" href="TC.html#TCAPLK" title="Linking the Apparatus to the Text"><span class="headingNumber">12.2 </span>Linking the Apparatus to the Text</a>.</p></div></div><div class="div2" id="HD4"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD5"><span class="headingNumber">2.3 </span>The Encoding Description</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD9"><span class="headingNumber">2.5 </span>Non-TEI Metadata</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD4" title="link to this section "><span class="invisible">TEI: The Profile Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4 </span><span class="head">The Profile Description</span></h3><p>The <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element is the third major subdivision of the TEI header. It is an optional element, the purpose of which is to enable information characterizing various descriptive aspects of a text or a corpus to be recorded within a single unified framework. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-profileDesc.html">profileDesc</a></span> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting.</li></ul><p> In principle, almost any component of the header might be of importance as a means of characterizing a text. The author of a written text, its title or its date of publication, may all be regarded as characterizing it at least as strongly as any of the parameters discussed in this section. The rule of thumb applied has been to exclude from discussion here most of the information which generally forms part of a standard bibliographic style description, if only because such information has already been included elsewhere in the TEI header.</p><p>The <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element contains elements taken from the <a class="link_odd" title="groups elements which may be used inside <profileDesc> and appear multiple times." href="ref-model.profileDescPart.html">model.profileDescPart</a> class. The default members of this class are the following : </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-abstract.html">abstract</a></span> contains a summary or formal abstract prefixed to an existing source document by the encoder.</li><li><span class="specList-elementSpec"><a href="ref-creation.html">creation</a></span> contains information about the creation of a text.</li><li><span class="specList-elementSpec"><a href="ref-langUsage.html">langUsage</a></span> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.</li><li><span class="specList-elementSpec"><a href="ref-textClass.html">textClass</a></span> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.</li><li><span class="specList-elementSpec"><a href="ref-correspDesc.html">correspDesc</a></span> (correspondence
description) contains a description of the actions related to one act of correspondence.</li><li><span class="specList-elementSpec"><a href="ref-calendarDesc.html">calendarDesc</a></span> (calendar description) contains a description of the calendar system used in any dating expression found in the text.</li></ul><p> These elements are further described in the remainder of this section.</p><p>When the <span class="ident-module">corpus</span> module described in chapter <a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a> is included in a schema, three further elements become available within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-textDesc.html">textDesc</a></span> (text description) provides a description of a text in terms of its situational parameters.</li><li><span class="specList-elementSpec"><a href="ref-particDesc.html">particDesc</a></span> (participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata.</li><li><span class="specList-elementSpec"><a href="ref-settingDesc.html">settingDesc</a></span> (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata.</li></ul><p> For descriptions of these elements, see section <a class="link_ptr" href="CC.html#CCAH" title="Contextual Information"><span class="headingNumber">15.2 </span>Contextual Information</a>.</p><p>When the <span class="ident-module">transcr</span> module for the transcription of primary sources described in chapter <a class="link_ptr" href="PH.html" title="18"><span class="headingNumber">11 </span>Representation of Primary Sources</a> is included in a schema, the following elements become available within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-handNotes.html">handNotes</a></span> contains one or more <a class="gi" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> elements documenting the different hands identified within the source texts.</li><li><span class="specList-elementSpec"><a href="ref-listTranspose.html">listTranspose</a></span> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks.</li></ul><p> For a description of the <a class="gi" title="contains one or more <handNote> elements documenting the different hands identified within the source texts." href="ref-handNotes.html">handNotes</a> element, see section <a class="link_ptr" href="PH.html#PHDH" title="Document Hands"><span class="headingNumber">11.3.2.1 </span>Document Hands</a>. Its purpose is to group together a number of <a class="gi" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> elements, each of which describes a different hand or equivalent identified within a manuscript. The <a class="gi" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> element can also appear within a structured manuscript description, when the <span class="ident-module">msdescription</span> module described in chapter <a class="link_ptr" href="MS.html" title="Manuscript Description"><span class="headingNumber">10 </span>Manuscript Description</a> is included in a schema. For this reason, the <a class="gi" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> element is actually declared within the header module, but is only accessible to a schema when one or other of the <span class="ident-module">transcr</span> or <span class="ident-module">msdescription</span> modules is included in a schema. See further the discussion at <a class="link_ptr" href="PH.html#PHDH" title="Document Hands"><span class="headingNumber">11.3.2.1 </span>Document Hands</a>.</p><p>The <a class="gi" title="supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks." href="ref-listTranspose.html">listTranspose</a> element is discussed in detail in section <a class="link_ptr" href="PH.html#transpo" title="Transpositions"><span class="headingNumber">11.3.4.5 </span>Transpositions</a>.</p><div class="div3" id="HD4C"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD41"><span class="headingNumber">2.4.2 </span>Language Usage</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD4C" title="link to this section "><span class="invisible">TEI: Creation</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.1 </span><span class="head">Creation</span></h4><div class="p">The <a class="gi" title="contains information about the creation of a text." href="ref-creation.html">creation</a> element contains phrases describing the origin of the text, e.g. the date and place of its composition. <ul class="specList"><li><span class="specList-elementSpec"><a href="ref-creation.html">creation</a></span> contains information about the creation of a text.</li></ul> The date and place of composition are often of particular importance for studies of linguistic variation; since such information cannot be inferred with confidence from the bibliographic description of the copy text, the <a class="gi" title="contains information about the creation of a text." href="ref-creation.html">creation</a> element may be used to provide a consistent location for this information: <div id="index-egXML-d52e26804" class="pre egXML_valid"><span class="element"><creation></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1992-08</span>"></span>August 1992<span class="element"></date></span><br /> <span class="element"><rs <span class="attribute">type</span>="<span class="attributevalue">city</span>"></span>Taos, New Mexico<span class="element"></rs></span><br /><span class="element"></creation></span></div></div></div><div class="div3" id="HD41"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD4C"><span class="headingNumber">2.4.1 </span>Creation</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD43"><span class="headingNumber">2.4.3 </span>The Text Classification</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD41" title="link to this section "><span class="invisible">TEI: Language Usage</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.2 </span><span class="head">Language Usage</span></h4><p>The <a class="gi" title="(language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text." href="ref-langUsage.html">langUsage</a> element is used within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element to describe the languages, sublanguages, registers, dialects, etc. represented within a text. It contains one or more <a class="gi" title="characterizes a single language or sublanguage used within a text." href="ref-language.html">language</a> elements, each of which provides information about a single language, notably the quantity of that language present in the text. Note that this element should <em>not</em> be used to supply information about any non-standard characters or glyphs used by this language; such information should be recorded in the <a class="gi" title="(character declarations) provides information about nonstandard characters and glyphs." href="ref-charDecl.html">charDecl</a> element in the encoding description (see further <a class="link_ptr" href="WD.html" title="25"><span class="headingNumber">5 </span>Characters, Glyphs, and Writing Modes</a>). </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-langUsage.html">langUsage</a></span> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.</li><li><span class="specList-elementSpec"><a href="ref-language.html">language</a></span> characterizes a single language or sublanguage used within a text.<table class="specDesc"><tr><td class="Attribute"><span class="att">usage</span></td><td>specifies the approximate percentage (by volume) of the text which uses this language.</td></tr><tr><td class="Attribute"><span class="att">ident</span></td><td>(identifier) Supplies a language code constructed as defined in <a class="link_ref" href="https://tools.ietf.org/html/bcp47">BCP 47</a> which is used to identify the language documented by this element, and which is referenced by the global <span class="att">xml:lang</span> attribute.</td></tr></table></li></ul><p>A <a class="gi" title="characterizes a single language or sublanguage used within a text." href="ref-language.html">language</a> element may be supplied for each different language used in a document. If used, its <span class="att">ident</span> attribute should specify an appropriate language identifier, as further discussed in section <a class="link_ptr" href="CH.html#CHSH" title="Language Identification"><span class="headingNumber">vi.1. </span>Language Identification</a>. This is particularly important if extended language identifiers have been used as the value of <span class="att">xml:lang</span> attributes elsewhere in the document.</p><div class="p">Here is an example of the use of this element: <div id="index-egXML-d52e26984" class="pre egXML_valid"><span class="element"><langUsage></span><br /> <span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">fr-CA</span>" <span class="attribute">usage</span>="<span class="attributevalue">60</span>"></span>Québecois<span class="element"></language></span><br /> <span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">en-CA</span>" <span class="attribute">usage</span>="<span class="attributevalue">20</span>"></span>Canadian business English<span class="element"></language></span><br /> <span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">en-GB</span>" <span class="attribute">usage</span>="<span class="attributevalue">20</span>"></span>British English<span class="element"></language></span><br /><span class="element"></langUsage></span></div></div></div><div class="div3" id="HD43"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD41"><span class="headingNumber">2.4.2 </span>Language Usage</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD4ABS"><span class="headingNumber">2.4.4 </span>Abstracts</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD43" title="link to this section "><span class="invisible">TEI: The Text Classification</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.3 </span><span class="head">The Text Classification</span></h4><p>The <a class="gi" title="(text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc." href="ref-textClass.html">textClass</a> element is used to classify a text in some way. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-textClass.html">textClass</a></span> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.</li></ul><p>Text classification may be carried out according to one or more of the following methods: </p><ul class="bulleted"><li class="item">by reference to a recognized international classification such as the Dewey Decimal Classification, the Universal Decimal Classification, the Colon Classification, the Library of Congress Classification, or any other system widely used in library and documentation work</li><li class="item">by providing a set of keywords, as provided for example by British Library or Library of Congress Cataloguing in Publication data</li><li class="item">by referencing any other taxonomy of text categories recognized in the field concerned, or peculiar to the material in hand; this may include one based on recurring sets of values for the situational parameters defined in section <a class="link_ptr" href="CC.html#CCAHTD" title="The Text Description"><span class="headingNumber">15.2.1 </span>The Text Description</a>, or the demographic elements described in section <a class="link_ptr" href="CC.html#CCAHPA" title="The Participant Description"><span class="headingNumber">15.2.2 </span>The Participant Description</a></li></ul><p> The last of these may be particularly important for dealing with existing corpora or collections, both as a means of avoiding the expense or inconvenience of reclassification and as a means of documenting the organizing principles of such materials.</p><p>The following elements are provided for this purpose: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-keywords.html">keywords</a></span> contains a list of keywords or phrases identifying the topic or nature of a text.<table class="specDesc"><tr><td class="Attribute"><span class="att">scheme</span></td><td>identifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element, or by some other resource.</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-classCode.html">classCode</a></span> (classification code) contains the classification code used for this text in some standard classification system.<table class="specDesc"><tr><td class="Attribute"><span class="att">scheme</span></td><td>identifies the classification system in use, as defined by, e.g. a <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element, or some other resource.</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-catRef.html">catRef</a></span> (category reference) specifies one or more defined categories within some taxonomy or text typology.</li></ul><p>The <a class="gi" title="contains a list of keywords or phrases identifying the topic or nature of a text." href="ref-keywords.html">keywords</a> element simply categorizes an individual text by supplying a list of keywords which may describe its topic or subject matter, its form, date, etc. In some schemes, the order of items in the list is significant, for example, from major topic to minor; in others, the list has an organized substructure of its own. No recommendations are made here as to which method is to be preferred. Wherever possible, such keywords should be taken from a recognized source, such as the British Library/Library of Congress Cataloguing in Publication data in the case of printed books, or a published thesaurus appropriate to the field.</p><div class="p">The <span class="att">scheme</span> attribute is used to indicate the source of the keywords used, in the case where such a source exists. If the keywords are taken from an externally defined authority which is available online, this attribute should point directly to it, as in the following examples: <div id="index-egXML-d52e27286" class="pre egXML_valid"><span class="element"><keywords <span class="attribute">scheme</span>="<span class="attributevalue">http://classificationweb.net</span>"></span><br /> <span class="element"><term></span>Babbage, Charles<span class="element"></term></span><br /> <span class="element"><term></span>Mathematicians - Great Britain - Biography<span class="element"></term></span><br /><span class="element"></keywords></span></div> <div id="index-egXML-d52e27293" class="pre egXML_valid"><span class="element"><keywords <span class="attribute">scheme</span>="<span class="attributevalue">http://id.loc.gov/authorities/about.html#lcsh</span>"></span><br /> <span class="element"><term></span>English literature -- History and criticism -- Data processing.<span class="element"></term></span><br /> <span class="element"><term></span>English literature -- History and criticism -- Theory, etc.<span class="element"></term></span><br /> <span class="element"><term></span>English language -- Style -- Data processing.<span class="element"></term></span><br /> <span class="element"><term></span>Style, Literary -- Data processing.<span class="element"></term></span><br /><span class="element"></keywords></span></div></div><div class="p">If the authority file is not available online, but is generally recognized and commonly cited, a bibliographic description for it should be supplied within the <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element described in section <a class="link_ptr" href="HD.html#HD55" title="The Classification Declaration"><span class="headingNumber">2.3.7 </span>The Classification Declaration</a>; the <span class="att">scheme</span> attribute may then reference that <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element by means of its identifier in the usual way: <div id="index-egXML-d52e27317" class="pre egXML_valid"><span class="element"><keywords <span class="attribute">scheme</span>="<span class="attributevalue">#welch</span>"></span><br /> <span class="element"><term></span>ceremonials<span class="element"></term></span><br /> <span class="element"><term></span>fairs<span class="element"></term></span><br /> <span class="element"><term></span>street life<span class="element"></term></span><br /><span class="element"></keywords></span><br /><span class="comment"><!-- elsewhere in the document --></span><br /><span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">welch</span>"></span><br /> <span class="element"><bibl></span><br /> <span class="element"><title></span>Notes on London Municipal Literature, and a Suggested<br /> Scheme for Its Classification<span class="element"></title></span><br /> <span class="element"><author></span>Charles Welch<span class="element"></author></span><br /> <span class="element"><edition></span>1895<span class="element"></edition></span><br /> <span class="element"></bibl></span><br /><span class="element"></taxonomy></span></div></div><p>If no authority file exists, perhaps because the keywords used were assigned directly by an author, the <span class="att">scheme</span> attribute should be omitted.</p><p>Alternatively, if the keyword vocabulary itself is locally defined, the <span class="att">scheme</span> attribute will point to the local definition, which will typically be held in a <a class="gi" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> element within the <a class="gi" title="(classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text." href="ref-classDecl.html">classDecl</a> part of the encoding description (see section <a class="link_ptr" href="HD.html#HD55" title="The Classification Declaration"><span class="headingNumber">2.3.7 </span>The Classification Declaration</a>). </p><div class="p">The <a class="gi" title="(classification code) contains the classification code used for this text in some standard classification system." href="ref-classCode.html">classCode</a> element also categorizes an individual text, by supplying a numerical or other code rather than descriptive terms. Such codes constitute a recognized classification scheme, such as the Dewey Decimal Classification. On this element, the <span class="att">scheme</span> attribute is required; it indicates the source of the classification scheme in the same way as for keywords: this may be a pointer of any kind, either to a TEI element, possibly in the current document, as in the <a class="gi" title="contains a list of keywords or phrases identifying the topic or nature of a text." href="ref-keywords.html">keywords</a> examples above, or to some canonical source for the scheme, as in the following example: <div id="index-egXML-d52e27371" class="pre egXML_valid"><span class="element"><classCode <span class="attribute">scheme</span>="<span class="attributevalue">http://www.udcc.org/udcsummary/php/index.php</span>"></span>005.756<span class="element"></classCode></span></div></div><p>The <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> element categorizes an individual text by pointing to one or more <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> elements using the <span class="att">target</span> attribute, which it inherits from the <a class="link_odd" title="provides a set of attributes used by all elements which point to other elements by means of one or more URI references." href="ref-att.pointing.html">att.pointing</a> class. The <a class="gi" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> element (which is fully described in section <a class="link_ptr" href="HD.html#HD55" title="The Classification Declaration"><span class="headingNumber">2.3.7 </span>The Classification Declaration</a>) holds information about a particular classification or category within a given taxonomy. Each such category must have a unique identifier, which may be supplied as the value of the <span class="att">target</span> attribute for <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> elements which are regarded as falling within the category indicated.</p><div class="p">A text may, of course, fall into more than one category, in which case more than one identifier may be supplied as the value for the <span class="att">target</span> attribute on the <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> element, as in the following example: <div id="index-egXML-d52e27410" class="pre egXML_valid"><span class="element"><catRef <span class="attribute">target</span>="<span class="attributevalue">#b.a4 #b.d2</span>"/></span></div></div><div class="p">The <span class="att">scheme</span> attribute may be supplied to specify the taxonomy to which the categories identified by the target attribute belong, if this is not adequately conveyed by the resource pointed to. For example, <div id="index-egXML-d52e27417" class="pre egXML_valid"><span class="element"><catRef <span class="attribute">target</span>="<span class="attributevalue">#b.a4 #b.d2</span>"<br /> <span class="attribute">scheme</span>="<span class="attributevalue">http://www.example.com/browncorpus</span>"/></span><br /><span class="element"><catRef <span class="attribute">target</span>="<span class="attributevalue">http://www.example.com/SUC/#A45</span>"/></span></div> Here the same text has been classified as of categories <span class="val">b.a4</span> and <span class="val">b.d2</span> within the Brown classification scheme (presumed to be available from <span class="ident-file">http://www.example.com/browncorpus</span>), and as of category <span class="q">‘A45’</span> within the SUC classification scheme documented at the URL given.</div><p>In general, it is a matter of style whether to use a single <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> with multiple identifiers in the value of <span class="att">target</span> or multiple <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> elements, each with a single identifier in the value of <span class="att">target</span>. However, note that maintenance of a TEI document with a large number of values within a single <span class="att">target</span> can be cumbersome.</p><p>The distinction between the <a class="gi" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> and <a class="gi" title="(classification code) contains the classification code used for this text in some standard classification system." href="ref-classCode.html">classCode</a> elements is that the values used as identifying codes are exhaustively enumerated for the former, typically within the TEI header. In the latter case, however, the values use any externally-defined scheme, and therefore may be taken from a more open-ended descriptive classification system.</p></div><div class="div3" id="HD4ABS"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD43"><span class="headingNumber">2.4.3 </span>The Text Classification</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD44"><span class="headingNumber">2.4.5 </span>Calendar Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD4ABS" title="link to this section "><span class="invisible">TEI: Abstracts</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.4 </span><span class="head">Abstracts</span></h4><div class="p">The main purpose of the <a class="gi" title="contains a summary or formal abstract prefixed to an existing source document by the encoder." href="ref-abstract.html">abstract</a> element is to supply a brief resume or abstract for an article which was originally published without such a component. An abstract or summary forming part of the document at its creation should usually appear in the front matter (<a class="gi" title="(front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body." href="ref-front.html">front</a>) of the document. <div id="index-egXML-d52e27929" class="pre egXML_valid"><span class="element"><profileDesc></span><br /> <span class="element"><abstract></span><br /> <span class="element"><p></span>This paper is a draft studying<br /> various aspects of using the TEI<br /> as a reference serialization framework<br /> for LMF. Comments are welcome to bring<br /> this to a useful document for the<br /> community.<br /> <span class="element"></p></span><br /> <span class="element"></abstract></span><br /><span class="element"></profileDesc></span></div></div><div class="p">Abstracts may be provided in multiple languages, distinguished by the <span class="att">xml:lang</span> attribute: <div id="index-egXML-d52e27940" class="pre egXML_valid"><span class="element"><profileDesc></span><br /> <span class="element"><abstract <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span><br /> <span class="element"><p></span>The recent archaeological emphasis<br /> on the study of settlement patterns,<br /> landscape and palaeoenvironments has<br /> shaped and re-shaped our understanding<br /> of the Viking settlement of Iceland.<br /> This paper reviews the developments<br /> in Icelandic archaeology, examining<br /> both theoretical and practical advances.<br /> Particular attention is paid to new<br /> ideas in terms of settlement patterns<br /> and resource exploitation. Finally,<br /> some of the key studies of the ecological<br /> consequences of the Norse<br /> <span class="element"><foreign <span class="attribute">xml:lang</span>="<span class="attributevalue">is</span>"></span>landnám<span class="element"></foreign></span> <br /> are presented. <span class="element"></p></span><br /> <span class="element"></abstract></span><br /> <span class="element"><abstract <span class="attribute">xml:lang</span>="<span class="attributevalue">fr</span>"></span><br /> <span class="element"><p></span>L’accent récent des<br /> recherches archéologiques sur l’étude des<br /> configurations spatiales des colonies, de la<br /> géographie des sites ainsi que des éléments<br /> paléo-environnementaux nous mène à réexaminer<br /> et réévaluer nos connaissances acquises sur<br /> la colonisation de l’Islande par les Vikings.<br /> Cet article passe en revue le développement<br /> de l’archéologie islandaise en examinant les<br /> progrès théoriques et pratiques en la matière.<br /> Une attention particulière est portée sur<br /> l’étude des configurations spatiales des<br /> colonies ainsi qu’une considération des<br /> questions d’exploitation des ressources.<br /> Finalement, l’article présente un aperçu des<br /> études principales qui traitent des<br /> conséquences écologiques du<br /> <span class="element"><foreign <span class="attribute">xml:lang</span>="<span class="attributevalue">is</span>"></span>landnám<span class="element"></foreign></span> <br /> islandais.<span class="element"></p></span><br /> <span class="element"></abstract></span><br /><span class="element"></profileDesc></span></div></div><div class="p">The same element may be used to provide other summary information supplied by the encoder, perhaps grouped together into a list of discrete items: <div id="index-egXML-d52e27957" class="pre egXML_valid"><span class="element"><profileDesc></span><br /> <span class="element"><abstract></span><br /> <span class="element"><list></span><br /> <span class="element"><item></span>An annual HBC supply ship is<br /> set to the North West Coast for mid-September.<span class="element"></item></span><br /> <span class="element"><item></span><br /> <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">pelly_jh</span>"></span>Pelly<span class="element"></name></span> writes<br /> to ascertain the British Government's plans<br /> for the lands associated with the Oregon Treaty;<br /> he wants to know what will happen to the HBC's<br /> establishment on the southern <span class="element"><name <span class="attribute">type</span>="<span class="attributevalue">place</span>"<br /> <span class="attribute">key</span>="<span class="attributevalue">vancouver_island</span>"></span>Vancouver Island<span class="element"></name></span>.<br /> He adds that a former Crown grant, an 1838 exclusive<br /> trade-grant for the lands in question, has yet to<br /> expire.<span class="element"></item></span><br /> <span class="element"><item></span>The minutes discuss the nature of the HBC's<br /> original entitlements and question whether or not,<br /> and in what capacity, the Oregon Treaty affects the<br /> HBC's position. The majority council further<br /> investigation, and to reply cautiously and<br /> judiciously to the HBC inquiry.<span class="element"></item></span><br /> <span class="element"><item></span>A<br /> summary of a meeting with <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">pelly_jh</span>"></span>Pelly<span class="element"></name></span> is offered in<br /> order to elucidate the HBC's intentions.<span class="element"></item></span><br /> <span class="element"><item></span><br /> <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">grey_hg</span>"></span>Lord Grey<span class="element"></name></span> calls<br /> for greater consideration on the issue of<br /> colonization; he asks that <span class="element"><name <span class="attribute">key</span>="<span class="attributevalue">stephen_j</span>"></span>Stephen<span class="element"></name></span> write the Company,<br /> asking them to detail their intentions, and to<br /> state their legal opinion for entitlement.<br /> <span class="element"></item></span><br /> <span class="element"></list></span><br /> <span class="element"></abstract></span><br /><span class="element"></profileDesc></span></div></div></div><div class="div3" id="HD44"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD4ABS"><span class="headingNumber">2.4.4 </span>Abstracts</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD44CD"><span class="headingNumber">2.4.6 </span>Correspondence Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD44" title="link to this section "><span class="invisible">TEI: Calendar Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.5 </span><span class="head">Calendar Description</span></h4><p>The <a class="gi" title="(calendar description) contains a description of the calendar system used in any dating expression found in the text." href="ref-calendarDesc.html">calendarDesc</a> element is used within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element to document objects referenced by means of either the <span class="att">calendar</span> attribute on <a class="gi" title="contains a date in any format." href="ref-date.html">date</a> or the <span class="att">datingMethod</span> attribute on any member of the <a class="link_odd" title="provides attributes for normalization of elements that contain dates, times, or datable events." href="ref-att.datable.html">att.datable</a> class. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-calendarDesc.html">calendarDesc</a></span> (calendar description) contains a description of the calendar system used in any dating expression found in the text.</li></ul><p>This element may contain one or more <a class="gi" title="describes a calendar or dating system used in a dating formula in the text." href="ref-calendar.html">calendar</a> elements: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-calendar.html">calendar</a></span> describes a calendar or dating system used in a dating formula in the text.</li></ul><div class="p">Each such element contains one or more paragraphs of description for the calendar system concerned, and also supplies an identifying code for it as the value of its <span class="att">xml:id</span> attribute. <div id="index-egXML-d52e28024" class="pre egXML_valid"><span class="element"><calendarDesc></span><br /> <span class="element"><calendar <span class="attribute">xml:id</span>="<span class="attributevalue">Gregorian</span>"></span><br /> <span class="element"><p></span>Gregorian calendar<span class="element"></p></span><br /> <span class="element"></calendar></span><br /> <span class="element"><calendar <span class="attribute">xml:id</span>="<span class="attributevalue">Stardate</span>"></span><br /> <span class="element"><p></span>Fictional Stardate (from Star Trek series)<span class="element"></p></span><br /> <span class="element"></calendar></span><br /> <span class="element"><calendar <span class="attribute">xml:id</span>="<span class="attributevalue">BP</span>"></span><br /> <span class="element"><p></span>Calendar years before present (measured from 1950)<span class="element"></p></span><br /> <span class="element"></calendar></span><br /><span class="element"></calendarDesc></span></div></div><div class="p">This identifying code may then be referenced from any element supplying a date expressed using that calendar system: <div id="index-egXML-d52e28038" class="pre egXML_valid"><span class="element"><p></span>Captain's log <span class="element"><date <span class="attribute">calendar</span>="<span class="attributevalue">#stardate</span>"></span>stardate 23.9 rounded off<br /> to the nearest decimal point<span class="element"></date></span>...<span class="element"></p></span></div> See <a class="link_ptr" href="ND.html#NDDATECUSTOM" title="Using NonGregorian Calendars"><span class="headingNumber">13.3.6.4 </span>Using Non-Gregorian Calendars</a> for details of the usage of dating attributes in conjunction with <a class="gi" title="describes a calendar or dating system used in a dating formula in the text." href="ref-calendar.html">calendar</a> elements in the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a>.</div></div><div class="div3" id="HD44CD"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD44"><span class="headingNumber">2.4.5 </span>Calendar Description</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#HD44CD" title="link to this section "><span class="invisible">TEI: Correspondence Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.4.6 </span><span class="head">Correspondence Description</span></h4><p>The <a class="gi" title="(correspondence description) contains a description of the actions related to one act of correspondence." href="ref-correspDesc.html">correspDesc</a> element is used within the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> element to provide detailed correspondence-specific metadata, concerning in particular the communicative aspects (sending, receiving, forwarding etc.) associated with an act of correspondence.</p><p>This information is complementary to the detailed descriptions of physical objects (such as letters) associated with correspondence acts, which are typically provided by the <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> element. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-correspDesc.html">correspDesc</a></span> (correspondence
description) contains a description of the actions related to one act of correspondence.</li></ul><p>The <a class="gi" title="(correspondence description) contains a description of the actions related to one act of correspondence." href="ref-correspDesc.html">correspDesc</a> element contains the elements <a class="gi" title="(correspondence action) 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." href="ref-correspAction.html">correspAction</a> and <a class="gi" title="(correspondence context) provides references to preceding or following correspondence related to this piece of correspondence." href="ref-correspContext.html">correspContext</a>, describing the actions identified and the context in which the correspondence occurs respectively. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-correspAction.html">correspAction</a></span> (correspondence action) 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.<table class="specDesc"><tr><td class="Attribute"><span class="att">type</span></td><td>describes the nature of the action.
Suggested values include: 1] sent; 2] received; 3] transmitted; 4] redirected; 5] forwarded</td></tr></table></li><li><span class="specList-elementSpec"><a href="ref-correspContext.html">correspContext</a></span> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence.</li></ul><div class="p">Acts of correspondence typically do not occur in isolation from each other. The <a class="gi" title="(correspondence context) provides references to preceding or following correspondence related to this piece of correspondence." href="ref-correspContext.html">correspContext</a> element is used to group references relevant to the item of correspondence being described, typically to other items such as the item to which it is a reply, or the item which replies to it: <div id="index-egXML-d52e28284" class="pre egXML_valid"><span class="element"><correspContext></span><br /> <span class="element"><ref <span class="attribute">type</span>="<span class="attributevalue">prev</span>" <span class="attribute">target</span>="<span class="attributevalue">#CLF0102</span>"></span>Previous letter of <span class="element"><persName></span>Chamisso<span class="element"></persName></span> to <span class="element"><persName></span>de La<br /> Foye<span class="element"></persName></span>: <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1807-01-16</span>"></span>16 January 1807<span class="element"></date></span><span class="element"></ref></span><br /> <span class="element"><ref <span class="attribute">type</span>="<span class="attributevalue">next</span>" <span class="attribute">target</span>="<span class="attributevalue">#CLF0104</span>"></span>Next letter of <span class="element"><persName></span>Chamisso<span class="element"></persName></span> to <span class="element"><persName></span>de La Foye<span class="element"></persName></span>:<br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1810-05-07</span>"></span>07 May 1810<span class="element"></date></span><span class="element"></ref></span><br /><span class="element"></correspContext></span></div></div><p>Many types of correspondence actions may be distinguished. The <span class="att">type</span> attribute should be used to indicate the type of action being documented, using values such as those suggested above.</p><div class="p">The following simple example uses <a class="gi" title="(correspondence action) 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." href="ref-correspAction.html">correspAction</a> to describe the sending of a letter by Adelbert von Chamisso from Vertus on 29 January 1807 to Louis de La Foye at Caen. The date of reception is unknown: <div id="index-egXML-d52e28318" class="pre egXML_valid"><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">sent</span>"></span><br /> <span class="element"><persName></span>Adelbert von Chamisso<span class="element"></persName></span><br /> <span class="element"><placeName></span>Vertus<span class="element"></placeName></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1807-01-29</span>"/></span><br /><span class="element"></correspAction></span><br /><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>"></span><br /> <span class="element"><persName></span>Louis de La Foye<span class="element"></persName></span><br /> <span class="element"><placeName></span>Caen<span class="element"></placeName></span><br /> <span class="element"><date></span>unknown<span class="element"></date></span><br /><span class="element"></correspAction></span></div> Note the use of the <span class="att">when</span> attribute described in <a class="link_ptr" href="CO.html#CONADA" title="Dates and Times"><span class="headingNumber">3.5.4 </span>Dates and Times</a> to provide a normalized form of the date. The content of the <a class="gi" title="contains a date in any format." href="ref-date.html">date</a> element may be omitted, since no underlying source is being transcribed.</div><div class="p">Several senders, recipients, etc. can be specified for a single <a class="gi" title="(correspondence action) 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." href="ref-correspAction.html">correspAction</a> if the action is considered to apply to them all acting as a single group. In the following example, two people are considered to have received the piece of correspondence. <div id="index-egXML-d52e28346" class="pre egXML_valid"><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>"></span><br /> <span class="element"><persName></span>Hermann Hesse<span class="element"></persName></span><br /> <span class="element"><persName></span>Ninon Hesse<span class="element"></persName></span><br /> <span class="element"><placeName></span>Montagnola<span class="element"></placeName></span><br /><span class="element"></correspAction></span></div></div><div class="p">The <span class="att">subtype</span> attribute may be used to further distinguish types of action. In the following example, an e-mail is sent to two people directly and to a third by ‘carbon copy’ (<span class="term">cc</span>). <div id="index-egXML-d52e28366" class="pre egXML_valid"><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">sent</span>"></span><br /> <span class="element"><persName></span>PN0001<span class="element"></persName></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1999-06-02</span>"/></span><br /><span class="element"></correspAction></span><br /><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>" <span class="attribute">subtype</span>="<span class="attributevalue">to</span>"></span><br /> <span class="element"><persName></span>PN0002<span class="element"></persName></span><br /><span class="element"></correspAction></span><br /><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>" <span class="attribute">subtype</span>="<span class="attributevalue">to</span>"></span><br /> <span class="element"><persName></span>PN0003<span class="element"></persName></span><br /><span class="element"></correspAction></span><br /><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>" <span class="attribute">subtype</span>="<span class="attributevalue">cc</span>"></span><br /> <span class="element"><persName></span>PN0004<span class="element"></persName></span><br /><span class="element"></correspAction></span></div></div><div class="p">The same person may be associated with several actions. For example, it will often be the case that the author and sender of a message are identical, and that many individual letters will need to be associated with the same person. The <span class="att">sameAs</span> attribute defined in section <a class="link_ptr" href="SA.html#SAIE" title="Identical Elements and Virtual Copies"><span class="headingNumber">16.6 </span>Identical Elements and Virtual Copies</a> may be used to indicate that the same name applies to many actions. Its value will usually be the identifier of an element defining the person or name concerned, which is supplied elsewhere in the document. <div id="index-egXML-d52e28388" class="pre egXML_valid"><span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">sent</span>"></span><br /> <span class="element"><name <span class="attribute">sameAs</span>="<span class="attributevalue">#author</span>"/></span><br /><span class="element"></correspAction></span></div> </div><div class="p">It is assumed that each correspondence action applies to a single act of communication. However, it may be the case that the same physical object is involved in several such acts, if for example person A sends a letter to person B, who then annotates it and sends it on to person C, or if persons A and B both use the same document to convey quite different messages. In such situations, multiple <a class="gi" title="(correspondence description) contains a description of the actions related to one act of correspondence." href="ref-correspDesc.html">correspDesc</a> elements should be supplied, one for each communication. In the following example, the same document contains distinct messages, sent by two different people to the same destination: <a class="gi" title="(correspondence description) contains a description of the actions related to one act of correspondence." href="ref-correspDesc.html">correspDesc</a> is used for each separately: <div id="index-egXML-d52e28403" class="pre egXML_valid"><span class="element"><correspDesc <span class="attribute">xml:id</span>="<span class="attributevalue">message1</span>"></span><br /> <span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">sent</span>"></span><br /> <span class="element"><persName></span>John Gneisenau Neihardt<span class="element"></persName></span><br /> <span class="element"><placeName></span>Branson (Montgomery)<span class="element"></placeName></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1932-12-17</span>"/></span><br /> <span class="element"></correspAction></span><br /> <span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>"></span><br /> <span class="element"><persName <span class="attribute">xml:id</span>="<span class="attributevalue">JTH</span>"></span>Julius Temple House<span class="element"></persName></span><br /> <span class="element"><placeName></span>New York<span class="element"></placeName></span><br /> <span class="element"></correspAction></span><br /><span class="element"></correspDesc></span><br /><span class="element"><correspDesc <span class="attribute">xml:id</span>="<span class="attributevalue">message2</span>"></span><br /> <span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">sent</span>"></span><br /> <span class="element"><persName></span>Enid Neihardt<span class="element"></persName></span><br /> <span class="element"><placeName></span>Branson (Montgomery)<span class="element"></placeName></span><br /> <span class="element"><date <span class="attribute">when</span>="<span class="attributevalue">1932-12-17</span>"/></span><br /> <span class="element"></correspAction></span><br /> <span class="element"><correspAction <span class="attribute">type</span>="<span class="attributevalue">received</span>"></span><br /> <span class="element"><persName <span class="attribute">sameAs</span>="<span class="attributevalue">#JTH</span>"/></span><br /> <span class="element"><placeName></span>New York<span class="element"></placeName></span><br /> <span class="element"></correspAction></span><br /><span class="element"></correspDesc></span></div></div></div></div><div class="div2" id="HD9"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD4"><span class="headingNumber">2.4 </span>The Profile Description</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD6"><span class="headingNumber">2.6 </span>The Revision Description</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD9" title="link to this section "><span class="invisible">TEI: Non-TEI Metadata</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.5 </span><span class="head">Non-TEI Metadata</span></h3><p>Projects often maintain metadata about their TEI documents in more than one form or system. For example, a project may have a database of bibliographic information on the set of documents they intend to encode. From this database, both a MARC record and a <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> are generated. The document is then encoded, during which process additional information is added to the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> manually. Then, when the document is published on the web, a Dublin Core record is generated for discoverability of the resource. It is sometimes advantageous to store some or all of the non-TEI metadata in the TEI file.</p><p>Such non-TEI data may be placed anywhere within a TEI file (other than as the root element), as it does not affect TEI conformance. However, it is easier for humans to manage these kinds of data if they are grouped together in a single location. In addition, such grouping makes it easy to avoid accidentally flagging non-TEI data as errors during validation of the file against a TEI schema. The <a class="gi" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a> element, which may appear in the TEI Header after the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> but before the optional <a class="gi" title="(revision description) summarizes the revision history for a file." href="ref-revisionDesc.html">revisionDesc</a>, is provided for this purpose. </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-xenoData.html">xenoData</a></span> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed.</li></ul><p>The <a class="gi" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a> element may contain anything except TEI elements. It may contain one or more elements from outside the TEI<span id="Note46_return"><a class="notelink" title="As is always the case when mixing elements from different namespaces in an XML document, the namespace of these non-TEI elements must be declared eith…" href="#Note46"><sup>9</sup></a></span> or data in some non-XML text format.<span id="Note47_return"><a class="notelink" title="As is always the case when using text inside an XML document, certain characters cannot occur in their normal form, and must be escaped. The most comm…" href="#Note47"><sup>10</sup></a></span></p><div class="p">In the following example, the prefix <code>rdf</code> is bound to the namespace <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>, the prefix <code>dc</code> is bound to the namespace <code>http://purl.org/dc/elements/1.1/</code>, and the prefix <code>cc</code> is bound to the namespace <code>http://web.resource.org/cc/</code>. <div id="index-egXML-d52e29025" class="pre egXML_feasible"><span class="element"><xenoData></span><br /> <span class="element"><rdf:RDF></span><br /> <span class="element"><cc:Work <span class="attribute">rdf:about</span>="<span class="attributevalue"></span>"></span><br /> <span class="element"><dc:title></span>Applied Software Project Management - review<span class="element"></dc:title></span><br /> <span class="element"><dc:type <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://purl.org/dc/dcmitype/Text</span>"/></span><br /> <span class="element"><dc:license <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://creativecommons.org/licenses/by-sa/2.0/uk/</span>"/></span><br /> <span class="element"></cc:Work></span><br /> <span class="element"><cc:License <span class="attribute">rdf:about</span>="<span class="attributevalue">http://creativecommons.org/licenses/by-sa/2.0/uk/</span>"></span><br /> <span class="element"><cc:permits <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/Reproduction</span>"/></span><br /> <span class="element"><cc:permits <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/Distribution</span>"/></span><br /> <span class="element"><cc:requires <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/Notice</span>"/></span><br /> <span class="element"><cc:requires <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/Attribution</span>"/></span><br /> <span class="element"><cc:permits <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/DerivativeWorks</span>"/></span><br /> <span class="element"><cc:requires <span class="attribute">rdf:resource</span>="<span class="attributevalue">http://web.resource.org/cc/ShareAlike</span>"/></span><br /> <span class="element"></cc:License></span><br /> <span class="element"></rdf:RDF></span><br /><span class="element"></xenoData></span></div></div></div><div class="div2" id="HD6"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD9"><span class="headingNumber">2.5 </span>Non-TEI Metadata</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD7"><span class="headingNumber">2.7 </span>Minimal and Recommended Headers </a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD6" title="link to this section "><span class="invisible">TEI: The Revision Description</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.6 </span><span class="head">The Revision Description</span></h3><p>The final sub-element of the TEI header, the <a class="gi" title="(revision description) summarizes the revision history for a file." href="ref-revisionDesc.html">revisionDesc</a> element, provides a detailed change log in which each change made to a text may be recorded. Its use is optional but highly recommended. It provides essential information for the administration of large numbers of files which are being updated, corrected, or otherwise modified as well as extremely useful documentation for files being passed from researcher to researcher or system to system. Without change logs, it is easy to confuse different versions of a file, or to remain unaware of small but important changes made in the file by some earlier link in the chain of distribution. No significant change should be made in any TEI-conformant file without corresponding entries being made in the change log.</p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-revisionDesc.html">revisionDesc</a></span> (revision description) summarizes the revision history for a file.</li><li><span class="specList-elementSpec"><a href="ref-listChange.html">listChange</a></span> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text.</li><li><span class="specList-elementSpec"><a href="ref-change.html">change</a></span> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file.</li></ul><p>The main purpose of the revision description is to record changes in the text to which a header is prefixed. However, it is recommended TEI practice to include entries also for significant changes in the header itself (other than the revision description itself, of course). At the very least, an entry should be supplied indicating the date of creation of the header.</p><p>The log consists of a list of entries, one for each change. Changes may be grouped and organised using either the <a class="gi" title="groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text." href="ref-listChange.html">listChange</a> element described in section <a class="link_ptr" href="PH.html#PH-changes" title="Identifying Changes and Revisions"><span class="headingNumber">11.7 </span>Identifying Changes and Revisions</a> or the simple <a class="gi" title="contains any sequence of items organized as a list." href="ref-list.html">list</a> element described in section <a class="link_ptr" href="CO.html#COLI" title="Lists"><span class="headingNumber">3.7 </span>Lists</a>. Alternatively, a simple sequence of <a class="gi" title="documents a change or set of changes made during the production of a source document, or during the revision of an electronic file." href="ref-change.html">change</a> elements may be given. The attributes <span class="att">when</span> and <span class="att">who</span> may be supplied for each <a class="gi" title="documents a change or set of changes made during the production of a source document, or during the revision of an electronic file." href="ref-change.html">change</a> element to indicate its date and the person responsible for it respectively. The description of the change itself can range from a simple phrase to a series of paragraphs. If a number is to be associated with one or more changes (for example, a revision number), the global <span class="att">n</span> attribute may be used to indicate it.</p><p>It is recommended to give changes in reverse chronological order, most recent first.</p><div class="p">For example: <div id="index-egXML-d52e29102" class="pre egXML_valid"><br /><span class="comment"><!-- ... --></span><span class="element"><revisionDesc></span><br /> <span class="element"><change <span class="attribute">n</span>="<span class="attributevalue">RCS:1.39</span>" <span class="attribute">when</span>="<span class="attributevalue">2007-08-08</span>"<br /> <span class="attribute">who</span>="<span class="attributevalue">#jwernimo.lrv</span>"></span>Changed <span class="element"><val></span>drama.verse<span class="element"></val></span><br /> <span class="element"><gi></span>lg<span class="element"></gi></span>s to <span class="element"><gi></span>p<span class="element"></gi></span>s. <span class="element"><note></span>we have opened a discussion about the need for a new<br /> value for <span class="element"><att></span>type<span class="element"></att></span> of <span class="element"><gi></span>lg<span class="element"></gi></span>, <span class="element"><val></span>drama.free.verse<span class="element"></val></span>, in order to address<br /> the verse of Behn which is not in regular iambic pentameter. For the time being these<br /> instances are marked with a comment note until we are able to fully consider the best way<br /> to encode these instances.<span class="element"></note></span><span class="element"></change></span><br /> <span class="element"><change <span class="attribute">n</span>="<span class="attributevalue">RCS:1.33</span>" <span class="attribute">when</span>="<span class="attributevalue">2007-06-28</span>"<br /> <span class="attribute">who</span>="<span class="attributevalue">#pcaton.xzc</span>"></span>Added <span class="element"><att></span>key<span class="element"></att></span> and <span class="element"><att></span>reg<span class="element"></att></span><br /> to <span class="element"><gi></span>name<span class="element"></gi></span>s.<span class="element"></change></span><br /> <span class="element"><change <span class="attribute">n</span>="<span class="attributevalue">RCS:1.31</span>" <span class="attribute">when</span>="<span class="attributevalue">2006-12-04</span>"<br /> <span class="attribute">who</span>="<span class="attributevalue">#wgui.ner</span>"></span>Completed renovation. Validated.<span class="element"></change></span><br /><span class="element"></revisionDesc></span></div> In the above example, the <span class="att">who</span> attributes point to <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> elements which have been included earlier in the <a class="gi" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a> of the same header: <div id="index-egXML-d52e29152" class="pre egXML_valid"><span class="element"><titleStmt></span><br /> <span class="element"><title></span>The Amorous Prince, or, the Curious Husband, 1671<span class="element"></title></span><br /> <span class="element"><author></span><br /> <span class="element"><persName <span class="attribute">ref</span>="<span class="attributevalue">#abehn.aeh</span>"></span>Behn, Aphra<span class="element"></persName></span><br /> <span class="element"></author></span><br /> <span class="element"><respStmt <span class="attribute">xml:id</span>="<span class="attributevalue">pcaton.xzc</span>"></span><br /> <span class="element"><persName></span>Caton, Paul<span class="element"></persName></span><br /> <span class="element"><resp></span>electronic publication editor<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /> <span class="element"><respStmt <span class="attribute">xml:id</span>="<span class="attributevalue">wgui.ner</span>"></span><br /> <span class="element"><persName></span>Gui, Weihsin<span class="element"></persName></span><br /> <span class="element"><resp></span>encoder<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /> <span class="element"><respStmt <span class="attribute">xml:id</span>="<span class="attributevalue">jwernimo.lrv</span>"></span><br /> <span class="element"><persName></span>Wernimont, Jacqueline<span class="element"></persName></span><br /> <span class="element"><resp></span>encoder<span class="element"></resp></span><br /> <span class="element"></respStmt></span><br /><span class="element"></titleStmt></span></div> There is however no requirement that the <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> be used for this person, or that the elements indicated be contained within the same document. A project might for example maintain a separate document listing all of its personnel in which they were represented using the <a class="gi" title="provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source." href="ref-person.html">person</a> element described in <a class="link_ptr" href="CC.html#CCAHPA" title="The Participant Description"><span class="headingNumber">15.2.2 </span>The Participant Description</a>.</div></div><div class="div2" id="HD7"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD6"><span class="headingNumber">2.6 </span>The Revision Description</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#HD8"><span class="headingNumber">2.8 </span>Note for Library Cataloguers</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD7" title="link to this section "><span class="invisible">TEI: Minimal and Recommended Headers
</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.7 </span><span class="head">Minimal and Recommended Headers </span></h3><p>The TEI header allows for the provision of a very large amount of information concerning the text itself, its source, its encodings, and revisions of it, as well as a wealth of descriptive information such as the languages it uses and the situation(s) in which it was produced, together with the setting and identity of participants within it. This diversity and richness reflects the diversity of uses to which it is envisaged that electronic texts conforming to these Guidelines will be put. It is emphatically <em>not</em> intended that all of the elements described above should be present in every TEI Header.</p><p>The amount of encoding in a header will depend both on the nature and the intended use of the text. At one extreme, an encoder may expect that the header will be needed only to provide a bibliographic identification of the text adequate to local needs. At the other, wishing to ensure that their texts can be used for the widest range of applications, encoders will want to document as explicitly as possible both bibliographic and descriptive information, in such a way that no prior or ancillary knowledge about the text is needed in order to process it. The header in such a case will be very full, approximating to the kind of documentation often supplied in the form of a manual. Most texts will lie somewhere between these extremes; textual corpora in particular will tend more to the latter extreme. In the remainder of this section we demonstrate first the minimal, and next a commonly recommended, level of encoding for the bibliographic information held by the TEI header. </p><div class="p">Supplying only the minimal level of encoding required, the TEI header of a single text might look like the following example: <div id="index-egXML-d52e29463" class="pre egXML_valid"><span class="element"><teiHeader></span><br /> <span class="element"><fileDesc></span><br /> <span class="element"><titleStmt></span><br /> <span class="element"><title></span>Thomas Paine: Common sense, a<br /> machine-readable transcript<span class="element"></title></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>compiled by<span class="element"></resp></span><br /> <span class="element"><name></span>Jon K Adams<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /> <span class="element"></titleStmt></span><br /> <span class="element"><publicationStmt></span><br /> <span class="element"><distributor></span>Oxford Text Archive<span class="element"></distributor></span><br /> <span class="element"></publicationStmt></span><br /> <span class="element"><sourceDesc></span><br /> <span class="element"><bibl></span>The complete writings of Thomas Paine, collected and edited<br /> by Phillip S. Foner (New York, Citadel Press, 1945)<span class="element"></bibl></span><br /> <span class="element"></sourceDesc></span><br /> <span class="element"></fileDesc></span><br /><span class="element"></teiHeader></span></div></div><p>The only mandatory component of the TEI header is the <a class="gi" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> element. Within this, <a class="gi" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a>, <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a>, and <a class="gi" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> are all required constituents. Within the title statement, a title is required, and an author should be specified, even if it is <span class="mentioned">unknown</span>, as should some additional statement of responsibility, here given by the <a class="gi" title="(statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work." href="ref-respStmt.html">respStmt</a> element. Within the <a class="gi" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a>, a publisher, distributor, or other agency responsible for the file must be specified. Finally, the source description should contain at the least a loosely structured bibliographic citation identifying the source of the electronic text if (as is usually the case) there is one.</p><div class="p">We now present the same example header, expanded to include additionally recommended information, adequate to most bibliographic purposes, in particular to allow for the creation of an <a class="link_ref" href="BIB.html#HD-BIBL-1" title="AngloAmerican Cataloguing RulesSecond Edition 2002 revision 2005 updateChicagoAmerican Library AssociationOttawaCanadian Librar...">AACR2</a>-conformant bibliographic record. We have also added information about the encoding principles used in this (imaginary) encoding, about the text itself (in the form of Library of Congress subject headings), and about the revision of the file. <div id="index-egXML-d52e29518" class="pre egXML_valid"><span class="element"><teiHeader></span><br /> <span class="element"><fileDesc></span><br /> <span class="element"><titleStmt></span><br /> <span class="element"><title></span>Common sense, a machine-readable transcript<span class="element"></title></span><br /> <span class="element"><author></span>Paine, Thomas (1737-1809)<span class="element"></author></span><br /> <span class="element"><respStmt></span><br /> <span class="element"><resp></span>compiled by<span class="element"></resp></span><br /> <span class="element"><name></span>Jon K Adams<span class="element"></name></span><br /> <span class="element"></respStmt></span><br /> <span class="element"></titleStmt></span><br /> <span class="element"><editionStmt></span><br /> <span class="element"><edition></span><br /> <span class="element"><date></span>1986<span class="element"></date></span><br /> <span class="element"></edition></span><br /> <span class="element"></editionStmt></span><br /> <span class="element"><publicationStmt></span><br /> <span class="element"><distributor></span>Oxford Text Archive.<span class="element"></distributor></span><br /> <span class="element"><address></span><br /> <span class="element"><addrLine></span>Oxford University Computing Services,<span class="element"></addrLine></span><br /> <span class="element"><addrLine></span>13 Banbury Road,<span class="element"></addrLine></span><br /> <span class="element"><addrLine></span>Oxford OX2 6RB,<span class="element"></addrLine></span><br /> <span class="element"><addrLine></span>UK<span class="element"></addrLine></span><br /> <span class="element"></address></span><br /> <span class="element"></publicationStmt></span><br /> <span class="element"><notesStmt></span><br /> <span class="element"><note></span>Brief notes on the text are in a<br /> supplementary file.<span class="element"></note></span><br /> <span class="element"></notesStmt></span><br /> <span class="element"><sourceDesc></span><br /> <span class="element"><biblStruct></span><br /> <span class="element"><monogr></span><br /> <span class="element"><editor></span>Foner, Philip S.<span class="element"></editor></span><br /> <span class="element"><title></span>The collected writings of Thomas Paine<span class="element"></title></span><br /> <span class="element"><imprint></span><br /> <span class="element"><pubPlace></span>New York<span class="element"></pubPlace></span><br /> <span class="element"><publisher></span>Citadel Press<span class="element"></publisher></span><br /> <span class="element"><date></span>1945<span class="element"></date></span><br /> <span class="element"></imprint></span><br /> <span class="element"></monogr></span><br /> <span class="element"></biblStruct></span><br /> <span class="element"></sourceDesc></span><br /> <span class="element"></fileDesc></span><br /> <span class="element"><encodingDesc></span><br /> <span class="element"><samplingDecl></span><br /> <span class="element"><p></span>Editorial notes in the Foner edition have not<br /> been reproduced. <span class="element"></p></span><br /> <span class="element"><p></span>Blank lines and multiple blank spaces, including paragraph<br /> indents, have not been preserved. <span class="element"></p></span><br /> <span class="element"></samplingDecl></span><br /> <span class="element"><editorialDecl></span><br /> <span class="element"><correction <span class="attribute">status</span>="<span class="attributevalue">high</span>"<br /> <span class="attribute">method</span>="<span class="attributevalue">silent</span>"></span><br /> <span class="element"><p></span>The following errors<br /> in the Foner edition have been corrected:<br /> <span class="element"><list></span><br /> <span class="element"><item></span>p. 13 l. 7 cotemporaries contemporaries<span class="element"></item></span><br /> <span class="element"><item></span>p. 28 l. 26 [comma] [period]<span class="element"></item></span><br /> <span class="element"><item></span>p. 84 l. 4 kin kind<span class="element"></item></span><br /> <span class="element"><item></span>p. 95 l. 1 stuggle struggle<span class="element"></item></span><br /> <span class="element"><item></span>p. 101 l. 4 certainy certainty<span class="element"></item></span><br /> <span class="element"><item></span>p. 167 l. 6 than that<span class="element"></item></span><br /> <span class="element"><item></span>p. 209 l. 24 publshed published<span class="element"></item></span><br /> <span class="element"></list></span><span class="element"></p></span><br /> <span class="element"></correction></span><br /> <span class="element"><normalization></span><br /> <span class="element"><p></span>No normalization beyond that performed<br /> by Foner, if any. <span class="element"></p></span><br /> <span class="element"></normalization></span><br /> <span class="element"><quotation <span class="attribute">marks</span>="<span class="attributevalue">all</span>"></span><br /> <span class="element"><p></span>All double quotation marks<br /> rendered with ", all single quotation marks with<br /> apostrophe. <span class="element"></p></span><br /> <span class="element"></quotation></span><br /> <span class="element"><hyphenation <span class="attribute">eol</span>="<span class="attributevalue">none</span>"></span><br /> <span class="element"><p></span>Hyphenated words that appear at the<br /> end of the line in the Foner edition have been reformed.<span class="element"></p></span><br /> <span class="element"></hyphenation></span><br /> <span class="element"><stdVals></span><br /> <span class="element"><p></span>The values of <span class="element"><att></span>when-iso<span class="element"></att></span> on the <span class="element"><gi></span>time<span class="element"></gi></span><br /> element always end in the format <span class="element"><val></span>HH:MM<span class="element"></val></span> or<br /> <span class="element"><val></span>HH<span class="element"></val></span>; i.e., seconds, fractions thereof, and time<br /> zone designators are not present.<span class="element"></p></span><br /> <span class="element"></stdVals></span><br /> <span class="element"><interpretation></span><br /> <span class="element"><p></span>Compound proper names are marked. <span class="element"></p></span><br /> <span class="element"><p></span>Dates are marked. <span class="element"></p></span><br /> <span class="element"><p></span>Italics are recorded without interpretation. <span class="element"></p></span><br /> <span class="element"></interpretation></span><br /> <span class="element"></editorialDecl></span><br /> <span class="element"><classDecl></span><br /> <span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">lcsh</span>"></span><br /> <span class="element"><bibl></span>Library of Congress Subject Headings<span class="element"></bibl></span><br /> <span class="element"></taxonomy></span><br /> <span class="element"><taxonomy <span class="attribute">xml:id</span>="<span class="attributevalue">lc</span>"></span><br /> <span class="element"><bibl></span>Library of Congress Classification<span class="element"></bibl></span><br /> <span class="element"></taxonomy></span><br /> <span class="element"></classDecl></span><br /> <span class="element"></encodingDesc></span><br /> <span class="element"><profileDesc></span><br /> <span class="element"><creation></span><br /> <span class="element"><date></span>1774<span class="element"></date></span><br /> <span class="element"></creation></span><br /> <span class="element"><langUsage></span><br /> <span class="element"><language <span class="attribute">ident</span>="<span class="attributevalue">en</span>" <span class="attribute">usage</span>="<span class="attributevalue">100</span>"></span>English.<span class="element"></language></span><br /> <span class="element"></langUsage></span><br /> <span class="element"><textClass></span><br /> <span class="element"><keywords <span class="attribute">scheme</span>="<span class="attributevalue">#lcsh</span>"></span><br /> <span class="element"><term></span>Political science<span class="element"></term></span><br /> <span class="element"><term></span>United States -- Politics and government —<br /> Revolution, 1775-1783<span class="element"></term></span><br /> <span class="element"></keywords></span><br /> <span class="element"><classCode <span class="attribute">scheme</span>="<span class="attributevalue">#lc</span>"></span>JC 177<span class="element"></classCode></span><br /> <span class="element"></textClass></span><br /> <span class="element"></profileDesc></span><br /> <span class="element"><revisionDesc></span><br /> <span class="element"><change <span class="attribute">when</span>="<span class="attributevalue">1996-01-22</span>" <span class="attribute">who</span>="<span class="attributevalue">#MSM</span>"></span> finished proofreading <span class="element"></change></span><br /> <span class="element"><change <span class="attribute">when</span>="<span class="attributevalue">1995-10-30</span>" <span class="attribute">who</span>="<span class="attributevalue">#LB</span>"></span> finished proofreading <span class="element"></change></span><br /> <span class="element"><change <span class="attribute">notBefore</span>="<span class="attributevalue">1995-07-04</span>" <span class="attribute">who</span>="<span class="attributevalue">#RG</span>"></span> finished data entry at end of term <span class="element"></change></span><br /> <span class="element"><change <span class="attribute">notAfter</span>="<span class="attributevalue">1995-01-01</span>" <span class="attribute">who</span>="<span class="attributevalue">#RG</span>"></span> began data entry before New Year 1995 <span class="element"></change></span><br /> <span class="element"></revisionDesc></span><br /><span class="element"></teiHeader></span></div> </div><p>Many other examples of recommended usage for the elements discussed in this chapter are provided here, in the reference index and in the associated tutorials. </p></div><div class="div2" id="HD8"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD7"><span class="headingNumber">2.7 </span>Minimal and Recommended Headers </a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html#index-body.1_div.2_div.9"><span class="headingNumber">2.9 </span>The TEI Header Module</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#HD8" title="link to this section "><span class="invisible">TEI: Note for Library Cataloguers</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.8 </span><span class="head">Note for Library Cataloguers</span></h3><p>A strong motivation in preparing the material in this chapter was to provide in the TEI header a viable chief source of information for cataloguing computer files. The TEI header is not a library catalogue record, and so will not make all of the distinctions essential in standard library work. It also includes much information generally excluded from standard bibliographic descriptions. It is the intention of the developers, however, to ensure that the information required for a catalogue record be retrievable from the TEI file header, and moreover that the mapping from the one to the other be as simple and straightforward as possible. Where the correspondence is not obvious, it may prove useful to consult one of the works which were influential in developing the content of the TEI header. These include:</p><dl><dt><span><a class="link_ref" href="BIB.html#ISBD" title="ISBD International Standard Bibliographic DescriptionBerlin MünchenDe Gruyter Saur2011 IFLA Series on Bibliographic Control 44">ISBD</a></span></dt><dd><span class="bibl"><span class="titlem">ISBD: International Standard Bibliographic Description</span></span> is an international standard setting out what information should be recorded in a description of a bibliographical item. Until a consolidated edition published in 2011, there was a general standard called ISBD(G) and separate ISBDs covering different types of material, e.g. ISBD(M) for monographs, ISBD(ER) for electronic resources. These separate ISBDs follow the same general scheme as the main ISBD(G), but provide appropriate interpretations for the specific materials under consideration.</dd><dt><span><a class="link_ref" href="BIB.html#HD-BIBL-1" title="AngloAmerican Cataloguing RulesSecond Edition 2002 revision 2005 updateChicagoAmerican Library AssociationOttawaCanadian Librar...">AACR2</a></span></dt><dd>The <span class="bibl"><span class="titlem">Anglo-American Cataloguing Rules</span> (second edition)</span> were published in 1978, with revisions appearing periodically through 2005. AACR2 provides guidelines for the construction of catalogues in general libraries in the English-speaking world. AACR2 is explicitly based on the general framework of the ISBD(G) and the subsidiary ISBDs: it gives a description of how to describe bibliographic items and how to create access points such as subject or name headings and uniform titles. Other national cataloguing codes exist as well, including the Z44 series of standards from issued by the Association française de normalisation (AFNOR), <span class="titlem">Regeln für die alphabetische Katalogisierung in wissenschaftlichen Bibliotheken</span> (RAK-WB), <span class="titlem">Regole italiane di catalogazione per autore</span> (RICA), and <span class="titlem">Система стандартов по информации, библиотечному и издательскому делу. Библиографическая запись. Библиографическое описание. Общие требования и правила составления</span> (ГОСТ 7.1).</dd><dt><span><a class="link_ref" href="BIB.html#COBICOR-eg-246" title="American National Standard for Bibliographic References ANSI Z39.291977 New York American National Standards Institute (1977)">ANSI Z39.29</a></span></dt><dd>The <span class="titlem">American National Standard for Bibliographic References</span> was an American national standard governing bibliographic references for use in bibliographies, end-of-work lists, references in abstracting and indexing publications, and outputs from computerized bibliographic data bases. A revised version is maintained by the National Information Standards Organization (NISO). The related ISO standard is ISO 690. Other relevant national standards include BS 5605:1990, BS 6371:1983. DIN 1505-2, and ГОСТ 7.0.5.</dd></dl><p>Since the TEI file description elements are based on the ISBD areas, it should be possible to use the content of file description as the basis for a catalog record for a TEI document. However, cataloguers should be aware that the permissive nature of the TEI Guidelines may lead to divergences between practice in using the TEI file description and the comparatively strict recommendations of AACR2 and other national cataloguing codes. Such divergences as the following may preclude automatic generation of catalogue records from TEI headers: </p><ul><li class="item">The TEI Guidelines do not require that text be transcribed from the ‘chief source of information’ using normalized capitalization and punctuation .</li><li class="item">The TEI title statement may not categorize constituent titles in the same way as prescribed by a national cataloguing code.</li><li class="item">The TEI title statement contains authors, editors, and other responsible parties in separate elements, with names which may not have been normalized; it does not necessarily contain a single statement of responsibility .</li><li class="item">There is no specific place in a TEI header to specify the <span class="term">main entry</span> or <span class="term">added entries</span> (<span class="gloss">name or title headings under which a catalogue record is filed</span>) for the catalogue record.</li><li class="item">The TEI header does not require use of a particular vocabulary for subject headings nor require the use of subject headings.</li></ul></div><div class="teidiv1" id="index-body.1_div.2_div.9"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="HD.html#HD8"><span class="headingNumber">2.8 </span>Note for Library Cataloguers</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#index-body.1_div.2_div.9" title="link to this section "><span class="invisible">TEI: The TEI Header Module</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">2.9 </span><span class="head">The TEI Header Module</span></h3><p>The module described in this chapter makes available the following components: </p><dl class="moduleSpec"><dt class="moduleSpecHead"><span lang="en">Module</span> header: The TEI Header</dt><dd><ul><li><span lang="en">Elements defined</span>: <a class="link_odd" title="contains a summary or formal abstract prefixed to an existing source document by the encoder." href="ref-abstract.html">abstract</a> <a class="link_odd" title="(application information) records information about an application which has edited the TEI file." href="ref-appInfo.html">appInfo</a> <a class="link_odd" title="provides information about an application which has acted upon the document." href="ref-application.html">application</a> <a class="link_odd" title="(release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor." href="ref-authority.html">authority</a> <a class="link_odd" title="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." href="ref-availability.html">availability</a> <a class="link_odd" title="(fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present." href="ref-biblFull.html">biblFull</a> <a class="link_odd" title="(canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI." href="ref-cRefPattern.html">cRefPattern</a> <a class="link_odd" title="describes a calendar or dating system used in a dating formula in the text." href="ref-calendar.html">calendar</a> <a class="link_odd" title="(calendar description) contains a description of the calendar system used in any dating expression found in the text." href="ref-calendarDesc.html">calendarDesc</a> <a class="link_odd" title="(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>." href="ref-catDesc.html">catDesc</a> <a class="link_odd" title="(category reference) specifies one or more defined categories within some taxonomy or text typology." href="ref-catRef.html">catRef</a> <a class="link_odd" title="contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy." href="ref-category.html">category</a> <a class="link_odd" title="documents a change or set of changes made during the production of a source document, or during the revision of an electronic file." href="ref-change.html">change</a> <a class="link_odd" title="(classification code) contains the classification code used for this text in some standard classification system." href="ref-classCode.html">classCode</a> <a class="link_odd" title="(classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text." href="ref-classDecl.html">classDecl</a> <a class="link_odd" title="(correction principles) states how and under what circumstances corrections have been made in the text." href="ref-correction.html">correction</a> <a class="link_odd" title="(correspondence action) 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." href="ref-correspAction.html">correspAction</a> <a class="link_odd" title="(correspondence context) provides references to preceding or following correspondence related to this piece of correspondence." href="ref-correspContext.html">correspContext</a> <a class="link_odd" title="(correspondence description) contains a description of the actions related to one act of correspondence." href="ref-correspDesc.html">correspDesc</a> <a class="link_odd" title="contains information about the creation of a text." href="ref-creation.html">creation</a> <a class="link_odd" title="supplies the name of a person or other agency responsible for the distribution of a text." href="ref-distributor.html">distributor</a> <a class="link_odd" title="describes the particularities of one edition of a text." href="ref-edition.html">edition</a> <a class="link_odd" title="(edition statement) groups information relating to one edition of a text." href="ref-editionStmt.html">editionStmt</a> <a class="link_odd" title="(editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text." href="ref-editorialDecl.html">editorialDecl</a> <a class="link_odd" title="(encoding description) documents the relationship between an electronic text and the source or sources from which it was derived." href="ref-encodingDesc.html">encodingDesc</a> <a class="link_odd" title="describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units." href="ref-extent.html">extent</a> <a class="link_odd" title="(file description) contains a full bibliographic description of an electronic file." href="ref-fileDesc.html">fileDesc</a> <a class="link_odd" title="(funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text." href="ref-funder.html">funder</a> <a class="link_odd" title="(geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <geo> element elsewhere within the document." href="ref-geoDecl.html">geoDecl</a> <a class="link_odd" title="(note on hand) describes a particular style or hand distinguished within a manuscript." href="ref-handNote.html">handNote</a> <a class="link_odd" title="summarizes the way in which hyphenation in a source text has been treated in an encoded version of it." href="ref-hyphenation.html">hyphenation</a> <a class="link_odd" title="(identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way." href="ref-idno.html">idno</a> <a class="link_odd" title="describes the scope of any analytic or interpretive information added to the text in addition to the transcription." href="ref-interpretation.html">interpretation</a> <a class="link_odd" title="contains a list of keywords or phrases identifying the topic or nature of a text." href="ref-keywords.html">keywords</a> <a class="link_odd" title="(language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text." href="ref-langUsage.html">langUsage</a> <a class="link_odd" title="characterizes a single language or sublanguage used within a text." href="ref-language.html">language</a> <a class="link_odd" title="contains information about a licence or other legal agreement applicable to the text." href="ref-licence.html">licence</a> <a class="link_odd" title="groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text." href="ref-listChange.html">listChange</a> <a class="link_odd" title="(list of prefix definitions) contains a list of definitions of prefixing schemes used in data.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs." href="ref-listPrefixDef.html">listPrefixDef</a> <a class="link_odd" title="supplies the formal name of the namespace to which the elements documented by its children belong." href="ref-namespace.html">namespace</a> <a class="link_odd" title="indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form." href="ref-normalization.html">normalization</a> <a class="link_odd" title="(notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description." href="ref-notesStmt.html">notesStmt</a> <a class="link_odd" title="(prefix definition) defines a prefixing scheme used in data.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs." href="ref-prefixDef.html">prefixDef</a> <a class="link_odd" title="(principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text." href="ref-principal.html">principal</a> <a class="link_odd" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a> <a class="link_odd" title="(project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected." href="ref-projectDesc.html">projectDesc</a> <a class="link_odd" title="(publication statement) groups information concerning the publication or distribution of an electronic or other text." href="ref-publicationStmt.html">publicationStmt</a> <a class="link_odd" title="specifies editorial practice adopted with respect to punctuation marks in the original." href="ref-punctuation.html">punctuation</a> <a class="link_odd" title="specifies editorial practice adopted with respect to quotation marks in the original." href="ref-quotation.html">quotation</a> <a class="link_odd" title="(reference state) specifies one component of a canonical reference defined by the milestone method." href="ref-refState.html">refState</a> <a class="link_odd" title="(references declaration) specifies how canonical references are constructed for this text." href="ref-refsDecl.html">refsDecl</a> <a class="link_odd" title="supplies information about the rendition or appearance of one or more elements in the source text." href="ref-rendition.html">rendition</a> <a class="link_odd" title="(revision description) summarizes the revision history for a file." href="ref-revisionDesc.html">revisionDesc</a> <a class="link_odd" title="(sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection." href="ref-samplingDecl.html">samplingDecl</a> <a class="link_odd" title="(schema reference) describes or points to a related customization or schema file" href="ref-schemaRef.html">schemaRef</a> <a class="link_odd" title="describes a particular script distinguished within the description of a manuscript or similar resource." href="ref-scriptNote.html">scriptNote</a> <a class="link_odd" title="describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc." href="ref-segmentation.html">segmentation</a> <a class="link_odd" title="(series statement) groups information about the series, if any, to which a publication belongs." href="ref-seriesStmt.html">seriesStmt</a> <a class="link_odd" title="(source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> <a class="link_odd" title="specifies the name of a sponsoring organization or institution." href="ref-sponsor.html">sponsor</a> <a class="link_odd" title="(standard values) specifies the format used when standardized date or number values are supplied." href="ref-stdVals.html">stdVals</a> <a class="link_odd" title="(style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied." href="ref-styleDefDecl.html">styleDefDecl</a> <a class="link_odd" title="documents the usage of a specific element within a specified document." href="ref-tagUsage.html">tagUsage</a> <a class="link_odd" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> <a class="link_odd" title="defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy." href="ref-taxonomy.html">taxonomy</a> <a class="link_odd" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> <a class="link_odd" title="(text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc." href="ref-textClass.html">textClass</a> <a class="link_odd" title="(title statement) groups information about the title of a work and those responsible for its content." href="ref-titleStmt.html">titleStmt</a> <a class="link_odd" title="(non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed." href="ref-xenoData.html">xenoData</a></li><li><span lang="en">Classes defined</span>: <a class="link_odd" title="provides attributes for regular-expression matching and replacement." href="ref-att.patternReplacement.html">att.patternReplacement</a></li></ul></dd></dl><p> The selection and combination of modules to form a TEI schema is described in <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a>.</p></div></div><nav class="left"><span class="upLink"> ↑ </span><a class="navigation" href="index.html">TEI P5 Guidelines</a><span class="previousLink"> « </span><a class="navigation" href="ST.html"><span class="headingNumber">1 </span>The TEI Infrastructure</a><span class="nextLink"> » </span><a class="navigation" href="CO.html"><span class="headingNumber">3 </span>Elements Available in All TEI Documents</a></nav><!--Notes in [div]--><div class="notes"><div class="noteHeading">Notes</div><div class="note" id="Note42"><span class="noteLabel">5 </span><div class="noteBody">For more information on this highly influential family of standards, first proposed in 1969 by the International Federation of Library Associations, see <a class="link_ptr" href="http://www.ifla.org/VII/s13/pubs/isbd.htm"><span>http://www.ifla.org/VII/s13/pubs/isbd.htm</span></a>. On the relation between the TEI proposals and other standards for bibliographic description, see further section <a class="link_ptr" href="HD.html#HD8" title="Note for Library Cataloguers"><span class="headingNumber">2.8 </span>Note for Library Cataloguers</a>.</div> <a class="link_return" title="Go back to text" href="#Note42_return">↵</a></div><div class="note" id="Note43"><span class="noteLabel">6 </span><div class="noteBody">Agencies compiling catalogues of machine-readable files are recommended to use available authority lists, such as the Library of Congress Name Authority List, for all common personal names.</div> <a class="link_return" title="Go back to text" href="#Note43_return">↵</a></div><div class="note" id="Note44"><span class="noteLabel">7 </span><div class="noteBody">In the case of a TEI corpus (<a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a>), a <a class="gi" title="(tagging declaration) provides detailed information about the tagging applied to a document." href="ref-tagsDecl.html">tagsDecl</a> in a corpus header will describe tag usage across the whole corpus, while one in an individual text header will describe tag usage for the individual text concerned.</div> <a class="link_return" title="Go back to text" href="#Note44_return">↵</a></div><div class="note" id="Note45"><span class="noteLabel">8 </span><div class="noteBody">On the <a class="gi" title="marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element." href="ref-milestone.html">milestone</a> tag itself, what are here referred to as ‘variables’ are identified by the combination of the <span class="att">ed</span> and <span class="att">unit</span> attributes.</div> <a class="link_return" title="Go back to text" href="#Note45_return">↵</a></div><div class="note" id="Note46"><span class="noteLabel">9 </span><div class="noteBody">As is always the case when mixing elements from different namespaces in an XML document, the namespace of these non-TEI elements must be declared either on the elements themselves or on an ancestor element.</div> <a class="link_return" title="Go back to text" href="#Note46_return">↵</a></div><div class="note" id="Note47"><span class="noteLabel">10 </span><div class="noteBody">As is always the case when using text inside an XML document, certain characters cannot occur in their normal form, and must be ‘escaped’. The most common of these are LESS-THAN SIGN (<span class="q">‘<’</span>, U+003C) and AMPERSAND (<span class="q">‘&’</span>, U+0026), which may be escaped with <code>&lt;</code> and <code>&amp;</code> respectively. See <a class="link_ptr" href="SG.html#SG-er" title="Character References"><span class="headingNumber"></span>Character References</a>.</div> <a class="link_return" title="Go back to text" href="#Note47_return">↵</a></div></div><div class="stdfooter autogenerated"><p>
[<a href="../../en/html/HD.html">English</a>]
[<a href="../../de/html/HD.html">Deutsch</a>]
[<a href="../../es/html/HD.html">Español</a>]
[<a href="../../it/html/HD.html">Italiano</a>]
[<a href="../../fr/html/HD.html">Français</a>]
[<a href="../../ja/html/HD.html">日本語</a>]
[<a href="../../ko/html/HD.html">한국어</a>]
[<a href="../../zh-TW/html/HD.html">中文</a>]
</p><hr /><div class="footer"><a class="plain" href="http://www.tei-c.org/About/">TEI Consortium</a> | <a class="plain" href="http://www.tei-c.org/About/contact.xml">Feedback</a></div><hr /><address><br />TEI Guidelines <a class="link_ref" href="AB.html#ABTEI4">Version</a> <a class="link_ref" href="../../readme-3.1.1.html">3.1.1a</a>. Last updated on <span class="date">10th May 2017</span>, revision <a class="link_ref" href="https://github.com/TEIC/TEI/commit/bd8dda3">bd8dda3</a>. This page generated on 2017-05-12T12:30:09Z.</address></div></div></body></html>