Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

Ron Van den Branden and Martin Holmes

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

Ron Van den Branden

Martin Holmes

2014

Table of contents

1. Introduction

2. Encoding for jTEI in Oxygen

2.1. Using the Template

2.2. Testing Your Document

3. Basic Text Structure

3.1. The Header and Metadata

3.2. Front Matter

3.3. The Body

3.4. Back Matter: the Bibliography and Appendices

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

4.2. Paragraphs

4.3. Lists

4.4. Quotations, Inline and Block

4.5. Figures and Graphics

4.6. Example Code, XML and non-XML

4.7. Tables

5. Inline Rhetorical Elements

6. Inline Technical Elements

7. Footnotes

8. Internal Linking

9. External Linking

10. Frequently-asked Questions

Appendix A Summary of Elements and their Rendition

Appendix B §

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

1. Introduction

Next 2. Encoding for jTEI in Oxygen

Home

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 lodel.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).

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

2. Encoding for jTEI in Oxygen

Table of contents

2.1. Using the Template

2.2. Testing Your Document

Previous 1. Introduction

Next 3. Basic Text Structure

Home

TEI: Using the Template⚓︎2.1. 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.

Figure 1. 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.

Previous 2.1. Using the Template

Home

TEI: Testing Your Document⚓︎2.2. 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.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

3. Basic Text Structure

Table of contents

3.1. The Header and Metadata

3.2. Front Matter

3.3. The Body

3.4. Back Matter: the Bibliography and Appendices

Previous 2. Encoding for jTEI in Oxygen

Next 4. Divisions, Paragraphs, Lists and Other Block Elements

Home

A jTEI journal article is a relatively simple TEI document consisting of a teiHeader and a text.

Next 3.2. Front Matter

Home

TEI: The Header and Metadata⚓︎3.1. The Header and Metadata

This is an example teiHeader:

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

⚓︎

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 if possible. 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.

Previous 3.1. The Header and Metadata

Next 3.3. The Body

Home

TEI: Front Matter⚓︎3.2. 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.

Previous 3.2. Front Matter

Next 3.4. Back Matter: the Bibliography and Appendices

Home

TEI: The Body⚓︎3.3. 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 heads of your divs. These will be provided automatically by the rendering tools.

An Editorial Introduction can be added in the body using a <div type="editorialIntroduction">. This is the only div which does not require head.

Previous 3.3. The Body

Home

TEI: Back Matter: the Bibliography and Appendices⚓︎3.4. 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 type

web 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:

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

⚓︎

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

4. Divisions, Paragraphs, Lists and Other Block Elements

Table of contents

4.1. Divisions

4.2. Paragraphs

4.3. Lists

4.4. Quotations, Inline and Block

4.5. Figures and Graphics

4.6. Example Code, XML and non-XML

4.7. Tables

Previous 3. Basic Text Structure

Next 5. Inline Rhetorical Elements

Home

TEI: Divisions⚓︎4.1. 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:

subdivisions

lists

quotations

figures and graphics

tables

code 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.

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

⚓︎

Previous 4.1. Divisions

Next 4.3. Lists

Home

TEI: Paragraphs⚓︎4.2. 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:

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

⚓︎

Previous 4.2. Paragraphs

Next 4.4. Quotations, Inline and Block

Home

TEI: Lists⚓︎4.3. 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 labels and items, like this:

<list type="gloss">
 <label>compressor</label>
 <item>a device which reduces the peaks of volume in an audio signal</item>
 <label>equalizer</label>
 <item>a device which allows different frequency bands in an audio signal
   to be cut or boosted</item>
</list>

⚓︎

All other types of list (numbered, bulleted etc.) do not have the type attribute. Their appearance is controlled by the rend attribute:

list (list) contains any sequence of items organized as a list.

rend
describes the way the list should be rendered.

Lists may be nested:

<list rend="bulleted">
 <item>compressor:
 <list rend="ordered">
   <item>limiter</item>
   <item>multiband compressor</item>
  </list>
 </item>
 <item>equalizer:
 <list rend="ordered">
   <item>graphic equalizer</item>
   <item>parametric equalizer</item>
  </list>
 </item>
</list>

⚓︎

For processing reasons, jTEI puts one restriction on what can appear inside lists: you can't use table anywhere inside item.

Previous 4.3. Lists

Next 4.5. Figures and Graphics

Home

TEI: Quotations, Inline and Block⚓︎4.4. 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:

<p>In his blog post, <title level="a">Text: A Massively Addressable Object</title>,
published in the 2012 anthology <title level="m">Debates in the Digital
   Humanities</title>, Michael Witmore defines texts as objects that are
<quote source="#quoteref3">massively addressable at different levels of scale</quote>
(<ref type="bibl" xml:id="quoteref3"
  target="#witmore12">Witmore 2012, 325</ref>).
</p>

⚓︎

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:

<p>An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
<quote source="#quoteref1">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<gap/> Where does she go for help?
   Where in the TEI universe is the level of ubiquitous Grade I support?</quote>
(<bibl xml:id="quoteref1">Martin Mueller, pers. comm, Jan. 18, 2013</bibl>).</p>

⚓︎

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:

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

⚓︎

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 5. Inline Rhetorical Elements). 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: …¹. 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 5. Inline Rhetorical Elements.

Previous 4.4. Quotations, Inline and Block

Next 4.6. Example Code, XML and non-XML

Home

TEI: Figures and Graphics⚓︎4.5. 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:

<figure xml:id="titlePage">
 <graphic url="img/titlePage.png"
  width="620px" height="980px"/>
 <head type="legend">The title page of the 1598 edition</head>
</figure>

⚓︎

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:

<p>As you can see from <ptr target="#titlePage" type="crossref"/>,
the title page is damaged...</p>

⚓︎

This will be expanded at rendering time into ‘Figure X’, where X is the appropriate figure number.

Previous 4.5. Figures and Graphics

Next 4.7. Tables

Home

TEI: Example Code, XML and non-XML⚓︎4.6. 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 article²:

<p>Links between authors and books are encoded using <gi>link</gi> elements: <egXML
xmlns="http://www.tei-c.org/ns/Examples"> <link target="#middlemarch #eliot"/>
</egXML> </p>

⚓︎

You might want to provide a caption for code examples. In these cases, the eg or egXML element should be enclosed in a figure:

<figure xml:id="example_code_1">
 <eg> declare function local:getTitles($source as element(div)) as xs:string*{
   for $t in $source//title
   return xs:string($t)
   };
 </eg>
 <head type="legend">A simple XQuery function</head>
</figure>

⚓︎

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.

Previous 4.6. Example Code, XML and non-XML

Home

TEI: Tables⚓︎4.7. 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:

label

The row or cell contains a header, not actual data.

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.

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

⚓︎

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:

<p>As you can see from <ptr target="#table1" type="crossref"/>, the elements included...</p>

⚓︎

This will be expanded at rendering time into ‘Table X’, where X is the appropriate table number.

Notes

1

Note, if you're omitting text at the end of a sentence, the sentence punctuation should precede the gap element.

↵

2

Note, 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 6. Inline Technical Elements.

↵

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

5. Inline Rhetorical Elements

Previous 4. Divisions, Paragraphs, Lists and Other Block Elements

Next 6. Inline Technical Elements

Home

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.

<p>
 <term>Interoperability</term> may be defined as the property of data that allows
it to be loaded <emph>unmodified</emph> and fully used in a <emph>variety</emph>
of software applications. <term>Interchange</term> is basically the same property
that applies after a preliminary conversion of the data (<ref type="bibl" target="#bauman11">Bauman
   2011</ref>; <ref type="bibl" target="#unsworth11">Unsworth 2011</ref>), 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.
</p>

⚓︎

<p>Unicode is a <emph>character</emph> encoding standard, and is not intended to
standardize ligatures or other presentation forms
(<ref type="bibl" xml:id="quoteref16"
  target="#unicode14">Unicode 2014</ref>).
For example, there is no Unicode character for old Latin <foreign xml:lang="la">sescuncia</foreign>
(like a pound-sign, = one eighth), since it can be composed from <foreign xml:lang="la">semuncia</foreign>
(character 10192) and an EN-dash (<ref type="bibl" target="#unicode06">Unicode 2006, 4</ref>)</p>

⚓︎

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.

Note:

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.

<p>The standard definition of metadata as <q>data about data</q> seems to pose more
questions than it answers.</p>

⚓︎

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

⚓︎

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).

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

6. Inline Technical Elements

Previous 5. Inline Rhetorical Elements

Next 7. Footnotes

Home

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.

<p>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
<val>iou</val> as the value of <att>commodity</att> of <gi>measure</gi> for this purpose.</p>

⚓︎

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 4.6. Example Code, XML and non-XML).

<p>A range like <code>#range(left(//lb[@n='3']),left(//lb[@n='4']))</code>, however,
could unambiguously address the sequence of nodes comprising line 3, even if the
<gi>lb</gi> happened to be a child of another element that began in the previous line.</p>
<!-- ... -->
<p>For example, <tag type="empty">rng:ref name="model.pLike"</tag> becomes <tag type="empty">classRef key="model.pLike"</tag>.</p>

⚓︎

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:

<p>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 <att>xml:id</att>
attribute (say, <code>xml:id="foo"</code>), and point at the ID using either a
URI with an appended fragment identifier (<val>#foo</val>) or using an attribute
whose type is IDREF.</p>

⚓︎

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:

<p>For example <ident>teidata.duration.iso</ident>, <ident>teidata.outputMeasurement</ident>,
<ident>teidata.pattern</ident>, <ident>teidata.point</ident>, <ident>teidata.version</ident>,
and <ident>teidata.word</ident> all map to the same datatype CDATA in XML DTD, and to
various TEI-defined regular expressions in RELAX NG or W3C Schema.</p>

⚓︎

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

7. Footnotes

Previous 6. Inline Technical Elements

Next 8. Internal Linking

Home

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:

<p>There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the <att>match</att> attribute,
<note>
  <p>See <ptr target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/ref-att.scoping.html"/>
  </p>
 </note> and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have <att>xml:id</att> attributes.</p>

⚓︎

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

8. Internal Linking

Previous 7. Footnotes

Next 9. External Linking

Home

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. Additionally, internal links can point to footnotes inside note elements, too. 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:

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

⚓︎

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:

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

⚓︎

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 OpenEdition version for publication at journals.openedition.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:

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

⚓︎

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 4.4. Quotations, Inline and Block.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

9. External Linking

Previous 8. Internal Linking

Next 10. Frequently-asked Questions

Home

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:

<item>addresses the range between two points (<ref target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/SA.html#SATSRN">16.2.5.4 range()</ref>)</item>

⚓︎

<p>More detailed information can be found at <ptr target="http://www.tei-c.org/Vault/P5/2.5.0/doc/tei-p5-doc/en/html/ref-elementSpec.html"/>.</p>

⚓︎

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 http://www.tei-c.org/Guidelines/P5/ 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.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

10. Frequently-asked Questions

Previous 9. External Linking

Next Appendix A Summary of Elements and their Rendition

Home

Where 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 initial 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.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

Appendix A Summary of Elements and their Rendition

Next Appendix B §

Home

Element/Tag
Usage
Example
Rendition

abbr
an abbreviation of any sort

<abbr>DPI</abbr>

⚓︎

DPI

att
attribute name

<att>place</att>

⚓︎

@place

cit
blockquote with bibliographic reference

<cit>
 <quote source="quoteref7">
  <supplied>A</supplied>ccount books
   are among the most common but least accessible primary sources
   for historians<gap/>
 </quote>
 <ref type="bibl"
  xml:id="quoteref7"
  target="#mcgaw85">McGaw 1985</ref>
</cit>

⚓︎

[A]ccount books are among the most common but least accessible primary sources for historians …
(McGaw 1985)

code
short inline code example

<p>A mixed content model such as
<code>(#PCDATA | a | model.b)*</code>
might be expressed as follows</p>

⚓︎

A mixed content model such as (#PCDATA | a | model.b)* might be expressed as follows

eg
non-XML code example

<eg>   $('#teiHolder').data('modVers', {     xmlFile: 'data/teiFile.xml'     annotations: 'data/annotations.json',     fixFirst: false,     fullscreen: false,     height: 300,     ids: 'a,b,c',     witnesses: 'v1,v2'                }); </eg>

⚓︎

  $('#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>               

⚓︎

<content>
 <classRef key="model.ab"
  maxOccurs="unlimited"/>
</content>

⚓︎

emph
emphasized text (italics)

The TEI began as a conscious attempt to <emph>model</emph>
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 heading

<figure xml:id="figure1">
 <graphic url="img/ives_img_01.png"
  width="768px"
  height="1004px"/>
 <head type="legend">Page-image from Ingelow’s
 <title level="m">Poems</title>
 </head>
</figure>

⚓︎

Figure 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 <foreign xml:lang="fr">par
excellence</foreign> 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 text

<quote source="#quoteref7">Leisure moments only <gap/>
available for its execution</quote>

⚓︎

“Leisure moments only … available for its execution”

gi
the name of an XML element

<gi>quote</gi>

⚓︎

<quote>

graphic
a digital image

<graphic url="img/ives_img_01.png"
 width="768px"
 height="1004px"/>

⚓︎

head
a heading for a text division, figure, table, or list

<div xml:id="futuredirections">
 <head>Future Directions</head>
</div>

⚓︎

4. Future Directions

ident
identifier in a formal language

the new <ident>range()</ident> and <ident>string-range()</ident>
pointers

⚓︎

the new range() and string-range() pointers

list
a list

<list rend="ordered">
 <item>The first misconception is this: digital texts and digital
   archives merely replicate physical texts and physical archives
   in a non-material environment.</item>
 <item>The second misconception is that all possible digital
   representations of a text are created equal.</item>
</list>

⚓︎

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
<mentioned>text</mentioned> and
<mentioned>representation</mentioned>

⚓︎

conversations on the multi-dimensional understanding of text and representation

note
a footnote

A similar suggestion is made in Eric Van der Vlist’s
<title level="m">RELAX NG</title>
<note>
 <p>
  <ref target="http://relaxng/">http://relaxng/</ref>.
 </p>
</note>
(<ref type="bibl"
 target="#vlist04">2004</ref>)

⚓︎

A similar suggestion is made in Eric Van der Vlist’s RELAX NG1 (2004)
Notes

1 http://relaxng/.

ptr
a pointer to another location (internal or external)

The rest of this paper treats each of these points in more detail.
<ptr type="crossref"
 target="#interoperability"/> 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
<q>apprehensive</q>, <q>intimidated</q>, and even
<q>terrified</q>), which explains why one student
commented that TEI training
<q>was not something
I would have sought out on my own.</q>

⚓︎

(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 quotation

<quote source="#quoteref4">Names of authors</quote> appear
in <quote source="#quoteref4">Italic Capitals</quote>
(<ref type="bibl"
 xml:id="quoteref4"
 target="#arber1875">Arber 1875–95, 1:29</ref>).

⚓︎

“Names of authors” appear in “Italic Capitals” (Arber 1875–95, 1:29).

ref
a reference to another location (with custom label text)

<ref target="http://www.tei-c.org/#SATSRN">16.2.5.4 range()</ref>)

⚓︎

16.2.5.4 range())

soCalled
a word from which the author distances herself

There are possible ways (<soCalled>hacks</soCalled>) 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)

<q>Finding what you need can be problematic. Lack of
links to chapters that describe elements next
<supplied>to</supplied> some element definitions</q>

⚓︎

“Finding what you need can be problematic. Lack of links to chapters that describe elements next [to] some element definitions”

table
a table

<table xml:id="table3">
 <head>Allowable <att>rend</att> attribute values in
 <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>)
  <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
 <row>
  <cell role="label">
   <val>ab</val>
  </cell>
  <cell>rendered above the line</cell>
 </row>
 <row>
  <cell role="label">
   <val>al</val>
  </cell>
  <cell>rendered aligned to the left</cell>
 </row>
</table>

⚓︎

Table 4: Allowable @rend attribute values in tei_corset customization

@rend
(renamed @r)
attribute value
Meaning

ab
rendered above the line

al
rendered aligned to the left

tag
a full XML tag

<tag type="empty">rng:ref name="model.pLike"</tag>

⚓︎

<rng:ref name="model.pLike"/>

term
a technical term

Annotations are stored in <term>triple stores</term>
or graph databases like Neo4J

⚓︎

Annotations are stored in triple stores or graph databases like Neo4J

title
the title of a bibliographic work

<title level="a">Where Did All the Document Kids Go?
Open-source, Markup, and the Casual Developer.</title>
Presented at Balisage: The Markup Conference 2013,
Montréal, Canada, August 6–9, 2013. In
<title level="m">Proceedings of Balisage: The Markup
Conference 2013</title>.

⚓︎

“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 <att>preserveOrder</att> taking values
<val>true</val> or
<val>false</val>

⚓︎

an attribute @preserveOrder taking values "true" or "false"

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Journal of the Text-Encoding Initiative Article Schema

Schema and guidelines for encoding an article for the journal

Appendix B §

Previous Appendix A Summary of Elements and their Rendition

Home

Appendix B §

Schema tei_jtei: changed components

Schema tei_jtei: unchanged components

abbr: (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]

appInfo: (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]

att.anchoring: (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.

att.ascribed: provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]

att.ascribed.directed: provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]

