Difference between revisions of "Recommended Practices"
(→Introduction) |
(→div) |
||
| Line 61: | Line 61: | ||
==div== | ==div== | ||
| − | The <front>, <body>, and <back> elements all use the nested <div> structure to organize primary sections as well as child sections. The <div> elements are identified by a unique xml:id, and also have an n attribute to aid in reference. A type attribute is also used to describe the kind of division. Type includes the following values: | + | The <code><front></code>, <code><body></code>, and <code><back></code> elements all use the nested <div> structure to organize primary sections as well as child sections. The <code><div></code> elements are identified by a unique <code>@xml:id</code>, and also have an <code>@n</code> attribute to aid in reference. A <code>@type</code> attribute is also used to describe the kind of division. Type includes the following values: |
<table border="1"> | <table border="1"> | ||
Revision as of 18:59, 19 January 2010
Contents
Introduction
These recommended practices are for publishers intending to use TEI P5 as their encoding schema. They are intended to highlight features necessary for publishing both journal articles and books.
General Recommendations
Introduction
This document describes the specifications for the encoding of textual matter in accordance with the Text Encoding Initiative’s Guidelines for Text Encoding and Interchange (P5)
We will be using the following modules as part of our schema:
- core
- header
- textstructure
- figures
- linking
- analysis
- tagdocs
- namesdates
- textcrit
- verse
- transcr
This is a working document and as such assumes that further explication will be added as the need arises. Not every element nor attribute has been covered in this document, and the TEI online documentation should be able to assist in clarification. When in doubt, the authors of this document will provide updates to ensure best practices.
Basic Structure: Monographs
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="isbn-book">
<teiHeader>
<!-- header goes here -->
</teiHeader>
<text>
<front>
<div type="halftitle">[text]</div>
<titlePage>[text]</titlePage>
<div type="copyright">[text]</div>
<div type="dedication">[text]</div>
<div type="contents">[text]</div>
</front>
<body>
<div type="introduction">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="chapter">[text]</div>
<div type="conclusion">[text]</div>
</body>
<back>
<div type="endnotes">[text]</div>
<div type="bibliography">[text]</div>
<div type="index">[text]</div>
</back>
</text>
</TEI>
text
The <teiHeader> is followed directly by the mandatory <text> element, which contains the textual matter being encoded. The <text> element is broken down into three subelements: <front> for frontmatter, <body> for the main body of the work, and <back> for backmatter. Only the <body> element is required. Additionally, groups of discrete texts can be packaged together in one document using the <group> element as a parent for the separate <text> elements.
div
The <front>, <body>, and <back> elements all use the nested
@xml:id, and also have an @n attribute to aid in reference. A @type attribute is also used to describe the kind of division. Type includes the following values:
| Value | Description |
|---|---|
| copyright | copyright information |
| dedication | dedication |
| contents | table of contents |
| frontispiece | frontispiece |
| acknowledgments | acknowledgments |
| preface | preface |
| introduction | frontmatter or body introduction |
| epigraph | epigraph |
| halftitle | halftitle |
| volume | volume |
| part | part |
| chapter | chapter |
| appendix | appendix |
| endnotes | endnote section |
| glossary | glossary |
| bibliography | bibliography |
| index | index |
| colophon | colophon |
| illustrations | illustrations |
| maps | maps |
| ahead | ahead |
| bhead | bhead |
| chead | chead |
| fmhead | frontmatter head |
| bmhead | backmatter head |
| halftitle | halftitle |
| other | other |
