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
ST.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>1 The TEI Infrastructure - The TEI Guidelines</title><meta property="Language" content="en" /><meta property="DC.Title" content="1 The TEI Infrastructure - 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">1 </span>The TEI Infrastructure</h2><div class="div1" id="ST"><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="ST.html#STMA" title="TEI Modules">1.1 TEI Modules</a></li><li class="subtoc"><a class="subtoc" href="ST.html#STIN" title="Defining a TEI Schema">1.2 Defining a TEI Schema</a></li><li class="subtoc"><a class="subtoc" href="ST.html#STEC" title="The TEI Class System">1.3 The TEI Class System</a></li><li class="subtoc"><a class="subtoc" href="ST.html#STmacros" title="Macros">1.4 Macros</a></li><li class="subtoc"><a class="subtoc" href="ST.html#STOV" title="The TEI Infrastructure Module">1.5 The TEI Infrastructure Module</a></li><li class="subtoc"><a class="subtoc" href="ST.html#STDD" title="Deprecated Datatype Macros">1.6 Deprecated Datatype Macros</a></li></ul></div><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="CH.html"><span class="headingNumber">vi. </span>Languages and Character Sets</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="HD.html"><span class="headingNumber">2 </span>The TEI Header</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><p>This chapter describes the infrastructure for the encoding scheme defined by these Guidelines. It introduces the conceptual framework within which the following chapters are to be understood, and the means by which that conceptual framework is implemented. It assumes some familiarity with XML and XML schemas (see chapter <a class="link_ptr" href="SG.html" title="A Gentle Introduction to XML"><span class="headingNumber">v. </span>A Gentle Introduction to XML</a>) but is intended to be accessible to any user of these Guidelines. Other chapters supply further technical details, in particular chapter <a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a> which describes the XML schema used to express these Guidelines themselves, and chapter <a class="link_ptr" href="USE.html" title="Using the TEI"><span class="headingNumber">23 </span>Using the TEI</a> which combines a discussion of modification and conformance issues with a description of the intended behaviour of an ODD processor; these chapters should be read by anyone intending to implement a new TEI-based system.</p><p>The TEI encoding scheme consists of a number of <span class="term">modules</span>, each of which declares particular XML elements and their attributes. Part of an element's declaration includes its assignment to one or more element <span class="term">classes</span>. Another part defines its possible content and attributes with reference to these classes. This indirection gives the TEI system much of its strength and its flexibility. Elements may be combined more or less freely to form a <span class="term">schema</span> appropriate to a particular set of requirements. It is also easy to add new elements which reference existing classes or elements to a schema, as it is to exclude some of the elements provided by any module included in a schema.</p><p>In principle, a TEI schema may be constructed using any combination of modules. However, certain TEI modules are of particular importance, and should always be included in all but exceptional circumstances: the module <span class="ident-module">tei</span> described in the present chapter is of this kind because it defines classes, macros, and datatypes which are used by all other modules. The <span class="ident-module">core</span> module, defined in chapter <a class="link_ptr" href="CO.html" title="6"><span class="headingNumber">3 </span>Elements Available in All TEI Documents</a> contains declarations for elements and attributes which are likely to be needed in almost any kind of document, and is therefore recommended for global use. The <span class="ident-module">header</span> module defined in chapter <a class="link_ptr" href="HD.html" title="5"><span class="headingNumber">2 </span>The TEI Header</a> provides declarations for the metadata elements and attributes constituting the TEI header, a component which is required for TEI conformance, while the <span class="ident-module">textstructure</span> module defined in chapter <a class="link_ptr" href="DS.html" title="7"><span class="headingNumber">4 </span>Default Text Structure</a> declares basic structural elements needed for the encoding of most book-like objects. Most schemas will therefore need to include these four modules.</p><p>The specification for a TEI schema is itself a TEI document, using elements from the module described in chapter <a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a>: we refer to such a document informally as an <span class="term">ODD</span> document, from the design goal originally formulated for the system: <span class="q">‘One Document Does it all’</span>. Stylesheets for maintaining and processing ODD documents are maintained by the TEI, and these Guidelines are also maintained as such a document. As further discussed in <a class="link_ptr" href="USE.html#IM" title="Implementation of an ODD System"><span class="headingNumber">23.5 </span>Implementation of an ODD System</a>, an ODD document can be processed to generate a schema expressed using any of the three schema languages currently in wide use: the XML DTD language, the ISO RELAX NG language, or the W3C Schema language, as well as to generate documentation such as the <span class="titlem">Guidelines</span> and their associated web site.</p><p>The bulk of this chapter describes the TEI infrastructure module itself. Although it may be skipped at a first reading, an understanding of the topics addressed here is essential for anyone planning to take full advantage of the TEI customization techniques described in chapter <a class="link_ptr" href="USE.html#MD" title="Customization"><span class="headingNumber">23.3 </span>Customization</a>.</p><p>The chapter begins by briefly characterizing each of the modules available in the TEI scheme. Section <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a> describes in general terms the method of constructing a TEI schema in a specific schema language such as XML DTD language, RELAX NG, or W3C Schema.</p><p>The next and largest part of the chapter introduces the attribute and element classes used to define groups of elements and their characteristics (section <a class="link_ptr" href="ST.html#STEC" title="The TEI Class System"><span class="headingNumber">1.3 </span>The TEI Class System</a>).</p><p>Finally, section <a class="link_ptr" href="ST.html#STmacros" title="Macros"><span class="headingNumber">1.4 </span>Macros</a> introduces the concept of <span class="term">macros</span>, which are used to express some commonly used content models, and lists the <span class="term">datatypes</span> used to constrain the range of legal values for TEI attributes (section <a class="link_ptr" href="ST.html#DTYPES" title="Datatype Specifications"><span class="headingNumber">1.4.2 </span>Datatype Specifications</a>).</p><div class="div2" id="STMA"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STIN"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#STMA" title="link to this section "><span class="invisible">TEI: TEI Modules</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.1 </span><span class="head">TEI Modules</span></h3><p>These Guidelines define several hundred elements and attributes for marking up documents of any kind. Each definition has the following components: </p><ul class="simple"><li class="item">a prose description</li><li class="item">a formal declaration, expressed using a special-purpose XML vocabulary defined by these Guidelines in combination with elements taken from the ISO schema language RELAX NG</li><li class="item">usage examples</li></ul><p>Each chapter of these Guidelines presents a group of related elements, and also defines a corresponding set of declarations, which we call a <span class="term">module</span>. All the definitions are collected together in the reference sections provided as an appendix. Formal declarations for a given chapter are collected together within the corresponding module. For convenience, each element is assigned to a single module, typically for use in some specific application area, or to support a particular kind of usage. A module is thus simply a convenient way of grouping together a number of associated element declarations. In the simple case, a TEI schema is made by combining together a small number of modules, as further described in section <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a> below.</p><p>The following table lists the modules defined by the current release of these Guidelines: </p><div class="table" id="tab-mods"><table><tr class="label"><td>Module name</td><td>Formal public identifier</td><td>Where defined</td></tr><tr><td>analysis</td><td>Analysis and Interpretation</td><td><a class="link_ptr" href="AI.html" title="15"><span class="headingNumber">17 </span>Simple Analytic Mechanisms</a></td></tr><tr><td>certainty</td><td>Certainty and Uncertainty</td><td><a class="link_ptr" href="CE.html" title="17"><span class="headingNumber">21 </span>Certainty, Precision, and Responsibility</a></td></tr><tr><td>core</td><td>Common Core</td><td><a class="link_ptr" href="CO.html" title="6"><span class="headingNumber">3 </span>Elements Available in All TEI Documents</a></td></tr><tr><td>corpus</td><td>Metadata for Language Corpora</td><td><a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a></td></tr><tr><td>dictionaries</td><td>Print Dictionaries</td><td><a class="link_ptr" href="DI.html" title="12"><span class="headingNumber">9 </span>Dictionaries</a></td></tr><tr><td>drama</td><td>Performance Texts</td><td><a class="link_ptr" href="DR.html" title="10"><span class="headingNumber">7 </span>Performance Texts</a></td></tr><tr><td>figures</td><td>Tables, Formulae, Figures</td><td><a class="link_ptr" href="FT.html" title="22"><span class="headingNumber">14 </span>Tables, Formulæ, Graphics and Notated Music</a></td></tr><tr><td>gaiji</td><td>Character and Glyph Documentation</td><td><a class="link_ptr" href="WD.html" title="25"><span class="headingNumber">5 </span>Characters, Glyphs, and Writing Modes</a></td></tr><tr><td>header</td><td>Common Metadata</td><td><a class="link_ptr" href="HD.html" title="5"><span class="headingNumber">2 </span>The TEI Header</a></td></tr><tr><td>iso-fs</td><td>Feature Structures</td><td><a class="link_ptr" href="FS.html" title="16"><span class="headingNumber">18 </span>Feature Structures</a></td></tr><tr><td>linking</td><td>Linking, Segmentation, and Alignment</td><td><a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">16 </span>Linking, Segmentation, and Alignment</a></td></tr><tr><td>msdescription</td><td>Manuscript Description</td><td><a class="link_ptr" href="MS.html" title="Manuscript Description"><span class="headingNumber">10 </span>Manuscript Description</a></td></tr><tr><td>namesdates</td><td>Names, Dates, People, and Places</td><td><a class="link_ptr" href="ND.html" title="20"><span class="headingNumber">13 </span>Names, Dates, People, and Places</a></td></tr><tr><td>nets</td><td>Graphs, Networks, and Trees</td><td><a class="link_ptr" href="GD.html" title="21"><span class="headingNumber">19 </span>Graphs, Networks, and Trees</a></td></tr><tr><td>spoken</td><td>Transcribed Speech</td><td><a class="link_ptr" href="TS.html" title="11"><span class="headingNumber">8 </span>Transcriptions of Speech</a></td></tr><tr><td>tagdocs</td><td>Documentation Elements</td><td><a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a></td></tr><tr><td>tei</td><td>TEI Infrastructure</td><td><a class="link_ptr" href="ST.html" title="3"><span class="headingNumber">1 </span>The TEI Infrastructure</a></td></tr><tr><td>textcrit</td><td>Text Criticism</td><td><a class="link_ptr" href="TC.html" title="19"><span class="headingNumber">12 </span>Critical Apparatus</a></td></tr><tr><td>textstructure</td><td>Default Text Structure</td><td><a class="link_ptr" href="DS.html" title="7"><span class="headingNumber">4 </span>Default Text Structure</a></td></tr><tr><td>transcr</td><td>Transcription of Primary Sources</td><td><a class="link_ptr" href="PH.html" title="18"><span class="headingNumber">11 </span>Representation of Primary Sources</a></td></tr><tr><td>verse</td><td>Verse</td><td><a class="link_ptr" href="VE.html" title="9"><span class="headingNumber">6 </span>Verse</a></td></tr></table></div><p>For each module listed above, the corresponding chapter gives a full description of the classes, elements, and macros which it makes available when it is included in a schema. Other chapters of these Guidelines explore other aspects of using the TEI scheme.</p></div><div class="div2" id="STIN"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STMA"><span class="headingNumber">1.1 </span>TEI Modules</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STEC"><span class="headingNumber">1.3 </span>The TEI Class System</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#STIN" title="link to this section "><span class="invisible">TEI: Defining a TEI Schema</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.2 </span><span class="head">Defining a TEI Schema</span></h3><p>To determine that an XML document is valid (as opposed to merely well-formed), its structure must be checked against a schema, as discussed in chapter <a class="link_ptr" href="SG.html" title="A Gentle Introduction to XML"><span class="headingNumber">v. </span>A Gentle Introduction to XML</a>. For a valid TEI document, this schema must be a conformant TEI schema, as further defined in chapter <a class="link_ptr" href="USE.html#CF" title="Conformance"><span class="headingNumber">23.4 </span>Conformance</a>. Local systems may allow their schema to be implicit, but for interchange purposes the schema associated with a document <em>must</em> be made explicit. The method of doing this recommended by these Guidelines is to provide explicitly or by reference a TEI schema specification against which the document may be validated.</p><p>A TEI-conformant schema is a specific combination of TEI modules, possibly also including additional declarations that modify the element and attribute declarations contained by each module, for example to suppress or rename some elements. The TEI provides an application-independent way of specifying a TEI schema by means of the <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> element defined in chapter <a class="link_ptr" href="TD.html" title="27"><span class="headingNumber">22 </span>Documentation Elements</a>. The same system may also be used to specify a schema which extends the TEI by adding new elements explicitly, or by reference to other XML vocabularies. In either case, the specification may be processed to generate a formal schema, expressed in a variety of specific schema languages, such as XML DTD language, RELAX NG, or W3C Schema. These output schemas can then be used by an XML processor such as a validator or editor to validate or otherwise process documents. Further information about the processing of a TEI formal specification is given in chapter <a class="link_ptr" href="USE.html" title="Using the TEI"><span class="headingNumber">23 </span>Using the TEI</a>.</p><div class="div3" id="STINsimpleExample"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STINlargerExample"><span class="headingNumber">1.2.2 </span>A Larger Customization</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#STINsimpleExample" title="link to this section "><span class="invisible">TEI: A Simple Customization</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.2.1 </span><span class="head">A Simple Customization</span></h4><div class="p">The simplest customization of the TEI scheme combines just the four recommended modules mentioned above. In ODD format, this schema specification takes this form: <div id="index-egXML-d52e3585" class="pre egXML_valid"><span class="element"><schemaSpec <span class="attribute">ident</span>="<span class="attributevalue">TEI-minimal</span>" <span class="attribute">start</span>="<span class="attributevalue">TEI</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">core</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">textstructure</span>"/></span><br /><span class="element"></schemaSpec></span></div></div><p>This schema specification contains references to each of four modules, identified by the <span class="att">key</span> attribute on the <a class="gi" title="(module reference) references a module which is to be incorporated into a schema." href="ref-moduleRef.html">moduleRef</a> element. The schema specification itself is also given an identifier (<span class="ident">TEI-minimal</span>). An ODD processor will generate an appropriate schema from this set of declarations, expressed using the XML DTD language, the ISO RELAX NG language, the W3C Schema language, or in principle any other adequately powerful schema language. The resulting schema may then be associated with the document instance by one of a number of different mechanisms, as further described in chapter <a class="link_ptr" href="SG.html" title="A Gentle Introduction to XML"><span class="headingNumber">v. </span>A Gentle Introduction to XML</a>. The start point (or root element) of document instances to be validated against the schema is specified by means of the <span class="att">start</span> attribute. Further information about the processing of an ODD specification is given in <a class="link_ptr" href="USE.html#IM" title="Implementation of an ODD System"><span class="headingNumber">23.5 </span>Implementation of an ODD System</a>.</p></div><div class="div3" id="STINlargerExample"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STINsimpleExample"><span class="headingNumber">1.2.1 </span>A Simple Customization</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="#STINlargerExample" title="link to this section "><span class="invisible">TEI: A Larger Customization</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.2.2 </span><span class="head">A Larger Customization</span></h4><p>These Guidelines introduce each of the modules making up the TEI scheme one by one, and therefore, for clarity of exposition, each chapter focusses on elements drawn from a single module. In reality, of course, the markup of a text will draw on elements taken from many different modules, partly because texts are heterogeneous objects, and partly because encoders have different goals. Some examples of this heterogeneity include: </p><ul class="bulleted"><li class="item">a text may be a collection of other texts of different types: for example, an anthology of prose, verse, and drama;</li><li class="item">a text may contain other smaller, embedded texts: for example, a poem or song included in a prose narrative;</li><li class="item">some sections of a text may be written in one form, and others in a different form: for example, a novel where some chapters are in prose, others take the form of dictionary entries, and still others the form of scenes in a play; </li><li class="item">an encoded text may include detailed analytic annotation, for example of rhetorical or linguistic features; </li><li class="item">an encoded text may combine a literal transcription with a diplomatic edition of the same or different sources; </li><li class="item">the description of a text may require additional specialized metadata elements, for example when describing manuscript material in detail.</li></ul><p>The TEI provides mechanisms to support all of these and many other use cases. The architecture permits elements and attributes from any combination of modules to co-exist within a single schema. Within particular modules, elements and attributes are provided to support differing views of the ‘granularity’ of a text, for example: </p><ul class="bulleted"><li class="item">a definition of a corpus or collection as a series of <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple <TEI> elements may be combined to form a <teiCorpus> element." href="ref-TEI.html">TEI</a> documents, sharing a common TEI header (see chapter <a class="link_ptr" href="CC.html" title="23"><span class="headingNumber">15 </span>Language Corpora</a>)</li><li class="item">a definition of composite texts which combine optional front- and back-matter with a group of collected texts, themselves possibly composite (see section <a class="link_ptr" href="DS.html#DSGRP" title="Grouped Texts"><span class="headingNumber">4.3.1 </span>Grouped Texts</a>)</li><li class="item">an element for the representation of <span class="term">embedded texts</span>, where one narrative appears to ‘float’ within another (see section <a class="link_ptr" href="DS.html#DSFLT" title="Floating Texts"><span class="headingNumber">4.3.2 </span>Floating Texts</a>)</li></ul><p>Subsequent chapters of these Guidelines describe in detail markup constructs appropriate for these and many other possible features of interest. The markup constructs can be combined as needed for any given set of applications or project.</p><div class="p">For example, a project aiming to produce an ambitious digital edition of a collection of manuscript materials, to include detailed metadata about each source, digital images of the content, along with a detailed transcription of each source, and a supporting biographical and geographical database might need a schema combining several modules, as follows: <div id="index-egXML-d52e3659" class="pre egXML_valid"><span class="element"><schemaSpec <span class="attribute">ident</span>="<span class="attributevalue">TEI-PROJECT</span>" <span class="attribute">start</span>="<span class="attributevalue">TEI</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">core</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">textstructure</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">msdescription</span>"/></span><br /><span class="comment"><!-- manuscript description --></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">transcr</span>"/></span><br /><span class="comment"><!-- transcription of primary sources --></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">figures</span>"/></span><br /><span class="comment"><!-- figures and tables --></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">namesdates</span>"/></span><br /><span class="comment"><!-- names, dates, people, and places --></span><br /><span class="element"></schemaSpec></span></div></div><div class="p">Alternatively, a simpler schema might be used for a part of such a project: those preparing the transcriptions, for example, might need only elements from the <span class="ident-module">core</span>, <span class="ident-module">textstructure</span>, and <span class="ident-module">transcr</span> modules, and might therefore prefer to use a simpler schema such as that generated by the following: <div id="index-egXML-d52e3684" class="pre egXML_valid"><span class="element"><schemaSpec <span class="attribute">ident</span>="<span class="attributevalue">TEI-TRANSCR</span>" <span class="attribute">start</span>="<span class="attributevalue">TEI</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">core</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">textstructure</span>"/></span><br /> <span class="element"><moduleRef <span class="attribute">key</span>="<span class="attributevalue">transcr</span>"/></span><br /><span class="element"></schemaSpec></span></div></div><p>The TEI architecture also supports more detailed customization beyond the simple selection of modules. A schema may suppress elements from a module, suppress some of their attributes, change their names, or even add new elements and attributes. Detailed discussion of the kind of modification possible in this way is provided in <a class="link_ptr" href="USE.html#MD" title="Customization"><span class="headingNumber">23.3 </span>Customization</a> and conformance rules relating to their application are discussed in <a class="link_ptr" href="USE.html#CF" title="Conformance"><span class="headingNumber">23.4 </span>Conformance</a>. These facilities are available for any schema language (though some features may not be available in all languages). The ODD language also makes it possible to combine TEI and non-TEI modules into a single schema, provided that the non-TEI module is expressed using the RELAX NG schema language (see further <a class="link_ptr" href="TD.html#ST-aliens" title="Combining TEI and NonTEI Modules"><span class="headingNumber">22.8.2 </span>Combining TEI and Non-TEI Modules</a>).</p></div></div><div class="div2" id="STEC"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STIN"><span class="headingNumber">1.2 </span>Defining a TEI Schema</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STmacros"><span class="headingNumber">1.4 </span>Macros</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#STEC" title="link to this section "><span class="invisible">TEI: The TEI Class System</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3 </span><span class="head">The TEI Class System</span></h3><p>The TEI scheme distinguishes about five hundred different elements. To aid comprehension, modularity, and modification, the majority of these elements are formally classified in some way. Classes are used to express two distinct kinds of commonality among elements. The elements of a class may share some set of attributes, or they may appear in the same locations in a content model. A class is known as an <span class="term">attribute class</span> if its members share attributes, and as a <span class="term">model class</span> if its members appear in the same locations. In either case, an element is said to <span class="term">inherit</span> properties from any classes of which it is a member.</p><p>Classes (and therefore elements which are members of those classes) may also inherit properties from other classes. For example, supposing that class A is a member (or a <span class="term">subclass</span>) of class B, any element which is a member of class A will inherit not only the properties defined by class A, but also those defined by class B. In such a situation, we also say that class B is a <span class="term">superclass</span> of class A. The properties of a superclass are inherited by all members of its subclasses.</p><p>A basic understanding of the classes into which the TEI scheme is organized is strongly recommended and is essential for any successful customization of the system.</p><div class="div2" id="STECAT"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STECCM"><span class="headingNumber">1.3.2 </span>Model Classes</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#STECAT" title="link to this section "><span class="invisible">TEI: Attribute Classes</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1 </span><span class="head">Attribute Classes</span></h4><p>An attribute class groups together elements which share some set of common attributes. Attribute classes are given names composed of the prefix <code>att.</code>, often followed by an adjective. For example, the members of the class <a class="link_odd" title="provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced." href="ref-att.canonical.html">att.canonical</a> have in common a <span class="att">key</span> and a <span class="att">ref</span> attribute, both of which are inherited from their membership in the class rather than individually defined for each element. These attributes are said to be defined by (or inherited from) the <a class="link_odd" title="provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced." href="ref-att.canonical.html">att.canonical</a> class. If another element were to be added to the TEI scheme for which these attributes were considered useful, the simplest way to provide them would be to make the new element a member of the <a class="link_odd" title="provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced." href="ref-att.canonical.html">att.canonical</a> class. Note also that this method ensures that the attributes in question are always defined in the same way, taking the same default values etc., no matter which element they are attached to.</p><p>Some attribute classes are defined within the <span class="ident-module">tei</span> infrastructural module and are thus globally available. Other attribute classes are specific to particular modules and thus defined in other chapters. Attributes defined by such classes will not be available unless the module concerned is included in a schema.</p><p>The attributes provided by an attribute class are those specified by the class itself, either directly, or by inheritance from another class. For example, the attribute class <a class="link_odd" title="provides a set of attributes common to all elements which enclose groups of pointer elements." href="ref-att.pointing.group.html">att.pointing.group</a> provides attributes <span class="att">domains</span> and <span class="att">targFunc</span> to all of its members. This class is however a subclass of 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, from which its members also inherit the attributes <span class="att">target</span>, <span class="att">targetLang</span> and <span class="att">evaluate</span>. Members of the class <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> will thus have these three attributes, while members of the class <a class="link_odd" title="provides a set of attributes common to all elements which enclose groups of pointer elements." href="ref-att.pointing.group.html">att.pointing.group</a> will have all five.</p><p>Note that some modules define superclasses of an existing infrastructural class. For example, the global attribute class <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a> makes attributes <span class="att">org</span> and <span class="att">sample</span> available, while the <a class="link_odd" title="defines a set of attributes which certain elements may use to represent metrical information." href="ref-att.metrical.html">att.metrical</a> class, which is specific to the <span class="ident-module">verse</span> module, provides attributes <span class="att">met</span>, <span class="att">real</span>, and <span class="att">rhyme</span>. Because <a class="link_odd" title="defines a set of attributes which certain elements may use to represent metrical information." href="ref-att.metrical.html">att.metrical</a> is defined as a superclass of <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a>, all five of these attributes are available to elements; the declaration for <a class="link_odd" title="defines a set of attributes which certain elements may use to represent metrical information." href="ref-att.metrical.html">att.metrical</a> adds its three attributes to the three already defined by <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a> when the <span class="ident-module">verse</span> module is included in a schema. If, however, this module is not included in a schema, then the <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a> class supplies only the two attributes first mentioned.</p><p>Attributes specific to particular modules are documented along with the relevant module rather than in the present chapter. One particular attribute class, known as <a class="link_odd" title="provides attributes common to all elements in the TEI encoding scheme." href="ref-att.global.html">att.global</a>, is common to all modules, and is therefore described in some detail in the next section. A full list of all attribute classes is given in <a class="link_ptr" href="REF-CLASSES-ATTS.html" title="Attribute Classes"><span class="headingNumber">Appendix B </span>Attribute Classes</a> below.</p><div class="div2" id="STGA"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></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="#STGA" title="link to this section "><span class="invisible">TEI: Global Attributes</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1 </span><span class="head">Global Attributes</span></h5><p>The following attributes are defined in the infrastructure module for every TEI element. </p><ul class="specList"><li><span class="specList-classSpec"><a href="ref-att.global.html">att.global</a></span> provides attributes common to all elements in the TEI encoding scheme.<table class="specDesc"><tr><td class="Attribute"><span class="att">xml:id</span></td><td>(identifier) provides a unique identifier for the element bearing the attribute.</td></tr><tr><td class="Attribute"><span class="att">n</span></td><td>(number) gives a number (or other label) for an element, which is not necessarily unique within the document.</td></tr><tr><td class="Attribute"><span class="att">xml:lang</span></td><td>(language) indicates the language of the element content using a ‘tag’ generated according to <a class="link_ref" href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">BCP 47</a>.</td></tr><tr><td class="Attribute"><span class="att">rend [att.global.rendition]</span></td><td>(rendition) indicates how the element in question was rendered or presented in the source text.</td></tr><tr><td class="Attribute"><span class="att">style [att.global.rendition]</span></td><td>contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text</td></tr><tr><td class="Attribute"><span class="att">rendition [att.global.rendition]</span></td><td>points to a description of the rendering or presentation used for this element in the source text.</td></tr><tr><td class="Attribute"><span class="att">xml:base</span></td><td>provides a base URI reference with which applications can resolve relative URI references into absolute URI references.</td></tr><tr><td class="Attribute"><span class="att">xml:space</span></td><td>signals an intention about how white space should be managed by applications.</td></tr><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">cert [att.global.responsibility]</span></td><td>(certainty) signifies the degree of certainty associated with the intervention or interpretation.</td></tr><tr><td class="Attribute"><span class="att">resp [att.global.responsibility]</span></td><td>(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.</td></tr></table></li></ul><p>Some of these attributes (specifically <span class="att">xml:id</span>, <span class="att">n</span>, <span class="att">xml:lang</span>, <span class="att">xml:base</span> and <span class="att">xml:space</span>) are provided by the <a class="link_odd" title="provides attributes common to all elements in the TEI encoding scheme." href="ref-att.global.html">att.global</a> attribute class itself. The others are provided by one its subclasses <a class="link_odd" title="provides rendering attributes common to all elements in the TEI encoding scheme." href="ref-att.global.rendition.html">att.global.rendition</a>, <a class="link_odd" title="provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it." href="ref-att.global.responsibility.html">att.global.responsibility</a>, or <a class="link_odd" title="provides an attribute used by elements to point to an external source." href="ref-att.global.source.html">att.global.source</a>. Their usage is discussed in the following subsections.</p><p>Several other globally-available attributes are defined by other subclasses of the <a class="link_odd" title="provides attributes common to all elements in the TEI encoding scheme." href="ref-att.global.html">att.global</a> class. These are provided by other modules, and are therefore discussed in the chapter discussing that module. A brief summary table is provided in section <a class="link_ptr" href="ST.html#STGAothers" title="Other Globally Available Attributes"><span class="headingNumber">1.3.1.1.7 </span>Other Globally Available Attributes</a> below.</p><div class="teidiv4" id="STGAid"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAla"><span class="headingNumber">1.3.1.1.2 </span>Language Indicators</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAid" title="link to this section "><span class="invisible">TEI: Element Identifiers and Labels</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.1 </span><span class="head">Element Identifiers and Labels</span></h6><p>The value supplied for the <span class="att">xml:id</span> attribute must be a legal <span class="term">name</span>, as defined in the World Wide Web Consortium's <a class="link_ref" href="http://www.w3.org/TR/REC-xml/">XML Recommendation</a>. This means that it must begin with a letter, or the underscore character (<span class="q">‘_’</span>), and contain no characters other than letters, digits, hyphens, underscores, full stops, and certain combining and extension characters.<span id="Note38_return"><a class="notelink" title="The colon is also by default a valid name character; however, it has a specific purpose in XML (to indicate namespace prefixes), and may not therefore…" href="#Note38"><sup>1</sup></a></span></p><p>In XML names (and thus the values of <span class="att">xml:id</span> in an XML TEI document) uppercase and lowercase letters are distinguished, and thus <span class="mentioned">partTime</span> and <span class="mentioned">parttime</span> are two distinctly different names, and could (though perhaps unwisely) be used to denote two different element occurrences.</p><div class="p">If two elements are given the same identifier, a validating XML parser will signal a syntax error. The following example, therefore, is <em>not</em> valid: <div id="index-egXML-d52e3916" class="pre cdata egXML_invalid">
<p xml:id="PAGE1"><q>What's it going to be then, eh?</q></p>
<p xml:id="PAGE1">There was me, that is Alex, and my three droogs, that is Pete,
Georgie, and Dim, ... </p><div style="float: right;"><a href="BIB.html#STGA-eg-4">bibliography</a> </div></div></div><p>For a discussion of methods of providing unique identifiers for elements, see section <a class="link_ptr" href="CO.html#CORS2" title="Creating New Reference Systems"><span class="headingNumber">3.10.2 </span>Creating New Reference Systems</a>.</p><div class="p">The <span class="att">n</span> attribute also provides an identifying name or number for an element, but in this case the information need not be a legal <span class="att">xml:id</span> value. Its value may be any string of characters; typically it is a number or other similar enumerator or label. For example, the numbers given to the items of a numbered list may be recorded with the <span class="att">n</span> attribute; this would make it possible to record errors in the numeration of the original, as in this list of chapters, transcribed from a faulty original in which the number 10 is used twice, and 11 is omitted: <div id="index-egXML-d52e3934" class="pre egXML_valid"><span class="element"><list <span class="attribute">rend</span>="<span class="attributevalue">numbered</span>"></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span>About These Guidelines<span class="element"></item></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">2</span>"></span>A Gentle Introduction to XML<span class="element"></item></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">9</span>"></span>Verse<span class="element"></item></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">10</span>"></span>Drama<span class="element"></item></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">10</span>"></span>Spoken Materials <span class="element"></item></span><br /> <span class="element"><item <span class="attribute">n</span>="<span class="attributevalue">12</span>"></span>Dictionaries<span class="element"></item></span><br /><span class="element"></list></span></div> The <span class="att">n</span> attribute may also be used to record non-unique names associated with elements in a text, possibly together with a unique identifier as in the following example: <div id="index-egXML-d52e3953" class="pre egXML_valid"><span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">book</span>" <span class="attribute">n</span>="<span class="attributevalue">one</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">TXT0101</span>"></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"><div <span class="attribute">type</span>="<span class="attributevalue">stanza</span>" <span class="attribute">n</span>="<span class="attributevalue">xlii</span>"></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></div></span><br /><span class="element"></div></span><div style="float: right;"><a href="BIB.html#STGA-eg-6">bibliography</a> </div></div></div><div class="p">As noted above there is no requirement to record a value for either the <span class="att">xml:id</span> or the <span class="att">n</span> attribute. Any XML processor can identify the sequential position of one element within another in an XML document without any additional tagging. An encoding in which each line of a long poem is explicitly labelled with its numerical sequence such as the following <div id="index-egXML-d52e3967" class="pre egXML_valid"><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">1</span>"></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></l></span><br /><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">2</span>"></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></l></span><br /><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">3</span>"></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></l></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><l <span class="attribute">n</span>="<span class="attributevalue">100</span>"></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></l></span></div> is therefore probably redundant.</div></div><div class="teidiv4" id="STGAla"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAid"><span class="headingNumber">1.3.1.1.1 </span>Element Identifiers and Labels</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAre"><span class="headingNumber">1.3.1.1.3 </span>Rendition Indicators</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAla" title="link to this section "><span class="invisible">TEI: Language Indicators</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.2 </span><span class="head">Language Indicators</span></h6><p>The <span class="att">xml:lang</span> attribute indicates the natural language and writing system applicable to the content of a given element. If it is not specified, the value is inherited from that of the immediately enclosing element. As a rule, therefore, it is simplest to specify the base language of the text on the <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple <TEI> elements may be combined to form a <teiCorpus> element." href="ref-TEI.html">TEI</a> element, and allow most elements to take the default value for <span class="att">xml:lang</span>; the language of an element then need be explicitly specified only for elements in languages other than the base language. For this reason, it is recommended practice to supply a default value for the <span class="att">xml:lang</span> attribute, either on the <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple <TEI> elements may be combined to form a <teiCorpus> element." href="ref-TEI.html">TEI</a> root element, or on both 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> and 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. The latter is appropriate in the not uncommon case where the text element in a TEI document uses a different default language from that of the TEI header attached to it. Other language shifts in the source should be explicitly identified by use of the <span class="att">xml:lang</span> attribute on an element at an appropriate level wherever possible.</p><div class="p">In the following example schematic, an English language TEI header is attached to an English language text: <div id="index-egXML-d52e4010" class="pre egXML_feasible"><span class="element"><TEI <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>" xmlns="http://www.tei-c.org/ns/1.0"></span><br /> <span class="element"><teiHeader></span><br /><span class="comment"><!-- ... --></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></div></div><div class="p">The same effect would be obtained by specifying the default language for both header and text: <div id="index-egXML-d52e4019" 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">en</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">The latter approach is necessary in the case where the two differ: for example, where an English language header is applied to a French text: <div id="index-egXML-d52e4028" 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">en</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">fr</span>"></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></text></span><br /><span class="element"></TEI></span></div></div><div class="p">The same principle applies at any hierarchic level. In the following example, the default language of the text is French, but one section of it is in German: <div id="index-egXML-d52e4037" 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">en</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">fr</span>"></span><br /> <span class="element"><body></span><br /> <span class="element"><div></span><br /><span class="comment"><!-- chapter one is in French --></span><br /> <span class="element"></div></span><br /> <span class="element"><div <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"></span><br /><span class="comment"><!-- chapter two is in German --></span><br /> <span class="element"></div></span><br /> <span class="element"><div></span><br /><span class="comment"><!-- chapter three is French --></span><br /> <span class="element"></div></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"></body></span><br /> <span class="element"></text></span><br /><span class="element"></TEI></span></div></div><div class="p">Similarly, in the following example the <span class="att">xml:lang</span> attribute on the <a class="gi" title="contains a single-word, multi-word, or symbolic designation which is regarded as a technical term." href="ref-term.html">term</a> element allows us to record the fact that the technical terms used are Latin rather than English; no <span class="att">xml:lang</span> attribute is needed on 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, by contrast, because it is in the same language as its parent. <div id="index-egXML-d52e4065" class="pre egXML_valid"><span class="element"><p <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"></span>The<br /> constitution declares <span class="element"><q></span>that no bill of attainder or <span class="element"><term <span class="attribute">xml:lang</span>="<span class="attributevalue">la</span>"></span>ex post<br /> facto<span class="element"></term></span> law shall be passed.<span class="element"></q></span> ...<span class="element"></p></span><div style="float: right;"><a href="BIB.html#STGA-eg-10">bibliography</a> </div></div></div><div class="p">Note that in cases where it is advisable or necessary to identify the language of the text that is pointed at, the (non-global) attribute <span class="att">targetLang</span> should be used, for example in <div id="index-egXML-d52e4080" class="pre egXML_valid"><span class="element"><ptr <span class="attribute">target</span>="<span class="attributevalue">x12</span>" <span class="attribute">targetLang</span>="<span class="attributevalue">fr</span>"/></span></div> the pointer references text written in French.</div><p>The values used for the <span class="att">xml:lang</span> and <span class="att">targetLang</span> attributes must be constructed in a particular way, using values from standard lists. See further <a class="link_ptr" href="CH.html#CHSH" title="Language Identification"><span class="headingNumber">vi.1. </span>Language Identification</a>.</p><p>Additional information about a particular language may be supplied in the <a class="gi" title="characterizes a single language or sublanguage used within a text." href="ref-language.html">language</a> element within the header (see section <a class="link_ptr" href="HD.html#HD41" title="Language Usage"><span class="headingNumber">2.4.2 </span>Language Usage</a>).</p></div><div class="teidiv4" id="STGAre"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAla"><span class="headingNumber">1.3.1.1.2 </span>Language Indicators</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAso"><span class="headingNumber">1.3.1.1.4 </span>Sources, certainty, and responsibility</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAre" title="link to this section "><span class="invisible">TEI: Rendition Indicators</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.3 </span><span class="head">Rendition Indicators</span></h6><div class="p">The <span class="att">rend</span>, <span class="att">rendition</span>, and <span class="att">style</span> attributes are all used to give information about the physical presentation of the text in the source. In the following example, <span class="att">rend</span> is used to indicate that both the emphasized word and the proper name are printed in italics: <div id="index-egXML-d52e4117" class="pre egXML_valid"><span class="element"><p></span> ... Their motives <span class="element"><emph <span class="attribute">rend</span>="<span class="attributevalue">italics</span>"></span>might<span class="element"></emph></span> be pure<br /> and pious; but he was equally alarmed by his knowledge of the ambitious <span class="element"><name <span class="attribute">rend</span>="<span class="attributevalue">italics</span>"></span>Bohemond<span class="element"></name></span>, and his ignorance of the Transalpine chiefs:<br /> ...<span class="element"></p></span><div style="float: right;"><a href="BIB.html#STGA-eg-11">bibliography</a> </div></div> The same effect might be achieved using the <span class="att">style</span> attribute, as follows: <div id="index-egXML-d52e4131" class="pre egXML_valid"><span class="element"><p></span> ... Their motives <span class="element"><emph <span class="attribute">style</span>="<span class="attributevalue">font-style: italic</span>"></span>might<span class="element"></emph></span> be pure and pious; but he was equally alarmed by his knowledge of<br /> the ambitious <span class="element"><name <span class="attribute">style</span>="<span class="attributevalue">font-style: italic</span>"></span>Bohemond<span class="element"></name></span>, and his ignorance of<br /> the Transalpine chiefs: ...<span class="element"></p></span><div style="float: right;"><a href="BIB.html#STGA-eg-11">bibliography</a> </div></div> If all or most <a class="gi" title="(emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect." href="ref-emph.html">emph</a> and <a class="gi" title="(name, proper noun) contains a proper noun or noun phrase." href="ref-name.html">name</a> elements are rendered in the text by italics, it will be more convenient to register that fact in the TEI header once and for all (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 discussed below) and specify a <span class="att">rend</span> or <span class="att">style</span> value only for any elements which deviate from the stated rendition.</div><p>The main difference between <span class="att">rend</span> attribute and <span class="att">style</span> is that the value used for the former may contain one or more tokens from any vocabulary devised by the encoder, separated by space characters, whereas the value used for the latter must be a single string taken from a formally-defined style definition language such as CSS. The <span class="att">rend</span> attribute values are sequence-indeterminate set of whitespace-separated tokens, whereas <span class="att">style</span> values allow whitespace and sequence relationships as part of the formally-defined style definition language.</p><div class="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 defined in <a class="link_ptr" href="HD.html#HD57" title="The Tagging Declaration"><span class="headingNumber">2.3.4 </span>The Tagging Declaration</a> may be used to hold repeatedly-used format descriptions. 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 can then be associated with any element, either by default, or by means of the global <span class="att">rendition</span> attribute. For example: <div id="index-egXML-d52e4184" class="pre egXML_valid"><span class="element"><tagsDecl></span><br /><span class="comment"><!-- define italic style using CSS, selecting it as default for emph and hi elements --></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">IT</span>" <span class="attribute">scheme</span>="<span class="attributevalue">css</span>"<br /> <span class="attribute">selector</span>="<span class="attributevalue">emph hi</span>"></span>font-style: italic;<span class="element"></rendition></span><br /><span class="comment"><!-- define a serif font family, selecting it as default for the text element --></span><br /> <span class="element"><rendition <span class="attribute">xml:id</span>="<span class="attributevalue">FontRoman</span>" <span class="attribute">scheme</span>="<span class="attributevalue">css</span>"<br /> <span class="attribute">selector</span>="<span class="attributevalue">text</span>"></span>font-family: serif;<span class="element"></rendition></span><br /><span class="element"></tagsDecl></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><text></span><br /> <span class="element"><body></span><br /> <span class="element"><div></span><br /> <span class="element"><p <span class="attribute">rendition</span>="<span class="attributevalue">#IT</span>"></span><br /><span class="comment"><!-- this paragraph uses the seriffed font, but is in italic--></span><br /> <span class="element"></p></span><br /> <span class="element"><p></span><br /><span class="comment"><!-- this paragraph uses the seriffed font, but is not in italic --></span><br /> <span class="element"></p></span><br /> <span class="element"></div></span><br /> <span class="element"></body></span><br /><span class="element"></text></span></div></div><p>The <span class="att">rendition</span> attribute always points to one or more <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 defines some aspect of the rendering or appearance of the text in its original form. These details may most conveniently be described using a formal style definition language, such as CSS (<a class="link_ptr" href="BIB.html#CSS1" title="Håkon Wium Lie Bert Bos Cascading Style Sheets Level 1W3C11 January 1999">Lie and Bos (eds.) (1999)</a>) or XSL-FO (<a class="link_ptr" href="BIB.html#XSL11" title="Anders Berglund Extensible Stylesheet Language (XSL) Version 1.1W3C5 December 2006">Berglund (ed.) (2006)</a>); in some other formal language developed for a specific project; or even informally in running prose. Although languages such as CSS and XSL-FO are generally used to describe document output to screen or print, they nonetheless provide formal and precise mechanisms for describing the appearance of source documents, especially print documents, but also many aspects of manuscript documents. For example, both CSS and XSL-FO provide mechanisms for describing typefaces, weight, and styles; character and line spacing; and so on.</p><p>As noted above, the <span class="att">style</span> attribute is provided for encoders wishing to describe the appearance of individual source elements using a language such as CSS directly rather than by reference to 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. Its value may be any expression in the chosen formal style definition language.</p><p>Formal definition languages such as CSS typically identity a series of <span class="term">properties</span> (such as font-style or margin-left) for which <span class="term">values</span> are specified. A sequence of such property-value pairs makes up a stylesheet. The TEI uses such languages simply to describe the appearance of a source document, rather than to control how it should be formatted.</p><p>In the TEI scheme, it is possible to supply information about the appearance of elements within a source document in the following distinct ways: </p><ol class="numbered"><li class="item">One or more properties may be specified as the default for a set of elements (based on an external scheme, by default CSS), using <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 and their <span class="att">selector</span> attributes;</li><li class="item">One or more properties may be specified for individual element occurrences, using the <span class="att">rend</span> attribute with any convenient set of one or more sequence-indeterminate tokens;</li><li class="item">One or more properties may be specified for individual element occurrences, using the <span class="att">rendition</span> attribute to point to <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;</li><li class="item">One or more properties may be supplied explicitly for individual element occurrences, using the <span class="att">style</span> attribute.</li></ol><p>If the same property is specified in more than one of the above ways, the one with the highest number in the list above is understood to be applicable. The resulting properties from each way are then combined to provide the full set of property-value pairs applicable to the given element, and (by default) to all of its children. </p><p>For simplicity of processing, the same formal style definition should be used throughout; however, the architecture does permit this to be varied, by using the <span class="att">scheme</span> attribute to indicate a different language for one or more <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. Care should be taken to ensure that such values can be meaningfully combined. Similar considerations apply to the use of the <span class="att">rend</span> attribute, if this is used in combination with either <span class="att">rendition</span> or <span class="att">style</span>.</p><p>Note that these TEI attributes always describe the rendition or appearance of the source document, <em>not</em> intended output renditions, although often the two may be closely related.</p></div><div class="teidiv4" id="STGAso"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAre"><span class="headingNumber">1.3.1.1.3 </span>Rendition Indicators</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAba"><span class="headingNumber">1.3.1.1.5 </span>Evaluation of Links</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAso" title="link to this section "><span class="invisible">TEI: Sources, certainty, and responsibility</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.4 </span><span class="head">Sources, certainty, and responsibility</span></h6><p>The <span class="att">source</span> attribute is used to indicate the source of an element and its content, for example by pointing to a bibliographic citation for a quotation to indicate the source from which it derives. The target of the pointer may be an entry in a bibliographic list of some kind, or a pointer to a digital version of the source itself.</p><div class="p">As with other TEI pointers, the value of this attribute is expressed as any form of URI, for example an absolute URL, a relative URL, or a private scheme URI that is expanded to a relative or absolute URL as documented in 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>. In the following typical example a relative ‘bare name’ URL value is used to point to a <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> elsewhere in the bibliography of the document which contains a bibliographic source for the quotation itself: <div id="index-egXML-d52e4302" class="pre egXML_valid"><span class="element"><p></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"><quote <span class="attribute">source</span>="<span class="attributevalue">#chicago-15_ed</span>"></span>Grammatical theories<br /> are in flux, and the more we learn, the less we<br /> seem to know.<span class="element"></quote></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></p></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><bibl <span class="attribute">xml:id</span>="<span class="attributevalue">chicago-15_ed</span>"></span><br /> <span class="element"><title <span class="attribute">level</span>="<span class="attributevalue">m</span>"></span>The Chicago Manual of Style<span class="element"></title></span>,<br /> <span class="element"><edition></span>15th edition<span class="element"></edition></span>.<br /> <span class="element"><pubPlace></span>Chicago<span class="element"></pubPlace></span>:<br /> <span class="element"><publisher></span>University of Chicago Press<span class="element"></publisher></span> <br /> (<span class="element"><date></span>2003<span class="element"></date></span>),<br /> <span class="element"><biblScope <span class="attribute">unit</span>="<span class="attributevalue">page</span>"></span>p.147<span class="element"></biblScope></span>.<br /> <span class="element"></bibl></span></div></div><div class="p">Alternatively, the quotation might be directly linked to the online edition of this source using a full URI : <div id="index-egXML-d52e4330" class="pre egXML_valid"><span class="element"><p></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"><quote <span class="attribute">source</span>="<span class="attributevalue">http://www.chicagomanualofstyle.org/15/ch05/ch05_sec002.html</span>"></span>Grammatical theories<br /> are in flux, and the more we learn, the less we<br /> seem to know.<span class="element"></quote></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></p></span></div> </div><div class="p">The <span class="att">source</span> attribute is also used on schema documentation elements such as <a class="gi" title="(schema specification) generates a TEI-conformant schema and documentation for it." href="ref-schemaSpec.html">schemaSpec</a> or <a class="gi" title="points to the specification for some element which is to be included in a schema" href="ref-elementRef.html">elementRef</a> to indicate the location from which declarations for the components being defined may be obtained by an ODD processor. For example, a customization wishing to include the <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a> element specifically as it was in version 2.0.1 of TEI P5 would indicate the source for this on an <a class="gi" title="points to the specification for some element which is to be included in a schema" href="ref-elementRef.html">elementRef</a> element like the following: <div id="index-egXML-d52e4357" class="pre egXML_valid"><span class="element"><elementRef <span class="attribute">key</span>="<span class="attributevalue">p</span>" <span class="attribute">source</span>="<span class="attributevalue">tei:2.0.1</span>"/></span></div> Here the value of the <span class="att">source</span> attribute is provided using private URI syntax, using a short cut predefined for the TEI Guidelines. More generally, an ODD customization can point to a URI from which a compiled version of any ODD can be downloaded. The above shortcut is equivalent to <div id="index-egXML-d52e4363" class="pre egXML_valid"><span class="element"><elementRef <span class="attribute">key</span>="<span class="attributevalue">p</span>"<br /> <span class="attribute">source</span>="<span class="attributevalue">http://www.tei-c.org/Vault/P5/2.0.1/xml/tei/odd/p5subset.xml</span>"/></span></div> Elements such as <a class="gi" title="(module reference) references a module which is to be incorporated into a schema." href="ref-moduleRef.html">moduleRef</a> or <a class="gi" title="points to the specification for some element which is to be included in a schema" href="ref-elementRef.html">elementRef</a> can use the <span class="att">source</span> attribute in this way to point to any previously compiled set of TEI ODD specifications which are to be included in a schema, as further discussed in section <a class="link_ptr" href="TD.html#TDbuild" title="TEI customizations"><span class="headingNumber">22.8.1 </span>TEI customizations</a></div><div class="p">The <span class="att">cert</span> attribute provides a method of indicating the encoder's certainty concerning an intervention or interpretation represented by the markup. It is typically used where the encoder wishes to supply one or more possible corrections to a text, indicating the certainty they wish to attach to each, as in the following example: <div id="index-egXML-d52e4383" class="pre egXML_valid"> Blessed are the <span class="element"><choice></span><br /> <span class="element"><sic></span>cheesemakers<span class="element"></sic></span><br /> <span class="element"><corr <span class="attribute">cert</span>="<span class="attributevalue">high</span>"></span>peacemakers<span class="element"></corr></span><br /> <span class="element"><corr <span class="attribute">cert</span>="<span class="attributevalue">low</span>"></span>placemakers<span class="element"></corr></span><br /><span class="element"></choice></span>:<br /> for they shall be called the children of God.<div style="float: right;"><a href="BIB.html#pythonBrian">bibliography</a> </div></div> The <span class="att">cert</span> attribute will usually, as here, characterize the degree of certainty simply as <span class="val">high</span>, <span class="val">medium</span> or <span class="val">low</span>. In situations where a more detailed or nuanced indication is required, it can instead supply a probability value between <span class="val">0</span> (minimal probability) and <span class="val">1</span> (maximal probability). Other more sophisticated mechanisms are discussed in chapter <a class="link_ptr" href="CE.html" title="17"><span class="headingNumber">21 </span>Certainty, Precision, and Responsibility</a>.</div><div class="p">The <span class="att">resp</span> attribute is used to indicate the person or organization considered responsible for some aspects of the information encoded by an element. For example, the preceding example might be revised as follows to indicate the editors responsible for the two corrections: <div id="index-egXML-d52e4420" class="pre egXML_valid"> ... <span class="element"><corr <span class="attribute">cert</span>="<span class="attributevalue">high</span>" <span class="attribute">resp</span>="<span class="attributevalue">#ed1</span>"></span>peacemakers<span class="element"></corr></span><br /><span class="element"><corr <span class="attribute">cert</span>="<span class="attributevalue">low</span>" <span class="attribute">resp</span>="<span class="attributevalue">#ed2</span>"></span>placemakers<span class="element"></corr></span>...<div style="float: right;"><a href="BIB.html#pythonBrian">bibliography</a> </div></div> When a more detailed or nuanced representation of responsibility is required, it is recommended that the element indicated by the <span class="att">resp</span> attribute should not be a generic agent (for example a <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> or <a class="gi" title="(organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people." href="ref-org.html">org</a>) but a more precise element such as <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>, <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>, or <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> which can document the exact role played by the agent. In the following example, we indicate that the correction of <span class="val">n</span> to <span class="val">u</span> was made by a particular named transcriber: <div id="index-egXML-d52e4453" class="pre egXML_valid"><br /><span class="comment"><!-- in the <text> ... --></span><span class="element"><lg></span><br /><span class="comment"><!-- ... --></span><br /> <span class="element"><l></span>Punkes, Panders, baſe extortionizing<br /> sla<span class="element"><choice></span><br /> <span class="element"><sic></span>n<span class="element"></sic></span><br /> <span class="element"><corr <span class="attribute">resp</span>="<span class="attributevalue">#JENSJ</span>"></span>u<span class="element"></corr></span><br /> <span class="element"></choice></span>es,<span class="element"></l></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"></lg></span><br /><span class="comment"><!-- in the <teiHeader> ... --></span><br /><span class="comment"><!-- ... --></span><br /><span class="element"><respStmt <span class="attribute">xml:id</span>="<span class="attributevalue">JENSJ</span>"></span><br /> <span class="element"><resp></span>Transcriber<span class="element"></resp></span><br /> <span class="element"><name></span>Janelle Jenstad<span class="element"></name></span><br /><span class="element"></respStmt></span><div style="float: right;"><a href="BIB.html#TAYLOR">bibliography</a> </div></div> Pointing to multiple <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>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.). If appropriate, the <a class="gi" title="(name, proper noun) contains a proper noun or noun phrase." href="ref-name.html">name</a> element inside a <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> may also be associated with a more detailed <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> or <a class="gi" title="(organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people." href="ref-org.html">org</a> element using methods discussed in chapter <a class="link_ptr" href="ND.html" title="20"><span class="headingNumber">13 </span>Names, Dates, People, and Places</a>.</div></div><div class="teidiv4" id="STGAba"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAso"><span class="headingNumber">1.3.1.1.4 </span>Sources, certainty, and responsibility</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAxs"><span class="headingNumber">1.3.1.1.6 </span>XML Whitespace</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAba" title="link to this section "><span class="invisible">TEI: Evaluation of Links</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.5 </span><span class="head">Evaluation of Links</span></h6><p>Several TEI elements carry attributes whose values are defined as <code>anyURI</code>, meaning that such attributes supply a link or pointer, typically expressed as a URL. Like other XML applications, the TEI allows use of a special attribute to set the context within which relative URLs are to be evaluated. The global attribute <span class="att">xml:base</span> is defined as part of the XML specification and belongs to the XML namespace rather than the TEI namespace. We do not describe it in detail here: reference information about <span class="att">xml:base</span> is provided by <a class="link_ptr" href="BIB.html#XMLBASE" title="Jonathan Marsh Richard Tobin XML Base (Second Edition)W3C28 January 2009">Marsh and Tobin (eds.) (2009)</a></p><div class="p">In essence <span class="att">xml:base</span> is used to set a context for all relative URLs within the scope of the element on which it is specified. For example: <div id="index-egXML-d52e4513" class="pre egXML_valid"><span class="element"><body></span><br /> <span class="element"><div <span class="attribute">xml:base</span>="<span class="attributevalue">http://www.example.org/somewhere.xml</span>"></span><br /> <span class="element"><p></span><br /><span class="comment"><!--... --></span><br /> <span class="element"><ptr <span class="attribute">target</span>="<span class="attributevalue">elsewhere.xml</span>"/></span><br /><span class="comment"><!--... --></span><br /> <span class="element"></p></span><br /> <span class="element"></div></span><br /> <span class="element"><div></span><br /> <span class="element"><p></span><br /><span class="comment"><!--... --></span><br /> <span class="element"><ptr <span class="attribute">target</span>="<span class="attributevalue">elsewhere.xml</span>"/></span><br /><span class="comment"><!--... --></span><br /> <span class="element"></p></span><br /> <span class="element"></div></span><br /><span class="element"></body></span></div>The first <a class="gi" title="(pointer) defines a pointer to another location." href="ref-ptr.html">ptr</a> element here is within the scope of a <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> which supplies a value for <span class="att">xml:base</span>; its target is therefore to be found at <code>http://www.example.org/elsewhere.xml</code>. The second <a class="gi" title="(pointer) defines a pointer to another location." href="ref-ptr.html">ptr</a>, however, is within the scope of a <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> which does not change the default context, and its target is therefore a document in the same directory as the current document.</div><p>The <span class="att">xml:base</span> attribute is intended to enable the stable resolution of relative URIs in a document after that document's context may have changed (for example as a result of being embedded in another document via XInclude). Setting the <span class="att">xml:base</span> simply as a way to allow encoders to write shorter URIs is not recommended. In particular, <span class="att">xml:base</span> may cause ambiguity as to the referent of same-document references in the form <code>#id</code> (where <code>id</code> is an <span class="att">xml:id</span>). <a class="link_ref" href="https://tools.ietf.org/html/rfc3986#section-4.4">RFC 3986</a> states that URIs of this type should not result in the loading of a different document. The RFC therefore assumes that such references are internal to the document in which they are located. Using <span class="att">xml:base</span> to denote arbitrary external bases while also using same-document references may mean that software agents deal with these links in unexpected and inconsistent ways. Further discussion of this element and its effect on TEI linking methods is provided in chapter <a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">16 </span>Linking, Segmentation, and Alignment</a>.</p></div><div class="teidiv4" id="STGAxs"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAba"><span class="headingNumber">1.3.1.1.5 </span>Evaluation of Links</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STGAothers"><span class="headingNumber">1.3.1.1.7 </span>Other Globally Available Attributes</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAxs" title="link to this section "><span class="invisible">TEI: XML Whitespace</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.6 </span><span class="head">XML Whitespace</span></h6><p>The global attribute <span class="att">xml:space</span> provides a mechanism for indicating to systems processing an XML file how they should treat whitespace, that is, any sequences of consecutive tab (#x09), space (#x20), carriage return (#x0D) or linefeed (#x0A) characters. Like <span class="att">xml:id</span> this attribute is defined as part of the XML specification and belongs to the XML namespace rather than the TEI namespace. Complete information about this attribute is provided by <a class="link_ref" href="http://www.w3.org/TR/REC-xml/#sec-white-space">section 2.10 of the XML Specification</a>; here we provide a summary of how its use affects users of the TEI scheme.</p><p>The <span class="att">xml:space</span> attribute has only two permitted values: <span class="val">preserve</span> and <span class="val">default</span>. The first indicates that whitespace in a text node—every carriage return, every tab, etc.—should be maintained as is when the document is processed. The second (which is implied when the attribute is not supplied), indicates that whitespace should be handled ‘as appropriate’. Exactly what is deemed appropriate is left unspecified by the XML Recommendation.</p><div class="p">These Guidelines assume one of two different ways of processing whitespace will apply in a given case, depending on an element's content model. For an element that can contain only other elements with no intervening non-whitespace characters, whitespace is considered to have no semantic significance, and should therefore be discarded by a processor. For example, in a <a class="gi" title="groups a number of alternative encodings for the same point in a text." href="ref-choice.html">choice</a> element, such as <div id="index-egXML-d52e4607" class="pre egXML_valid"><span class="element"><choice></span><br /> <span class="element"><sic></span>1724<span class="element"></sic></span><br /> <span class="element"><corr></span>1728<span class="element"></corr></span><br /><span class="element"></choice></span></div> since non-whitespace text is not permitted between the <a class="gi" title="groups a number of alternative encodings for the same point in a text." href="ref-choice.html">choice</a> start-tag and the <a class="gi" title="(Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate." href="ref-sic.html">sic</a> tags or between the <a class="gi" title="(Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate." href="ref-sic.html">sic</a> and <a class="gi" title="(correction) contains the correct form of a passage apparently erroneous in the copy text." href="ref-corr.html">corr</a> tags, any whitespace found there has no significance and can be ignored completely by a processor.</div><p>Similarly, the <a class="gi" title="contains a postal address, for example of a publisher, an organization, or an individual." href="ref-address.html">address</a> element has a content model containing only elements: any punctuation or whitespace required between the lines of an address must therefore be supplied by the processor, as any whitespace present in the input document will be ignored.</p><p>Elements with content models of this type are comparatively unusual in the TEI: a list of them is provided in the TEI release file <span class="ident-file">stripspace.xsl.model</span>, formatted there for use as an <span class="gi"><xsl:strip-space></span> command for XSL stylesheets.</p><div class="p">Most TEI elements permit what is known as mixed-content: that is, they can contain both text and other elements. Here the assumption of these Guidelines is that whitespace will be normalized. This means that all space, carriage return, linefeed, and tab characters are converted into spaces, all consecutive spaces are then deleted and replaced by one space, and then space immediately after a start-tag or immediately before an end-tag is deleted. The result is that this encoding, <div id="index-egXML-d52e4642" class="pre egXML_valid"><span class="element"><persName></span><br /> <span class="element"><forename></span>Edward<span class="element"></forename></span><br /> <span class="element"><forename></span>George<span class="element"></forename></span><br /> <span class="element"><surname <span class="attribute">type</span>="<span class="attributevalue">linked</span>"></span>Bulwer-Lytton<span class="element"></surname></span>, <span class="element"><roleName></span>Baron Lytton of<br /> <span class="element"><placeName></span>Knebworth<span class="element"></placeName></span><span class="element"></roleName></span><span class="element"></persName></span></div> would be rendered as <span class="q">‘Edward George Bulwer-Lytton, Baron Lytton of Knebworth’</span>. The space before his name has been removed, a space is included between his forenames, the comma is preserved, and the newlines within his name have all been removed.</div><p>If the default treatment described above is not appropriate for a mixed content element, the processing required may be described in 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 of the TEI header, but generic XML processing tools may not take note of this.</p><p>Alternatively, the <span class="att">xml:space</span> attribute may be supplied with a value of <span class="val">preserve</span> in order to indicate that every space, tab, carriage return and linefeed character found within that element in the document being processed is significant. Typically, the result of that processing will be to retain the whitespace characters in the output. Thus if the above example began <span class="tag"><persName xml:space="preserve"></span>, the resulting text would most likely be rendered over five lines, indented, and with a blank line following.</p><p>The <code>xml:space="preserve"</code> attribute is rarely used in TEI documents because such layout features are generally captured with less risk and more precision by using native TEI elements such as <a class="gi" title="(line break) marks the start of a new (typographic) line in some edition or version of a text." href="ref-lb.html">lb</a> or <a class="gi" title="indicates the location of a significant space in the text." href="ref-space.html">space</a>, or by using the renditional attributes described in section <a class="link_ptr" href="ST.html#STGAre" title="Rendition Indicators"><span class="headingNumber">1.3.1.1.3 </span>Rendition Indicators</a>.</p></div><div class="teidiv4" id="STGAothers"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STGAxs"><span class="headingNumber">1.3.1.1.6 </span>XML Whitespace</a></li><li class="subtoc"></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h6><span class="bookmarklink"><a class="bookmarklink" href="#STGAothers" title="link to this section "><span class="invisible">TEI: Other Globally Available Attributes</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.1.1.7 </span><span class="head">Other Globally Available Attributes</span></h6><p>The following table lists for convenience other potentially available global attributes. The table specifies the name of the attribute class providing the attributes concerned, the module which must be included in a schema if the attributes are to be made available, and the section of these Guidelines where the class is discussed. </p><div class="table"><table><tr class="label"><td>class name</td><td>module name</td><td>see further</td></tr><tr><td>att.global.linking</td><td>linking</td><td><a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">16 </span>Linking, Segmentation, and Alignment</a></td></tr><tr><td>att.global.analytic</td><td>analysis</td><td><a class="link_ptr" href="AI.html" title="15"><span class="headingNumber">17 </span>Simple Analytic Mechanisms</a></td></tr><tr><td>att.global.facs</td><td>transcr</td><td><a class="link_ptr" href="PH.html#PHFAX" title="Digital Facsimiles"><span class="headingNumber">11.1 </span>Digital Facsimiles</a></td></tr><tr><td>att.global.change</td><td>transcr</td><td><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></td></tr></table></div></div></div></div><div class="div2" id="STECCM"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STECAT"><span class="headingNumber">1.3.1 </span>Attribute Classes</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="#STECCM" title="link to this section "><span class="invisible">TEI: Model Classes</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.2 </span><span class="head">Model Classes</span></h4><p>As noted above, the members of a given TEI model class share the property that they can all appear in the same location within a document. Wherever possible, the content model of a TEI element is expressed not directly in terms of specific elements, but indirectly in terms of particular model classes. This makes content models simpler and more consistent; it also makes them much easier to understand and to modify.</p><p>Like attribute classes, model classes may have subclasses or superclasses. Just as elements inherit from a class the ability to appear in certain locations of a document (wherever the class can appear), so all members of a subclass inherit the ability to appear wherever any superclass can appear. To some extent, the class system thus provides a way of reducing the whole TEI galaxy of elements into a tidy hierarchy. This is however not entirely the case.</p><p>In fact, the nature of a given class of elements can be considered along two dimensions: as noted, it defines a set of places where the class members are permitted within the document hierarchy; it also implies a semantic grouping of some kind. For example, the very large class of elements which can appear within a paragraph comprises a number of other classes, all of which have the same structural property, but which differ in their field of application. Some are related to highlighting, while others relate to names or places, and so on. In some cases, the ‘set of places where class members are permitted’ is very constrained: it may just be within one specific element, or one class of element, for example. In other cases, elements may be permitted to appear in very many places, or in more than one such set of places.</p><p>These factors are reflected in the way that model classes are named. If a model class has a name containing <span class="val">part</span>, such as <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a> or <a class="link_odd" title="groups elements which represent components of a bibliographic description." href="ref-model.biblPart.html">model.biblPart</a> then it is primarily defined in terms of its structural location. For example, those elements (or classes of element) which appear as content of a <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> constitute the <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a> class; those which appear as content of a <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> constitute the <a class="link_odd" title="groups elements which represent components of a bibliographic description." href="ref-model.biblPart.html">model.biblPart</a> class. If, however, a model class has a name containing <span class="val">like</span>, such as <a class="link_odd" title="groups elements containing a bibliographic description." href="ref-model.biblLike.html">model.biblLike</a> or <a class="link_odd" title="groups elements which name or refer to a person, place, or organization." href="ref-model.nameLike.html">model.nameLike</a>, the implication is that its members all have some additional semantic property in common, for example containing a bibliographic description, or containing some form of name, respectively. These semantically-motivated classes often provide a useful way of dividing up large structurally-motivated classes: for example, the very general structural class <a class="link_odd" title="groups phrase-level elements containing names, dates, numbers, measures, and similar data." href="ref-model.pPart.data.html">model.pPart.data</a> (‘data elements that form part of a paragraph’) has four semantically-motivated member classes (<a class="link_odd" title="groups elements used to represent a postal or email address." href="ref-model.addressLike.html">model.addressLike</a>, <a class="link_odd" title="groups elements containing temporal expressions." href="ref-model.dateLike.html">model.dateLike</a>, <a class="link_odd" title="groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning." href="ref-model.measureLike.html">model.measureLike</a>, and <a class="link_odd" title="groups elements which name or refer to a person, place, or organization." href="ref-model.nameLike.html">model.nameLike</a>), the last of these being itself a superclass with several members.</p><p>Although most classes are defined by the <span class="ident-module">tei</span> infrastructure module, a class cannot be populated unless some other specific module is included in a schema, since element declarations are contained by modules. Classes are not declared ‘top down’, but instead gain their members as a consequence of individual elements' declaration of their membership. The same class may therefore contain different members, depending on which modules are active. Consequently, the content model of a given element (being expressed in terms of model classes) may differ depending on which modules are active.</p><p>Some classes contain only a single member, even when all modules are loaded. One reason for declaring such a class is to make it easier for a customization to add new member elements in a specific place, particularly in areas where the TEI does not make fully elaborated proposals. For example, the TEI class <a class="link_odd" title="groups elements which contain a single reading, other than the lemma, within a textual variation." href="ref-model.rdgLike.html">model.rdgLike</a>, initially empty, is expanded by the <span class="ident-module">textcrit</span> module to include just the TEI <a class="gi" title="(reading) contains a single reading within a textual variation." href="ref-rdg.html">rdg</a> element. A project wishing to add an alternative way of structuring text-critical information could do so by defining their own elements and adding it to this class.</p><p>Another reason for declaring single-member classes is where the class members are not needed in all documents, but appear in the same place as elements which are very frequently required. For example, the specialized element <a class="gi" title="(character or glyph) represents a glyph, or a non-standard character." href="ref-g.html">g</a> used to represent a non-Unicode character or glyph is provided as the only member of the <a class="link_odd" title="groups elements used to represent individual non-Unicode characters or glyphs." href="ref-model.gLike.html">model.gLike</a> class when the <span class="ident-module">gaiji</span> module is added to a schema. References to this class are included in almost every content model, since if it is used at all the <a class="gi" title="(character or glyph) represents a glyph, or a non-standard character." href="ref-g.html">g</a> must be available wherever text is available; however these references have no effect unless the gaiji module is loaded.</p><p>At the other end of the scale, a few of the classes predefined by the tei module are subsequently populated with very many members. For example, the class <a class="link_odd" title="groups phrase-level elements for simple editorial correction and transcription." href="ref-model.pPart.edit.html">model.pPart.edit</a> groups all the classes of element for simple editorial correction and transcription which can appear within a <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a> or paragraph element. The <span class="ident-module">core</span> module alone adds more than fifty elements to this class; the <span class="ident-module">namesdates</span> module adds another twenty, as does the <span class="ident-module">tagdocs</span> module. Since the <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a> element is one of the basic building blocks of a TEI document it is not surprising that each module will need to add elements to it. The class system here provides a very convenient way of controlling the resulting complexity. Typically, elements are not added directly to these very general classes, but via some intermediate semantically-motivated class.</p><p>Just as there are a few classes which have a single member, so there are some classes which are used only once in the TEI architecture. These classes, which have no superclass and therefore do not fit into the class hierarchy defined here, are a convenient way of maintaining elements which are highly structured internally, but which appear from the outside to be uniform objects like others at the same level.<span id="Note39_return"><a class="notelink" title="In former editions of these Guidelines, such elements were known metaphorically as crystals." href="#Note39"><sup>2</sup></a></span> Members of such classes can only ever appear within one element, or one class of elements. For example, the class <a class="link_odd" title="groups elements such as names or postal codes which may appear as part of a postal address." href="ref-model.addrPart.html">model.addrPart</a> is used only to express the content model for the element <a class="gi" title="contains a postal address, for example of a publisher, an organization, or an individual." href="ref-address.html">address</a>; it references some other classes of elements, which can appear elsewhere, and also some elements which can only appear inside an address.</p><div class="teidiv3" id="STBTC"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></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="#STBTC" title="link to this section "><span class="invisible">TEI: Informal Element Classifications </span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.3.2.1 </span><span class="head">Informal Element Classifications </span></h5><p>Most TEI elements may also be informally classified as belonging to one of the following groupings: </p><dl><dt><span><span class="term">divisions</span></span></dt><dd>high level, possibly self-nesting, major divisions of texts. These elements populate such classes as <a class="link_odd" title="groups elements used to represent un-numbered generic structural divisions." href="ref-model.divLike.html">model.divLike</a> or <a class="link_odd" title="groups top-level structural divisions." href="ref-model.div1Like.html">model.div1Like</a>, and typically form the largest component units of a text.</dd><dt><span><span class="term">chunks</span></span></dt><dd>elements such as paragraphs and other paragraph-level elements, which can appear directly within texts or within divisions of them, but not (usually) within other chunks. These elements populate the class <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a>, either directly or by means of other classes such as <a class="link_odd" title="groups paragraph-like elements." href="ref-model.pLike.html">model.pLike</a> (paragraph-like elements), <a class="link_odd" title="groups elements structurally analogous to paragraphs within dictionaries." href="ref-model.entryLike.html">model.entryLike</a>, etc.</dd><dt><span><span class="term">phrase-level elements</span></span></dt><dd>elements such as highlighted phrases, book titles, or editorial corrections which can occur only within chunks, but not between them (and thus cannot appear directly within a division). These elements populate the class <a class="link_odd" title="groups elements which can occur at the level of individual words or phrases." href="ref-model.phrase.html">model.phrase</a>.<span id="Note40_return"><a class="notelink" title="Note that in this context, phrase means any string of characters, and can apply to individual words, parts of words, and groups of words indifferently…" href="#Note40"><sup>3</sup></a></span></dd></dl><p>The TEI also identifies two further groupings derived from these three: </p><dl><dt><span><span class="term">inter-level elements</span></span></dt><dd>elements such as lists, notes, quotations, etc. which can appear either between chunks (as children of a <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a>) or within them; these elements populate the class <a class="link_odd" title="groups elements which can appear either within or between paragraph-like elements." href="ref-model.inter.html">model.inter</a>. Note that this class is not a superset of the <a class="link_odd" title="groups elements which can occur at the level of individual words or phrases." href="ref-model.phrase.html">model.phrase</a> and <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a> classes but rather a distinct grouping of elements which are both chunk-like and phrase-like. However, the classes <a class="link_odd" title="groups elements which can occur at the level of individual words or phrases." href="ref-model.phrase.html">model.phrase</a>, <a class="link_odd" title="groups paragraph-like elements." href="ref-model.pLike.html">model.pLike</a>, and <a class="link_odd" title="groups elements which can appear either within or between paragraph-like elements." href="ref-model.inter.html">model.inter</a> are all disjoint.</dd><dt><span><span class="term">components</span></span></dt><dd>elements which can appear directly within texts or text divisions; this is a combination of the inter- and chunk- level elements defined above. These elements populate the class <a class="link_odd" title="groups common chunk- and inter-level elements." href="ref-model.common.html">model.common</a>, which is defined as a superset of the classes <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a>, <a class="link_odd" title="groups elements which can appear either within or between paragraph-like elements." href="ref-model.inter.html">model.inter</a>, and (when the dictionary module is included in a schema) <a class="link_odd" title="groups elements structurally analogous to paragraphs within dictionaries." href="ref-model.entryLike.html">model.entryLike</a>.</dd></dl><p> Broadly speaking, the front, body, and back of a text each comprises a series of components, optionally grouped into divisions.</p><p>As noted above, some elements do not belong to any model class, and some model classes are not readily associated with any of the above informal groupings. However, over two-thirds of the 568 elements defined in the present edition of these Guidelines are classified in this way, and future editions of these recommendations will extend and develop this classification scheme.</p><p>A complete alphabetical list of all model classes is provided in <a class="link_ptr" href="REF-CLASSES-MODEL.html" title="Model Classes"><span class="headingNumber">Appendix A </span>Model Classes</a>.</p></div></div></div><div class="div2" id="STmacros"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STEC"><span class="headingNumber">1.3 </span>The TEI Class System</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STOV"><span class="headingNumber">1.5 </span>The TEI Infrastructure 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="#STmacros" title="link to this section "><span class="invisible">TEI: Macros</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.4 </span><span class="head">Macros</span></h3><p>The infrastructure module defined by this chapter also declares a number of <span class="term">macros</span>, or shortcut names for frequently occurring parts of other declarations. Macros are used in two ways in the TEI scheme: to stand for frequently-encountered content models, or parts of content models (<a class="link_ptr" href="ST.html#STECST" title="Standard Content Models"><span class="headingNumber">1.4.1 </span>Standard Content Models</a>); and to stand for attribute datatypes (<a class="link_ptr" href="ST.html#DTYPES" title="Datatype Specifications"><span class="headingNumber">1.4.2 </span>Datatype Specifications</a>).</p><div class="div3" id="STECST"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#DTYPES"><span class="headingNumber">1.4.2 </span>Datatype Specifications</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h4><span class="bookmarklink"><a class="bookmarklink" href="#STECST" title="link to this section "><span class="invisible">TEI: Standard Content Models</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.4.1 </span><span class="head">Standard Content Models</span></h4><p>As far as possible, the TEI schemas use the following set of frequently-encountered content models to help achieve consistency among different elements. </p><ul class="specList"><li><span class="specList-macroSpec"><a href="ref-macro.paraContent.html">macro.paraContent</a></span> (paragraph content) defines the content of paragraphs and similar elements.</li><li><span class="specList-macroSpec"><a href="ref-macro.limitedContent.html">macro.limitedContent</a></span> (paragraph content) defines the content of prose elements that are not used for transcription of extant materials.</li><li><span class="specList-macroSpec"><a href="ref-macro.phraseSeq.html">macro.phraseSeq</a></span> (phrase sequence) defines a sequence of character data and phrase-level elements.</li><li><span class="specList-macroSpec"><a href="ref-macro.phraseSeq.limited.html">macro.phraseSeq.limited</a></span> (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents.</li><li><span class="specList-macroSpec"><a href="ref-macro.schemaPattern.html">macro.schemaPattern</a></span> provides a pattern to match elements from the chosen schema language</li><li><span class="specList-macroSpec"><a href="ref-macro.specialPara.html">macro.specialPara</a></span> ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements.</li><li><span class="specList-macroSpec"><a href="ref-macro.xtext.html">macro.xtext</a></span> (extended text) defines a sequence of character data and gaiji elements.</li></ul><p>The present version of the TEI Guidelines includes some 568 different elements. <a class="link_ptr" href="ST.html#tab-content-models" title="Content modelNumber of elements using thisDescriptionmacro.phraseSeq82defines a sequence of character data and phraselevel elem...">Table 4</a> shows, in descending order of frequency, the seven most commonly used content models.</p><div class="table" id="tab-content-models"><table class="display"><tr class="label"><td>Content model</td><td>Number of elements using this</td><td>Description</td></tr><tr><td>macro.phraseSeq</td><td>82</td><td>defines a sequence of character data and phrase-level elements.</td></tr><tr><td>macro.paraContent</td><td>53</td><td>defines the content of paragraphs and similar elements.</td></tr><tr><td>macro.specialPara</td><td>33</td><td>defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements.</td></tr><tr><td>macro.phraseSeq.limited</td><td>22</td><td>defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents.</td></tr><tr><td>macro.xtext</td><td>15</td><td>defines a sequence of character data and gaiji elements.</td></tr><tr><td>macro.limitedContent</td><td>8</td><td>defines the content of prose elements that are not used for transcription of extant materials.</td></tr><tr><td>macro.anyXML</td><td>0</td><td>defines a content model within which any XML elements are permitted</td></tr></table></div></div><div class="div3" id="DTYPES"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STECST"><span class="headingNumber">1.4.1 </span>Standard Content Models</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="#DTYPES" title="link to this section "><span class="invisible">TEI: Datatype Specifications</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.4.2 </span><span class="head">Datatype Specifications</span></h4><p>The values which attributes may take in a TEI schema are defined, for the most part, by reference to a TEI <span class="term">datatype specification</span>. Each such specification is defined in terms of other primitive datatypes, derived mostly from <a class="link_ref" href="BIB.html#XSD2" title="Paul V. Biron Ashok Malhotra XML Schema Part 2 Datatypes Second EditionW3C28 October 2004">W3C Schema Datatypes</a>, literal values, or other datatypes. This indirection makes it possible for a TEI application to set constraints either globally or in individual cases, by redefining the datatype definition or the reference to it respectively. In some cases, the TEI datatype includes additional usage constraints which cannot be enforced by existing schema languages, although a TEI-compliant processor should attempt to validate them (see further discussion in chapter <a class="link_ptr" href="USE.html#CF" title="Conformance"><span class="headingNumber">23.4 </span>Conformance</a>).</p><p>The following element is used to define a TEI datatype: </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-dataSpec.html">dataSpec</a></span> (datatype specification) documents a datatype.</li></ul><p>TEI-defined datatypes may be grouped into those which define normalized values for numeric quantities, probabilities, or temporal expressions, those which define various kinds of shorthand codes or keys, and those which define pointers or links.</p><p>The following datatypes are used for attributes which are intended to hold normalized values of various kinds. First, expressions of quantity or probability: </p><ul class="specList"><li><span class="specList-dataSpec"><a href="ref-teidata.certainty.html">teidata.certainty</a></span> defines the range of attribute values expressing a degree of certainty.</li><li><span class="specList-dataSpec"><a href="ref-teidata.probability.html">teidata.probability</a></span> defines the range of attribute values expressing a probability.</li><li><span class="specList-dataSpec"><a href="ref-teidata.numeric.html">teidata.numeric</a></span> defines the range of attribute values used for numeric values.</li><li><span class="specList-dataSpec"><a href="ref-teidata.interval.html">teidata.interval</a></span> defines attribute values used to express an interval value.</li><li><span class="specList-dataSpec"><a href="ref-teidata.percentage.html">teidata.percentage</a></span> defines attribute values used to express a percentage value.</li><li><span class="specList-dataSpec"><a href="ref-teidata.count.html">teidata.count</a></span> defines the range of attribute values used for a non-negative integer value used as a count.</li></ul><p>Examples of attributes using the <span class="ident-datatype">teidata.probability</span> datatype include <span class="att">degree</span> on <a class="gi" title="contains an area of damage to the text witness." href="ref-damage.html">damage</a> or <a class="gi" title="indicates the degree of certainty associated with some aspect of the text markup." href="ref-certainty.html">certainty</a>; examples of <span class="ident-datatype">teidata.numeric</span> include <span class="att">quantity</span> on members of the <a class="link_odd" title="provides attributes to represent a regularized or normalized measurement." href="ref-att.measurement.html">att.measurement</a> class or <span class="att">value</span> on <a class="gi" title="(numeric value) represents the value part of a feature-value specification which contains a numeric value or range." href="ref-numeric.html">numeric</a>; examples of <span class="ident-datatype">teidata.count</span> include <span class="att">cols</span> on <a class="gi" title="contains one cell of a table." href="ref-cell.html">cell</a> and <a class="gi" title="contains text displayed in tabular form, in rows and columns." href="ref-table.html">table</a>.</p><p>Next, the datatypes used for attributes which are intended to hold normalized dates or times, durations, truth values, and language identifiers: </p><ul class="specList"><li><span class="specList-dataSpec"><a href="ref-teidata.duration.w3c.html">teidata.duration.w3c</a></span> defines the range of attribute values available for representation of a duration in time using W3C datatypes.</li><li><span class="specList-dataSpec"><a href="ref-teidata.duration.iso.html">teidata.duration.iso</a></span> defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats</li><li><span class="specList-dataSpec"><a href="ref-teidata.temporal.w3c.html">teidata.temporal.w3c</a></span> defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C <span class="titlem">XML Schema Part 2: Datatypes Second Edition</span> specification.</li><li><span class="specList-dataSpec"><a href="ref-teidata.temporal.iso.html">teidata.temporal.iso</a></span> defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard <span class="titlem">Data elements and interchange formats – Information interchange – Representation of dates and times</span>.</li><li><span class="specList-dataSpec"><a href="ref-teidata.truthValue.html">teidata.truthValue</a></span> defines the range of attribute values used to express a truth value.</li><li><span class="specList-dataSpec"><a href="ref-teidata.xTruthValue.html">teidata.xTruthValue</a></span> (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.</li><li><span class="specList-dataSpec"><a href="ref-teidata.language.html">teidata.language</a></span> defines the range of attribute values used to identify a particular combination of human language and writing system.</li></ul><p>Note that in each of these cases the values used are those recommended by existing international standards: ISO 8601 as profiled by <span class="titlem">XML Schema Part 2: Datatypes Second Edition</span> in the case of durations, times, and date; W3C Schema datatypes in the case of truth values; and BCP 47 in the case of language.</p><p>The following datatypes have more specialized uses: </p><ul class="specList"><li><span class="specList-dataSpec"><a href="ref-teidata.namespace.html">teidata.namespace</a></span> defines the range of attribute values used to indicate XML namespaces as defined by the W3C <a class="link_ref" href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">Namespaces in XML</a> Technical Recommendation.</li><li><span class="specList-dataSpec"><a href="ref-teidata.namespaceOrName.html">teidata.namespaceOrName</a></span> defines attribute values which contain either a namespace URI or an XML name.</li><li><span class="specList-dataSpec"><a href="ref-teidata.outputMeasurement.html">teidata.outputMeasurement</a></span> defines a range of values for use in specifying the size of an object that is intended for display.</li><li><span class="specList-dataSpec"><a href="ref-teidata.pattern.html">teidata.pattern</a></span> defines attribute values which are expressed as a regular expression.</li><li><span class="specList-dataSpec"><a href="ref-teidata.point.html">teidata.point</a></span> defines the data type used to express a point in cartesian space.</li><li><span class="specList-dataSpec"><a href="ref-teidata.pointer.html">teidata.pointer</a></span> defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.</li><li><span class="specList-dataSpec"><a href="ref-teidata.version.html">teidata.version</a></span> defines the range of attribute values which may be used to specify a TEI or Unicode version number.</li><li><span class="specList-dataSpec"><a href="ref-teidata.versionNumber.html">teidata.versionNumber</a></span> defines the range of attribute values used for version numbers.</li><li><span class="specList-dataSpec"><a href="ref-teidata.replacement.html">teidata.replacement</a></span> defines attribute values which contain a replacement template.</li><li><span class="specList-dataSpec"><a href="ref-teidata.xpath.html">teidata.xpath</a></span> defines attribute values which contain an XPath expression.</li></ul><p>By far the largest number of TEI attributes take values which are coded values or names of some kind. These values may be constrained or defined in a number of different ways, each of which is given a different name, as follows: </p><ul class="specList"><li><span class="specList-dataSpec"><a href="ref-teidata.word.html">teidata.word</a></span> defines the range of attribute values expressed as a single word or token.</li><li><span class="specList-dataSpec"><a href="ref-teidata.text.html">teidata.text</a></span> defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.</li><li><span class="specList-dataSpec"><a href="ref-teidata.name.html">teidata.name</a></span> defines the range of attribute values expressed as an XML Name.</li><li><span class="specList-dataSpec"><a href="ref-teidata.enumerated.html">teidata.enumerated</a></span> defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.</li><li><span class="specList-dataSpec"><a href="ref-teidata.sex.html">teidata.sex</a></span> defines the range of attribute values used to identify human or animal sex.</li><li><span class="specList-dataSpec"><a href="ref-teidata.xmlName.html">teidata.xmlName</a></span> defines attribute values which contain an XML name.</li><li><span class="specList-dataSpec"><a href="ref-teidata.prefix.html">teidata.prefix</a></span> defines a range of values that may function as a URI scheme name.</li></ul><p>Attributes of type <span class="ident-datatype">teidata.word</span>, such as <span class="att">age</span> on <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>, are used to supply an identifier expressed as any kind of single token or word. The TEI places a few constraints on the characters which may be used for this purpose: only Unicode characters classified as letters, digits, punctuation characters, or symbols can appear in an attribute value of this kind. Note in particular that such values cannot include whitespace characters. Legal values include <span class="val">cholmondeley</span>, <span class="val">été</span>, <span class="val">1234</span>, <span class="val">e_content</span>, or <span class="val">xml:id</span>, but not <span class="val">grand wazoo</span>. Attributes of this kind are sometimes used to associate (by co-reference) elements of different types.</p><p>Where identifiers are defined externally, for example as part of a database or file system, the inability to include whitespace or other special characters in a value may be problematic. In other cases, it may also be simply more convenient to supply a short sequence of natural language words including spaces as a single value. For these reasons, we also provide a datatype <span class="ident">teidata.text</span> which does permit whitespace and indeed any other Unicode character. Legal values include <span class="val">cholmondeley</span>, <span class="val">été</span>, <span class="val">1234</span>, <span class="val">e-content</span>, <span class="val">xml:id</span>, and <span class="val">grand wazoo</span>. This datatype should be used with care since XML will not normalize whitespace characters within it: for example the values <code>n="a b"</code> (two spaces) and <code>n="a b"</code> (three spaces) would be considered distinct. This case should be distinguished from that of an attribute permitting multiple values, each of which may be separated by whitespace which <em>will</em> be normalized (see further <a class="link_ptr" href="TD.html#TD-datatypes" title="Datatypes"><span class="headingNumber">22.5.4.1 </span>Datatypes</a>).</p><p>Attributes of type <span class="ident-datatype">teidata.name</span> are similar to those of type <span class="ident-datatype">teidata.word</span>, but with the additional constraint that they must be legal XML identifiers, as defined by the XML 1.0 specification, or successors. Hence, they may not begin with digits or punctuation characters. Legal identifiers include <span class="val">cholmondeley</span>, <span class="val">été</span>, <span class="val">e_content</span>, or <span class="val">xml:id</span>, but not <span class="val">grand wazoo</span> or <span class="val">1234</span>. Attributes of this kind are typically used to represent XML element or attribute names.</p><p>Attributes of type <span class="ident-datatype">teidata.xmlName</span> are similar to those of type <span class="ident-datatype">teidata.name</span>, but with the additional constraint that they must not contain a colon character (<span class="mentioned">:</span>, U+003A). Thus attributes of this kind are used to represent XML element or attribute names that do not have a namespace prefix.</p><p>Attributes of type <span class="ident-datatype">teidata.prefix</span>, such as <span class="att">ident</span> of <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>, are restricted to strings that form legal URI prefixes.<span id="Note41_return"><a class="notelink" title="Technically the specification permits the 26 uppercase letters A-Z; however, since the canonical form is lowercase and documents that specify schemes …" href="#Note41"><sup>4</sup></a></span> Examples of valid values are <span class="val">http</span>, <span class="val">https</span>, <span class="val">tn3270</span>, <span class="val">xmlrpc.beep</span>, and <span class="val">view-source</span>.</p><p>Attributes of type <span class="ident-datatype">teidata.enumerated</span>, such as <span class="att">new</span> on <a class="gi" title="marks the point at which some paralinguistic feature of a series of utterances by any one speaker changes." href="ref-shift.html">shift</a> or <span class="att">evidence</span> supplied by <a class="link_odd" title="provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind." href="ref-att.editLike.html">att.editLike</a>, have the same definition as <span class="ident-datatype">teidata.word</span> above, with the added constraint that the word supplied is taken from a specific list of possibilities. In each case, the element or class specification which includes the definition for the attribute will also contain a list of possible values, together with a prose description of their intended significance. This list may be open (in which case the list is advisory), or closed (in which case it determines the range of legal values). In this latter case, the datatype will not be <span class="ident-datatype">teidata.enumerated</span>, but an explicit list of the possible values.</p><p>An attribute may, of course, take more than one value of a given type, for example a list of pointer values, or a list of words. In the TEI scheme, this information is regarded as a property of the <a class="gi" title="specifies the declared value for an attribute, by referring to any datatype defined by the chosen schema language." href="ref-datatype.html">datatype</a> element used to document the attribute in question rather than as a distinct ‘datatype’, and is provided by the <span class="att">minOccurs</span> or <span class="att">maxOccurs</span> attribute. See further <a class="link_ptr" href="TD.html#TD-datatypes" title="Datatypes"><span class="headingNumber">22.5.4.1 </span>Datatypes</a>.</p><p>In a small number of cases, an attribute may take a value of either one datatype or another. These cases are considered as distinct datatypes: </p><ul class="specList"><li><span class="specList-dataSpec"><a href="ref-teidata.probCert.html">teidata.probCert</a></span> defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.</li><li><span class="specList-dataSpec"><a href="ref-teidata.unboundedInt.html">teidata.unboundedInt</a></span> defines an attribute value which can be either any non-negative integer or the string "unbounded".</li><li><span class="specList-dataSpec"><a href="ref-teidata.nullOrName.html">teidata.nullOrName</a></span> defines attribute values which contain either the null string or an XML name.</li></ul></div></div><div class="div2" id="STOV"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STmacros"><span class="headingNumber">1.4 </span>Macros</a></li><li class="subtoc"><span class="nextLink"> » </span><a class="navigation" href="ST.html#STDD"><span class="headingNumber">1.6 </span>Deprecated Datatype Macros</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#STOV" title="link to this section "><span class="invisible">TEI: The TEI Infrastructure Module</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.5 </span><span class="head">The TEI Infrastructure Module</span></h3><p>The <span class="ident-module">tei</span> module defined by this chapter is a required component of any TEI schema. It provides declarations for all datatypes, and initial declarations for the attribute classes, model classes, and macros used by other modules in the TEI scheme. Its components are listed below in alphabetical order:</p><dl class="moduleSpec"><dt class="moduleSpecHead"><span lang="en">Module</span> tei: Declarations for classes, datatypes, and macros available to all TEI modules</dt><dd><ul><li><span lang="en">Classes defined</span>: <a class="link_odd" title="provides attributes for elements representing speech or action that can be ascribed to a specific individual." href="ref-att.ascribed.html">att.ascribed</a> <a class="link_odd" title="provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace." href="ref-att.breaking.html">att.breaking</a> <a class="link_odd" title="provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer." href="ref-att.cReferencing.html">att.cReferencing</a> <a class="link_odd" title="provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced." href="ref-att.canonical.html">att.canonical</a> <a class="link_odd" title="provides attributes for specifying the specific part of a bibliographic item being cited." href="ref-att.citing.html">att.citing</a> <a class="link_odd" title="provides attributes describing the nature of any physical damage affecting a reading." href="ref-att.damaged.html">att.damaged</a> <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> <a class="link_odd" title="provides attributes for normalization of elements that contain datable events conforming to the W3C _XML_Schema_Part_2:_Datatypes_Second_Edition_." href="ref-att.datable.w3c.html">att.datable.w3c</a> <a class="link_odd" title="provides the @dcr:datacat and @dcr:ValueDatacat attributes which are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/." href="ref-att.datcat.html">att.datcat</a> <a class="link_odd" title="provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose @decls attribute." href="ref-att.declarable.html">att.declarable</a> <a class="link_odd" title="provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element." href="ref-att.declaring.html">att.declaring</a> <a class="link_odd" title="provides attributes for describing the size of physical objects." href="ref-att.dimensions.html">att.dimensions</a> <a class="link_odd" title="provides attributes common to all elements which behave in the same way as divisions." href="ref-att.divLike.html">att.divLike</a> <a class="link_odd" title="provides attributes for use on metadata elements describing the status of a document." href="ref-att.docStatus.html">att.docStatus</a> <a class="link_odd" title="provides attributes for recording normalized temporal durations." href="ref-att.duration.iso.html">att.duration.iso</a> <a class="link_odd" title="provides attributes for recording normalized temporal durations." href="ref-att.duration.w3c.html">att.duration.w3c</a> <a class="link_odd" title="provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind." href="ref-att.editLike.html">att.editLike</a> <a class="link_odd" title="provides attributes identifying the source edition from which some encoded feature derives." href="ref-att.edition.html">att.edition</a> <a class="link_odd" title="provides an attribute for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy." href="ref-att.fragmentable.html">att.fragmentable</a> <a class="link_odd" title="provides attributes common to all elements in the TEI encoding scheme." href="ref-att.global.html">att.global</a> <a class="link_odd" title="provides rendering attributes common to all elements in the TEI encoding scheme." href="ref-att.global.rendition.html">att.global.rendition</a> <a class="link_odd" title="provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it." href="ref-att.global.responsibility.html">att.global.responsibility</a> <a class="link_odd" title="provides an attribute used by elements to point to an external source." href="ref-att.global.source.html">att.global.source</a> <a class="link_odd" title="provides attributes describing aspects of the hand in which a manuscript is written." href="ref-att.handFeatures.html">att.handFeatures</a> <a class="link_odd" title="provides attributes for specifying the type of a computer resource using a standard taxonomy." href="ref-att.internetMedia.html">att.internetMedia</a> <a class="link_odd" title="provides attributes for elements which represent a formal analysis or interpretation." href="ref-att.interpLike.html">att.interpLike</a> <a class="link_odd" title="provides attributes to represent a regularized or normalized measurement." href="ref-att.measurement.html">att.measurement</a> <a class="link_odd" title="provides attributes for specifying display and related properties of external media." href="ref-att.media.html">att.media</a> <a class="link_odd" title="provides attributes common to elements which refer to named persons, places, organizations etc." href="ref-att.naming.html">att.naming</a> <a class="link_odd" title="provides an attribute to indicate any specialised notation used for element content." href="ref-att.notated.html">att.notated</a> <a class="link_odd" title="provides attributes for describing the extent of lexical references for a dictionary term." href="ref-att.partials.html">att.partials</a> <a class="link_odd" title="(attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name." href="ref-att.personal.html">att.personal</a> <a class="link_odd" title="provides attributes for describing where on the source page or object a textual element appears." href="ref-att.placement.html">att.placement</a> <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> <a class="link_odd" title="provides a set of attributes common to all elements which enclose groups of pointer elements." href="ref-att.pointing.group.html">att.pointing.group</a> <a class="link_odd" title="provides attributes for describing numerical ranges." href="ref-att.ranging.html">att.ranging</a> <a class="link_odd" title="provides attributes by which a resource (such as an externally held media file) may be located." href="ref-att.resourced.html">att.resourced</a> <a class="link_odd" title="provides attributes for selecting particular elements within a document." href="ref-att.scoping.html">att.scoping</a> <a class="link_odd" title="provides attributes for elements used for arbitrary segmentation." href="ref-att.segLike.html">att.segLike</a> <a class="link_odd" title="provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content." href="ref-att.sortable.html">att.sortable</a> <a class="link_odd" title="provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it." href="ref-att.spanning.html">att.spanning</a> <a class="link_odd" title="provides attributes to specify the name of a formal definition language used to provide formatting or rendition information." href="ref-att.styleDef.html">att.styleDef</a> <a class="link_odd" title="provides attributes used to decorate rows or cells of a table." href="ref-att.tableDecoration.html">att.tableDecoration</a> <a class="link_odd" title="provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map." href="ref-att.timed.html">att.timed</a> <a class="link_odd" title="provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources." href="ref-att.transcriptional.html">att.transcriptional</a> <a class="link_odd" title="provides attributes used to indicate the status of a translatable portion of an ODD document." href="ref-att.translatable.html">att.translatable</a> <a class="link_odd" title="provides attributes which can be used to classify or subclassify elements in any way." href="ref-att.typed.html">att.typed</a> <a class="link_odd" title="provides an attribute to indicate the hand in which the textual content of an element was written in the source being transcribed." href="ref-att.written.html">att.written</a> <a class="link_odd" title="groups elements such as names or postal codes which may appear as part of a postal address." href="ref-model.addrPart.html">model.addrPart</a> <a class="link_odd" title="groups elements used to represent a postal or email address." href="ref-model.addressLike.html">model.addressLike</a> <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> <a class="link_odd" title="groups elements such as licences and paragraphs of text which may appear as part of an availability statement" href="ref-model.availabilityPart.html">model.availabilityPart</a> <a class="link_odd" title="groups elements containing a bibliographic description." href="ref-model.biblLike.html">model.biblLike</a> <a class="link_odd" title="groups elements which represent components of a bibliographic description." href="ref-model.biblPart.html">model.biblPart</a> <a class="link_odd" title="groups component elements of an entry in a cast list, such as dramatic role or actor's name." href="ref-model.castItemPart.html">model.castItemPart</a> <a class="link_odd" title="groups component elements of the TEI header Category Description." href="ref-model.catDescPart.html">model.catDescPart</a> <a class="link_odd" title="groups elements which are used to indicate uncertainty or precision of other elements." href="ref-model.certLike.html">model.certLike</a> <a class="link_odd" title="groups elements (other than <choice> itself) which can be used within a <choice> alternation." href="ref-model.choicePart.html">model.choicePart</a> <a class="link_odd" title="groups common chunk- and inter-level elements." href="ref-model.common.html">model.common</a> <a class="link_odd" title="groups elements which define the parts (usually names, dates and places) of one action related to the correspondence." href="ref-model.correspActionPart.html">model.correspActionPart</a> <a class="link_odd" title="groups elements which may appear as part of the correspContext element" href="ref-model.correspContextPart.html">model.correspContextPart</a> <a class="link_odd" title="groups together metadata elements for describing correspondence" href="ref-model.correspDescPart.html">model.correspDescPart</a> <a class="link_odd" title="groups elements containing temporal expressions." href="ref-model.dateLike.html">model.dateLike</a> <a class="link_odd" title="groups elements which contain a description of their function." href="ref-model.descLike.html">model.descLike</a> <a class="link_odd" title="groups elements which describe a measurement forming part of the physical dimensions of some object." href="ref-model.dimLike.html">model.dimLike</a> <a class="link_odd" title="groups top-level structural divisions." href="ref-model.div1Like.html">model.div1Like</a> <a class="link_odd" title="groups second-level structural divisions." href="ref-model.div2Like.html">model.div2Like</a> <a class="link_odd" title="groups third-level structural divisions." href="ref-model.div3Like.html">model.div3Like</a> <a class="link_odd" title="groups fourth-level structural divisions." href="ref-model.div4Like.html">model.div4Like</a> <a class="link_odd" title="groups fifth-level structural divisions." href="ref-model.div5Like.html">model.div5Like</a> <a class="link_odd" title="groups sixth-level structural divisions." href="ref-model.div6Like.html">model.div6Like</a> <a class="link_odd" title="groups seventh-level structural divisions." href="ref-model.div7Like.html">model.div7Like</a> <a class="link_odd" title="groups elements appearing at the end of a text division." href="ref-model.divBottom.html">model.divBottom</a> <a class="link_odd" title="groups elements which can occur only at the end of a text division." href="ref-model.divBottomPart.html">model.divBottomPart</a> <a class="link_odd" title="groups elements used to represent a structural division which is generated rather than explicitly present in the source." href="ref-model.divGenLike.html">model.divGenLike</a> <a class="link_odd" title="groups elements used to represent un-numbered generic structural divisions." href="ref-model.divLike.html">model.divLike</a> <a class="link_odd" title="groups paragraph-level elements appearing directly within divisions." href="ref-model.divPart.html">model.divPart</a> <a class="link_odd" title="groups elements appearing at the beginning of a text division." href="ref-model.divTop.html">model.divTop</a> <a class="link_odd" title="groups elements which can occur only at the beginning of a text division." href="ref-model.divTopPart.html">model.divTopPart</a> <a class="link_odd" title="groups elements which can appear at either top or bottom of a textual division." href="ref-model.divWrapper.html">model.divWrapper</a> <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> <a class="link_odd" title="groups elements containing examples or illustrations." href="ref-model.egLike.html">model.egLike</a> <a class="link_odd" title="groups phrase-level elements which are typographically distinct and to which a specific function can be attributed." href="ref-model.emphLike.html">model.emphLike</a> <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> <a class="link_odd" title="groups non-morphological elements appearing within a dictionary entry." href="ref-model.entryPart.html">model.entryPart</a> <a class="link_odd" title="groups high level elements within a structured dictionary entry" href="ref-model.entryPart.top.html">model.entryPart.top</a> <a class="link_odd" title="groups elements which describe events." href="ref-model.eventLike.html">model.eventLike</a> <a class="link_odd" title="groups elements which represent feature values in feature structures." href="ref-model.featureVal.html">model.featureVal</a> <a class="link_odd" title="groups elements which express complex feature values in feature structures." href="ref-model.featureVal.complex.html">model.featureVal.complex</a> <a class="link_odd" title="group elements used to represent atomic feature values in feature structures." href="ref-model.featureVal.single.html">model.featureVal.single</a> <a class="link_odd" title="groups elements which appear at the level of divisions within front or back matter." href="ref-model.frontPart.html">model.frontPart</a> <a class="link_odd" title="groups elements which appear at the level of divisions within front or back matter of performance texts only." href="ref-model.frontPart.drama.html">model.frontPart.drama</a> <a class="link_odd" title="groups elements used to represent individual non-Unicode characters or glyphs." href="ref-model.gLike.html">model.gLike</a> <a class="link_odd" title="groups elements which may appear at any point within a TEI text." href="ref-model.global.html">model.global</a> <a class="link_odd" title="groups globally available elements which perform a specifically editorial function." href="ref-model.global.edit.html">model.global.edit</a> <a class="link_odd" title="groups globally available elements which describe the status of other elements." href="ref-model.global.meta.html">model.global.meta</a> <a class="link_odd" title="groups elements which provide an alternative name, explanation, or description for any markup construct." href="ref-model.glossLike.html">model.glossLike</a> <a class="link_odd" title="groups elements containing images, formulae, and similar objects." href="ref-model.graphicLike.html">model.graphicLike</a> <a class="link_odd" title="groups elements used to provide a title or heading at the start of a text division." href="ref-model.headLike.html">model.headLike</a> <a class="link_odd" title="groups phrase-level elements which are typographically distinct but to which no specific function can be attributed." href="ref-model.hiLike.html">model.hiLike</a> <a class="link_odd" title="groups phrase-level elements which are typographically distinct." href="ref-model.highlighted.html">model.highlighted</a> <a class="link_odd" title="groups the bibliographic elements which occur inside imprints." href="ref-model.imprintPart.html">model.imprintPart</a> <a class="link_odd" title="groups elements which can appear either within or between paragraph-like elements." href="ref-model.inter.html">model.inter</a> <a class="link_odd" title="groups elements representing metrical components such as verse lines." href="ref-model.lLike.html">model.lLike</a> <a class="link_odd" title="groups phrase-level elements which may appear within verse only." href="ref-model.lPart.html">model.lPart</a> <a class="link_odd" title="groups elements used to gloss or explain other parts of a document." href="ref-model.labelLike.html">model.labelLike</a> <a class="link_odd" title="groups phrase-level elements excluding those elements primarily intended for transcription of existing sources." href="ref-model.limitedPhrase.html">model.limitedPhrase</a> <a class="link_odd" title="groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element." href="ref-model.linePart.html">model.linePart</a> <a class="link_odd" title="groups list-like elements." href="ref-model.listLike.html">model.listLike</a> <a class="link_odd" title="groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning." href="ref-model.measureLike.html">model.measureLike</a> <a class="link_odd" title="groups milestone-style elements used to represent reference systems." href="ref-model.milestoneLike.html">model.milestoneLike</a> <a class="link_odd" title="groups elements which can appear within a manuscript item description." href="ref-model.msItemPart.html">model.msItemPart</a> <a class="link_odd" title="groups elements which represent passages such as titles quoted from a manuscript as a part of its description." href="ref-model.msQuoteLike.html">model.msQuoteLike</a> <a class="link_odd" title="groups elements which name or refer to a person, place, or organization." href="ref-model.nameLike.html">model.nameLike</a> <a class="link_odd" title="groups elements which contain names of individuals or corporate bodies." href="ref-model.nameLike.agent.html">model.nameLike.agent</a> <a class="link_odd" title="groups globally-available note-like elements." href="ref-model.noteLike.html">model.noteLike</a> <a class="link_odd" title="groups elements which generate declarations in some markup language in ODD documents." href="ref-model.oddDecl.html">model.oddDecl</a> <a class="link_odd" title="groups elements which reference declarations in some markup language in ODD documents." href="ref-model.oddRef.html">model.oddRef</a> <a class="link_odd" title="groups elements which can appear only as part of a place name." href="ref-model.offsetLike.html">model.offsetLike</a> <a class="link_odd" title="groups elements which form part of the description of an organization." href="ref-model.orgPart.html">model.orgPart</a> <a class="link_odd" title="groups elements describing changeable characteristics of an organization which have a definite duration." href="ref-model.orgStateLike.html">model.orgStateLike</a> <a class="link_odd" title="groups paragraph-like elements." href="ref-model.pLike.html">model.pLike</a> <a class="link_odd" title="groups paragraph-like elements which can occur as direct constituents of front matter." href="ref-model.pLike.front.html">model.pLike.front</a> <a class="link_odd" title="groups phrase-level elements containing names, dates, numbers, measures, and similar data." href="ref-model.pPart.data.html">model.pPart.data</a> <a class="link_odd" title="groups phrase-level elements for simple editorial correction and transcription." href="ref-model.pPart.edit.html">model.pPart.edit</a> <a class="link_odd" title="groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring." href="ref-model.pPart.editorial.html">model.pPart.editorial</a> <a class="link_odd" title="groups phrase-level elements used in manuscript description." href="ref-model.pPart.msdesc.html">model.pPart.msdesc</a> <a class="link_odd" title="groups phrase-level elements used for editorial transcription of pre-existing source materials." href="ref-model.pPart.transcriptional.html">model.pPart.transcriptional</a> <a class="link_odd" title="groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name." href="ref-model.persStateLike.html">model.persStateLike</a> <a class="link_odd" title="groups elements which provide information about people and their relationships." href="ref-model.personLike.html">model.personLike</a> <a class="link_odd" title="groups elements which form part of the description of a person." href="ref-model.personPart.html">model.personPart</a> <a class="link_odd" title="groups elements which can occur at the level of individual words or phrases." href="ref-model.phrase.html">model.phrase</a> <a class="link_odd" title="groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values" href="ref-model.phrase.xml.html">model.phrase.xml</a> <a class="link_odd" title="groups specialized elements forming part of the physical description of a manuscript or similar written source." href="ref-model.physDescPart.html">model.physDescPart</a> <a class="link_odd" title="groups elements used to provide information about places and their relationships." href="ref-model.placeLike.html">model.placeLike</a> <a class="link_odd" title="groups elements which form part of a place name." href="ref-model.placeNamePart.html">model.placeNamePart</a> <a class="link_odd" title="groups elements which describe changing states of a place." href="ref-model.placeStateLike.html">model.placeStateLike</a> <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> <a class="link_odd" title="groups elements used for purposes of location and reference." href="ref-model.ptrLike.html">model.ptrLike</a> <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> <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> <a class="link_odd" title="groups elements related to highlighting which can appear either within or between chunk-level elements." href="ref-model.qLike.html">model.qLike</a> <a class="link_odd" title="groups elements used to directly contain quotations." href="ref-model.quoteLike.html">model.quoteLike</a> <a class="link_odd" title="groups separate elements which constitute the content of a digital resource, as opposed to its metadata." href="ref-model.resourceLike.html">model.resourceLike</a> <a class="link_odd" title="groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element." href="ref-model.respLike.html">model.respLike</a> <a class="link_odd" title="groups elements used for arbitrary segmentation." href="ref-model.segLike.html">model.segLike</a> <a class="link_odd" title="groups elements used to describe the setting of a linguistic interaction." href="ref-model.settingPart.html">model.settingPart</a> <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> <a class="link_odd" title="groups elements for referring to specification elements." href="ref-model.specDescLike.html">model.specDescLike</a> <a class="link_odd" title="groups elements containing stage directions or similar things defined by the module for performance texts." href="ref-model.stageLike.html">model.stageLike</a> <a class="link_odd" title="groups high level elements which may appear more than once in a TEI header." href="ref-model.teiHeaderPart.html">model.teiHeaderPart</a> <a class="link_odd" title="groups elements used to categorize a text for example in terms of its situational parameters." href="ref-model.textDescPart.html">model.textDescPart</a> <a class="link_odd" title="groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>." href="ref-model.titlepagePart.html">model.titlepagePart</a></li><li><span lang="en">Macros defined</span>: <a class="link_odd" title="" href="ref-data.certainty.html">data.certainty</a> <a class="link_odd" title="" href="ref-data.count.html">data.count</a> <a class="link_odd" title="" href="ref-data.duration.iso.html">data.duration.iso</a> <a class="link_odd" title="" href="ref-data.duration.w3c.html">data.duration.w3c</a> <a class="link_odd" title="" href="ref-data.enumerated.html">data.enumerated</a> <a class="link_odd" title="" href="ref-data.interval.html">data.interval</a> <a class="link_odd" title="" href="ref-data.language.html">data.language</a> <a class="link_odd" title="" href="ref-data.name.html">data.name</a> <a class="link_odd" title="" href="ref-data.namespace.html">data.namespace</a> <a class="link_odd" title="" href="ref-data.numeric.html">data.numeric</a> <a class="link_odd" title="" href="ref-data.outputMeasurement.html">data.outputMeasurement</a> <a class="link_odd" title="" href="ref-data.pattern.html">data.pattern</a> <a class="link_odd" title="" href="ref-data.percentage.html">data.percentage</a> <a class="link_odd" title="" href="ref-data.point.html">data.point</a> <a class="link_odd" title="" href="ref-data.pointer.html">data.pointer</a> <a class="link_odd" title="" href="ref-data.probability.html">data.probability</a> <a class="link_odd" title="" href="ref-data.replacement.html">data.replacement</a> <a class="link_odd" title="" href="ref-data.sex.html">data.sex</a> <a class="link_odd" title="" href="ref-data.temporal.iso.html">data.temporal.iso</a> <a class="link_odd" title="" href="ref-data.temporal.w3c.html">data.temporal.w3c</a> <a class="link_odd" title="" href="ref-data.text.html">data.text</a> <a class="link_odd" title="" href="ref-data.truthValue.html">data.truthValue</a> <a class="link_odd" title="" href="ref-data.version.html">data.version</a> <a class="link_odd" title="" href="ref-data.versionNumber.html">data.versionNumber</a> <a class="link_odd" title="" href="ref-data.word.html">data.word</a> <a class="link_odd" title="" href="ref-data.xTruthValue.html">data.xTruthValue</a> <a class="link_odd" title="" href="ref-data.xmlName.html">data.xmlName</a> <a class="link_odd" title="" href="ref-data.xpath.html">data.xpath</a> <a class="link_odd" title="" href="ref-macro.anyXML.html">macro.anyXML</a> <a class="link_odd" title="" href="ref-macro.limitedContent.html">macro.limitedContent</a> <a class="link_odd" title="" href="ref-macro.paraContent.html">macro.paraContent</a> <a class="link_odd" title="" href="ref-macro.phraseSeq.html">macro.phraseSeq</a> <a class="link_odd" title="" href="ref-macro.phraseSeq.limited.html">macro.phraseSeq.limited</a> <a class="link_odd" title="" href="ref-macro.specialPara.html">macro.specialPara</a> <a class="link_odd" title="" href="ref-macro.xtext.html">macro.xtext</a> <a class="link_odd" title="" href="ref-teidata.certainty.html">teidata.certainty</a> <a class="link_odd" title="" href="ref-teidata.count.html">teidata.count</a> <a class="link_odd" title="" href="ref-teidata.duration.iso.html">teidata.duration.iso</a> <a class="link_odd" title="" href="ref-teidata.duration.w3c.html">teidata.duration.w3c</a> <a class="link_odd" title="" href="ref-teidata.enumerated.html">teidata.enumerated</a> <a class="link_odd" title="" href="ref-teidata.interval.html">teidata.interval</a> <a class="link_odd" title="" href="ref-teidata.language.html">teidata.language</a> <a class="link_odd" title="" href="ref-teidata.name.html">teidata.name</a> <a class="link_odd" title="" href="ref-teidata.namespace.html">teidata.namespace</a> <a class="link_odd" title="" href="ref-teidata.namespaceOrName.html">teidata.namespaceOrName</a> <a class="link_odd" title="" href="ref-teidata.nullOrName.html">teidata.nullOrName</a> <a class="link_odd" title="" href="ref-teidata.numeric.html">teidata.numeric</a> <a class="link_odd" title="" href="ref-teidata.outputMeasurement.html">teidata.outputMeasurement</a> <a class="link_odd" title="" href="ref-teidata.pattern.html">teidata.pattern</a> <a class="link_odd" title="" href="ref-teidata.percentage.html">teidata.percentage</a> <a class="link_odd" title="" href="ref-teidata.point.html">teidata.point</a> <a class="link_odd" title="" href="ref-teidata.pointer.html">teidata.pointer</a> <a class="link_odd" title="" href="ref-teidata.prefix.html">teidata.prefix</a> <a class="link_odd" title="" href="ref-teidata.probCert.html">teidata.probCert</a> <a class="link_odd" title="" href="ref-teidata.probability.html">teidata.probability</a> <a class="link_odd" title="" href="ref-teidata.replacement.html">teidata.replacement</a> <a class="link_odd" title="" href="ref-teidata.sex.html">teidata.sex</a> <a class="link_odd" title="" href="ref-teidata.temporal.iso.html">teidata.temporal.iso</a> <a class="link_odd" title="" href="ref-teidata.temporal.w3c.html">teidata.temporal.w3c</a> <a class="link_odd" title="" href="ref-teidata.text.html">teidata.text</a> <a class="link_odd" title="" href="ref-teidata.truthValue.html">teidata.truthValue</a> <a class="link_odd" title="" href="ref-teidata.unboundedInt.html">teidata.unboundedInt</a> <a class="link_odd" title="" href="ref-teidata.version.html">teidata.version</a> <a class="link_odd" title="" href="ref-teidata.versionNumber.html">teidata.versionNumber</a> <a class="link_odd" title="" href="ref-teidata.word.html">teidata.word</a> <a class="link_odd" title="" href="ref-teidata.xTruthValue.html">teidata.xTruthValue</a> <a class="link_odd" title="" href="ref-teidata.xmlName.html">teidata.xmlName</a> <a class="link_odd" title="" href="ref-teidata.xpath.html">teidata.xpath</a></li></ul></dd></dl><p>The order in which declarations are made within the infrastructure module is critical, since several class declarations refer to others, which must therefore precede them. Other constraints on the order of declarations derive from the way in which the modularity of the TEI scheme is implemented in different schema languages. The XML DTD fragment implementing this TEI module makes extensive use of <span class="term">parameter entities</span> and <span class="term">marked sections</span> to effect a kind of conditional construction; the RELAX NG schema fragment similarly predeclares a number of patterns with null (‘notAllowed’) values. These issues are further discussed in chapter <a class="link_ptr" href="USE.html#IM" title="Implementation of an ODD System"><span class="headingNumber">23.5 </span>Implementation of an ODD System</a>.</p></div><div class="teidiv1" id="STDD"><div class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> « </span><a class="navigation" href="ST.html#STOV"><span class="headingNumber">1.5 </span>The TEI Infrastructure Module</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="#STDD" title="link to this section "><span class="invisible">TEI: Deprecated Datatype Macros</span><span class="pilcrow">¶</span></a></span><span class="headingNumber">1.6 </span><span class="head">Deprecated Datatype Macros</span></h3><p>For each of the datatypes mentioned in <a class="link_ptr" href="ST.html#DTYPES" title="Datatype Specifications"><span class="headingNumber">1.4.2 </span>Datatype Specifications</a> above, an older datatype macro also exists which uses RELAX NG syntax rather than the pure ODD syntax used throughout these Guidelines. These older macros have the prefix <code>data.</code> rather than <code>teidata.</code>. They have been retained for backwards compatability, but will be removed at a future release. A TEI customization which makes reference to an old style datatype, for example <span class="ident">data.xxxx</span> should continue to work until that time; it is however recommended to replace such references with the new form <span class="ident">teidata.xxxx</span> as soon as convenient.</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="CH.html"><span class="headingNumber">vi. </span>Languages and Character Sets</a><span class="nextLink"> » </span><a class="navigation" href="HD.html"><span class="headingNumber">2 </span>The TEI Header</a></nav><!--Notes in [div]--><div class="notes"><div class="noteHeading">Notes</div><div class="note" id="Note38"><span class="noteLabel">1 </span><div class="noteBody">The colon is also by default a valid name character; however, it has a specific purpose in XML (to indicate namespace prefixes), and may not therefore be used in any other way within a name.</div> <a class="link_return" title="Go back to text" href="#Note38_return">↵</a></div><div class="note" id="Note39"><span class="noteLabel">2 </span><div class="noteBody">In former editions of these Guidelines, such elements were known metaphorically as ‘crystals’.</div> <a class="link_return" title="Go back to text" href="#Note39_return">↵</a></div><div class="note" id="Note40"><span class="noteLabel">3 </span><div class="noteBody">Note that in this context, <span class="term">phrase</span> means any string of characters, and can apply to individual words, parts of words, and groups of words indifferently; it does not refer only to linguistically-motivated phrasal units. This may cause confusion for readers accustomed to applying the word in a more restrictive sense.</div> <a class="link_return" title="Go back to text" href="#Note40_return">↵</a></div><div class="note" id="Note41"><span class="noteLabel">4 </span><div class="noteBody">Technically <a class="link_ref" href="https://tools.ietf.org/html/rfc3986#section-3.1">the specification</a> permits the 26 uppercase letters <span class="mentioned">A-Z</span>; however, since <span class="quote">‘the canonical form is lowercase and documents that specify schemes must do so with lowercase letters’</span>, the TEI <span class="ident-datatype">teidata.prefix</span> datatype does not permit uppercase letters.</div> <a class="link_return" title="Go back to text" href="#Note41_return">↵</a></div></div><div class="stdfooter autogenerated"><p>
[<a href="../../en/html/ST.html">English</a>]
[<a href="../../de/html/ST.html">Deutsch</a>]
[<a href="../../es/html/ST.html">Español</a>]
[<a href="../../it/html/ST.html">Italiano</a>]
[<a href="../../fr/html/ST.html">Français</a>]
[<a href="../../ja/html/ST.html">日本語</a>]
[<a href="../../ko/html/ST.html">한국어</a>]
[<a href="../../zh-TW/html/ST.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>