att.cmc: (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.

att.datable.w3c: provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates]

att.global: provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]

att.global.responsibility: provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]

att.global.source: provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]

att.notated: provides attributes to indicate any specialised notation used for element content.

att.placement: provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 12.3.1.4. Additions and Deletions]

att.resourced: provides attributes by which a resource (such as an externally held media file) may be located.

att.scope: provides attributes to describe, in general terms, the scope of an element’s application.

att.written: provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]

catRef: (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]

cell: (cell) contains one cell of a table. [15.1.1. TEI Tables]

change: (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]

classCode: (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]

code: contains literal code from some formal language such as a programming language. [23.1.1. Phrase Level Terms]

edition: (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]

eg: (example) contains any kind of illustrative example. [23.5. Element Specifications 23.5.3. Attribute List Specification]

egXML: (example of XML) a single XML fragment demonstrating the use of some XML, such as elements, attributes, or processing instructions, etc., in which the egXML element functions as the root element. [23.1.1. Phrase Level Terms]

email: (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]

encodingDesc: (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]

fileDesc: (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]

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]

gi: (element name) contains the name (generic identifier) of an element. [23. Documentation Elements 23.5. Element Specifications]

hi: (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

item: (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]

keywords: (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]

langUsage: (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]

licence: contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]

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 Description 12.7. Identifying Changes and Revisions]

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. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements]

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]

macro.paraContent: (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]

macro.phraseSeq: (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]

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]

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]

mentioned: marks words or phrases mentioned, not used. [3.3.3. Quotation]

model.addressLike: groups elements used to represent a postal or email address. [1. The TEI Infrastructure]

model.applicationLike: groups elements used to record application-specific information about a document in its header.

model.attributable: groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]

model.availabilityPart: groups elements such as licences and paragraphs of text which may appear as part of an availability statement. [2.2.4. Publication, Distribution, Licensing, etc.]

model.biblLike: groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]

model.biblPart: groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]

model.certLike: groups elements which are used to indicate uncertainty or precision of other elements.

model.cmc: includes the CMC-specific element <post> and makes it available on the divPart level. This allows for using (and combining) occurrences of <post>, <u>, <incident>, and <kinesic> in one and the same div in order to be able to represent the combined use of written and spoken posts, utterances, and nonverbal acts on the GUI of multimodal CMC environments.

model.common: groups common chunk- and inter-level elements. [1.3. The TEI Class System]

model.dateLike: groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates]

model.descLike: groups elements which contain a description of their function.

model.div1Like: groups top-level structural divisions.

model.divBottom: groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]

model.divBottomPart: groups elements which can occur only at the end of a text division. [4.6. Title Pages]

model.divGenLike: groups elements used to represent a structural division which is generated rather than explicitly present in the source.

model.divLike: groups elements used to represent un-numbered generic structural divisions.

model.divPart: groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]

model.divTop: groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]

model.divTopPart: groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]

model.divWrapper: groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]

model.egLike: groups elements containing examples or illustrations. [23.1.1. Phrase Level Terms]

model.emphLike: groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]

model.encodingDescPart: groups elements which may be used inside encodingDesc and appear multiple times.

model.eventLike: groups elements which describe events.

model.frontPart: groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]

model.frontPart.drama: groups elements which appear at the level of divisions within front or back matter of performance texts only. [7.1. Front and Back Matter ]

model.gLike: groups elements used to represent individual non-Unicode characters or glyphs.

model.global: groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]

model.global.edit: groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]

model.global.meta: groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]

model.graphicLike: groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]

model.headLike: groups elements used to provide a title or heading at the start of a text division.

model.highlighted: groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]

model.hiLike: groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]

model.imprintPart: groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]

model.inter: groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]

model.labelLike: groups elements used to gloss or explain other parts of a document.

model.limitedPhrase: groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]

model.listLike: groups list-like elements. [3.8. Lists]

model.lLike: groups elements representing metrical components such as verse lines.

model.lPart: groups phrase-level elements which may appear within verse only. [6.2. Components of the Verse Line]

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

model.milestoneLike: groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements]

model.nameLike: groups elements which name or refer to a person, place, or organization.

model.nameLike.agent: groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

model.noteLike: groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]

model.oddDecl: groups elements which generate declarations in some markup language in ODD documents.

model.offsetLike: groups elements which can appear only as part of a place name. [14.2.3. Place Names]

model.paraPart: groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs]

model.persNamePart: groups elements which form part of a personal name. [14.2.1. Personal Names]

model.personLike: groups elements which provide information about people and their relationships.

model.personPart: groups elements which form part of the description of a person. [16.2.2. The Participant Description]

model.persStateLike: groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.

model.phrase: groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]

model.phrase.xml: groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values. [23. Documentation Elements]

model.placeNamePart: groups elements which form part of a place name. [14.2.3. Place Names]

model.placeStateLike: groups elements which describe changing states of a place.

model.pLike: groups paragraph-like elements.

model.pLike.front: groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]

model.pPart.data: groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

model.pPart.edit: groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]

model.pPart.editorial: groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]

model.pPart.msdesc: groups phrase-level elements used in manuscript description. [11. Manuscript Description]

model.pPart.transcriptional: groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]

model.profileDescPart: groups elements which may be used inside profileDesc and appear multiple times.

model.ptrLike: groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]

model.publicationStmtPart.agency: groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]

model.publicationStmtPart.detail: groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]

model.quoteLike: groups elements used to directly contain quotations.

model.resource: groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]

model.respLike: groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.

model.segLike: groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]

model.sourceDescPart: groups elements which may be used inside sourceDesc and appear multiple times.

model.specDescLike: groups elements for referring to specification elements. [23. Documentation Elements]

model.stageLike: groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]

model.teiHeaderPart: groups high level elements which may appear more than once in a TEI header.

p: (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]

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. [16.2. Contextual Information]

person: (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description]

placeName: (place name) contains an absolute or relative place name. [14.2.3. Place Names]

profileDesc: (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]

projectDesc: (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements]

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]

publisher: (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]

resp: (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

revisionDesc: (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]

row: (row) contains one row of a table. [15.1.1. TEI Tables]

series: (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]

seriesStmt: (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]

soCalled: (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]

sourceDesc: (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]

tagsDecl: (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]

teidata.certainty: defines the range of attribute values expressing a degree of certainty.

teidata.count: defines the range of attribute values used for a non-negative integer value used as a count.

teidata.enumerated: defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.

teidata.gender: defines the range of attribute values used to represent the gender of a person, persona, or character.

teidata.language: defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]

teidata.name: defines the range of attribute values expressed as an XML Name.

teidata.namespace: defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.

teidata.numeric: defines the range of attribute values used for numeric values.

teidata.outputMeasurement: defines a range of values for use in specifying the size of an object that is intended for display.

teidata.pointer: defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.

teidata.probability: defines the range of attribute values expressing a probability.

teidata.probCert: defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.

teidata.sex: defines the range of attribute values used to identify the sex of an organism.

teidata.temporal.w3c: defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.

teidata.text: defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.

teidata.truthValue: defines the range of attribute values used to express a truth value.

teidata.versionNumber: defines the range of attribute values used for version numbers.

teidata.word: defines the range of attribute values expressed as a single word or token.

teidata.xpath: defines attribute values which contain an XPath expression.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

Information about this book

Title statement

jTEI input customization

Ron Van den Branden
ron.vandenbranden@kantl.be

Martin Holmes
mholmes@uvic.ca

Edition statement

Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.

Publication

Source

Originally generated by oddbyexample.xsl, based on analyzing 6 files from file:/F:/ctb/jTEI/jTEIsource/branches/working docs/tei2openedition/oddbyexample. Manually modified thereafter.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <p> (paragraph)

These search results reproduce every example of the use of <p> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <p> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

5. Inline Rhetorical Elements

6. Inline Technical Elements

7. Footnotes

8. Internal Linking

9. External Linking

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

4.4. Quotations, Inline and Block

<p>In his blog post, <title level="a">Text: A Massively Addressable Object</title>,
published in the 2012 anthology <title level="m">Debates in the Digital
   Humanities</title>, Michael Witmore defines texts as objects that are
<quote source="#quoteref3">massively addressable at different levels of scale</quote>
(<ref type="bibl" xml:id="quoteref3"
  target="#witmore12">Witmore 2012, 325</ref>).
</p>

4.4. Quotations, Inline and Block

<p>An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
<quote source="#quoteref1">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<gap/> Where does she go for help?
   Where in the TEI universe is the level of ubiquitous Grade I support?</quote>
(<bibl xml:id="quoteref1">Martin Mueller, pers. comm, Jan. 18, 2013</bibl>).</p>

4.4. Quotations, Inline and Block

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

4.5. Figures and Graphics

<p>As you can see from <ptr target="#titlePage" type="crossref"/>,
the title page is damaged...</p>

4.6. Example Code, XML and non-XML

<p>Links between authors and books are encoded using <gi>link</gi> elements: <egXML
xmlns="http://www.tei-c.org/ns/Examples"> <link target="#middlemarch #eliot"/>
</egXML> </p>

4.7. Tables

<p>As you can see from <ptr target="#table1" type="crossref"/>, the elements included...</p>

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>
 <term>Interoperability</term> may be defined as the property of data that allows
it to be loaded <emph>unmodified</emph> and fully used in a <emph>variety</emph>
of software applications. <term>Interchange</term> is basically the same property
that applies after a preliminary conversion of the data (<ref type="bibl" target="#bauman11">Bauman
   2011</ref>; <ref type="bibl" target="#unsworth11">Unsworth 2011</ref>), 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.
</p>

5. Inline Rhetorical Elements

<p>Unicode is a <emph>character</emph> encoding standard, and is not intended to
standardize ligatures or other presentation forms
(<ref type="bibl" xml:id="quoteref16"
  target="#unicode14">Unicode 2014</ref>).
For example, there is no Unicode character for old Latin <foreign xml:lang="la">sescuncia</foreign>
(like a pound-sign, = one eighth), since it can be composed from <foreign xml:lang="la">semuncia</foreign>
(character 10192) and an EN-dash (<ref type="bibl" target="#unicode06">Unicode 2006, 4</ref>)</p>

5. Inline Rhetorical Elements

<p>The standard definition of metadata as <q>data about data</q> seems to pose more
questions than it answers.</p>

5. Inline Rhetorical Elements

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

6. Inline Technical Elements

6. Inline Technical Elements

<p>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
<val>iou</val> as the value of <att>commodity</att> of <gi>measure</gi> for this purpose.</p>

6. Inline Technical Elements

<p>A range like <code>#range(left(//lb[@n='3']),left(//lb[@n='4']))</code>, however,
could unambiguously address the sequence of nodes comprising line 3, even if the
<gi>lb</gi> happened to be a child of another element that began in the previous line.</p>
<!-- ... -->
<p>For example, <tag type="empty">rng:ref name="model.pLike"</tag> becomes <tag type="empty">classRef key="model.pLike"</tag>.</p>

6. Inline Technical Elements

