<%@include file="../includes/eadaheader"%>

EADA Project Documentation Description

Element Description

The following is a description of each element. Explanations for general project procedures can be found in the General Overview.

<address> <addrLine> <argument> <author> <body><byline><closer><date> <div#> <distinct><emph><encodingDesc> <epigraph><extent> <figure> <figDesc><fileDesc> <foreign> <front><head> <hi> <item><l> </lb> <lg><list><note><opener> <p> <profileDesc><publicationStmt><q><rs> <salute> <sic> <signed> <sourceDesc> <sp> <speaker> <stage> <teiHeader> <text> <title> <titleStmt> <trailer>

I. Header <teiHeader>

This element contains header information. A Web header example can be used as an example to fill out the XML header template (to dowload, right click and save as "EADAHeader.xml". To use the template, fill in the appropriate editorial information in fields indicated by question marks (??). Phrases that appear in all-caps should be deleted and replaced by editorial data.

<resp>Encoded by <name>YOUR NAME HERE??</name></resp>" might be encoded as "<resp>Encoded by <name>Tanya Clement</name></resp>".

Instructions on using the the following elements appear in alphabetical order. Elements that may appear within the header but also appear in the main body of the text are explained in Section II below.

Images that appear within the body of the text are also declared at the beginning of the header.

  <!ENTITY image1 SYSTEM "http://www.dev.umd.edu/projects/eada/images/picl.jpg" NDATA JPG>
  <!ENTITY image2 SYSTEM "http://www.dev.umd.edu/projects/eada/images/pic2.jpg" NDATA JPG>

back to the top

  • File Description <fileDesc>
    This element contains publishing information pertinent to the electronic version of the text. The elements <titleStmt>, <extent>, <publicationStmt>, and <sourceDesc> are explained below.

  • Title Statement <titleStmt>
    This element contains publishing information pertinent to the electronic version of the text. The <title> element contains the title of the electronic text divided (when necessary) in three parts:
       type="main"-- the main title
       type="sub"-- the subtitle
       type="version"-- in this case, <title type="version">An Electronic Edition</title>

    <fileDesc>
    <titleStmt>
    <title type="main">A Divine and Supernatural Light</title><title type="sub">Immediately Imparted to the Soul by the Spirit of God, Shown to be Both Scriptural and Rational Doctrine</title><title type="version"> An Electronic Edition</title>

    This element also contains both author's name in the <name> tag and the author's dates of birth and death in the <date> tag. The value of the <name> tag is the name of the author of the text as it appears on the source. The 'reg' attribute contains the regularized name of the author. Both the regularized name and the date range may be found in the Library of Congress authority file at http://authorities.loc.gov/.

    Editors and translators are encoded in the <editor> tags. The attribute 'type' is used to indicate "editor" or "translator".

    <author><name reg="Edwards, Jonathan">Jonathan Edwards</name><date>1703-1758</date></author>
    <editor role="editor">Hershel Parker</editor>

    Finally, this element contains information pertaining to those persons responsible for the creation of the electronic edition within the <respStmt> element. Each instance of the <resp> element contains the name of each person responsible for the creation of the electronic text including the editor and the encoder.

    <respStmt>
    <resp>Header creation by <name>Ralph Bauer</name></resp>
    <resp>Encoded by <name>Tanya Clement</name></resp>
    </respStmt>
    </titleStmt>

  • back to the top

  • Extent <extent>
    This element contains the size of the electronic text in kilobytes. This number is filled in by the encoder as a last step.

    <extent>125 KB</extent>

  • Publication Statement <publicationStmt>
    This element contains information pertinent to the publication of the electronic edition including the <publisher> and the <pubPlace>. The encoder must fill in the <date> value in the format "Month day, year." The 'value' attribute for the <date> tag is in numeric form: value="yyyy-mm-dd".

    <publicationStmt>
    <idno>edwards_divine.xml</idno>

    <publisher>Maryland Institute for Technology in the Humanities (MITH)</publisher>
    <pubPlace> <address>
    <addrLine>University of Maryland</addrLine>
    <addrLine>College Park</addrLine>
    </address></pubPlace>
    <date value="2003-10-01">October 1, 2003</date>

    This element also contains the <availability> information which outlines use practices and Copyright information. For this project, this tag presumes that the text is out of copyright.

    <availability> <p>Copyright 2003. This text is freely available provided the text is distributed with the header information provided.</p> </availability>
    </publicationStmt>

  • back to the top

  • Source Description <sourceDesc>
    This element contains the bibliographic details of the source edition within the <bibl> tags. The bibliographic details appear in MLA style in plain text.

    <sourceDesc> <bibl>Jonathan Edwards: American Writers Series. Eds. Clarence H. Faust and Thomas H. Johnson. New York: American Book Co.,1935. </bibl>
    </sourceDesc>
    </fileDesc>

  • Encoding Description <encodingDesc>
    This element contains the editor's declaration about encoding practices used in this electronic edition. The text is contained within the <editorialDecl> element and may be changed by any editor as needed.

    <encodingDesc>
      <editorialDecl>
    <p>This text was first published in <date>1730-1740</date> in Boston</p>
    <p>The text of the document was initially prepared from and proofed against Jonathan Edwards: American Writers Series. Eds. Clarence H. Faust and Thomas H. Johnson. New York: American Book Co.,1935. All preliminaries have been omitted except those for which the author is responsible and those in which editorial notes indicate significant textual variations. Line and paragraph numbers contained in the source text have been retained. In cases where the source text displays no numbers, numbers are automatically generated. In the header, personal names have been regularized according to the Library of Congress authority files as "Last Name, First Name" for the REG attribute and "First Name Last Name" for the element value. Names have not been regularized in the body of the text.</p>
    </editorialDecl>
    </encodingDesc>

  • back to the top

  • Profile Description <profileDesc>
    This element contains information pertinent to the classification of the text including the languages used, categories, and keywords.

    Foreign languages that appear in the text are encoded in the <langUsage> and <language> elements. The value of the 'id' attribute in the <language> element must contain the appropriate ISO639 language code. (ISO639 is available online at http://www.loc.gov/standards/iso639-2/englangn.html). For this project, North American Indian languages that cannot be specifically located on the list provided are encoded with the recommended "nai".

    <profileDesc>
    <langUsage>
    <language id="nai">North American Indian</language>
    <language id="eng">English</language>
    </langUsage>

    Values for classification categories (within <textClass> and <classCode> elements) and keyword categories (within <keyword>, <list>, and <item> elements) are always copied and pasted to avoid spelling and capitalization errors. Complete documentation for these metaterms appears in the document Metaterms.

    <textClass>
    <classCode>Prose</classCode>
    <keywords> <list>
    <item type="mode">Fiction</item>
    <item type="form">Account/Relation</item>
    <item type="chronological">1850-1900</item>
    <item type="geographic">New England</item>
    <item type="subject">Native Americans</item>
    <item type="subject">Puritans</item>
    <item type="subject">Travel</item>
    </list></keywords>
    </textClass>
    </profileDesc>

back to the top

III. Front <front>

This element contains text written by the author that appears before the main body of the text such as dedications and prefaces, etc. Title pages and tables of contents are not included. When appropriate, the <div#> tags are used with a type attribute. Appropriate type attributes used in <front> include:

  1. type="preface"
  2. type="dedication"--a note or letter written to a specific reader
  3. type="letter_to_reader"--a note or letter written to the non-specific reader
  4. type="abstract"
  5. type="foreword"
  6. type="acknowledgment"
  7. type="introduction"
  8. type="list_of_abbreviations"
  9. type="chronology"
  10. type="preface"

<front>
<div1 type="dedication"><opener><salute>To the Right Honorable Caecilius Lord Baltemore Absolute Lord and Proprietary of the Provinces . . .
</front>

back to the top

III. Body <body>

This element contains the main body of the text for each work. The elements explained below will usually appear within the body, but may, on occasion, appear within the <teiHeader> or <front> tags. The following tags appear in alphabetical order. The 'rend' attribute, among general encoding procedures, is explained in the EADA Overview.

Please note: examples for those elements that are contained within parent elements appear within the description of the parent element.

back to the top

  • Address <address>
    This element resides within the <opener> tag and contains information pertaining to the address of a letter including the date and place a letter was written. Each line is captured in the <addrLine> element.

    <p><address><addrLine>Boston, Massachusetts</addrLine>
    <addrLine><date>October 2, 1772</date></addrLine></address></p>

  • Address Line <addrLine>
    This element contains the distinct lines of address information including the date <addrLine> and location indicated on a letter.

  • Argument <argument>
    This element contains any argument that appears at the beginning of a text, section, or poem. The argument usually contains an abstract of the subsequent text and appears outside of the <head>.

    <div1><head>Doctrine</head><argument><p n="10">That there is such a thing as a spiritual and divine light immediately imparted to the soul by God, of a different nature from any that is obtained by natural means. </p></argument> . . .

  • back to the top

  • Byline <byline>
    This element contains the responsibility statement of the author, editor or translator as it appears at the beginning or end of the work. This element may also appear anywhere within the body of the text if it is associated with the beginning or end of a particular <div#> or <lg>.

    <byline>translated by Samuel Beckett</byline>

  • Closer <closer>
    This element groups together the dateline, byline, salutation, and similar phrases appearing as a final group at the end of a division, especially of a letter. Since the TEI dtd does not accomodate postscripts, postscripts are to be moved to a paragraph before the <closer> in a <p> tag with type="postscript". The postscript will appear in the correct place in the final rendition of the document, but for tagging purposes, must be tagged as described above.

    This element is not used in letters that appear as blockquotes in paragraphs.

    <p n="72" type="postscript">And not to forget Tom Forge I beseech you, tell him that my Love's the same towards him still, and as firm as it was about the overgrown Tryal, when Judgements upon judgements, had not I stept in, would have pursued him untill the day of Judgement, &c. </p>

    <closer><salute>Yours to command,</salute><signed>G. A.</signed></closer>

  • back to the top

  • Date <date>
    This element contains dates that appear at the top of sections or documents. This tag is also used at the beginning or ending of letters, usually within <address> tags.

  • Distinct <distinct>
    This element is used to signify a distinct term that needs marking. The 'type' attribute describes how that term is unique and is picked from one of the following values:
       type="vernacular"
       type="colloquial"

    <rs reg="tobacco">
    <distinct type="vernacular">Sot-Weed</distinct></rs>

  • Divisions <div#>
    Explanation and examples for this element can be found in the EADA Overview

  • back to the top

  • Emphasis <emph>
    This element contains text that appears in a textual font (italics, bold, underlined, etc.) different than the main text. If it is not obvious that the author intends emphasis, the <hi> tags should be used instead. Font changes are noted in the 'rend' attribute.

    <p n="3">Upon this occasion, Christ says as he does <emph rend="italic">to</emph> him, and <emph rend="italic">of</emph> him in the text: in which we may observe,</p>

  • Epigraph <epigraph>
    This element contains quotes or lines that appear at the beginning of a text, section, or poem. The epigraph appears outside of the <head>. The 'rend' attribute should be used with this tag if the entire epigraph is one font.

    <body><div0><head type="main">A DIVINE AND SUPERNATURAL LIGHT</head><epigraph><head type="sub">Immediately Imparted to the Soul by the Spirit of God, Shown to be Both Scriptural and Rational Doctrine</head><epigraph><p n="1"><p>Matthew 16:17 —And Jesus answered and said unto him, Blessed art thou, Simon Barjona: for flesh and blood hath not revealed it unto thee, but my Father which is in heaven.</p></epigraph><div1> . . .

  • back to the top

  • Figure <figure>
    This element contains references to graphics that appear on the source. Any text is contained in a <figDesc> tag. The value of the 'entity' attribute is also declared in the header which then links to the outside image.

    <figure entity="image1"><figDesc>Dr. Cook.</figDesc></figure>

  • Figure Description <figureDesc>
    This element is used inside the <figure> element to encode any text associated with a figure including captions.

  • Foreign <foreign>
    This element contains any string of text that is different from the main language of the text. If the word or phrase is distinguished from the rest of the text by virtue of its function (i.e., a title, head, epigraph, etc.) it is identified with the 'lang' attribute of that element. As with the <foreign> element, 'lang' contains the proper iso639-2 language code.(iso639-2 is available online at http://www.loc.gov/standards/iso639-2/englangn.html).

    Please Note: Any language that is tagged as such in the text is also noted in the <language> tag within <profileDesc> in the header.

    <foreign lang="nai">Inwewinan</foreign>.

    This element also uses the 'rend' attribute when appropriate.

    <p>Pensé yo que huía de mí misma, pero ¡miserable de mí! trájeme a mí conmigo y traje mi mayor enemigo en esta inclinación, y se verificaba en mí el <foreign lang="lat" rend="italic">privatio est causa appetitus</foreign>. </p>

  • back to the top

  • Head <head>
    This element contains heading content for a <div#>. No tags may appear before a <head> tag within the respective <div#>. If text appears before the <head> on the source, that information is tagged after the <head> in the digital text.

    It is not usually necessary to use the 'rend' attribute with this element.

    The 'type' attribute is used to designate if the head is "main" or "sub".

    <body><div0><head type="main">A DIVINE AND SUPERNATURAL LIGHT</head><head type="sub">Immediately Imparted to the Soul by the Spirit of God, Shown to be Both Scriptural and Rational Doctrine</head><div1> . . . .

  • Highlighted <hi>
    This element contains text that is bold, italicized, etc. for reasons that are not easily identifiable. This tag should only be used when all other tags are inappropriate (e.g., <title>, <foreign>, <head>, etc.) . The 'rend' attribute is used to identify format.

    Text that is obviously highlighted for emphasis is captured in the <emph> tag.

    <p n="13">There is an old Saying in <hi rend="italic">England</hi>, <hi rend="italic">He must rise betimes that would please every one.</hi> </p>

  • back to the top

  • Item <item>
    This element contains each line of a <list>. Titles appear in the <head> tags. Regardless of the source, all lines are numbered with the appropriate sequential number appearing as the value of the 'n' attribute. If the source is numbered, the number represents the numbering in the source regardless of error.

  • Line <l>
    This element contains each separate line of poetry. Titles appear in <head> tags. Lines are numbered sequentially within each line group <lg>. If the source is numbered, the number represents the numbering in the source regardless of error.

  • Line Break </lb>
    This empty element is used to mark where line breaks occur in the text. This element is only used in those situations in which the line break is not already delineated by another structure tag. For example, since each line of poetry appears in a distinct <l> tag, it is not necessary to mark the line breaks. The same principle holds true for many structures such as the <head>, <closer>, <item>, etc.

    In the following example, there is no appropriate tag to differentiate "My Lord" "Your Lordship most" and "Humble Servant", yet these three strings appear on separate lines. Here the </lb> tag can retain the structure of the original text.

    <closer><salute>My Lord <lb/>Your Lordship most <lb/>Humble Servant,</salute><signed>George Alsop</signed></closer>

  • Line Group <lg>
    This element contains complete stanzas of poetry. Each line is separated into line <l> tags. Each <lg> is numbered sequentially if numbering does not already appear in the source.

    Titles that pertain to multiple stanzas or <lg>s appear in <head> tags oustide the <lg>. Headings that pertain to each individual stanza or <lg> appear within that <lg>.

    <div0>
    <head><title>By night when others soundly slept</title></head>
    <lg n="1">
    <l n="1">By night when others soundly slept</l>
    <l n="2">And hath at once both ease and Rest,</l>
    <l n="3">My waking eyes were open kept</l>
    <l n="4">And so to lie I found it best.</l>
    <l n="5">I sought him whom my Soul did Love,</l>
    . . . </lg>
    <lg n="2"> . . .

  • List <list>
    This element contains lists. Each line is separated into line <l> tags. Titles appear in <head> tags.

    <list>
    <head>An account of the distances of places. From Westover to Col. Mumford's, 16 miles. </head>
    <item n="1">From Col. Mumford's to major Mumford's, 6 </item>
    <item n="2">From thence to Sapponi chapel, 20 </item>
    <item n="3">From thence to major Embry's on Nottoway, 10 </item>
    <item n="4">From thence to Brunswick court-house, 15 </item>
    <item n="5">From thence to Meherrin river, 8 </item>
    </list>

  • back to the top

  • Note <note>
    This element contains notes written by the author and the electronic editor. Notes written by the editor of the original source only appear in the digital text if the note refers to textual differences between editions. Notes appear where they are referenced in the text (that is where the asterisk or number appears).

    A <note> is assumed to be the product of the author. If for some rare reason and editorial note is retained in the text, the 'resp' attribute is used: resp="editor".

    . . . ornament due to their Heroes. <note resp="editor"> Smith thus describes them: <q>"Sixty of those Sasquesahanocks came to vs with skins, Bowes, . . .

  • Opener <opener>
    This element contains the opening to a letter which may include the <salute> and <address>.

    This element is not used in letters that appear in blockquotes within paragraphs.

    <opener>
    <address><addrLine><date>November 1, 1737</date></addrLine></address>
    <salute>To my Friend Mr. George Alsop, on his Character of Maryland,</salute>
    </opener>

  • back to the top

  • Paragraph <p>
    This element contains the body of a paragraph. The <p> tag always contains a sequentially-numbered 'n' attribute. If the source is numbered, this value is always according to the source, regardless of source errors.

    <p n="1">This is the first paragraph . . . </p>

    <p n="2">This is the second paragraph . . . </p>

    The 'type' attribute is used to identify a postscript in a letter. If a postscript appears, that postscript is encoded before the <closer>. See <closer> for an example.

  • Quote-Block <q>
    This element contains the body of a blockquote that is separated from the main body of a text. This element is also used for letters if they appear within a paragraph structure. The 'rend' attribute should be used to indicate font.

    <p> . . . Smith thus describes them: <q>"Sixty of those Sasquesahanocks came to vs with skins, Bowes, Arrows, Targets, Beads, swords and Tobacco pipes for presents. . . </q></p>

  • back to the top

  • Referent String <rs>
    This element contains referent strings that could be part of a keyword search but require regularization. The 'type' attribute is not used in this element. Type is indicated in the <distinct> element. The 'reg' attribute contains the associated keyword.

    For example, <rs reg="tobacco">Sot-Weed</rs> where the term "Sot-Weed" is contained in the Keyword Authority File as an alternate term for "tobacco."

  • Salute <salute>
    This element appears within the <opener> and <closer> elements and contains closing and opening salutations in a letter such as "Dear" and "your humble servant".

  • Speech <sp>
    This element contains all parts (speaker <speaker> and stage directions <stage>) that pertain to a certain speech act (usually the portion of dialog that can be attributed to one character) in a dramatic text.

    <sp>
    <speaker>VAN ROUGH.</speaker>
    <p n="492"> Why, all this is nothing to the purpose; can you explain it, Miss?
    <stage>To Charlotte.</stage>
    </p>
    <stage>Enter: LETITIA through the back scene.</stage>
    </sp>

  • Speaker <speaker>
    This elment is used inside the speech <sp> tag to indicate the character who is speaking.
  • Stage Directions <stage>
    This element contains stage directions within a dramatic text. Stage directions can appear within the <sp> element if it pertains to the speech act or outside the <sp> element if it pertains to the action of more than one speech act.

    <sp>
    <speaker>CHARLOTTE.</speaker>
    <p n="86">Hush! I hear some person coming through the entry.</p>
    </sp>
    <stage>Enter: SERVANT.</stage>

  • Spelling <sic>
    This element contains words that are not spelled correctly in the prepared edition. The 'corr' attribute contains the editor's best guess at the correct spelling.

    <l n="25">Tho: children thou hast given me,</l>
    <l n="26">And <sic corr="friends">freinds</sic> I have also:</l>

  • Signed <signed>
    This element appears within the <closer> element and contains names that appear at the end of a letter after the closing salutation.

  • Title <title>
    This element contains titles. Titles that appear throughout the document are tagged with this element. The format of titles should appear in the 'rend' attribute with the appropriate values mentioned in the EADA Overview.

    <title rend="italic">To My Dear Children</title>

  • Trailer <trailer>
    This element contains a footer appearing at the very end of a text like "The End" or "Finis". The 'rend' attribute should be used for this tag.

    <trailer>FINIS</trailer>

back to the top

Any questions about this description should be sent to Tanya Clement, MITH Program Associate, at tclement@wam.umd.edu.