Encoding for ELTeC : a summary guide

The checklist

Here's a list of the information you must supply in your header:

• Identification of title and language (xml:id and xml:lang on <TEI>)
• Title of the work, followed by the phrase : ELTeC edition (<title>)
• Author, in format Surname, Forename/s (birthYear-deathYear) (<author>)
• Statements of responsibility in format encoded by Name (<respStmt>)
• Date of publication in ELTeC (<publicationStmt>)
• Source description containing one or more <bibl> elements
• Encoding level : use the n attribute of <encodingDesc>
• Profile description specifying languages used and sampling criteria values (<langUsage>, <textDesc>)
• Revision description containing at least one <change>

Most but not all requirements are enforced by the schema

Identification

• xml:id values must be unique across the corpus, preferably short, and valid XML names
• recommended format: xxxyyyyd where xxx is ISO 639-3 language code, yyyy the year of publication, and d an extra digit for disambiguation
• the xmlns attribute is needed for TEI conformance
• the value of xml:lang is the ISO 639-2 language code

The title

• Use standard form of title, simplified if necessary, followed by the phrase ELTeC edition in appropriate language
• Optionally supply VIAF or other identifying code for title

The author

• VIAF codes available from https://viaf.org
• Standard forms for names should (or for E Europe may not) include comma
• Alternative name may be provided between names and dates, enclosed in square brackets
• Dates must be separated by hyphen

Check details on Wikipedia, Worldcat, National library etc.

Extent statement

• oXygen will calculate a word count for you
• page and volume counts are optional; wordcount is mandatory
• figures must be supplied without punctuation or spaces

Publication statement

• Nothing is required here: when the text is published on Zenodo, a fuller standard format will be generated
• Any information you supply here will be transfered to a <change> element in the <revisionDesc>

Source description (1)

The ELTeC edition is derived from a known print edition

• Add an extra <bibl type="firstEdition"> if this is not the first edition
• Add an extra <bibl type="digitalSource"> if another digital version of the text is also available e.g. as page images

Source description (2)

The ELTeC edition is derived from a pre-existing digital version which is in turn derived from the first printed edition.

• Add an extra <bibl type="printSource"> if the digital version does not derive from the first edition

Encoding description

• The value for n must be one of eltec-0, eltec-1, or eltec-2
• An empty <p> is required as content :-(
• We may add more here later

Profile description

• Supply a <language> for each language present in significant amounts in the text
• Use ISO 646 three-letter codes to identify the language, optionally extended with script or dialect
• The namespace prefix eltec is arbitrary and can be defined wherever you please
• Values for the four balance criteria must be supplied

Balance criteria

Revision description

• At least one <change> element, typically indicating the date of creation of the ELTeC file, is required
• The when attribute is required and must have value in form YYYY-MM-DD
• Give <change>s in reverse chronological order (most recent first)
• Include only major changes