This edition is still being developed and proofed. Please do
not cite this preview until this notice is removed.
The editors welcome suggestions and corrections (see link above).
The following guidelines constitute a formalized markup scheme for this edition of the Samuel Sullivan Cox Journal. At present, it is a working document and will change over the next several months as we continue work on the editon and discover more about the text.
Markup of Physical Structure and Page Layout. The manuscript pages, encoded by the empty page break or <pb/> element, are the primary physical structures represented in the markup. Each <pb> element includes an "mmid" attribute identifying the unique ID of a high-resolution scan of that image in the Media Manager application, as well as "audiostart" and "audioend" attributes that identify the section of the audio edition that corresponds to that page. Line breaks (i.e., lineation determined or influenced by the physical constraints of the page rather than compositional choices by the author) are encoded with the empty <lb/> element. No attributes are included in the <lb> element.
Markup of Textual Structure. The journal entry constitutes the primary textual structure represented in the markup. It is encoded by a <div1> element with the attribute-value pair "type='Entry,'" an "id" attribute with the unique value "CoxYYYYMMDDa" (where the date corresponds to the date of the entry and the trailing letter allows for multiple entries on a given day), and "audiostart" and "audioend" attributes that identify the section of the audio edition that corresponds to that entry. Each entry contains an <opener> element—which in turn contains a <dateline> element—and one or more paragraphs. Each dateline may include a <name> element with (optionally) a "type" attribute containing one of the following values: city, region; and a <date> element with a "value" attribute whose value is in the form YYYY-MM-DD.
Entries consist of a series of paragraphs. Where indicated by indentation of a line from the left margin of a page, line breaks part-way across a page, or additional white space between lines, paragraphs are encoded with the <p> element and no attributes.
If present, any prefatory text preceding the dateline may be encoded as a <head> element at the beginning of the entry (i.e., within the <div>element and before the <opener>).
Level of Transcription/Encoding. This markup scheme supports a modest range of presentations, from semi-modernized/corrected to semi-diplomatic. The basic transcription follows the manuscript verbatim. Various manuscript features (e.g., cancellations, interlinear or marginal additions, tears in pages) are encoded, as are regularized versions of proper names and dates and standard versions of nonstandard spellings and expansions of abbreviations. See below for details.
Other Editorial Apparatus. Links to scans of manuscript pages and other rich media, textual variants, explanatory annotations, and bibliographic information about works cited in annotations are all encoded in the XML file. See below for details.
| Feature Group | Feature |
|---|---|
| Abbreviation | Abbreviation |
| Annotation | Explanatory Annotations |
| Bibliography | Works Cited Entry |
| Corrections and Emendations | Cancelation-Unrecoverable |
| Corrections and Emendations | Cancellation-Recoverable |
| Corrections and Emendations | Uncertain Reading |
| Corrections and Emendations | Additions-interlinear |
| Corrections and Emendations | Additions-marginal |
| Highlighting | Underlining |
| Corrections and Emendations | Apparent Errors |
| Corrections and Emendations | Supplied text |
| Discourse | Quotation (speech or thought) |
| Handwriting | Shift in hand or medium |
| Language | Foreign Terms |
| Names | Name |
| Names | Referring String |
| Page Layout | Page Break |
| Page Layout | Line Break |
| Paper | Gap in transcription |
| Punctuation | Word broken across two lines (with or without a mark such as a hyphen) |
| Punctuation | Em Dash |
| Punctuation | Hyphen |
| Rich Media | Images |
| Structure | Dateline (and date) |
| Structure | Paragraph |
| Titles | Title |
| Continuation Notice | Continuation Notice |
Common Name: Abbreviation
Contextual Notes: Abbreviations and acronyms occur throughout the text. For purposes of markup, we treat the entire abbreviation (e.g., “Ret.”) as the abbreviation, not just the mark, if any, indicating missing letters; and the entire word as the expansion (e.g., “Retired”), not just the missing letters.
Element Name: <abbr>
Encoding Rule: We favor a diplomatic perspective, tagging abbreviations with <abbr> and providing an expanded version of all abbreviations or acronyms as “expan” attributes. We transcribe without comment common contractions such as “don’t” or “won’t.”
Sample Source Text: Capt Judkins Ret.
Sample Encoding:
<name type="person" reg="Judkins, Charles Henry Evans"> <abbr expan="Captain">Capt</abbr> Judkins<abbr expan=”Retired”> Ret.</abbr> </name>
Sample Image from the MSS: Sample manuscript image
Common Name: Explanatory Annotations
Contextual Notes: We annotate the text in order to identify a person, place, or event; to draw attention to a physical feature of the manuscript; to provide links to supplemental material; or to explain an editorial judgment.
Element Name: <note>
Encoding Rule: We place a note reference
and the text of an annotation in the text at the point where
the note reference should appear. The note reference is encoded
with a <note> tag and two attributes: a "resp" attribute
with the value
"ed" and a "target" attribute with a unique ID value
(must begin with a letter). The note text immediately follows the
note reference element and is enclosed with another <note> tag
in which the "target"
attribute is replaced by an "id" attribute with the
same value as the "target" attribute in the note reference
element. Notes provide standard citation information (e.g., author,
page) that allows readers to find the source of the information in the
list of works cited (see encoding information for bibliography entries
below).
Note: If a <note> element will not validate in
the spot where the note reference should appear, it may be enclosed
in a <seg> element (without any attributes).
Sample Source Text: Six bonna fide icebergs1
Sample Encoding:
<!-- Place in text at point of note reference: --> <lb/> six <sic corr="bona">bonna</sic> fide icebergs—
<note resp="ed" target="C0513berg"/>
<note resp="ed" id="C0513berg">Judging from the mileage recorded in its log, the <name type="ship">RMS Asia</name>
probably encountered icebergs while running over the "Flemish Cap" of the Grand Banks off the Newfoundland coa
In <title level="m">The Physical Geography of the Sea</title> (1855), M. F. Maury
describes the contemporary understanding of the currents that carry icebergs to the coast of Newfoundland:
"cold waters, as they come down from the Arctic Ocean through Davis's Straits, press upon the warm waters
of the Gulf Stream, and curve their channel into a horse-shoe. . . . This 'bend' is the great receptacle of
the icebergs which drift down from the north" (241–42).
<figure rend="link">
<head>The dotted line indicates the 'bend'" in the Gulf Stream\line where cold Arctic waters intrude (Maury, Plate VI)</head>
<figDesc>
<xref url="https://images.asc.ohio-state.edu/is/image/mediamanager?layer=0&size=600,600&layer=1&src=is{mediamanager/6/66f4049b-e765-496d-8788-e81592799f58.jpg?scale=0.5&rgn=650,50,600,400&fmt=png}&posN=0,-.25&layer=2&size=600,400&text=\vertalt\cf1\qc\fs30\%20The%20dotted%20line%20indicates%20the%20"bend"&PosN=.06,-.25">Click to view Maury's isothermic map of the 'bend' in the Gulf Stream.</xref
</figDesc>
</figure>
</note>
Sample Image from the MSS: No sample image available
Common Name: Works Cited Entry
Contextual Notes: Anytime we paraphrase, quote, or otherwise present information gleaned from another source (e.g., in annotations), we provide a citation to that source in a list of works cited.
Element Name: <bibl>
Encoding Rule: A <div1> element
of type “Citations” appears in
the <back> of our <text>. That division
consists of a bibliography list enclosed in a <listBibl> element,
which in turn consists of a series of bibliography entries enclosed in <bibl> elements.
See below for elements that may be contained within the <bibl> element
in order to construct an entry for a book or Web site.
Note: Each <bibl> element contains an "id" attribute
with a unique identifier. Elements within each entry (e.g., <author>)
are entered in the order they should appear in the final entry. No
end punctuation is entered for any sub-element (e.g., in the first
example below, the period following the "F" in M. F. Maury's
name is not entered
in the XML encoding).
Sample Source Texts:
Maury, M. F. The Physical Geography of the Sea. 2nd ed. New York, NY: Harper, 1855.
Patuxent Wildlife Research Center, U.S. Geological Survey. "Wilson's storm-petrel Oceanites oceanicus." Patuxent Bird Identification InfoCenter. Patuxent Wildlife Research Center, [http://www.mbr-pwrc.usgs.gov/id/framlst/i1090id.html]. n.d. Date of visit: 10 Feb. 2007.
Sample Encoding:
<div1 type="Citations">
<listBibl> <head>Works Cited in Notes</head>
<bibl id="MFM>
<author>Maury, M. F</author>
<title level="m">The Physical Geography of the Sea</title>
<edition>2nd</edition>
<pubPlace>New York, NY</pubPlace>
<publisher>Harper</publisher>
<date>1855</date>
</bibl>
<bibl id="PWRC">
<author >Patuxent Wildlife Research Center, U.S. Geological Survey</author>
<title level="a" >Wilson's storm-petrel <name type="binomial">Oceanites oceanicus</name></title>
<title level="m" >Patuxent Bird Identification InfoCenter</title>
<publisher>Patuxent Wildlife Research Center</publisher>
<biblScope type="URL">http://www.mbr-pwrc.usgs.gov/id/framlst/i1090id.html</biblScope>
<date>n.d</date>
<biblScope type="DateOfVisit">10 Feb. 2007</biblScope>
</bibl>
Sample Image from the MSS: No sample image available
Group: Corrections and Emendations
Common Name: Cancelation-Unrecoverable
Contextual Notes: When the author or some later hand has canceled a letter, word, or phrase in such a manner that it cannot be read, we encode an unrecoverable cancelation, distinguishing it from a physical gap in the page.
Element Name: <del>
Encoding Rule: The <del> tag surrounds one of the following: "letter," "word," or "words" and contains three attributes: type=”unrecoverable”, rend=”(overstrike | overwritten | erased)”; hand=”XXX” [i.e., whatever identifier is appropriate].
Sample Source Text: [an erased word]
Sample Encoding:
<del type=”unrecoverable” rend=”erased” hand=”WBA”>word</del>
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Cancellation-Recoverable
Contextual Notes: When the author or some later hand has canceled a letter, word, or phrase in such a manner that we can read the canceled material, we encode a recoverable cancelation.
Element Name: <del>
Encoding Rule: The tag surrounds the recovered words and contains three attributes: type=”recoverable”, rend=”(overstrike | overwritten | erased)”; hand=”XXX” [i.e., whatever identifier is appropriate].
Sample Source Text: passed the
Sample Encoding:
passed <del type="recoverable" hand="SSC" rend="overstrike">the</del>
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Uncertain Reading
Contextual Notes: If, after assessing all the available evidence, we cannot read with certainty a word that is not canceled or otherwise obscured, we tag the text as an uncertain reading.
Element Name: <unclear>
Encoding Rule: Surround the text in question with the <unclear> tag and, optionally, provide attributes indicating degree of certainty (e.g., cert=”50%"); editorial responsibility, indicated by your initials (e.g., resp=”HLU”); and the reason for the lack of clarity (e.g., reason="coined word?").
Sample Source Text: It is an exelegant Hotel
Sample Encoding:
<lb/>It is an <unclear cert="60%" resp="HLU" reason="coined word?">exelegant</unclear>hotel.
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Additions-interlinear
Contextual Notes: Interlinear additions may appear above or below a line of text.
Element Name: <add>
Encoding Rule: Include a “place” attribute indicating whether the addition is above the line (”supralinear”) or below the line (”infralinear”). Indicate the person who apparently made the addition with the “hand” attribute. If the writer includes a caret or other mark to indicate the addition, indicate the mark as the value of a “rend” attribute.
Sample Source Text:
dock crowded our friends were there—
The crowd cheered as we left—
Six times our guns fired as we
Sample Encoding:
<lb/> dock crowded our friends were there—
<add hand="SSC" place="infralinear">The crowd cheered as we left— </add>
<lb/> Six times our guns fired as we
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Additions-marginal
Contextual Notes: Additions may be placed in the top, left, right, or bottom margins.
Element Name: <add>
Encoding Rule: Include a “place” attribute indicating the placement of the addition (top margin | bottom margin | left margin | right margin). Indicate the person who apparently made the addition with the “hand” attribute. If the writer includes a caret or other mark to indicate the addition, indicate the mark as the value of a “rend” attribute.
Sample Source Text: Additions *can sometimes be placed in the margins.
Sample Encoding:
Additions <add place=”right margin” hand=”WBA” rend=”*”>can
sometimes be placed in the margins</add>
Sample Image from the MSS: No example available
Common Name: Underlining
Contextual Notes: The most commonly used highlighting technique in the Cox journal is underscoring.
Element Name: <hi>
Encoding Rule: Surround the highlighted text with the <hi> element and provide a “type” attribute that indicates the type of highlighting (underlining is the most common in our text).
Sample Source Text: Coe et ux
Sample Encoding:
<lb/> Coe <foreign lang="lat">et <hi rend="underline"><abbr expan="uxor">ux</abbr></hi></foreign>
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Apparent Errors
Contextual Notes: If the writer has apparently written something in error (e.g., a misspelling), we report it along with whatever we believe the correct text to be.
Element Name: <sic>
Encoding Rule: Since we favor a diplomatic transcription, we report the error and include a “corr” attribute giving the correct text.
Sample Source Text: All is exhileration—watched the
Sample Encoding:
<lb/> All is <sic corr="exhilaration">exhileration</sic>—watched the
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Supplied text
Contextual Notes: We add text to the document if we are certain that the text was intended or necessary to make sense but inadvertently omitted by the writer.
Element Name: <supplied>
Encoding Rule: Enclose the supplied text within the <supplied> element and provide a “reason” attribute (a common value would be “omitted”) and a responsibility attribute with the value "ed" for "editor." Include a “source” attribute if another source suggests the reading. The <supplied> element may also contain an <unclear> or <del type=”unrecoverable”> element. See TEI 18.2.4.
Sample Source Text: of chaos—soon to whelmed for-
Sample Encoding:
<lb/> of chaos—soon to <supplied reason="omitted" resp="ed">be</supplied> whelmed
Sample Image from the MSS: Sample manuscript image
Common Name: Quotation (speech or thought)
Contextual Notes: This element reports quotations however punctuated. According to TEI, it represents “speech or thought marked as being quoted from someone else.”
Element Name: <q>
Encoding Rule: Enclose the quoted text within the <q> element and include any quotation marks as entities (e.g., ").
Sample Source Text:
. . . "Have anything
today"—Says Kind
John Miller our servent
"No!" is the sharp retort
of the sea sick soul. . . .
Sample Encoding:
<lb/> . . . <q>"Have
<lb/> anything today"</q>—Says Kind
<lb/> <name type="person" reg="Miller, John">John Miller</name> our <sic corr="servant">servent</sic> <lb/> <q>"No!"</q> is the sharp retort
<lb/> of the sea sick soul. . . .
Sample Image from the MSS: Sample manuscript image
Common Name: Shift in hand or medium
Contextual Notes: Changes in handwriting from one writer to another or one medium to another are noted in the encoded transcript.
Element Name: <handShift/>
Encoding Rule: See the sample encoding below for establishing a list of hands in the TEI header. In the text, include the empty <handShift/> element at the point where the handwriting shifts. Include a “new” attribute to indicate the writer by the ID established in the <handList> and an “ink” attribute to indicate the medium (e.g., ink=”pencil | pen”).
Sample Source Text:
Sample Encoding:
In the TEI Header within the <profileDesc>: <handList> <hand id="WBA" scribe=”William B.Anderson” first="yes"/> <hand id="UNK"scribe="Unknown" first="no"/> </handList> In the body of the letter: <handShift ink="pencil" new="UNK"/>
Sample Image from the MSS: Sample manuscript image
Common Name: Foreign Terms
Contextual Notes: If the writer shifts to a foreign language or uses a foreign term, we note the shift.
Element Name: <foreign>
Encoding Rule: In the TEI header, declare a list of languages used in the document (see example below). In the text, enclose any foreign terms or phrases in a <foreign> element and provide a “lang” attribute.
Sample Source Text: Coe[?] et ux (just married yesterday)
Sample Encoding:
<!-- Languages: Declaring languages in your text. In order to indicate shifts from one language to
another in a text, TEI requires that the profile description in the header first declare all the languages used in the text. [See TEI 5.4.2 Language Usage]--> <langUsage>
<language id="eng">English</language>
<language id="fre">French</language> <language id="lat">Latin</language>
<language id="grc">Greek, Ancient (to 1453)</language>
</langUsage>
<!-- Languages: Marking a shift in language. In the text, indicate a shift in language using the global "lang" attribute with the id value of the language from the header. [See TEI 4.3 Code Shifting] --> <lb/> <unclear>Coe </unclear><foreign lang="lat">et <hi rend=underscore><abbr expan="uxor">ux </abbr></hi></foreign> (just married yesterday)
Sample Image from the MSS: Sample manuscript image
Common Name: Name
Contextual Notes: We distinguish between proper names and referring strings (e.g., “Wife,” “the eternal city”).
Element Name: <name>
Encoding Rule: Enclose the name as written with the <name> element, and if appropriate, include a “type” attribute with one of the following values: person, city, ship, building, nationality, landmark, region. In addition, provide a “reg” attribute with a regularized version of the name. If available, the regularized version of people's names should come from the OSCAR catalog and include dates of birth and death. The regularized version of city or region names should include the appropriate state (for U.S. locations) or country: e.g., Columbus, OH. For all names, we will construct an "authority list" for the project so that our regularized values for names are consistent.
Sample Source Text:
. . . Capt
Judkins Ret. . . .
Sample Encoding:
<name type="person" reg="Judkins, Charles Henry Evans (?-1878)"><abbr expan="Captain">Capt</abbr>
<lb/> Judkins <abbr expan="Retired">Ret.</abbr></name>
Sample Image from the MSS: Sample manuscript image
Common Name: Referring String
Contextual Notes: Text that refers to a proper name without using a version of the name is identified with the "referring string" element <rs>
Element Name: <rs>
Encoding Rule: Where appropriate, the <rs> element should have a “type” attribute with the value (person | city | ship | building | nationality | and so on ) as well as a “reg” attribute that supplies a regularized version of the proper name referred to. If two types must be declared, <rs> tags may be nested.
Sample Source Text:
. . .
The Bishop
of Chester . . .
Sample Encoding:
<lb/>Chapel attracted our ego. The <rs type="person" reg="Graham, John (?-?)">Bishop
<lb/>of Chester</rs> . . .
Sample Image from the MSS: Sample manuscript image
Common Name: Page Break
Contextual Notes: Marks pages in the manuscript.
Element Name: <pb/>
Encoding Rule: The page break appears at the beginning of each page of the transcript, including the first. It includes the following attributes: an “mmid” attribute whose value is the Media Manager Item ID for the scan of that page, and "audiostart" and "audioend" attributes that identify the section of the audio edition corresponding to that page
Sample Source Text: [a page break]
Sample Encoding:
<pb mmid="/a/a49d8621-1ce7-44c1-b4c1-7c0ba72b79f1" audiostart="00:13:48:10" audioend="00:15:11:03"/>
Sample Image from the MSS: Sample manuscript image
Common Name: Line Break
Contextual Notes: Lines may be difficult to determine. For instance, if Cox adds a word or phrase between two lines of a letter, the added text would not constitute a line. If in doubt, consult with the principal editor.
Element Name: <lb/>
Encoding Rule: Encode the beginning of each line of the text with a <lb> tag. The tag should be followed by a space unless the two lines are run together (as in the case of a soft hyphen).
Sample Source Text: waves. All our baggage being a-
board
Sample Encoding:
<lb/> waves. All our baggage being a<seg type=”softhyphen”>- <lb/></seg>board
Sample Image from the MSS: Sample manuscript image
Common Name: Gap in transcription
Contextual Notes: Used when physical damage renders the text unreadable (e.g., a stain or torn page.
Element Name: <gap>
Encoding Rule: The <gap> element optionally includes “reason,” “extent,” and "agent" attributes. For an inkblot covering a word or words, describe the extent as the number of words obscured. For a tear, provide approximate dimensions in centimeters.
Sample Source Text: But to [torn page]
Sample Encoding:
But to<gap agent="wax seal apparently tore page when letter opened" extent="2 cm" reason="torn page"/>
Sample Image from the MSS: Sample manuscript image (from Sophia Hawthorne letters)
Common Name: Soft-hyphen
Contextual Notes: Nineteenth-century manuscripts often break words across lines with a hyphen at the end of the first line, a colon or equal sign at the beginning of the second line, or with some other mark. We encode such marks in order to suppress them in presentations whose line breaks don’t match those of the manuscript.
Element Name: <seg>
Encoding Rule: If the author breaks a word across two lines, encode the end-of-line or beginning-of-line hyphen (or mark) with the <seg> tag and a “type” attribute with the value “softhyphen.” The <seg> element includes the <lb/> element.
Sample Source Text:
we are not able
to get out till tom
=orrow we will not
Sample Encoding:
Mark at the end of a line: <lb/>we are not able to get out till tom<seg type="softhyphen">- <lb/></seg>orrow we will not Mark at the beginning of line: <lb/>we are not able to get out till tom<seg type="softhyphen"> <lb/>=</seg>orrow we will not
Sample Image from the MSS: Sample manuscript image
Common Name: Em Dash
Contextual Notes: Encode any single long dash (not hyphens) as character entities.
Entity Name: —
Encoding Rule: Use the character entity — to encode this mark of punctuation. Do not add white space around the entity.
Sample Source Text: Some text—some following text
Sample Encoding:
Some text—some following text
Sample Image from the MSS: No example available
Common Name: Hyphen
Contextual Notes: “True” hyphens—hyphens considered part of the conventional spelling of a word—are entered as hyphens. If, by chance, they appear at the end of a line, they are encoded as “true” hyphens rather than soft-hyphens in order to retain them even in reformatted lines.
Element Name: ‐
Encoding Rule: Enter hyphens as hyphens.
Sample Source Text: top-heavy load
Sample Encoding:
top-heavy load
Sample Image from the MSS: No example available
Common Name: Images
Contextual Notes: To embed images or other rich media, we employ the figure tag.
Element Name: <figure>
Encoding Rule: The <figure> element contains a “rend” attribute with one of several values (e.g., “link” or “embedImg.” Use the project's rich media code generating tools to create <figure> elements.
Sample Source Text: NA
Sample Encoding:
<figure rend="link">
<head>Cox's sketch of a Johnny Jump-Up (<emph rend="italic">Viola cornuta</emph>)</head>
<figDesc>
<xref url="https://images.asc.ohio-state.edu/is/image/mediamanager?. . .
</figDesc>
</figure>
Sample Image from the MSS: No example available
Common Name: Dateline (and date)
Contextual Notes: Typically appears on a separate line at the top of each entry. Dates may appear anywhere in the text.
Element Name: <dateline>
Encoding Rule: The <dateline> element includes (if present in the source document) a <name> element containing the city and a <date> element. The <name> element should have a “reg” attribute specifying a standard version of the name in the form "NAME, ST", and the <date> element should have a “value” attribute listing the date in YYYY-MM-DD format.
Sample Source Text: New York May 7 /51
Sample Encoding:
<dateline> <name type="city" reg="New York, NY">New York </name> <date value="1851-05-07">May 7/51</date> </dateline>
Sample Image from the MSS: Sample manuscript image
Common Name: Paragraph
Contextual Notes: Paragraphs may be indicated in the Cox manuscript by indenting first lines, by starting a new line without filling a line on the page, and/or by leaving white space between paragraphs.
Element Name: <p>
Encoding Rule: Surround paragraphs with the <p> tag.
Sample Source Text: Left Jersey City dock in the ‘Asia’ Capt Judkins Ret. The day was fine, the sun shone - no white caps to the waves. All our baggage being aboard, we went amid the throng on deck. The boat was crowded with passengers and friends. (just named yesterday) came over - Henry Clark we saw, & spoke to one the dock. We began to move away at 12 M.—
Sample Encoding:
Note: For purposes of this example only, there is no internal encoding of text within the paragraph. <p> Left Jersey City dock in the ‘Asia’ Capt Judkins Ret. The day was fine, the sun shone - no white caps to the waves. All our baggage being aboard, we went amid the throng on deck. The boat was crowded with passengers and friends. Cal et ux (just married yesterday) came over - Henry Clark we saw, & spoke to on the dock. We began to move away at 12 M.— </p>
Sample Image from the MSS: Sample manuscript image
Common Name: Title
Contextual Notes: Refers to titles of works, not honorific titles such as “Captain.”
Element Name: <title>
Encoding Rule: The title element takes a "level" attribute, which indicates whether the title refers to an article, monograph, journal, series, or unpublished material, indicated as a, m, j, s, or u, thus making it possible to distinguish among such titles when processing and rendering them accordingly (TEI P4X, ch. 5.2.1).
Sample Source Text: Lord of the Rings
Sample Encoding:
<title level=”m”>Lord of the Rings</title>
Sample Image from the MSS: No example available
Common Name: Continuation Notice
Contextual Notes: Used during an individual editor's work on a series of journal pages.
Element Name: Primarily affects <div1> and <p>, but may affect any element split across a page break.
Encoding Rule: When the first or last page transcribed by a given editor does not end at the end of a division or paragraph, the editor will encode a start or end tag for the affected element(s) as needed to make his or her document well-formed and valid, along with a continuation notice reading "CONTINUED FROM PREVIOUS PAGE" or "CONTINUED ON PREVIOSU PAGE," as appropriate. The extra tag and continuation notice should be the first/last information on the affected page and will be removed when the full edition is compiled.
Sample Source Text:
when will the end come?
not for more than a week—
Poor Julia—have not seen
her all day—
Sample Encoding:
<div1>
<p>
CONTINUED FROM PREVIOUS PAGE
<pb mmid="/5/55375ffa-d0cb-4408-a6de-40329fa7908c" audiostart="00:05:15:05" audioend="00:05:58:05"/>
<lb/> when will the end come?
<lb/> not for more than a week—
<lb/> Poor Julia—have not seen
<lb/> her all day—
</p>
</div1>
Sample Image from the MSS: No example available
