jTEI input customizationRon Van den Brandenron.vandenbranden@kantl.beMartin Holmesmholmes@uvic.caOriginally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.
Originally generated by oddbyexample.xsl, based on analyzing 6 files from file:/F:/ctb/jTEI/jTEIsource/branches/working docs/tei2openedition/oddbyexample. Manually modified thereafter.
font-style:italic;font-style: italic;font-style: italic;font-style: italic;font-style: italic;font-family:Courier;font-family:Courier;font-family:Courier;font-family:Courier;font-family:Courier;font-family:Courier;font-family:Courier;vertical-align:super;border: 1px solid black;width: 100%;margin-left:2em;display:block;font-weight: bold; font-size: 120%;display: block;font-weight: bold;display: block;white-space:preserve; Gradual enhancement and modification of the schema as we work through the initial tests with documents for Issue 6 and 7 of the journal.Created initial ODD with oddbyexample.xslSimplified + refined initial versionJournal of the Text-Encoding Initiative Article SchemaSchema and guidelines for encoding an article for the journalRon Van den BrandenMartin Holmes2014
Introduction
This document introduces and documents the content and use of the schemas provided by the
Journal of the Text Encoding Initiative, as part of the TEI P5 distribution, for the use of authors who want to submit their articles to the journal in TEI. The schema described in this document is highly constrained and restrictive, consisting only of some 80 elements, compared with the complete TEI schema which contains nearly six hundred. In addition to general structural constraints, the ODD file also embeds fine-grained Schematron rules, severely limiting your options as you encode your file.
It is very likely that, as an experienced and confident TEI encoder with a broad knowledge of the TEI schema, you will find this at least a little frustrating. Where the TEI typically provides several ways of encoding the same phenomenon, we usually support only one. Where larger TEI schemas will allow you to describe rendering features (<hi rend="italic">) we do not allow that; we force you to choose a conceptual tag such as <emph> or <title level="j">.
The reasons for this are fairly obvious. From the XML document you submit, we need to generate a range of different outputs—ODT for reviewers and copyeditors to read and annotate, OpenEdition XML for submission to the revues.org publication engine that supports the journal website, and an accompanying PDF version. We must enforce a degree of conformity across all submissions, not only in order to maintain consistency when we publish, but also to ensure that contributions are assessed by reviewers in as fair a manner as possible, without possible influences due to divergence from the expected style rules or formatting conventions.
However, this constraint and conformity has advantages for you too, as an author. Our schemas will enforce a number of constraints which, we believe, may assist you in improving the quality of your article; these are a few of them: All quotations should be linked to references in the text.All references must be linked to bibliography items.All bibliography items must be cited somewhere in the text.All text styles such as italicization or quotation marks appear as a result of conceptual tags.
In what follows, we aim to provide a readable guide to encoding your article (or perhaps even composing it) according to the journal schemas, beginning with the template we provide, and viewing your results as you work through the use of CSS (in Author Mode in Oxygen) or by transforming it into ODT for examination in your word-processor, or to PDF.
This document is a work-in-progress (always), and we welcome your feedback at either mholmes@uvic.ca (Martin Holmes) or ron.vandenbranden@kantl.be (Ron Van den Branden).
Encoding for jTEI in Oxygen
Using the Template
Starting with version 16.2, the default distribution of Oxygen should include the jTEI components as part of its built-in TEI P5 framework. If you are using an older version of Oxygen, you can subscribe to the TEI-built version of the framework, by following these instructions.
In Oxygen, you can start a new article based on the jTEI template by selecting File → New, and selecting JTEI Article [TEI P5] under Framework templates → TEI P5.
Selecting the jTEI article template in Oxygen.
You will see that the root <TEI> element in the new file has an attribute rend=jTEI. This tells Oxygen that it's a jTEI file, so that it can apply standard jTEI rendering and validation scenarios to it. If you don't want to keep this attribute value, you can achieve the same effect by saving the file with a filename matching this format: jtei-*-source.xml (where the asterisk stands for anything you like); Oxygen will also recognize files with names in this format as jTEI files.
Testing Your Document
The Oxygen framework provides two output rendering scenarios, which allow you to transform your jTEI article to the ODT and PDF formats. Open the ODT file you create in a recent version of LibreOffice or OpenOffice; Microsoft Office does not support the current ODT specification. The PDF file can be viewed in a PDF viewer such as Adobe Reader. If you see any problems with the rendering, don't worry, and please don't change good TEI XML to bad TEI in an attempt to make it render more successfully; report the problem to us and we'll look into it.
Basic Text Structure
A jTEI journal article is a relatively simple TEI document consisting of a <teiHeader> and a <text>.
The Header and Metadata
This is an example <teiHeader>:
Learning the TEI in a Digital EnvironmentStellaDeeStella Dee is currently a Research Associate
working to develop e-learning resources for historical languages with the
Open Philology Project at the University of Leipzig.
The research of this article was conducted while studying for a Masters
degree in digital humanities at King’s College, London.dee@informatik.uni-leipzig.deTEI Consortium2014Issue 7
Revues.org -centre for open electronic publishing- is the platform for journals in the
humanities and social sciences, open to quality periodicals looking to publish full-text
articles online.
pedagogystudent resourcessurveyfile publication
Some of the content is boilerplate material provided by the template. These are the parts that you must supply:
The title of your article (in fileDesc/titleStmt/title[@type='main']).Author information for each author (in fileDesc/titleStmt/author). Provide one <author> element for each author. Encode the names as shown, using <forename> and <surname>, inside <name>. Then provide a brief biographical paragraph for each author in <affiliation>, and an email address.Keywords (in profileDesc/textClass/keywords). Provide a handful of general categories under which you feel your article fits. There is (currently) no formal ontology of article categories to choose from. You may consult the list of keywords from previous articles on the journal website, but if you don't see what you need, feel free to use new ones. The editors may formalize these categories in future.
Front Matter
The front matter must consist of an abstract, encoded in <div type="abstract">. This should consist of one or two short paragraphs, covering the purpose and content of the article.
The only other thing that may appear in the front matter is a brief acknowledgements section. If you need to include this to acknowledge contributors, funding agencies etc., insert it after the abstract, encoded as <div type="acknowledgements">. It should be no longer than one short paragraph.
The Body
The content of the article appears in the body. It should be divided into sections using <div> elements. Each <div> element should have an xml:id attribute, and its first child should be a <head> element with a suitable heading (in title case). <div> elements may be nested to provide subsections.
Do not provide section numbering in explicitly in the <head>s of your <div>s. These will be provided automatically by the rendering tools.
Back Matter: the Bibliography and Appendices
The back matter consists of a bibliography (required), which is encoded in <div type="bibliography">, and optional appendices, each of which if present must be encoded using <div type="appendix">. Appendices must appear after the bibliography.
The bibliography consists of a <listBibl> element containing a series of <bibl> elements. Each <bibl> element should contain a reference formatted as required by the
Chicago Manual of Style (16th edition), including all required punctuation, with a couple of exceptions:Do not provide quotation marks around article titles. Instead, tag them with <title level="a"> (for chapters or contributions in a monograph, or journal articles) or <title level="u"> (for unpublished materials). The rendering tools will then provide the quotation marks.Tag titles that would normally be in italics using <title level="j"> (for journal titles) or <title level="m"> (for monographs).
Give each <bibl> element a unique xml:id attribute, so that you can link to it from the quotations in the body of your text. In your bibliography entries, put the appropriate tags around the following components:
titles: <title>, with an appropriate value for level (see above)editions: <edition>dates: <date>authors: <author>editors: <editor>publishers: <publisher>publication places: <pubPlace>name of series: <series>scope of a bibliographic reference: <biblScope>, with an appropriate value for unit (volume, issue, page, chapter, part)id numbers such as DOIs: <idno>, with an appropriate value for typeweb urls (use <ref>)
Note: if you have both a formal identification number such as a DOI code and a hyperlink to an online version, the DOI code should be placed last in the bibliographic description.
Here is a short example:
Aoki, Paul M.2007.
Back Stage on the Front Lines: Perspectives and
Performance in the Combat Information Center. In
Proceedings of the SIGCHI Conference on
Human Factors in Computing Systems,
717–26. CHI ’07.
New York: ACM.
http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
. doi:10.1145/1240624.1240735.
Bański, Piotr. 2010.
Why TEI Stand-off Annotation Doesn’t Quite Work and
Why You Might Want to Use It Nevertheless. In
Proceedings of Balisage: The Markup Conference 2010.
Balisage Series on Markup Technologies,
vol. 5.
doi:10.4242/BalisageVol5.Banski01.
Bowers, John. 2012.
The Logic of Annotated Portfolios: Communicating the
Value of <soCalled>Research through Design.</soCalled> In
Proceedings of the Designing Interactive Systems
Conference, 68–77.
DIS ’12. New York:
ACM. doi:10.1145/2317956.2317968.
Divisions, Paragraphs, Lists and Other Block Elements
Divisions
Text divisions are encoded in <div>. Each division must have a <head> containing the heading for this division. Headings should just contain the bare heading, without numbering or other labels; those are added automatically when the TEI source file is rendered.
Divisions typically consist of a number of paragraphs, inside <p> elements. Apart from paragraphs, they can contain following text structures:subdivisionslistsquotationsfigures and graphicstablescode examples
Divisions can nest, by simply including a new <div> element with an xml:id attribute and a <head> in a parent division. There's no need to indicate the nesting level for subdivisions: this is determined from the structural encoding by the rendering scripts. Please note that the general TEI limitations hold: divisions may not be followed by bare paragraphs. In order to facilitate cross-referencing, you are encouraged to provide a unique identification code in an xml:id attribute for each <div>.
Following example illustrates a text division in which two introductory paragraphs are being followed by two more subdivisions.
What’s not ODD?
In the current source of TEI P5, there is extensive use of several different
XML vocabularies: Examples in TEI P5 are presented as if they belonged to some other
TEI Example Namespace;Element content models are expressed using a subset of RELAX NG, as
discussed in the previous section;Datatypes are expressed in a variety of ways, mapping either to built-in
W3C datatypes (as defined in the W3C Schema Language) or to RELAX NG
constructs;Additional semantic constraints (for example, co-dependence of
attributes and element content) are expressed using ISO Schematron
rules.
Everything else in a TEI-conformant ODD specification uses only constructs from
the TEI namespace. In this paper, we will argue for a further extension of the
ODD language to replace several of the cases listed above.
Element Content Models
ODD was originally intended to support the intersection of the
content models definable using three different schema languages. In practice,
this reduced our modeling requirements quite significantly.
Datatyping and Other Forms of Validation
Validation of an element’s content model is but one of many different layers
of validation that a TEI user may wish to express in their ODD specification.
Paragraphs
Paragraphs are encoded with <p> elements. They are the main building blocks of a division. They can contain plain text, mixed with other structural elements:
Thus we introduce the transferGrp element, a grouping element somewhat
like surfaceGrp but, like altGrp or attList, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an org attribute whose suggested
values include:
an unordered seta (chronologically) ordered setonly one of the child transfers
obtained
The following example demonstrates the use of transferGrp to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.
Lists
Lists in jTEI are relatively simple. They are encoded in a <list> element and differentiated by the type attribute, which may have only one value, gloss. <list type="gloss"> is (as you might expect) a glossary list, and must consist of a sequence of <label>s and <item>s, like this:
a device which reduces the peaks of volume in an audio signala device which allows different frequency bands in an audio signal
to be cut or boosted
All other types of list (numbered, bulleted etc.) do not have the type attribute. Their appearance is controlled by the rend attribute: listcontains any sequence of items organized as a list.
rend(rendition) describes the way the list should be rendered.
Lists may be nested: compressor:
limitermultiband compressorequalizer:
graphic equalizerparametric equalizer
For processing reasongs, jTEI puts one restriction on what can appear inside lists: you can't use <table> anywhere inside <item>.
Quotations, Inline and Block
The main components of a quotation are the quoted text itself, and a reference to the source it was quoted from. The quoted text is encoded with a <quote> element, without quotation marks. Quotations marks are added automatically by the rendering scripts. The jTEI schema requires that each quotation is linked to a bibliographic reference, identifying the source from where the text has been quoted. Typically, the source of a quotation is listed in the bibliography at the end of the article. References to such sources are encoded in a <ref> element, with a type attribute of value bibl, whose target attribute must point to the xml:id value of a <bibl> element in the article's bibliography. You must provide an xml:id attribute for the <ref> element itself. This makes it possible to connect the quotation with its specific reference via the source attribute on the <quote> element:
In his blog post,
Text: A Massively Addressable Object,
published in the 2012 anthology Debates in the Digital
Humanities, Michael Witmore defines texts as objects that are
massively addressable at different levels of scale
(Witmore 2012, 325).
Here, we see how the value #quoteref3 for the source attribute expresses the correspondence with the bibliographic reference in <ref type="bibl" xml:id="quoteref3" target="#witmore12">Witmore 2012, 325</ref>.
In some cases, quotations are taken from less bibliographic sources, such as email conversations and other non-published texts. Such sources are not listed in the bibliography, so you can't refer to them with a <ref type="bibl"> reference. Instead, you should include the description of the source in the text. The description should be encoded in a <bibl> element with an xml:id attribute. You should link the quotation to this bibliographic description by pointing to this xml:id attribute with the source attribute of the <quote> element:
An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
a graduate student in English who has heard about TEI
and wants to dip her toes into it because she thinks it may be a better way of
putting on the Web some 17th century poems Where does she go for help?
Where in the TEI universe is the level of ubiquitous Grade I support?
(Martin Mueller, pers. comm, Jan. 18, 2013).
Here, the #quoteref1 value for the source attribute on <quote> points to the <bibl> element in the text, describing the less bibliographic source for the quotation in a footnote.
Note how the examples above were inline quotations, which will be rendered inside the running text of the paragraph they appear in. It is also possible to encode block quotations, by wrapping the <quote> and its <ref> inside a <cit> container. A <cit> element can occur either in or between paragraphs, but is always rendered as a blockquote:
In
Wampum as Hypertext, Angela Haas complicates the
distinction between technology and high technology by discussing the way wampum
belts function the same as Western hypertexts. Haas contends that while there are
many similarities, they differ when we understand the way wampum is reliant on
cultural practices and memory:
Consequently one could argue that wampum is limited
in relation to contemporary Western hypertexts in that it requires human
intervention to remember the intent and content of the original message; however,
one could also posit that such interaction encourages continuous civic involvement
instead of an over-reliance on technology.Haas 2007, 93
The <cit> element has been constrained in jTEI so it can only contain <quote>, <ref>, and <bibl>.
Inside quotations, inline rhetorical elements can be used (see ). Two of such elements are quite specific to quotations, in the context of a jTEI article, however, namely omissions and supplied text. Omissions are encoded with <gap>, which at rendering time is transformed to the typographic omission symbol: …Note, if you're omitting text at the end of a sentence, the sentence punctuation should precede the <gap> element.. If you supply text that wasn't present in the original quotation, you should wrap the supplied text in a <supplied> element. At rendering time, the <supplied> start and end tags are replaced with the [ and ] characters, respectively.
Apart from <quote> for attributed quotations, you can also use <q> for short anonymous inline quotations, whose source is not known or irrelevant. This is discussed in more detail in .
Figures and Graphics
Illustrative figures are encoded using the<figure> element, along with a mandatory <head type="legend"> element providing the caption for the figure, as in this example:
The title page of the 1598 edition
The graphics file should be in PNG or JPEG format, and should be stored in a directory called img which is a sibling of the article XML file. Graphics file names should not contain spaces or punctuation. The <graphic> element must include the width and height attributes containing the image size in pixels. A second <head type="license"> may also be provided in cases where an explicit statement of licensing, copyright or accreditation is required.
The caption in the <head type="legend"> element should not begin with Figure 1 or any similar prefix; this will be provided by the rendering code at output time. To link to the figure, all you need to do is to provide a pointer targeting its xml:id attribute, like this:
As you can see from ,
the title page is damaged...
This will be expanded at rendering time into Figure X, where X is the appropriate figure number.
Example Code, XML and non-XML
Example computer code in jTEI falls into two categories. XML code appears in the <egXML xmlns="http://www.tei-c.org/ns/Examples"> element. When you use this element, make sure you get the namespace right; all elements appearing in the <egXML> element are also in the Examples namespace, to distinguish them from regular TEI elements that are part of the encoding of the document. Code from non-XML languages appears in the <eg> element.
In many cases, example code will appear inline as part of the prose of your articleNote, however, that <eg> and <egXML> examples are always rendered as blocks, regardless of their appearance as inline or block-level elements in the article encoding. If you want to include a short code fragment that should be rendered inline, you can use the <code> element as discussed in .:
Links between authors and books are encoded using link elements: <egXML
xmlns="http://www.tei-c.org/ns/Examples">
</egXML>
You might want to provide a caption for code examples. In these cases, the <eg> or <egXML> element should be enclosed in a <figure>:
declare function local:getTitles($source as element(div)) as xs:string*{
for $t in $source//title
return xs:string($t)
};
A simple XQuery function At rendering time, captions of examples will be supplied with a leading Example X, where X is the number of the example. You can link to and refer to block examples like this using ref and ptr. In order to do so, you should provide a unique identification code to the <figure> in an xml:id attribute.
Tables
Tables can be encoded with the <table> element. Tables consist of a number of rows (<row>) that contain a number of cells (<cell>). Header rows and cells can be distinguished by different values for the type attribute:The row or cell contains a header, not actual data.(default) The row or cell contains data.
Cells and rows can be merged. In order to indicate how many columns a row or cell spans, a number can be provided for a cols attribute; the number of rows spanned can be given as value for a rows attribute.
Elements in tei_corset customizationModuleElements in tei_corsettextstructurebodydivTEIfigurescellrowtablea sample cell spanning two columns (this was not in the original)
The example above illustrates how the first row is marked as a header row with <row role="label">, and how the left column is marked as a header column by specifying each first cell in a row as <cell role="label">. The last cell illustrates how column spanning can be indicated with <cell cols="2">.
Note how the example also illustrates how tables can have headings, in a <head> element. The text of this heading should not begin with Table 1 or any similar prefix; this will be provided when the article is rendered. To link to the table, all you need to do is to provide a pointer targeting its xml:id attribute:
As you can see from , the elements included...
This will be expanded at rendering time into Table X, where X is the appropriate table number.
Inline Rhetorical Elements
The jTEI schema prompts you to encode information as much as possible with conceptual tags. Therefore, the general-purpose <hi> tag has been removed from the jTEI schema. Instead, you should use more semantically expressive elements for identifying the rhetorical phenomenon you want to encode. If you want to stress a word in a sentence, you can do so with the <emph> element, which is rendered as italicized text. Foreign terms can be tagged with <foreign>, with a proper language identification code for the xml:lang attribute. Technical terms, or terms in general, can be encoded with <term>, and appear as italicized text in the rendered article.
Interoperability may be defined as the property of data that allows
it to be loaded unmodified and fully used in a variety
of software applications. Interchange is basically the same property
that applies after a preliminary conversion of the data (Bauman
2011; Unsworth 2011), and
implies some loss of information in the process. Interchange can thus be seen as
an easier, less stringent or less useful kind of information exchange than pure interoperability.
Unicode is a character encoding standard, and is not intended to
standardize ligatures or other presentation forms
(Unicode 2014).
For example, there is no Unicode character for old Latin sescuncia
(like a pound-sign, = one eighth), since it can be composed from semuncia
(character 10192) and an EN-dash (Unicode 2006, 4)
Another category of inline rhetorical elements are those that are used for text that is somehow quoted. When a word is mentioned to illustrate its form or usage, without its actual meaning, it should be encoded as <mentioned>. At rendering time, it will be displayed in italics. When you use a word while at the same time distancing yourself from it, you should encode it with <soCalled>. At rendering time, the start and end tag will be replaced with double quotation marks. Finally, if you want to quote a word or passage without attributing it to an external source, you can use the <q> element. Such anonymous quotations are rendered in double quotation marks.
The actual form of the quotation marks depends on the nesting level of quotation marks, so that double and single quotation marks alternate when they nest. For example, if a word tagged as <soCalled> appears inside a <q> element, then the quoted text will be wrapped in double quotation marks, while the text inside <soCalled> will be rendered with single quotation marks.
The standard definition of metadata as data about data seems to pose more
questions than it answers.
There are possible ways (hacks) around some of these problems
even without rewriting the software, and some software is open source. For example,
some software may permit dates in the future, in which case a project
might record eighteenth-century dates using values from the twenty-eighth century.
Pounds, shillings, and pence could be converted to a modern standard unit (for
example, US dollars; Measuring Worth
provides calculators for determining values in some historical currencies). A
project could consistently use the comments, memo,
or notes field to record pointers into the attesting document.
If you mention titles in paragraph text, you should encode them as such, with the <title> element and a proper type for the level attribute. Titles of journals (level="j" for level) and monographs (m) are rendered in italics. Titles of book chapters or journal articles (a), or unpublished materials (u) are enclosed in quotation marks at rendering time (so you mustn't provide them yourself).
Inline Technical Elements
Due to the nature of this journal, a discussion of technical XML or TEI elements is a common feature in jTEI articles. When elements from an XML vocabulary are discussed, they should be identified in a <gi> element, with an optional scheme attribute in which the XML vocabulary can be named. The default value for this attribute is TEI for TEI elements; others could be HTML, Schematron, DBK (Docbook), etc. At rendering time, the <gi> start and end tags are replaced with the < and > characters, respectively. The element name is always presented in this form: <p> in the output rendering, even if it is an empty element which in actual usage is almost always self-closing, such as <lb/> or pb.
Attribute names should be tagged in an <att> element, which at rendering time will be preceded with a @ character. Attribute values should be tagged in <val>. At rendering time, the <val> start and end tags are replaced with straight quotation marks, so there is no need to quote the values yourself.
For example, the extension of credit can be represented in a transactionography
by the transfer of a commodity of indebtedness. We have been using the keyword
iou as the value of commodity of measure for this purpose.
When you want to quote an instance of a single start or end tag, you should use the <tag> element. If you want to specify the XML vocabulary this tag belongs to, this can be done in the scheme attribute (see above). In the type attribute, you can specify the kind of tag: start (start tag), end (end tag), empty (an empty tag), pi (processing instruction), comment (an XML comment), or ms (a CDATA marked section). For all these types of tags, the proper delimiters (starting with the < and ending with the > characters) are inserted when the article is rendered. Note, for full-fledged XML examples, the <egXML> element should be used (see ).
A range like #range(left(//lb[@n='3']),left(//lb[@n='4'])), however,
could unambiguously address the sequence of nodes comprising line 3, even if the
lb happened to be a child of another element that began in the previous line.
For example, rng:ref name="model.pLike" becomes classRef key="model.pLike".
If you want to cite a brief inline code fragment from a formal programming language, you can use the <code> element. With the lang attribute, you can identify the language of the code:
Most of the time, pointing from one part of a TEI document to another, it is easy
to use IDs. Simply wrap the thing in an element, give that element an xml:id
attribute (say, xml:id="foo"), and point at the ID using either a
URI with an appended fragment identifier (#foo) or using an attribute
whose type is IDREF.
The <ident> element should be used to encode identifiers in a formal language, such as variable, class, and function names in a programming language. When discussing the TEI encoding scheme or customizations, the names of model and attribute classes, datatypes, macros, and TEI customizations should be encoded with <ident>:
For example data.duration.iso, data.outputMeasurement,
data.pattern, data.point, data.version,
and data.word all map to the same datatype CDATA in XML DTD, and to
various TEI-defined regular expressions in RELAX NG or W3C Schema.
Footnotes
jTEI articles can have footnotes. Since no other notes are supported, the encoding is fairly simple: just add a <note> element at the place where you want to insert the footnote in the text. No further attributes are required: numbering is catered for at rendering time. Notes can contain plain text or paragraphs. No block-level elements are allowed:
There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the match attribute,
See
and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have xml:id attributes.
Internal Linking
Internal links are cross-links within the article. In jTEI, you can point to other text structures that can have labels, namely <div>, <figure> (containing either graphics or code examples), or <table>. You can link to those structures either with an unlabeled cross-reference in <ptr/>, or with a labeled link in <ref>. Both must have a type attribute with value crossref, and a target attribute, whose value should start with the # sign, followed by the xml:id value of the element it addresses:
The following figure shows a typical example of such a tag document.
Tagdoc for resp element in P2.
For unlabeled cross-links, the <ptr type="crossref" xml:id="#link-target"> is replaced with an appropriate label for the link target at rendering time:
shows allowable rend values and
their equivalent meanings.
Allowable rend attribute values in tei_corset
customizationrend(renamed r) attribute valueMeaning
In the generated ODT, OpenEdition, and PDF version, the cross-reference is is rendered as: Table X shows allowable @rend values and their equivalent meanings.
Note how internal links are rendered as plain text instead of hyperlinks in the ODT version and the final version in revues.org.
Another type of internal linking consists of bibliographic references, pointing to entries in the bibliography. This should be done with a specific type of <ref> element, with value bibl for the type attribute. The value of the target attribute for bibliographic references must point to a <bibl> element in the bibliography:
Thomas notes numerous additional developments in the use of computers in historical
study, both in the United States and elsewhere between the 1940s and the early
twenty-first century (Thomas 2004).
Thomas, William G., III. 2004.
Computing and the Historical Imagination:
A Companion to Digital Humanities, edited by
Susan Schreibman, Ray Siemens, and
John Unsworth. Oxford:
Blackwell Publishing.
Note, how all characters surrounding bibliographic references have to be hard-coded in the text; they are not generated automatically at rendering time. For linking bibliographic references with quotations, see .
External Linking
Links to external destinations can be encoded with <ptr/> (unlabeled) or <ref> (labeled). They must have a target attribute whose value is the URI of the link's destination:addresses the range between two points (16.2.5.4 range())
More detailed information can be found at .
At rendering time, both types of links are transformed to clickable hyperlinks, and for <ptr/> the value of the target attribute is used as the link label.
One caveat for external links to the TEI Guidelines: since the web version at is unstable and will be updated at each new release, you must point to the archived versions in the Vault section of the TEI website. There, you can find an archive of all previous TEI releases and their documentation. Follow the links to the exact version you're referencing in your article (even if it's the current version), and use them for your external hyperlinks. In the examples above, the first link points to the documentation of version 2.2.0 of the TEI Guidelines, while the second link points to version 2.5.0.
Frequently-asked QuestionsWhere did <hi> go? How do I do italics?
We're trying to avoid <hi> because it's so widely used in so many different ways. We would also prefer that all styling be applied for semantic reasons, so rather than italics, think journal title or emphasis or foreign word. Also, what you believe should be in italics might in our style guide be rendered in quotation marks, or not styled at all; that's why it's easier if you identify things and let the system style them.
Why can't I use quotation marks?
Literal quotation marks can be straight double, straight single, curly double, curly single, or (if you happen to be on a non-English keyboard) a range of other symbols. All copyeditors are familiar with the tedium of checking that they're all the right form, and that all the inital ones are opening ones and the closing ones are the matching closing ones. It's much simpler if you tag your text as <quote>, <soCalled> or whatever, and let the XSLT provide the quotation marks in a reliable way.
Why is this so restrictive?
The TEI is a huge standard; there are lots of available approaches to encoding any given phenomenon, and every TEI user has their own habits and preferences, arising out of their history and the projects they've worked on. If we accept submissions in any valid TEI (tei_all), we inevitably spend many hours re-encoding them to get something that will work with our system. It's much simpler if we let the schema do the work for us.
Summary of Elements and their Rendition
Element/TagUsageExampleRendition<abbr>an abbreviation of any sortDPIDPI<att>attribute nameplace@place<cit>blockquote with bibliographic referenceAccount books
are among the most common but least accessible primary sources
for historiansMcGaw 1985[A]ccount books are among the most common but least accessible primary sources for historians … (McGaw 1985)<code>short inline code example
A mixed content model such as
(#PCDATA | a | model.b)*
might be expressed as follows
A mixed content model such as (#PCDATA | a | model.b)* might be expressed as follows
<eg>non-XML code example
$('#teiHolder').data('modVers', {
xmlFile: 'data/teiFile.xml'
annotations: 'data/annotations.json',
fixFirst: false,
fullscreen: false,
height: 300,
ids: 'a,b,c',
witnesses: 'v1,v2'
});
$('#teiHolder').data('modVers', {
xmlFile: 'data/teiFile.xml'
annotations: 'data/annotations.json',
fixFirst: false,
fullscreen: false,
height: 300,
ids: 'a,b,c',
witnesses: 'v1,v2'
});
<egXML>XML example code
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<content>
<classRef key="model.ab" maxOccurs="unlimited"/>
</content>
</egXML>
<emph>emphasized text (italics)
The TEI began as a conscious attempt to model
existing and future markup systems.
The TEI began as a conscious attempt to model existing and future markup systems.<figure>a block figure or example code, with a mandatory headingPage-image from Ingelow’s
PoemsFigure 1: Page-image from Ingelow’s Poems<foreign>a foreign text fragment
Nowhere is this more obvious than in the weight
accorded the single author monograph, which remains
the standard par
excellence of scholarship in the humanities.
Nowhere is this more obvious than in the weight accorded the single author monograph, which remains the standard par excellence of scholarship in the humanities.<gap>an omission in quoted textLeisure moments only
available for its execution“Leisure moments only … available for its execution”<gi>the name of an XML elementquote<quote><graphic>a digital image<head>a heading for a text division, figure, table, or list
Future Directions
4. Future Directions<ident>identifier in a formal language
the new range() and string-range()
pointers
the new range() and string-range() pointers<list>a listThe first misconception is this: digital texts and digital
archives merely replicate physical texts and physical archives
in a non-material environment.The second misconception is that all possible digital
representations of a text are created equal.The first misconception is this: digital texts and digital archives merely replicate physical texts and physical archives in a non-material environment.The second misconception is that all possible digital representations of a text are created equal.<mentioned>a word that is mentioned
conversations on the multi-dimensional understanding of
text and representationconversations on the multi-dimensional understanding of text and representation<note>a footnote
A similar suggestion is made in Eric Van der Vlist’s
RELAX NG
http://relaxng/.
(2004)
A similar suggestion is made in Eric Van der Vlist’s RELAX NG1 (2004) Notes
1http://relaxng/.
<ptr/>a pointer to another location (internal or external)
The rest of this paper treats each of these points in more detail.
describes the
nature of the interoperability problem.
The rest of this paper treats each of these points in more detail. Section 2 describes the nature of the interoperability problem.<q>a short, unattributed inline quotation
(student survey responses included words such as
apprehensive, intimidated, and even
terrified), which explains why one student
commented that TEI training was not something
I would have sought out on my own.(student survey responses included words such as “apprehensive,” “intimidated,” and even “terrified”), which explains why one student commented that TEI training “was not something I would have sought out on my own.”<quote>an attributed quotationNames of authors appear
in Italic Capitals
(Arber 1875–95, 1:29).
“Names of authors” appear in “Italic Capitals” (Arber 1875–95, 1:29).<ref>a reference to another location (with custom label text)16.2.5.4 range())
16.2.5.4 range())<soCalled>a word from which the author distances herself
There are possible ways (hacks) around
some of these problems
There are possible ways (“hacks”) around some of these problems<supplied>text that has been added by the jTEI author (in a quotation)Finding what you need can be problematic. Lack of
links to chapters that describe elements next
to some element definitions“Finding what you need can be problematic. Lack of links to chapters that describe elements next [to] some element definitions”<table>a table
Allowable rend attribute values in
tei_corset customizationrend(renamed r)
attribute valueMeaningabrendered above the linealrendered aligned to the left
Table 4: Allowable @rend attribute values in tei_corset customization
@rend(renamed @r) attribute valueMeaningabrendered above the linealrendered aligned to the left
<tag>a full XML tagrng:ref name="model.pLike"<rng:ref name="model.pLike"/><term>a technical term
Annotations are stored in triple stores
or graph databases like Neo4JAnnotations are stored in triple stores or graph databases like Neo4J<title>the title of a bibliographic workWhere Did All the Document Kids Go?
Open-source, Markup, and the Casual Developer.
Presented at Balisage: The Markup Conference 2013,
Montréal, Canada, August 6–9, 2013. In
Proceedings of Balisage: The Markup
Conference 2013.“Where Did All the Document Kids Go? Open-source, Markup, and the Casual Developer.” Presented at Balisage: The Markup Conference 2013, Montréal, Canada, August 6–9, 2013. In Proceedings of Balisage: The Markup Conference 2013.<val>an attribute value
an attribute preserveOrder taking values
true or falsean attribute @preserveOrder taking values "true" or "false"
Elements
<TEI><TEI>
<TEI> (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of <TEI> elements may be combined together to form a teiCorpus element. [4. Default Text Structure15.1. Varieties of Composite Text]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained by—May containheader: teiHeadertextstructure: textDeclaration
element TEI
{
att.global.attributes,
( teiHeader, ( ( model.resourceLike+, text? ) | text ) )
}Schematron
<s:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<s:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/>Schematron
<s:ns prefix="rng"
uri="http://relaxng.org/ns/structure/1.0"/>ExampleThe shortest TEI Document Imaginable
First published as part of TEI P2, this is the P5
version using a name space.
No source: this is an original work.
This is about the shortest TEI document imaginable.
ExampleA TEI Document containing four page images
Unpublished demonstration file.
No source: this is an original work.
NoteThis element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.
<abbr><abbr>@type
<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.source (@source)
typeallows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedSample values include:the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.the abbreviation omits some letter(s) in the middle.the abbreviation comprises a special symbol or mark.the abbreviation includes writing above the line.the abbreviation comprises the initial letters of the words of a phrase.the abbreviation is for a title of address (Dr, Ms, Mr, …)the abbreviation is for the name of an organization.the abbreviation is for a geographic name.NoteThe type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see
Member ofmodel.pPart.editorialContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element abbr
{
att.global.attributes,
att.source.attributes,
attribute type { data.enumerated }?,
macro.phraseSeq
}ExampleNorth Atlantic Treaty OrganizationNorATONATOOTANExampleSPQRsenatus populusque romanorumNoteThe <abbr> tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate.
<affiliation><affiliation>
<affiliation> contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source)) att.datable.w3c (notAfter, @when, @notBefore, @from, @to) Member ofmodel.addressLikemodel.persStateLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element affiliation
{
att.global.attributes,
att.editLike.attributes,
att.datable.w3c.attribute.when,
att.datable.w3c.attribute.notBefore,
att.datable.w3c.attribute.from,
att.datable.w3c.attribute.to,
macro.phraseSeq
}ExampleJunior project officer for the US National Endowment for
the HumanitiesPaid up member of the
Australian Journalists AssociationNoteIf included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.
<appInfo><appInfo>
<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.10. The Application Information Element]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.encodingDescPartContained byheader: encodingDescMay containheader: applicationDeclaration
element appInfo { att.global.attributes, model.applicationLike+ }Example
<application><application>@ident@version
<application> provides information about an application which has acted upon the document. [2.3.10. The Application Information Element]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.datable.w3c (notAfter, @when, @notBefore, @from, @to)
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequiredDatatypedata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequiredDatatypedata.versionNumber
Member ofmodel.applicationLikeContained byheader: appInfoMay containcore: desclabelpptrrefDeclaration
element application
{
att.global.attributes,
att.datable.w3c.attribute.when,
att.datable.w3c.attribute.notBefore,
att.datable.w3c.attribute.from,
att.datable.w3c.attribute.to,
attribute ident { data.name },
attribute version { data.versionNumber },
( model.labelLike+, ( model.ptrLike* | model.pLike* ) )
}ExampleThis example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr/> elements.
<att><att>
<att> (attribute) contains the name of an attribute appearing within running text. [22. Documentation Elements]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.phrase.xmlContained bycore: abbrauthorbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element att { att.global.attributes, data.name }Schematron
<sch:rule context="tei:att">
<sch:assert test="not(matches(., '^@'))"> Attribute delimiters are not allowed for <sch:name/>: they are completed at processing time via XSLT.
</sch:assert></sch:rule>Example
The TEI defines several global attributes; their names include
xml:id, rend, xml:lang, n, xml:space,
and xml:base; type is not amongst them.
NoteA namespace prefix may be used in order to specify the scheme as an alternative to specifying it via the scheme attribute: it takes precedence
<author><author>
<author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors2.2.1. The Title Statement]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.respLikeContained bycore: biblheader: titleStmtMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element author { att.global.attributes, macro.phraseSeq }Schematron
<sch:rule context="tei:titleStmt/tei:author">
<sch:assert test="tei:name and tei:affiliation and tei:email"> Author information in the <titleStmt> must include <name>, <affiliation> and <email>.
</sch:assert></sch:rule>ExampleBritish Broadcasting CorporationLa Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)AnonymousBill and Melinda Gates FoundationBeaumont, Francis and
John FletcherBritish Broadcasting
Corporation: Radio 3 NetworkNoteParticularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.
<availability><availability>
<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.biblPartmodel.publicationStmtPart.detailContained bycore: biblseriesheader: publicationStmtMay containcore: pDeclaration
element availability
{
att.global.attributes,
( model.availabilityPart | model.pLike )+
}Example
Available for academic research purposes only.
In the public domain
Available under licence from the publishers.
Example
The MIT License
applies to this document.
Copyright (C) 2011 by The University of Victoria
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
NoteA consistent format should be adopted
<back><back>
<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter4. Default Text Structure]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bytextstructure: textMay containcore: gapheadlblistnotepfigures: figuretablenamesdates: listPersontextstructure: divDeclaration
element back
{
att.global.attributes,
(
(
model.frontPart
| model.pLike.front
| model.pLike
| model.listLike
| model.global
)*,
(
(
(
( model.div1Like ),
( model.frontPart | model.div1Like | model.global )*
)
| (
( model.divLike ),
( model.frontPart | model.divLike | model.global )*
)
)?
),
( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? )
)
}Schematron
<sch:rule context="tei:back">
<sch:assert test="tei:div[@type='bibliography']/tei:listBibl">
<sch:name/> must have a bibliography (div[@type="bibliography"]), which must be organized inside a listBibl element.
</sch:assert></sch:rule>ExampleThe Golden Dream or, the Ingenuous Confession
To shew the Depravity of human Nature
A letter from the Printer, which he desires may be insertedSir.
I have done with your Copy, so you may return it to the Vatican, if you please
The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
Newbery's at the Bible and Sun in St Paul's Church-yard.The Christmas Box, Price 1d.The History of Giles Gingerbread, 1d.A Curious Collection of Travels, selected from the Writers of all Nations,
10 Vol, Pr. bound 1l.By the KING's Royal Patent, Are sold by J. NEWBERY, at the
Bible and Sun in St. Paul's Church-Yard.Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c.
2s. 6dDr. Hooper's Female Pills, 1s.NoteBecause cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.
<bibl><bibl>
<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References2.2.7. The Source Description15.3.2. Declarable Elements]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.biblLikemodel.biblPartContained bycore: biblcitdescemphheadhiitemlistBiblnotepqquotereftitlefigures: cellheader: changerenditionsourceDescnamesdates: persontextstructure: bodydivtranscr: suppliedMay containcore: abbrauthorbiblbiblScopedateeditoremailemphforeigngaphilbmentionednamenotenumptrpubPlacepublisherrefseriessoCalledtermtitlefigures: figureheader: availabilityeditionidnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: codeidenttranscr: suppliedDeclaration
element bibl
{
att.global.attributes,
(
text
| model.gLike
| model.highlighted
| model.pPart.data
| model.pPart.edit
| model.segLike
| model.ptrLike
| model.biblPart
| model.global
)*
}Schematron
<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:bibl"
role="warning">
<sch:assert test="@xml:id"> A bibliographic entry should have a unique value for @xml:id.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:bibl"
role="warning">
<sch:let name="currId" value="@xml:id"/>
<sch:assert test="some $i in //tei:ref[@type='bibl'] satisfies tokenize($i/@target,
'\s+')[replace(., '#', '') = $currId]"> This bibliographic entry is an orphan: no ref[@type="bibl"] references to it occur in the text.
</sch:assert></sch:rule>ExampleBlain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)ExampleThe Interesting story of the Children in the Wood. In
Victor E Neuberg, The Penny Histories.
OUP1968. ExampleCarlin
(Claire),
The Staging of Impotence : France’s last
congrès dans
Theatrum mundi : studies in honor of Ronald W.
Tobin, éd.
ClaireCarlin et
KathleenWine,
Charlottesville, Va.,
Rookwood Press,
2003.
NoteContains phrase-level elements, together with any combination of elements from the biblPart class
<biblScope><biblScope>@unit
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume.
Member ofmodel.imprintPartContained bycore: biblseriesheader: seriesStmtMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element biblScope
{
att.global.attributes,
attribute unit { text }?,
macro.phraseSeq
}Examplepp 12–34II12NoteWhen a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute should be used without to. For example, if the citation has p. 3ff as a page reference.
<body><body>
<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bytextstructure: textMay containcore: biblcitdescgapheadlabellblistlistBiblnotepqquotefigures: figuretablenamesdates: listPersontagdocs: egegXMLtextstructure: divDeclaration
element body
{
att.global.attributes,
(
( model.divTop | model.global )*,
(
(
( ( ( model.divLike | model.divGenLike ), model.global* )+ )
| (
( ( model.common ), model.global* )+,
( ( model.divLike | model.divGenLike ), model.global* )*
)
),
( ( model.divBottom ), model.global* )*
)?
)
}Schematron
<sch:rule context="tei:body[child::tei:div[not(@type=('editorialIntroduction'))]]">
<sch:assert test="count(child::tei:div) gt 1"> If <sch:name/> contains a div, and that div is not an editorial introduction, then there should be
more than one div. Rather than using only a single div, you may place the content directly
in the <sch:name/> element.
</sch:assert></sch:rule>
<catRef/><catRef>@scheme
<catRef/> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.pointing (@target)
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a taxonomy element, or by some other resource.
StatusOptionalDatatypedata.pointer
Contained byheader: textClassMay containEmpty elementDeclaration
element catRef
{
att.global.attributes,
att.pointing.attributes,
attribute scheme { data.pointer }?,
empty
}ExampleNewspapersProvincialLow to average annual salesNoteThe scheme attribute need be supplied only if more than one taxonomy has been declared.
<cell><cell>
<cell> contains one cell of a table. [14.1.1. TEI Tables]ModulefiguresAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (@role, @rows, @cols)Contained byfigures: rowMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element cell
{
att.global.attributes,
att.tableDecoration.attributes,
macro.specialPara
}ExampleGeneral conductNot satisfactory, on account of his great unpunctuality
and inattention to duties
<change><change>@target
<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description2.4.1. Creation11.7. Changes]ModuleheaderAttributesAttributes att.ascribed (@who)att.datable (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.typed (@type)
targetpoints to one or more elements that belong to this change.
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespace
Contained byheader: listChangerevisionDescMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element change
{
att.ascribed.attributes,
att.datable.attributes,
att.global.attributes,
att.typed.attributes,
attribute target { list { data.pointer+ } }?,
macro.specialPara
}Example ... Lou Burnardcopy editingBrett ZamirFinished chapter 23Finished chapter 2Added examples to section 3Deleted chapter 10ExampleFirst draft in pencilFirst revision, mostly
using green inkFinal corrections as
supplied to printer.NoteThe who attribute may be used to point to any other element, but will typically specify a respStmt or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.
<cit><cit>
<cit> (cited block quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In jTEI, this is used only for block quotations, and it will be rendered as a block. For inline quotations, use the <quote> element and link it to a reference using source. [3.3.3. Quotation4.3.1. Grouped Texts9.3.5.1. Examples]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.quoteLikeContained bycore: descemphheadhiitemnotepqquotereftitlefigures: cellheader: changerenditiontextstructure: bodydivtranscr: suppliedMay containcore: bibllistBiblptrquoterefDeclaration
element cit
{
att.global.attributes,
( quote | model.biblLike | model.ptrLike )+
}Schematron
<sch:rule context="tei:cit" role="warning">
<sch:assert test="tei:ref">
<sch:name/> is normally expected to have a bibliographic reference (ref[@type="bibl"]). Please make sure you intended not to add one here.
</sch:assert></sch:rule>Exampleand the breath of the whale is frequently attended with such an insupportable smell,
as to bring on disorder of the brain.Ulloa's South AmericaExampleto horrifyelle était horrifiée par la dépenseshe was horrified at the expense.
<classCode><classCode>@scheme
<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
schemeidentifies the classification system in use, as defined by for example by a taxonomy element, or some other resource.
<code> contains literal code from some formal language such as a programming language. [22.1.1. Phrase Level Terms]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
lang(formal language) a name identifying the formal language in which the code is expressed
StatusOptionalDatatypedata.word
Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element code { att.global.attributes, attribute lang { data.word }?, text }Example
Size fCheckbox1Size = new Size();
fCheckbox1Size.Height = 500;
fCheckbox1Size.Width = 500;
xCheckbox1.setSize(fCheckbox1Size);
<date><date>
<date> contains a date in any format. [3.5.4. Dates and Times2.2.4. Publication, Distribution, Licensing, etc.2.6. The Revision Description3.11.2.4. Imprint, Size of a Document, and Reprint Information15.2.3. The Setting Description13.3.6. Dates and Times]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.datable (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (att.dimensions) (att.source (@source)) Member ofmodel.dateLikemodel.publicationStmtPart.detailContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagepublicationStmtrenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element date
{
att.global.attributes,
att.datable.attributes,
att.editLike.attributes,
( text | model.gLike | model.phrase | model.global )*
}Exampleearly February 1980ExampleGiven on the Twelfth Day
of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
the Two Hundredth and first and of the University the Eighty-Sixth.ExampleSeptember 1990
<desc><desc>
<desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.1. Description of Components]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.descLikemodel.labelLikeContained bycore: descemphgapgraphicheadhiitemnotepqquotereftitlefigures: cellheader: applicationchangerenditiontextstructure: bodydivtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeignhilabellistlistBiblmentionednamenumptrqquoterefsoCalledtermtitlefigures: tableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvalDeclaration
element desc { att.global.attributes, macro.limitedContent }Examplecontains a brief description of the purpose and application for an element, attribute,
attribute value, class, or entity.NoteTEI convention requires that this be expressed as a finite clause, begining with an active verb.
<div><div>@type
<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.divLike
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedLegal values are:(Abstract for the article, appearing inside <front>.) Every article must include an abstract, consisting of one or two paragraphs. This appears in the <front> element and may not appear anywhere else.(Acknowledgements for the article, appearing inside <front>.) If an article includes a section for acknowledgements (for funders, supporters, etc.), it should be as brief as possible, and must appear in the <front> element and nowhere else.(Appendix to the article, appearing inside <back>.) Any appendices must appear in the <back> of the article, following the bibliography.(Bibliography, appearing inside <back>.) Every article must include a bibliography, which appears as the first component of the <back> element, followed by any appendices.(Editorial introduction, appearing inside <body>.) An editorial introduction to an issue must contain a <div type="editorialIntroduction">, which must appear in the <body> element and may not appear anywhere else.
Member ofmodel.divLikeContained bytextstructure: backbodydivfrontMay containcore: biblcitdescgapheadlabellblistlistBiblnotepqquotefigures: figuretablenamesdates: listPersontagdocs: egegXMLtextstructure: divDeclaration
element div
{
att.global.attributes,
att.divLike.attributes,
attribute type { text }?,
(
( model.divTop | model.global )*,
(
(
( ( ( model.divLike | model.divGenLike ), model.global* )+ )
| (
( ( model.common ), model.global* )+,
( ( model.divLike | model.divGenLike ), model.global* )*
)
),
( ( model.divBottom ), model.global* )*
)?
)
}Schematron
<sch:rule context="tei:div[@type = ('abstract', 'acknowledgements')]">
<sch:assert test="parent::tei:front"> Abstracts (<sch:name/>[@type="abstract"]) and acknowledgements (<sch:name/>[@type="acknowledgements"]) may only occur inside front.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:front/tei:div">
<sch:assert test="@type=('abstract', 'acknowledgements')"> Only abstracts (div[@type="abstract"]) and acknowledgements (div[@type="acknowledgements"]) may appear in the <front>.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:div[@type = ('bibliography', 'appendix')]">
<sch:assert test="parent::tei:back"> Bibliography (<sch:name/>[@type="bibliography"]) and appendices (<sch:name/>[@type="appendix"]) may only occur inside back.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:div[@type = ('editorialIntroduction')]">
<sch:assert test="parent::tei:body"> An editorial introduction (<sch:name/>[@type="editorialIntroduction"]) may only occur inside body.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:div[not(@type = ('editorialIntroduction', 'bibliography', 'abstract',
'acknowledgements'))]">
<sch:assert test="tei:head"> A <sch:name/> must contain a head.
</sch:assert></sch:rule>Schematron
<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div.
</s:report>Schematron
<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div.
</s:report>Example
Fallacies of Authority
The subject of which is Authority in various shapes, and the object, to repress all
exercise of the reasoning faculty.
The Nature of Authority
With reference to any proposed measures having for their object the greatest
happiness of the greatest number....
Analysis of Authority
What on any given occasion is the legitimate weight or influence to be attached to
authority ...
Appeal to Authority, in What Cases Fallacious.
Reference to authority is open to the charge of fallacy when...
<edition><edition>
<edition> describes the particularities of one edition of a text. [2.2.2. The Edition Statement]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.biblPartContained bycore: biblMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element edition { att.global.attributes, macro.phraseSeq }ExampleFirst edition Oct 1990Students' edition
<editor><editor>@role
<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. Titles, Authors, and Editors]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Derived fromatt.namingStatusOptionalDatatype 1–∞ occurrences ofdata.enumeratedseparated by whitespaceLegal values are:
Member ofmodel.respLikeContained bycore: biblseriesheader: seriesStmtMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element editor
{
att.global.attributes,
attribute role { list { + } }?,
macro.phraseSeq
}ExampleEric JohnsonJohn TennielNoteA consistent format should be adopted.Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.
<eg><eg>
<eg> (example) contains any kind of illustrative example. [22.4.4. Element Specifications22.4.5. Attribute List Specification]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.egLikeContained bycore: descemphheadhiitemnotepqquotereftitlefigures: cellfigureheader: changerenditiontextstructure: bodydivtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element eg { att.global.attributes, macro.phraseSeq }Example
The
term element is declared using the following syntax:
<![CDATA[<!ELEMENT term (%phrase.content;)>]]
NoteIf the example contains material in XML markup, either it must be enclosed within a CDATA marked section, or character entity references must be used to represent the markup delimiters. If the example contains well-formed XML, it should be marked using the more specific <egXML> element.
<egXML><egXML>@valid
<egXML> (example of XML) contains a single well-formed XML fragment demonstrating the use of some XML element or attribute, in which the <egXML> element itself functions as the root element. [22.1.1. Phrase Level Terms]Namespacehttp://www.tei-c.org/ns/ExamplesModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.source (@source)
validindicates the intended validity of the example with respect to a schema.
StatusOptionalDatatypedata.enumeratedLegal values are:the example is intended to be fully valid, assuming that its root element, or a provided root element, could have been used as a possible root element in the schema concerned. [Default]the example could be transformed into a valid document by inserting any number of valid attributes and child elements anywhere within it; or it is valid against a version of the schema concerned in which the provision of character data, list, element, or attribute values has been made optional.the example is not intended to be valid, and contains deliberate errors.
Member ofmodel.egLikeContained bycore: descemphheadhiitemnotepqquotereftitlefigures: cellfigureheader: changerenditiontextstructure: bodydivtranscr: suppliedMay containANYDeclaration
element egXML
{
att.global.attributes,
att.source.attributes,
attribute valid { text }?,
( text | macro.anyXML )*
}Example
A slide about egXMLegXML can be used to give XML examples in the TEI
Examples namespaceAttributes values for valid:
true: intended to be fully
validfeasible: valid if missing nodes
providedfalse: not intended to be validThe rend attribute in the TEI namespace can be
used for recording how parts of the example was rendered.
ExampleExample
<egXML xmlns="http://www.tei-c.org/ns/Examples" valid="false">
<para xml:lang="en">Doubloons are a pirate's best friend</para>
</egXML>
NoteIn the source of the TEI Guidelines, this element declares itself and its content as belonging to the namespace http://www.tei-c.org/ns/Examples. This enables the content of the element to be validated independently against the TEI scheme. Where this element is used outside this context, a different namespace or none at all may be preferable. The content must however be a well-formed XML fragment or document: where this is not the case, the more general <eg> element should be used in preference. In a TEI context use of the rend attribute in the TEI namespace, as opposed to the TEI Examples namespace, enables recording of rendition information.
<email><email>
<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.5.2. Addresses]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.addressLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element email { att.global.attributes, macro.phraseSeq }Examplemembership@tei-c.orgNoteThe format of a modern Internet email address is defined in RFC 2822
<emph><emph>
<emph> (Emphasis (italicization)) The <emph> element is used for emphasized text, and will be rendered in italics. [3.3.2.2. Emphatic Words and Phrases3.3.2. Emphasis, Foreign Words, and Unusual Language]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element emph { att.global.attributes, macro.paraContent }ExampleYou took the car and did what?!!ExampleWhat it all comes to is this, he said. What
does Christopher Robin do in the morning nowadays?
<encodingDesc><encodingDesc>
<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description2.1.1. The TEI Header and Its Components]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.teiHeaderPartContained byheader: teiHeaderMay containcore: pheader: appInfoprojectDesctagsDeclDeclaration
element encodingDesc
{
att.global.attributes,
( ( model.encodingDescPart | model.pLike )+ )
}Example
Basic encoding, capturing lexical information only. All
hyphenation, punctuation, and variant spellings normalized. No
formatting or layout information preserved.
<figure><figure>
<figure> (figure) groups elements representing or containing graphic information such as a graphic illustration, or a block of example code. Figure must contain either <graphic>, <egXML> (for example XML code) or <eg> (for non-XML code), and a mandatory <head> element containing the caption for the figure. Inline code examples may be provided through <egXML> and <eg> without the <figure> wrapper. [14.4. Specific Elements for Graphic Images]ModulefiguresAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.globalContained bycore: abbrauthorbiblbiblScopedateeditoremailemphforeignheadhiitemlabellistmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: celltableheader: changeclassCodeeditionlanguagenamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtextstructure: backbodydivfronttexttranscr: suppliedMay containcore: graphicheadtagdocs: egegXMLDeclaration
element figure { att.global.attributes, ( graphic | egXML | eg ), head+ }ExampleThe View from the BridgeUsed with permissionExampleif ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
goto fail;
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
goto fail;
goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
goto fail;
An embarrassing error for AppleExample
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<list rend="bulleted">
<item>Life</item>
<item>The Universe</item>
<item>Everything</item>
</list>
</egXML>
A book title rendered as a list
<fileDesc><fileDesc>
<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description2.1.1. The TEI Header and Its Components]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: teiHeaderMay containheader: publicationStmtseriesStmtsourceDesctitleStmtDeclaration
element fileDesc
{
att.global.attributes,
(
(
titleStmt,
editionStmt?,
extent?,
publicationStmt,
seriesStmt?,
notesStmt?
),
sourceDesc+
)
}ExampleThe shortest possible TEI document
Distributed as part of TEI P5
No print source exists: this is an original digital text
NoteThe major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.
<foreign><foreign>
<foreign> identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element foreign { att.global.attributes, macro.phraseSeq }ExampleThis is
heathen Greek to you still? Your lapis
philosophicus?NoteThe global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.The distinct element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.
<forename><forename>
<forename> contains a forename, given or baptismal name. [13.2.1. Personal Names]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.persNamePartContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element forename { att.global.attributes, macro.phraseSeq }ExampleEx-PresidentGeorgeBush
<front><front>
<front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages4. Default Text Structure]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bytextstructure: textMay containcore: gapheadlbnotepfigures: figuretextstructure: divDeclaration
element front
{
att.global.attributes,
(
( ( model.frontPart | model.pLike | model.pLike.front | model.global )* ),
(
(
(
model.div1Like,
( model.div1Like | model.frontPart | model.global )*
)
| (
model.divLike,
( model.divLike | model.frontPart | model.global )*
)
),
( ( ( model.divBottom ), ( model.divBottom | model.global )* )? )
)?
)
}Schematron
<sch:rule context="tei:front">
<sch:assert test="tei:div[@type='abstract']">
<sch:name/> must have an abstract (div[@type='abstract']).
</sch:assert></sch:rule>ExampleNam Sibyllam quidem Cumis ego ipse oculis meis
vidi in ampulla pendere, et cum illi pueri dicerent:
Σίβυλλα τί θέλεις; respondebat
illa: ὰποθανεῖν θέλω.
For Ezra Pound il miglior fabbro.
Example
To our three selves
Author's Note
All the characters in this book are purely imaginary, and if the
author has used names that may suggest a reference to living persons
she has done so inadvertently.
...
NoteBecause cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.
<gap><gap>@reason@hand@agent
<gap> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source))
reasongives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
StatusOptionalDatatype 1–∞ occurrences ofdata.wordseparated by whitespace
handin the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, indicates the hand which made the deletion.
StatusOptionalDatatypedata.pointer
agentin the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptionalDatatypedata.enumeratedSample values include:damage results from rubbing of the leaf edgesdamage results from mildew on the leaf surfacedamage results from smoke
Member ofmodel.global.editContained bycore: abbrauthorbiblbiblScopedateeditoremailemphforeignheadhiitemlabellistmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: celltableheader: changeclassCodeeditionlanguagenamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtextstructure: backbodydivfronttexttranscr: suppliedMay containcore: descDeclaration
element gap
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
attribute hand { data.pointer }?,
attribute agent { data.enumerated }?,
( model.descLike | model.certLike )*
}Schematron
<sch:rule context="tei:gap-period">
<sch:report test="following-sibling::node()[1][self::text()] and starts-with(following-sibling::node()[1],
'.')"> A <sch:name/> element should follow a period rather than precede it when an ellipsis follows the end of a sentence.
</sch:report></sch:rule>Schematron
<sch:rule context="tei:gap">
<sch:report test="preceding-sibling::node()[1][self::text()][matches(., '\.\s+$')]"> A <sch:name/> should follow a period directly, without preceding whitespace.
</sch:report></sch:rule>ExampleExampleExampleExampleNoteThe <gap>, unclear, and del core tag elements may be closely allied in use with the damage and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as del in the case of deliberate deletion.
<gi><gi>@scheme
<gi> (element name) contains the name (generic identifier) of an element. [22. Documentation Elements22.4.4. Element Specifications]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
schemesupplies the name of the scheme in which this name is defined.
StatusOptionalDatatypedata.enumeratedSample values include:this element is part of the TEI scheme. [Default](docbook) this element is part of the Docbook scheme.(unknown) this element is part of an unknown scheme.this element is from Schematron.this element is from the HTML scheme.
Member ofmodel.phrase.xmlContained bycore: abbrauthorbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element gi
{
att.global.attributes,
attribute scheme { data.enumerated }?,
data.name
}Example
The xhtml:li element is roughly analogous to the item element, as is the
listItem element.
This example shows the use of both a namespace prefix and the schema attribute as alternative ways of indicating that the gi in question is not a TEI element name: in practice only one method should be adopted.
<graphic><graphic>
<graphic> indicates the location of an inline graphic, illustration, or figure. [3.9. Graphics and Other Non-textual Components]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.media (@width, @height)att.resourced (@url)Member ofmodel.graphicLikeContained bycore: abbrauthorbiblScopedateeditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellfiguretableheader: changeeditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: descDeclaration
element graphic
{
att.global.attributes,
att.media.attributes,
att.resourced.attributes,
model.descLike*
}Schematron
<sch:rule context="tei:graphic">
<sch:assert test="matches(@width, '\d+px') and matches(@height, '\d+px')"> Width and height in pixels must be specified for any <sch:name/>.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:graphic">
<sch:assert test="parent::tei:figure">
<sch:name/> may only occur inside figure.
</sch:assert></sch:rule>ExampleFigure One: The View from the BridgeA Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.NoteThe mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.
<head><head>@type
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
typeindicates the type of heading. In jTEI, we only use this attribute in the context of a <head> element in <figure>, where it must have one of two values.
Member ofmodel.headLikemodel.pLike.frontContained bycore: listlistBiblfigures: figuretablenamesdates: listPersontextstructure: backbodydivfrontMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element head
{
att.global.attributes,
attribute type { data.enumerated }?,
(
text
| lg
| model.gLike
| model.phrase
| model.inter
| model.lLike
| model.global
)*
}Schematron
<sch:rule context="tei:head">
<sch:report test="matches(., '^\s*((figure|table|example|section) )?\d', 'i')"> Headings are numbered and labeled automatically, please remove the hard-coded label from the text.
</sch:report></sch:rule>Schematron
<sch:rule context="tei:figure/tei:head">
<sch:assert test="@type = ('legend', 'license')"> Figure titles must have a type 'legend' or 'license'.
</sch:assert></sch:rule>ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a trailer, as in this example:In the name of Christ here begins the first book of the ecclesiastical history of
Georgius Florentinus, known as Gregory, Bishop of Tours.In the name of Christ here begins Book I of the history.
Proposing as I do ...
From the Passion of our Lord until the death of Saint Martin four hundred and twelve
years passed.
Here ends the first Book, which covers five thousand, five hundred and ninety-six
years from the beginning of the world down to the death of Saint Martin.ExampleThe <head> element is also used to mark headings of other units, such as lists:With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. Connectivesaboveaccordinglyacross fromadjacent toagainNoteThe <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a div1 is the title of that chapter or section.
<hi><hi>
<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases3.3.2. Emphasis, Foreign Words, and Unusual Language]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.hiLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element hi { att.global.attributes, macro.paraContent }ExampleAnd this Indenture further witnesseth
that the said Walter Shandy, merchant,
in consideration of the said intended marriage ...
<ident><ident>
<ident> (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. Phrase Level Terms]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element ident { att.global.attributes, text }Examplehttp://www.tei-c.org/ns/ExamplesNoteIn running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements <gi> and <att> are provided.
<idno><idno>@type
<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc.2.2.5. The Series Statement3.11.2.4. Imprint, Size of a Document, and Reprint Information]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
StatusOptionalDatatypedata.enumerated
Member ofmodel.nameLikemodel.personPartmodel.publicationStmtPart.detailContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: cellheader: changeclassCodeeditionidnolanguagepublicationStmtrenditionseriesStmtnamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtranscr: suppliedMay containheader: idnoDeclaration
element idno
{
att.global.attributes,
attribute type { data.enumerated }?,
( text | model.gLike | idno )*
}Schematron
<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:idno[@type eq 'doi']">
<sch:report test="following-sibling::tei:ref"> If a bibliographic entry has a formal DOI code, it should be placed at the very end of the bibliographic description.
</sch:report></sch:rule>Example978-1-906964-22-10143-338510.1000/123http://www.worldcat.org/oclc/185922478http://authority.nzetc.org/463/Thomason Tract E.537(17)C695345In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a glyph or char element referenced here as #sym.Note<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.
<item><item>
<item> contains one component of a list. [3.7. Lists2.6. The Revision Description]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bycore: listMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element item { att.global.attributes, macro.specialPara }ExampleHere begin the chapter headings of Book IVThe death of Queen Clotild.How King Lothar wanted to appropriate one third of the Church revenues.The wives and children of Lothar.The Counts of the Bretons.Saint Gall the Bishop.The priest Cato. ...NoteMay contain simple prose or a sequence of chunks.Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.
<keywords><keywords>@scheme
<keywords> contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined identifies the classification scheme within which the set of categories concerned is defined, for example by a taxonomy element, or by some other resource.
StatusOptionalDatatypedata.pointer
Contained byheader: textClassMay containcore: listtermDeclaration
element keywords
{
att.global.attributes,
attribute scheme { data.pointer }?,
( term+ | list )
}ExampleBabbage, CharlesMathematicians - Great Britain - BiographyExampleFermented beveragesCentral AndesSchinus molleMolle beerIndigenous peoplesEthnographyArchaeologyNoteEach individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within a <item> inside a <list> is permitted for backwards compatibility, but is deprecated.If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.
<label><label>
<label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.labelLikeContained bycore: descemphheadhiitemlistnotepqquotereftitlefigures: cellheader: applicationchangerenditiontextstructure: bodydivtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element label { att.global.attributes, macro.phraseSeq }ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:VocabularyMiddle EnglishNew Englishnowloudlybloomsmeadowwoodewelowsbounds, frisks (cf. Chaucer, K.T.644a courser, stertingas the fyrpeditmerrilyceaseneverExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. My first rough manuscript, without any intermediate copy, has been sent to the press.Not a sheet has been seen by any human eyes, excepting those of the author and the
printer: the faults and the merits are exclusively my own.ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:I wrote some critical observations upon Plautus.I wrote a long dissertation upon some lines of Virgil.I saw Mademoiselle Curchod — Omnia vincit amor, et nos cedamus
amori.I went to Crassy, and staid two days.Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or lg element, rather than as a preceding sibling of it.
[...]
& n’entrer en mauuais & mal-heu-
ré meſnage. Or des que le conſente-
ment des parties y eſt le mariage eſt
arreſté, quoy que de faict il ne ſoit
conſommé. Depuis la conſomma-
tion du mariage la femme eſt ſoubs
la puiſſance du mary, s’il n’eſt eſcla-
ue ou enfant de famille : car en ce
cas, la femme, qui a eſpouſé vn en-
fant de famille, eſt ſous la puiſſance
[...]
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
<langUsage><langUsage>
<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage2.4. The Profile Description15.3.2. Declarable Elements]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.profileDescPartContained byheader: profileDescMay containheader: languageDeclaration
element langUsage { att.global.attributes, language+ }ExampleQuébecoisCanadian business EnglishBritish English
<language><language>@ident
<language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
StatusRequiredDatatypedata.language
Contained byheader: langUsageMay containcore: abbrdateemailemphforeigngaphilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvalDeclaration
element language
{
att.global.attributes,
attribute ident { data.language },
macro.phraseSeq.limited
}Examplemodern American EnglishAzerbaijani in Arabic scriptPig LatinNoteParticularly for sublanguages, an informal prose characterization should be supplied as content for the element.
<lb/><lb>
<lb/> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone
Elements7.2.5. Speech Contents]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.milestoneLikeContained bycore: abbrauthorbiblbiblScopedateeditoremailemphforeignheadhiitemlabellistlistBiblmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: celltableheader: changeclassCodeeditionlanguagenamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtextstructure: backbodydivfronttexttranscr: suppliedMay containEmpty elementDeclaration
element lb { att.global.attributes, empty }ExampleThis example shows typographical line breaks within metrical lines, where they occur at different places in different editions:Of Mans First Disobedience, and the FruitOf that Forbidden Tree, whose mortal tastBrought Death into the World, and all our woe,ExampleThis example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.With Additions, ne-ver before Printed.NoteBy convention, <lb/> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb/> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked.The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.
<list><list>@rend@type
<list> contains any sequence of items organized as a list. [3.7. Lists]ModulecoreAttributesAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (rend, @rendition) att.global.responsibility (@cert, @resp)
rend(rendition) describes the way the list should be rendered.
Derived fromatt.global.renditionStatusOptionalDatatype 1–∞ occurrences ofdata.enumeratedseparated by whitespaceLegal values are:(A bulleted list) Bulleted lists will appear with each item preceded by a leading dot.(An inline list) Inline lists appear within a paragraph of ordinary text; list items do not start on a new line, but follow immediately from the preceding text or item. The value "inline" may be combined with another value; for example, "ordered inline" means that the list will be rendered inline, but each item will be preceded by a number in parentheses: (1) first item (2) second item, and so on.(A numbered list) Items in a numbered list will be preceded by a number. If the list is inline, then the number will be enclosed in parentheses, but if it is a block-level list (the default), the number will be followed by a period. (A simple list (no bullets or numbers)) Items in a simple list will be rendered with no bullet or preceding number at all.
typedescribes the nature of the items in the list.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedLegal values are:NotePrevious versions of these Guidelines recommended the use of type on <list> to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.NoteThe formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.
Member ofmodel.listLikeContained bycore: descemphheadhiitemnotepqquotereftitlefigures: cellheader: changekeywordsrenditionrevisionDescsourceDesctextstructure: backbodydivtranscr: suppliedMay containcore: gapheaditemlabellbnotefigures: figureDeclaration
element list
{
att.global.attribute.xmlid,
att.global.attribute.n,
att.global.attribute.xmllang,
att.global.attribute.xmlbase,
att.global.attribute.xmlspace,
att.global.rendition.attribute.rendition,
att.global.responsibility.attribute.cert,
att.global.responsibility.attribute.resp,
attribute rend { list { + } }?,
attribute type { text }?,
(
( ( model.divTop ) | ( model.global ) )*,
(
( item, model.global* )+
| (
headLabel?,
headItem?,
( label, model.global*, item, model.global* )+
)
),
( ( model.divBottom ), model.global* )*
)
}Schematron
<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert></sch:rule>NoteMay contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.
<listBibl><listBibl>
<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.11.1. Methods of Encoding Bibliographic References and Lists of References2.2.7. The Source Description15.3.2. Declarable Elements]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.biblLikeContained bycore: citdescemphheadhiitemlistBiblnotepqquotereftitlefigures: cellheader: changerenditionsourceDescnamesdates: persontextstructure: bodydivtranscr: suppliedMay containcore: biblheadlblistBiblDeclaration
element listBibl
{
att.global.attributes,
(
model.headLike*,
( model.biblLike | model.milestoneLike )+,
( relation | listRelation )*
)
}ExampleWorks consultedBlain, Clements and Grundy: Feminist Companion to
Literature in English (Yale, 1990)
The Interesting story of the Children in the WoodThe Penny HistoriesVictor E NeubergOUP1968
<listChange><listChange>@ordered
<listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description11.7. Changes]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
orderedindicates whether the ordering of its child <change> elements is to be considered significant or not
StatusOptionalDatatypedata.truthValueDefaulttrue
Contained byheader: listChangerevisionDescMay containheader: changelistChangeDeclaration
element listChange
{
att.global.attributes,
attribute ordered { data.truthValue }?,
( listChange | change )+
}Example deleted chapter 10 completed first draft ExampleFirst stage, written in ink by a writerSecond stage, written in Goethe's hand using pencilFixation of the revised passages and further revisions by
Goethe using inkAddition of another stanza in a different hand,
probably at a later stageNoteWhen this element appears within the creation element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text.
<listPerson><listPerson>
<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element15.2. Contextual Information2.4. The Profile Description15.3.2. Declarable Elements]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.typed (@type)Member ofmodel.listLikeContained bycore: descemphheadhiitemnotepqquotereftitlecorpus: particDescfigures: cellheader: changerenditionsourceDescnamesdates: listPersontextstructure: backbodydivtranscr: suppliedMay containcore: headnamesdates: listPersonpersonDeclaration
element listPerson
{
att.global.attributes,
att.typed.attributes,
(
model.headLike*,
( model.personLike | listPerson )+,
( relation | listRelation )*
)
}ExampleNoteThe type attribute may be used to distinguish lists of people of a particular type if convenient.
<mentioned><mentioned>
<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element mentioned { att.global.attributes, macro.phraseSeq }ExampleThere is thus a
striking accentual difference between a verbal form like eluthemenwe were released, accented on the second syllable of the
word, and its participial derivative lutheisreleased, accented on the last.
<name><name>
<name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source)) att.datable.w3c (notAfter, @when, @notBefore, @from, @to) Member ofmodel.nameLike.agentContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element name
{
att.global.attributes,
att.datable.w3c.attribute.when,
att.datable.w3c.attribute.notBefore,
att.datable.w3c.attribute.from,
att.datable.w3c.attribute.to,
att.editLike.attributes,
macro.phraseSeq
}ExampleThomas HoccleveVillingaholtVetus Latina InstitutOccleveNoteProper nouns referring to people, places, and organizations may be tagged instead with persName, placeName, or <orgName>, when the TEI module for names and dates is included.
<note><note>
<note> contains a note or annotation. [3.8.1. Notes and Simple Annotation2.2.6. The Notes Statement3.11.2.8. Notes and Statement of Language9.3.5.4. Notes within Entries]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.source (@source)Member ofmodel.noteLikeContained bycore: abbrauthorbiblbiblScopedateeditoremailemphforeignheadhiitemlabellistmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: celltableheader: changeclassCodeeditionlanguagenamesdates: affiliationforenameorgNamepersonroleNamesurnametagdocs: egtextstructure: backbodydivfronttexttranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element note
{
att.global.attributes,
att.source.attributes,
macro.specialPara
}Schematron
<sch:rule context="tei:note">
<sch:assert test="not(following-sibling::text()[1][matches(., '^[,\.:;!?)\]]')])"> Footnotes should follow punctuation marks, not precede them. Place
your <note> element after the punctuation mark.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:note">
<sch:report test=".//(tei:cit|tei:table|tei:list[not(tokenize(@rend, '\s+')[. eq 'inline'])]|tei:figure|eg:egXML|tei:eg)"> No block-level elements are allowed inside note.
</sch:report></sch:rule>ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly Malerisch. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
picturesque and
painterly respectively. style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance. For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header:translation from German to EnglishHottinger, Marie Donald MackieExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. is well known from Geniza documents
published by Jacob Mann.However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
<num><num>@type@value
<num> (number) contains a number, written in any form. [3.5.3. Numbers and
Measures]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
typeindicates the type of numeric value. In jTEI, we particularly use num[@type='ordinal'] for e.g. 21st or 2nd; in rendering, this results in the non-numeric suffix to the number being output as superscript. Note, however, that ordinals for centuries should be spelled out, not written using digits (nineteenth century, not 19th century).
StatusOptionalDatatypedata.enumeratedSuggested values include:absolute number, e.g. 21, 21.5ordinal number, e.g. 21stfraction, e.g. one half or three-quartersa percentageNoteIf a different typology is desired, other values can be used for this attribute.
valuesupplies the value of the number in standard form.
StatusOptionalDatatypedata.numericValuesa numeric value.NoteThe standard form used is defined by the TEI datatype data.numeric.
Member ofmodel.measureLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element num
{
att.global.attributes,
attribute type
{
"cardinal" | "ordinal" | "fraction" | "percentage" | xsd:Name
}?,
attribute value { data.numeric }?,
macro.phraseSeq
}Example
I reached twenty-one on
my twenty-first birthday
Light travels at 3×1010 cm per second.
NoteDetailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The <num> element is intended for use in simple applications.
<orgName><orgName>
<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source)) att.datable.w3c (notAfter, @when, @notBefore, @from, @to) Member ofmodel.nameLike.agentContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element orgName
{
att.global.attributes,
att.datable.w3c.attribute.when,
att.datable.w3c.attribute.notBefore,
att.datable.w3c.attribute.from,
att.datable.w3c.attribute.to,
att.editLike.attributes,
macro.phraseSeq
}ExampleAbout a year back, a question of considerable interest was agitated in the Pennsyla. Abolition Society....
<p><p>
<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs7.2.5. Speech Contents]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.pLikeContained bycore: itemnoteqquotecorpus: particDescfigures: cellheader: applicationavailabilitychangeencodingDescprojectDescpublicationStmtseriesStmtsourceDescnamesdates: persontextstructure: backbodydivfrontMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element p { att.global.attributes, macro.paraContent }Schematron
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum
|parent::tei:item |parent::tei:note
|parent::tei:q |parent::tei:quote
|parent::tei:remarks |parent::tei:said
|parent::tei:sp |parent::tei:stage
|parent::tei:cell |parent::tei:figure)"> Abstract model violation: Paragraphs may not contain other paragraphs or ab elements.
</s:report>Schematron
<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab.
</s:report>Example
Hallgerd was outside. There is blood on your axe, she said. What have you
done?
I have now arranged that you can be married a second time, replied Thjostolf.
Then you must mean that Thorvald is dead, she said.
Yes, said Thjostolf. And now you must think up some plan for me.
<particDesc><particDesc>
<particDesc> (participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata. [15.2. Contextual Information]ModulecorpusAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.profileDescPartContained byheader: profileDescMay containcore: pnamesdates: listPersonpersonDeclaration
element particDesc
{
att.global.attributes,
( model.pLike+ | ( model.personLike | listPerson | listOrg )+ )
}Example
Female informant, well-educated, born in
Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently.
Socio-Economic status B2.
HancockAntonyAloysiusSt JohnRailway CuttingsEast CheamcomedianThis example shows both a very simple person description, and a very detailed one, using some of the more specialized elements from the module for Names and Dates. NoteMay contain a prose description organized as paragraphs, or a structured list of persons and person groups, with an optional formal specification of any relationships amongst them.
<person><person>@role@sex@age
<person> provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element15.2.2. The Participant Description]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source))
rolespecifies a primary role or classification for the person.
StatusOptionalDatatype 1–∞ occurrences ofdata.enumeratedseparated by whitespaceNoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema specification.
sexspecifies the sex of the person.
StatusOptionalDatatype 1–∞ occurrences ofdata.sexseparated by whitespaceNoteValues for this attribute may be locally defined by a project, or may refer to an external standard, such as vCard's sex property (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People.
agespecifies an age group for the person.
StatusOptionalDatatypedata.enumeratedNoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a valList element in the project schema specification.
Member ofmodel.personLikeContained bycorpus: particDescnamesdates: listPersonMay containcore: biblgaplblistBiblnotepfigures: figureheader: idnonamesdates: affiliationDeclaration
element person
{
att.global.attributes,
att.editLike.attributes,
attribute role { list { data.enumerated+ } }?,
attribute sex { list { data.sex+ } }?,
attribute age { data.enumerated }?,
( model.pLike+ | ( model.personPart | model.global )* )
}Example
Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
status B2.
ExampleHermaphroditosἙρμαφρόδιτοςExampleOvidPublius Ovidius Naso 20 March 43 BC SulmonaItaly17 or 18 AD Tomis (Constanta)RomaniaNoteMay contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.
<profileDesc><profileDesc>
<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description2.1.1. The TEI Header and Its Components]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.teiHeaderPartContained byheader: teiHeaderMay containcorpus: particDescheader: langUsagetextClassDeclaration
element profileDesc { att.global.attributes, ( model.profileDescPart* ) }ExampleFrenchprint; part issuesParis, FranceNoteAlthough the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.In earlier versions of these Guidelines, it was required that the creation element appear first.
<projectDesc><projectDesc>
<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description2.3. The Encoding Description15.3.2. Declarable Elements]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.encodingDescPartContained byheader: encodingDescMay containcore: pDeclaration
element projectDesc { att.global.attributes, model.pLike+ }Example
Texts collected for use in the Claremont Shakespeare Clinic, June 1990
<ptr/><ptr>@target@type
<ptr/> (pointer) defines a pointer to another location. [3.6. Simple Links and Cross-References16.1. Links]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
targetspecifies the destination of the reference by supplying one or more URI References
Derived fromatt.pointingStatusRequiredDatatype 1–∞ occurrences ofdata.pointerseparated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedLegal values are:(A cross-reference (reference to another part of the article).) To link to another part of your article, use <ptr type="crossref">, and point to the xml:id value of the target location: <ptr type="crossref" target="#intro">. The <ptr/> element will be expanded to create an appropriate link to the target location.
Member ofmodel.ptrLikeContained bycore: abbrauthorbiblbiblScopecitdatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: cellheader: applicationchangeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containEmpty elementDeclaration
element ptr
{
att.global.attributes,
attribute target { list { data.pointer+ } },
attribute type { text }?,
empty
}Schematron
<sch:rule context="tei:ptr[not(@type='crossref')]">
<sch:report test="count(tokenize(normalize-space(@target), '\s+')) > 1"> Multiple targets are only allowed for <sch:name/>[@type='crossref'].
</sch:report></sch:rule>Schematron
<s:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on <s:name/>.</s:report>Example
<pubPlace><pubPlace>
<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.imprintPartmodel.publicationStmtPart.detailContained bycore: biblheader: publicationStmtMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element pubPlace { att.global.attributes, macro.phraseSeq }ExampleOxford University PressOxford1989
<publicationStmt><publicationStmt>
<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc.2.2. The File Description]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: fileDescMay containcore: dateppubPlacepublisherheader: availabilityidnoDeclaration
element publicationStmt
{
att.global.attributes,
(
(
( model.publicationStmtPart.agency ),
model.publicationStmtPart.detail*
)+
| model.pLike+
)
}ExampleC. Muquardt Bruxelles & LeipzigExampleChadwyck HealeyCambridge
Available under licence only
1992NoteWhere a publication statement contains several members of the model.publicationStmtPart classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.
<publisher><publisher>
<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information2.2.4. Publication, Distribution, Licensing, etc.]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.imprintPartmodel.publicationStmtPart.agencyContained bycore: biblheader: publicationStmtMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element publisher { att.global.attributes, macro.phraseSeq }ExampleOxfordClarendon Press1987NoteUse the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page
<q><q>
<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.ascribed (@who)att.source (@source)Member ofmodel.qLikeContained bycore: descemphheadhiitemnotepqquotereftitlefigures: cellheader: changerenditiontextstructure: bodydivtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element q
{
att.global.attributes,
att.ascribed.attributes,
att.source.attributes,
macro.specialPara
}ExampleIt is spelled Tübingen — to enter the
letter u with an umlaut hold down the option key and press 0 0 f cNoteMay be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.
<quote><quote>
<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation4.3.1. Grouped Texts]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.source (@source)Member ofmodel.quoteLikeContained bycore: citdescemphheadhiitemnotepqquotereftitlefigures: cellheader: changerenditiontextstructure: bodydivtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumpptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element quote
{
att.global.attributes,
att.source.attributes,
macro.specialPara
}Schematron
<sch:rule context="tei:quote">
<sch:assert test="id(substring-after(@source, '#'))/(self::tei:ref[@type eq 'bibl']|self::tei:bibl[ancestor::tei:body])">
<sch:name/> must be accompanied by a bibliographic reference (ref[@type="bibl"]) or a bibliographic description in the running text.
</sch:assert></sch:rule>ExampleLexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, You shall know a word by the company it
keeps(Firth, 1957)NoteIf a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.
<ref><ref>@target@type
<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References16.1. Links]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
targetspecifies the destination of the reference by supplying one or more URI References
Derived fromatt.pointingStatusRequiredDatatype 1–∞ occurrences ofdata.pointerseparated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedLegal values are:(A cross-reference (reference to another part of the article).) To link to another part of your article, use <ref type="crossref">, and point to the xml:id value of the target location: <ref type="crossref" target="#intro">.(A bibliographic reference (reference to an entry in the bibliography).) To link to a bibliographic description in the bibliography, use <ref type="bibl">, and point to the xml:id value of the target location: <ref type="bibl" target="#ide88">.
Member ofmodel.ptrLikeContained bycore: abbrauthorbiblbiblScopecitdatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: cellheader: applicationchangeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element ref
{
att.global.attributes,
attribute target { list { data.pointer+ } },
attribute type { text }?,
macro.paraContent
}Schematron
<sch:rule context="tei:ref">
<sch:report test="count(tokenize(normalize-space(@target), '\s+')) > 1">
<sch:name/> with multiple targets is not supported.
</sch:report></sch:rule>Schematron
<sch:rule context="tei:ref[@type eq 'bibl']">
<sch:assert test="not(matches(., '^\(.*\)$'))"> Parentheses are not part of bibliographic references. Please move them out of <sch:name/>.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:ref[@type eq 'bibl']">
<sch:assert test="id(substring-after(@target, '#'))/(self::tei:bibl|self::tei:person[ancestor::tei:particDesc/parent::tei:profileDesc])"> A bibliographic reference must point to an entry in the bibliography.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:ref[id(substring-after(@target, '#'))/self::tei:bibl]">
<sch:assert test="@type eq 'bibl'"> A bibliographic reference must be typed as @type="bibl".
</sch:assert></sch:rule>Schematron
<s:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <s:name/></s:report>ExampleSee especially the second
sentenceExampleSee also s.v. locution.NoteThe target and cRef attributes are mutually exclusive.
<rendition><rendition>@scheme@selector
<rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
schemeidentifies the language used to describe the rendition.
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptionalDatatypedata.text
display: block;
font-style: italic;
NoteSince the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.NoteWhile rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.
Contained byheader: tagsDeclMay containcore: abbrbiblcitdatedescemailemphforeignhilabellistlistBiblmentionednamenumptrqquoterefsoCalledtermtitlefigures: tableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvalDeclaration
element rendition
{
att.global.attributes,
attribute scheme { text }?,
attribute selector { data.text }?,
macro.limitedContent
}Schematron
<sch:rule context="tei:rendition">
<sch:assert test="some $i in //@rendition satisfies tokenize($i, '\s+')[replace(., '#',
'') = current()/@xml:id]"> Please remove all <sch:name/> definitions that aren't actually being used in the article.
</sch:assert></sch:rule>Exampletext-align: center;font-size: small;font-size: large;font-size: xx-largeNoteThe present release of these Guidelines does not specify the content of this element in any further detail. It may be used to hold a description of the default rendition to be associated with the specified element, expressed in running prose, or in some more formal language such as CSS.
<revisionDesc><revisionDesc>
<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description2.1.1. The TEI Header and Its Components]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: teiHeaderMay containcore: listheader: changelistChangeDeclaration
element revisionDesc
{
att.global.attributes,
( list | listChange | change+ )
}Example deleted chapter 10 NoteIf present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.
<roleName><roleName>
<roleName> contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.persNamePartContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element roleName { att.global.attributes, macro.phraseSeq }ExampleWilliamPoultenyEarl of BathNoteA <roleName> may be distinguished from an addName by virtue of the fact that, like a title, it typically exists independently of its holder.
<row><row>
<row> contains one row of a table. [14.1.1. TEI Tables]ModulefiguresAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (@role, @rows, @cols)Contained byfigures: tableMay containfigures: cellDeclaration
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }ExampleClassicsIdle listless and unimproving
<series><series>
<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.11.2.1. Analytic, Monographic, and Series Levels]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.biblPartContained bycore: biblMay containcore: biblScopeeditorgaplbnoteptrreftitlefigures: figureheader: availabilityidnoDeclaration
element series
{
att.global.attributes,
(
text
| model.gLike
| title
| model.ptrLike
| editor
| respStmt
| biblScope
| idno
| textLang
| model.global
| availability
)*
}ExampleHalbgraue Reihe zur Historischen FachinformatikHerausgegeben vonManfred ThallerMax-Planck-Institut für GeschichteSerie A: Historische QuellenkundenBand 11
<seriesStmt><seriesStmt>
<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement2.2. The File Description]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: fileDescMay containcore: biblScopeeditorptitleheader: idnoDeclaration
element seriesStmt
{
att.global.attributes,
( model.pLike+ | ( title+, ( editor | respStmt )*, ( idno | biblScope )* ) )
}ExampleMachine-Readable Texts for the Study of Indian Literatureed. byJan Gonda1.20 345 6789
<soCalled><soCalled>
<soCalled> contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element soCalled { att.global.attributes, macro.phraseSeq }ExampleTo edge his way along
the crowded paths of life, warning all human sympathy to keep its distance, was what the
knowing ones call nuts to Scrooge.
<sourceDesc><sourceDesc>
<sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: fileDescMay containcore: bibllistlistBiblpfigures: tablenamesdates: listPersonDeclaration
element sourceDesc
{
att.global.attributes,
(
model.pLike+
| ( model.biblLike | model.sourceDescPart | model.listLike )+
)
}ExampleThe Interesting story of the Children in the Wood. In
Victor E Neuberg, The Penny Histories.
OUP1968. Example
Born digital: no previous source exists.
<supplied><supplied>@reason
<supplied> signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]ModuletranscrAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) att.editLike (att.dimensions) (att.source (@source))
reasonone or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
StatusOptionalDatatype 1–∞ occurrences ofdata.wordseparated by whitespace
Member ofmodel.pPart.transcriptionalContained bycore: abbrauthorbiblbiblScopedateeditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeeditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element supplied
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
macro.paraContent
}Schematron
<sch:rule context="tei:supplied">
<sch:assert test="not(matches(., '^\[|\]$'))"> Please remove square brackets from <sch:name/>: they are completed at processing time via XSLT.
</sch:assert></sch:rule>ExampleI am dr Sr yr
very humble Servt
Sydney SmithExampleDedication to the duke of BejarNoteThe damage, <gap>, del, unclear and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.
<surname><surname>
<surname> contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]ModulenamesdatesAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.persNamePartContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element surname { att.global.attributes, macro.phraseSeq }ExampleSt John Stevas
<table><table>@rows@cols
<table> contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]ModulefiguresAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
rowsindicates the number of rows in the table.
StatusOptionalDatatypedata.countNoteIf no number is supplied, an application must calculate the number of rows.Rows should be presented from top to bottom.
cols(columns) indicates the number of columns in each row of the table.
StatusOptionalDatatypedata.countNoteIf no number is supplied, an application must calculate the number of columns.Within each row, columns should be presented left to right.
Poor Men's Lodgings in Norfolk (Mayhew, 1843)Dossing Cribs or Lodging HousesBedsNeedys or Nightly LodgersBury St Edmund's58128Thetford3636Attleboro'3520Wymondham11122
NoteContains an optional heading and a series of rows.Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.
<tag><tag>@type@scheme
<tag> contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [22. Documentation Elements]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
typeindicates the type of XML tag intended
StatusOptionalDatatypedata.enumeratedLegal values are:a start-tag, with delimiters < and > is intendedan end-tag, with delimiters </ and > is intendeda empty tag, with delimiters < and /> is intendeda pi (processing instruction), with delimiters <? and ?> is intendeda comment, with delimiters <!-- and --> is intendeda marked-section, with delimiters <[CDATA[ and ]]> is intended
schemesupplies the name of the schema in which this tag is defined.
StatusOptionalDatatypedata.enumeratedSample values include:(text encoding initiative) This tag is defined as part of the TEI scheme. [Default](docbook) this tag is part of the Docbook scheme.(unknown) this tag is part of an unknown scheme.
Member ofmodel.phrase.xmlContained bycore: abbrauthorbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element tag
{
att.global.attributes,
attribute type { text }?,
attribute scheme { data.enumerated }?,
text
}Schematron
<sch:rule context="tei:tag">
<sch:assert test="not(matches(., '^[<!?-]|[>/?\-]$'))"> Tag delimiters such as angle brackets and tag-closing slashes are not allowed for <sch:name/>: they are completed at processing time via XSLT.
</sch:assert></sch:rule>ExampleMark the start of each italicised phrase with a
hi rend="it" tag, and its end with a hi tag.Example updated on 2008-04-05
<tagsDecl><tagsDecl>@partial
<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration2.3. The Encoding Description]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommendedDatatypedata.truthValueNoteTEI recommended practice is to specify this attribute. When the tagUsage elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the tagUsage elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.
Member ofmodel.encodingDescPartContained byheader: encodingDescMay containheader: renditionDeclaration
element tagsDecl
{
att.global.attributes,
attribute partial { data.truthValue }?,
( rendition*, namespace* )
}Exampleto be rendered in italic font
<teiHeader><teiHeader>
<teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document. [2.1.1. The TEI Header and Its Components15.1. Varieties of Composite Text]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bytextstructure: TEIMay containheader: encodingDescfileDescprofileDescrevisionDescDeclaration
element teiHeader
{
att.global.attributes,
( fileDesc, model.teiHeaderPart*, revisionDesc? )
}ExampleShakespeare: the first folio (1623) in electronic formShakespeare, William (1564–1616)Originally prepared byTrevor Howard-HillRevised and edited byChristine Avern-CarrOxford Text Archive13 Banbury Road, Oxford OX2 6NN, UK119
Freely available on a non-commercial basis.
1968The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)
Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).
Turned letters are silently corrected.
Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.
A reference is created by assembling the following, in the reverse order as that
listed here: the n value of the preceding lba periodthe n value of the ancestor div2a spacethe n value of the parent div1
12 Apr 89 Last checked by CAC1 Mar 89 LB made new fileNoteOne of the few elements unconditionally required in any TEI document.
<term><term>
<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionkeywordslanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrdateemailemphforeigngapgraphichilbmentionednamenotenumptrrefsoCalledtermtitlefigures: figureheader: idnonamesdates: affiliationforenameorgNameroleNamesurnametagdocs: attcodegiidenttagvaltranscr: suppliedDeclaration
element term { att.global.attributes, macro.phraseSeq }ExampleA computational device that infers structure
from grammatical strings of words is known as a parser, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.ExampleWe may define discoursal point of view as the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.NoteThis element is used to supply the form under which an index entry is to be made for the location of a parent index element.In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.
<text><text>
<text> (text) contains the complete text of the article. Must include a <front> containing an abstract, a <body> containing the main text, and a <back> containing the bibliography and any appendices. [4. Default Text Structure15.1. Varieties of Composite Text]ModuletextstructureAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained bytextstructure: TEIMay containcore: gaplbnotefigures: figuretextstructure: backbodyfrontDeclaration
element text
{
att.global.attributes,
(
model.global*,
( front, model.global* )?,
( body | group ),
model.global*,
( back, model.global* )?
)
}Schematron
<sch:rule context="tei:text[not(tei:body/tei:div[@type = ('editorialIntroduction')])]">
<sch:assert test="parent::tei:TEI/tei:teiHeader/tei:profileDesc/tei:textClass/tei:keywords"> An article must have a keyword list in the header.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:text[not(tei:body/tei:div[@type = ('editorialIntroduction')])]">
<sch:assert test="tei:front/tei:div[@type='abstract']"> An article must have a front section with an abstract.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:text[not(tei:body/tei:div[@type = ('editorialIntroduction')])]">
<sch:assert test="tei:back/tei:div[@type='bibliography']/tei:listBibl"> An article must have a back section with a bibliography.
</sch:assert></sch:rule>Example
This article is about...
Introduction
A great deal of previous research...
Method
This project was undertaken...
[...]
NoteThis element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the floatingText is provided for this purpose.
<textClass><textClass>
<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.profileDescPartContained byheader: profileDescMay containheader: catRefclassCodekeywordsDeclaration
element textClass { att.global.attributes, ( classCode | catRef )*, keywords }ExampleAcademic prose001.9End of the worldHistory - philosophy
<title><title>@type@level
<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors2.2.1. The Title Statement2.2.5. The Series Statement]ModulecoreAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp))
typeclassifies the title according to some convenient typology.
Derived fromatt.typedStatusOptionalDatatypedata.enumeratedLegal values are:(The main title of your article.) Academic articles often have a main title followed by a subtitle (sometimes with a colon separating them). If you have two such components in your article title, then in the <titleStmt>, use <title type="main"> and <title type="sub"> to encode the two components of your title.(The subtitle of your article.) Academic articles often have a main title followed by a subtitle (sometimes with a colon separating them). If you have two such components in your article title, then in the <titleStmt>, use <title type="main"> and <title type="sub"> to encode the two components of your title.NoteThis attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptionalDatatypedata.enumeratedLegal values are:(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper(series) the title applies to a series of otherwise distinct publications such as a collection(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)NoteThe level of a title is sometimes implied by its context: for example, a title appearing directly within an analytic element is ipso facto of level a, and one appearing within a <series> element of level s. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.
Member ofmodel.emphLikeContained bycore: abbrauthorbiblbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefseriessoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionseriesStmttitleStmtnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containcore: abbrbiblcitdatedescemailemphforeigngapgraphichilabellblistlistBiblmentionednamenotenumptrqquoterefsoCalledtermtitlefigures: figuretableheader: idnonamesdates: affiliationforenamelistPersonorgNameroleNamesurnametagdocs: attcodeegegXMLgiidenttagvaltranscr: suppliedDeclaration
element title
{
att.global.attributes,
attribute type { text }?,
attribute level { text }?,
macro.paraContent
}ExampleInformation Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989ExampleHardy's Tess of the D'Urbervilles: a machine readable
editionExample<title type="main">Synthèsean international journal for
epistemology, methodology and history of
scienceNoteThe attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.
<titleStmt><titleStmt>
<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. In jTEI, this must include a title and an <author> element for each author of the paper, which in turn must include <name>, <affiliation> and <email>. [2.2.1. The Title Statement2.2. The File Description]ModuleheaderAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Contained byheader: fileDescMay containcore: authortitleDeclaration
element titleStmt { att.global.attributes, ( title+, author+ ) }Schematron
<sch:rule context="tei:titleStmt">
<sch:assert test="tei:title[@type = 'main']"> A title of type "main" is required in <sch:name/>.
</sch:assert></sch:rule>ExampleCapgrave's Life of St. John Norbert: a machine-readable transcriptioncompiled byP.J. Lucas
<val><val>
<val> (value) contains a single attribute value. [22. Documentation Elements22.4.5. Attribute List Specification]ModuletagdocsAttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @rendition)) (att.global.responsibility (@cert, @resp)) Member ofmodel.phrase.xmlContained bycore: abbrauthorbiblScopedatedesceditoremailemphforeignheadhiitemlabelmentionednamenotenumppubPlacepublisherqquoterefsoCalledtermtitlefigures: cellheader: changeclassCodeeditionlanguagerenditionnamesdates: affiliationforenameorgNameroleNamesurnametagdocs: egtranscr: suppliedMay containCharacter data onlyDeclaration
element val { att.global.attributes, text }Schematron
<sch:rule context="tei:val">
<sch:assert test="not(matches(., concat('^', $quotes, '|', $quotes, '$')))"> Attribute value delimiters are not allowed for <sch:name/>: they are completed at processing time via XSLT.
</sch:assert></sch:rule>Exampleunknown
Model classes
model.addressLike
model.addressLikemodel.addressLike (model class)groups elements used to represent a postal or email address. [1. The TEI Infrastructure]ModuleteiUsed bymodel.pPart.dataMembersaffiliationemail
model.applicationLike
model.applicationLikemodel.applicationLike (model class)groups elements used to record application-specific information about a document in its header.ModuleteiUsed byappInfoMembersapplication
model.biblLike
model.biblLikemodel.biblLike (model class)groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]ModuleteiUsed bycitlistBiblmodel.intermodel.personPartsourceDescMembersbibllistBibl
model.biblPart
model.biblPartmodel.biblPart (model class)groups elements which represent components of a bibliographic description. [3.11. Bibliographic Citations and References]ModuleteiUsed bybiblMembersmodel.imprintPart [biblScopepubPlacepublisher] model.respLike [authoreditor] availabilitybibleditionseries
model.common
model.commonmodel.common (model class)groups common chunk- and inter-level elements. [1.3. The TEI Class System]ModuleteiUsed bybodydivMembersmodel.divPart [model.lLikemodel.pLike [p] ] model.inter [model.biblLike [bibllistBibl] model.egLike [egegXML] model.labelLike [desclabel] model.listLike [listlistPersontable] model.oddDeclmodel.qLike [model.quoteLike [citquote] q] model.stageLike] NoteThis class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.
model.dateLike
model.dateLikemodel.dateLike (model class)groups elements containing temporal expressions. [3.5.4. Dates and Times13.3.6. Dates and Times]ModuleteiUsed bymodel.pPart.dataMembersdate
model.descLike
model.descLikemodel.descLike (model class)groups elements which contain a description of their function.ModuleteiUsed bygapgraphicMembersdesc
model.divBottom
model.divBottommodel.divBottom (model class)groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]ModuleteiUsed bybodydivfrontlisttableMembersmodel.divBottomPartmodel.divWrapper
model.divLike
model.divLikemodel.divLike (model class)groups elements used to represent un-numbered generic structural divisions.ModuleteiUsed bybackbodydivfrontMembersdiv
model.divPart
model.divPartmodel.divPart (model class)groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]ModuleteiUsed bymacro.specialParamodel.commonMembersmodel.lLikemodel.pLike [p] NoteNote that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.
model.divTop
model.divTopmodel.divTop (model class)groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]ModuleteiUsed bybodydivlistMembersmodel.divTopPart [model.headLike [head] ] model.divWrapper
model.divTopPart
model.divTopPartmodel.divTopPart (model class)groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]ModuleteiUsed bymodel.divTopMembersmodel.headLike [head]
model.egLike
model.egLikemodel.egLike (model class)groups elements containing examples or illustrations. [22.1.1. Phrase Level Terms]ModuleteiUsed bymodel.interMembersegegXML
model.emphLike
model.emphLikemodel.emphLike (model class)groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]ModuleteiUsed bymodel.highlightedmodel.limitedPhraseMemberscodeemphforeignidentmentionedsoCalledtermtitle
model.encodingDescPart
model.encodingDescPartmodel.encodingDescPart (model class)groups elements which may be used inside <encodingDesc> and appear multiple times.ModuleteiUsed byencodingDescMembersappInfoprojectDesctagsDecl
model.frontPart
model.frontPartmodel.frontPart (model class)groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter
]ModuleteiUsed bybackfrontMembersmodel.frontPart.drama
model.global
model.globalmodel.global (model class)groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]ModuleteiUsed bybackbiblbodydatedivfrontheadlistmacro.paraContentmacro.phraseSeqmacro.phraseSeq.limitedmacro.specialParapersonseriestabletextMembersmodel.global.edit [gap] model.global.metamodel.milestoneLike [lb] model.noteLike [note] figure
model.global.edit
model.global.editmodel.global.edit (model class)groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]ModuleteiUsed bymodel.globalMembersgap
model.graphicLike
model.graphicLikemodel.graphicLike (model class)groups elements containing images, formulae, and similar objects. [3.9. Graphics and Other Non-textual Components]ModuleteiUsed bymodel.phrasetableMembersgraphic
model.headLike
model.headLikemodel.headLike (model class)groups elements used to provide a title or heading at the start of a text division.ModuleteiUsed bylistBibllistPersonmodel.divTopParttableMembershead
model.hiLike
model.hiLikemodel.hiLike (model class)groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]ModuleteiUsed bymodel.highlightedmodel.limitedPhraseMembershi
model.highlighted
model.highlightedmodel.highlighted (model class)groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]ModuleteiUsed bybiblmodel.phraseMembersmodel.emphLike [codeemphforeignidentmentionedsoCalledtermtitle] model.hiLike [hi]
model.imprintPart
model.imprintPartmodel.imprintPart (model class)groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References]ModuleteiUsed bymodel.biblPartMembersbiblScopepubPlacepublisher
model.inter
model.intermodel.inter (model class)groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]ModuleteiUsed byheadmacro.limitedContentmacro.paraContentmacro.specialParamodel.commonMembersmodel.biblLike [bibllistBibl] model.egLike [egegXML] model.labelLike [desclabel] model.listLike [listlistPersontable] model.oddDeclmodel.qLike [model.quoteLike [citquote] q] model.stageLike
model.labelLike
model.labelLikemodel.labelLike (model class)groups elements used to gloss or explain other parts of a document.ModuleteiUsed byapplicationmodel.interMembersdesclabel
model.limitedPhrase
model.limitedPhrasemodel.limitedPhrase (model class)groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]ModuleteiUsed bymacro.limitedContentmacro.phraseSeq.limitedMembersmodel.emphLike [codeemphforeignidentmentionedsoCalledtermtitle] model.hiLike [hi] model.pPart.data [model.addressLike [affiliationemail] model.dateLike [date] model.measureLike [num] model.nameLike [model.nameLike.agent [nameorgName] model.offsetLikemodel.persNamePart [forenameroleNamesurname] model.placeStateLike [model.placeNamePart] idno] ] model.pPart.editorial [abbr] model.pPart.msdescmodel.phrase.xml [attgitagval] model.ptrLike [ptrref]
model.measureLikemodel.measureLike (model class)groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. Numbers and
Measures]ModuleteiUsed bymodel.pPart.dataMembersnum
model.milestoneLike
model.milestoneLikemodel.milestoneLike (model class)groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System3.10.3. Milestone
Elements]ModuleteiUsed bylistBiblmodel.globalMemberslb
model.nameLike
model.nameLikemodel.nameLike (model class)groups elements which name or refer to a person, place, or organization.ModuleteiUsed bymodel.pPart.dataMembersmodel.nameLike.agent [nameorgName] model.offsetLikemodel.persNamePart [forenameroleNamesurname] model.placeStateLike [model.placeNamePart] idnoNoteA superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.
model.nameLike.agent
model.nameLike.agentmodel.nameLike.agent (model class)groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]ModuleteiUsed bymodel.nameLikeMembersnameorgNameNoteThis class is used in the content model of elements which reference names of people or organizations.
model.pLike.frontmodel.pLike.front (model class)groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]ModuleteiUsed bybackfrontMembershead
model.pPart.data
model.pPart.datamodel.pPart.data (model class)groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]ModuleteiUsed bybiblmodel.limitedPhrasemodel.phraseMembersmodel.addressLike [affiliationemail] model.dateLike [date] model.measureLike [num] model.nameLike [model.nameLike.agent [nameorgName] model.offsetLikemodel.persNamePart [forenameroleNamesurname] model.placeStateLike [model.placeNamePart] idno]
model.pPart.edit
model.pPart.editmodel.pPart.edit (model class)groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]ModuleteiUsed bybiblmodel.phraseMembersmodel.pPart.editorial [abbr] model.pPart.transcriptional [supplied]
model.pPart.editorial
model.pPart.editorialmodel.pPart.editorial (model class)groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. Simple Editorial Changes]ModuleteiUsed bymodel.limitedPhrasemodel.pPart.editMembersabbr
model.pPart.transcriptional
model.pPart.transcriptionalmodel.pPart.transcriptional (model class)groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. Simple Editorial Changes]ModuleteiUsed bymodel.pPart.editMemberssupplied
model.persNamePart
model.persNamePartmodel.persNamePart (model class)groups elements which form part of a personal name. [13.2.1. Personal Names]ModulenamesdatesUsed bymodel.nameLikeMembersforenameroleNamesurname
model.persStateLike
model.persStateLikemodel.persStateLike (model class)groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.ModuleteiUsed bymodel.personPartMembersaffiliationNoteThese characteristics of an individual are typically a consequence of their own action or that of others.
model.personLike
model.personLikemodel.personLike (model class)groups elements which provide information about people and their relationships.ModuleteiUsed bylistPersonparticDescMembersperson
model.personPart
model.personPartmodel.personPart (model class)groups elements which form part of the description of a person. [15.2.2. The Participant Description]ModuleteiUsed bypersonMembersmodel.biblLike [bibllistBibl] model.eventLikemodel.persStateLike [affiliation] idno
model.phrase
model.phrasemodel.phrase (model class)groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]ModuleteiUsed bydateheadmacro.paraContentmacro.phraseSeqmacro.specialParaMembersmodel.graphicLike [graphic] model.highlighted [model.emphLike [codeemphforeignidentmentionedsoCalledtermtitle] model.hiLike [hi] ] model.lPartmodel.pPart.data [model.addressLike [affiliationemail] model.dateLike [date] model.measureLike [num] model.nameLike [model.nameLike.agent [nameorgName] model.offsetLikemodel.persNamePart [forenameroleNamesurname] model.placeStateLike [model.placeNamePart] idno] ] model.pPart.edit [model.pPart.editorial [abbr] model.pPart.transcriptional [supplied] ] model.pPart.msdescmodel.phrase.xml [attgitagval] model.ptrLike [ptrref] model.segLikemodel.specDescLikeNoteThis class of elements can occur within paragraphs, list items, lines of verse, etc.
model.phrase.xml
model.phrase.xmlmodel.phrase.xml (model class)groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements]ModuleteiUsed bymodel.limitedPhrasemodel.phraseMembersattgitagval
model.placeStateLike
model.placeStateLikemodel.placeStateLike (model class)groups elements which describe changing states of a place.ModuleteiUsed bymodel.nameLikeMembersmodel.placeNamePart
model.profileDescPart
model.profileDescPartmodel.profileDescPart (model class)groups elements which may be used inside <profileDesc> and appear multiple times.ModuleteiUsed byprofileDescMemberslangUsageparticDesctextClass
model.ptrLike
model.ptrLikemodel.ptrLike (model class)groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]ModuleteiUsed byapplicationbiblcitmodel.limitedPhrasemodel.phraseseriesMembersptrref
model.publicationStmtPart.agency
model.publicationStmtPart.agencymodel.publicationStmtPart.agency (model class)groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]ModuleteiUsed bypublicationStmtMemberspublisherNoteThe agency child elements, while not required, are required if one of the detail child elements is to be used. It is not valid to have a detail child element without a preceding agency child element.See also model.publicationStmtPart.detail.
model.publicationStmtPart.detail
model.publicationStmtPart.detailmodel.publicationStmtPart.detail (model class)groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]ModuleteiUsed bypublicationStmtMembersavailabilitydateidnopubPlaceNoteA detail child element may not occur unless an agency child element precedes it.See also model.publicationStmtPart.agency.
model.qLike
model.qLikemodel.qLike (model class)groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]ModuleteiUsed bymodel.interMembersmodel.quoteLike [citquote] q
model.quoteLike
model.quoteLikemodel.quoteLike (model class)groups elements used to directly contain quotations.ModuleteiUsed bymodel.qLikeMemberscitquote
model.respLike
model.respLikemodel.respLike (model class)groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.ModuleteiUsed bymodel.biblPartMembersauthoreditor
model.teiHeaderPart
model.teiHeaderPartmodel.teiHeaderPart (model class)groups high level elements which may appear more than once in a TEI header.ModuleteiUsed byteiHeaderMembersencodingDescprofileDesc
Attribute classes
att.ascribed
att.ascribedatt.ascribed (attribute class)@whoprovides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation8.3. Elements Unique to Spoken Texts]ModuleteiMemberschangeqAttributesAttributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespaceIn the following example from Hamlet, speeches (sp) in the body of the play are linked to castItem elements in the castList using the who attribute.BernardoFranciscoa soldierBernardoWho's there?FranciscoNay, answer me: stand, and unfold yourself.NoteFor transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.
att.datable
att.datableatt.datable (attribute class)provides attributes for normalization of elements that contain dates, times, or datable events.ModuleteiMemberschangedateAttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)
att.datable.w3c
att.datable.w3catt.datable.w3c (attribute class)@when@notBefore@notAfter@from@toprovides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times13.3.6. Dates and Times]ModuleteiMembersatt.datable [changedate] AttributesAttributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptionalDatatypedata.temporal.w3cExamples of W3C date, time, and date & time formats.
24 Oct 45September 24th, 1996 at 3:25 in the morningOctober of 1962June 12ththe first of the monthAugustMMVIAD 5656 BC
This list begins in
the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
Pentecost, in that year the 27th of May (old style).Dorchester, Village,March 2d. 1828.To
Mrs. Cornell, Sunday
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptionalDatatypedata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptionalDatatypedata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptionalDatatypedata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptionalDatatypedata.temporal.w3c
Example28 May through 1 June 1863NoteThe value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.
att.dimensions
att.dimensionsatt.dimensions (attribute class)provides attributes for describing the size of physical objects.ModuleteiMembersatt.editLike [affiliationdategapnameorgNamepersonsupplied] AttributesAttributes
att.divLike
att.divLikeatt.divLike (attribute class)provides attributes common to all elements which behave in the same way as divisions.ModuleteiMembersdivAttributesAttributes
att.editLike
att.editLikeatt.editLike (attribute class)provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind.ModuleteiMembersaffiliationdategapnameorgNamepersonsuppliedAttributesAttributes att.dimensionsatt.source (@source)
att.global
att.globalatt.global (attribute class)@xml:id@n@xml:lang@xml:base@xml:spaceprovides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]ModuleteiMembersTEIabbraffiliationappInfoapplicationattauthoravailabilitybackbiblbiblScopebodycatRefcellchangecitclassCodecodedatedescdiveditioneditoregegXMLemailemphencodingDescfigurefileDescforeignforenamefrontgapgigraphicheadhiidentidnoitemkeywordslabellangUsagelanguagelblistBibllistChangelistPersonmentionednamenotenumorgNamepparticDescpersonprofileDescprojectDescptrpubPlacepublicationStmtpublisherqquoterefrenditionrevisionDescroleNamerowseriesseriesStmtsoCalledsourceDescsuppliedsurnametabletagtagsDeclteiHeadertermtexttextClasstitletitleStmtvalAttributesAttributes att.global.rendition (@rend, @rendition)att.global.responsibility (@cert, @resp)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptionalDatatype
xsd:IDNoteThe xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. Reference Systems.
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptionalDatatypedata.textNoteThe value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.
xml:lang(language) indicates the language of the element content using a tag generated according to BCP 47.
StatusOptionalDatatypedata.language
… The consequences of
this rapid depopulation were the loss of the last
ariki or chief
(Routledge 1920:205,210) and their connections to
ancestral territorial organization.
NoteThe xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.The authoritative list of registered language subtags is maintained by IANA and is available at . For a good general overview of the construction of language tags, see , and for a practical step-by-step guide, see .The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their IETFInternet Engineering Task Force definitions.
xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptionalDatatypedata.pointer
BibliographyLandon, Letitia ElizabethThe Vow of the PeacockCompton, Margaret ClephaneIrene, a Poem in Six CantosTaylor, JaneEssays in Rhyme on Morals and Manners
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptionalDatatypedata.enumeratedLegal values are:signals that the application's default white-space processing modes are acceptableindicates the intent that applications preserve all white spaceNoteThe XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.
att.global.rendition
att.global.renditionatt.global.rendition (attribute class)@rend@renditionprovides rendering attributes common to all elements in the TEI encoding scheme.ModuleteiMembersatt.global [TEIabbraffiliationappInfoapplicationattauthoravailabilitybackbiblbiblScopebodycatRefcellchangecitclassCodecodedatedescdiveditioneditoregegXMLemailemphencodingDescfigurefileDescforeignforenamefrontgapgigraphicheadhiidentidnoitemkeywordslabellangUsagelanguagelblistBibllistChangelistPersonmentionednamenotenumorgNamepparticDescpersonprofileDescprojectDescptrpubPlacepublicationStmtpublisherqquoterefrenditionrevisionDescroleNamerowseriesseriesStmtsoCalledsourceDescsuppliedsurnametabletagtagsDeclteiHeadertermtexttextClasstitletitleStmtval] AttributesAttributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptionalDatatype 1–∞ occurrences ofdata.wordseparated by whitespaceTo The Duchesse of Newcastle,
On Her New Blazing-World. NoteThese Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.
renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespaceTo The Duchesse of Newcastle, On Her
New Blazing-World. font-variant: small-capsfont-variant: normaltext-align: centerNoteThe rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.Where both rendition and rend are supplied, the latter is understood to override or complement the former.Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.
att.global.responsibility
att.global.responsibilityatt.global.responsibility (attribute class)@cert@respprovides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [3.4. Simple Editorial Changes11.3.2.2. Hand, Responsibility, and Certainty Attributes17.3. Spans and Interpretations13.1.1. Linking Names and Their Referents]ModuleteiMembersatt.global [TEIabbraffiliationappInfoapplicationattauthoravailabilitybackbiblbiblScopebodycatRefcellchangecitclassCodecodedatedescdiveditioneditoregegXMLemailemphencodingDescfigurefileDescforeignforenamefrontgapgigraphicheadhiidentidnoitemkeywordslabellangUsagelanguagelblistBibllistChangelistPersonmentionednamenotenumorgNamepparticDescpersonprofileDescprojectDescptrpubPlacepublicationStmtpublisherqquoterefrenditionrevisionDescroleNamerowseriesseriesStmtsoCalledsourceDescsuppliedsurnametabletagtagsDeclteiHeadertermtexttextClasstitletitleStmtval] AttributesAttributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptionalDatatypedata.certainty
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespaceNoteNote that a simple resp pointing to a person or organization is likely to be somewhat ambiguous with regard to the nature of the responsibility. For this reason, we recommend that resp be used to point not to an agent (<person> or org) but to a respStmt, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).
ExampleBlessed are the
placemakerspeacemakers: for they shall be called the children of God.ExamplePunkes, Panders, baſe extortionizing
slanues,TranscriberJanelle Jenstad
att.media
att.mediaatt.media (attribute class)@width@heightprovides attributes for specifying display and related properties of external media.ModuleteiMembersgraphicAttributesAttributes
widthWhere the media are displayed, indicates the display width
StatusOptionalDatatypedata.outputMeasurement
heightWhere the media are displayed, indicates the display height
StatusOptionalDatatypedata.outputMeasurement
att.naming
att.namingatt.naming (attribute class)@roleprovides attributes common to elements which refer to named persons, places, organizations etc.ModuleteiMembersatt.personalAttributesAttributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptionalDatatype 1–∞ occurrences ofdata.enumeratedseparated by whitespace
att.pointing
att.pointingatt.pointing (attribute class)@targetdefines a set of attributes used by all elements which point to other elements by means of one or more URI references.ModuleteiMemberscatRefAttributesAttributes
targetspecifies the destination of the reference by supplying one or more URI References
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespaceNoteOne or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.
att.resourced
att.resourcedatt.resourced (attribute class)@urlprovides attributes by which a resource (such as an externally held media file) may be located.ModuleteiMembersgraphicAttributesAttributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
StatusRequiredDatatypedata.pointer
att.source
att.sourceatt.source (attribute class)@sourceprovides attributes for pointing to the source of a bibliographic reference. [3.3.3. Quotation8.3.4. Writing]ModuleteiMembersatt.editLike [affiliationdategapnameorgNamepersonsupplied] abbregXMLnoteqquoteAttributesAttributes
sourceprovides a pointer to the bibliographical source from which a quotation or citation is drawn.
StatusOptionalDatatype 1–∞ occurrences ofdata.pointerseparated by whitespace
Example
As Willard McCarty (2012, p.2)
tells us, ‘Collaboration’ is a
problematic and should be a contested term.
Example
Grammatical theories
are in flux, and the more we learn, the less we
seem to know.
The Chicago Manual of Style,
15th edition.
Chicago:
University of Chicago Press
(2003),
p.147.
att.tableDecoration
att.tableDecorationatt.tableDecoration (attribute class)@role@rows@colsprovides attributes used to decorate rows or cells of a table.ModuleteiMemberscellrowAttributesAttributes
roleindicates the kind of information held in this cell or in each cell of this row.
StatusOptionalDatatypedata.enumeratedLegal values are: [Default]NoteWhen this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent <row> element.
rowsindicates the number of rows occupied by this cell or row.
StatusOptionalDatatypedata.countDefault1NoteA value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.
cols(columns) indicates the number of columns occupied by this cell or row.
StatusOptionalDatatypedata.countDefault1NoteA value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.
att.typed
att.typedatt.typed (attribute class)@typeprovides attributes which can be used to classify or subclassify elements in any way.ModuleteiMemberschangelistPersonAttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptionalDatatypedata.enumerated
Night in TarrasAt evening tramping on the hot white road…A wind sprang up from nowhere as the sky…
NoteThe type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.
Schematron
<sch:rule context="*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype
unless also categorized in general with @type</sch:assert></sch:rule>
Macros
data.certaintydata.certainty (macro)
data.certaintydefines the range of attribute values expressing a degree of certainty.ModuleteiUsed byDeclaration
data.certainty = "high" | "medium" | "low" | "unknown"NoteCertainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. For more precise indication, data.probability may be used instead or in addition.
data.countdata.count (macro)
data.countdefines the range of attribute values used for a non-negative integer value used as a count.ModuleteiUsed byElement: table/@rowstable/@colsDeclaration
data.count = xsd:nonNegativeIntegerNoteOnly positive integer values (including zero) are permitted
data.enumerateddata.enumerated (macro)
data.enumerateddefines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.ModuleteiUsed byElement: abbr/@typebiblScope/@unitdiv/@typeeditor/@roleegXML/@validgap/@agentgi/@schemehead/@typeidno/@typelist/@rendlist/@typenum/@typeperson/@roleperson/@ageptr/@typeref/@typerendition/@schemetag/@typetag/@schemetitle/@typetitle/@levelDeclaration
data.enumerated = data.wordNoteAttributes using this datatype must contain a single word matching the pattern defined for this datatype: for example it cannot include whitespace but may begin with digits. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a valList element.
data.languagedata.language (macro)
data.languagedefines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]ModuleteiUsed byElement: language/@identDeclaration
data.language = xsd:language | ""NoteThe values for this attribute are language tags as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.A language tag, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable. The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at . It is recommended that this code be written in lower case.The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at . The IETF recommends this code be omitted unless it is necessary to make a distinction you need.Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at . The latter consist of 3 digits; the list of codes can be found at .An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been grandfathered from previous specifications.Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.Examples include ShonaTaiwaneseChinese written in traditional script as used in Hong KongEnglish as spoken in Sierra LeonePolishSpanish as spoken in MexicoSpanish as spoken in Latin AmericaThe W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.
data.namedata.name (macro)
data.namedefines the range of attribute values expressed as an XML Name.ModuleteiUsed byattgiElement: application/@identDeclaration
data.name = xsd:NameNoteAttributes using this datatype must contain a single word which follows the rules defining a legal XML name (see ): for example they cannot include whitespace or begin with digits.
data.namespacedata.namespace (macro)
data.namespacedefines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.ModuleteiUsed byDeclaration
data.namespace = xsd:anyURINoteThe range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
data.numericdata.numeric (macro)
data.numericdefines the range of attribute values used for numeric values.ModuleteiUsed byElement: num/@valueDeclaration
data.numeric =
xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimalNoteAny numeric value, represented as a decimal number, in floating point format, or as a ratio.To represent a floating point number, expressed in scientific notation, E notation, a variant of exponential notation, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.
data.outputMeasurementdefines a range of values for use in specifying the size of an object that is intended for display.ModuleteiUsed byDeclaration
data.outputMeasurement =
token
{
pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
}ExampleThe TEI LogoStylized yellow angle brackets with the letters TEI in
between and text encoding initiative underneath, all on a white
background.NoteThese values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.
data.pointerdata.pointer (macro)
data.pointerdefines 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.ModuleteiUsed byElement: catRef/@schemechange/@targetclassCode/@schemegap/@handkeywords/@schemeptr/@targetref/@targetDeclaration
data.pointer = xsd:anyURINoteThe range of syntactically valid values is defined by RFC 3986Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/
data.sexdata.sex (macro)
data.sexdefines the range of attribute values used to identify human or animal sex.ModuleteiUsed byElement: person/@sexDeclaration
data.sex = data.wordNoteValues for attributes using this datatype may be locally defined by a project, or may refer to an external standard, such as vCard's sex property (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People.
data.temporal.w3cdata.temporal.w3c (macro)
data.temporal.w3cdefines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.ModuleteiUsed byDeclaration
data.temporal.w3c =
xsd:date
| xsd:gYear
| xsd:gMonth
| xsd:gDay
| xsd:gYearMonth
| xsd:gMonthDay
| xsd:time
| xsd:dateTimeNoteIf it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.
data.textdata.text (macro)
data.textdefines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.ModuleteiUsed byElement: rendition/@selectorDeclaration
data.text = stringNoteAttributes using this datatype must contain a single token in which whitespace and other punctuation characters are permitted.
data.truthValuedata.truthValue (macro)
data.truthValuedefines the range of attribute values used to express a truth value.ModuleteiUsed byElement: listChange/@orderedtagsDecl/@partialDeclaration
data.truthValue = xsd:booleanNoteThe possible values of this datatype are 1 or true, or 0 or false.This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: data.xTruthValue.
data.versionNumberdata.versionNumber (macro)
data.versionNumberdefines the range of attribute values used for version numbers.ModuleteiUsed byElement: application/@versionDeclaration
data.versionNumber =
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }
data.worddata.word (macro)
data.worddefines the range of attribute values expressed as a single word or token.ModuleteiUsed bydata.enumerateddata.sexElement: code/@langgap/@reasonsupplied/@reasonDeclaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }NoteAttributes using this datatype must contain a single word which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.
macro.anyXMLmacro.anyXML (macro)
macro.anyXMLdefines a content model within which any XML elements are permittedModuleteiUsed byegXMLmacro.anyXMLDeclaration
macro.anyXML =
element * - (tei:* | teix:egXML)
{
attribute * { text }*,
( text | macro.anyXML )*
}
macro.limitedContentmacro.limitedContent (macro)
macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]ModuleteiUsed bydescrenditionDeclaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*
macro.paraContentmacro.paraContent (macro)
macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]ModuleteiUsed byemphhiprefsuppliedtitleDeclaration
macro.paraContent =
(
text
| model.gLike
| model.phrase
| model.inter
| model.global
| lg
| model.lLike
)*
macro.phraseSeqmacro.phraseSeq (macro)
macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]ModuleteiUsed byabbraffiliationauthorbiblScopeeditioneditoregemailforeignforenamelabelmentionednamenumorgNamepubPlacepublisherroleNamesoCalledsurnametermDeclaration
macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )*
macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]ModuleteiUsed byclassCodelanguageDeclaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*
macro.specialParamacro.specialPara (macro)
macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]ModuleteiUsed bycellchangeitemnoteqquoteDeclaration
macro.specialPara =
(
text
| model.gLike
| model.phrase
| model.inter
| model.divPart
| model.global
)*
Constraints
Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag)][matches(.,
$apos.typographic)]">
<sch:report test="matches(., '\W[’]\D') or matches(., '[‘](\W|$)') or matches(., '\w[‘]\w')"> Left and Right Single Quotation Marks should be used in the right place.
</sch:report></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:quote or ancestor::tei:title)]">
<sch:assert test="not(matches(., '\d\d?((th)|(st)|(rd)|(nd))[- ]centur((y)|(ies))',
'i'))"> Centuries such as "the nineteenth century" should be spelled out, not written with digits.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:body//tei:div[not(@type='editorialIntroduction')]|tei:figure|tei:table"
role="warning">
<sch:assert test="@xml:id"> You're strongly advised to add an @xml:id attribute to <sch:name/> to ease formal cross-referencing
with (ptr|ref)[@type='crossref']
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:ptr[@type='crossref']|tei:ref[@type='crossref']">
<sch:assert test="id(substring-after(@target, '#'))/(self::tei:div|self::tei:figure|self::tei:table)"> Cross-links (<sch:name/>[@type="crossref"]) should be targeted at div, figure, or table elements.
</sch:assert></sch:rule>Schematron
<sch:rule context="tei:ptr[not(@type='crossref')]|tei:ref[not(@type='crossref')]">
<sch:report test="id(substring-after(@target, '#'))/(self::tei:div|self::tei:figure|self::tei:table)"> Please type internal cross-references as 'crossref' (<sch:name/>[@type="crossref"]).
</sch:report></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag|ancestor::tei:ref)]">
<sch:assert test="not(contains(., '--'))"> Double hyphens should not be used for dashes. Please use
the EM Dash (U+2014 or —) instead.
</sch:assert></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag|ancestor::tei:ref[not(@type='crossref')])]"
role="warning">
<sch:assert test="not(matches(., '(table|figure|example|section) \d+([.,]\d+)* ((above)|(below))',
'i'))"> Please replace literal references to tables, figures, examples, and sections with a formal crosslink:
(ptr|ref)[@type="crossref"]
</sch:assert></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag)]">
<sch:report test="matches(., '(i\.e\.|e\.g\.)[^,]', 'i')"> You should put a comma after "i.e." and "e.g.".
</sch:report></sch:rule>Schematron
<sch:rule context="@*[not(ancestor::eg:egXML)][name() = ('corresp', 'target', 'from',
'to', 'ref', 'rendition', 'resp', 'source')][some $i in tokenize(.,
'\s+') satisfies starts-with($i, '#')]">
<sch:assert test="every $i in tokenize(., '\s+')[starts-with(., '#')] satisfies id(
substring-after($i, '#'))"> There's no local target for this link. Please make sure you use an existing @xml:id value.
</sch:assert></sch:rule>Schematron
<sch:ns prefix="sch"
uri="http://purl.oclc.org/dsdl/schematron"/>
<sch:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<sch:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/>
<sch:ns prefix="xsl"
uri="http://www.w3.org/1999/XSL/Transform"/>
<sch:ns prefix="eg"
uri="http://www.tei-c.org/ns/Examples"/>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag)]">
<sch:report test="matches(., $double.quotes) or matches(., '(^|\W)[‘][^‘’]+[’](\W|$)')"> Quotation marks are not permitted in plain text. Please use appropriate mark-up that will ensure the appropriate quotation marks will be generated consistently.
</sch:report></sch:rule>Schematron
<sch:rule context="tei:title[@level eq 'a']|tei:mentioned|tei:soCalled|tei:quote|tei:q">
<sch:assert test="not(matches(., concat('^', $double.quotes, '|', $double.quotes, '$')))"> Quotation mark delimiters are not allowed for <sch:name/>: they are completed at processing time via XSLT.
</sch:assert></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag|ancestor::tei:idno)][not(.
= parent::*/@*)]">
<sch:assert test="not(matches(., '\d-\d'))"> Numeric ranges should not be indicated with a hyphen. Please use
the EN Dash (U+2013 or –) character instead.
</sch:assert></sch:rule>Schematron
<sch:rule context="text()[not(ancestor::tei:eg|ancestor::eg:egXML|ancestor::tei:code|ancestor::tei:tag)]">
<sch:report test="matches(., $apos.straight)"> "Straight apostrophe" characters are not permitted. Please use the
Right Single Quotation Mark (U+2019 or ’) character instead. On the other hand, if the straight
apostrophe characters function as quotation marks, please replace them with appropriate mark-up
that will ensure the appropriate quotation marks will be generated consistently.
</sch:report></sch:rule>Schematron
<sch:rule context="@target[contains(., 'http://www.tei-c.org/release/doc/tei-p5-doc')]">
<sch:assert test="false()"> Please refer to the exact version of the TEI Guidelines, and link to the version that can be found in the Vault section. For an overview of all archived versions, see http://www.tei-c.org/Vault/P5/.
If you're referring to the English version, the correct URL will likely take the form of http://www.tei-c.org/Vault/P5/{$version-number}/doc/tei-p5-doc/en/html/.
</sch:assert></sch:rule>Schematron
<sch:pattern>
<sch:let name="double.quotes"
value="'["“”]'"/>
<sch:let name="apos.typographic"
value="'[‘’]'"/>
<sch:let name="apos.straight" value="''''"/>
<sch:let name="quotes"
value="concat('[', $apos.straight, '"]')"/></sch:pattern>