-
Notifications
You must be signed in to change notification settings - Fork 9
textFeatures
This summary table tries to map identifiable features of a novel to the different ways it might be encoded at each of the three levels of ELTeC encoding. Or, to look at it another way, it identifies which annotations you can expect to be provided by an encoded text at each such level.
In this table, omitted means the textual feature is either silently suppressed or commented out in the encoded version; <gap/> means that the presence of the feature is marked by an empty <gap> element but any associated text content is suppressed; unmarked means that the text concerned is retained but no markup distinguishes it from its surroundings.
At every level, every novel is represented by a <TEI> element, containing a <teiHeader> and a <text> element.
Every text has a unique identifier comprising 3 uppercase letters and four digits, e.g. ENG1234. This identifier must be supplied as the value of an xml:id attribute on the root <TEI> element. The primary language of the text must also be specified, using the xml:lang attribute on the same element.
The structure of the TEI Header is the same for each level: for details see this page
The following features are encoded in the same way in every ELTeC text, using the elements indicated:
| Textual Feature | Encoding | Notes |
|---|---|---|
| Page break | <pb/> | @n supplies printed page number; @facs supplies URI of image; supply this if possible; if not supply a page count in the header |
| Authorial preface, foreword, appendix, etc | <div type="liminal"> within <front> or <back> as appropriate | |
| Non-authorial preface etc. | omitted | |
| volume, chapter etc. | <div> nested as necessary within <body> | @type may be chapter, vol, or group (for anything else);@n may indicate original numbering |
| Heading or title | <head> at start of <div>; <trailer> at end | |
| Running title/page footer | omitted | Page number should be included in pb/@n |
| Prose paragraph or list item | <p> | Discard any formatting information |
| Verse line | <l> | Use only for verse lines in display blocks |
The following textual features are treated differently by ELTeC texts of differing levels:
| Textual Feature | Level 0 Encoding | Level 1 Encoding | Notes |
|---|---|---|---|
| Title page | omitted | <div type="titlePage"> within <front> | components are encoded as <p> |
| Table of contents, errata list, other liminal matter | omitted | <gap/> | use @unit and @extent to specify what has been omitted |
| Mid-chapter structural marker | ignored | <milestone/> | use @unit and @rend to describe format |
| Authorial footnote | omitted | <note> and <ref> | transcribe note text within a <note> within <div type="notes"> inside <back>; mark point of attachment with <ref> in text; use @target of <ref> to point to <note> (see example) |
| Font change | <hi> (no attributes) | If possible, replace <hi> with <foreign>, <title>, or<emph> as appropriate | may also use @rend attribute with values ul ro sc it (tbc) |
| Graphic | omitted | <gap unit="graphic"/> | optionally add a comment to describe the content of the graphic |
| Quotation, display block, epigraph etc. | <p> (or series of <l>) | <quote> containing one or more <p> or <l> | note that <lg> is not available |
| Editorial correction | unmarked | <corr> | use wherever encoded text differs from printed original. |
Current versions of the ELTeC schema in RELAX NG are available from the following addresses:
- https://distantreading.github.io/Schema/eltec-0.rng (level 0)
- https://distantreading.github.io/Schema/eltec-1.rng (level 1)
To check whether a text is valid against an ELTeC schema in oXygen, insert a PI like the following at the start of the document:
<?xml-model href="https://distantreading.github.io/Schema/eltec-1.rng" ?>
For authoritative information about the TEI ODD from which the schemas are derived, see
E5C-discussion-paper ELTeC Corpus Composition Criteria Compliance Calculations : draft for discussion
Challenges-on-text-selection Reports on challenges regarding text selection and balancing
Workflow Step-by-step introduction for contributing texts to ELTeC.
Uploading-files-on-GitHub-Step-by-Step How to upload texts on GitHub
textFeatures Table of textual features and their encodings
teiHeaders Instructions for compiling an ELTeC Header
choosingTitles Suggestions on how to select texts for ELTeC
Versioning-Guidelines-for-ELTeC Draft for defining our versioning guidelines.
Filenames and identifiers: A proposal
Please feel free to add ideas and discussion notes
Call-for-Contributions What texts can you contribute?
Example-Texts Add an example here!
ELTeC-List-of-Candidates Draft table for text candidates
Online-Text-Collections Some links to less well known collections