The following guidelines are the product of a collaboration between Samuel J. Huskey (University of Oklahoma) and Hugh Cayless (Duke Collaboratory for Classical Computing), but many others deserve acknowledgment for their contributions.
Cynthia Damon (University of Pennsylvania) and Robert Kaster (Princeton University) read and commented on the guidelines from their perspectives as editors of critical texts. Their insights into the methods and practices of textual criticism, particularly with regard to terminology, have been invaluable. They also contributed pilot projects for use in evaluating and refining the encoding guidelines. In addition, Robert Kaster devoted considerable time to developing the typology of variant readings in the section "Tagging Readings for Analysis." Since that typology is the basis for a significant feature of the Library of Digital Latin Texts, his efforts deserve special recognition here.
Tom Elliott (Institute for the Study of the Ancient World, New York University) contributed valuable insights and suggestions throughout, but particularly with regard to the sections "People" and "Places."
Jeffrey C. Witt (Loyola University, Maryland) also contributed to the development of these guidelines by sharing the encoding guidelines for his own project, Lombard Press (http://lombardpress.org/).
Jim Ginther (St. Michael's College, University of Toronto), Patrick Cuba (St. Louis University), Joshua D. Sosin (Duke University), and Jeffrey C. Witt (Loyola University, Maryland) participated in technical meetings to discuss various aspects of this project.
Chris Weaver (University of Oklahoma) and June Abbas (University of Oklahoma), both co-PI's with Huskey on the Digital Latin Library project, provided important comments and insights from their perspectives in the fields of computer science and library and information studies, respectively.
Virginia K. Felkner (University of Oklahoma) helped to refine the guidelines in many places through her work in designing scripts for automating some of the encoding tasks described here.
The Andrew W. Mellon Foundation provided funding for the development of these guidelines.
Donald Mastronarde (University of California, Berkeley, and Richard Tarrant (Harvard) collaborated to review an earlier version (72479d0) of these guidelines. Their review was published on December 4, 2017 on the Society for Classical Studies' blog as "Review: Guidelines for Encoding Critical Editions for the Library of Digital Latin Texts." The current version of these guidelines owes much to their constructive criticism.
Finally, the many contributors to the standard established and maintained by Text Encoding Initiative (TEI) deserve the gratitude of anyone involved in humanities computing. The LDLT guidelines are a customization of the TEI and the EpiDoc guidelines for XML text markup of ancient documents, to which they also owe much.
This document contains encoding guidelines for The Library of Digital Latin Texts (LDLT), a series to be published by the Digital Latin Library in collaboration with the Society for Classical Studies, the Medieval Academy of America, and the Renaissance Society of America.
The LDLT uses a customization of the standard established by the Text Encoding Initiative (TEI). LDLT texts are in a format called XML, which uses tags wrapped in angle brackets to mark various aspects of the text. XML is a ‘plain text’ format, meaning writing programs like Microsoft Word are not suitable for editing it. We recommend you either purchase an XML editor, like oXygen, or use a free text editor, ideally with XML support. Atom, with the linter-autocomplete-jing plugin is one example. Oxygen comes with a lot of built-in TEI support, so it may give you a better experience.
There are some very basic rules to editing XML documents you should be aware of: XML tags (or elements) must nest properly. If you open one (e.g. <p>), you must close it (</p>) or have it close itself (e.g. <ptr/>). You can have only one root element (<TEI> in this case). Some special characters (especially <) need to be escaped (< is how you do a left angle branket). LDLT documents use a ‘schema’ to check whether the tags you've used are in the right places. In general, you can only put certain tags in certain locations, so no <div>s (which mark a section of text, e.g. a chapter) inside a <p> (a paragraph), for example (because that would be silly). The schema contains rules that enforce these kinds of restrictions. Your editing program should tell you when and where you've done something wrong, and should help you out by telling you what tags you're allowed to use at any given spot. We have provided a template file to get you started with your edition.
The term "scholarly digital edition" can refer to many different kinds of digital objects, from simple text or HTML files to dynamic, multimedia resources. Most scholarly digital editions attempt to combine textual criticism with insights and techniques from a variety of other scholarly fields such as human-computer interaction, information visualization, interface design, and data analytics. In addition to a critical text, these multi-media resources provide a digital environment designed for experiencing textual and other kinds of data (e.g., visual, aural). Often these environments highlight the idiosyncrasies of a specific work or works, and they require a variety of technologies to function as expected.
Although such editions can promote new and original ways of thinking about texts and their contexts, they are liable to loss of functionality over time as technology changes. Moreover, they do not lend themselves to contributing to a larger collection of texts that can be stored, searched, analyzed, visualized, and reused with reliable, reproducible results. The overall goal of the LDLT is to build such a collection, and to make the collection and its individual texts available for use with a variety of platforms and applications.
A tenet of the Digital Latin Library project is that editors of critical editions should not have to become experts in the full stack of technology required for designing, building, and maintaining digital resources. A corollary is that designing, building, and maintaining digital resources can and should be considered scholarly activities, too, especially if they make original contributions to scholarship or enable others to make those contributions. For these reasons, the LDLT separates, as much as possible, textual data from visualization and interaction.
Accordingly, an LDLT edition is a single, version-controlled file encoded in TEI XML according to the guidelines articulated in this document. The file contains the elements traditionally associated with critical editions: a preface, a critical text, scholarly apparatuses, and ancillary materials. Editors may include critical transcriptions of witnesses, collation tables, notes, images, and other materials in the repository that holds the LDLT edition so that users can have access to that data if they wish to study the text in greater detail. Although LDLT editions themselves are not multimedia resources, editors should take advantage of the opportunity to enhance their editions by incorporating links to digital resources both within the edition (e.g., names of people and/or places) and elsewhere (e.g., digital copies of books and articles, images of manuscripts, maps, etc.). See the section "Linking" for more information.
Because LDLT editions are openly available for reuse as the basis for information visualization, data analysis, or other projects, nothing precludes anyone from creating a multimedia project to highlight aspects of LDLT data. Indeed, the Digital Latin Library itself is developing an application for using information visualization techniques on LDLT data, and it also provides the official LDLT Viewer as a reading environment for LDLT editions. It should be emphasized, however, that the text as presented in the LDLT Viewer is not the same thing as the LDLT edition. Rather, the edition is a specific version of the file that contains the data that the LDLT Viewer visualizes.
Because LDLT editions are XML files, humans can read them, but not with ease. That is why the Digital Latin Library has developed and maintains the official LDLT Viewer, an application that provides an interactive reading environment.
The LDLT Viewer itself is an example of the reuse of LDLT data for scholarly purposes. Drawing on his experience with and knowledge of human-computer interaction, interface design, and traditional philology, Cayless built the LDLT Viewer to highlight certain aspects of these guidelines. Depending on the choices made by editors when following these guidelines, the following features may be available when an LDLT edition is viewed in the LDLT Viewer:
The LDLT Viewer also presents the apparatus criticus in two formats: clickable icons in the margin of the text, and a more traditional critical apparatus format at the end of each section of text. Reading aids are also available through the implementation of Javascript libraries available from The Alpheios Project. Clicking on a word will reveal a window that provides lexical and morphological information.
To provide maximum flexibility in making editorial decisions, these guidelines offer several approaches to encoding certain types of information. As noted in the sections of this document, some approaches may affect the availability of the LDLT Viewer's features.
Since the LDLT Viewer is not the same thing as the LDLT edition, the functionality of the viewer should not be the determining factor in editorial decisions. Rather, editors should opt for the method that most accurately expresses their view of the text.
The front matter (i.e., preface, manuscript descriptions, etc.), textual commentary, and any appendices of an LDLT edition may be in Latin or English, depending on the editor's preference.
Traditional Latin conventions for the apparatus fontium, apparatus testium, and apparatus criticus should be used for those components of an LDLT edition.
In a traditional edition in print, citations and references link the edition's content with its own content (e.g., via cross-references) and content in other texts (e.g., parallel texts, quotations, etc.) and resources (e.g., scholarly notes, maps, images, etc.). Over time, scholars have developed standards for referring to texts with abbreviations (e.g., Verg. Ecl.) and citation schemes (e.g. Sent. I, prol., [n. 1]). To be sure, there are competing standards (e.g., Cat. and Catil. are two standard ways of referring to Cicero's In Catilinam) and competing citation schemes (e.g., the numbering of chapters in works by Cicero according to the editions of Gruter [1618] or Scot [1588]).Note: Cf. , "Chapter and Verse in Cicero
," Grazer Beiträge 11 (1984): 103–112. As in all other matters in editing, being accurate and consistent with references and citations is paramount.
The same is true with digital editions, but there is an additional consideration. The ability to click on a hyperlink in a text and have immediate, unmediated access to another digital resource is a distinctive characteristic of digital editions, and it is understandable that editors would want to take advantage of that functionality. But linking to specific sites on the internet can also have pitfalls. Link rot, for example, is a concern. Links can change or expire, and entire sites can become defunct. Although many maintainers of online texts take pains to observe best practices with regard to the stability and reliability of their sites, several factors beyond their control can render resources inaccessible on a temporary or permanent basis. Moreover, hypertextuality is still an active area for research, and best practices have yet to be established.
For these reasons, the implementation of hyperlinks is an important consideration for an editor of a digital edition. To preserve a high degree of confidence in an edition's scholarship, these guidelines recommend a conservative approach. That is not to say that hyperlinks should never be used. Rather, editors should select the method that makes the best use of resources available. Above all, they should bear in mind that their first concern in linking, whatever the method, is to be accurate and consistent.
The following sections describe different ways of linking to resources.
At a minimum, editors should use the citation schemes familiar from printed editions. This establishes a "link" to other texts that does not depend on any other technology to be meaningful. Moreover, it facilitates the automatic production of an index of passages cited or other similar resources.
Such references should consist of standard conventions for identifying a text. The basic elements for this kind of reference are:
The following is a minimal example of "linking" in this way:
Standard abbreviations can be used in place of the full name of the author and the full title of the work:
It may be useful to include in the edition's front matter a list of abbreviations for frequently cited works. In that case, abbreviations can be referenced using corresp:
If editors wish to establish hyperlinks to other texts, the best way of mitigating the risk of link rot is to refer not to specific resources, but to a Universal Resource Name (URN). Canonical Text Services (CTS) is a scheme for providing URNs for texts that can be used on any sites that are configured to resolve them. For example, the CTS URN for Vergil's Eclogues is urn:cts:latinLit:phi0690.phi001. A link to line 1.5 of that poem could be implemented using target on <citedRange> as follows:
In this case, the editor must add a <refsDecl> to the edition's TEI header to explain how the URN should be resolved to point to a particular resource for displaying the text (e.g, the Scaife Viewer).
CTS URNs exist for all of Classical Latin and much of Medieval Latin; coverage of Neo-Latin texts, however, is spotty, but progress is being made to improve it, and the Digital Latin Library is contributing to that effort. For example, texts added to the LDLT will be citable with CTS URNs. However, since the adoption of CTS URNs varies from one scholarly community to another, what may be second nature to one group may be foreign to another, so these guidelines suggest an alternative approach for inserting hyperlinks to texts and other resources.
A mission of the DLL is to build and maintain a Linked Open Data architecture for referring to information related to works in Latin. This Linked Open Data architecture includes author pages and works pages that feature a range of identifiers, including not only CTS URNs (where they exist), but also identifiers from the Virtual International Authority File, the Library of Congress, and individual collections such as the Packard Humanities Institute's Latin Texts, among others.
Looking up DLL pages for all of the citations in a critical edition would take a great deal of time, once search times and page-load times are factored into the equation. Therefore, to simplify the process, and to make it possible to automate it, the DLL has made the addresses for these pages easy to generate by following a pattern based on the work's ID number in the DLL's catalog. Those ID numbers are available online or as a downloadable CSV file for quick reference.
Generating the address for a work is a matter of following the pattern https://catalog.digitallatin.org/dll-work/[ID]. For example, the DLL ID for Vergil's Eclogues is W3894, so its address is https://catalog.digitallatin.org/dll-work/W3894. The information at that address includes the authorized form of the author's name, standard and alternative forms of the title of the work, known identifiers for the work, and links to versions of the text known to the DLL catalog.
In an LDLT edition, an editor referring to line 1.5 of Vergil's Eclogues could link to the DLL's work page as follows:
In this shorthand version, the prefix "dll" in ref can be expanded automatically to the string "https://catalog.digitallatin.org/dll-work/", and the ID or alias after the colon can be appended to it to create the link to the DLL page for that work. Although this means that access to the resource will be mediated (i.e., users will be sent to the DLL's site first, where they will find a link to the resource), that mediation provides some protection against link rot. That means that this method does not allow editors to link to a specific line number, but the resulting page may give readers access to a variety of options for viewing the text. If any necessary information is not yet in the DLL's catalog, editors should alert DLL staff so that it can be given the highest priority in the queue for adding entries to the catalog.
The following example uses <ptr> to produce a hyperlink reading "http://www.someurl.org/resource/":
In the next example, the words "Some linked text" would become a hyperlink to the resource at http://www.someurl.org/resource/:
Either one of these methods is acceptable for producing a hyperlink. It is up to the editor to decide which one is most appropriate in each instance. It is also up to the editor to determine the reliability of a digital resource and to use good scholarly judgment about linking to it. The following subsections include guidelines for making those decisions.
These guidelines recommend encoding an edition's list of manuscripts and its bibliography in the front matter. The following sections describe in detail how to encode the different types of sources:
Those sections also include information about encoding hyperlinks to digital versions of items in lists of manuscripts or the bibliography. Because each item should have a unique identifier (see "Human- and Machine-Readable Sigla, Symbols, and Abbreviations", references to these sources can be made anywhere in the text using <ref> with target as follows:
That encoding will render "Wehrlein's 1922 edition" as a hyperlink to the full item in the edition's bibliography.
If it is desireable to refer to a particular source on the internet without citing it in the bibliography, <ptr> or <ref> with target may be used as described in the section "Linking".
For example, at Calp. 1.73 Giarratano refers once to a made by Müller in his review of Schenkl: asseret L. Mueller (Berl. phil. Woch. V. p. 1071). Since the fifth volume of Berliner philologische Wochenschrift is openly available, the editor of an LDLT edition could include a link to it with <ref>:
That link will point the reader to the PDF of that page (column, to be exact) as stored at the HathiTrust's digital library.
This section describes the basic structure of the file containing an edition for the LDLT. The structure of an LDLT edition resembles the structure of a traditional printed critical edition.
Since every text is unique, not every LDLT edition will have all of these sections. The nature of the text and the editor’s judgment will determine the contents of an edition. The purpose of this section is to define the parts of an LDLT edition and to provide guidelines for representing them in XML.
The following is an example of the general overall structure of an XML file for an LDLT edition:
A traditional critical edition in print has a title page announcing the title of the work, its author, the editor(s), and details of publication. In an LDLT edition, these details are presented as structured data within a TEI header (<teiHeader>). For example:
Since a critical edition is often based upon many sources (e.g., manuscripts, previous editions, commentaries, etc.), the <teiHeader> for an LDLT edition does not hew strictly to the TEI guidelines for <sourceDesc>. The sources for an LDLT edition are documented and described in the edition’s front matter.
Just as an editor is not expected to create the title page and document the publication information, this section of an LDLT text is the responsibility of the DLL staff.
The <front> contains the argument for the current edition, a survey of the witnesses and sources, the bibliography, and other information that may be of interest. The front matter may be organized into sections and subsections (using <div>, each with a unique xml:id). See the section "Structure of an LDLT Edition" for an example.
The front matter may be in Latin or English, depending on the editor's preference.
The elements and attributes available to all TEI documents may be used in the edition's front matter. For example, in addition to using <p> to divide the preface into paragraphs, an editor might want to make a table comparing the readings of manuscript families. In that case, the editor would use <table> and its related elements. Similarly, certain standard elements may be used in the description of manuscripts and other sources. See section 3 of the TEI Guidelines, "Elements Available in All TEI Documents" for a list of the available elements and attributes and more information about using them.
Because the <front> also defines the edition's data and data model, it is important to understand how the LDLT's data model handles certain traditional aspects of critical editions. In particular, it is vital to understand what the terms "witness" and "source" mean in the context of the LDLT, and how to refer to them with sigla and abbreviations that can be understood by humans and processed by machines.
Editors consult many types of documents and publications in the process of creating critical editions: manuscripts, incunabula, modern editions, monographs, articles, notes, correspondence, etc. Some of these types (i.e., manuscripts and incunables) are commonly referred to as “witnesses,” since they stand in close relationship to a certain version of the text. The term “witness” cannot be applied to the other types, since they do not cleave to one exemplar, but rather reflect a broad range of sources (including scholarly conjecture).
This issue is raised here because the model for LDLT editions requires precision in the use of the terms “witness” and “source,” particularly with regard to the encoding of the critical apparatus, where wit (witness) and source (external source) are used to classify readings. The classification of resources as witnesses and sources also affects how they are encoded in the edition's preface and bibliography.
Witness: For the purposes of these guidelines, manuscripts and some incunabula retain their traditional distinction as witnesses, but that category has been enlarged to include manuscript hands, which may bear witness to alternative readings in glosses, marginalia, corrections, conjectures, etc. This is a departure from the TEI's guidelines on Manuscript Description, which treat the manuscript itself as a witness, but consider hands as agents responsible for specific textual content. It is up to the editor to determine whether an incunabulum is a witness to a single manuscript. For more on editions as witnesses, see "Editions."
Source: All other resources cited in an edition fall under the category of “source,” a capacious term that refers to any resource external to the current edition.
Whether an item is a witness or a source, it must have two kinds of identifier that will stand for it wherever it is referenced in the edition: one for human readers, the other for machines. The next section explains the concept of human- and machine-readable sigla, symbols, and abbreviations.
Printed editions have long used a system of references for manuscripts and other items. For example, single letters, or sigla, stand for manuscripts, and the last names of scholars stand for editions, commentaries, or other works of scholarship. Centuries of use have demontrated that this system of sigla and other symbols and abbreviations is an efficient, effective, and economical way of presenting the complex information contained in critical editions. Although its development was motivated by the constraints of the printed page, its virtues for representing data commend it for other media, too. But just as the printed page has limits, so too does the digital file, which means that the traditional system requires an update to make it useful in a digital context.
Given some guidance and experience, people can learn how to navigate the system of letters, numbers, symbols, and other typographical conventions for referring to the sources of a crticial edition. If one edition uses superscript numerals to indicate the hands that wrote in a manuscript, but another uses superscript numerals to signify the number of a manuscript in a collection, a human reader can adjust to the difference in meaning without much effort. In contrast, machines need clear instructions and a reliable set of rules for reading a digital file. For example, a human might see N2 and correctly interpret it within a particular edition as meaning “text written by the second in a succession of people who wrote in the manuscript known as codex Neapolitanus V A 8.” Without explicit instructions, a machine will interpret the same information as simply the letter “N” with a superscript numeral 2 next to it. A less experienced human reader might reach the same conclusion as the machine.
Since the audience for LDLT editions includes an entirely new class of reader (i.e., machines), it stands to reason that the reference system should be adapted to accommodate the needs of the expanded readership. For this reason, LDLT editions encode sigla and other aspects of the traditional reference system in two ways: a machine-readable version (using xml:id) and a human-readable version (using <abbr>, with special instructions for rendering typographical conventions such as superscript and subscript notation). In some cases, the values for both will be the same, but the strict rules of the XML specification for xml:id do not allow for the traditional system of combining letters with superscript and/or subscript numerals. Nevertheless, the values of xml:id and <abbr> should be similar, if not identical, to each other, and they should be meaningful. Editors should follow the conventions in previous editions of the same text, changing a siglum only if it is important to the edition’s argument. If the text has never been edited, the editor should choose sigla according to the principles outlined by West (74–75). In brief, sigla should have mnemonic value (e.g., “V” for “Vaticanus” or “P” for “Parisinus”).
Because the needs of editors will vary from edition to edition, the LDLT does not have strict rules for representing manuscript hands or similar information. The following suggestions might be useful:
| Information | Example Value of xml:id | Example Value of <abbr> |
|---|---|---|
| A single manuscript | V | V |
| Manuscript Hands | Vh1, Vh2 | V1, V2 |
| Multiple manuscripts from one collection | Vms1, Vms2 | V1, V2 |
| One of many indistinguishable hands | Vrec | Vrec |
| Fragments of ancient copies | Π1, Π2 | Π1, Π2 |
| Consensus of manuscripts | ω | ω |
| One or more late manuscripts | Ϛ (see note below) | ϛ |
| Scholia | Σ | Σ |
| Scholia in a certain manuscript | Σa, Σb | Σa, Σb |
| A Single Edition, Book or Other Source | Mynors | Mynors |
| Multiple editions | Schenkl1, Schenkl2 | Schenkl1, Schenkl2 |
| Multiple books or articles by the same scholar | Burm1731, Burm1759 | Burm. 1731, Burm. 1759 |
In short, every witness or source in an LDLT edition must have both a machine-readable ID (using xml:id) and a human-readable siglum or abbreviation (using <abbr> with type="siglum"). Otherwise, the edition will not be able to make full use of the digital format. Morever, if an entry lacks <abbr>, it will not be available for a print version of the edition, should one be required.
The description of manuscripts is a discipline unto itself, with long-established conventions for capturing all of the details about not only a manuscript’s contents, but also its dimensions, provenance, material, and other details. The TEI has a module for manuscript description, but its highly structured nature is intended for use in catalogs and databases of manuscripts. Accordingly, these guidelines describe a method similar to what is found in traditional critical editions: detailed prose descriptions of manuscripts in a preface and/or a list of more concise information in the conspectus siglorum. If, however, the edition is a critical transcription of a single manuscript or a limited number of manuscripts, the editor may wish to enrich the edition's metadata by adding a structured description (using <msDesc>) in the <sourceDesc> portion of the TEI header. The Digital Latin Library is also building a catalog of manuscripts, using the TEI guidelines as a model. Editors of LDLT editions may elect to create records for manuscripts in the catalog and point to those records in their editions.
The following sections describe the components of manuscript description in an LDLT edition.
This section describes the minimum requirements for manuscript description in an LDLT edition: a concise list (using <listWit> and <witness>) of manuscripts in which the sigla (both human- and machine-readable) are defined. This is sufficient to give readers basic information about the manuscripts and to establish a data model for the edition. It is also sufficient to enable the functionality of the LDLT viewing application. The lists described here correspond to the conspectus siglorum in a traditional printed edition.
The absolute minimum required is <listWit>, <witness>, <abbr>, <name>, and <date>:
The following example demonstrates the bare minimum for describing manuscripts in an LDLT edition:
That example provides enough human- and machine-readable information to identify the manuscripts in the apparatus criticus, but it leaves much to be desired by anyone hoping to learn more about the manuscripts or to locate them for private study, which is why an editor may want to include a prose description with more information elsewhere in the front matter.
Note that the language used for listing manuscripts is the editor's choice, but if the manuscript is traditionally referred to by a Latin name, that form should be used.
The next sections demonstrate how to assign sigla to families of manuscripts, archetypes, and hyparchetypes so that they may be referred to in the apparatus criticus or elsewhere.
Since a manuscript's family is not itself a physical object, but a concept (i.e., a group of related manuscripts), the family's siglum is assigned to <listWit> as the container of the individual <witness> elements that describe the manuscripts in the family.
In the following example, <listWit> has the xml:id V for the machine-readable siglum; <head> contains the name of the family and the human-readable siglum in <abbr>.
An archetype is the most recent common ancestor of the known manuscripts (cf. West 32). A hyparchetype is the ancestor of a branch of a family of manuscripts. In editions of Latin texts, both archetypes and hyparchetypes are commonly represented with lower case Greek letters.
For example, Robert Kaster assigns the siglum ω to the archetype of the manuscripts of Suetonius’ De Vita Caesarum. The manuscripts can be analyzed into two families that stem from two hyparchetypes, to which Kaster has assigned the sigla α and β. The two families have branches, each with their own hyparchetype (α1 α2 β1 β2).
Kaster lists the sigla as follows:
Though no longer extant, archetypes and hyparchetypes can be referred to as witnesses to readings. Therefore, they are encoded with <witness>. The following example demonstrates how Kaster’s list should be encoded:
The nesting of witnesses in this way can lead to confusion, so it is a good idea to include code comments to show where information begins and ends:
Linking to digital records (e.g., catalog descriptions, images, etc.) of manuscripts can enhance an LDLT edition. For this reason, editors of LDLT editions are encouraged to request an account for adding records to the Digital Latin Library's catalog of manuscripts. Doing so will allow them to record information about manuscripts in a more detailed, structured format than is practical in a critical edition. If records and/or images are already available, editors may simply point to those instead.
Whether pointing to records in the DLL's catalog or elsewhere, both <ptr> and <ref> are available for inserting links. The former renders a simple hyperlink:
The latter may be used to cause certain words (e.g., the manuscript's name) to be linked to a URL:
Whichever method is used, the date when the URL was last verified as accessible must be included.
Although the information provided in the <witness> element described in the previous sections should be sufficient to identify a manuscript, editors may wish to discuss other details, such as whether a given manuscript has been fully collated, and how it was consulted (e.g., in situ, on microfilm, or in digital form). This information may be conveyed in a prose description (using <p>) in the edition's front matter.
All prose descriptions of manuscripts must include a link (using <ref> to the manuscript's human- and machine-readable siglum or abbreviation, which are defined elsewhere in <witness>:
Prose descriptions give editors the freedom to determine the amount of detail to give to the discussion of a manuscript or group of manuscripts.
Instead of separating the two forms of manuscript description into sections corresponding to the traditional preface and conspectus siglorum, editors may wish to combine them into one section. This might be especially helpful in cases where there are multiple groups of manuscripts.
Combining the two forms is as simple as listing the manuscripts in <listWit>, then following the list with a discussion of the manuscripts in prose:
To make the most of the functionality supported by the LDLT Viewer and to remain true to the LDLT's data model, previous editions should be classified in one of two categories: witness and source. Editors have considerable leeway for making the distinction. The following paragraphs provide some guidance.
Witness: An edition may be considered a witness if it is an early printed edition that is not clearly based on more than one external source. That is, incunabula, or books printed before 1500, were often reproductions of single manuscripts; they might also reflect some editing by the typesetter, but on nothing like the scale of modern critical editions.
Source: An edition may be considered a source if it is based on a scholarly approach to the text. An edition does not have to be based on a specific approach to textual criticism to be classified as a source. Indeed, tralatitious editions, variorum editions, and early commentaries may be classified as sources if it seems appropriate. In the case of early editions that are important not because of their text, but because of the comments of scholars preserved in their notes, it may be worth recording the edition in the bibliography and listing the names of those scholars separately in a "list of scholars".
Classification as "witness" or "source" will have consequences for how editions are handled in the front matter and the apparatus criticus (see the section "Apparatus Criticus"). In the front matter, <listWit> is used with one <witness> each for witnesses; <listBibl> is used with one <bibl> each for sources. In both types of list, the items should be presented in chronological order.
For more information on the terms “witness” and “source” as they are used here, see the section “Terminology: Witness and Source” above.
Editions classified as witnesses must be grouped in <listWit>. Since they are also printed books, they also require the use of <bibl> and its related elements.
Editions classified as sources follow the same pattern as early editions, except <listBibl> is used instead of <listWit>.
If it is necessary to group two or more editions together (e.g., first and second editions) and refer to them as a unit with one siglum, another <listBibl> should enclose the group:
Bibliographical information for other works cited in the edition should be gathered in a general bibliography (using <listBibl>), formatted according to the most recent edition of The Chicago Manual of Style, and presented in alphabetical order.
So that the bibliographical information will be available from citations in the edition, each entry should have a human- and machine-readable identifier. See the section "Human- and Machine-Readable Sigla, Symbols, and Abbreviations" for more information.
The following sections provide instructions for encoding different types of resources commonly found in the bibliographies of critical editions.
The following information about books, commentaries, monographs, collections of essays, etc., should be encoded:
This will be rendered as follows: Haupt 1854. = Haupt, Moriz. De Carminibus Bucolicis Calpurnii et Nemesiani. Berolini: Typis Academicis, 1854. URL: https://books.google.com/books?id=8SwUAAAAQAAJ&pg=PP5#v=onepage&q&f=false.
As with other items in the bibliography, articles in journals and periodicals should be formatted according to the latest edition of The Chicago Manual of Style. The minimum required encoding for articles is as follows:
Encoding more details is strongly recommended:
A review of an edition or other work should be handled in the same way as a journal article, with the exception that the title should begin with the words “Review of” followed by the title of the work being reviewed.
Occasionally it is necessary to refer to a scholar whose unpublished work has been quoted or paraphrased elsewhere. For example, editors often cite Heinsius’ unpublished conjectures, found in books in his own library. But “Heins.” does not help a reader find more information, which is why the bibliography of an LDLT edition must include a list of scholars mentioned by name in the edition, with information about where to find more information, if it is available.
References such as this will be rendered in digital media and in print as follows:
The edition text corresponds to the text printed “above the line” of the critical apparatus in a traditional edition. It is composed of lemmata, that is, text judged by the editor to be authentic, accurate, and/or authoritative.
There may be more than one authoritative version of a text, depending on the text and/or the approach adopted by the editor. Authors sometimes edit and revise their work over time. Scribes often record the version of the text that makes sense in their context. Scholars and other readers offer conjectures for problematic passages. But an editor must make decisions about the text an edition presents to readers. Those decisions are part of the editor’s argument about the text, and they are on display in the official edition text in its initial state.
“Initial state” is an important phrase. Since the LDLT Viewer allows readers to swap readings from the critical apparatus into the main text, it is possible to encounter many versions of the text in one viewing of it, but the official edition text in its default initial state (i.e., the contents of the XML file, or what is displayed when the edition is opened for the first time in the LDLT Viewer, with default settings) is the starting point for those interactions.
This section establishes guidelines for encoding the information typically found in the edition text.
The aim of this section is to provide guidance for marking up the structure of prose texts, using the generic model of book, chapter, and paragraph for the main components of a work. Individual texts may have different structures, so editors should consult LDLT staff about the best way to encode the structure.
In a traditional critical edition, numbers are printed in the margin and/or in the text itself. It is not always clear whether the numbers are meant to mark syntactic units, reflect the numbering of pages or sections in a canonical edition, or signify something else entirely. An advantage to semantically encoding the reference scheme is that it makes the scheme’s significance explicit. For that reason, a human- and machine-readable reference scheme is essential for an LDLT edition. If the structure is not encoded according to these guidelines, some of the functionality of the LDLT Viewer cannot be supported for the edition.
For an LDLT edition of a prose text, the top-level <div> has the type “edition”; this division contains the entire text of the edition. The next <div> must have the type “textpart” with subtype “book”, n to indicate the number of the book, and a unique xml:id.
If a different division scheme is required, editors should consult LDLT staff.
The individual sections of a prose work should be encoded as follows:
That text will be rendered as follows:
Liber I
1 1Gallia est omnis divisa in partes tres, quarum unam incolunt Belgae, aliam Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur. 2Hi omnes lingua, institutis, legibus inter se differunt. Gallos ab Aquitanis Garumna flumen, a Belgis Matrona et Sequana dividit. 3Horum omnium fortissimi sunt Belgae, propterea quod a cultu atque humanitate provinciae longissime absunt, minimeque ad eos mercatores saepe commeant atque ea quae ad effeminandos animos pertinent important, proximique sunt Germanis, qui trans Rhenum incolunt, quibuscum continenter bellum gerunt. 4Qua de causa Helvetii quoque reliquos Gallos virtute praecedunt, quod fere cotidianis proeliis cum Germanis contendunt, cum aut suis finibus eos prohibent aut ipsi in eorum finibus bellum gerunt. 5Eorum una, pars, quam Gallos obtinere dictum est, initium capit a flumine Rhodano, continetur Garumna flumine, Oceano, finibus Belgarum, attingit etiam ab Sequanis et Helvetiis flumen Rhenum, vergit ad septentriones. 6Belgae ab extremis Galliae finibus oriuntur, pertinent ad inferiorem partem fluminis Rheni, spectant in septentrionem et orientem solem. 7Aquitania a Garumna flumine ad Pyrenaeos montes et eam partem Oceani quae est ad Hispaniam pertinet; spectat inter occasum solis et septentriones.
The verse module of the TEI Guidelines offers many possibilities for marking up various aspects of prosody, but the LDLT is primarily concerned with the core tags for encoding the structure of verse texts. This does not mean that editors and others should avoid using the verse module. It means only that the LDLT does not provide functionality for any markup not described here.
For an LDLT edition of a verse text, the top-level <div> has the type “edition”; this division contains the entire text of the edition. The next <div> will normally have the type “textpart” with subtype “book” and n to indicate the number of the book and a unique xml:id. <div> with type="poem" contains the parts of a single poem (e.g., stanzas or lines). If there is more than one poem in a book, n should be used to number the poems. met with the name of the meter may also be used, if the editor wishes to identify the meter. If a different division scheme is required, editors should consult LDLT staff.
If text in languages other than Latin is encoded, language becomes available as a potential criterion for searching and filtering.
For example, authors of Latin texts often use Greek words and phrases, as Macrobius does at Saturnalia 1.17.64: ‘Ἀπόλλωνα Διδυμαῖον vocant, quod geminam speciem sui niminis praefert ipse inluminando formandoque lunam’. That should be encoded as follows:
This section discusses how to encode the following kinds of speech:
Quotation of direct speech may be handled in two ways: with punctuation alone or with semantic markup.
If an editor wishes to use standard punctuation to represent direct speech, the current edition of The Chicago Manual of Style should be the guide.
The following rules apply to the semantic markup of direct speech:
For example, Julius Caesar’s famous words before crossing the Rubicon, as reported by Suetonius, could be encoded as follows:
<said> may be nested inside <said> to indicate quotation within a quotation.
In texts with interlocutors, the label for a speaker is a “paratext,” or aid to the reader; it is not, strictly speaking, part of the text itself. For that reason, these guidelines treat labels for speakers as metadata associated with the point in the text where a character begins to speak. For example, the first line of Vergil's Eclogues is spoken by the character Corydon, but "Corydon" or "C" is not part of the text of the first line. Otherwise, the line would not scan properly as dactylic hexameter.
Texts that feature interlocutors (e.g., drama, dialogue) should use <label> to indicate a change in speaker. Labels are the simplest way of indicating a change of speakers, since they do not add a new layer of hierachy.
Since <label> is treated as metadata and thus ignored as part of the actual text, it may be omitted from searches of the text itself. However, since labels sometimes are applied differently in different witnesses or sources, those differences can be encoded in the apparatus criticus like any other variation. If used with exclude, the swapping of variants in the LDLT Viewer can allow readers to see the different ways the labels have been applied.
In this example, the first line is attributed to Corydon, but some manuscripts and editions omit the label, and others attribute the lines to Ornytus. One family of manuscripts, V, attributes the fourth line to Corydon. exclude has been used here to indicate that whenever the <lem> in line 1.1 is displayed, the variant reading in line 1.4 will not be displayed, since that would be a contradiction. Since the variant in line 1.4 does not contradict the variants in line 1.1, there is no need to use exclude in those cases.
Note also the placement of <label> in the example above: in the first line, <label> is outside of <app> because the editor of the text is asserting that a label belongs there, but he is also indicating that there is disagreement in the sources about the contents of the label; in the fourth line, the editor asserts that a label does not belong on that line, but he also indicates that a variant reading inserts a label there.
Quotations of literature should be encoded according to the guidelines set forth in the section “Apparatus Fontium.”
It can be useful to encode names of people mentioned in the text of an edition, whether to facilitate the creation of an index or to support digital search functionality. It is up to the editor to decide which names, if any, should be encoded. If names are to be encoded, the following guidelines should be observed.
Since inflected forms of names may appear in the text, it is vital to have a reference list of names in the nominative form. While working on a text, editors should establish a working list of names, in a separate XML document, using <listPerson>, <person> and <persName> or <org> and <orgName>:
Where names of people in the reference list appear in the edition text, they should be encoded with <persName> or <orgName> and ref pointing to the xml:id of the person in the <listPerson>.
It is also possible to encode indirect references to people:
If there are variant readings of a name, <persName> should be used within <lem> or <rdg> as needed. If the nature of the variation is such that one form is a proper noun, but the other is a common noun, <persName> should enclose only the proper noun inside of <lem> or <rdg>, as the case may be.
Names of places can be encoded in LDLT editions to facilitate creation of an index or to assist readers in identifying the places mentioned in the text. If it is desirable to encode this information, the following guidelines should be followed.
Since inflected forms of place names may appear in the text, it can be helpful to provide a reference list of names in the nominative form. While working on a text, editors should establish a working list of names, in a separate XML document, using <listPlace>, <place> and <placeName>.
The final list can be incorporated into the <back> of the edition at a later stage.
The following example from Caesar’s de bello Gallico demonstrates how to encode place names when a <listPlace> is maintained in the <back> of the edition:
It is also possible to forgo <listPlace> and just encode place names as they occur. This may be desirable in texts with only a few references to place names. In this case, it is recommended to include ref with each <placeName>, with a URI pointing to some reference (e.g., Pleiades) for the place name:
If there are variant readings of a place name, <placeName> should be used within <lem> or <rdg> as needed. If the nature of the variation is such that one form is a proper noun, but the other is a common noun, <placeName> should enclose only the proper noun inside of <lem> or <rdg>, as the case may be.
Over time, certain typographical conventions have become standard for representing emendations, lacunae, omissions, gaps, editorial deletions, and other information in the edition text. The present guidelines observe the standards as described by West (80–81), but they call for semantically encoding them instead of simply inserting the various punctuation marks and other symbols that represent complex information. The LDLT Viewer will display the familiar symbols to human readers, but encoding the data in this way also makes that information available to machines. That means that it will also be available for processing, querying, and analyzing with digital tools.
Since most of the standard symbols usually have corresponding annotations in the critical apparatus, the encoding guidelines for many of them can be found in subsections of the guidelines for encoding entries in the critical apparatus. The following list identifies the symbols and points to the guidelines for encoding them:
( ) = An editor expands an abbreviation as an aid to reading or to remove ambiguity. Encoded according to the following guidelines, a digital edition might display the abbreviated forms by default, but a user could be given the option to toggle between the abbreviated and expanded forms.
The preface should indicate whether or not abbreviations are expanded.
Example: M(arcus) Cicero S(alutem) D(ixit) L(ucio) Lucceio Q(uinti) F(ilio)
Multiple <abbr> elements within a single <expan> compose a single abbreviation between them. For example, "e.g." is one abbreviation for the phrase “exempli gratia.”
When an edition is based on a limited number of witnesses, it may be necessary to indicate that characters are difficult to read. The accepted way to do this is with dots underneath the uncertainly restored characters.
For example, the entry for Mensae in Lindsay’s edition of Festus (157M) has the following uncertainly deciphered text:
ạṃẹ . . . ạ ṭẹṇẹḅạṭ ạṛạṃ . . . . . . . . . .
In an LDLT edition, that should be encoded as follows:
*** = An unknown amount of text has been lost from the entire textual tradition, whether because of physical loss or human error (e.g., saut du même au même).
For example, an undetermined amount of text is missing from all witnesses at the end of 3.8.4 of Julius Caesar's de Bello Civili. Cynthia Damon's OCT edition has the following in the main text: Custodiisque diligentius dispositis ipse grauissima hieme in nauibus excubans neque ullum laborem aut munus despiciens neque subsidium expectans si in Caesaris complexum uenire posset ***.
<gap> with reason="lost" is inserted into the main text to indicate the lacuna:
If it is desirable to insert a comment on the lacuna in the apparatus criticus, <note> should be used as explained in the section Editorial Notes.
These guidelines also have provisions for cases where an editor suspects a lacuna in the text, but lacks physical evidence of damage to support the claim. See the section "Conjectured Lacunae" for more information.
If a single witness or family of witnesses has a gap in coverage of the text, but the rest of the tradition preserves the text, the symbol for a lacuna should not be used, but the gap in the witness(es) should be noted in the apparatus criticus. See the section "Gaps in Witnesses" for encoding instructions.
An apparatus fontium collects references to texts quoted or cited by the author(s) in the text of the edition. This section demonstrates how to encode such references so that they will be displayed appropriately in the text and so that bibliographical information about them will appear in the edition.
Any text in <quote> will be displayed or printed in quotation marks on the same line as the rest of the text, so there is no need to insert quotation marks manually. Any text in <quote> with rend="blockquote" will be or printed on a new line and indented. In the latter case, prose and verse text within <quote> should be encoded according to the guidelines in the sections "Prose" and "Verse.”
The choice to use <bibl> or <ref> to indicate the source in the <note> for the apparatus fontium depends on whether the author is referring to a work, in which case <ref> should be used, or an editor is citing a source for the reference, in which case <bibl> should be used. The following sections illustrate the difference.
When the author identifies a source in the text, <ref> should be used to indicate that the author is referring to a work, not a specific material copy of that work. If it is desirable to cite a specific edition, the editor should use <bibl> and its associated elements for that purpose.
In the following example, Duns Scotus has referred to a work by Boethius, but he has not quoted it directly: Probatio minoris per Boethium De Trinitate: dicit quod septem praedicamenta non dicunt absolutas res, sed tantum respectus. The editor wishes to cite a specific edition. The entire passage should be encoded as follows:
In the edition text, the text would be displayed or printed without interruption: Probatio minoris per Boethium De Trinitate: dicit quod septem praedicamenta non dicunt absolutas res, sed tantum respectus. The apparatus fontium would include the following entry: Boethius De Trin. c. 4 (ed. R. Peiper 159; PL 64, 1353C). If variant readings exist for the citation, they will appear in the apparatus criticus.
If it is desirable to provide the text of the reference in the apparatus fontium, it may be inserted in <quote> after <bibl> inside of the <note>:
The text of the quotation will be displayed in the apparatus fontium after the bibliographical information.
The following example from Robert Kaster's edition of Saturnalia (3.16.1–5) demonstrates a more complex entry that features other aspects of the quotation of sources, including direct speech, block quotations of prose and verse texts, and an inline quotation of a prose text:
If the author has not identified the source of a direct or indirect quotation, the editor may supply it in the apparatus fontium.
For example, Cicero often mentions the name of the authors he quotes, but editors must supply more detailed citation information, as in this passage from Orator 157:
Quid quod sic loqui: nosse, iudicasse vetant, novisse iubent et iudicavisse? Quasi vero nesciamus in hoc genere et plenum verbum recte dici et imminutum usitate. Itaque utrumque Terentius:eho tu, cognatum tuom non noras?
post idem: Stilponem, inquam, noveras.
Sient plenum est, sint imminutum; licet utare utroque.
To be sure that the citation information appears in the apparatus fontium, this is how that passage should be encoded:
An apparatus testium differs from an apparatus fontium in that it collects testimonia, or quotations of the text by other authors, but the apparatus fontium collects quotations of other authors in the text itself. Since it can happen that a quotation of the text attests to a variant reading, such information can also be included as a reading or annotation in the apparatus criticus. In those cases, the section on encoding the apparatus criticus should be the guide. Sometimes, however, it makes sense to include a separate register of testimonia. In those cases the following guidelines should be observed.
Testimonia are encoded using <note> with type "testium" (as in "apparatus testium"):
For example, Thomson's edition of Catullus has the following in the apparatus testium for poem 14: "9 Martianus Capella 3.229 15 Macrobius, Saturnalia 2.1.8." In an LDLT edition, the testimonia are encoded in close proximity to their point of reference:
A register of parallel passages differs from an apparatus fontium in that it reflects the editor's judgment about passages that might be of interest to readers, whereas an apparatus fontium provides information on passages quoted or cited by the author(s). For this reason, entries in the apparatus fontium are encoded within the edition text, but parallel passages are encoded as notes, similar to the way that an editor's textual notes are handled (see the section "Editorial Notes").
It should be noted here that register of parallel passages is optional. It is entirely up to the editor to decide if a listing of parallel passages is necessary and/or useful.
In an extreme example, Gelsomino includes an extensive list of parallel passages to individual entries in his edition of Vibius Sequester. If that edition were encoded according to these guidelines, each paragraph in the edition text would have an xml:id and corresp pointing to the xml:id of the note with the parallel passages:
This section provides models for handling the different kinds of entries that occur in an apparatus criticus. It uses the terminology, elements, and attributes of the TEI’s module 12 Critical Apparatus, but it also defines terms and encoding methods specific to LDLT editions. This section is not an instructional manual for composing an apparatus criticus. Rather, it presents a model for semantically encoding the information to be included in the apparatus criticus of an LDLT edition.
In a digital context, critical editions encoded according to these guidelines will have certain interactive features in the LDLT Viewer:
In a printed version of an LDLT edition, critical editions encoded according to these guidelines can be styled to have an apparatus criticus in a format familiar from standard critical ediitons.
The apparatus criticus is where editors assemble the variant readings from witnesses and sources they believe to be important for establishing the text, occasionally adding brief comments, bibliographical citations, and palaeographical details. This section defines the terms used in these guidelines.
It is important to emphasize that a critical apparatus reflects an editor's judgment about what is and is not important for supporting the argument advanced by the edition. Accordingly, the amount of information included in the critical apparatus depends on the method and aims of the editor. Although these guidelines make it possible to include every reading from every possible source, editors should bear in mind that manuscript collations, notes, and other data can be made available to readers as ancillary materials associated with an LDLT edition. Editors should consult LDLT staff and the editorial board regarding the format and storage of ancillary materials.
A critical edition contains two types of reading: lemma and variant.
A lemma (pl. lemmata) is a word or phrase (or the absence thereof) judged by the editor to be authentic, accurate, and/or authoritative. It may be attested by documentary sources (e.g., a manuscript, an early edition) or it may be an emendation made by a scholar independently of a documentary source. The text printed in the main portion (i.e., edition text) of a critical edition is made up of lemmata.
A variant is a word or phrase (or absence thereof) judged by the editor to be unsatisfactory for linguistic and/or stylistic reasons, but of interest for establishing the text. This type of reading is a “variant” insofar as it varies from what the editor has judged to be the lemma. A variant reading may be attested by a manuscript or it may be a conjecture or the result of a correction. By default in LDLT editions, variant readings are displayed or printed in the apparatus criticus. In digital versions, variants can be swapped into the edition text in real time so that readers may judge the merits of variant readings for themselves.
An emendation is a reading expressly proposed by some person (possibly the editor) and accepted by the editor into the main text of an edition.
A conjecture is a reading expressly proposed by some person (possibly the editor) and determined by an editor to be of interest in establishing the text, but not to be printed in the main text of the edition.
This distinction between "emendation” and "conjecture" supports the goal of these guidelines of drawing attention to editions as arguments. The terms are used subjectively, with regard to a particular edition. Readers of an edition may agree or disagree about whether a particular reading emends the text, but the editor's argument is that a reading either emends the text, in which case it is an emendation, or does not in which case it is a conjecture.
Correction describes any attempt by the original copyist or some other hand to alter a witness’ reading, regardless of whether the result of the correction matches the lemma of the current edition. It is a matter of perspective whether the result of a correction is “correct.” For more information, see the section “Correction”.
Opinions can differ from editor to editor about what the “correct” reading is, which is why having more than one critical edition of a text is not necessarily redundant. Similarly, copyists and other users of manuscripts have their own idea of what the “correct” reading is. The original copyist might notice a slip of the pen in his own work and correct it. A later hand might correct a mistake missed by the copyist. Another reader comparing two manuscripts might “correct” one of them based on the other’s reading. In these cases and others, the motivation is to correct what is perceived to be incorrect. For all of these reasons, “correction” is used in these guidelines to refer to an attempt to alter existing text so that it conforms to some perceived standard, whether or not that standard matches the editor’s view of what the correct reading is.
The next two sections discuss where readings are found, i.e., in witnesses and sources.
A witness may be a manuscript, the individual hands that wrote in a manuscript, a quotation of the text by another author, or an early printed edition (editio princeps) that may preserve the readings of a single manuscript.
The physical object referred to as a manuscript is not by itself a witness. Rather, it preserves a record of the activities of the copyist(s), rubricator(s), corrector(s), and/or other annotator(s) who wrote on its pages, each of whom might be a witness to a different exemplar. At the very least, they represent different perceptions of the same exemplar. By synecdoche, those people are referred to as “hands.” (These hands are not to be confused with the drawings of hands, known as manicules, that sometimes appear in the margins of manuscripts to point out passages of interest.) A manuscript’s hands are represented in a critical edition by superscript numerals appended to its siglum. A change in number, however, does not necessarily indicate a change of person. For example, the copyist and corrector might be one and the same person, but it can be important to distinguish them, since they represent different views and experiences of the text.
Confusion can arise from assigning numbers only to hands subsequent to the original copyist. That is, the siglum for the manuscript by itself (i.e., without a superscript numeral) is understood to represent both the physical object and the hand of the original copyist who wrote in it; every subsequent hand, including the original copyist correcting his own mistakes, is numbered in ascending order from “1”. Strictly speaking, the original copyist is “hand zero,” but adding a superscript zero to every siglum would be redundant, since it can be inferred from the absence of a numeral that the original copyist is meant.
In some cases, it is not necessary, possible, or desirable to make such a sharp distinction between hands. It may be sufficient instead to refer to hands other than the original copyist with the general manus recentior, or m.r. (“a later hand”). However the editor decides to represent the activities of a manuscript’s hands and the relationships between them, an explanation must be provided in the preface.
For more information on representing the hands in manuscripts, see the sections "Manuscript Description" and "Sigla.”
In sum, for the purposes of these guidelines, manuscript hands are witnesses, and the following scheme should be used to indicate them:
Another acceptable approach is to append abbreviations such as “ac” and “pc” (ante correctionem and post correctionem) as superscript notations on the manuscript’s siglum. It all depends on what suits the editor’s purposes, provided that the method of distinguishing hands is explained in the description of manuscripts and both human- and machine-readable sigla are assigned to them.
If it is desirable to identify different copyists (e.g., if the manuscript was originally copied by more than one person), subscript notations should be used (e.g, A1, A2, A3, etc.). Each copyist’s hand must be described and assigned a human- and machine-readable siglum in the description of the manuscript.
A source may be any modern critical edition, commentary, article, review, or other item (e.g., personal correspondence) in which an argument about the text has been advanced or discussed.
As in traditional printed editions, the order in which certain information is presented has meaning in LDLT editions, although the order’s meaning is not itself explicitly encoded. Editors should follow the recommendations of West (87–88) on the issue of order. In brief:
The following attributes and elements are required for putting the concepts discussed above into practice:
In traditional printed editions, a lemma might appear in the apparatus criticus for the purpose of disambiguation (e.g., if there are two instances of the word in the same line or if the degree of variance makes it difficult to infer the lemma), but more often the lemma must be inferred. This can lead to confusion and frustration, particularly for readers not used to navigating a critical edition. Moreover, variant readings are sequestered from the edition text and displayed at the bottom of the page, an arrangement that can lead to false impressions about the certainty and reliability of the edition text.
In the TEI’s model for the critical apparatus, which is the basis for these guidelines, each entry includes the lemma and its variants. How that information is displayed or printed is a separate issue, but at least the relationship between the lemma and the variant readings is explicitly encoded. In digital representations of an edition encoded according to the guidelines presented here, readings may be swapped into or out of the edition text, but the editor’s determination about what the lemma is and what the variant readings are remains encoded to preserve the argument the edition makes about the text. In this way, it is possible for readers to experience many versions of a text in addition to the edition’s initial state (i.e., its default setting). The variety of readings depends on what the editor decides to encode, and it is expected that those decisions will be explained in the preface.
The patterns displayed below are designed to handle the various kinds of information conveyed in a typical apparatus criticus, including readings ante correctionem and in rasura, among other paleographical and editorial details.
The most basic type of entry in an apparatus criticus reports only a variant reading, without editorial comment or a description of palaeographical details. The pattern is as follows:
In other words, <app> begins the apparatus entry, followed by <lem>, which contains the lemma for the entry. The lemma may be a single word or phrase or the omission of a word or phrase. The variant reading follows, contained in <rdg>. Only the contents of <lem> appear in the initial state of the edition text. The contents of <rdg> appear in the apparatus criticus.
If there is more than one variant reading to be reported, new <rdg> elements should be added for each one.
It is up to the editor to decide whether to list the witnesses for the lemma. In many cases, it can be inferred that the lemma is supported by most of the evidence. All variant readings, however, should include witnesses or sources so that users will be able to track that information.
The attribute wit contains the witness(es) for the lemma and variant reading(s). A hash or pound sign (#) before the siglum for the witness indicates that the witness has been described elsewhere in the edition, making it possible to retrieve that information.
If there is more than one witness for a reading, the sigla should be values for wit separated by spaces.
If it is desirable to indicate that a reading is found in a manuscript and a modern edition or other source, the same pattern applies, with the addition of source.
At Calpurnius (Calp.) 1.2 (quamvis et madidis incumbant praela racemis), the manuscript P has praeda where the lemma is praela. In a traditional apparatus criticus, this would be printed as follows: 2 praeda P.
The following pattern demonstrates how to encode the entry in according to these guidelines:
This encoding can be rendered in the traditional manner, or it can be used in an interactive apparatus to swap the variant with the lemma in the main edition text.
The lemma quamvis in the same line demonstrates how to indicate that a variant has more than one witness:
The witnesses are listed here in chronological order, but an editor may wish to use a different ordering principle. The order should be described and explained in the preface.
The following example demonstrates how to encode a reading supported by a witness and a source.
Testimonia are quotations of the text by other ancient sources. As such, they may be considered witnesses to the text. In some editions, testimonia are recorded in an apparatus testium; in others, they are incorporated into the apparatus criticus. Guidelines for encoding an apparatus testium may be found in the section "Apparatus Testium". This section explains how to encode testimonia in the apparatus criticus.
<note> (note) contains the relevant testimonium and a citation of its source if the testimonium is to be considered as supporting evidence for a reading.
Martianus Capella quotes Catullus 14.9 section 3.299 of his De nuptiis Philologiae et Mercurii: "hoc etiam Catullus quidam, non insuavis poeta, commemorat dicens 'munus dat tibi Sylla litterator.'" Thomson identifies the citation in his apparatus testium as follows: "9 Martianus Capella 3.229." In the apparatus criticus, he writes: "9 sulla δ (Sylla Martianus Capella): si illa V."
The parentheses suggest that Thomson considers "Sylla" to be not a unique reading, but an orthographical variant of δ's "sulla". In an LDLT edition, this presentation of the information, including the separate apparatus testium would be encoded as follows:
Note that Thomson records the citation in the apparatus testium, not in the apparatus criticus. One could eliminate the apparatus testium and include the citation in the apparatus criticus:
If a testimonium is to be considered a witness to a lemma or a variant reading, the relevant text must be encoded with <lem> or <rdg>, and <wit> should be used to encode the citation.
For example, Thomson cites Pliny the Younger as a witness to several readings in Catullus 16. In the apparatus testium, Thomson prints "5–8 Plinius, Epistulae 4.14.5". Leaving aside the more complex entry for tum, which involves a correction (a subject dealt with at length elsewhere in these guidelines), the relevant entries in the apparatus are: "7 ac V: et Plinius 8 sunt Plinius: sint V ac V: et Plinius."
Fully accounting for Thomson's use of an apparatus testium, this information would be encoded in an LDLT edition as follows:
In other words, <note> defines a witness for a specific number of lines, then <wit> is used to record Pliny as a witness.
If there had been only one reading to report, the citation could have been included in <wit>:
Alternatively, a <witness> could be defined for this passage in the edition's front matter (i.e., in a <listWit> containing testimonia). In that case, Pliny would be recorded in wit using his machine-readable siglum (e.g., "Plinius4.14":
All of these methods accomplish the objective of identifying a testimonium and referring to it in the apparatus criticus. The needs of individual editors and their texts will determine which method is most appropriate.
Most entries in an critical apparatus concern text within the boundaries of a structural unit such as a line of poetry or a section within a paragraph, but sometimes it is necessary for entries to cross those structural boundaries. This presents a problem for the hierarchical nature of XML, since a "child" element cannot overlap its "parent" element. Using next and prev can compensate for that issue.
For example, the witness V omits the final word of section 18.3 and all of section 18.4 from the Bellum Alexandrinum. In a print edition, it would be possible to write the following: enatauerunt … 18.4 fuit VI milium om. V, but in an LDLT edition, the <app> contained by <seg> 3 cannot extend into <seg> 4. It must be encoded using next and prev as follows:
This particular example could also be handled with <lacunaStart> and <lacunaEnd>, as described in the section "Gaps in Witnesses."
For the sake of keeping the emphasis on the grouping of witnesses or sources, it may be necessary to indicate that variations on a reading appear in the group, instead of reporting which witnesses or sources have the variations. In that case, <note> can be used with contents an, aut, or vel.
If it is desirable to use a consensus reference (e.g., ω, ς) or a catch-all reference (e.g., codd. for codices, mss. for "manuscripts", cett. for ceteri codices, edd. for editores) the references must be defined in the bibliography of the edition according to the guidelines in the section “Catch-all References.” This section demonstrates how to insert consensus and catch-all references into the apparatus.
If consensus or catch-all references are used without any additional annotation, they may be treated like any other witness or source (i.e., as values of wit or source), provided that they have both machine- and human-readable sigla.
If they are annotated (e.g., edd. ante Glaeser), they must be encoded in <note> according to the guidelines below. Alternatively, if an annotated form is frequently used, an editor could consider adding that form to the list of references in the bibliography.
In the following example, the editor wishes to show that the editors of previous editions are divided, with one in particular (Glaeser) marking a definitive shift in preference.
This may be displayed or printed as vicit] N P Glaeser sqq. : vīcit G : ludit d : lusit V edd. ante Glaeser : visit μ : om. γ.
Omission is different from a lacuna, which is the absence or conjectured absence of an unknown or uncertain quantity of text from the tradition in general. This section explains how to encode omission of known quantities of text from a particular witness or witnesses. Two kinds of omission are discussed here:
Related sections:
Witnesses and sources sometimes omit items from the text. This section describes how to encode those omissions.
For example, the witness known as P omitted the word pecus from Calp. 1.38: securo custode pecus nocturnaque pastor. A traditional apparatus criticus might indicate the omission as follows: pecus om. P
In these guidelines, omission is represented by a so-called "self-closing" or empty <rdg> (i.e., <rdg />):
The same model applies to the omission of an entire line of verse by a witness or witnesses, but in that case <app> has type="line-omission" and <lem> contains the entire line, with the omission marked by a self-closing <rdg>:
This will be displayed in the apparatus criticus of an LDLT edition as ‘vers. om. n h’
[ . . . ] = The editor knows from context and/or observation how many characters have been lost. Each dot represents a missing character.
For example, in the apparatus criticus to Calp. 4.4, Giarratano has the following with reference to lemma spiritus amnis: ‘spc̅ N (deinde lac. 6 litt.)’.
In an LDLT edition, that would be encoded as follows:
That encoding would produce the following entry in the apparatus: ‘spc̅ [......]’. If it is desirable to supplement that with a note, the <rdg> should be given an xml:id and the note should be inserted in a <witDetail> pointing to it:
If a witness or family of witnesses has a gap in coverage of the text, for whatever reason, the gap may be noted in the apparatus criticus using <lacunaStart> and <lacunaEnd>.
The use of the term "lacuna" here is likely to cause confusion. The TEI Guidelines (12.1.5 Fragmentary Witnesses) use the term "lacuna" in the elements <lacunaStart> and <lacunaEnd>, which are used here to indicate a gap in a witness or group of witnesses. If the gap occurs in the entire tradition, the section "Lacunae" in these guidelines should be followed.
For example, sections 1.1–1.33.3 of Julius Caesar's de Bello Civili are missing from manuscript M. Cynthia Damon's OCT edition has the following in the critical apparatus: 1.1.1–1.33.3 M deest, vice eius m citatur.
In an LDLT edition, that should be encoded as follows:
At 1.33.3, Damon's apparatus criticus has: ‘-duum hinc adest M’. In an LDLT edition, that should be encoded as follows:
The presence of fragmentary witnesses should be noted in the apparatus criticus using <witStart> and <witEnd>.
For example, the fragmentary witnesses known collectively as "Exc. Par." (= Thuaneus 7647 and Nostradamensis 17903) in Giarratano's edition of Calpurnius Siculus have 5.12–13. Giarratano notes this fact in the apparatus criticus as follows: 12 et sq. habent Exc. Par.. In an LDLT edition, this should be noted in an <app> as follows:
<rdg> with wit and the value of the witness' machine-readable siglum (xml:id) encloses <witStart> or <witEnd> to show where the witness begins and ends. <witDetail> may be used to describe the presence of witnesses.
This section demonstrates how to indicate that text has been added to a witness. There are two methods for encoding additions: prose description and semantic markup. Both are described in this section. The same information is presented in both cases, but the semantic markup version supports additional functionality such as querying and filtering on readings added in the margin or elsewhere.
For additions made by the editor of the current edition or a previous editor, see the section "Editorial Additions and Deletions.”
For additional text in a witness or witnesses that does not correspond to anything in the edition's text, see the section
For example, the copyist of manuscript G has the lemma certare, but a later hand has added the variant reading certate in the margin.
89 certare] certate G1 in mg.
The prose description method uses <witDetail> to describe the addition:
The semantic markup method uses <add> to encode the addition:
The following guidelines demonstrate how to produce a notation about the deletion of text from a witness by a scribe, along with the method of deletion (if known).
For deletions made by the editor of the current edition or a previous editor, see the section "Editorial Additions and Deletions.”
Deletion almost always occurs as part of a correction. In that case, this section should be used in combination with the guidelines in the section “Correction.” The examples in this section represent deletion as part of a correction.
There are two methods for encoding deletions: prose description and semantic markup. Both are described in the following subsections. The same information is presented in both cases, but the semantic markup version will support additional functionality such as querying and filtering on deleted readings and the method of deletion.
The prose description method uses <witDetail> to describe the deletion:
The output of this encoding would be amotae] adamote G (a.c.), amote G1 (ad exp.)
The semantic markup method uses <del> to encode the deletion. Deletions encoded according to these guidelines will be displayed or printed enclosed in double brackets: ⟦ ⟧.
The output of this encoding would be amotae] adamote G (a.c.), 〚ad〛amote G1 (p.c., ad exp.)
It is occasionally necessary to indicate the presence of illegible characters in a witness' text.
For example, at Calp. 6.4, the lemma is dedit, but the witness known as N has deo and some illegible characters after it. Giarratano has indicated the presence of illegible characters with an asterisk: deo *. These guidelines use dashes to indicate illegible characters, but the attributes reason, extent, and unit provide more information.
Transpositions may be handled in two ways: prose description or semantic markup. Prose description produces a note in the apparatus criticus. Semantic encoding produces a note in the apparatus criticus, but it will also enable readers to swap the transpositions in and out of the text in a digital version.
The sections below demonstrate the prose description and semantic markup methods for the following examples:
Example 1: In the Teubner edition of Ovid’s Tristia, J.B. Hall follows the recommendation of Wilamowitz and transposes lines 41–42 of poem 3.12 so that they follow line 36. In the apparatus criticus, Hall writes ‘41–42 post 36 transposuit Wilamowitz.’
Example 2: In Richard Tarrant’s OCT of Ovid’s Metamorphoses, the text of 1.304–305 is as follows:
In the apparatus criticus, Tarrant notes the following: 304–5 fuluos … tigres om. HMac(Nac); habet Bern, sed ordine turbato (nat … oues nec uires f. apro | unda u. tigres, fuluos … leones)
To describe this transposition in the apparatus criticus, <app> encloses the affected passage, and <witDetail> or <note> contains the description.
Example 1 (Ov. Tr. 3.12.36ff.)
Example 2 (Ov. Met., 1.304–305):
Neither one of these examples would support the functionality of swapping the transpositions in and out of the main text of the edition. Instead, readers would just see a note in the apparatus criticus describing the transposition.
In some cases, a transposition may be semantically encoded using the basic pattern for an apparatus entry. In example 1 (Ov. Tr. 3.12.36ff., text above), there are basically two forms of the text: with and without the transposition. Since the editor (Hall) has accepted Wilamowitz’ proposed transposition, the transposed version is contained in <lem> and the original is contained in <rdg>:
This will allow users to toggle between the original and emended versions of the text. Using exclude ensures that lines 41–42 will never be displayed in two places at once. When the lemma (i.e., Wilamowitz’ emendation) is displayed in the edition text, lines 41–42 will follow line 36. When the reading that has lines 41–42 following line 40 is selected for display, Wilamowitz’ emendation will be excluded from the display.
More complicated transpositions, like the one in the second example below, operate in the same way: using exclude and require ensures that mutually exclusive readings are never displayed together.
Keeping track of the mutually exclusive readings can be a challenge, as the example below demonstrates. When encoding complex transpositions, it can be helpful to make a table or to use some other method of keeping track of the mutually exclusive readings.
Example 2 (Ov. Met., 1.304–305, text above). In this example, the witness known as Bern transposes portions of two lines. Witnesses H Mac (and Nac) conflate the lines, which is another kind of transposition (or omission). That is, it can be assumed that they did not write the first half of the line at 304 and the second half of the line at 305, but rather wrote the two halves together on the same line (i.e., nat lupus inter oues, nec uires fulminis apro).
The extensive markup in this example calls for explication. The desired outcomes are:
These outcomes require nested <app> elements:
Instead of entering the text of the transposed lines more than once, copyOf causes the text to be inserted automatically. This not only reduces the potential for errors in transcription, but also acknowledges that the text is otherwise identical.
The use of require ensures that Bern's transposed lines will be displayed or printed together. That is, the reader will not see one correctly transposed half-line and one without transposition, since that would be a false representation of Bern's text.
The use of <join> to represent the conflated lines in H and M allows the text of the two lemmata in question to be copied and displayed or printed together.
The effort required to keep track of the mutually exclusive readings pays off in the ability to swap the conflated and transposed readings in and out of the edition text in the digital version.
In some cases, it may be necessary to show that a witness or a source has variants in separate places that are related to each other. For example, the text of Calp. 6.68 is as follows: ‘imminet exesa veluti testudine concha.’. Heinsius proposes exesae - conchae. That means that whenever the lemma exesa is displayed, the lemma concha must also be displayed, and whenever one of Heinsius’ conjectures is displayed, the other one must accompany it. In other words, exesa should not be displayed with conchae and exesae should never be displayed with concha
As with line transpositions, exclude and require are used to prevent mutually exclusive readings from being displayed together. Calp. 6.68 should be encoded as follows:
Correction has been discussed in the section “Concepts and Definitions.” In short, for the purposes of these guidelines, “correction” describes any attempt by the original copyist or some other hand to alter a witness’ reading, whether or not the result matches what is in the main edition text.
The amount of detail to report about corrections is a matter for editors to decide; these guidelines accommodate a range of approaches. When determining the method to use, editors should bear in mind not only the amount of detail necessary to communicate the nature of a correction, but also the functionality they want their edition to support. The subsections below include discussions intended to help editors make those decision.
Before reading the encoding guidelines for corrections, it is recommended to read the section “Correction as Metadata” to understand the concepts behind the guidelines.
Over time, editors have devised creative ways of reporting corrections. The simplest method is to report readings and annotate them with ante correctionem, post correctionem, or something similar. Another method is to add abbreviations for those phrases as superscript notations on manuscript sigla (e.g., Bac, Bpc). Sometimes it is necessary to provide more detail about the method of correction, in which cases editors will either describe the correction (e.g., t exp., r add. s.l.) or they will try to represent it typographically (e.g., referṭre). Some rely on superscript notation for all of these details (e.g., Pcsl = P correctio supra lineam).
The different methods have advantages and disadvantages, but each one effectively demonstrates that correction is a complex subject. Even the word “correction” is problematic, since it can refer to the result of a process or the process itself. Therefore, representing correction faithfully in a digital critical edition depends on careful analysis of the information that comprises a correction.
Aside from judgments about correctness, “correction” may involve at least four kinds of information:
In the context of a digital edition, it is useful to think of readings as the data, and the information about state, agency, method, and relationship as metadata, or data about the data.
Not all of these metadata items will be reported in every instance. The original reading, for example, obviously does not have a method of correction, but it will have a state (original). The original reading might have a correspondence to show that it is related to its altered form, if one is provided, but it is not always necessary to report the altered form. For example, if the altered form matches the lemma in the main text of the edition, it may be sufficient to report the original form with a note that it was corrected (the inference being that it was corrected to the lemma printed in the edition, if no other form is reported). Similarly, it may not be necessary to report the method of correction.
It is possible to use techniques described elsewhere in these guidelines to encode the details of corrections (e.g., deletion and/or addition of characters), but it is also possible to describe those details in prose. The examples below demonstrate both options.
The simplest way of encoding descriptions is to define sigla in the <handNote> section of a manuscript description. For example, an editor might define Vac and Vpc for readings of manuscript V before and after correction, if it makes sense to do so. In that case, original and corrected readings will be encoded in the same way as any other readings, with <lem> or <rdg> inside of <app>.
Where there are multiple hands or other factors to consider, relying on sigla to indicate the state of correction may restrict options for representing the manuscript's data. The following subsections offer guidance for encoding those instances.
Readings before and after correction are encoded as any other readings, i.e., with <rdg> inside of <app>.
The details of the correction are contained in <witDetail>, with the use of several attributes to determine how the information is processed. However, if the decision has been made to use sigla to indicate uncorrected or corrected readings (see the section "Correction as Metadata"), <witDetail> is not necessary.
It is impossible to describe all of the possible scenarios for correction, but the examples in the following sections should provide a basis for determining how to encode the most common instances.
The first example is simple correction of a variant reading to the lemma: protegit] protegis G (a.c.).
It is clear in this instance what the reading after correction is, so there is no need to report it. There is no need to list all of the other witnesses to the lemma, since it is clear that the uncorrected form is a unique reading. Also, the editor has decided that it is not useful to indicate which hand made the correction. In this example, manuscript G simply has the variant reading protegis for the lemma protegit, to which the variant reading in G has been corrected in some way.
If the sigla are being used to convey information about correction, the following encoding will be sufficient:
In this example, the machine-readable siglum "Gac" indicates that the reading protegis was present prior to correction. And since the human-readable siglum for "Gac" can be set to "G a.c.", the entry in the apparatus can be displayed as "protegit] protegis G a.c."
The same passage could also be encoded with <witDetail>, if the editor prefers to keep correction state separate from the siglum for the manuscript:
That is, <witDetail> uses target to point to the variant reading, and type shows that protegis is the original, uncorrected form.
This example is similar to the first one, but it is necessary to indicate which hand made the correction.
The lemma is insidias. Manuscript N has insidia; N2 has added the letter “s.” A traditional apparatus criticus might report this as follows: insidias] insidia N (corr. N2).
As in the first example, the encoding for the method that represents correction with sigla is straightforward:
The siglum Nac indicates the reading before correction. The siglum Npc indicates the reading after correction, and the usage of copyOf shows that the corrected form matches the lemma. Using <witDetail> allows the editor to indicate which hand made the correction.
The following example shows how the same passage could be encoded with more metadata:
This encoding will produce the following entry in the apparatus criticus: insidias] insidia N(a.c.) insidias N2(p.c.).
In this example, a variant reading is corrected to the lemma, but for a number of reasons it is important to indicate the reading before and after correction.
The witness N originally had co and ice with an erasure of two characters between them. The correcting hand N2 has inserted the letters “r” and “t” in the erasure. The corrected form (cortice) matches the reading in witnesses P and V. Another reading is present in witnesses G and A.
A traditional apparatus criticus might report this as follows: cortice N2 (p.c., rt add. in ras.) PV : co⟦..⟧ice N (a.c.) : codice G A.
Using sigla to indicate both manuscripts and their state of correction, that passage should be encoded as follows:
This encoding will produce the following entry in the apparatus criticus: cortice Npc (rt add. in ras. N2) PV : co⟦..⟧ice Nac : codice G A.
More metadata, however, could be encoded using the following method:
This encoding will produce the following entry in the apparatus criticus: cortice PV : co«rt»ice N2 (p.c.) : co⟦..⟧ice N (a.c.) : codice G A.
This example includes multiple corrections.
The lemma is descripta. Manuscript N originally had dipicta, but N1 corrected it to depicta. Another hand (N2 has descripta in the margin. Other manuscripts support these and other readings.
A traditional apparatus criticus might report this as follows: descripta P V N2 (in mg.) : depicta G N1 (p.c.) : dipicta N (a.c.).
Using sigla to indicate both manuscripts and their state of correction, that passage should be encoded as follows:
This encoding will produce the following entry in the apparatus criticus: descripta N2 (in mg.) PV : depicta G N1 (p.c.) : dipicta N (a.c.).
The following method accomplishes the same thing, but with richer metadata:
As explained in the section Concepts and Definitions, conjectures are readings that are not supported by documentary evidence, but are instead proposed by someone and considered by the editor to be worthy of inclusion in a critical edition. A conjecture is called an emendation if it is adopted as the official reading of a particular criticial edition’s main text. In other words, for the purposes of these guidelines, an emendation is a “successful conjecture.” But above all, conjectures and emendations are readings (<lem> or <rdg>), and they are encoded as such in LDLT editions.
Traditionally, conjectures and emendations have been annotated in various ways in critical editions (e.g., ci. or conj. for coniecit, em. or emend. for emendavit, among others). They should be annotated in digital editions, too, both to facilitate their identification and to enable features such as filtering and searching for them. The annotation is accomplished with type.
Since an emendation is a conjecture that has been adopted for the main text of the edition, only <lem> may have type with the value “emendation.” It could be inferred that a lemma with source only is an emendation, but in the interest of being explicit, an emendation should be annotated accordingly. Using type with the value of “emendation” will also facilitate searching and filtering for emendations.
Conversely, only <rdg> may have type with the value “conjecture.” It could be inferred that a reading with source only is a conjecture, but it is best to be explicit in the identification, if for no other reason than ensuring that “conjecture” is available as a criterion for searching and filtering.
The following example demonstrates how to encode both an emendation and a conjecture.
This encoding will produce plenumque in the main text of the edition and the following in the apparatus criticus: plenumque] em. Haupt (prob. Keene et Schenkl) : primumque ω edd. : rivumque ci. Baehr. : pronumque ci. C. Schenkl.
Multiple conjectures proposed by a single person should be separated by <note> with value vel (or something similar).
This would be displayed in the apparatus criticus as pallenti] ridenti vel varianti vel vernanti vel roranti ci. Heins.
Occasionally, editors propose conjectures at the end of an entry in the critical apparatus but express uncertainty or doubt about the viability of the proposal.
For example, Cynthia Damon prints the following in her OCT edition of Caesar's De Bello Civili at 1.24.3: relicto praetore] -tis -oribus Basiner coll. Cic. Att. 9.6.1 : an [r- p-]?
At the end of that entry, Damon has suggested the deletion of relicto praetore, but it is only a suggestion for others to consider. In an LDLT edition, that would be encoded as follows:
In some cases, an editor may wish to indicate that text has been supplied or removed by conjecture. The following subsections describe the methods for encoding editorial additions and deletions.
< > = Text added or supplied by conjecture where text does not exist in the documentary evidence.
For example, Cynthia Damon prints the following in her OCT of Caesar's de Bello Civili: Ipsi Massilienses et celeritate nauium et scientia gubernatorum confisi nostros eludebant impetusque eorum excipiebant <cedendo>.
Her apparatus criticus has the following:
excipiebant <cedendo> scripsi ex Luc. 3.55 (cf. Liu. 29.34.13) : <non> exc- Kramer : dec- Nipperdey (cf. Stat. Theb. 2.304) : effugiebant Terpstra coll. 2.41.6 : nisi mauis e.g. <laxata classe> exc- ex Luc. 3.548 (cf. BG 2.25.2).
Every instance of text enclosed in < > indicates that text has been added where text does not exist in the documentary evidence.
In an LDLT edition, that would be encoded as follows:
The use of <supplied> will cause < and > to be inserted on either side of the text added by conjecture. The rest of the information is handled as a normal entry in the apparatus criticus.
If it is desirable to indicate in the apparatus criticus that a previous editor has proposed adding some text, even if the addition has not been adopted for the main text of the edition, <supplied> should be used inside of <rdg>. If the reading is swapped into the main text in the digital version, it will appear inside < and >.
{ } = Text considered by the editor to be inauthentic, but nevertheless retained between braces in the edition to indicate that it is part of the text’s documentary history.
Square brackets have been used to indicate editorial deletions in the past, but, as West argues (p. 80), this is apt to cause confusion, since square brackets have a different meaning for papyrologists and epigraphists (see “Undetermined Amount Of Text Lost” in these guidelines). Accordingly, LDLT editions follow West’s suggestion to use braces to indicate editorial deletions.
For example, at section 29 of Suetonius’ life of Claudius, Robert Kaster indicates in the text of his OCT edition that he accepts as correct the deletion of two words by previous scholars: His, ut dixi, uxoribusque addictus non principem {se} sed ministrum egit, compendio cuiusque horum uel etiam studio aut libidine honores exercitus impunitates supplicia largitus {est} et quidem insciens plerumque et ignarus.
The entry for the first one in the apparatus criticus has the following: ‘se secl. Graev. 1697, 411 (Polak 1882, 12)’. The entry for the second one is as follows: ‘est del. Bent.’.
In an LDLT edition, the deletion would be encoded in the text as follows:
The use of <surplus> will cause the braces { } to be inserted on both sides of the word(s) to be deleted (when displayed in the LDLT Viewer). The rest of the information is handled as a normal entry in the apparatus criticus.
If it is desirable to indicate in the apparatus criticus that a previous editor has proposed deleting some text, even if the deletion has not been adopted for the main text of the edition, <surplus> should be used inside of <rdg>. If the reading is swapped into the main text in the digital version, the braces { } will be displayed around the reading.
<***> = A lacuna has been conjectured on the grounds of style, context, or carelessness of a copyist (e.g., saut du même au même). No text has been supplied in its place.
The conjectured lacuna itself should be encoded with <gap> with reason="lost" as indicated in the section “Lacunae.” To indicate that it has been added by conjecture, <gap> should be enclosed by <supplied>. Further, if it has been accepted by the editor of the edition, it should be contained by <lem> with type="emendation". If the conjectured lacuna is only noted in the apparatus criticus, then it should be contained by <rdg> with type="conjecture".
For example, at the conclusion of section 3.8.4 of Julius Caesar's de Bello Civili, Cynthia Damon's OCT edition has the following in the main text: si in Caesaris complexum uenire posset ***. The apparatus criticus has the following annotation: lacunam statuit Vascosanus.
In an LDLT edition, that should be encoded as follows:
The same encoding should be used to indicate the conjectured lacuna of a number of lines of verse. For example, Verdière argues that nine verses have been omitted by the copyist of the archetype of all manuscripts of Calpurnius Siculus' eclogues. He prints nine lines of equally spaced dots in the text, and he writes in the apparatus criticus, ‘u. 1–9 librarii incuria cecidisse puto.’
If the editor of an LDLT edition of Calpurnius accepts this argument, Verdière's conjecture would be encoded as follows:
In the LDLT Viewer, nine lines of < *** > would be printed at the beginning of the text, and the numbering of the lines that follow would begin with 10. The apparatus criticus would have the entry ‘u. 1–9 librarii incuria cecidisse putavit Verdière’.
Text found in a witness that does not correspond to anything in the edition's text, but that is nevertheless worth reporting, is commonly represented in printed editions by referring to a word or words that serve as an anchor for the additional text.
For example, the text of Andrew Dunning's edition of the Miracula sancte Frideswide includes the word archiepiscopus, and the critical apparatus has "cantuariensis add. L," indicating that the manuscript known as L has a word that Dunning considered extraneous, but worth reporting.
This phenomenon could be encoded using the method described in the section on addition in these guidelines:
That, however, does not accurately describe the situation, which is that the witness did not add the text; rather, the text exists in the witness, but the editor chooses not to include it in the edition's text. Since there is not, strictly speaking, a lemma for this additional text, an "empty" lemma must be used:
Although it is possible to avoid using n in this way by leveraging computational methods to look up the preceding word or words, these guidelines opt for simplicity. The empty <lem> signifies that the edition's text does not have anything where a witness has something, but n provides context and an anchor for the witness' text. For the sake of accuracy, the edition's text should be copied and pasted as the value of n.
† † = Text deemed by the editor to be readable but not understandable, with no satisfactory alternative or convincing emendation.
For example, at section 2.4.12 of Macrobius’ Saturnalia, Robert Kaster marks two words in the text of his OCT edition with cruces:… “vale mel gentium †meculle†, ebur ex Etruria, lasar Arretinum, adamas Supernas, Tiberinum margaritum, Cilniorum smargde, iaspi figulorum, berulle Porsenae, carbunculum †habeas†, ἵνα συντέμω πάντα, ἄλλαγμα moecharum.”
In the apparatus criticus for the first crux, Kaster has the following: ‘meculle Nβ(melcule DP2G, n.l. P1): Medulliae Turnebus 1604, 584.’ The second one is simpler: ‘habeas] Hadriae Jahn’.
The following example demonstrates how these cruces would be encoded in an LDLT edition:
The use of <sic> would cause the symbol † to be placed on both ends of each crux in the LDLT Viewer. The rest of the information would be handled in the normal manner for readings in the apparatus criticus.
An editor may enhance an edition’s functionality by adding one or more of the analytical “tags” listed below. Use of these tags will enable additional filtering and querying functionality, such as filtering out purely orthographical variants or focusing on variants that affect the syntax of the text.
It is up to the editor to decide how extensively to apply these analytical tags, if at all. If analytical tags are used, the preface should make clear which ones are used and why they are used. For example, an editor may wish only to tag orthographical variants so that users can filter them in or out of the text as they please.
ana (analysis) on <rdg> applies one or more of the following values to a reading:
These guidelines cover most of the types of information commonly found in a critical apparatus, but not all of them, since it would be impossible to anticipate everything any editor of a text would ever need to encode.
If a certain kind of annotation or comment is needed, but a method for encoding it is not described in these guidelines, <witDetail> or <note> may be used ad hoc, depending on whether the subject is a single witness (<witDetail>) or something of a more general nature (<note>).
These guidelines may also be extended as the community of users discovers and proposes additional encoding patterns to the staff of the LDLT.
Traditionally, extended commentary on textual matters has been published apart from the critical edition (e.g., as a monograph or in textual notes published in periodicals). Editors of LDLT editions are encouraged to include longer notes on textual matters in a section enclosed in <div> with xml:id="textual-commentary".
This section demonstrates how to encode longer notes.
For example, after Calp. 4.96, Giarratano prints five unnumbered lines of dots to indicate that he believes a stanza is missing. At 4.97, he includes in his apparatus criticus an extended discussion about his rearrangement of several sets of lines. In an LDLT edition, it is preferable to put that sort of discussion in the textual commentary. The following example demonstrates how it would be encoded in an LDLT edition:
This encoding will produce the following in a digital or print version:
The digital version will have the additional feature of links from the apparatus to the commentary and from the commentary to the apparatus.
The following is a list of works cited in these guidelines.
| <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. [«#DS» «#CCDEF»] | |||||||||
| Module | textstructure | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" 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> | ||||||||
| 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> | ||||||||
| Schematron |
<sch:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<sch:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/> | ||||||||
| Schematron |
<sch:ns prefix="rng"
uri="http://relaxng.org/ns/structure/1.0"/> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="teiHeader"/>
<alternate>
<sequence>
<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
{
tei_att.global.attributes,
tei_att.typed.attributes,
attribute version { text }?,
( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}⚓ | ||||||||
| <ab> (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. Blocks, Segments, and Anchors] | |
| Module | linking |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declaring (@decls) att.fragmentable (@part) att.written (@hand) |
| Member of | |
| Contained by | corpus: particDesc settingDesc header: abstract application availability cRefPattern calendar change correction correspAction correspContext correspDesc editionStmt editorialDecl encodingDesc handNote hyphenation interpretation langUsage licence normalization prefixDef projectDesc publicationStmt punctuation quotation refsDecl samplingDecl scriptNote segmentation seriesStmt sourceDesc stdVals styleDefDecl msdescription: accMat acquisition additions binding bindingDesc collation condition custEvent custodialHist decoDesc decoNote filiation foliation handDesc history layout layoutDesc msContents msDesc msFrag msItem msItemStruct msPart musicNotation objectDesc origin physDesc provenance recordHist scriptDesc seal sealDesc signatures source summary support supportDesc surrogates typeDesc typeNote spoken: transcriptionDesc transcr: metamark |
| May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct ellipsis email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs ruby said sic soCalled stage term time title unclear unit figures: figure notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName listEvent listNym listObject listOrg listPerson listPlace listRelation location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data |
| Note | The <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. |
| Example | <div type="book" n="Genesis">
<div type="chapter" n="1">
<ab>In the beginning God created the heaven and the earth.</ab>
<ab>And the earth was without form, and void; and
darkness was upon the face of the deep. And the
spirit of God moved upon the face of the waters.</ab>
<ab>And God said, Let there be light: and there was light.</ab>
<!-- ...-->
</div>
</div> |
| Schematron |
<sch:report test=" (ancestor::tei:p or ancestor::tei:ab) and not( ancestor::tei:floatingText
|parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q
|parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp
|parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: ab may not occur inside paragraphs or other ab elements.
</sch:report> |
| Schematron |
<sch:report test=" (ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText
|parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText.
</sch:report> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element ab
{
tei_att.global.attributes,
tei_att.typed.attributes,
tei_att.declaring.attributes,
tei_att.fragmentable.attributes,
tei_att.written.attributes,
tei_macro.paraContent
}⚓ |
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions] | |||||||||||||
| Module | core | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del desc distinct editor email emph expan foreign gloss head headItem headLabel hi item l label measure meeting mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said sic soCalled speaker stage street term textLang time title unit header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset orgName persName persPronouns placeName region roleName settlement surname textstructure: byline dateline docAuthor docDate docEdition docImprint titlePart | ||||||||||||
| May contain | core: abbr add address binaryObject cb choice cit corr date del distinct ellipsis email emph expan foreign gap gb gloss graphic hi index lb measure measureGrp media mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs ruby said sic soCalled term time title unclear unit figures: figure notatedMusic gaiji: g header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data | ||||||||||||
| Note | If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>. | ||||||||||||
| Example | <choice>
<expan>North Atlantic Treaty Organization</expan>
<abbr cert="low">NorATO</abbr>
<abbr cert="high">NATO</abbr>
<abbr cert="high" xml:lang="fr">OTAN</abbr>
</choice> | ||||||||||||
| Example | <choice>
<abbr>SPQR</abbr>
<expan>senatus populusque romanorum</expan>
</choice> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element abbr
{
tei_att.global.attributes,
tei_att.typed.attribute.subtype,
attribute type { text }?,
tei_macro.phraseSeq
}⚓ | ||||||||||||
| <abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | figures: table linking: ab namesdates: listEvent listNym listObject listOrg listPerson listPlace listRelation |
| Note | This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a <div> within the <front>, as it should for a born-digital document. |
| Example | <profileDesc>
<abstract resp="#LB">
<p>Good database design involves the acquisition and deployment of
skills which have a wider relevance to the educational process. From
a set of more or less instinctive rules of thumb a formal discipline
or "methodology" of database design has evolved. Applying that
methodology can be of great benefit to a very wide range of academic
subjects: it requires fundamental skills of abstraction and
generalisation and it provides a simple mechanism whereby complex
ideas and information structures can be represented and manipulated,
even without the use of a computer. </p>
</abstract>
</profileDesc> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<classRef key="model.listLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element abstract
{
tei_att.global.attributes,
( tei_model.pLike | tei_model.listLike )+
}⚓ |
| <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct ellipsis email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note noteGrp num orig p pb ptr q quote ref reg rs ruby said sic soCalled sp stage term time title unclear unit figures: figure notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName listEvent listNym listObject listOrg listPerson listPlace listRelation location objectName offset orgName persName persPronouns placeName region roleName settlement state surname spoken: annotationBlock tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data |
| Example | <accMat>A copy of a tax form from 1947 is included in the envelope
with the letter. It is not catalogued separately.</accMat> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element accMat
{
tei_att.global.attributes,
tei_att.typed.attributes,
tei_macro.specialPara
}⚓ |
| <acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) |
| Contained by | msdescription: history |
| May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct ellipsis email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note noteGrp num orig p pb ptr q quote ref reg rs ruby said sic soCalled sp stage term time title unclear unit figures: figure notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName listEvent listNym listObject listOrg listPerson listPlace listRelation location objectName offset orgName persName persPronouns placeName region roleName settlement state surname spoken: annotationBlock tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data |
| Example | <acquisition>Left to the <name type="place">Bodleian</name> by
<name type="person">Richard Rawlinson</name> in 1755.
</acquisition> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element acquisition
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_macro.specialPara
}⚓ |
| <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions] | |||||||
| Module | core | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi item l label measure mentioned name note num orig p pubPlace publisher q quote rb ref reg rs rt said sic soCalled speaker stage street term textLang time title unit figures: cell msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset orgName persName persPronouns placeName region roleName settlement surname textstructure: byline dateline docAuthor docDate docEdition docImprint titlePart | ||||||
| May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct ellipsis email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs ruby said sic soCalled stage term time title unclear unit figures: figure notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName listEvent listNym listObject listOrg listPerson listPlace listRelation location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data | ||||||
| Note | In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended. In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project. | ||||||
| Example | The story I am
going to relate is true as to its main facts, and as to the
consequences <add place="above">of these facts</add> from which
this tale takes its title. | ||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||
| Schema Declaration |
element add
{
tei_att.global.attributes,
tei_att.transcriptional.attributes,
tei_att.typed.attributes,
tei_att.dimensions.attributes,
attribute place
{
"above"
| "below"
| "bottom"
| "inline"
| "inRas"
| "interlinear"
| "left"
| "margin"
| "mixed"
| "opposite"
| "overleaf"
| "overstrike"
| "right"
| "top"
| "unspecified"
}?,
tei_macro.paraContent
}⚓ | ||||||
| <addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [11.3.1.4. Additions and Deletions] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.placement (@place) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi imprint item l label lg list measure mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said series sic soCalled sp speaker stage street term textLang time title unit header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset orgName persName persPronouns person personGrp persona placeName region roleName settlement surname |
| May contain | Empty element |
| Note | Both the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute. |
| Example | <handNote xml:id="HEOL"
scribe="HelgiÓlafsson"/>
<!-- ... -->
<body>
<div>
<!-- text here -->
</div>
<addSpan n="added_gathering" hand="#HEOL"
spanTo="#P025"/>
<div>
<!-- text of first added poem here -->
</div>
<div>
<!-- text of second added poem here -->
</div>
<div>
<!-- text of third added poem here -->
</div>
<div>
<!-- text of fourth added poem here -->
</div>
<anchor xml:id="P025"/>
<div>
<!-- more text here -->
</div>
</body> |
| Schematron |
<sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> |
| Schematron |
<sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element addSpan
{
tei_att.global.attributes,
tei_att.transcriptional.attributes,
tei_att.placement.attributes,
tei_att.typed.attributes,
tei_att.spanning.attributes,
tei_att.dimensions.attributes,
empty
}⚓ |
| <additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | |
| May contain | core: listBibl msdescription: adminInfo surrogates |
| Example | <additional>
<adminInfo>
<recordHist>
<p>
<!-- record history here -->
</p>
</recordHist>
<custodialHist>
<p>
<!-- custodial history here -->
</p>
</custodialHist>
</adminInfo>
<surrogates>
<p>
<!-- information about surrogates here -->
</p>
</surrogates>
<listBibl>
<bibl>
<!-- ... -->
</bibl>
<!-- full bibliography here -->
</listBibl>
</additional> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="adminInfo" minOccurs="0"/>
<elementRef key="surrogates"
minOccurs="0"/>
<elementRef key="listBibl" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element additional
{
tei_att.global.attributes,
( tei_adminInfo?, tei_surrogates?, tei_listBibl? )
}⚓ |
| <additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct ellipsis email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note noteGrp num orig p pb ptr q quote ref reg rs ruby said sic soCalled sp stage term time title unclear unit figures: figure notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName listEvent listNym listObject listOrg listPerson listPlace listRelation location objectName offset orgName persName persPronouns placeName region roleName settlement state surname spoken: annotationBlock tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data |
| Example | <additions>
<p>There are several marginalia in this manuscript. Some consist of
single characters and others are figurative. On 8v is to be found a drawing of
a mans head wearing a hat. At times sentences occurs: On 5v:
<q xml:lang="is">Her er skrif andres isslendin</q>,
on 19r: <q xml:lang="is">þeim go</q>,
on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
batar þad mælgi ok mal</q>,
On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
</additions> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element additions { tei_att.global.attributes, tei_macro.specialPara }⚓ |
| <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Member of | |
| Contained by | core: address |
| May contain | core: abbr add address binaryObject cb choice cit corr date del distinct ellipsis email emph expan foreign gap gb gloss graphic hi index lb measure measureGrp media mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs ruby said sic soCalled term time title unclear unit figures: figure notatedMusic gaiji: g header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo character data |
| Note | Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text. |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL</addrLine>
<addrLine>60680 USA</addrLine>
</address> |
| Example | <addrLine>
<ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }⚓ |
| <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope citedRange corr date del desc distinct editor email emph expan foreign gloss head headItem headLabel hi item l label measure meeting mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said sic soCalled speaker stage street term textLang time title unit header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote language licence principal publicationStmt rendition scriptNote sponsor tagUsage msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName location objectIdentifier objectName offset orgName persName persPronouns placeName region roleName settlement surname textstructure: byline dateline docAuthor docDate docEdition docImprint titlePart |
| May contain | core: addrLine cb ellipsis gap gb index lb milestone name note noteGrp pb postBox postCode rs street figures: figure notatedMusic header: idno |
| Note | This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc. |
| Example | Using just the elements defined by the core module, an address could be represented as follows: <address>
<street>via Marsala 24</street>
<postCode>40126</postCode>
<name>Bologna</name>
<name>Italy</name>
</address> |
| Example | When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>: <address>
<street>via Marsala 24</street>
<postCode>40126</postCode>
<settlement>Bologna</settlement>
<country>Italy</country>
</address> |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL 60680</addrLine>
<addrLine>USA</addrLine>
</address> |
| Example | <address>
<country key="FR"/>
<settlement type="city">Lyon</settlement>
<postCode>69002</postCode>
<district type="arrondissement">IIème</district>
<district type="quartier">Perrache</district>
<street>
<num>30</num>, Cours de Verdun</street>
</address> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.addrPart"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element address
{
tei_att.global.attributes,
( tei_model.global*, ( tei_model.addrPart, tei_model.global* )+ )
}⚓ |
| <adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | msdescription: additional |
| May contain | |
| Example | <adminInfo>
<recordHist>
<source>Record created <date>1 Aug 2004</date></source>
</recordHist>
<availability>
<p>Until 2015 permission to photocopy some materials from this
collection has been limited at the request of the donor. Please ask repository staff for details
if you are interested in obtaining photocopies from Series 1:
Correspondence.</p>
</availability>
<custodialHist>
<p>Collection donated to the Manuscript Library by the Estate of
Edgar Holden in 1993. Donor number: 1993-034.</p>
</custodialHist>
</adminInfo> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="recordHist"
minOccurs="0"/>
<elementRef key="availability"
minOccurs="0"/>
<elementRef key="custodialHist"
minOccurs="0"/>
<classRef key="model.noteLike"
minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element adminInfo
{
tei_att.global.attributes,
(
tei_recordHist?,
tei_availability?,
tei_custodialHist?,
tei_model.noteLike?
)
}⚓ |
| <altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) |
| Contained by | msdescription: msFrag msIdentifier namesdates: objectIdentifier |
| May contain | |
| Note | An identifying number of some kind must be supplied if known; if it is not known, this should be stated. |
| Example | <altIdentifier>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>MS.El.26.C.9</idno>
</altIdentifier> |
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<classRef key="model.placeNamePart"
expand="sequenceOptional"/>
<elementRef key="institution"
minOccurs="0"/>
<elementRef key="repository"
minOccurs="0"/>
<elementRef key="collection"
minOccurs="0"/>
<elementRef key="idno"/>
<elementRef key="note" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element altIdentifier
{
tei_att.global.attributes,
tei_att.typed.attributes,
tei_att.datable.attributes,
(
tei_placeName?,
tei_bloc?,
tei_country?,
tei_region?,
tei_settlement?,
tei_district?,
tei_geogName?,
tei_institution?,
tei_repository?,
tei_collection?,
tei_idno,
tei_note?
)
}⚓ |
| <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice citedRange corr date del desc distinct editor email emph expan foreign gloss head headItem headLabel hi item l label measure meeting mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said sic soCalled speaker stage street term textLang time title unit header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset orgName persName persPronouns placeName region roleName settlement surname textstructure: byline dateline docAuthor docDate docEdition docImprint titlePart |
| May contain | |
| Example | do you <abbr>Mr<am>.</am></abbr> Jones?
|
| Example | <choice>
<abbr>Aug<am>g</am></abbr>
<expan>Aug<ex>ustorum duo</ex></expan>
</choice> |
| Example | <abbr>eu<am>
<g ref="#b-er"/>
</am>y</abbr>
<abbr>
<am>
<g ref="#b-per"/>
</am>sone
</abbr> ...
|
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.pPart.transcriptional"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element am
{
tei_att.global.attributes,
tei_att.typed.attributes,
tei_att.editLike.attributes,
( text | tei_model.gLike | tei_model.pPart.transcriptional )*
}⚓ |
| <analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | core: biblStruct |
| May contain | |
| Note | May contain titles and statements of responsibility (author, editor, or other), in any order. The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item. |
| Example | <biblStruct>
<analytic>
<author>Chesnutt, David</author>
<title>Historical Editions in the States</title>
</analytic>
<monogr>
<title level="j">Computers and the Humanities</title>
<imprint>
<date when="1991-12">(December, 1991):</date>
</imprint>
<biblScope>25.6</biblScope>
<biblScope>377–380</biblScope>
</monogr>
</biblStruct> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="respStmt"/>
<elementRef key="title"/>
<classRef key="model.ptrLike"/>
<elementRef key="date"/>
<elementRef key="textLang"/>
<elementRef key="idno"/>
<elementRef key="availability"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element analytic
{
tei_att.global.attributes,
(
tei_author
| tei_editor
| tei_respStmt
| tei_title
| tei_model.ptrLike
| tei_date
| tei_textLang
| tei_idno
| tei_availability
)*
}⚓ |
| <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment] | |
| Module | linking |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi imprint item l label lg list listBibl measure mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said series sic soCalled sp speaker stage street term textLang time title unit header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset org orgName persName persPronouns person personGrp persona placeName region roleName settlement surname |
| May contain | Empty element |
| Note | On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence. |
| Example | <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/></s> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element anchor { tei_att.global.attributes, tei_att.typed.attributes, empty }⚓ |
| <annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container] | |||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||
| Attributes | Attributesatt.global (xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source) att.pointing (target, @targetLang, @evaluate)
| ||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||
| Contained by | linking: listAnnotation standOff | ||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||
| Example | <annotation xml:id="ann1"
motivation="linking" target="#Gallia">
<!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and
https://www.w3.org/TR/annotation-model/#agents -->
<respStmt xml:id="fred">
<resp>creator</resp>
<persName>Fred Editor</persName>
</respStmt>
<revisionDesc>
<change status="created"
when="2020-05-21T13:59:00Z" who="#fred"/>
<change status="modified"
when="2020-05-21T19:48:00Z" who="#fred"/>
</revisionDesc>
<!-- See https://www.w3.org/TR/annotation-model/#rights-information -->
<licence target="http://creativecommons.org/licenses/by/3.0/"/>
<!-- Multiple bodies -->
<!-- Pointers to sections of text in the same document -->
<ptr target="#string-range(c1p1s1,0,6)"/>
<ptr target="#string-range(c1p1s6,19,7)"/>
</annotation> | ||||||||||||||||||||||||||
| Example | <annotation xml:id="TheCorrectTitle"
motivation="commenting" target="#line1">
<note>The correct title of this specification, and the correct full name of XML, is
"Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.
However, the abbreviation "XML" is not only correct but, appearing as it does in the title
of the specification, an official name of the Extensible Markup Language. </note>
</annotation> | ||||||||||||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="respStmt" minOccurs="0"
maxOccurs="unbounded"/>
<elementRef key="revisionDesc"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="licence" minOccurs="0"
maxOccurs="unbounded"/>
<classRef key="model.annotationPart.body"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ | ||||||||||||||||||||||||||
| Schema Declaration |
element annotation
{
tei_att.global.attribute.n,
tei_att.global.attribute.xmllang,
tei_att.global.attribute.xmlbase,
tei_att.global.attribute.xmlspace,
tei_att.global.rendition.attribute.rend,
tei_att.global.rendition.attribute.style,
tei_att.global.rendition.attribute.rendition,
tei_att.global.linking.attribute.corresp,
tei_att.global.linking.attribute.synch,
tei_att.global.linking.attribute.sameAs,
tei_att.global.linking.attribute.copyOf,
tei_att.global.linking.attribute.next,
tei_att.global.linking.attribute.prev,
tei_att.global.linking.attribute.exclude,
tei_att.global.linking.attribute.select,
tei_att.global.analytic.attribute.ana,
tei_att.global.facs.attribute.facs,
tei_att.global.change.attribute.change,
tei_att.global.responsibility.attribute.cert,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.pointing.attribute.targetLang,
tei_att.pointing.attribute.evaluate,
attribute xml:id { text },
attribute target { list { + } },
attribute motivation
{
list
{
(
"assessing"
| "bookmarking"
| "classifying"
| "commenting"
| "describing"
| "editing"
| "highlighting"
| "identifying"
| "linking"
| "moderating"
| "questioning"
| "replying"
| "tagging"
)+
}
}?,
(
tei_respStmt*,
tei_revisionDesc*,
tei_licence*,
tei_model.annotationPart.body*
)
}⚓ | ||||||||||||||||||||||||||
| <annotationBlock> groups together various annotations, e.g. for parallel interpretations of a spoken segment. [8.4.6. Analytic Coding] | |
| Module | spoken |
| Attributes | Attributes att.ascribed (@who) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Member of | |
| Contained by | header: change handNote licence scriptNote linking: listAnnotation standOff msdescription: accMat acquisition additions collation condition custEvent decoNote filiation foliation layout musicNotation origin provenance signatures source summary support surrogates typeNote transcr: metamark |
| May contain | Empty element |
| Example | <annotationBlock who="#SPK1" start="#T2"
end="#T3" xml:id="ag20">
<u xml:id="u20">
<seg xml:id="seg37" type="utterance"
subtype="modeless">
<w xml:id="w46">Yeah</w>
</seg>
</u>
</annotationBlock>
<annotationBlock who="#SPK1" start="#T5"
end="#T6" xml:id="ag21">
<u xml:id="u21">
<seg xml:id="seg38" type="utterance"
subtype="modeless">
<w xml:id="w47">Mhm</w>
</seg>
</u>
</annotationBlock> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="u"/>
<elementRef key="spanGrp"/>
<classRef key="model.global.spoken"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element annotationBlock
{
tei_att.ascribed.attributes,
tei_att.timed.attributes,
tei_att.global.attributes,
( u | spanGrp | tei_model.global.spoken )*
}⚓ |
| <app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [«#TCAPEN»] | |||||||||||||||||||||||||||||||||||||||||
| Module | textcrit | ||||||||||||||||||||||||||||||||||||||||
| Attributes | Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source) att.typed (type, @subtype)
| ||||||||||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit citedRange corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi imprint item l label lg list measure mentioned name note num orig p pubPlace publisher q quote rb ref reg resp rs rt said series sic soCalled sp speaker stage street term textLang time title unit header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor msdescription: accMat acquisition additions catchwords collation collection colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit institution layout material msItem musicNotation objectType origDate origPlace origin provenance repository rubric secFol signatures source stamp summary support surrogates typeNote watermark namesdates: addName birth bloc country death district floruit forename genName geogFeat geogName objectName offset orgName persName persPronouns person personGrp persona placeName region roleName settlement surname | ||||||||||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||||||||||
| Example | <app>
<lem wit="#El #Hg">Experience</lem>
<rdg wit="#La" type="substantive">Experiment</rdg>
<rdg wit="#Ra2" type="substantive">Eryment</rdg>
</app> | ||||||||||||||||||||||||||||||||||||||||
| Example | <app type="substantive">
<rdgGrp type="subvariants">
<lem wit="#El #Hg">Experience</lem>
<rdg wit="#Ha4">Experiens</rdg>
</rdgGrp>
<rdgGrp type="subvariants">
<lem wit="#Cp #Ld1">Experiment</lem>
<rdg wit="#La">Ex<g ref="#per"/>iment</rdg>
</rdgGrp>
<rdgGrp type="subvariants">
<lem resp="#ed2013">Eriment</lem>
<rdg wit="#Ra2">Eryment</rdg>
</rdgGrp>
</app> | ||||||||||||||||||||||||||||||||||||||||
| Example | <app loc="1">
<rdg resp="#SEG">TIMΩΔA</rdg>
</app> | ||||||||||||||||||||||||||||||||||||||||
| Example | <app loc="1-6">
<note>Too badly worn to yield a text</note>
</app> | ||||||||||||||||||||||||||||||||||||||||
| Example | <choice xml:id="choice3">
<reg>σύμπαντα</reg>
<orig>ΣΙΝΠΑΤΑΝ</orig>
</choice>
<!-- ... -->
<app from="#choice3">
<note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note>
</app> | ||||||||||||||||||||||||||||||||||||||||
| Content model |
<content>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="lem" minOccurs="0"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.rdgLike"/>
<classRef key="model.noteLike"/>
<elementRef key="witDetail"/>
<elementRef key="wit"/>
<elementRef key="rdgGrp"/>
</alternate>
</sequence>
</content>
⚓ | ||||||||||||||||||||||||||||||||||||||||
| Schema Declaration |
element app
{
tei_att.global.attribute.xmlid,
tei_att.global.attribute.n,
tei_att.global.attribute.xmllang,
tei_att.global.attribute.xmlbase,
tei_att.global.attribute.xmlspace,
tei_att.global.rendition.attribute.rend,
tei_att.global.rendition.attribute.style,
tei_att.global.rendition.attribute.rendition,
tei_att.global.linking.attribute.corresp,
tei_att.global.linking.attribute.synch,
tei_att.global.linking.attribute.sameAs,
tei_att.global.linking.attribute.copyOf,
tei_att.global.linking.attribute.next,
tei_att.global.linking.attribute.prev,
tei_att.global.linking.attribute.exclude,
tei_att.global.linking.attribute.select,
tei_att.global.facs.attribute.facs,
tei_att.global.change.attribute.change,
tei_att.global.responsibility.attribute.cert,
tei_att.global.responsibility.attribute.resp,
tei_att.global.source.attribute.source,
tei_att.typed.attribute.subtype,
attribute ana
{
list
{
(
"#lexical"
| "#syntactic"
| "#morphological"
| "#ordinal"
| "#orthographical"
| "#subtractive"
| "#additive"
)+
}
}?,
attribute type { text }?,
attribute from { text }?,
attribute to { text }?,
attribute loc { list { + } }?,
(
tei_lem?,
(
tei_model.rdgLike
| tei_model.noteLike
| tei_witDetail
| tei_wit
| tei_rdgGrp
)*
)
}⚓ | ||||||||||||||||||||||||||||||||||||||||
| <application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element] | |||||||||||||
| Module | header | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
| ||||||||||||
| Contained by | — | ||||||||||||
| May contain | |||||||||||||
| 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> 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
{
tei_att.global.attributes,
tei_att.typed.attributes,
tei_att.datable.attributes,
attribute ident { text },
attribute version { text },
( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
}⚓ | ||||||||||||
| <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 | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address binaryObject cb choice cit corr date del distinct ellipsis email emph expan foreign gap gb gloss graphic hi index lb measure measureGrp media mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs ruby said sic soCalled term time title unclear unit figures: figure notatedMusic gaiji: g header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code textstructure: floatingText transcr: addSpan am damage delSpan ex fw handShift listTranspose metamark mod redo retrace secl space subst substJoin supplied surplus undo 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> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element author
{
tei_att.global.attributes,
tei_att.naming.attributes,
tei_att.datable.attributes,
tei_macro.phraseSeq
}⚓ |
| <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | core: monogr header: publicationStmt |
| May contain | core: abbr address cb choice date distinct ellipsis email emph expan foreign gap gb gloss hi index lb measure measureGrp mentioned milestone name note noteGrp num pb ptr q ref rs soCalled term time title unit figures: figure notatedMusic header: idno msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName bloc country district forename genName geo geogFeat geogName location objectName offset orgName persName persPronouns placeName region roleName settlement state surname tagdocs: code character data |
| Example | <authority>John Smith</authority> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element authority
{
tei_att.global.attributes,
tei_att.canonical.attributes,
tei_macro.phraseSeq.limited
}⚓ |
| <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 | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| 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> | ||||||||
| 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> | ||||||||
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.availabilityPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element availability
{
tei_att.global.attributes,
tei_att.declarable.attributes,
attribute status { "free" | "unknown" | "restricted" }?,
( tei_model.availabilityPart | tei_model.pLike )+
}⚓ | ||||||||
| <back> (back matter) contains any appendixes, etc. following the main part of a text. [«#DSBACK» «#DS»] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) |
| Contained by | textstructure: floatingText text transcr: facsimile |
| May contain | figures: figure notatedMusic table namesdates: listEvent listNym listObject listOrg listPerson listPlace listRelation |
| 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, &c. 2s.
6d</item>
<item n="2">Dr. Hooper's Female Pills, 1s.</item>
<!-- ... -->
</list>
</div>
</back> |
| Content model |
<content>
<sequence>
<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">
<sequence>
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.frontPart"/>
<classRef key="model.div1Like"/>
<classRef key="model.global"/>
</alternate>
</sequence>
<sequence>
<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">
<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
{
tei_att.global.attributes,
tei_att.declaring.attributes,
(
(
tei_model.frontPart
| tei_model.pLike.front
| tei_model.pLike
| tei_model.listLike
| tei_model.global
)*,
(
(
tei_model.div1Like,
( tei_model.frontPart | tei_model.div1Like | tei_model.global )*
)
| (
tei_model.divLike,
( tei_model.frontPart | tei_model.divLike | tei_model.global )*
)
)?,
(
tei_model.divBottomPart,
( tei_model.divBottomPart | tei_model.global )*
)?
)
}⚓ |