TEI: The Header and Metadata¶3.1. The Header and Metadata

This is an example 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. 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.

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.

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.

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: