These guidelines (TEI P5 ODD Customization) summarize Livingstone Online project practices for encoding in TEI P5 the manuscripts of David Livingstone (1813-1873), the Victorian explorer, abolitionist, and missionary. The guidelines also offer a fairly comprehensive overview of Livingstone's practices and idiosyncrasies as a writer.
The guidelines are a product of the Livingstone Online Enrichment and Access Project (LEAP), a four-year initiative (2013-2017) funded by the National Endowment for the Humanities (USA). James Cummings with assistance from Adrian S. Wisnicki, Heather F. Ball, and Justin Livingstone created the guidelines, with the initial prose based on Livingstone Online's TEI P5 Tagging Guidelines (2010-13) written by Wisnicki and Ball. Wisnicki has since further developed the guidelines based on the experiences of LEAP.
Significant contributions to the development of the guidelines have also come from the LEAP critical encoding team: Angela Aliff, Mary Borgo, Erin Cheatham, Samantha Fitch, Ashanka Kumari, Chris Lawrence, Anne Martin, Jared McDonald, Alexander Munson, Kate Simpson, and Megan Ward (critical encoding director).
The guidelines are released under a Creative Commons Attribution-NonCommercial 3.0 Unported license, and we encourage broad, non-commercial use of the guidelines per the open educational remit of Livingstone Online.
In the prose of this documentation XML Elements, Attributes and Values appear as follows:
the man turned out to be Livingstone
(Note: the colors/formats are provided only to assist you in distinguishing between tags, attributes, and values. You do not need to change font colors in your transcriptions as you are transcribing. In general these colours mimic those found in the oxygen XML editor.)
the man turned out to be LivingstoneMarked up:
Note: that the first tag denotes the beginning of the marked up text, while the second tag begins with "/" and denotes the end of the marked up text.
we were greeted by the NyamweziMarked up:
If there are two or more tags nested over one bit of text, the closing tags are placed in reverse order:
Original text:we saw the LualabaMarked up:
we saw the LualabaMarked up:
He called me over.Marked up:
<!-- followed by a space and ends with -->. Always add your initials inside but at the end of the comment.When transcribing, please use the LEAP designated file name for the given item. This can be found in the Livingstone Online Digital Catalogue along with the rest of the bibliographical data for the given item. So, for instance, Livingstone's letter to Rev. D.G. Watt (18 August 1850) would be:
liv_000699.xml
If you are transcribing the given item with other individuals in sequence (and so the transcription is not yet final) please add your initials directly after the LEAP designated name:
liv_000699_aw_hb_ks_hb.xml
In the above example, the four sets of intials indicate that the transcription has been worked on in four stages. The first three stages were done by three different individuals (aw, hb, ks) and the last stage was done by the second individual (hb).
Please Note: All TEI P5 XML files are in the TEI Namespace which means their root element has a psuedo-attribute xmlns with a value of "http://www.tei-c.org/ns/1.0". This is the TEI Namespace and is inherited by any elements underneath keeps TEI elements safe from confusion with similarly-named elements from other schemes.
Definitions of the elements used above are:
| xml:id [att.global] | (identifier) provides a unique identifier for the element bearing the attribute. |
That might look overwhelming, so let's break that down. Notice that there are really only a few elements directly inside <teiHeader>: <fileDesc>, <profileDesc>, and <revisionDesc>. Take a look at the header text above. You'll need to change some parts of this text (indicated in the comments) each time you start a new file in XML. Please copy the data exactly as found on Livingstone Online.
Once you have found the corresponding entry for the item you're transcribing on Livingstone Online, you will need to modify the template to match this information.
The item <title> should match the title found on Livingstone Online.
Definitions of the elements used above are:
Definitions of the elements used above are:
Definitions of the elements used above are:
Definitions of the elements used above are:
| ident | (identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute. |
Definitions of the elements used above are:
| when [att.datable.w3c] | supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. |
| who [att.ascribed] | indicates the person, or group of people, to whom the element content is ascribed. |
We use the <div> to contain the main body of text of any given Livingstone object, so in most cases a transcription will only have one <div> elment that opens and closes the text. However, there are some cases where a second <div> element should be used. See 5. Front and Back Matter, 11.4. Textual Colors, and 11.10. Textual Directions. In other cases, it may be necessary to mark the beginning of a new gathering with <gb/> (see 4.1. New Gatherings).
Definitions of the elements used above are:
We record the beginning of a new gathering, if a document consists of more than one, using the <gb/> tag. The specification of an type is optional, while the value of type will often be improvised based on the source material.
Note: If <gb/> is used, every gathering in the document should be marked, including the opening one.
Note: Using the <gb/> tag with the <div> is allowed, but not required. One would normally use both in combination only when a new gathering begins a new divison or section of text.
Note: The <gb/> tag should not normally be used without consulting the project directors
Definitions of the elements used above are:
Definitions of the elements used above are:
Note that this combined or empty element ends with a "/" and has no separate closing tag. The facs attribute points to the image facsimile for this page, the n attribute records the project page number separately.
Definitions of the elements used above are:
| facs [att.global.facs] | (facsimile) points to all or part of an image which corresponds with the content of the element. |
| n [att.global] | (number) gives a number (or other label) for an element, which is not necessarily unique within the document. |
As we traveledMarked up:
I came
across two men.
Note: Please do not mark blank space at the end of a page with a series of <lb/> tags. Once the text and/or material features on a given page end, you do not need to record any space beyond unless it has some clear semantic value. If unsure, leave a comment asking for further review by the project team.
Definitions of the elements used above are:
Note: It is especially important to use <p rend="no-indent"> when marking new, dated diary entries that Livingstone begins on a new line but does not indent.
Also, remember at the end of the paragraph to use the closing paragraph tag </p>.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
For coding dates that Livingstone adds to the margin of the Unyanyembe Journal, see 11.17. Authorial Notes Within the Text.
Definitions of the elements used above are:
| when [att.datable.w3c] | supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. |
| from [att.datable.w3c] | indicates the starting point of the period in standard form, e.g. yyyy-mm-dd. |
| to [att.datable.w3c] | indicates the ending point of the period in standard form, e.g. yyyy-mm-dd. |
Note that in the example above, each line is marked with a <p> tag and an rend attribute is used with a value such as "center" or "right" or even "no-indent". This coding places the line roughly where it appears on the page. The placement is then further fine-tuned with the use of <space/> with attributes specifying both unit and extent. Finally, note that the value for unit can be either "chars" or "words".
Note: Formerly, we used the <opener> and <closer> tags (and various associated tags such as <dateline>, <salute>, and <signed>) for the opening and closing of letters, but these are no longer in use. However, instances of these tags may still be found in some Livingstone Online legacy transcriptions
For both the opening and closing of letters, linebreaks (see 7. The Beginning of a Manuscript Line) should be marked in the regular fashion, as in the examples above.
The <date> and <persName> elements are discussed in more detail below.
Definitions of the elements used above are:
Note: Formerly, we used the <postscript> tag for postscripts, but this is no longer in use. However, instances of this tag may still be found in some Livingstone Online legacy transcriptions
Definitions of the elements used above are:
For any page numbers instituted by Livingstone himself, use the <fw> element plus n in the following manner:
In other words, whenever <fw> is used to encode one of Livingstone's page numbers, n value should begin with "heading_" followed by the number Livingstone uses, in the form that he uses it (i.e., Roman or Arabic numeral).
For catch words, i.e., words that appear at the foot of a page and duplicate the first word of the following page, do not use <fw>. Instead mark the catch words with <seg type="catch">.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
If the original text is formatted in some manner such as underlining, superscript, etc., use the <hi> element with the rend attribute.
I saw the man Marked up: If there is more than one type of formatting, for instance both underline and superscript, use the rend attribute only once but provide two values separated by a space.
He was the Number 1 manMarked up:
Also Note: Please don't use rend plus values like "left", "right", and "center" to position things horizontally on the page. Instead, use the <space/> for such positioning (see 11.6. More Than One Space between Words). Additionally, if something is placed on the left, no rend with a value of "left" is necessary.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
Use the <w> element to mark words that Livingstone breaks up over two lines and use <seg type="hyphen"> to mark any associated hyphens or similar symbols. You should also add the break attribute with the value of "no" to the <lb/> that falls between the two halves of the word. For LEAP materials the assumed value for the break attribute is "yes", so you do not need to provide this unless it is an exceptional circumstance. Use "maybe" only in those cases when you are not sure whether a single word apparently broken up over two lines may indeed be two words.
Livingstone's use of hyphens is erratic. Sometimes he hyphenates a word at the end of the first line, sometimes at the beginning of the second, sometimes in both places, sometimes in neither. Sometimes he also uses "=" (i.e., the equal sign) in place of a hyphen.
We code each of these instances in the same way, but we also always supply a hyphen at the end of the line if Livingstone himself has failed to provide it.
Definitions of the elements used above are:
| break [att.breaking] | indicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace. |
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
In other words, in the example above the space being marked is actually five characters long. One of these spaces is marked in the normal fashion, the other four are marked with the <space> tag. Please follow this format when marking usual spacing between words.
The value for the extent attribute will of course be a bit of a judgment call, but a good rule of thumb is to mark only those spaces that extend for more than two characters and/or have some obvious, non-trivial significance in the text. For instance, Livingstone on occasion inserts an unusally large space just before a new sentence and indeed uses this space to indicate that the substance of the sentence that follows the space differs significantly from that of the sentence that precedes the space.
The value "chars" stands for "characters"; you can also use "words". There is a dim attribute on <space> with allowed values of "horiztonal" or "vertical", but the default assumption in LEAP is that extra space is horizontal so this does not need to be marked.
The only exception for this rule is <milestone>, where you can use rend with values of "center" and "right" to position shorter lines (e.g., "half-line", "quarter-line", etc.) across the page.
Definitions of the elements used above are:
| extent [att.dimensions] | indicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words. |
| unit [att.dimensions] | names the unit used for the measurement |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
Definitions of the elements used above are:
Definitions of the elements used above are:
Livingstone often uses lines that he draws across the page to separate sections of the text. Sometimes he uses a single line that runs across the entire page from left to right; sometimes a double-line; sometimes a single line that only runs across half or a quarter of the page. For all such lines, use the <milestone/> element in the following manner:
As in the example, <milestone/> should always inlcude a unit attribute with the value of "section" and a rend attribute. Possible values for the rend attribute include: "line", "double-line", "triple-line", "three-quarter-line", "half-line", "quarter-line", "dotted-line", and "dotted-double-line".
Definitions of the elements used above are:
| unit [att.milestoneUnit] | provides a conventional name for the kind of section changing at this milestone. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
There are four possible situations we've encountered, so here's how to handle them:
Definitions of the elements used above are:
Occassionaly Livingstone breaks up his text into one or more columns. We mark this shift using the <cb/> tag plus the rend attribute with the appropriate value of "left", "center", or "right", or the n attribute with the appropriate value of "1", "2", "3", etc. Either of these attribute/value combinations is acceptable; it is left open to the judgment of the transcriber to choose the one most appropriate for the context. However, one should use n plus a series of numbers for instances of four or more columns.
If Livingstone breaks his writing up into more than one column, please code as follows. First, use <cb rend="left/> (or <cb n="1"/>) to mark the beginning of the first column to the left. Then transcribe the first column. Then, as appropriate, use <cb rend="center/> or <cb rend="right/> (or <cb n="2"/>) to mark the beginning of the next column to the right. Then transcribe the next column (if there is one). And so on. Finally, use <cb/> without any attribute to mark the return to normal text.
Note: As in the example above, <cb> may be used inside or outside of the <p> tag (or the <ab> tag).
Note: <cb> is the assumed default, so should not normally be marked except in instances, as above, where there have been multiple columns, but the text is now returning to normal.
Note: In some instances it may be better to use the <table> tag plus the <row> and <cell> tags or, alternately, to use the <list> and <item> tags (see 20. Using Lists and Tables). However, there is no fast rule; often it will be a judgment call. If in doubt, please consult the project directors.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| n [att.global] | (number) gives a number (or other label) for an element, which is not necessarily unique within the document. |
Occasionally Livingstone includes blocks of text on a given manuscript page that have no clear relationship to the main text on that page. Such blocks should be encoded with the <ab> element.
Note that, as in the example above, you can use <p> or <ab> to enclose sections of text, but not both.
Definitions of the elements used above are:
he saw us [in this case it's clear in the ms. that "saw" was added later]Marked up:
he saw us Marked up: Note: For coding additions and deletions that span more than a few lines of text, please consult the project team.
If you can identify individual hands, but not to whom they belong, these values could be "#hand01" or "#hand02" or similar.
Note: The Missionary Travels team is also working with more specialized metamarks. For guidance on using these, see 23.4. Metamarks. This additional coding is not required in other parts of the project, so should only be done in consultation with the project team.
Definitions of the elements used above are:
| place [att.placement] | specifies where this item is placed. |
| hand [att.written] | points to a <handNote> element describing the hand considered responsible for the textual content of the element concerned. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
For additions or deletions that span more than one paragraph (<p>) or section of text (<ab>), use the <addSpan/> or <delSpan/> elements combined with the <anchor/> element.
The <addSpan/>, <delSpan/>, and <anchor/> elements can appear anywhere in a <div>, including outside or inside a <p> or <ab>. As a result, they can be used to mark precisely where a longer addition or deletion begins and ends without regard to other coding.
Note: In the above examples the values "longadd-1" and "del-1" are arbitrary. The value, however, must be the same for the <addSpan/> and its corresponding <anchor/> tag, or for <delSpan/> and its corresponding <anchor/> tag. The given value should not otherwise be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive these values for each instance of <addSpan/> or <delSpan/> in order to avoid repetition.
Also note: If the given addition or deletion spans less than one paragraph, then use the <add> or <del> tags (see 11.13. Addition to or Deletions from the Original Manuscript).
Definitions of the elements used above are:
| spanTo [att.spanning] | indicates the end of a span initiated by the element bearing this attribute. |
| hand [att.written] | points to a <handNote> element describing the hand considered responsible for the textual content of the element concerned. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| xml:id [att.global] | (identifier) provides a unique identifier for the element bearing the attribute. |
On a number of occasions, Livingstone or someone else places an addition elsewhere other than in the immediate area where it should be added (for instance on another page). The place for insertion is often indicated by an arrow that runs from the addition to its intended position. Code such additions as follows.
First, code the addition in the place where it actually appears on the page.
If the addition is on an otherwise blank page, this will involve indicating that there are empty lines that precede the addition. For this, use the <space/> tag to mark multiple blank lines (see 11.7. One or More Spaces between Lines).
(Notice that the value for corresp is preceded by a "#" [number sign].)
(Notice that the value of the attribute xml:id is the same as on the corresp above, but now is not preceded by a "#" [number sign].)
Note: In the above example the value of "add-1" is arbitrary. The value must be the same for the relevant attributes on the <add> and <anchor/> tags, but should also not be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive this value for each such addition in order to avoid repetition.
Also note: The above method can be used to insert longer additions that span several paragraphs by replacing <add> with <addSpan/>. (For guidance on <addSpan> see 11.14. Additions or Deletions that Span More Than One Paragraph).
However, to use <addSpan/> to encode a standalone addition, two <anchor/> tags will be required – one in conjunction with <addSpan/> to record the extent of the addition (i.e., its beginning and end), the other to mark the place the addition is intended to be inserted. The <addSpan/> should thus have both the spanTo and corresp attributes.
In the example above, the first <anchor/> tag thus indicates where the addition ends; the second <anchor/> tag indicates where Livingstone wants the addition inserted.
Note: In the above example, the value "longadd-1" on spanTo is arbitrary. The value must be the same for the corresponding <addSpan/> and <anchor/> tags but should also not be repeated for any other tags. Depending on the project, you will be given specific instructions on how to derive this value for each instance of <addSpan/> in order to avoid repetition.
Definitions of the elements used above are:
| dim | (dimension) indicates whether the space is horizontal or vertical. |
| extent [att.dimensions] | indicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words. |
| unit [att.dimensions] | names the unit used for the measurement |
| place [att.placement] | specifies where this item is placed. |
| corresp [att.global.linking] | (corresponds) points to elements that correspond to the current element in some way. |
| xml:id [att.global] | (identifier) provides a unique identifier for the element bearing the attribute. |
| spanTo [att.spanning] | indicates the end of a span initiated by the element bearing this attribute. |
| corresp [att.global.linking] | (corresponds) points to elements that correspond to the current element in some way. |
In the example above, unknown hand #2 writes the word "any" over Livingstone’s word "no." The mark up shows that Livingstone’s initial word has been replaced (and hence deleted) by overwriting.
The <retrace> element specifies that it is Livingstone’s hand doing the retracing.
In the example above, the word "You" has been deleted by someone else and then also deleted by Livingstone.
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
| place [att.placement] | specifies where this item is placed. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| hand [att.written] | points to a <handNote> element describing the hand considered responsible for the textual content of the element concerned. |
If the date added to the left margin spans more than one line, use <lb/> as appropriate (see 7. The Beginning of a Manuscript Line):
Definitions of the elements used above are:
Livingstone limits his punctuation primarily to n-dashes (-), which often shade into m-dashes or even longer dashes, and equal signs (=). He distinctly prefers n-dashes, but he uses these interchangeably with equal signs in places of such punctuation as commas, colons, semicolons, and periods as well as to mark simple pauses in the text. When transcribing an n-dash or equal sign, please adhere to the following guidelines.
When Livingstone uses an n-dash for any reason other than hyphenation of a word, place a space before and after the n-dash when trascribing it, even if it looks like Livingstone himself hasn't:
a very old town - country
Likewise, when transcribing an equal sign that Livingstone has used as punctuation, place a space before and after, even if it looks like Livingstone himself hasn't:
tea = coffee
When Livingstone uses an n-dash to introduce or follow a quotation, he places the n-dash directly below the opening or closing quotation marks rather than next to them. However, when transcribing this, you should nonetheless put a space between the dash and the quotation mark:
He said - "I will" - in answer to me.
If unsure, whether Livingstone is using a period or dash, select dash by default.
If Livingstone's n-dash looks like an m-dask or even longer, use two or more n-dashes without any space between them:
poor -- mostly
Livingstone also has a tendency to run the first person pronoun ("I") onto the following word, as in the following: "Iwent". All instances of this should be silently separated when transcribed:
I went
Livingstone is by no means consistent in his use of capitalization and, moreover, it is often even not clear whether a word is capitalized or not. When transcribing, use the following rules of thumb. When a word is capitalized (or not) and the context suggests this is correct, transcribe as is. When a word is capitalized (or not) and the context suggests this is incorrect, transcribe as is but if (in your opinion) it is very important that the capitalization be corrected, use <choice> plus <sic> and <corr> to provide a corrected verison of the word:
For use of the <choice>, <sic>, and <corr> elements, see 12.2. Authorial Grammatical, Typographical, and Other Mistakes.
Finally, if it is not clear whether a word is capitalized and it would therefore be OK to transcribe it either way, allow context to guide your decision as to whether to capialize it or not.
I recieved your letterMarked up:
Important Note: Be sure to remember that there is a difference between errors and variants. If Livingstone makes an obvious error, then use <choice>, <sic>, and <corr>, as described above. However, if Livingstone uses a variant that would not have been incorrect in his own day (e.g., Mosambique) and/or that exists in a more common, alternative form now (Mozambique), use <choice>, <orig>, and <reg> to normalize this (see 12.7. Normalized Text).
Definitions of the elements used above are:
| cert [att.global.responsibility] | (certainty) signifies the degree of certainty associated with the intervention or interpretation. |
Definitions of the elements used above are:
| cert [att.global.responsibility] | (certainty) signifies the degree of certainty associated with the intervention or interpretation. |
Definitions of the elements used above are:
| cert [att.global.responsibility] | (certainty) signifies the degree of certainty associated with the intervention or interpretation. |
In the <gap> element, the values we use for the agent attribute include: "blot", "fading", "hole", "illegible", "overwriting", and "stain".
The value of the extent attribute is always an approximation.
Note: For coding manuscript damage that spans more than a few lines of text, please consult the project team.
Definitions of the elements used above are:
| agent | in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified. |
| extent [att.dimensions] | indicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words. |
| unit [att.dimensions] | names the unit used for the measurement |
If a portion of the original text is missing for whatever reason and you supply it, use <supplied> to mark up this addition; furthermore, use the cert with values of "low", "medium", "high" to denote the degree of confidence in the addition you have made:
He saw manMarked up:
Important Note: You should be very conservative in your use of the <supplied> tag and only supply text of which you are 100% certain. Otherwise, use <gap/>. In other words, avoid guessing at Livingstone's meaning unnecessarily and supply words for clarification only when absolutely essential.
Definitions of the elements used above are:
| cert [att.global.responsibility] | (certainty) signifies the degree of certainty associated with the intervention or interpretation. |
Definitions of the elements used above are:
& instead of an actual ampersand: Original text: I saw one man & one womanMarked up:
my no. 1 friendMarked up:
Please note: Any prefix pertaining to a personal name, i.e. Dr, Mr, Miss, Rev, need not be expanded.
Definitions of the elements used above are:
| cert [att.global.responsibility] | (certainty) signifies the degree of certainty associated with the intervention or interpretation. |
Please note: In the context of names, titles such as Dr., Mrs., and the like do not need to be expanded. Likewise any possessive marker ('s) should be left outside the <persName> tag whenever possible.
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Important Note: Formerly Livingstone Online always used a combination both of <placeName> and one of the foregoing tags (<bloc>, <country>, <region>, <settlement>, <geogName>), but we are no longer following that practice. Legacy Livingstone Online transcriptions, however, will still be coded in this fashion.
Note: Livingstone uses distinct abbreviations to denote "river" and "rivulet." He abbreviates "river" as either "R." or "R", while he abbreviates "rivulet" as "Rt" or "Rt". In the latter case, the superscript "t" may resemble a superscript "r" but should nonetheless be treated as a "t". Code these abbreviations as follows:
You should also use <geogName> when encoding the full reference to a geographical entity that includes any kind of formal name (which itself would also be separately encoded:
If Livingstone refers to a specific, named geographical entity (and you know what that entity is), but uses only a generic term such as "the Lake" or "the River," you should identify this entity in a comment that directly follows the relevant term, but not otherwise mark the term used:
Note: Livingstone uses "Metamba" to reference the Central African rainforest, although the term is really a local word for "forest." To account for this usage, please code as follows:
Note: "Cape" and "Interior" should be coded with the <region> element (even though technically incorrect). Code "Zanzibar" as follows:
Directional words (North, South, East, and West) should not be tagged when referring to directions. Rather tag directional words only when Livingstone uses them to designate a region:
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Note: Terms relating to meals (such as breakfast, lunch, supper) should not be coded as "foodstuff."
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
However, for practitioners of particular faiths, see 17. Organizations and Other Groups.
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Note: In Missionary Travels, the following terms and any variations thereof should be marked up as "occupation": chief, chieftain, and rain doctor.
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
Use the <orgName> element to mark instances in the text where there is mention of an organization or other type of group (or any reference to an individual as being part of a group) that is not covered by 16.2. Nationalities, 16.3. People of a Given Nationality, or 16.4. African Ethnic Groups. Note that all the following entities should be marked with the <orgName> element: Aborigine, Aborigines, African, Africans, Arab, Arabs, Banian, Banians, Boer, Boers, Bushman, Bushmen, Caffre (or the variant spellings, Kaffre and Kaffir), Caffres (or the variant spellings, Kaffres and Kaffirs), Christian (an individual; for use of Christian as an adjective, see 16.5. Religious Faith), Christians, European, Europeans, Griqua, Moslem (an individual; for use of Moslem as an adjective, see 16.5. Religious Faith), and Moslems. For references to organized religions (e.g., Christianity, Islam), see 16.5. Religious Faith.
"Johanna men" and "Nassick boys" (and all variants of these two groups) to be coded as follows:
Please note: Havildar and Sepoy (singular and plural) should be marked with both <orgName>, and <term> with the type attribute and a value of "occupation":
Definitions of the elements used above are:
| type [att.typed] | characterizes the element in some sense, using any convenient classification scheme or typology. |
In some cases, one or more entities encoded with the <orgName> or <term type="occupation"> tags may themselves, in combination, constitute a larger organization or group. In such cases, nestle the individual entities within one additonal <orgName> as follows:
In the above examples, "Arab" and "trader" (first example) and "Portuguese" and "sailor" (second example) are coded per normal practice, but are also collectively encapsulated, in each case, in an additional <orgName> tag.
Note: All variants of "slave trader" should be coded in the following unique manner:
In other words code "slave" with <orgName> per usual practice. Then code the whole phrase "slave trader" as a <term type="occupation">. Finally, wrap the fully coded phrase "slave trader" in an additional <orgName> tag.
Definitions of the elements used above are:
Use <bibl> to encode any elements of a book, including the title, that Livingstone references:
Definitions of the elements used above are:
When dealing with foreign words, there are three steps to complete:
Please note: If you are unsure of the language/dialect, but know that it is not English, simply mark it as "Undetermined" using the code "und". Also, we do not tag references to languages (Spanish, French, etc.) in any way.
Definitions of the elements used above are:
| ident | (identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute. |
| xml:lang [att.global] | (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47. |
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
Definitions of the elements used above are:
The above example indicates that "26" and "29" appear sequentially, left to right and separated by a space, in the right-hand corner of the top margin of the given page.
Note: While the various sets of numbers may be added by different hands there is little to be gained by differentiating them. Indeed, it’s quite likely that they’re actually the same hand – sometimes it’s difficult to distinguish between them. So on the assumption that it’s one hand adding the numbers, but perhaps at different times, we consider them to be two separate additions.
Also note: While "gray right" is often the right value to use on rend, "gray left" and "gray center" will also be required on occasion.
Definitions of the elements used above are:
| place [att.placement] | specifies where this item is placed. |
| hand [att.written] | points to a <handNote> element describing the hand considered responsible for the textual content of the element concerned. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
In Missionary Travels, the majority of text is rendered to the right of the page in order to leave room for marginal comments on the left. Accordingly, the value "right" is used on rend in the <body> element at the beginning of the transcription i.e. <body rend="right">.
Please also include a comment in such places, noting that Livingstone has departed from his norm by writing a portion of text across the full width of the page.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
In Missionary Travels the various editors occasionally format portions of Livingstone's text. For instance, unknown hand#2 might underline one of Livingstone's words in pencil. Record such occurrences using the resp (responsibility) attribute on the <hi> tag. Use the rend attribute per usual practice, as necessary, to record other characteristics of the formatting.
Note: The <hi> element doesn’t accept hand, so we indicate authorial responsibility using resp, as in the example above.
Definitions of the elements used above are:
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| resp [att.global.responsibility] | (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber. |
Long Arrows
But when there appears to be a caret with a long line following it, we should just treat this as an arrow and therefore encode it with the <metamark/> tag. In other words, in such a case we shouldn’t mark up the caret and arrow separately.
For such arrows: Use the <add> element since most of them are clearly added later in order to point to an additional piece of text.
Also include function on the <metamark/> to indicate the purpose of the metamark. Arrows will be marked up with the function "insertion".
Note: Long arrows leading to a portion of text are generally the only metamarks (aside from carets) that should be nested in an <add> tag. See further details below.
Definitions of the elements used above are:
| function | describes the function (for example status, insertion, deletion, transposition) of the metamark. |
Other Metamarks
Where possible, record the purpose of a particular metamark by using the function attribute with any of the following values: "insertion", "deletion", "reorder", "newParagraph", "let-stand", or "query":
For metamarks not covered by the above, only record the presence of the <metamark/> along with a note that the metamark should be reviewed.
However, if a metamark encloses text (for example, a square or circle is drawn around a word, or a long line in the margin brackets a portion of text), encode the extent of the metamark by using the spanTo attribute and the <anchor/> tag, as per the following instructions.
(Notice that the value for spanTo is preceded by a "#" [number sign].)
(Notice that the value of the attribute xml:id is the same as on the spanTo above, but now is not preceded by a "#" [number sign].)
In the above example, the value of "meta-1" is arbitrary. The value must be the same for spanTo on the <metamark/> tag and xml:id on the <anchor/> tag, but should also not be repeated for any other tags. Drawing from the list on the Missionary Travels google doc "Transcription Workflows," use the next available value and highlight it in yellow to show that it has been used.
Note: If a metamark is in an unusual place (for example "marginleft", "margintop", "marginbottom"), you may also include the place attribute on <metamark/>. This is only necessary if the metamark is outside (or above or below) the body of the text and needs to be signalled specially.
As in the example above, the <metamark/> element doesn’t accept hand, so we indicate the authorial responsibility using resp.
Please note that it is generally only necessary to use a separate <add> tag on a metamark when encoding a long arrow leading to a portion of text. In other words, if the metamark is part of a longer addition that includes text added by either DL or an editor, it should be nested in an <add> tag. Otherwise, by default we assume that metamarks are added later and therefore this does not need to be coded separately.
Definitions of the elements used above are:
| function | describes the function (for example status, insertion, deletion, transposition) of the metamark. |
| spanTo [att.spanning] | indicates the end of a span initiated by the element bearing this attribute. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| resp [att.global.responsibility] | (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber. |
| xml:id [att.global] | (identifier) provides a unique identifier for the element bearing the attribute. |
Note on "reorder"
When a textual mark or arrow is used to signal that a portion of text should be moved to another place in the document (often up or down several lines), do not move the word itself while transcribing. Instead, transcribe what you see on the page, while capturing the intended reordering as follows:
(Notice that the value for corresp is preceded by a "#" [number sign].)
(Notice that the value of the attribute xml:id is the same as on the corresp above, but now is not preceded by a "#" [number sign].)
Note: In the above examples the values "reorder-1" and "reorder-2" are arbitrary. The value must be the same for corresp on the <seg> tag and the xml:id on the <anchor/> tag, but should also not be repeated for any other tags. Drawing from the list on the Missionary Travels google doc "Transcription Workflows," take the next available value and highlight it in yellow to show that it has been used.
Also note: If it is the case that two words are intended to be switched (a transposition, technically), code this as a single reordering where possible (i.e. if the two words are side-by-side). However, if it is not possible to capture Livingstone's or the editor's intention using a single reordering, code the two words as separate reorderings, each contained in their own <metamark/> and <anchor/> tags.
Definitions of the elements used above are:
| corresp [att.global.linking] | (corresponds) points to elements that correspond to the current element in some way. |
| xml:id [att.global] | (identifier) provides a unique identifier for the element bearing the attribute. |
| function | describes the function (for example status, insertion, deletion, transposition) of the metamark. |
| rend [att.global.rendition] | (rendition) indicates how the element in question was rendered or presented in the source text. |
| resp [att.global.responsibility] | (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber. |
| spanTo [att.spanning] | indicates the end of a span initiated by the element bearing this attribute. |
This is particularly important for volume three of Missionary Travels, where a considerable portion of text is written by Charles Livingstone and by another unidentified hand.
Note: <p> must be contained within <div>, so the previous paragraph must be closed before a new <div> can be opened. Whether or not the long portion of text begins a new paragraph, it will thus be necessary to make one to indicate the change of hand.
Definitions of the elements used above are:
| resp [att.global.responsibility] | (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber. |
It is important to note that multiple hands contribute to the manuscript of Missionary Travels. (For guidance on coding these, see 11.13. Addition to or Deletions from the Original Manuscript and 23.5. Substantial Sections in Another Hand.)
In Missionary Travels the hands currently in use are:
Please notify the project team if you discover another hand.
Note: In the example above, empty lines have been put between the <handNote> elements to facilitate reading, but such emtpy lines are not necessary in your actual transcription
Definitions of the elements used above are:
Analysis Module
Core Module
Dictionaries
Figures Module
Header Module
Linking Module
Manuscript Description Module
Names and Dates Module
Text Critical Apparatus Module
Text Structure Module
Transcription Module
| <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple <TEI> elements may be combined to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text] | |||||||||
| Module | textstructure — Formal declaration and Reference Pages | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
| ||||||||
| 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, using the xmlns attribute. | ||||||||
| 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 name space.</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 |
<s:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<s:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/> | ||||||||
| Schematron |
<s:ns prefix="rng"
uri="http://relaxng.org/ns/structure/1.0"/> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="teiHeader"/>
<classRef key="model.resourceLike"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
</content>
| ||||||||
| Schema Declaration |
element TEI
{
att.global.attributes,
att.typed.attributes,
attribute version { text }?,
( teiHeader, model.resourceLike+ )
} | ||||||||
| <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 — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.written (@hand) |
| Member of | |
| Contained by | header: availability change editionStmt encodingDesc handNote langUsage licence prefixDef projectDesc publicationStmt sourceDesc styleDefDecl msdescription: accMat acquisition condition custEvent custodialHist decoDesc decoNote foliation handDesc history layout layoutDesc msContents msDesc msItem msPart objectDesc origin physDesc provenance recordHist scriptDesc seal sealDesc signatures summary support supportDesc surrogates textcrit: rdg textstructure: back body div front postscript transcr: metamark |
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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 |
<s:report test="not(ancestor::tei:floatingText) and (ancestor::tei:p or ancestor::tei:ab)
and not(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.
</s:report> |
| Schematron |
<s:report test="ancestor::tei:l or ancestor::tei:lg"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab.
</s:report> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
|
| Schema Declaration |
element ab
{
att.global.attributes,
att.typed.attributes,
att.written.attributes,
macro.paraContent
} |
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions] | |||||||||||||
| Module | core — Formal declaration and Reference Pages | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | analysis: w core: abbr add addrLine author bibl biblScope choice corr date del desc editor expan foreign gloss head hi item label measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset orgName persName placeName region roleName settlement surname textcrit: rdg | ||||||||||||
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app | ||||||||||||
| 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
{
att.global.attributes,
attribute type { text }?,
macro.phraseSeq
} | ||||||||||||
| <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript being described, such as non-contemporaneous documents or fragments bound in with the manuscript at some earlier historical period. [10.7.3.3. Accompanying Material] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) |
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig p pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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
{
att.global.attributes,
att.typed.attributes,
macro.specialPara
} |
| <acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. History] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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)) |
| Contained by | msdescription: history |
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig p pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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
{
att.global.attributes,
att.datable.attributes,
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.4.3. Additions, Deletions, and Omissions] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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) (att.written (@hand)) att.placement (@place) att.typed (@type) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) |
| Member of | |
| Contained by | analysis: w core: abbr add addrLine author bibl biblScope corr date del editor expan foreign gloss head hi item label measure name note orig p pubPlace publisher q quote ref reg sic term title unclear figures: cell msdescription: accMat acquisition condition custEvent decoNote foliation layout material objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation birth bloc country death education faith forename geogFeat geogName nationality occupation offset orgName persName placeName region roleName settlement surname textcrit: rdg |
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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
{
att.global.attributes,
att.transcriptional.attributes,
att.placement.attributes,
att.typed.attributes,
att.dimensions.attributes,
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 — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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) (att.written (@hand)) att.placement (@place) att.typed (@type) att.spanning (@spanTo) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) |
| Member of | |
| Contained by | analysis: w core: abbr add addrLine address author bibl biblScope corr date del editor expan foreign gloss head hi imprint item label list measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material msItem objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset orgName persName person placeName region roleName settlement surname textcrit: rdg |
| 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/>
|
| Schema Declaration |
element addSpan
{
att.global.attributes,
att.transcriptional.attributes,
att.placement.attributes,
att.typed.attributes,
att.spanning.attributes,
att.dimensions.attributes,
empty
} |
| <additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. Additional Information] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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>
<elementRef key="adminInfo" minOccurs="0"/>
<elementRef key="surrogates"
minOccurs="0"/>
<elementRef key="listBibl" minOccurs="0"/>
</sequence>
</content>
|
| Schema Declaration |
element additional
{
att.global.attributes,
( adminInfo?, surrogates?, listBibl? )
} |
| <addrLine> (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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 { att.global.attributes, macro.phraseSeq } |
| <address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 corr date del desc editor expan foreign gloss head hi item label measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear header: authority catDesc change edition funder handNote language licence principal publicationStmt rendition msdescription: accMat acquisition condition custEvent decoNote foliation layout material objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName location nationality occupation offset orgName persName placeName region roleName settlement surname textcrit: rdg |
| May contain | |
| 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>
<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
{
att.global.attributes,
( model.global*, ( model.addrPart, model.global* )+ )
} |
| <adminInfo> (administrative information) contains information about the present custody and availability of the manuscript, and also about the record description itself. [10.9.1. Administrative Information] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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>
<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
{
att.global.attributes,
( recordHist?, availability?, custodialHist?, model.noteLike? )
} |
| <affiliation> contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description] | |||||||||||
| Module | namesdates — Formal declaration and Reference Pages | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLikeatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.naming (@role) (att.canonical (@ref))
| ||||||||||
| Member of | |||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor expan foreign gloss head hi item label measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName location nationality occupation offset orgName persName person placeName region roleName settlement surname textcrit: rdg | ||||||||||
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app | ||||||||||
| Note | If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element. | ||||||||||
| Example | <affiliation>Junior project officer for the US <name type="org">National Endowment for
the Humanities</name>
</affiliation> | ||||||||||
| Example | This example indicates that the person was affiliated with the Australian Journalists Association at some point between the date ranges listed. <affiliation notAfter="1960-01-01" notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation> | ||||||||||
| Example | This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date ranges listed. <affiliation from="1902-01-01" to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
| ||||||||||
| Schema Declaration |
element affiliation
{
att.global.attributes,
att.editLike.attributes,
att.datable.attributes,
att.naming.attributes,
attribute type { text }?,
macro.phraseSeq
} | ||||||||||
| <age> specifies the age of a person. [13.3.2.1. Personal Characteristics] | |||||||||||||||||||
| Module | namesdates — Formal declaration and Reference Pages | ||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLikeatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | namesdates: person | ||||||||||||||||||
| May contain | core: abbr address cb choice date expan foreign gap gb gloss hi lb measure measureGrp milestone name note pb ref term title dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app transcr: addSpan damageSpan delSpan fw listTranspose metamark space subst | ||||||||||||||||||
| Note | As with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text. | ||||||||||||||||||
| Example | <age value="2" notAfter="1986">under 20 in the early eighties</age> | ||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
| ||||||||||||||||||
| Schema Declaration |
element age
{
att.global.attributes,
att.editLike.attributes,
att.datable.attributes,
att.dimensions.attributes,
attribute type { text }?,
attribute value { text }?,
macro.phraseSeq.limited
} | ||||||||||||||||||
| <altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) |
| Contained by | msdescription: msIdentifier |
| 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>
<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
{
att.global.attributes,
att.typed.attributes,
(
placeName?,
bloc?,
country?,
region?,
settlement?,
geogName?,
institution?,
repository?,
collection?,
idno,
note?
)
} |
| <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 — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) |
| Member of | |
| Contained by | analysis: w core: abbr add addrLine address author bibl biblScope corr date del editor expan foreign gloss head hi imprint item label list listBibl measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material msItem objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset org orgName persName person placeName region roleName settlement surname textcrit: rdg |
| 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>
</content>
|
| Schema Declaration |
element anchor { att.global.attributes, att.typed.attributes, empty } |
| <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. [12.1.1. The Apparatus Entry] | |||||||||||||||||||||||||||||||
| Module | textcrit — Formal declaration and Reference Pages | ||||||||||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | analysis: w core: abbr add addrLine address author bibl biblScope corr date del editor expan foreign gloss head hi imprint item label list measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material msItem objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset orgName persName person placeName region roleName settlement surname textcrit: rdg | ||||||||||||||||||||||||||||||
| 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>
<elementRef key="lem" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.rdgLike"/>
<classRef key="model.noteLike"/>
<elementRef key="wit"/>
<elementRef key="rdgGrp"/>
</alternate>
</sequence>
</content>
| ||||||||||||||||||||||||||||||
| Schema Declaration |
element app
{
att.global.attributes,
attribute type { text }?,
attribute from { text }?,
attribute to { text }?,
attribute loc { list { + } }?,
( lem?, ( model.rdgLike | model.noteLike | wit | rdgGrp )* )
} | ||||||||||||||||||||||||||||||
| <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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role) (att.canonical (@ref)) |
| Member of | |
| Contained by | |
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| 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
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq
} |
| <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 — Formal declaration and Reference Pages | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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
{
att.global.attributes,
att.declarable.attributes,
attribute status { "free" | "unknown" | "restricted" }?,
( model.availabilityPart | model.pLike )+
} | ||||||||
| <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
| Module | textstructure — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | |
| 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
{
att.global.attributes,
(
(
model.frontPart
| model.pLike.front
| model.pLike
| model.listLike
| model.global
)*,
(
(
model.div1Like,
( model.frontPart | model.div1Like | model.global )*
)
| ( model.divLike, ( model.frontPart | model.divLike | model.global )* )
)?,
( model.divBottomPart, ( model.divBottomPart | model.global )* )?
)
} |
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status) |
| Member of | |
| Contained by | msdescription: accMat acquisition condition custEvent decoNote foliation layout msItem origin provenance signatures summary support surrogates textcrit: rdg |
| May contain | analysis: w core: abbr add address author bibl biblScope cb choice corr date del editor expan foreign gap gb gloss hi lb measure measureGrp milestone name note orig pb pubPlace publisher ref reg respStmt sic term title unclear dictionaries: lang figures: figure header: availability edition funder idno principal msdescription: depth dim height msIdentifier width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl> |
| Example | <bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>.
</bibl> |
| Example | <bibl type="article" subtype="book_chapter" xml:id="carlin_2003">
<author>
<name>
<surname>Carlin</surname>
(<forename>Claire</forename>)</name>
</author>,
<title level="a">The Staging of Impotence : France’s last
congrès</title> dans
<bibl type="monogr">
<title level="m">Theatrum mundi : studies in honor of Ronald W.
Tobin</title>, éd.
<editor>
<name>
<forename>Claire</forename>
<surname>Carlin</surname>
</name>
</editor> et
<editor>
<name>
<forename>Kathleen</forename>
<surname>Wine</surname>
</name>
</editor>,
<pubPlace>Charlottesville, Va.</pubPlace>,
<publisher>Rookwood Press</publisher>,
<date when="2003">2003</date>.
</bibl>
</bibl> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.highlighted"/>
<classRef key="model.pPart.data"/>
<classRef key="model.pPart.edit"/>
<classRef key="model.segLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.biblPart"/>
<classRef key="model.global"/>
</alternate>
</content>
|
| Schema Declaration |
element bibl
{
att.global.attributes,
att.declarable.attributes,
att.typed.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
text
| model.gLike
| model.highlighted
| model.pPart.data
| model.pPart.edit
| model.segLike
| model.ptrLike
| model.biblPart
| model.global
)*
} |
| <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to) |
| Member of | |
| Contained by | |
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff<biblScope>.It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint. |
| Example | <biblScope>pp 12–34</biblScope>
<biblScope unit="page" from="12" to="34"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
|
| Schema Declaration |
element biblScope
{
att.global.attributes,
att.citing.attributes,
macro.phraseSeq
} |
| <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status) |
| Member of | |
| Contained by | msdescription: accMat acquisition condition custEvent decoNote foliation layout msItem origin provenance signatures summary support surrogates textcrit: rdg |
| May contain | |
| Example | <biblStruct>
<monogr>
<author>Blain, Virginia</author>
<author>Clements, Patricia</author>
<author>Grundy, Isobel</author>
<title>The Feminist Companion to Literature in English: women writers from the middle ages
to the present</title>
<edition>first edition</edition>
<imprint>
<publisher>Yale University Press</publisher>
<pubPlace>New Haven and London</pubPlace>
<date>1990</date>
</imprint>
</monogr>
</biblStruct> |
| Content model |
<content>
<sequence>
<elementRef key="analytic" minOccurs="0"
maxOccurs="unbounded"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="monogr"/>
<elementRef key="series" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.noteLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="relatedItem"/>
<elementRef key="citedRange"/>
</alternate>
</sequence>
</content>
|
| Schema Declaration |
element biblStruct
{
att.global.attributes,
att.declarable.attributes,
att.typed.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
analytic*,
( monogr, series* )+,
( model.noteLike | model.ptrLike | relatedItem | citedRange )*
)
} |
| <birth> contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description] | |||||||||||
| Module | namesdates — Formal declaration and Reference Pages | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLikeatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.naming (@role) (att.canonical (@ref))
| ||||||||||
| Member of | |||||||||||
| Contained by | namesdates: person | ||||||||||
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app | ||||||||||
| Example | <birth>Before 1920, Midlands region.</birth> | ||||||||||
| Example | <birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>,
early in the morning of <date>10 Dec 1960</date>
</birth> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
| ||||||||||
| Schema Declaration |
element birth
{
att.global.attributes,
att.editLike.attributes,
att.datable.attributes,
att.dimensions.attributes,
att.naming.attributes,
attribute type { text }?,
macro.phraseSeq
} | ||||||||||
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | textstructure: text |
| May contain | dictionaries: entry msdescription: msDesc namesdates: listEvent listOrg listPerson listPlace textcrit: app transcr: addSpan damageSpan delSpan fw listTranspose metamark space |
| Example | <body>
<l>Nu scylun hergan hefaenricaes uard</l>
<l>metudæs maecti end his modgidanc</l>
<l>uerc uuldurfadur sue he uundra gihuaes</l>
<l>eci dryctin or astelidæ</l>
<l>he aerist scop aelda barnum</l>
<l>heben til hrofe haleg scepen.</l>
<l>tha middungeard moncynnæs uard</l>
<l>eci dryctin æfter tiadæ</l>
<l>firum foldu frea allmectig</l>
<trailer>primo cantauit Cædmon istud carmen.</trailer>
</body> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<classRef key="model.divTop"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divTop"/>
</alternate>
</sequence>
<sequence minOccurs="0">
<classRef key="model.divGenLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.common"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0">
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
</alternate>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
|
| Schema Declaration |
element body
{
att.global.attributes,
(
model.global*,
( model.divTop, ( model.global | model.divTop )* )?,
( model.divGenLike, ( model.global | model.divGenLike )* )?,
(
( model.divLike, ( model.global | model.divGenLike )* )+
| ( model.div1Like, ( model.global | model.divGenLike )* )+
| (
( model.common, model.global* )+,
(
( model.divLike, ( model.global | model.divGenLike )* )+
| ( model.div1Like, ( model.global | model.divGenLike )* )+
)?
)
),
( model.divBottom, model.global* )*
)
} |
| <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration] | |
| Module | header — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | header: category |
| May contain | dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait transcr: subst |
| Example | <catDesc>Prose reportage</catDesc> |
| Example | <catDesc>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc>
</catDesc> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.catDescPart"/>
</alternate>
</content>
|
| Schema Declaration |
element catDesc
{
att.global.attributes,
( text | model.limitedPhrase | model.catDescPart )*
} |
| <category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | |
| Example | <category xml:id="b1">
<catDesc>Prose reportage</catDesc>
</category> |
| Example | <category xml:id="b2">
<catDesc>Prose </catDesc>
<category xml:id="b11">
<catDesc>journalism</catDesc>
</category>
<category xml:id="b12">
<catDesc>fiction</catDesc>
</category>
</category> |
| Example | <category xml:id="LIT">
<catDesc xml:lang="pl">literatura piękna</catDesc>
<catDesc xml:lang="en">fiction</catDesc>
<category xml:id="LPROSE">
<catDesc xml:lang="pl">proza</catDesc>
<catDesc xml:lang="en">prose</catDesc>
</category>
<category xml:id="LPOETRY">
<catDesc xml:lang="pl">poezja</catDesc>
<catDesc xml:lang="en">poetry</catDesc>
</category>
<category xml:id="LDRAMA">
<catDesc xml:lang="pl">dramat</catDesc>
<catDesc xml:lang="en">drama</catDesc>
</category>
</category> |
| Content model |
<content>
<sequence>
<alternate>
<elementRef key="catDesc" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.descLike"/>
<classRef key="model.glossLike"/>
</alternate>
</alternate>
<elementRef key="category" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
|
| Schema Declaration |
element category
{
att.global.attributes,
( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* )
} |
| <cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.10.3. Milestone Elements] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.spanning (@spanTo) att.breaking (@break) |
| Member of | |
| Contained by | analysis: w core: abbr add addrLine address author bibl biblScope corr date del editor expan foreign gloss head hi imprint item label list listBibl measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material msItem objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset org orgName persName person placeName region roleName settlement surname textcrit: rdg |
| May contain | Empty element |
| Note | On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb> element is placed at the head of the column to which it refers. |
| Example | Markup of an early English dictionary printed in two columns: <pb/>
<cb n="1"/>
<entryFree>
<form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
<sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
sinks into the Ground, to find out and disappoint the Enemies Mines,
or to prepare one</sense>.
</entryFree>
<entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
<sense>lie groveling</sense>.</entryFree>
<!-- remainder of column -->
<cb n="2"/>
<entryFree>
<form>Wey</form>, <sense>the greatest Measure for dry Things,
containing five Chaldron</sense>.
</entryFree>
<entryFree>
<form>Whale</form>, <sense>the greatest of
Sea-Fishes</sense>.
</entryFree> |
| Content model |
<content>
</content>
|
| Schema Declaration |
element cb
{
att.global.attributes,
att.typed.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
} |
| <change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions] | |||||||
| Module | header — Formal declaration and Reference Pages | ||||||
| Attributes | Attributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
| ||||||
| Contained by | header: listChange revisionDesc msdescription: recordHist | ||||||
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig p pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app | ||||||
| Note | The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented. | ||||||
| Example | <titleStmt>
<title> ... </title>
<editor xml:id="LDB">Lou Burnard</editor>
<respStmt xml:id="BZ">
<resp>copy editing</resp>
<name>Brett Zamir</name>
</respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
<change who="#BZ" when="2008-02-02" status="public">Finished chapter 23</change>
<change who="#BZ" when="2008-01-02" status="draft">Finished chapter 2</change>
<change n="P2.2" when="1991-12-21" who="#LDB">Added examples to section 3</change>
<change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc> | ||||||
| Example | <profileDesc>
<creation>
<listChange>
<change xml:id="DRAFT1">First draft in pencil</change>
<change xml:id="DRAFT2" notBefore="1880-12-09">First revision, mostly
using green ink</change>
<change xml:id="DRAFT3" notBefore="1881-02-13">Final corrections as
supplied to printer.</change>
</listChange>
</creation>
</profileDesc> | ||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
| ||||||
| Schema Declaration |
element change
{
att.ascribed.attributes,
att.datable.attributes,
att.docStatus.attributes,
att.global.attributes,
att.typed.attributes,
attribute target { list { + } }?,
macro.specialPara
} | ||||||
| <choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes] | |
| Module | core — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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 | analysis: w core: abbr add addrLine author bibl biblScope choice corr date del desc editor expan foreign gloss head hi item label measure name note orig p pubPlace publisher q quote ref reg resp sic term title unclear msdescription: accMat acquisition condition custEvent decoNote foliation layout material objectType origDate origPlace origin provenance signatures stamp summary support surrogates namesdates: addName affiliation age birth bloc country death education faith forename geogFeat geogName nationality occupation offset orgName persName placeName region roleName settlement surname textcrit: rdg |
| May contain | |
| Note | Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.Note also that <choice> elements may self-nest. Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred. |
| Example | An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows. <p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
<sic>1724</sic>
<corr>1728</corr>
</choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
<orig>favour</orig>
<reg>favor</reg>
</choice>.</p> |
| Content model |
<content>
<alternate minOccurs="2"
maxOccurs="unbounded">
<classRef key="model.choicePart"/>
<elementRef key="choice"/>
</alternate>
</content>
|
| Schema Declaration |
element choice { att.global.attributes, ( model.choicePart | choice )+ } |
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (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: encodingDesc |
| May contain | header: taxonomy |
| Example | <classDecl>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
<!-- ... -->
<textClass>
<keywords scheme="#LCSH">
<term>Political science</term>
<term>United States -- Politics and government —
Revolution, 1775-1783</term>
</keywords>
</textClass> |
| Content model |
<content>
<elementRef key="taxonomy" minOccurs="1"
maxOccurs="unbounded"/>
</content>
|
| Schema Declaration |
element classDecl { att.global.attributes, taxonomy+ } |
| <closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions] | |
| Module | textstructure — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.written (@hand) |
| Member of | |
| Contained by | |
| May contain | analysis: w core: abbr add address cb choice corr date del expan foreign gap gb gloss graphic hi lb measure measureGrp milestone name note orig pb ref reg sic term title unclear dictionaries: lang figures: figure header: idno msdescription: depth dim dimensions height locus locusGrp material objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| Example | <div type="letter">
<p> perhaps you will favour me with a sight of it when convenient.</p>
<closer>
<salute>I remain, &c. &c.</salute>
<signed>H. Colburn</signed>
</closer>
</div> |
| Example | <div type="chapter">
<p>
<!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>
<closer>
<dateline>
<name type="place">Trieste-Zürich-Paris,</name>
<date>1914–1921</date>
</dateline>
</closer>
</div> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="signed"/>
<elementRef key="dateline"/>
<elementRef key="salute"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
|
| Schema Declaration |
element closer
{
att.global.attributes,
att.written.attributes,
(
text
| model.gLike
| signed
| dateline
| salute
| model.phrase
| model.global
)*
} |
| <collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. The Manuscript Identifier] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role) (att.canonical (@ref)) att.typed (@type) |
| Contained by | msdescription: altIdentifier msIdentifier |
| May contain | Empty element |
| Example | <msIdentifier>
<country>USA</country>
<region>California</region>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<collection>Ellesmere</collection>
<idno>El 26 C 9</idno>
<msName>The Ellesmere Chaucer</msName>
</msIdentifier> |
| Content model |
<content>
<macroRef key="macro.xtext"/>
</content>
|
| Schema Declaration |
element collection
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
macro.xtext
} |
| <condition> contains a description of the physical condition of the manuscript. [10.7.1.5. Condition] | |
| Module | msdescription — Formal declaration and Reference Pages |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style)) (att.global.linking (@corresp)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) |
| Contained by | msdescription: sealDesc supportDesc |
| May contain | analysis: w core: abbr add address bibl biblStruct cb choice corr date del desc expan foreign gap gb gloss graphic hi label lb list listBibl measure measureGrp milestone name note orig p pb q quote ref reg sic term title unclear dictionaries: lang header: idno msdescription: depth dim dimensions height locus locusGrp material msDesc objectType origDate origPlace signatures stamp width namesdates: addName affiliation bloc country forename geo geogFeat geogName listEvent listOrg listPerson listPlace location offset orgName persName placeName region roleName settlement state surname trait textcrit: app |
| Example | <condition>
<p>There are lacunae in three places in this
manuscript. After 14v two
leaves has been cut out and narrow strips leaves remains in the spine. After
68v one gathering is missing and after 101v at least one gathering of 8 leaves
has been lost. </p>
<p>Several leaves are damaged with tears or holes or have a
irregular shape. Some of the damages do not allow the lines to be of full
length and they are apparently older than the script. There are tears on fol.
2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,
37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,
74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98
the corner has been torn off. Several leaves are in a bad condition due to
moist and wear, and have become dark, bleached or
wrinkled. </p>
<p>The script has been
touched up in the 17th century with black ink. The touching up on the following
fols. was done by
<name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An
AM-note says according to the lawman
<name>Sigurður Björnsson</name> that the rest of the
touching up was done by himself and another lawman
<name>Sigurður Jónsson</name>.
<name>Sigurður Björnsson</name> did the touching up
on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
<name>Sigurður Jónsson</name> did the rest of the
touching up in the section 36r-59r containing
<title>Bretasögur</title>
</p>
</condition> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
|
| Schema Declaration |
element condition { att.global.attributes, macro.specialPara } |