<p>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 <att>xml:id</att>
attribute (say, <code>xml:id="foo"</code>), and point at the ID using either a
URI with an appended fragment identifier (<val>#foo</val>) or using an attribute
whose type is IDREF.</p>

6. Inline Technical Elements

<p>For example <ident>teidata.duration.iso</ident>, <ident>teidata.outputMeasurement</ident>,
<ident>teidata.pattern</ident>, <ident>teidata.point</ident>, <ident>teidata.version</ident>,
and <ident>teidata.word</ident> all map to the same datatype CDATA in XML DTD, and to
various TEI-defined regular expressions in RELAX NG or W3C Schema.</p>

7. Footnotes

7. Footnotes

<p>There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the <att>match</att> attribute,
<note>
  <p>See <ptr target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/ref-att.scoping.html"/>
  </p>
 </note> and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have <att>xml:id</att> attributes.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

9. External Linking

9. External Linking

<p>More detailed information can be found at <ptr target="http://www.tei-c.org/Vault/P5/2.5.0/doc/tei-p5-doc/en/html/ref-elementSpec.html"/>.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <foreign> (foreign)

These search results reproduce every example of the use of <foreign> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <foreign> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>Unicode is a <emph>character</emph> encoding standard, and is not intended to
standardize ligatures or other presentation forms
(<ref type="bibl" xml:id="quoteref16"
  target="#unicode14">Unicode 2014</ref>).
For example, there is no Unicode character for old Latin <foreign xml:lang="la">sescuncia</foreign>
(like a pound-sign, = one eighth), since it can be composed from <foreign xml:lang="la">semuncia</foreign>
(character 10192) and an EN-dash (<ref type="bibl" target="#unicode06">Unicode 2006, 4</ref>)</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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 Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.written

@hand

Member of

model.emphLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Example

You took the car and did <emph>what</emph>?!!

Show all ⚓︎

Example

<q>What it all comes to is this,</q> he said.
<q>
 <emph>What
   does Christopher Robin do in the morning nowadays?</emph>
</q>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element emph { macro.paraContent }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <emph> (Emphasis (italicization))

These search results reproduce every example of the use of <emph> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <emph> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

5. Inline Rhetorical Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>
 <term>Interoperability</term> may be defined as the property of data that allows
it to be loaded <emph>unmodified</emph> and fully used in a <emph>variety</emph>
of software applications. <term>Interchange</term> is basically the same property
that applies after a preliminary conversion of the data (<ref type="bibl" target="#bauman11">Bauman
   2011</ref>; <ref type="bibl" target="#unsworth11">Unsworth 2011</ref>), 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.
</p>

5. Inline Rhetorical Elements

<p>Unicode is a <emph>character</emph> encoding standard, and is not intended to
standardize ligatures or other presentation forms
(<ref type="bibl" xml:id="quoteref16"
  target="#unicode14">Unicode 2014</ref>).
For example, there is no Unicode character for old Latin <foreign xml:lang="la">sescuncia</foreign>
(like a pound-sign, = one eighth), since it can be composed from <foreign xml:lang="la">semuncia</foreign>
(character 10192) and an EN-dash (<ref type="bibl" target="#unicode06">Unicode 2006, 4</ref>)</p>

5. Inline Rhetorical Elements

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <hi> (highlighted)

These search results reproduce every example of the use of <hi> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <hi> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.notated

@notation

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.biblPart model.quoteLike

Contained by

core: abbr author bibl biblScope cit desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref soCalled term title

figures: cell

header: change edition licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

textstructure: body div

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num p ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

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

Example

Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, <quote>You shall know a word by the company it
keeps</quote>
<ref>(Firth, 1957)</ref>

Show all ⚓︎

Schematron

<sch:rule context="tei:quote">
<sch:assert see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#quotations"
 test="id(substring-after(@source, '#'))/(self::tei:ref[@type eq 'bibl']|self::tei:bibl[ancestor::tei:body])">
 <sch:name/> must have a @source that points to the @xml:id of either a
ref[type='bibl'], or a <bibl> in the <body>. </sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element quote { attribute type { text }?, macro.specialPara }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <quote> (quotation)

These search results reproduce every example of the use of <quote> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <quote> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>In his blog post, <title level="a">Text: A Massively Addressable Object</title>,
published in the 2012 anthology <title level="m">Debates in the Digital
   Humanities</title>, Michael Witmore defines texts as objects that are
<quote source="#quoteref3">massively addressable at different levels of scale</quote>
(<ref type="bibl" xml:id="quoteref3"
  target="#witmore12">Witmore 2012, 325</ref>).
</p>

4.4. Quotations, Inline and Block

<p>An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
<quote source="#quoteref1">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<gap/> Where does she go for help?
   Where in the TEI universe is the level of ubiquitous Grade I support?</quote>
(<bibl xml:id="quoteref1">Martin Mueller, pers. comm, Jan. 18, 2013</bibl>).</p>

4.4. Quotations, Inline and Block

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.ascribed.directed

@toWhom

att.ascribed

@who

att.cmc

@generatedBy

type type⚓︎

Status
Optional

Member of

model.common model.hiLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

textstructure: body div

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num p ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

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

Example

It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element q { attribute type { text }?, macro.specialPara }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <q> (quoted)

These search results reproduce every example of the use of <q> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <q> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>The standard definition of metadata as <q>data about data</q> seems to pose more
questions than it answers.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.quoteLike

Contained by

core: abbr author biblScope desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref soCalled term title

figures: cell

header: change edition licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

textstructure: body div

transcr: supplied

May contain

core: bibl listBibl ptr quote ref

Example

<cit>
 <quote>and the breath of the whale is frequently attended with such an insupportable smell,
   as to bring on disorder of the brain.</quote>
 <bibl>Ulloa's South America</bibl>
</cit>

Show all ⚓︎

Example

<entry>
 <form>
  <orth>horrifier</orth>
 </form>
 <cit type="translation" xml:lang="en">
  <quote>to horrify</quote>
 </cit>
 <cit type="example">
  <quote>elle était horrifiée par la dépense</quote>
  <cit type="translation" xml:lang="en">
   <quote>she was horrified at the expense.</quote>
  </cit>
 </cit>
</entry>

Show all ⚓︎

Example

<cit type="example">
 <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
 <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
  mimeType="audio/wav"/>
 <cit type="translation">
  <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
 </cit>
 <cit type="translation">
  <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
 </cit>
</cit>

Show all ⚓︎

Schematron

<sch:rule context="tei:cit" role="warning">
<sch:assert test="tei:ref"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#quotations">
 <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>

Content model

<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <elementRef key="quote"/>
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>

Schema Declaration

element cit
{
   attribute type { text }?,
   ( quote | model.biblLike | model.ptrLike )+
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cit> (cited block quotation)

These search results reproduce every example of the use of <cit> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <cit> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <mentioned>

These search results reproduce every example of the use of <mentioned> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <mentioned> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <soCalled> (so called)

These search results reproduce every example of the use of <soCalled> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <soCalled> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

5. Inline Rhetorical Elements

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.descLike model.labelLike

Contained by

core: desc emph gap graphic head hi item list listBibl note p q quote ref title

figures: cell

header: application change licence listChange rendition

namesdates: listPerson

textstructure: body div

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign hi label list listBibl mentioned name num ptr q quote ref soCalled term title

figures: table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

character data

Note

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

Example

Example of a desc element inside a documentation element.

<dataSpec module="tei"
 ident="teidata.point">
 <desc versionDate="2010-10-17"
  xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
 <content>
  <dataRef name="token"
   restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
 </content>
<!-- ... -->
</dataSpec>

Show all ⚓︎

Example

Example of a desc element in a non-documentation element.

<place xml:id="KERG2">
 <placeName>Kerguelen Islands</placeName>
<!-- ... -->
 <terrain>
  <desc>antarctic tundra</desc>
 </terrain>
<!-- ... -->
</place>

Show all ⚓︎

Schematron
A desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.limitedContent"/>
</content>

Schema Declaration

element desc { attribute type { text }?, macro.limitedContent }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <desc> (description)

These search results reproduce every example of the use of <desc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <desc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.pointing

@target

att.typed

@type

target target⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.emphLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition keywords language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

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

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

Example

A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.

Show all ⚓︎

Example

We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>

Show all ⚓︎

Example

We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>

Show all ⚓︎

Example

We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element term
{
   attribute target { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <term> (term)

These search results reproduce every example of the use of <term> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <term> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

5. Inline Rhetorical Elements

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>
 <term>Interoperability</term> may be defined as the property of data that allows
it to be loaded <emph>unmodified</emph> and fully used in a <emph>variety</emph>
of software applications. <term>Interchange</term> is basically the same property
that applies after a preliminary conversion of the data (<ref type="bibl" target="#bauman11">Bauman
   2011</ref>; <ref type="bibl" target="#unsworth11">Unsworth 2011</ref>), 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.
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<gap>

<gap> (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.5.3. Additions, Deletions, and Omissions]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.dimensions

att.editLike

reason reason⚓︎
(reason) gives the reason for omission.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

Suggested values include:

cancelled

(cancelled)

deleted

(deleted)

editorial

(editorial) for features omitted from transcription due to editorial policy

illegible

(illegible)

inaudible

(inaudible)

irrelevant

(irrelevant)

sampling

(sampling)

agent agent⚓︎
(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.

Status
Optional

Datatype
teidata.enumerated

Sample values include:

rubbing

(rubbing) damage results from rubbing of the leaf edges

mildew

(mildew) damage results from mildew on the leaf surface

smoke

(smoke) damage results from smoke

Member of

model.global.edit

Contained by

core: abbr author bibl biblScope date editor email emph foreign head hi item label list mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell table

header: change classCode edition language licence

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

textstructure: back body div front text

transcr: supplied

May contain

core: desc

Note

The 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 12.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.

Example

<gap quantity="4" unit="chars"
 reason="illegible"/>

Show all ⚓︎

Example

<gap quantity="1" unit="essay"
 reason="sampling"/>

Show all ⚓︎

Example

<del>
 <gap atLeast="4" atMost="8" unit="chars"
  reason="illegible"/>
</del>

Show all ⚓︎

Example

<gap extent="several lines" reason="lost"/>

Show all ⚓︎

Schematron

<sch:rule context="tei:gap">
<sch:report test="following-sibling::node()[1][self::text()] and starts-with(following-sibling::node()[1], '.')"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#inline_rhetorical"> 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+$')]"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#inline_rhetorical"> A <sch:name/> should follow a period directly, without preceding whitespace.
</sch:report>
</sch:rule>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>

Schema Declaration

element gap
{
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { teidata.enumerated }?,
   ( model.descLike | model.certLike )*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gap> (gap)

These search results reproduce every example of the use of <gap> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <gap> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
<quote source="#quoteref1">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<gap/> Where does she go for help?
   Where in the TEI universe is the level of ubiquitous Grade I support?</quote>
(<bibl xml:id="quoteref1">Martin Mueller, pers. comm, Jan. 18, 2013</bibl>).</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.editLike

att.personal

att.naming

@role

att.typed

@type

role role⚓︎

Status
Optional

notAfter notAfter⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.nameLike.agent model.personPart

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp respStmt soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

Example

<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element name
{
   attribute role { text }?,
   attribute notAfter { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <name> (name, proper noun)

These search results reproduce every example of the use of <name> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <name> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <email> (electronic mail address)

These search results reproduce every example of the use of <email> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <email> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎
indicates 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’).

Status
Optional

Datatype
teidata.enumerated

Suggested values include:

cardinal

absolute number, e.g. 21, 21.5

ordinal

ordinal number, e.g. 21st

fraction

fraction, e.g. one half or three-quarters

percentage

a percentage

Note

If a different typology is desired, other values can be used for this attribute.

value value⚓︎
supplies the value of the number in standard form.

Status
Optional

Datatype
teidata.numeric

Values
a numeric value.

Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of

model.measureLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The num element is intended for use in simple applications.

Example

<p>I reached <num type="cardinal" value="21">twenty-one</num> on
my <num type="ordinal" value="21">twenty-first</num> birthday</p>
<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
 </num> cm per second.</p>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element num
{
   attribute type
   {
      "cardinal" | "ordinal" | "fraction" | "percentage" | teidata.enumerated
   }?,
   attribute value { teidata.numeric }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <num> (number)

These search results reproduce every example of the use of <num> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <num> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.dimensions

att.editLike

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.dateLike model.publicationStmtPart.detail

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence publicationStmt rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr date email emph foreign gap graphic hi lb mentioned name note num ptr q ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

<date when="1980-02">early February 1980</date>

Show all ⚓︎

Example

Given on the <date when="1977-06-12">Twelfth Day
of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
the Two Hundredth and first and of the University the Eighty-Sixth.</date>

Show all ⚓︎

Example

<date when="1990-09">September 1990</date>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element date
{
   attribute type { text }?,
   ( text | model.gLike | model.phrase | model.global )*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <date> (date)

These search results reproduce every example of the use of <date> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <date> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

8. Internal Linking

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <abbr> (abbreviation)

These search results reproduce every example of the use of <abbr> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <abbr> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.pointing

@target

att.typed

@type

target target⚓︎

Status
Required

type type⚓︎

Status
Optional

Legal values are:

crossref

(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 of

model.ptrLike

Contained by

core: abbr author bibl biblScope cit date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell

header: application change classCode edition language licence publicationStmt rendition

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

transcr: supplied

May contain
Empty element

Note

The target and cRef attributes are mutually exclusive.

Example

<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>

Show all ⚓︎

Schematron

<sch:rule context="tei:ptr[not(@type='crossref')]">
<sch:report test="count(tokenize(normalize-space(@target), '\s+')) > 1"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#internal_linking"> Multiple
values in @target are only allowed for <sch:name/>[@type='crossref'].
</sch:report>
</sch:rule>

Schematron

<sch:rule context="tei:ptr">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
</sch:rule>

Content model

<content>
 <empty/>
</content>

Schema Declaration

element ptr
{
   attribute target { text },
   attribute type { "crossref" }?,
   empty
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ptr> (pointer)

These search results reproduce every example of the use of <ptr> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ptr> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

7. Footnotes

8. Internal Linking

9. External Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.5. Figures and Graphics

<p>As you can see from <ptr target="#titlePage" type="crossref"/>,
the title page is damaged...</p>

4.7. Tables

<p>As you can see from <ptr target="#table1" type="crossref"/>, the elements included...</p>

7. Footnotes

7. Footnotes

<p>There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the <att>match</att> attribute,
<note>
  <p>See <ptr target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/ref-att.scoping.html"/>
  </p>
 </note> and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have <att>xml:id</att> attributes.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

9. External Linking

9. External Linking

<p>More detailed information can be found at <ptr target="http://www.tei-c.org/Vault/P5/2.5.0/doc/tei-p5-doc/en/html/ref-elementSpec.html"/>.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.pointing

@target

att.typed

@type

target target⚓︎

Status
Required

type type⚓︎

Status
Optional

Legal values are:

crossref

(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">.

bibl

(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 of

model.ptrLike

Contained by

core: abbr author bibl biblScope cit date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell

header: application change classCode edition language licence publicationStmt rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

The target and cRef attributes are mutually exclusive.

Example

See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
sentence</ref>

Show all ⚓︎

Example

See also <ref target="#locution">s.v. <term>locution</term>
</ref>.

Show all ⚓︎

Schematron

<sch:rule context="tei:ref">
<sch:report test="count(tokenize(normalize-space(@target), '\s+')) > 1"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#external_linking">
 <sch:name/> with multiple values for @target is not supported. </sch:report>
</sch:rule>

Schematron

<sch:rule context="tei:ref[@type eq 'bibl']">
<sch:assert test="not(matches(., '^\(.*\)$'))"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#internal_linking"> 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])"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#internal_linking"> A bibliographic reference must point with a @target to the @xml:id of an entry in the div[@type="bibliography"].
</sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:ref[id(substring-after(@target, '#'))/self::tei:bibl]">
<sch:assert test="@type eq 'bibl'"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#internal_linking" sqf:fix="bibltype.add"> A bibliographic reference must be typed as @type="bibl".
</sch:assert>
<sqf:fix id="bibltype.add">
 <sqf:description>
  <sqf:title>Add @type='bibl'.</sqf:title>
 </sqf:description>
 <sqf:add match="." node-type="attribute"
  target="type" select="'bibl'"/>
</sqf:fix>
</sch:rule>

Schematron

<sch:rule context="tei:ref">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
</sch:rule>

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element ref
{
   attribute target { text },
   attribute type { "crossref" | "bibl" }?,
   macro.paraContent
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ref> (reference)

These search results reproduce every example of the use of <ref> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ref> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

5. Inline Rhetorical Elements

8. Internal Linking

9. External Linking

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>In his blog post, <title level="a">Text: A Massively Addressable Object</title>,
published in the 2012 anthology <title level="m">Debates in the Digital
   Humanities</title>, Michael Witmore defines texts as objects that are
<quote source="#quoteref3">massively addressable at different levels of scale</quote>
(<ref type="bibl" xml:id="quoteref3"
  target="#witmore12">Witmore 2012, 325</ref>).
</p>

4.4. Quotations, Inline and Block

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

5. Inline Rhetorical Elements

5. Inline Rhetorical Elements

<p>
 <term>Interoperability</term> may be defined as the property of data that allows
it to be loaded <emph>unmodified</emph> and fully used in a <emph>variety</emph>
of software applications. <term>Interchange</term> is basically the same property
that applies after a preliminary conversion of the data (<ref type="bibl" target="#bauman11">Bauman
   2011</ref>; <ref type="bibl" target="#unsworth11">Unsworth 2011</ref>), 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.
</p>

5. Inline Rhetorical Elements

<p>Unicode is a <emph>character</emph> encoding standard, and is not intended to
standardize ligatures or other presentation forms
(<ref type="bibl" xml:id="quoteref16"
  target="#unicode14">Unicode 2014</ref>).
For example, there is no Unicode character for old Latin <foreign xml:lang="la">sescuncia</foreign>
(like a pound-sign, = one eighth), since it can be composed from <foreign xml:lang="la">semuncia</foreign>
(character 10192) and an EN-dash (<ref type="bibl" target="#unicode06">Unicode 2006, 4</ref>)</p>

5. Inline Rhetorical Elements

<p>There are possible ways (<soCalled>hacks</soCalled>) 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 <emph>future</emph>, 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; <ref target="http://www.measuringworth.com/">Measuring Worth</ref>
provides calculators for determining values in some historical currencies). A
project could consistently use the <mentioned>comments</mentioned>, <mentioned>memo</mentioned>,
or <mentioned>notes</mentioned> field to record pointers into the attesting document.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

9. External Linking

9. External Linking

<item>addresses the range between two points (<ref target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/SA.html#SATSRN">16.2.5.4 range()</ref>)</item>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

rend rend⚓︎
describes the way the list should be rendered.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

Legal values are:

bulleted

(A bulleted list) Bulleted lists will appear with each item preceded by a leading dot.

inline

(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.

ordered

(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.

simple

(A simple list (no bullets or numbers)) Items in a simple list will be rendered with no bullet or preceding number at all.

type type⚓︎
(type) describes the nature of the items in the list.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

gloss

Note

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

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

Member of

model.listLike

Contained by

core: desc emph head hi item note p q quote ref title

figures: cell

header: change keywords licence rendition revisionDesc sourceDesc

textstructure: back body div

transcr: supplied

May contain

core: desc gap head item label lb note

figures: figure

Note

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

Schematron

<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>

Schema Declaration

element list
{
   attribute rend
   {
      list { ( "bulleted" | "inline" | "ordered" | "simple" )+ }
   }?,
   attribute type { "gloss" }?,
   (
      ( model.divTop | model.global | desc* )*,
      (
         ( ( item, model.global* )+ )
       | (
            headLabel?,
            headItem?,
            ( ( label, model.global*, item, model.global* )+ )
         )
      ),
      ( ( model.divBottom, model.global* )* )
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <list> (list)

These search results reproduce every example of the use of <list> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <list> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

4.3. Lists

<list type="gloss">
 <label>compressor</label>
 <item>a device which reduces the peaks of volume in an audio signal</item>
 <label>equalizer</label>
 <item>a device which allows different frequency bands in an audio signal
   to be cut or boosted</item>
</list>

4.3. Lists

<list rend="bulleted">
 <item>compressor:
 <list rend="ordered">
   <item>limiter</item>
   <item>multiband compressor</item>
  </list>
 </item>
 <item>equalizer:
 <list rend="ordered">
   <item>graphic equalizer</item>
   <item>parametric equalizer</item>
  </list>
 </item>
</list>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <item> (item)

These search results reproduce every example of the use of <item> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <item> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

9. External Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

4.3. Lists

<list type="gloss">
 <label>compressor</label>
 <item>a device which reduces the peaks of volume in an audio signal</item>
 <label>equalizer</label>
 <item>a device which allows different frequency bands in an audio signal
   to be cut or boosted</item>
</list>

4.3. Lists

<list rend="bulleted">
 <item>compressor:
 <list rend="ordered">
   <item>limiter</item>
   <item>multiband compressor</item>
  </list>
 </item>
 <item>equalizer:
 <list rend="ordered">
   <item>graphic equalizer</item>
   <item>parametric equalizer</item>
  </list>
 </item>
</list>

9. External Linking

9. External Linking

<item>addresses the range between two points (<ref target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/SA.html#SATSRN">16.2.5.4 range()</ref>)</item>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.placement

@place

att.typed

@type

att.written

@hand

type type⚓︎

Status
Optional

place place⚓︎

Status
Optional

Member of

model.labelLike

Contained by

core: desc emph head hi item list note p q quote ref title

figures: cell

header: application change licence rendition

textstructure: body div

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

<list type="gloss" xml:lang="enm">
 <head xml:lang="en">Vocabulary</head>
 <headLabel xml:lang="en">Middle English</headLabel>
 <headItem xml:lang="en">New English</headItem>
 <label>nu</label>
 <item xml:lang="en">now</item>
 <label>lhude</label>
 <item xml:lang="en">loudly</item>
 <label>bloweth</label>
 <item xml:lang="en">blooms</item>
 <label>med</label>
 <item xml:lang="en">meadow</item>
 <label>wude</label>
 <item xml:lang="en">wood</item>
 <label>awe</label>
 <item xml:lang="en">ewe</item>
 <label>lhouth</label>
 <item xml:lang="en">lows</item>
 <label>sterteth</label>
 <item xml:lang="en">bounds, frisks (cf. <cit>
   <ref>Chaucer, K.T.644</ref>
   <quote>a courser, <term>sterting</term>as the fyr</quote>
  </cit>
 </item>
 <label>verteth</label>
 <item xml:lang="la">pedit</item>
 <label>murie</label>
 <item xml:lang="en">merrily</item>
 <label>swik</label>
 <item xml:lang="en">cease</item>
 <label>naver</label>
 <item xml:lang="en">never</item>
</list>

Show all ⚓︎

Example

Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
 <label>(1)</label>
 <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
 <label>(2) </label>
 <item>Not a sheet has been seen by any human eyes, excepting those of the author and the
   printer: the faults and the merits are exclusively my own.</item>
</list>

Show all ⚓︎

Example

Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

<list type="gloss">
 <label>March 1757.</label>
 <item>I wrote some critical observations upon Plautus.</item>
 <label>March 8th.</label>
 <item>I wrote a long dissertation upon some lines of Virgil.</item>
 <label>June.</label>
 <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
     amori.</quote>
 </item>
 <label>August.</label>
 <item>I went to Crassy, and staid two days.</item>
</list>

Show all ⚓︎

Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

Example

Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or <lg> element, rather than as a preceding sibling of it.

<p>[...]
<lb/>&amp; n’entrer en mauuais &amp; mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
   entre les Romains.</label>
 <lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p>

Show all ⚓︎

In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

If so desired the type attribute may be used to distinguish different categories of label.

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element label
{
   attribute type { text }?,
   attribute place { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <label> (label)

These search results reproduce every example of the use of <label> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <label> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

4.3. Lists

<list type="gloss">
 <label>compressor</label>
 <item>a device which reduces the peaks of volume in an audio signal</item>
 <label>equalizer</label>
 <item>a device which allows different frequency bands in an audio signal
   to be cut or boosted</item>
</list>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.placement

@place

att.typed

@type

att.written

@hand

type type⚓︎
indicates 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.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

legend

the caption for a figure.

license

licensing information that must be shown alongside the figure.

Member of

model.headLike model.pLike.front

Contained by

core: list listBibl

figures: figure table

namesdates: listPerson

textstructure: back body div front

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

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

Example

The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

<div1 n="I" type="book">
 <head>In the name of Christ here begins the first book of the ecclesiastical history of
   Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
 <div2 type="section">
  <head>In the name of Christ here begins Book I of the history.</head>
  <p>Proposing as I do ...</p>
  <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
     years passed.</p>
  <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
     years from the beginning of the world down to the death of Saint Martin.</trailer>
 </div2>
</div1>

Show all ⚓︎

Example

When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.

<div type="subsection">
 <head place="margin">Secunda conclusio</head>
 <p>
  <lb n="1251"/>
  <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
  </hi>
  <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
   [...]
 </p>
</div>

Show all ⚓︎

Example

The head element is also used to mark headings of other units, such as lists:

With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
 <head>Connectives</head>
 <item>above</item>
 <item>accordingly</item>
 <item>across from</item>
 <item>adjacent to</item>
 <item>again</item>
 <item>
<!-- ... -->
 </item>
</list>

Show all ⚓︎

Schematron

<sch:rule context="tei:head">
<sch:report test="matches(., '^\s*(((figure|fig\.|table|example|ex\.|section) )\d|\d+\.\d?)', 'i')"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#body"> 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')"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#figures"> Figure titles (<head>) must have a type
'legend' or 'license'. </sch:assert>
</sch:rule>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element head
{
   attribute type { "legend" | "license" }?,
   (
      text
    | lg
    | model.gLike
    | model.phrase
    | model.inter
    | model.lLike
    | model.global
   )*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <head> (heading)

These search results reproduce every example of the use of <head> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <head> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

4.5. Figures and Graphics

<figure xml:id="titlePage">
 <graphic url="img/titlePage.png"
  width="620px" height="980px"/>
 <head type="legend">The title page of the 1598 edition</head>
</figure>

4.6. Example Code, XML and non-XML

<figure xml:id="example_code_1">
 <eg> declare function local:getTitles($source as element(div)) as xs:string*{
   for $t in $source//title
   return xs:string($t)
   };
 </eg>
 <head type="legend">A simple XQuery function</head>
</figure>

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.anchoring

@anchored

@targetEnd

att.cmc

@generatedBy

att.placement

@place

att.pointing

@target

att.typed

@type

att.written

@hand

anchored anchored⚓︎

Status
Optional

targetEnd targetEnd⚓︎

Status
Optional

place place⚓︎

Status
Optional

target target⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.noteLike

Contained by

core: abbr author bibl biblScope date editor email emph foreign head hi item label list mentioned name note num p pubPlace publisher q quote ref resp respStmt series soCalled term title

figures: cell table

header: change classCode edition language licence

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

textstructure: back body div front text

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num p ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Example

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" type="gloss"
 resp="#MDMH">
 <term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.

<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>

Show all ⚓︎

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.

Example

The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note n="126" anchored="true"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann.

Show all ⚓︎

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.

Schematron

<sch:rule context="tei:note">
<sch:assert test="not(following::text()[not(ancestor::tei:note)][1][matches(., '^[,\.:;!?\]]')])"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#footnotes"> Footnotes should follow punctuation marks, not precede them. Place
your <<sch:name/>> element after the punctuation mark.
</sch:assert>
</sch:rule>
<sch:rule context="tei:note">
<sch:report test="preceding::text()[not(ancestor::tei:note)][1][matches(., '—$')]"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#footnotes"> Footnotes should precede the dash, not follow it. Place
your <<sch:name/>> element before the dash.
</sch:report>
</sch:rule>
<sch:rule context="tei:note" role="warning">
<sch:report test="following::text()[not(ancestor::tei:note)][1][matches(normalize-space(), '^\)')]"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#footnotes"> Footnotes may be placed before closing parentheses, though this is
exceptional. Please check if this note's placement is correct.
Otherwise, move it after the closing parenthesis.
</sch:report>
</sch:rule>
<sch:rule context="tei:note" role="warning">
<sch:report test="descendant::node()[last()][ not(matches(normalize-space(), '(^|[^.?!:;,])[.?!]$')) or preceding-sibling::node()[1]/descendant-or-self::*[last()] [matches(normalize-space(), '[.?!:;,]$')] ]"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#footnotes"> A footnote should end a with a single closing punctuation character.
</sch:report>
</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)"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#footnotes"> No block-level elements (<cit>, <table>, <figure>, <egXML>, <eg>, <list> which do not have the value inline for @rend) are allowed inside <sch:name/>. </sch:report>
</sch:rule>

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element note
{
   attribute anchored { text }?,
   attribute targetEnd { text }?,
   attribute place { text }?,
   attribute target { text }?,
   attribute type { text }?,
   macro.specialPara
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <note> (note)

These search results reproduce every example of the use of <note> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <note> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

7. Footnotes

7. Footnotes

7. Footnotes

<p>There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the <att>match</att> attribute,
<note>
  <p>See <ptr target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/ref-att.scoping.html"/>
  </p>
 </note> and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have <att>xml:id</att> attributes.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.media

@width

@height

att.resourced

@url

att.typed

@type

Member of

model.graphicLike

Contained by

core: abbr author biblScope date editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref soCalled term title

figures: cell figure table

header: change edition licence

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: desc

Note

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

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

Example

<figure>
 <graphic url="fig1.png"/>
 <head>Figure One: The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
</figure>

Show all ⚓︎

Example

<facsimile>
 <surfaceGrp n="leaf1">
  <surface>
   <graphic url="page1.png"/>
  </surface>
  <surface>
   <graphic url="page2-highRes.png"/>
   <graphic url="page2-lowRes.png"/>
  </surface>
 </surfaceGrp>
</facsimile>

Show all ⚓︎

Example

<facsimile>
 <surfaceGrp n="leaf1" xml:id="spi001">
  <surface xml:id="spi001r">
   <graphic type="normal"
    subtype="thumbnail" url="spi/thumb/001r.jpg"/>
   <graphic type="normal" subtype="low-res"
    url="spi/normal/lowRes/001r.jpg"/>
   <graphic type="normal"
    subtype="high-res" url="spi/normal/highRes/001r.jpg"/>
   <graphic type="high-contrast"
    subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/>
   <graphic type="high-contrast"
    subtype="high-res" url="spi/contrast/highRes/001r.jpg"/>
  </surface>
  <surface xml:id="spi001v">
   <graphic type="normal"
    subtype="thumbnail" url="spi/thumb/001v.jpg"/>
   <graphic type="normal" subtype="low-res"
    url="spi/normal/lowRes/001v.jpg"/>
   <graphic type="normal"
    subtype="high-res" url="spi/normal/highRes/001v.jpg"/>
   <graphic type="high-contrast"
    subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/>
   <graphic type="high-contrast"
    subtype="high-res" url="spi/contrast/highRes/001v.jpg"/>
   <zone xml:id="spi001v_detail01">
    <graphic type="normal"
     subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/>
    <graphic type="normal"
     subtype="low-res"
     url="spi/normal/lowRes/001v-detail01.jpg"/>
    <graphic type="normal"
     subtype="high-res"
     url="spi/normal/highRes/001v-detail01.jpg"/>
    <graphic type="high-contrast"
     subtype="low-res"
     url="spi/contrast/lowRes/001v-detail01.jpg"/>
    <graphic type="high-contrast"
     subtype="high-res"
     url="spi/contrast/highRes/001v-detail01.jpg"/>
   </zone>
  </surface>
 </surfaceGrp>
</facsimile>

Show all ⚓︎

Schematron

<sch:rule context="tei:graphic">
<sch:assert test="matches(@width, '\d+px') and matches(@height, '\d+px')"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#figures"> 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"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#figures">
 <sch:name/> may only occur inside <figure>. </sch:assert>
</sch:rule>

Content model

<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>

Schema Declaration

element graphic { model.descLike* }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <graphic> (graphic)

These search results reproduce every example of the use of <graphic> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <graphic> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.5. Figures and Graphics

<figure xml:id="titlePage">
 <graphic url="img/titlePage.png"
  width="620px" height="980px"/>
 <head type="legend">The title page of the 1598 edition</head>
</figure>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.milestoneLike

Contained by

core: abbr author bibl biblScope date editor email emph foreign head hi item label list listBibl mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell table

header: change classCode edition language licence

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

textstructure: back body div front text

transcr: supplied

May contain
Empty element

Note

By 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 the beginning of each new topographic line on a manuscript or printed page, at the point where it occurs; 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 beginning in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the beginning of the new topographic line is word-breaking, or to note the source from which it derives.

Example

This example shows the encoding of the beginning of each new topographic line within a metrical line, indicating where it occurs in both the 1667 and 1674 editions:

<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>

Show all ⚓︎

Example

This example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line does not (as elsewhere) mark the start of a new word.

<titlePart>
 <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart>

Show all ⚓︎

Content model

<content>
 <empty/>
</content>

Schema Declaration

element lb { attribute type { text }?, empty }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <lb> (line beginning)

These search results reproduce every example of the use of <lb> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <lb> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

8. Internal Linking

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <series> (series information)

These search results reproduce every example of the use of <series> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <series> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.naming

@role

role role⚓︎

Status
Optional

Member of

model.respLike

Contained by

core: bibl

header: titleStmt

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

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

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

Example

<author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
 <persName>Beaumont, Francis</persName>
and
<persName>John Fletcher</persName>
</author>
<author>
 <orgName key="BBC">British Broadcasting
   Corporation</orgName>: Radio 3 Network
</author>

Show all ⚓︎

Schematron

<sch:rule context="tei:titleStmt/tei:author">
<sch:assert test="tei:name and tei:affiliation and tei:email"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#structure"> Author information in the <titleStmt> must include <name>, <affiliation> and <email>.
</sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element author { attribute role { text }?, macro.phraseSeq }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <author> (author)

These search results reproduce every example of the use of <author> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <author> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

8. Internal Linking

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.naming

@role

role role⚓︎

Status
Optional

Legal values are:

translator

guest

chief

managing

technical

Member of

model.respLike

Contained by

core: bibl series

header: seriesStmt

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

A consistent format should be adopted.

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

Example

<editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element editor
{
   attribute role
   {
      "translator" | "guest" | "chief" | "managing" | "technical"
   }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <editor>

These search results reproduce every example of the use of <editor> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <editor> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

8. Internal Linking

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Member of

model.respLike

Contained by

core: bibl series

header: seriesStmt

May contain

core: name note resp

namesdates: orgName

Example

<respStmt>
 <resp>transcribed from original ms</resp>
 <persName>Claus Huitfeldt</persName>
</respStmt>

Show all ⚓︎

Example

<respStmt>
 <resp>converted to XML encoding</resp>
 <name>Alan Morrison</name>
</respStmt>

Show all ⚓︎

Schematron

<sch:rule context="tei:respStmt">
<sch:assert test="ancestor::tei:sourceDesc">
 <sch:name/> can only be used in the context of sourceDesc.
</sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>

Schema Declaration

element respStmt
{
   ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
   note*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <respStmt> (statement of responsibility)

These search results reproduce every example of the use of <respStmt> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <respStmt> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <resp> (responsibility)

These search results reproduce every example of the use of <resp> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <resp> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.typed

@type

level level⚓︎
indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

a

(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.

m

(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works

j

(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper

s

(series) the title applies to a series of otherwise distinct publications such as a collection

u

(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)

Note

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

type type⚓︎
classifies the title according to some convenient typology.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

main

(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.

sub

(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.

Note

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

Member of

model.emphLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell

header: change classCode edition language licence rendition seriesStmt titleStmt

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

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

Example

<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>

Show all ⚓︎

Example

<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>

Show all ⚓︎

Example

<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element title
{
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   attribute type { "main" | "sub" }?,
   macro.paraContent
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <title> (title)

These search results reproduce every example of the use of <title> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <title> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>In his blog post, <title level="a">Text: A Massively Addressable Object</title>,
published in the 2012 anthology <title level="m">Debates in the Digital
   Humanities</title>, Michael Witmore defines texts as objects that are
<quote source="#quoteref3">massively addressable at different levels of scale</quote>
(<ref type="bibl" xml:id="quoteref3"
  target="#witmore12">Witmore 2012, 325</ref>).
</p>

4.4. Quotations, Inline and Block

<p>In <title level="a">Wampum as Hypertext</title>, 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:
<cit>
  <quote source="#quoteref8">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.</quote>
  <ref type="bibl" xml:id="quoteref8"
   target="#haas07">Haas 2007, 93</ref>
 </cit>
</p>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <publisher> (publisher)

These search results reproduce every example of the use of <publisher> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <publisher> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

8. Internal Linking

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.citing

@unit

type type⚓︎

Status
Optional

unit unit⚓︎

Status
Optional

Legal values are:

chapter

issue

page

part

volume

Member of

model.imprintPart

Contained by

core: bibl series

header: seriesStmt

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

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

Example

<biblScope>pp 12–34</biblScope>
<biblScope unit="page" from="12" to="34"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element biblScope
{
   attribute type { text }?,
   attribute unit { "chapter" | "issue" | "page" | "part" | "volume" }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <biblScope> (scope of bibliographic reference)

These search results reproduce every example of the use of <biblScope> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <biblScope> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.naming

@role

role role⚓︎

Status
Optional

Member of

model.imprintPart model.publicationStmtPart.detail

Contained by

core: bibl

header: publicationStmt

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element pubPlace { attribute role { text }?, macro.phraseSeq }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pubPlace> (publication place)

These search results reproduce every example of the use of <pubPlace> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <pubPlace> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

8. Internal Linking

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.biblLike model.biblPart

Contained by

core: bibl cit desc emph head hi item listBibl note p q quote ref title

figures: cell

header: change licence rendition sourceDesc

namesdates: person

textstructure: body div

transcr: supplied

May contain

core: abbr author bibl biblScope date editor email emph foreign gap hi lb mentioned name note num ptr pubPlace publisher q quote ref respStmt series soCalled term title

figures: figure

header: availability edition idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: code ident

transcr: supplied

character data

Note

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

Example

<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl>

Show all ⚓︎

Example

<bibl>
 <title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
 <date>1968</date>.
</bibl>

Show all ⚓︎

Example

<bibl type="article" subtype="book_chapter"
 xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>

Show all ⚓︎

Schematron

<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:bibl"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back" 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:assert test="key('idrefs', @xml:id)/parent::tei:ref[@type='bibl']"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back"> This bibliographic entry is an orphan: no ref[@type="bibl"] references to it occur in the text.
</sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:bibl"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back" role="warning">
<sch:report test="descendant::node()[last()][ not(matches(normalize-space(), '(^|[^.?!:;,])\.$')) or preceding-sibling::node()[1]/descendant-or-self::*[last()] [matches(normalize-space(), '[.?!:;,]$')] ]"> A bibliographic entry should end with a single period.
</sch:report>
</sch:rule>

Schematron

<sch:rule context="tei:bibl/tei:title[@level='j']"
 role="warning">
<sch:report test="self::*[preceding-sibling::*[1]/self::tei:title[@level='a']] [not(preceding-sibling::node()[normalize-space()][1][matches(normalize-space(), '[.,!?]$')])] "
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back"> An analytic title and a journal title in a bibliographic entry should only be separated by a comma or a period (or the end punctuation of the analytic title).
</sch:report>
</sch:rule>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element bibl
{
   attribute type { text }?,
   (
      text
    | model.gLike
    | model.highlighted
    | model.pPart.data
    | model.pPart.edit
    | model.segLike
    | model.ptrLike
    | model.biblPart
    | model.global
   )*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <bibl> (bibliographic citation)

These search results reproduce every example of the use of <bibl> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <bibl> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.4. Quotations, Inline and Block

<p>An exchange on the TEI electronic mailing list sparked the research published
in this article, when a community expert wrote that given
<quote source="#quoteref1">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<gap/> Where does she go for help?
   Where in the TEI universe is the level of ubiquitous Grade I support?</quote>
(<bibl xml:id="quoteref1">Martin Mueller, pers. comm, Jan. 18, 2013</bibl>).</p>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]

Module
core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.biblLike model.frontPart

Contained by

core: cit desc emph head hi item listBibl note p q quote ref title

figures: cell

header: change licence rendition sourceDesc

namesdates: person

textstructure: back body div front

transcr: supplied

May contain

core: bibl desc head lb listBibl

Example

<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>

Show all ⚓︎

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>

Schema Declaration

element listBibl
{
   attribute type { text }?,
   (
      model.headLike*,
      desc*,
      ( model.milestoneLike | relation | listRelation )*,
      (
         (
            model.biblLike+,
            ( model.milestoneLike | relation | listRelation )*
         )+
      )
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <listBibl> (citation list)

These search results reproduce every example of the use of <listBibl> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <listBibl> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

8. Internal Linking

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <particDesc> (participation description)

These search results reproduce every example of the use of <particDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <particDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<table>

<table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]

Module
figures

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

rows rows⚓︎
(rows) indicates the number of rows in the table.

Status
Optional

Datatype
teidata.count

Note

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

Rows should be presented from top to bottom.

cols cols⚓︎
(columns) indicates the number of columns in each row of the table.

Status
Optional

Datatype
teidata.count

Note

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

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

Member of

model.listLike

Contained by

core: desc emph head hi item note p q quote ref title

figures: cell

header: change licence rendition sourceDesc

textstructure: back body div

transcr: supplied

May contain

core: gap graphic head lb note

figures: figure row

Note

Contains an optional heading and a series of rows.

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

Example

<table rows="4" cols="4">
 <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
 <row role="label">
  <cell role="data"/>
  <cell role="data">Dossing Cribs or Lodging Houses</cell>
  <cell role="data">Beds</cell>
  <cell role="data">Needys or Nightly Lodgers</cell>
 </row>
 <row role="data">
  <cell role="label">Bury St Edmund's</cell>
  <cell role="data">5</cell>
  <cell role="data">8</cell>
  <cell role="data">128</cell>
 </row>
 <row role="data">
  <cell role="label">Thetford</cell>
  <cell role="data">3</cell>
  <cell role="data">6</cell>
  <cell role="data">36</cell>
 </row>
 <row role="data">
  <cell role="label">Attleboro'</cell>
  <cell role="data">3</cell>
  <cell role="data">5</cell>
  <cell role="data">20</cell>
 </row>
 <row role="data">
  <cell role="label">Wymondham</cell>
  <cell role="data">1</cell>
  <cell role="data">11</cell>
  <cell role="data">22</cell>
 </row>
</table>

Show all ⚓︎

Schematron

<sch:rule context="tei:table">
<sch:assert test="not(ancestor::tei:list)"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#lists"> No tables are allowed inside
lists. </sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="row"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>

Schema Declaration

element table
{
   attribute rows { teidata.count }?,
   attribute cols { teidata.count }?,
   (
      ( model.headLike | model.global )*,
      (
         ( ( row, model.global* )+ )
       | ( ( model.graphicLike, model.global* )+ )
      ),
      ( ( model.divBottom, model.global* )* )
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <table> (table)

These search results reproduce every example of the use of <table> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <table> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <row> (row)

These search results reproduce every example of the use of <row> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <row> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cell> (cell)

These search results reproduce every example of the use of <cell> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <cell> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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. [15.4. Specific Elements for Graphic Images]

Module
figures

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.placement

@place

att.typed

@type

att.written

@hand

place place⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.global

Contained by

core: abbr author bibl biblScope date editor email emph foreign head hi item label list mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell table

header: change classCode edition language licence

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

textstructure: back body div front text

transcr: supplied

May contain

core: graphic head

tagdocs: eg egXML

Example

<figure>
 <graphic url="http://www.example.org/fig1.png"
  width="100px" height="750px"/>
 <head type="legend">The View from the Bridge</head>
 <head type="license">Used with permission</head>
</figure>

Show all ⚓︎

Example

<figure>
 <eg>if ((err = SSLHashSHA1.update(&amp;hashCtx, &amp;serverRandom)) != 0)
   goto fail;
   if ((err = SSLHashSHA1.update(&amp;hashCtx, &amp;signedParams)) != 0)
   goto fail;
   goto fail;
   if ((err = SSLHashSHA1.final(&amp;hashCtx, &amp;hashOut)) != 0)
   goto fail;
 </eg>
 <head type="legend">An embarrassing error for Apple</head>
</figure>

Show all ⚓︎

Example

<figure> <egXML xmlns="http://www.tei-c.org/ns/Examples">
<list rend="bulleted">
<item>Life</item>
<item>The Universe</item>
<item>Everything</item>
</list>
</egXML>
<head type="legend">A book title rendered as a list</head>
</figure>

Show all ⚓︎

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="graphic"/>
   <elementRef key="egXML"/>
   <elementRef key="eg"/>
  </alternate>
  <elementRef key="head" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>

Schema Declaration

element figure
{
   attribute place { text }?,
   attribute type { text }?,
   ( ( graphic | egXML | eg ), head+ )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <figure> (figure)

These search results reproduce every example of the use of <figure> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <figure> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.5. Figures and Graphics

<figure xml:id="titlePage">
 <graphic url="img/titlePage.png"
  width="620px" height="980px"/>
 <head type="legend">The title page of the 1598 edition</head>
</figure>

4.6. Example Code, XML and non-XML

<figure xml:id="example_code_1">
 <eg> declare function local:getTitles($source as element(div)) as xs:string*{
   for $t in $source//title
   return xs:string($t)
   };
 </eg>
 <head type="legend">A simple XQuery function</head>
</figure>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

type type⚓︎

Status
Optional

Contained by

textstructure: TEI

May contain

header: encodingDesc fileDesc profileDesc revisionDesc

Note

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

Example

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

Show all ⚓︎

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>

Schema Declaration

element teiHeader
{
   attribute type { text }?,
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <teiHeader> (TEI header)

These search results reproduce every example of the use of <teiHeader> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <teiHeader> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <fileDesc> (file description)

These search results reproduce every example of the use of <fileDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <fileDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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 Statement 2.2. The File Description]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Contained by

header: fileDesc

May contain

core: author title

Example

<titleStmt>
 <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
 <respStmt>
  <resp>compiled by</resp>
  <name>P.J. Lucas</name>
 </respStmt>
</titleStmt>

Show all ⚓︎

Schematron

<sch:rule context="tei:titleStmt">
<sch:assert test="tei:title[@type = 'main']"
 sqf:fix="type.add"> A title of type "main" is required in <sch:name/>.
</sch:assert>
<sqf:fix id="type.add">
 <sqf:description>
  <sqf:title>Add a @type='main' attribute to the first title.</sqf:title>
 </sqf:description>
 <sqf:add match="tei:title[not(@type='main')][1]"
  node-type="attribute" target="type">main</sqf:add>
</sqf:fix>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="author" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>

Schema Declaration

element titleStmt { title+, author+ }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titleStmt> (title statement)

These search results reproduce every example of the use of <titleStmt> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <titleStmt> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <edition> (edition)

These search results reproduce every example of the use of <edition> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <edition> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <publicationStmt> (publication statement)

These search results reproduce every example of the use of <publicationStmt> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <publicationStmt> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.typed

@type

type type⚓︎
categorizes the identifier, for example as an ISBN, Social Security number, etc.

Status
Optional

Datatype
teidata.enumerated

Suggested values include:

ISBN

International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.

ISSN

International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.

DOI

Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.

URI

Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.

VIAF

A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.

ESTC

English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.

OCLC

OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.

Member of

model.nameLike model.personPart model.publicationStmtPart.detail

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp series soCalled term title

figures: cell

header: change classCode edition idno language licence publicationStmt rendition seriesStmt

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

header: idno

character data

Note

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

Example

<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
 <g ref="#sym"/>345
</idno>

Show all ⚓︎

In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.

Schematron

<sch:rule context="tei:back/tei:div[@type eq 'bibliography']//tei:idno[@type eq 'doi']">
<sch:report test="following-sibling::tei:ref"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back"> 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>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>

Schema Declaration

element idno
{
   attribute type
   {
      "ISBN"
    | "ISSN"
    | "DOI"
    | "URI"
    | "VIAF"
    | "ESTC"
    | "OCLC"
    | teidata.enumerated
   }?,
   ( text | model.gLike | idno )*
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <idno> (identifier)

These search results reproduce every example of the use of <idno> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <idno> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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.]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

status status⚓︎

Status
Optional

Member of

model.biblPart model.publicationStmtPart.detail

Contained by

core: bibl series

header: publicationStmt

May contain

core: p

header: licence

Note

A consistent format should be adopted

Example

<availability status="restricted">
 <p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
 <p>In the public domain</p>
</availability>
<availability status="restricted">
 <p>Available under licence from the publishers.</p>
</availability>

Show all ⚓︎

Example

<availability>
 <licence target="http://opensource.org/licenses/MIT">
  <p>The MIT License
     applies to this document.</p>
  <p>Copyright (C) 2011 by The University of Victoria</p>
  <p>Permission is hereby granted, free of charge, to any person obtaining a copy
     of this software and associated documentation files (the "Software"), to deal
     in the Software without restriction, including without limitation the rights
     to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     copies of the Software, and to permit persons to whom the Software is
     furnished to do so, subject to the following conditions:</p>
  <p>The above copyright notice and this permission notice shall be included in
     all copies or substantial portions of the Software.</p>
  <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
     IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
     FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
     AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
     THE SOFTWARE.</p>
 </licence>
</availability>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>

Schema Declaration

element availability
{
   attribute status { text }?,
   ( model.availabilityPart | model.pLike )+
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <availability> (availability)

These search results reproduce every example of the use of <availability> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <availability> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <licence>

These search results reproduce every example of the use of <licence> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <licence> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <seriesStmt> (series statement)

These search results reproduce every example of the use of <seriesStmt> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <seriesStmt> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sourceDesc> (source description)

These search results reproduce every example of the use of <sourceDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <sourceDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <encodingDesc> (encoding description)

These search results reproduce every example of the use of <encodingDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <encodingDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <projectDesc> (project description)

These search results reproduce every example of the use of <projectDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <projectDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <tagsDecl> (tagging declaration)

These search results reproduce every example of the use of <tagsDecl> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <tagsDecl> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<rendition>

<rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.styleDef

@scheme

scheme scheme⚓︎

Status
Optional

Legal values are:

css

scope scope⚓︎

Status
Optional

selector selector⚓︎
contains 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.

Status
Optional

Datatype
teidata.text

<rendition scheme="css"
 selector="text, front, back, body, div, p, ab">
display: block;
</rendition>

Show all ⚓︎

<rendition scheme="css"
 selector="*[rend*=italic]"> font-style: italic;
</rendition>

Show all ⚓︎

Note

Since 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.

While 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 by

header: tagsDecl

May contain

core: abbr bibl cit date desc email emph foreign hi label list listBibl mentioned name num ptr q quote ref soCalled term title

figures: table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

character data

Example

<tagsDecl>
 <rendition xml:id="r-center" scheme="css">text-align: center;</rendition>
 <rendition xml:id="r-small" scheme="css">font-size: small;</rendition>
 <rendition xml:id="r-large" scheme="css">font-size: large;</rendition>
 <rendition xml:id="initcaps"
  scope="first-letter" scheme="css">font-size: xx-large</rendition>
</tagsDecl>

Show all ⚓︎

Schematron

<sch:rule context="tei:rendition">
<sch:assert test="key('idrefs', @xml:id)[. instance of attribute(rendition)]"> Please remove all <sch:name/> definitions that aren't actually being used in the article.
</sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.limitedContent"/>
</content>

Schema Declaration

element rendition
{
   attribute scheme { "css" }?,
   attribute scope { text }?,
   attribute selector { teidata.text }?,
   macro.limitedContent
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <rendition> (rendition)

These search results reproduce every example of the use of <rendition> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <rendition> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <appInfo> (application information)

These search results reproduce every example of the use of <appInfo> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <appInfo> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<application>

<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.typed

@type

type type⚓︎

Status
Optional

notAfter notAfter⚓︎

Status
Optional

ident ident⚓︎
supplies an identifier for the application, independent of its version number or display name.

Status
Required

Datatype
teidata.name

version version⚓︎
supplies a version number for the application, independent of its identifier or display name.

Status
Required

Datatype
teidata.versionNumber

Member of

model.applicationLike

Contained by

header: appInfo

May contain

core: desc label p ptr ref

Example

<appInfo>
 <application version="1.5"
  ident="ImageMarkupTool1" notAfter="2006-06-01">
  <label>Image Markup Tool</label>
  <ptr target="#P1"/>
  <ptr target="#P2"/>
 </application>
</appInfo>

Show all ⚓︎

This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two ptr elements.

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.labelLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.ptrLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>

Schema Declaration

element application
{
   attribute type { text }?,
   attribute notAfter { text }?,
   attribute ident { teidata.name },
   attribute version { teidata.versionNumber },
   ( model.labelLike+, ( model.ptrLike* | model.pLike* ) )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <application>

These search results reproduce every example of the use of <application> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <application> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <profileDesc> (text-profile description)

These search results reproduce every example of the use of <profileDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <profileDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <langUsage> (language usage)

These search results reproduce every example of the use of <langUsage> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <langUsage> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.scope

@scope

ident ident⚓︎
(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.

Status
Required

Datatype
teidata.language

usage usage⚓︎

Status
Optional

Contained by

header: langUsage

May contain

core: abbr date email emph foreign gap hi lb mentioned name note num ptr q ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

character data

Note

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

Example

<langUsage>
 <language ident="en-US" usage="75">modern American English</language>
 <language ident="az-Arab" usage="20">Azerbaijani in Arabic script</language>
 <language ident="x-lap" usage="05">Pig Latin</language>
</langUsage>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>

Schema Declaration

element language
{
   attribute ident { teidata.language },
   attribute usage { text }?,
   macro.phraseSeq.limited
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <language> (language)

These search results reproduce every example of the use of <language> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <language> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]

Module
header

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Member of

model.profileDescPart

Contained by

header: profileDesc

May contain

header: catRef classCode keywords

Example

<taxonomy>
 <category xml:id="acprose">
  <catDesc>Academic prose</catDesc>
 </category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
 <catRef target="#acprose"/>
 <classCode scheme="http://www.udcc.org">001.9</classCode>
 <keywords scheme="http://authorities.loc.gov">
  <list>
   <item>End of the world</item>
   <item>History - philosophy</item>
  </list>
 </keywords>
</textClass>

Show all ⚓︎

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <elementRef key="keywords"/>
 </sequence>
</content>

Schema Declaration

element textClass { ( classCode | catRef )*, keywords }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <textClass> (text classification)

These search results reproduce every example of the use of <textClass> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <textClass> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <keywords> (keywords)

These search results reproduce every example of the use of <keywords> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <keywords> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <classCode> (classification code)

These search results reproduce every example of the use of <classCode> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <classCode> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <catRef> (category reference)

These search results reproduce every example of the use of <catRef> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <catRef> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <revisionDesc> (revision description)

These search results reproduce every example of the use of <revisionDesc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <revisionDesc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <change> (change)

These search results reproduce every example of the use of <change> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <change> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <listChange>

These search results reproduce every example of the use of <listChange> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <listChange> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]

Module
namesdates

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.editLike

att.personal

att.naming

@role

att.typed

@type

notAfter notAfter⚓︎

Status
Optional

role role⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.nameLike.agent

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp respStmt soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
 <placeName key="PEN">Pennsyla.</placeName> Abolition Society
</orgName> [...]

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element orgName
{
   attribute notAfter { text }?,
   attribute role { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <orgName> (organization name)

These search results reproduce every example of the use of <orgName> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <orgName> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names]

Module
namesdates

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.personal

att.naming

@role

att.typed

@type

role role⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.persNamePart

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

<surname type="combine">St John Stevas</surname>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element surname
{
   attribute role { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <surname> (surname)

These search results reproduce every example of the use of <surname> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <surname> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<forename>

<forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names]

Module
namesdates

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.personal

att.naming

@role

att.typed

@type

role role⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.persNamePart

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Example

<persName>
 <roleName>Ex-President</roleName>
 <forename>George</forename>
 <surname>Bush</surname>
</persName>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element forename
{
   attribute role { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <forename> (forename)

These search results reproduce every example of the use of <forename> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <forename> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [14.2.1. Personal Names]

Module
namesdates

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.personal

att.naming

@role

att.typed

@type

role role⚓︎

Status
Optional

type type⚓︎

Status
Optional

Member of

model.persNamePart

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

Example

<persName>
 <forename>William</forename>
 <surname>Poulteny</surname>
 <roleName>Earl of Bath</roleName>
</persName>

Show all ⚓︎

Example

<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
including the Supreme Court justices, required by statute to be “learned in the law.”</p>

Show all ⚓︎

Example

<p>
 <persName ref="#NJF">
  <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
representing the administration, asserted in rebuttal that there was nothing to disavow (...)
<persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
alike, have repeatedly said they must honor.
</p>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element roleName
{
   attribute role { text }?,
   attribute type { text }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <roleName> (role name)

These search results reproduce every example of the use of <roleName> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <roleName> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <placeName> (place name)

These search results reproduce every example of the use of <placeName> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <placeName> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [16.2.2. The Participant Description]

Module
namesdates

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

att.editLike

att.naming

@role

att.typed

@type

notAfter notAfter⚓︎

Status
Optional

role role⚓︎

Status
Optional

type type⚓︎

Status
Optional

Datatype
teidata.enumerated

Sample values include:

sponsor

recommend

discredit

pledged

Member of

model.addressLike model.persStateLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName person placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr cit date email emph foreign gap graphic hi lb mentioned name note num ptr q quote ref soCalled term title

figures: figure

header: idno

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: att code gi ident tag val

transcr: supplied

character data

Note

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

Example

<affiliation>Junior project officer for the US <name type="org">National Endowment for
   the Humanities</name>
</affiliation>

Show all ⚓︎

Example

This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.

<affiliation notAfter="1960-01-01"
 notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation>

Show all ⚓︎

Example

This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.

<affiliation from="1902-01-01"
 to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element affiliation
{
   attribute notAfter { text }?,
   attribute role { text }?,
   attribute type { teidata.enumerated }?,
   macro.phraseSeq
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <affiliation> (affiliation)

These search results reproduce every example of the use of <affiliation> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <affiliation> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

3. Basic Text Structure

3.1. The Header and Metadata

<teiHeader>
 <fileDesc>
  <titleStmt>
   <title type="main">Learning the TEI in a Digital Environment</title>
   <author>
    <name>
     <forename>Stella</forename>
     <surname>Dee</surname>
    </name>
    <affiliation>Stella Dee is currently a <roleName>Research Associate</roleName>
         working to develop e-learning resources for historical languages with the
         Open Philology Project at the <orgName>University of Leipzig</orgName>.
         The research of this article was conducted while studying for a Masters
         degree in digital humanities at King’s College, London.</affiliation>
    <email>dee@informatik.uni-leipzig.de</email>
   </author>
  </titleStmt>
  <publicationStmt>
   <publisher>TEI Consortium</publisher>
   <date>2014</date>
   <idno>Issue 7</idno>
   <availability>
    <licence target="https://creativecommons.org/licenses/by/4.0/">
     <p>For this publication, a Creative Commons Attribution 4.0
           International license has been granted by the author(s), who
           retain full copyright.</p>
    </licence>
   </availability>
  </publicationStmt>
  <sourceDesc>
   <p>No source, born digital.</p>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>OpenEdition Journals -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.</p>
  </projectDesc>
 </encodingDesc>
 <profileDesc>
  <langUsage>
   <language ident="en"/>
  </langUsage>
  <textClass>
   <keywords xml:lang="en">
    <term>pedagogy</term>
    <term>student resources</term>
    <term>survey</term>
    <term>file publication</term>
   </keywords>
  </textClass>
 </profileDesc>
</teiHeader>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <listPerson> (list of persons)

These search results reproduce every example of the use of <listPerson> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <listPerson> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <person> (person)

These search results reproduce every example of the use of <person> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <person> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<att>

<att> (attribute) contains the name of an attribute appearing within running text. [23. Documentation Elements]

Module
tagdocs

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

scheme scheme⚓︎

Status
Optional

Member of

model.phrase.xml

Contained by

core: abbr author biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

XSD Name

Note

As an alternative to using the scheme attribute a namespace prefix may be used. Where both scheme and a prefix are used, the prefix takes precedence.

Example

<p>The TEI defines several <soCalled>global</soCalled> attributes; their names include
<att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>,
and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p>

Show all ⚓︎

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>

Content model

<content>
 <dataRef key="teidata.name"/>
</content>

Schema Declaration

element att { attribute scheme { text }?, teidata.name }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <att> (attribute)

These search results reproduce every example of the use of <att> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <att> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

6. Inline Technical Elements

7. Footnotes

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

6. Inline Technical Elements

6. Inline Technical Elements

<p>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
<val>iou</val> as the value of <att>commodity</att> of <gi>measure</gi> for this purpose.</p>

6. Inline Technical Elements

<p>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 <att>xml:id</att>
attribute (say, <code>xml:id="foo"</code>), and point at the ID using either a
URI with an appended fragment identifier (<val>#foo</val>) or using an attribute
whose type is IDREF.</p>

7. Footnotes

7. Footnotes

<p>There are essentially two pointing mechanisms TEI employs to implement its graph
data structure: XPath, used in the <att>match</att> attribute,
<note>
  <p>See <ptr target="http://www.tei-c.org/Vault/P5/2.2.0/doc/tei-p5-doc/en/html/ref-att.scoping.html"/>
  </p>
 </note> and URIs, which can indicate documents, or (using fragment identifiers)
elements in the current document which have <att>xml:id</att> attributes.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <code>

These search results reproduce every example of the use of <code> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <code> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

6. Inline Technical Elements

6. Inline Technical Elements

6. Inline Technical Elements

<p>A range like <code>#range(left(//lb[@n='3']),left(//lb[@n='4']))</code>, however,
could unambiguously address the sequence of nodes comprising line 3, even if the
<gi>lb</gi> happened to be a child of another element that began in the previous line.</p>
<!-- ... -->
<p>For example, <tag type="empty">rng:ref name="model.pLike"</tag> becomes <tag type="empty">classRef key="model.pLike"</tag>.</p>

6. Inline Technical Elements

<p>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 <att>xml:id</att>
attribute (say, <code>xml:id="foo"</code>), and point at the ID using either a
URI with an appended fragment identifier (<val>#foo</val>) or using an attribute
whose type is IDREF.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <eg> (example)

These search results reproduce every example of the use of <eg> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <eg> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.6. Example Code, XML and non-XML

<figure xml:id="example_code_1">
 <eg> declare function local:getTitles($source as element(div)) as xs:string*{
   for $t in $source//title
   return xs:string($t)
   };
 </eg>
 <head type="legend">A simple XQuery function</head>
</figure>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <egXML> (example of XML)

These search results reproduce every example of the use of <egXML> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <egXML> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gi> (element name)

These search results reproduce every example of the use of <gi> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <gi> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

6. Inline Technical Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

4.6. Example Code, XML and non-XML

<p>Links between authors and books are encoded using <gi>link</gi> elements: <egXML
xmlns="http://www.tei-c.org/ns/Examples"> <link target="#middlemarch #eliot"/>
</egXML> </p>

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

6. Inline Technical Elements

6. Inline Technical Elements

<p>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
<val>iou</val> as the value of <att>commodity</att> of <gi>measure</gi> for this purpose.</p>

6. Inline Technical Elements

<p>A range like <code>#range(left(//lb[@n='3']),left(//lb[@n='4']))</code>, however,
could unambiguously address the sequence of nodes comprising line 3, even if the
<gi>lb</gi> happened to be a child of another element that began in the previous line.</p>
<!-- ... -->
<p>For example, <tag type="empty">rng:ref name="model.pLike"</tag> becomes <tag type="empty">classRef key="model.pLike"</tag>.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ref type="crossref" target="#figure2">The following figure</ref> shows a typical example of such a tag document.
<figure xml:id="figure2">
  <graphic url="img/tagdoc-p2.png"
   width="642px" height="716px"/>
  <head type="legend">Tagdoc for <gi>resp</gi> element in P2.</head>
 </figure>
</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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. [23.1.1. Phrase Level Terms]

Module
tagdocs

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.typed

@type

type type⚓︎

Status
Optional

Member of

model.emphLike

Contained by

core: abbr author bibl biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain
Character data only

Note

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

Example

<ident type="ns">http://www.tei-c.org/ns/Examples</ident>

Show all ⚓︎

Content model

<content>
 <textNode/>
</content>

Schema Declaration

element ident { attribute type { text }?, text }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ident> (identifier)

These search results reproduce every example of the use of <ident> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ident> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

6. Inline Technical Elements

8. Internal Linking

4. Divisions, Paragraphs, Lists and Other Block Elements

4.7. Tables

<table xml:id="table1">
 <head>Elements in <ident>tei_corset</ident> customization</head>
 <row role="label">
  <cell>Module</cell>
  <cell>Elements in <ident>tei_corset</ident>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>textstructure</ident>
  </cell>
  <cell>
   <gi>body</gi>
   <gi>div</gi>
   <gi>TEI</gi>
  </cell>
 </row>
 <row>
  <cell role="label">
   <ident>figures</ident>
  </cell>
  <cell>
   <gi>cell</gi>
   <gi>row</gi>
   <gi>table</gi>
  </cell>
 </row>
 <row>
  <cell cols="2">a sample cell spanning two columns (this was not in the original)</cell>
 </row>
</table>

6. Inline Technical Elements

6. Inline Technical Elements

<p>For example <ident>teidata.duration.iso</ident>, <ident>teidata.outputMeasurement</ident>,
<ident>teidata.pattern</ident>, <ident>teidata.point</ident>, <ident>teidata.version</ident>,
and <ident>teidata.word</ident> all map to the same datatype CDATA in XML DTD, and to
various TEI-defined regular expressions in RELAX NG or W3C Schema.</p>

8. Internal Linking

8. Internal Linking

<p>
 <ptr target="#table2" type="crossref"/> shows allowable <att>rend</att> values and
their equivalent meanings.
</p>
<table xml:id="table2">
 <head>Allowable <att>rend</att> attribute values in <ident>tei_corset</ident>
   customization</head>
 <row role="label">
  <cell>
   <att>rend</att>
   <lb/>(renamed <att>r</att>) <lb/>attribute value</cell>
  <cell>Meaning</cell>
 </row>
<!-- ... -->
</table>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<tag>

<tag> (tag) contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [23. Documentation Elements]

Module
tagdocs

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.typed

@type

type type⚓︎
indicates the type of XML tag intended.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

start

a start-tag, with delimiters < and > is intended

end

an end-tag, with delimiters </ and > is intended

empty

an empty tag, with delimiters < and /> is intended

pi

a pi (processing instruction), with delimiters <? and ?> is intended

comment

a comment, with delimiters <!-- and --> is intended

ms

a marked-section, with delimiters <[CDATA[ and ]]> is intended

scheme scheme⚓︎
supplies the name of the schema in which this tag is defined.

Status
Optional

Datatype
teidata.enumerated

Sample values include:

TEI

(text encoding initiative) This tag is defined as part of the TEI scheme. [Default]

DBK

(docbook) this tag is part of the Docbook scheme.

XX

(unknown) this tag is part of an unknown scheme.

Schematron

HTML

Member of

model.phrase.xml

Contained by

core: abbr author biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain
Character data only

Example

Mark the start of each italicised phrase with a
<tag>hi rend="it"</tag> tag, and its end with a <tag type="end">hi</tag> tag.
<tag type="comment">Example updated on 2008-04-05</tag>

Show all ⚓︎

Schematron

<sch:rule context="tei:tag">
<sch:assert test="not(matches(., '^[<!?-]|[>/?\-]$'))"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#inline_technical"> 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>

Content model

<content>
 <textNode/>
</content>

Schema Declaration

element tag
{
   attribute type { "start" | "end" | "empty" | "pi" | "comment" | "ms" }?,
   attribute scheme { teidata.enumerated }?,
   text
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <tag> (tag)

These search results reproduce every example of the use of <tag> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <tag> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

6. Inline Technical Elements

6. Inline Technical Elements

6. Inline Technical Elements

<p>A range like <code>#range(left(//lb[@n='3']),left(//lb[@n='4']))</code>, however,
could unambiguously address the sequence of nodes comprising line 3, even if the
<gi>lb</gi> happened to be a child of another element that began in the previous line.</p>
<!-- ... -->
<p>For example, <tag type="empty">rng:ref name="model.pLike"</tag> becomes <tag type="empty">classRef key="model.pLike"</tag>.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<val>

<val> (value) contains a single attribute value. [23. Documentation Elements 23.5.3. Attribute List Specification]

Module
tagdocs

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Member of

model.phrase.xml

Contained by

core: abbr author biblScope date desc editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref resp soCalled term title

figures: cell

header: change classCode edition language licence rendition

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain
Character data only

Example

<val>unknown</val>

Show all ⚓︎

Schematron

<sch:rule context="tei:val">
<sch:assert test="not(matches(., concat('^', $quotes, '|', $quotes, '$')))"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#inline_technical"> Attribute value delimiters are not allowed for <sch:name/>: they are completed at processing time via XSLT.
</sch:assert>
</sch:rule>

Content model

<content>
 <textNode/>
</content>

Schema Declaration

element val { text }

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <val> (value)

These search results reproduce every example of the use of <val> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <val> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

6. Inline Technical Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.2. Paragraphs

<p>Thus we introduce the <gi>transferGrp</gi> element, a grouping element somewhat
like <gi>surfaceGrp</gi> but, like <gi>altGrp</gi> or <gi>attList</gi>, with
the ability to assert the relationship among its children rather than just common
features. This is accomplished with an <att>org</att> attribute whose suggested
values include:
<list type="gloss">
  <label>
   <val>group</val>
  </label>
  <item>an unordered set</item>
  <label>
   <val>sequence</val>
  </label>
  <item>a (chronologically) ordered set</item>
  <label>
   <val>choice</val>
  </label>
  <item>only one of the child <gi>transfer</gi>s
     obtained</item>
 </list>
</p>
<p>The following example demonstrates the use of <gi>transferGrp</gi> to indicate a
transaction which is attested in (at least) two source documents which disagree as to
the amount of money involved.</p>

6. Inline Technical Elements

6. Inline Technical Elements

<p>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
<val>iou</val> as the value of <att>commodity</att> of <gi>measure</gi> for this purpose.</p>

6. Inline Technical Elements

<p>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 <att>xml:id</att>
attribute (say, <code>xml:id="foo"</code>), and point at the ID using either a
URI with an appended fragment identifier (<val>#foo</val>) or using an attribute
whose type is IDREF.</p>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.typed

@type

version version⚓︎

Status
Optional

Contained by

textstructure: TEI

May contain

header: teiHeader

textstructure: TEI text

Note

As with all elements in the TEI scheme (except egXML) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example

<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a namespace.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <text>
  <body>
   <p>This is about the shortest TEI document imaginable.</p>
  </body>
 </text>
</TEI>

Show all ⚓︎

Example

<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>

Show all ⚓︎

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>

Schema Declaration

element TEI
{
   attribute version { text }?,
   ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <TEI> (TEI document)

These search results reproduce every example of the use of <TEI> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <TEI> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<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 Structure 16.1. Varieties of Composite Text]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.typed

@type

att.written

@hand

type type⚓︎

Status
Optional

Member of

model.resource

Contained by

textstructure: TEI

May contain

core: gap lb note

figures: figure

textstructure: back body front

Note

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

Example

<text>
 <front>
  <div type="abstract" xml:id="abstract">
   <p>This article is about...</p>
  </div>
 </front>
 <body>
  <div xml:id="intro">
   <head>Introduction</head>
   <p>A great deal of previous research...</p>
  </div>
  <div xml:id="method">
   <head>Method</head>
   <p>This project was undertaken...</p>
  </div>
 </body>
 <back>
  <div type="bibliography">
   <listBibl>
    <bibl>[...]</bibl>
   </listBibl>
  </div>
 </back>
</text>

Show all ⚓︎

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"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#header"> An article must have a keyword list in the header. This should be a list of <term> elements in TEI/teiHeader/profileDesc/textClass/keywords </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']"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#front"> An article must have a
front section with an abstract (div[@type='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"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back"> An article
must have a back section with a bibliography (div[@type='bibliography']). </sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>

Schema Declaration

element text
{
   attribute type { text }?,
   (
      model.global*,
      ( ( front, model.global* )? ),
      ( body | group ),
      model.global*,
      ( ( back, model.global* )? )
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <text> (text)

These search results reproduce every example of the use of <text> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <text> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Contained by

textstructure: text

May contain

core: bibl cit desc gap head label lb list listBibl note p q quote

figures: figure table

namesdates: listPerson

tagdocs: eg egXML

textstructure: div

Example

<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>

Show all ⚓︎

Schematron

<sch:rule context="tei:body[child::tei:div[not(@type=('editorialIntroduction'))]]">
<sch:assert test="count(child::tei:div) gt 1"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#body"> 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>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.common"/>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>

Schema Declaration

element body
{
   ( model.divTop | model.global )*,
   (
      (
         (
            ( ( ( model.divLike | model.divGenLike ), model.global* )+ )
          | (
               ( ( model.common, model.global* )+ ),
               ( ( ( model.divLike | model.divGenLike ), model.global* )* )
            )
         ),
         ( ( model.divBottom, model.global* )* )
      )?
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <body> (text body)

These search results reproduce every example of the use of <body> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <body> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Divisions, Paragraphs, Lists and Other Block Elements

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.divLike

att.placement

@place

att.typed

@type

att.written

@hand

type type⚓︎

Status
Optional

Legal values are:

abstract

(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

(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.

authorNotes

(Author's notes for the article, appearing inside <front>.) If an article includes a section for author notes, it should be as brief as possible, and must appear in the <front> element and nowhere else.)

dedication

(A dedication for the article, appearing inside <front>.) If an article includes a section for a dedication, it should be as brief as possible, and must appear in the <front> element and nowhere else.)

appendix

(Appendix to the article, appearing inside <back>.) Any appendices must appear in the <back> of the article, following the bibliography.

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.

editorialIntroduction

(Editorial introduction, appearing inside <body>.) [Reserved for editors only: 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.]

editorNotes

(Editor notes for the article, appearing inside <front>.) [Reserved for editors only: if an article includes a section for editor notes, it should be as brief as possible, and must appear in the <front> element and nowhere else.]

corrections

(Statement of corrections to the article, appearing inside <front>.) [Reserved for editors only: if an article needs corrections, those must be stated in this section, which must appear in the <front> element and nowhere else.]

Member of

model.divLike

Contained by

textstructure: back body div front

May contain

core: bibl cit desc gap head label lb list listBibl note p q quote

figures: figure table

namesdates: listPerson

tagdocs: eg egXML

textstructure: div

Example

<body>
 <div type="part">
  <head>Fallacies of Authority</head>
  <p>The subject of which is Authority in various shapes, and the object, to repress all
     exercise of the reasoning faculty.</p>
  <div n="1" type="chapter">
   <head>The Nature of Authority</head>
   <p>With reference to any proposed measures having for their object the greatest
       happiness of the greatest number [...]</p>
   <div n="1.1" type="section">
    <head>Analysis of Authority</head>
    <p>What on any given occasion is the legitimate weight or influence to be attached to
         authority [...] </p>
   </div>
   <div n="1.2" type="section">
    <head>Appeal to Authority, in What Cases Fallacious.</head>
    <p>Reference to authority is open to the charge of fallacy when [...] </p>
   </div>
  </div>
 </div>
</body>

Show all ⚓︎

Schematron

<sch:rule context="tei:div[@type = $div.types.front]">
<sch:assert test="parent::tei:front"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#front"> A text division of type <sch:value-of select="@type"/> may only occur inside <front>. </sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:front/tei:div">
<sch:assert test="@type = $div.types.front"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#front"> Only text divisions of type <sch:value-of select="string-join(for $i in $div.types.front return concat(if (index-of($div.types.front, $i) = count($div.types.front)) then 'or ' else (), '"', $i, '"'), ', ')"/> may appear in the <front>.
</sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:div[@type = ('bibliography', 'appendix')]"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back">
<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"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#body"> An editorial introduction (<sch:name/>[@type="editorialIntroduction"]) may only occur inside <body>.
</sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:body//tei:div[not(@type = ('editorialIntroduction'))]">
<sch:assert test="tei:head"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#divs"> A <sch:name/> must contain a <head>. </sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:l//tei:div">
<sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:assert>
</sch:rule>

Schematron

<sch:rule context="tei:div">
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>

Schema Declaration

element div
{
   attribute type
   {
      "abstract"
    | "acknowledgements"
    | "authorNotes"
    | "dedication"
    | "appendix"
    | "bibliography"
    | "editorialIntroduction"
    | "editorNotes"
    | "corrections"
   }?,
   (
      ( model.divTop | model.global )*,
      (
         (
            (
               ( ( ( model.divLike | model.divGenLike ), model.global* )+ )
             | (
                  ( ( ( schemaSpec | model.common ), model.global* )+ ),
                  ( ( ( model.divLike | model.divGenLike ), model.global* )* )
               )
            ),
            ( ( model.divBottom, model.global* )* )
         )?
      )
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div> (text division)

These search results reproduce every example of the use of <div> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Basic Text Structure

4. Divisions, Paragraphs, Lists and Other Block Elements

8. Internal Linking

3. Basic Text Structure

3.4. Back Matter: the Bibliography and Appendices

<div xml:id="bibliography"
 type="bibliography">
 <listBibl>
  <bibl xml:id="aoki07">
   <author>Aoki, Paul M.</author>
   <date>2007</date>.
  <title level="a">Back Stage on the Front Lines: Perspectives and
       Performance in the Combat Information Center</title>. In
  <title level="m">Proceedings of the SIGCHI Conference on
       Human Factors in Computing Systems</title>,
  <biblScope unit="page">717–26</biblScope>. CHI ’07.
  <pubPlace>New York</pubPlace>: <publisher>ACM</publisher>. <ref target="http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735"> http://doi.acm.org.ezproxy.lib.utexas.edu/10.1145/1240624.1240735
   </ref>. doi:<idno type="doi">10.1145/1240624.1240735</idno>.
  </bibl>
  <bibl xml:id="banski10">
   <author>Bański, Piotr</author>. <date>2010</date>.
  <title level="a">Why TEI Stand-off Annotation Doesn’t Quite Work and
       Why You Might Want to Use It Nevertheless</title>. In
  <title level="m">Proceedings of Balisage: The Markup Conference 2010</title>.
  <series>Balisage Series on Markup Technologies</series>,
  <biblScope unit="volume">vol. 5</biblScope>.
     doi:<idno type="doi">10.4242/BalisageVol5.Banski01</idno>.
  </bibl>
  <bibl xml:id="bowers12">
   <author>Bowers, John</author>. <date>2012</date>.
  <title level="a">The Logic of Annotated Portfolios: Communicating the
       Value of <soCalled>Research through Design.</soCalled>
   </title>
   <title level="j">Proceedings of the Designing Interactive Systems
       Conference</title>, <biblScope unit="page">68–77</biblScope>.
  <title level="s">DIS ’12</title>. <pubPlace>New York</pubPlace>:
  <publisher>ACM</publisher>. doi:<idno type="doi">10.1145/2317956.2317968</idno>.
  </bibl>
<!-- ... -->
 </listBibl>
</div>

4. Divisions, Paragraphs, Lists and Other Block Elements

4.1. Divisions

<body>
 <div xml:id="notodd">
  <head>What’s not ODD?</head>
  <p>In the current source of TEI P5, there is extensive use of several different
     XML vocabularies: <list rend="bulleted">
    <item>Examples in TEI P5 are presented as if they belonged to some other
    <soCalled>TEI Example Namespace</soCalled>;</item>
    <item>Element content models are expressed using a subset of RELAX NG, as
         discussed in the previous section;</item>
    <item>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;</item>
    <item>Additional semantic constraints (for example, co-dependence of
         attributes and element content) are expressed using ISO Schematron
         rules.</item>
   </list>
  </p>
  <p>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.</p>
  <div xml:id="elementcontentmodels">
   <head>Element Content Models</head>
   <p>ODD was originally intended to support the <emph>intersection</emph> of the
       content models definable using three different schema languages. In practice,
       this reduced our modeling requirements quite significantly.
<!-- ... -->
   </p>
<!-- ... -->
  </div>
  <div xml:id="datatyping">
   <head>Datatyping and Other Forms of Validation</head>
   <p>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.

<!-- ... -->
   </p>
<!-- ... -->
  </div>
 </div>
</body>

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Contained by

textstructure: text

May contain

core: gap head lb listBibl note p

figures: figure

textstructure: div

Note

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

Example

<front>
 <epigraph>
  <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla
     pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί
       θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>
  </quote>
 </epigraph>
 <div type="dedication">
  <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
  </p>
 </div>
</front>

Show all ⚓︎

Example

<front>
 <div type="dedication">
  <p>To our three selves</p>
 </div>
 <div type="preface">
  <head>Author's Note</head>
  <p>All the characters in this book are purely imaginary, and if the
     author has used names that may suggest a reference to living persons
     she has done so inadvertently. ...</p>
 </div>
</front>

Show all ⚓︎

Example

<front>
 <div type="abstract">
  <div>
   <head> BACKGROUND:</head>
   <p>Food insecurity can put children at greater risk of obesity because
       of altered food choices and nonuniform consumption patterns.</p>
  </div>
  <div>
   <head> OBJECTIVE:</head>
   <p>We examined the association between obesity and both child-level
       food insecurity and personal food insecurity in US children.</p>
  </div>
  <div>
   <head> DESIGN:</head>
   <p>Data from 9,701 participants in the National Health and Nutrition
       Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.
       Child-level food insecurity was assessed with the US Department of
       Agriculture's Food Security Survey Module based on eight
       child-specific questions. Personal food insecurity was assessed with
       five additional questions. Obesity was defined, using physical
       measurements, as body mass index (calculated as kg/m2) greater than
       or equal to the age- and sex-specific 95th percentile of the Centers
       for Disease Control and Prevention growth charts. Logistic
       regressions adjusted for sex, race/ethnic group, poverty level, and
       survey year were conducted to describe associations between obesity
       and food insecurity.</p>
  </div>
  <div>
   <head> RESULTS:</head>
   <p>Obesity was significantly associated with personal food insecurity
       for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to
       2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%
       CI 0.51 to 1.51). Child-level food insecurity was not associated
       with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>
  </div>
  <div>
   <head> CONCLUSIONS:</head>
   <p>Personal food insecurity is associated with an increased risk of
       obesity only in children aged 6 to 11 years. Personal
       food-insecurity measures may give different results than aggregate
       food-insecurity measures in children.</p>
  </div>
 </div>
</front>

Show all ⚓︎

Schematron

<sch:rule context="tei:front">
<sch:assert test="tei:div[@type='abstract']"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#front">
 <sch:name/> must have an abstract (div[@type='abstract']).
</sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0" maxOccurs="1">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>

Schema Declaration

element front
{
   ( 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 )* )? )
      )?
   )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <front> (front matter)

These search results reproduce every example of the use of <front> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <front> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]

Module
textstructure

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

Contained by

textstructure: text

May contain

core: gap head lb list listBibl note p

figures: figure table

namesdates: listPerson

textstructure: div

Note

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

Example

<back>
 <div type="appendix">
  <head>The Golden Dream or, the Ingenuous Confession</head>
  <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets
     and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she
     had like to have been, too fond of Money
<!-- .... -->
  </p>
 </div>
<!-- ... -->
 <div type="epistle">
  <head>A letter from the Printer, which he desires may be inserted</head>
  <salute>Sir.</salute>
  <p>I have done with your Copy, so you may return it to the Vatican, if you please;

<!-- ... -->
  </p>
 </div>
 <div type="advert">
  <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
     Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
  <list>
   <item n="1">The Christmas Box, Price 1d.</item>
   <item n="2">The History of Giles Gingerbread, 1d.</item>
<!-- ... -->
   <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
       10 Vol, Pr. bound 1l.</item>
  </list>
 </div>
 <div type="advert">
  <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.
     Paul's Church-Yard.</head>
  <list>
   <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.
       6d</item>
   <item n="2">Dr. Hooper's Female Pills, 1s.</item>
<!-- ... -->
  </list>
 </div>
</back>

Show all ⚓︎

Schematron

<sch:rule context="tei:back">
<sch:assert test="tei:div[@type='bibliography']/tei:listBibl"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#back">
 <sch:name/> must have a bibliography (div[@type="bibliography"]), which must be
organized inside a <listBibl> element. </sch:assert>
</sch:rule>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>

Schema Declaration

element back
{
   (
      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 )* )? )
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <back> (back matter)

These search results reproduce every example of the use of <back> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <back> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

8. Internal Linking

8. Internal Linking

8. Internal Linking

<p>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 (<ref type="bibl" target="#thomas04">Thomas 2004</ref>).</p>
<!-- ... -->
<back>
 <div type="bibliography">
  <listBibl>
   <bibl xml:id="thomas04">
    <author>Thomas, William G., III</author>. <date>2004</date>.
   <title level="a">Computing and the Historical Imagination</title>:
   <title level="m">A Companion to Digital Humanities</title>, edited by
   <editor>Susan Schreibman</editor>, <editor>Ray Siemens</editor>, and
   <editor>John Unsworth</editor>. <pubPlace>Oxford</pubPlace>:
   <publisher>Blackwell Publishing</publisher>.</bibl>
  </listBibl>
 </div>
</back>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

<supplied>

<supplied> (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. [12.3.3.1. Damage, Illegibility, and Supplied Text]

Module
transcr

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:base

@xml:space

att.global.rendition

@rend

@rendition

att.global.responsibility

@cert

@resp

att.global.source

@source

att.dimensions

att.editLike

reason reason⚓︎
one or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

Member of

model.pPart.transcriptional

Contained by

core: abbr author bibl biblScope date editor email emph foreign head hi item label mentioned name note num p pubPlace publisher q quote ref soCalled term title

figures: cell

header: change edition licence

namesdates: affiliation forename orgName placeName roleName surname

tagdocs: eg

transcr: supplied

May contain

core: abbr bibl cit date desc email emph foreign gap graphic hi label lb list listBibl mentioned name note num ptr q quote ref soCalled term title

figures: figure table

header: idno

namesdates: affiliation forename listPerson orgName placeName roleName surname

tagdocs: att code eg egXML gi ident tag val

transcr: supplied

character data

Note

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

Example

I am dr Sr yr
<supplied reason="illegible"
 source="#amanuensis_copy">very humble Servt</supplied>
Sydney Smith

Show all ⚓︎

Example

<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar

Show all ⚓︎

Schematron

<sch:rule context="tei:supplied">
<sch:assert test="not(matches(., '^\[|\]$'))"
 see="https://tei-c.org/release/doc/tei-p5-exemplars/html/tei_jtei.doc.html#inline_rhetorical"> Please remove square brackets from <sch:name/>: they are completed at processing time via XSLT.
</sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element supplied
{
   attribute reason { list { teidata.enumerated+ } }?,
   macro.paraContent
}

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <supplied> (supplied)

These search results reproduce every example of the use of <supplied> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <supplied> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]

Module
tei

Members
biblScope

Attributes

unit unit⚓︎
identifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.

Status
Optional

Datatype
teidata.enumerated

Suggested values include:

volume

(volume) the element contains a volume number.

issue

the element contains an issue number, or volume and issue numbers.

page

(page) the element contains a page number or page range.

line

the element contains a line number or line range.

chapter

(chapter) the element contains a chapter indication (number and/or title)

part

the element identifies a part of a book or collection.

column

the element identifies a column.

entry

the element identifies an entry number or label in a list of entries.

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work]

Module
tei

Members
affiliation date gap name orgName person placeName supplied

Attributes

Note

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

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

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]

Module
tei

Members
att.global [TEI abbr affiliation appInfo application att author availability back bibl biblScope body catRef cell change cit classCode code date desc div edition editor eg egXML email emph encodingDesc figure fileDesc foreign forename front gap gi graphic head hi ident idno item keywords label langUsage language lb licence list listBibl listChange listPerson mentioned name note num orgName p particDesc person placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher q quote ref rendition resp respStmt revisionDesc roleName row series seriesStmt soCalled sourceDesc supplied surname table tag tagsDecl teiHeader term text textClass title titleStmt val]

Attributes

rend rend⚓︎
(rendition) indicates how the element in question was rendered or presented in the source text.

Status
Optional

Datatype
1–∞ occurrences of teidata.word separated by whitespace

<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>

⚓︎

Note

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

rendition rendition⚓︎
points to a description of the rendering or presentation used for this element in the source text.

Status
Optional

Datatype
1–∞ occurrences of teidata.pointer separated by whitespace

<head rendition="#ac #sc">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi rendition="#normal">New Blazing-World</hi>.
</head>
<!-- elsewhere... -->
<rendition xml:id="sc" scheme="css">font-variant: small-caps</rendition>
<rendition xml:id="normal" scheme="css">font-variant: normal</rendition>
<rendition xml:id="ac" scheme="css">text-align: center</rendition>

⚓︎

Note

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

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

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

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]

Module
tei

Members
catRef licence note ptr ref term

Attributes

target target⚓︎
specifies the destination of the reference by supplying one or more URI References.

Status
Optional

Datatype
1–∞ occurrences of teidata.pointer separated by whitespace

Note

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

Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
</sch:rule>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.styleDef

att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.

Module
tei

Members
rendition

Attributes

scheme scheme⚓︎
identifies the language used to describe the rendition.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

css

Cascading Stylesheet Language

xslfo

Extensible Stylesheet Language Formatting Objects

free

Informal free text description

other

A user-defined rendition description language

Note

If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

Schematron

<sch:rule context="tei:*[@schemeVersion]">
<sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified.
</sch:assert>
</sch:rule>

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists]

Module
tei

Members
TEI abbr affiliation application bibl change cit date desc div figure forename graphic head ident idno label lb list listBibl listChange listPerson name note num orgName placeName ptr quote ref roleName surname table tag term text title

Attributes

type type⚓︎
characterizes the element in some sense, using any convenient classification scheme or typology.

Status
Optional

Datatype
teidata.enumerated

<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l>…</l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</l>
  <l>…</l>
 </lg>
</div>

⚓︎

Note

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

Schematron

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

Note

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

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]

Module
tei

Members
affiliation application author change date editor idno licence name orgName placeName resp title

Attributes

att.datable.w3c

@when

@notBefore

@notAfter

@from

@to

Note

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

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module | tei
Members | date gap supplied
Attributes |

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Module | tei
Members | div
Attributes |

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.media

att.media provides attributes for specifying display and related properties of external media.

Module
tei

Members
graphic

Attributes

width width⚓︎
Where the media are displayed, indicates the display width.

Status
Optional

Datatype
teidata.outputMeasurement

height height⚓︎
Where the media are displayed, indicates the display height.

Status
Optional

Datatype
teidata.outputMeasurement

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms]

Module
tei

Members
att.personal [forename name orgName placeName roleName surname] affiliation author editor pubPlace

Attributes

role role⚓︎
may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names]

Module
tei

Members
forename name orgName placeName roleName surname

Attributes

att.naming

@role

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.

§

Home

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [15. Tables, Formulæ, Graphics, and Notated Music]

Module
figures

Members
cell row

Attributes

role role⚓︎
(role) indicates the kind of information held in this cell or in each cell of this row.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

data

[Default]

label

Note

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

rows rows⚓︎
(rows) indicates the number of rows occupied by this cell or row.

Status
Optional

Datatype
teidata.count

Default
1

Note

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

cols cols⚓︎
(columns) indicates the number of columns occupied by this cell or row.

Status
Optional

Datatype
teidata.count

Default
1

Note

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

TEI Guidelines Originally generated on 2014-01-30T13:29:15Z using oddbyexample.xsl. Progressively modified after that.. This page generated on 2025-01-24T20:00:48Z.