Element Set

The following list includes all the elements that are valid according to the Casebooks schema, including a number that are not currently used (but may be one day) or that are used only in web page or project documentation files, or in the transcription of ancillary materials. The status of all such elements is clearly stated in the relevant Note section.

Elements

<ab>

<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.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.declaring (@decls) att.fragmentable (@part)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<abbr>

<abbr> (abbreviation) contains an abbreviation, and nests together with <expan> (containing the expanded version) in a <choice> element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.responsibility (@cert, @resp) (att.source (@source))
Example
<p>… here the number endeth on Agnes, <choice><abbr>therf.</abbr><expan>therfore</expan></choice> Agnes shall die first</p>
NoteThis element is not used in transcriptions of Casebooks entries, only in those of the more discursive guides to astrology or similar texts.
<abbr> always precedes <expan> within <choice>.

<add>

<add> (addition) indicates added text, with @place recording its position relative to the text to which it has been added.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) ) att.typed (@type)
@placegives the position of the inserted text. Permitted values: "supralinear" (above the line), "infralinear" (below the line), "inline" (neither higher nor lower than the surrounding text but obviously added later), "lineBeginning" (at the beginning of the line), "lineEnd" (at the end of the line), "marginLeft" (in the left margin), "marginRight" (in the right margin), "over" (physically overwriting an earlier text string), "pageTop (at the top of the page), and "pageBottom" (at the bottom of the page).
Status Required
Legal values are:
inlinesupralinearinfralinearinterlinearovermarginRightmarginLeftlineBeginninglineEndpageBottompageTop
Example
<p>… h. 10. <add place="supralinear">30</add> ant m …</p>
Note<add> may nest in <add>, in which case the @place value of the nested <add> refers to where it appears relative to the inserted text it nests in. For instance, a supralinear addition contained within an addition that was added infralinearly to the main text should have a @place value of "supralinear", even if the second insertion itself remains infralinear relative to the main text.
"lineBeginning" "lineEnd", "marginLeft" and "marginRight" should be taken as relative to the position of the entry as a whole. The ‘right margin’ or ‘line end’ of an entry in the left-hand column and the ‘left margin’ or ‘line beginning’ of an entry in the right-hand column are all in the middle of the page as a whole.
The distinctions between "lineBeginning" and "marginLeft", or between "lineEnd" and "marginRight" are somewhat nebulous and really not of any great significance, but generally speaking a word or two tacked on at the beginning or end of a line should be treated as "lineBeginning" or "lineEnd", while a more substantial added text string which itself runs to more than one line, or one placed at a significant distance from the beginning or end of the line, should be treated as "marginLeft" or "marginRight".

<addName>

<addName> (additional name) is used for soubriquets or alternative forms of names that do not obviously fit into any other category.
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type)
Example
<persName evidence="external"><roleName>Sultan</roleName> <forename>Mehmed</forename> <genName>III</genName> <addName>The Grand Turk</addName></persName>
In this example (CASE5121), the person in question is in fact referred to in the original document only as ‘the Turk’, but external evidence shows him to be Sultan Mehmed III, popularly known (at least in England) as ‘The Grand Turk’.
Example
<persName> <forename>Alice</forename> <addName>Deaf Alice</addName> </persName>
In this example (CASE14948), the person in question (a suspected witch) is referred to in the source document merely as ‘Deaf Alice’. It seems reasonable to suppose that ‘Alice’ is indeed her forename, but ‘Deaf’, on its own, can hardly be considered any definable part of her name, so ‘Alice’ is encoded as her forename and ‘Deaf Alice’ as her soubriquet.
NoteThis element is used only rarely in Casebooks transcriptions but is useful for anomalous situations of this sort where none of the other children of <persName> seems up to the job.

<addSpan/>

<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>).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) ) att.typed (@type) att.spanning (@spanTo)
@placePlacement
Status Required
Suggested values include:
inlinesupralinearinfralinearinterlinearovermarginRightmarginLeftlineBeginninglineEndpageBottompageTop
NoteThis element is not used in the transcription of Casebooks entries. However, it may prove useful for the more discursive astrology guides and similar texts.

<affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<age>

<age> (age) records a participant’s age as stated in the entry.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) att.dimensions (@quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@cert, @resp) att.source (@source)
@unitgives the unit in which the age is being measured. Permitted values: "days", "weeks", "months", "years".
Status Optional
Legal values are:
daysweeksmonthsyears
@valuemay be any numerical value, expressed as an integer in Arabic numerals.
Status Optional
Example
<age value="12">12</age>
Example
<age value="3" unit="months">quarter of a year</age>
Example
<age value="30" unit="months">2 and a half years</age>
NoteThe default value for @unit is "years" so this does not need to be entered by the encoder.

<altIdentifier>

<altIdentifier> (alternative identifier) denotes the number assigned by the project to the volume in which the entry occurs, as distinct from that volume’s more canonical (but less logical) Ashmole MS number.
Attributesatt.typed (@type)
Example
<altIdentifier type="fn_number"><idno n="Forman004">Forman, vol 4</idno></altIdentifier>
NoteThis element is generated automatically before transcription begins and is expressed as an entity in <fileDesc>, e.g &Forman004; for Forman Volume 4.

<anchor/>

<anchor/> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type)
NoteThis element is not used in the transcription of Casebooks entries, though it may prove useful for some of the ancillary texts.

<app>

<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.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@typeclassifies the variation contained in this element according to some convenient typology.
Status Optional
@fromidentifies the beginning of the lemma in the base text.
Status Optional
NoteThis attribute should be used when either the double-end point method of apparatus markup, or the location-referenced method with a URL rather than canonical reference, are used.
@toidentifies the endpoint of the lemma in the base text.
Status Optional
NoteThis attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not embedded in-line in the base-text.
@loc(location) indicates the location of the variation, when the location-referenced method of apparatus markup is used.
Status Optional
NoteThis attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage to which the variation applies.
NoteThis element is not used in transcriptions of Casebooks entries, only in those of the more discursive guides to astrology or similar texts.

<argument>

<argument> contains a formal list or prose description of the topics addressed by a subdivision of a text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<author>

<author> defines the author(s) of a document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
NoteThis element is not used in transcriptions of Casebooks entries, only in those of ancillary texts such as the astrology guides.

<bibl>

<bibl> (bibliographic citation) is used only (for Casebooks purposes) to define the physical location of an entry. The @type value "positionOnPage" gives the quadrant in which an entry begins or the quadrant(s) it occupies, as explained in the Guidelines.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declarableatt.sortable (@sortKey) att.docStatus
@typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Sample values include:
positionOnPage
Example
<bibl type="positionOnPage">1</bibl>
(meaning either that the entry occupies the upper left hand quadrant of the page or that it begins in that quadrant and proceeds into the lower left hand quadrant).
Example
<bibl type="positionOnPage">3B</bibl>
(meaning that this is the second entry in the upper right hand quadrant).
Example
<bibl type="positionOnPage">4, 2</bibl>
(meaning that the entry begins in the lower right hand quadrant and continues in the lower left hand quadrant).
Example
<bibl type="positionOnPage">f. 136v/Q4, f. 137r/Q1</bibl>
(meaning that the entry begins in the lower right hand quadrant of f. 136v and continues in the upper left hand quadrant of f. 137r).
NoteOnly the quadrant the entry begins in need be specified if it proceeds logically from that quadrant into another (i.e. from Q1 to Q2 or from Q3 to Q4) and does not cross any column or page breaks.

<birth>

<birth> (birth) encodes information drawn from the entry in question about a person’s birth, such as its date, time and/or place.
Attributesatt.global (@xml:id, @n, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.editLike (@evidence) att.responsibility (@cert, @resp) att.source (@source)
Example
<birth><date when="1583-10-27" n="Sunday"/><time when="18:00:00"/></birth>
Example
<birth><date when="1604-04-17" n="Tuesday"/><time notBefore="18:00:00"/><placeName sameAs="#address1"/></birth>
NoteWhere the date of birth is stated in plain terms in an untranscribed part of the entry, <date> takes the @evidence value "internal".
Especially in Napier‘s records, dates of birth are quite often given in highly elliptical terms such as
‘24 y the last satterday in Lent’
, meaning that the person in question was born on the last Saturday in Lent 24 years before the year of the consultation. The (rather complex) procedure for interpreting this sort of formulation is explained on the ‘Extrapolating dates’ page of the project wiki. If this mechanism is invoked, <date> should take the @evidence value "extrapolated".

<body>

<body> (text body) for Casebooks purposes, nests directly within <text> and contains the transcribed text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declaring (@decls)
NoteThis element (but not, obviously, its content) is generated automatically before transcription begins.

<byline>

<byline> contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not used in Casebooks transcriptions. It does occur in some of the files used to generate the website pages but editors need not concern themselves with it.

<catDesc>

<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.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
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>
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<category>

<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
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>
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<catRef/>

<catRef/> (category reference) points, by means of its @target value, at the category of text in question.
Attributesatt.responsibility (@cert, @resp) (att.source (@source)) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@targetdefines the type of document being encoded using one of the categories explained in Types of text. Permitted values: "#caseNotes", "#decumbiture", "#diary", "#election", "#horary", "#interrogation", "#nativity", "#practice", "#revolutions".
Status Required
Legal values are:
#caseNotes#decumbiture#diary#election#horary#interrogation#nativity#practice#revolutions
@schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
Status Optional
Example
<catRef target="#horary"/>
NoteThe vast majority of Casebooks entries are horary in nature so this is the default value applied to @target at the time of the file’s creation. Transcribers need only concern themselves with it if this needs to be changed to one of the other values.
Only one <catRef/> element is permitted within <textClass> at the time of transcription (further parent categories may be added during the build process but transcribers need not concern themselves with these).
<catRef/> may also take an optional @cert value of "high", "medium" or "low" in the very rare instances in which there is some doubt about the categorisation.

<cb/>

<cb/> (column break) marks the beginning of a new column in an entry that occupies more than one column. It takes the @xml:id value "colA" or "colB" and the @n value "a" or "b".
Attributesatt.typed (@type) att.edition (@edRef) att.spanning (@spanTo) att.breaking (@break) att.global (@xml:lang, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
@n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Example
<div><p>… William Garton of 31 yers 1597 the 15 Ian&rsquo; Saturday An&flourish; m&flourish; 30 p 9 Diz</p> </div> <div><cb xml:id="colB" n="b"/> <p><lb/>William Garton &slash; in bishops <lb/>gat strete&slash;</p> </div>
(CASE1076)
NoteIf the column break occurs outside the transcribed portion of the text (for instance, if the question and chart are in column A but the judgment in column B), <cb/> should be placed outside <div>. If, however, as in the example given here, the column break occurs within the transcribed portion, it should nest in <div>.
Especially in the case of Napier’s records, it is by no means unusual for an entry to cross a column break in counter-intuitive fashion, e.g. from the right hand column (column B) into the left hand column (column A).
Where a page, or part of it, has been divided horizontally rather than vertically, so that an entry proceeds seamlessly, and at several points, from Q1 to Q3 or from Q2 to Q4, <cb/> is not needed.
In the extremely rare event of text moving on to the column more than once within a given file, e.g. an entry begins in column A, continues in column B, reverts to column A and then moves back into column B a second time, the two @xml:id values should be distinguished by appending a hyphen and a numeral to the normal value, e.g. colA-1, colA-2, but the two @n values will be identical. The same applies in the even rarer event of an entry covering more than one page and having a column break on each.

<cb:consultant/>

<cb:consultant/> (consultant) points, by means of the @ref attribute, to the @xml:id value of the person conducting the consultation.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.participants (@reason, @present, @ref) (att.casebooks.participants.certainty (@evidence) (att.casebooks.minimal.responsibility (@cert, @resp)) )

<cb:consultation>

<cb:consultation> (consultation) contains information about the consultation and the roles of the participants.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Example
<cb:consultation> <cb:consultant ref="#sforman"/> <cb:practice name="forman"/> <cb:querent ref="#cp" cert="low"/> <cb:subject ref="#cp" present="yes"/> <cb:topic key="unspecifiedMedical"><person sameAs="#cp"/></cb:topic> <cb:judgment/> <cb:treatment/> </cb:consultation>
NoteThis element is automatically generated before transcription begins.

<cb:info/>

<cb:info/> (additional information) records the presence of information about events relevant to the case, financial transactions associated with it, the condition of the patient’s urine, or Napier’s reliance on angelic advice in formulating a diagnosis or prognosis.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )
@typestates what the information is about (or, in the case of angels, its source). Permitted values: "angel", "event", "financial" or "urine".
Status Required
Legal values are:
angeleventfinancialurine
@subtypeapplies only where the @type value is "event" or "angel". For events, it records whether the event falls into the "previousConsultation" or "subsequentEvent" category, or takes the value "unclear" if it is not apparent whether the event in question is prior or subsequent to the consultation. For angels, it records the angel’s name if known (currently permitted values are "Aladiah", "Asariel", "Gabriel", "Michael", "Raphael", "Uriel", or "Unspecified" if no name is given).
Status Optional
Legal values are:
previousConsultationsubsequentEventunclearAladiahAsarielGabrielMichaelRaphaelUrielUnspecified
NoteAs explained in more detail in the Guidelines, the names of angels are normally given in the record in truncated form, for instance ‘’ for Raphael or ‘Mich.’ for Michael.
<cb:info type="event" /> should be used for events prior to the consultation only if these concern previous consultations conducted by the same practitioner (‘she was here last weddensday’ or the like), or the effects of treatments given at previous consultations. Reports of other past events such as the patient’s father’s having died last week, the patient’s having been jilted by her or his sweetheart, the patient’s having been treated by another practitioner, or details about previous addresses, occupations, etc., should be considered part of the judgment.
<cb:info type="event" subtype="subsequentEvent" /> applies more generally to any subsequent event relevant to the case (typically the patient’s recovery, deterioration or death, or the outcome of a pregnancy), or to prior events that the practitioner only found out about later (for instance ‘shee proved with child’, which suggests that the patient already was pregnant at the time of the consultation but the practitioner was unaware of it). As a rule of thumb, if it seems reasonably clear that a comment was added some time after the writing of the original record (sometimes months or even years later), it counts as a subsequentEvent. For obvious reasons, after-the-fact reports of this sort normally appear at the foot of the entry, inside the chart, or as marginal or interlinear additions.
<cb:info type="financial" /> includes payments in kind (e.g. ‘he sent me a haunch of venyson’) or the practitioner’s decision not to charge for his services.
<cb:info type="urine" /> records the presence of information suggesting that the practitioner has used analysis or observation of the subject’s urine as a diagnostic tool. This is distinct (though not always unequivocally so) from comments about the patient’s urine that appear to represent symptom description rather than diagnostic judgment. It is also distinct from (though not incompatible with) mere statements that urine was brought or sent, which should be recorded in <cb:item>.

<cb:item/>

<cb:item/> (item) records the presence of explicit information about items brought or sent to the consultation. Note that this does not include inferences, such as taking the presence of a urine description as an indication that urine was brought or sent, or a statement that a question was ‘sent’ as an indication that a letter was involved. It is only used to record the presence of explicit statements such as ‘he sent a letter’ or ‘shee brought her vrine’.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )
@present
Status Optional
Legal values are:
explicitlyNo
@typedefines the type of item in question. Permitted values: "blood", "letter", "token" (some token of trust brought or sent by the querent), "urine".
Status Required
Legal values are:
bloodlettertokenurine

<cb:judgment/>

<cb:judgment/> (judgment) records the presence of a judgment in the record.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )

<cb:location/>

<cb:location/> (location) records, where possible, where the practitioner was at the time of the consultation, either in absolute terms or relative to the querent.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.canonical (@key)
@typetakes one of the values "neutralGround", "practitionerReceivesMessage", "practitionerVisitsQuerent", "querentVisitsPractitioner" or "unknown". By far the commonest @type values are practitionerVisitsQuerent and querentVisitsPractitioner, which are hopefully self-explanatory, except that "practitionerVisitsQuerent" also covers instances where the practitioner visits a subject who is not, or not necessarily, the same person or in the same place as the querent. "neutralGround" indicates that the encounter took place somewhere that was neither the querent’s nor the practitioner’s current place of residence. "practitionerReceivesMessage", which should only be used in conjunction with @ref, caters for the extremely rare instances in which there is concrete evidence of where the practitioner was when he received a message, such as CASE12933, in which Napier notes that the bringer of the message ‘met me then at Staunton’. "unknown", which should also be used only in conjunction with @ref, applies in the equally rare instances in which the place of the consultation is known, but it is not clear whether this was either the practitioner’s or the querent’s current place of residence at the time (for instance an inn that, so far as the record reveals, may have been either where the querent was staying, where the practitioner was staying, or a place where neither of them was staying but where they agreed, or happened, to meet).
Status Required
Legal values are:
neutralGroundpractitionerReceivesMessagepractitionerVisitsQuerentquerentVisitsPractitionerunknown
@ref(reference) points to the <rs> or <placeName> recording the location of the consultation, in the rare cases in which a location is specified.
Status Optional

<cb:messenger/>

<cb:messenger/> (messenger) points, where relevant, to the person acting as messenger from querent to practitioner, using the @ref value.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.participants (@reason, @present, @ref) (att.casebooks.participants.certainty (@evidence) (att.casebooks.minimal.responsibility (@cert, @resp)) )

<cb:object/>

<cb:object/> (object) points to any person(s) who is/are not among the principal participant(s) but is/are highly relevant to the case, e.g. prospective spouses or suspected thieves or witches.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.participants.certainty (@evidence) (att.casebooks.minimal.responsibility (@cert, @resp)) att.casebooks.linking (@exclude, @xml:id)
@ref(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Status Required
NoteDo not use @xml:id or @exclude as they are not yet supported.

<cb:practice/>

<cb:practice/> (practice) records whose practice it is, by means of the @name attribute.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )
@namerecords the practice name. Permitted values: "forman" and "napier".
Status Required
Legal values are:
formannapier
NoteIn the vast majority of cases, entries in Forman’s casebooks relate to Forman’s practice and entries in Napier’s casebooks relate to Napier’s practice, even if the consultant is someone else (for instance Gerence James acting as Napier’s locum). However, there are a very few examples of records in Forman’s casebooks referring to Napier’s practice or vice versa. This element is generated automatically at the time of the file’s creation and except in these very few cases does not need to be modified by the editors.

<cb:querent/>

<cb:querent/> (querent) points to the person(s) asking the question by means of the @ref attribute.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.linking (@exclude, @xml:id) att.casebooks.participants (@reason, @present, @ref) att.casebooks.minimal.responsibility (@cert, @resp)
@evidenceexplains the grounds for inferring or conjecturing the person in question is the querent. Permitted values: "internal" (there is an explicit statement, however vague, that this person is the querent), "external" (the fact that this person is the querent can deduced from some external source such as another case), "inferred" (we infer, on some systematic principle (usually the fact that the subject is under ten), that the querent is not the same person as the subject but we have no clear evidence about who he/she is) and "conjecture" (the editor has grounds for supposing that the querent is not the same person as the subject, for instance the subject appears to be insane, or the general layout and tenor of the entry suggests that the querent is in fact the practitioner, but no concrete evidence or systematic inference is possible).
Status Optional
Legal values are:
internalexternalinferredconjecture
NoteSee the Guidelines for advice about what to do in the fairly rare event of there being two or more mutually exclusive candidates for the role of querent.

<cb:questionNumber/>

<cb:questionNumber/> (question number) records, using the @n value, that a question is explicitly noted (either in the transcribed or the untranscribed part of the entry) as being the querent’s first, second, third etc. question.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributes
@nany integer, expressed as an Arabic numeral.
Status Required
Note<cb:questionNumber> does not mean that this is in fact the querent’s first, second, third etc. question, merely that it is recorded as such in the source.

<cb:recipe/>

<cb:recipe/> (recipe) records the presence of a medical recipe in the entry.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )

<cb:subject/>

<cb:subject/> (subject) points, by means of the @ref attribute, to the participant about whom or in whose interests the question is being asked.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.participants (@reason, @present, @ref) (att.casebooks.participants.certainty (@evidence) (att.casebooks.minimal.responsibility (@cert, @resp)) ) att.casebooks.linking (@exclude, @xml:id)
@consentindicates that there is an explicit statement that the consultation took place either with or without the subject’s (or subjects’) consent. Permitted values: yes, no and explicitlyUnclear.
Status Optional
Legal values are:
yesnoexplicitlyUnclear
@knowledgeindicates that there is an explicit statement that the consultation took place either with or without the subject’s (or subjects’) knowledge. Permitted values: yes, no.
Status Optional
Legal values are:
yesno
NoteIn a very few cases, the practitioner expresses some uncertainty as to whether the subject has given her/his consent or not, typically with a formula such as ‘credo sine consensu’. Here @consent takes the value explicitlyUnclear.
See the Guidelines for advice about what to do in the extremely rare event of there being two or more mutually exclusive candidates for the role of subject.

<cb:topic>

<cb:topic> (topic) defines the nature of the question being asked, using any of the terms recorded in the topics master list. Each <cb:topic> element must contain at least one <person>, <personGrp> and/or <org> element, pointing to the person or people being asked about, whether subject or object. If the nature of the query is not explicitly stated in the transcribed part of the document, an @evidence value should also be applied, as explained in more detail in the guidelines. If there are grounds for doubt about the nature of the question, a @cert value may also be applied. A single entry may feature any number of topics bar zero.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )
@keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Required
@xml:id(identifier)
Status Optional
@excludepoints to elements that are in exclusive alternation with the current element.
Status Optional
@reasonis used exclusively in cases where the @key value is "unknown", whether because the relevant information has been lost through illegible deletion or manuscript damage, because no information was given in the first place, or because the information is given in impenetrably cryptic terms. Permitted values: "deleted", "msDamage", "notGiven", "notUnderstood".
Status Optional
Legal values are:
deletedmsDamagenotGivennotUnderstood
Example
<cb:topic key="unspecifiedMedical" evidence="internal"><person sameAs="#js"/></cb:topic>
This is by a considerable margin the commonest type of topic to be found in Napier’s records. The @evidence value "internal" indicates that the problem is not specified in the transcribed part of the entry (the question) but the judgment makes it plain that the enquiry was of a medical nature. In Forman’s records, the commonest @key value of <cb:topic> is "diz", which effectively means the same thing, except that Forman usually does at least state in the question section that the enquiry is medical in nature, whereas Napier usually does not.
Example
<cb:topic key="nonDizDisease"><person sameAs="#am"/></cb:topic> <cb:topic key="witchcraft"><person sameAs="#am"/><person sameAs="#jw"/><person sameAs="#ds"/></cb:topic>
In this rather more complicated example (CASE11996), two different questions are being asked, and in one case the same question is being asked about three different people. The question states that Alice Mason (the subject) is ‘straingly handled’, indicating a medical problem not specified as ‘diz’ or ‘disease’, while Jane Warren and Dorothy Sumner (the objects) are suspected of bewitching her (so all three belong within the witchcraft topic). Since all this information is included in the question section, no @evidence value is required, as both topics are apparent from the transcribed text and users do not have to take our word for them.
NoteIf no judgment is given, or the judgment does not in itself indicate the nature of the enquiry, but the presence of a urine note and/or prescribed treatment, and/or the nature of the event information (e.g. ‘she recovered and did well’), strongly suggests that the question was of a medical nature, an @evidence value of "inferred" should be applied.
The querent should not be pointed to by a <person> element within <cb:topic> if he or she is not the same person as the subject.

<cb:treatment/>

<cb:treatment/> (treatment) indicates that the entry either records a particular treatment recommended or administered by the practitioner, or includes an explicit statement that no treatment was offered.
Namespacehttp://www.magicandmedicine.hps.cam.ac.uk/ns/1.0
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) )
NoteMentions of previous treatments administered by the practitioner, or the effects of such treatments, should be recorded as <cb:info type="event" />, not <cb:treatment>. Mentions of previous treatments administered by another practitioner should be regarded as part of the judgment.

<cell>

<cell> contains one cell of a table.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.tableDecoration (@role, @rows, @cols)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<change>

<change> documents significant stages in the creation, transcription, checking or processing of an electronic file.
Attributesatt.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatusatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type)
Example
<change when="2009-12-12">Data entered in Microsoft Excel spreadsheet by <name xml:id="rralley">Robert Ralley</name> as part of the Casebooks Pilot Project.</change> <change when="2010-07-05">XML file created by <name xml:id="mhawkins">Michael Hawkins</name> from Casebooks Pilot Project data.</change> <change when="2010-09-11">Transcribed by <name sameAs="#rralley">Robert Ralley</name>.</change> <change when="2010-09-16">Checked by <name xml:id="jyoung">John Young</name>.</change> <change when="2012-07-05">Facsimile coding added by <name sameAs="mhawkins">Michael Hawkins</name>.</change>
NoteChecking a file counts as a ‘change’ even if the checker has not in fact altered anything in it. The file itself may not have changed but its status has.

<choice>

<choice> contains the code for alternative renditions of the same text string, typically consisting of <orig>/<reg>, <sic>/<corr> or <abbr>/<expan>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<choice><orig>W<hi rend="overline">llm</hi></orig><reg>William</reg></choice>
Example
<p>… <choice><sic>mayed</sic><corr>maryed</corr></choice> 15 yeres …</p>
Note<choice> may nest within any child of <choice> if, for instance, it is necessary to provide a correction of an erroneous glyph or abbreviation before providing a regularisation of the corrected version.

<closer>

<closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<collection>

<collection> records the collection within which the source document is held. For Casebooks Project purposes, this is always ‘Ashmole Mss’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type)
Example
<msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 1r</idno> &Forman001; </msIdentifier>
NoteThis element is generated automatically before transcription begins.

<corr>

<corr> (correction) contains a corrected reading of what is considered to be an erroneous text string in the original.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
@typeis invoked if the original text should not be there. Permitted values: "noText" (there should never have been any text there in the first place), "delText" (the text should have been deleted).
Status Optional
Legal values are:
noTextdelText
Example
… her leg swelleth and hath an <choice><sic>issoe</sic><corr>issue</corr></choice> …
Example
… Ian Brown of <choice><sic>of</sic><corr type="noText"/></choice> Akely …
Example
<choice><orig><choice><sic>h</sic><corr>&SaturnSymbol;</corr></choice></orig><reg type="gloss">Saturday</reg></choice>
Note<corr> always follows <sic> (containing the original, erroneous text) within <choice>.
Where the erroneous text comprises part of a longer word or numeral, the <sic> and <corr> elements should contain the whole word or numeral, even if only one character requires correction.
The precise distinction between "delText" and "noText" hinges on the usually unanswerable question of whether the original author failed to spot his mistake or intended to delete it but forgot to. It is at best an educated guess and frankly not of very much importance.
Where the content of <sic> includes <lb/>, it is not necessary to repeat this in <corr> (and in any case not always clear where the line break would have occurred if the text had been correctly written).
Where the content of <corr> is a symbol or abbreviation that would otherwise be supplied with an expansion using <orig>/<reg>, it should not be expanded within <corr>. Instead, the entire <choice> string should nest within the <orig> element of a further <choice> string, with the regularisation of the corrected version appearing as the content of <reg> (see the third example above).

<country>

<country> (country) is used only within <msIdentifier> to state the country in which the source document is held.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Example
<country>UK</country>
NoteThis element is generated automatically before transcription begins.

<date>

<date> records a date or date range using ISO format (yyyy-mm-dd).
Attributesatt.typed (@type) att.global (@xml:id, @xml:lang, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @sameAs, @copyOf, @exclude) att.datable.custom (@when-custom) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@cert, @resp) att.source (@source)
@n(natural language expression) records the day of the week (where known), in natural language.
Status Optional
Legal values are:
MondayTuesdayWednesdayThursdayFridaySaturdaySunday
@whendefines a specific date.
Status Optional
@notBeforedefines the earliest possible date or beginning of a date range where this is not known precisely.
Status Optional
@notAfterdefines the latest possible date or end of a date range where this is not known precisely.
Status Optional
@fromdefines the beginning of a date range.
Status Optional
@todefines the end of a date range.
Status Optional
@notBefore-customdefines the earliest possible beginning of a temporal range where both date and time can be specified.
Status Optional
@notAfter-customdefines the latest possible end of a temporal range where both date and time can be specified.
Status Optional
@from-customdefines the beginning of a temporal range where both date and time can be specified.
Status Optional
@to-customdefines the end of a temporal range where both date and time can be specified.
Status Optional
@evidenceindicates the nature of the evidence supporting the date value.
Status Optional
Legal values are:
conjectureexternalextrapolatedinferredinternal
Example
<date when="1606-06-06" n="Friday"/>
Example
<date notBefore="1606-06-05" notAfter="1606-06-07"/>
Example
<date from="1605-01-12" to="1607-09-08"/>
Example
<date notBefore-custom="1604-03-07T18:05:00" notAfter-custom="1604-03-08T08:15:00"/>
This example indicates ‘some time between 6:05 pm on 7 March 1604 and 8:15 am on 8 March 1604’. This mechanism is typically used if it can be inferred that an entry was written after the last securely datable and timable entry before it and before the first one after it, but no date or time is given in the entry itself.
Example
<date when="1601-02-01" n="Sunday" xml:id="date1" exclude="#date2"/> <date when="1601-02-02" n="Monday" xml:id="date2" exclude="#date1"/>
This example means ‘either Sunday 1 or Monday 2 February 1601’.
NoteWhere two or more mutually exclusive dates are recorded for a given consultation or event, or (as happens more frequently) the date given in the entry is open to two (or more) interpretations, the alternatives should both or all be given, using the @xml:id and @exclude mechanism as illustrated in the last example above and explained in more detail in the Guidelines.
If <date> occurs within <birth>, <death> or <event>, an @n value should only be included if one is stated, correctly, in the original. If the source text gives a day of the week that is not compatible with the recorded date, it simply does not seem worth attempting to cater for all the possible causes of the error (is the day wrong, is the date wrong, is the year wrong, is the whole thing wrong?) and the date should simply be given as stated in the document, with no @n value.
<date> also appears within <publicationStmt> but is there generated automatically when the file is released online.

<dateline>

<dateline> contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<death>

<death> (death) encodes information drawn from the entry in question about a person’s death, such as its date, time and/or place.
Attributesatt.global (@xml:id, @n, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.editLike (@evidence) att.responsibility (@cert, @resp) att.source (@source)
Example
<death> <date notBefore="1604-09-15" notAfter="1605-09-17"/> </death>
Example
<death> <date when="1597-02-12" n="Saturday"/><time when="10:30:00"/><placeName sameAs="#address1"/> </death>
Example
<death><date notBefore="1599-10-01" notAfter="1599-10-31" precision="low" evidence="internal"/><placeName>the <lb/>spittell in southwork</placeName></death>
In this example, the untranscribed portion of the text (CASE4394) includes the comment ‘he fell Lame and died in the spittell in southwork 1599 about october’.
Note<placeName> should be included only in the very rare cases where the place of death is explicitly stated in the entry. It should not simply be assumed that if someone has been described as having fallen ill in a particular place, that is probably where he or she died.

<del>

<del> (deletion) marks deleted text with @type describing the type of deletion.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.transcriptional (@hand, @cause, @seq) att.editLike (@evidence) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@cert, @resp) att.source (@source)
@statuswith the value "erroneous" indicates that the deletion is itself a mistake, i.e. the text has been deleted but should not have been.
Status Optional
Legal values are:
erroneous
@typedescribes the type of deletion. Permitted values: "blockStrikethrough" (whole section struck through en bloc), "cancelled" (heavier deletion), "erased" (this text has been physically rubbed off of the page), "over" (this text string is overwritten by another), "strikethrough" (continuous horizontal line through a text string), "redactedBlockStrikethrough" (block strikethrough apparently indicating that the practitioner wished to suppress the entry rather than correct an error), and "redactedCancelled" (cancellation functioning as suppression rather than correction).
Status Required
Legal values are:
strikethroughblockStrikethroughcancellederasedoverredactedBlockStrikethroughredactedCancelled
Example
1 <del type="strikethrough">April</del> May 1601
Example
… of <subst><del type="over">6</del><add place="over">7</add></subst>0 yeres …
NoteText tagged <del type="over"> will always, by definition, be followed immediately by text tagged <add place="over">.
Where added text replaces deleted text, the two strings should nest in a <subst> element and the deleted text should be transcribed first. This applies even in cases where the caret mark or other insertion indicator appears, physically, before the <del>. If the added text has the @place value "over" and/or it replaces a character or characters that are only part of a word, number or other textual unit, it should follow the deleted text with no space in between the two elements. Otherwise, one space should be left between the <del> and <add> elements.
If <add> and <del> are co-extensive – i.e. the added text has been deleted in its entirety but the surrounding text is undeleted – <del> should nest directly within <add> rather than vice versa. However, <add> may nest within <del> if the insertion represents part of a larger text string that was subsequently deleted in its entirety.
If the content of <del> is a symbol or abbreviation that would otherwise be supplied with an expansion using <orig>/<reg>, or a mistake that would otherwise be supplied with a correction using <sic>/<corr>, the deleted should not be expanded or corrected.
<del> may also nest within <del> if it appears that some part of a text string had been deleted before the larger text string was.

<desc>

<desc> (description) contains a succinct prose description of whatever is documented by the element it nests in. For the purposes of transcribing Casebooks entries, this is invariably <trait>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.translatable (@versionDate) att.typed (@type)
Example
<trait type="regionalIdentity"><desc>Kentish man</desc></trait>
NoteThe content of <desc> should be based so far as possible on the original text but with modernised spelling and if necessary in English translation: thus the ‘Kentish man’ in the above example (CASE8592) is given in the original as ‘a Kintesh man’, while ‘a wallicus’ (CASE8781) becomes a ‘Welshman’.
This element is also used, in other contexts, in project documentation files and the master lists, but transcribers need not concern themselves with its usage there.

<district>

<district> contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<div>

<div> (text division) contains either the whole of a text or a subdivision of it.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (@type) att.declaring (@decls)
Example
<div><p>… William Garton of 31 yers 1597 the 15 Ian&flourish; Saturday An&flourish; m&flourish; 30 p 9 Diz</p> </div> <div><cb xml:id="colB" n="b"/> <p><lb/>William Garton &slash; in bishops <lb/>gat strete&slash;</p> </div>
NoteIf a column or page break occurs outside the transcribed portion of the text (for instance, if the question and chart are in column A but the judgment in column B), <cb/> should be placed outside <div>. If, however, as in the example given here, the column or page break occurs within the transcribed portion, it should nest in <div>.

<education>

<education> contains a description of the educational experience of a person.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<event>

<event> (event) records any significant event in a participant’s life other than birth, death or anything covered by <relation>. The currently available @type values are christening, baptism and burial, though others can be added should the need arise.
Attributesatt.sortable (@sortKey) att.global (@xml:id, @n, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.editLike (@evidence) att.responsibility (@cert, @resp) att.source (@source)
@typestates what type of event it is. Permitted values: "baptism", "burial" or "christening".
Status Required
Legal values are:
baptismburialchristening
Example
<event type="baptism"><p>Baptised on <date when="1587-01-01" sameAs="#date1">1 January 1587</date> at <time when="11:00:00" sameAs="#time1">11 am</time> at <placeName sameAs="#address1">St Pancras&rsquo; Church</placeName>.</p></event>

<ex>

<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<expan>

<expan> (expansion) contains an expansion, and nests together with <abbr> (containing the abbreviated version) in a <choice> element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
Example
<p>… here the number endeth on Agnes, <choice><abbr>therf.</abbr><expan>therfore</expan></choice> Agnes shall die first</p>
NoteThis element is not used in transcriptions of Casebooks entries, only in those of the more discursive guides to astrology or similar texts.
<expan> always follows <abbr> within <choice>.

<facsimile>

<facsimile> contains the element <graphic>, which in turn contains a pointer to an image (or pointers to images) of the source document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declaring (@decls)
NoteThis element is entered by the technical director when images become available from the Bodleian Library. If it does not already exist when transcription begins, editors should not add it since it will be automatically added by the technical director when the files are cleared for publication.
When images are already available from the Bodleian Library before transcription begins, the volume will be foliated and that information will be used to create the template files for use by the editors. This means that there will be no need to create additional files for supplementary sheets included within the document (for instance a second f. 138) since it will have been done automatically.
The only time editors should change the information in this element is when: a) the <facsimile> element already exists, and b) a case spans more than one page. Where both a) and b) are the case, the editor should copy the appropriate <graphic> from the relevant file in 00-Facsimile and paste it into <facsimile>. Be sure that the <graphic> elements are placed in the sequence in which they appear when reading the case. There is, however, no need to repeat <graphic> elements if a case crosses a page boundary back to a previous sheet, for instance if it begins on f. 50v, continues on f. 51r and then moves back to f. 50v (in which case only two <graphic> elements are needed).

<faith>

<faith> specifies the faith, religion, or belief set of a person.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<figure>

<figure> records the existence and position of an astrological or geomantic chart, whether complete, partial and/or deleted, or of a space left blank for one.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.placement (@place) att.typed (@type)
@subtype(subtype) provides a sub-categorization of the element, if needed
Status Optional
Example
&astroChart;
Example
&astroChartDeleted;
Example
&geoChart;
NoteThe assorted permissible permutations of this element are represented by the entities listed in subsection 5 of the Content Tagging section of the guidelines. In the vast majority of cases, it will appear at the end of a document, after the close of the main or final <div> element. In more convoluted entries, however, typically those running to more than one column or page, it may occur between <div>s.
Any number of <figure>s, from nought upward, may be recorded in a given file.

<fileDesc>

<fileDesc> (file description) describes the electronic text and its source.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<fileDesc> <titleStmt> <title xml:id="main_title">CASE5548</title> </titleStmt> <publicationStmt> <publisher>The Casebooks Project</publisher> <pubPlace>Cambridge</pubPlace> <date when="2010-07-05">05 July 2010</date> </publicationStmt> <sourceDesc> <bibl type="positionOnPage">1</bibl> <msDesc> <msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="219">MS Ashmole 219, f. 90r</idno> &Forman004; </msIdentifier> <msContents> <msItem> <locus from="0090r" to="0090r"/> <title sameAs="#main_title"/> </msItem> </msContents> </msDesc> </sourceDesc> </fileDesc>
NoteThis element is generated automatically before transcription begins.

<floruit>

<floruit> specifies a date or date range when a person mentioned in a case is said to have been active, if there is a significant disjuncture between this and the date of the consultation itself (i.e. he or she has been dead for a very long time).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<foreign>

<foreign> (foreign) marks up text written in a different language from the main language of the document, or from the text immediately surrounding it, using the @xml:lang values en, la, el, fr, he (English, Latin, Greek, French, Hebrew).
Attributesatt.global (@xml:id, @n, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@xml:lang(language) indicates the language of the element content using a tag generated according to BCP 47.
Status Required
Example
Mrs Blundell the younger the Cap. wife <foreign xml:lang="la">quærit utrum sit gravida</foreign> June 14 &Thursday; h. 5. p m 1610
(CASE25025)
NoteEnglish may of course be considered ‘foreign’ if the main language of the document is anything else.

<forename>

<forename> contains a forename, given or baptismal name.
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) )
@typeexplains the type of forename. Permitted values: "alternate" (the second of two alternative forenames by which a person was known), "variant" (the second of two alternative forenames by which a person was known, where the two forenames closely resemble one another but are sufficiently distinct not to be different spellings of the same name) "deckname" (a false forename either given by a querent or used by a practitioner to conceal someone's identity), or "nickname" (for the extremely unusual situation in which we know that a forename was informally bestowed rather than the name with which that person was christened, and was not given to conceal the person's identity). Typically in case files only alternate is needed; the others should not be used without clearance from a senior editor.
Status Optional
Legal values are:
alternatedecknamenicknamevariant
Example
<persName><forename>Elizabeth</forename> <surname>Blundell</surname></persName>
NoteIf a forename is unclear or partially illegible in the original, the legible or conjecturable parts should be included in the header with appropriate <unclear>, <supplied> and/or <gap> elements.

<formula>

<formula> is used in Casebooks solely in the extremely rare event of needing to code a vulgar fraction. This should be done following the template below (for one over two).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@notationnames the notation used for the content of the element.
Status Optional
Example
<formula><math xmlns="http://www.w3.org/1998/Math/MathML"><mfrac><mn>1</mn><mn>2</mn></mfrac></math></formula>

<funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.canonical (@key, @ref)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.placement (@place)
@typeclassifies the material encoded according to some useful typology.
Status Recommended
Sample values include:
headerfooterpageNumlineNumsigcatch
NoteSee Transcription Guide on how to code forme work.

<gap>

<gap> (gap) indicates a point at which material has been omitted from the transcription because it is lost or illegible.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) att.dimensions (@quantity, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@cert, @resp) att.source (@source)
@unitdefines the units (if any) in which the length of the omission is being measured. Permitted values: "chars" (characters), "words", "lines". Not needed if the @extent value is "unclear".
Status Optional
Legal values are:
charswordslines
@extentrecords the extent of the omission, expressed as an integer, or as "unclear" if it is impossible to assign a numerical value.
Status Required
@reasonexplains why the text is missing from the transcription. Permitted values: "del" (illegible deletion), "binding" (text is lost in the gutter due to over-zealous binding), "blot" (blotted), "blotDel" (text is obliterated by what could either be an accidental blot or a deliberate deletion), "code" (text is written in a code that we can neither decipher nor reproduce), "copy" (poor quality of the image being transcribed from), "damage" (manuscript damage), "faded", "foxed", "hand" (indecipherably poor handwriting), "omitted" (text appears to have been omitted from the original document but we have no means of supplying it), "over" (text is impossible to read because it is written over other text — if it is impossible to read because other text is written over it, it counts as "del").
Status Required
Legal values are:
bindingbleedthroughblotblotDelcodecopydamagedelfadedfoxedomittedoverhand
Example
<p>160<subst><del type="over"><gap reason="del" extent="1" unit="chars"/></del><add place="over">6</add></subst></p>
Example
<p>… Robart Smith of <gap reason="damage" unit="words" extent="1"/> Woulson …</p>
Example
<p>… he sent me a c<gap reason="binding" extent="unclear"/> <lb/>and some apels …</p>
Note<gap> is, by definition, an empty element.
If the @reason value is "del", <gap> must nest, directly or indirectly, in <del>.

<genName>

<genName> (genName) contains standard formulae used to distinguish between people who otherwise have the same name but are from different generations.
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) )
@typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Legal values are:
additionalprefix
Example
<persName><roleName>Mrs</roleName> <surname>Shaw</surname> <genName>the elder</genName></persName>
Example
<persName><genName>Young</genName> <roleName>Mrs</roleName> <surname>Blundell</surname> </persName>
NoteIt seems that Napier consistently uses ‘old’ and ‘young’, in formulae such as ‘Old Mr Smith’ or ‘Young Mrs Blundell’, as <genName>s rather than simple adjectives.

<geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declaring (@decls)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<geogFeat>

<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<geogName>

<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai.
Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type)
Example
<geogName> <geogFeat>Mount</geogFeat> <name>Sinai</name> </geogName>
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<graphic>

<graphic> contains a pointer to an image (or pointers to images) of the source document.
Attributesatt.typed (@type) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.declaring (@decls)
NoteThis element is entered by the technical director when images become available. The @n value of <graphic> contains the file name of the image supplied by the Bodleian, which should be used by editors when transcribing.
If a case containing an already existing <facsimile> element spans more than one page, editors should copy the appropriate <graphic> for the new page from the relevant file in 00-Facsimile and paste it into <facsimile>. Please ensure that the <graphic> elements are placed in the sequence in which they appear when reading the case. There is no need to repeat <graphic> elements if a case crosses a page boundary back to a previous sheet, for instance if it begins on f. 50v, continues on f. 51r and then moves back to f. 50v (in which case only two <graphic> elements are needed).
Normally, <graphic> only appears within <TEIHeader>, but it may in principle be included within the body text if there is a need to embed an image within the transcription. In such an event, this will be dealt with by the technical director and the editors need not concern themselves with it.

<handNote>

<handNote> (note on hand) identifies a person whose hand features in the original document, by means of a @sameAs attribute pointing to that person’s @xml:id value as recorded in <listPerson>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
Example
<handNotes> <handNote sameAs="#sforman">Simon Forman</handNote> </handNotes>
Example
<handNotes> <handNote sameAs="#gjames">Gerence James</handNote> <handNote sameAs="#rnapier">Richard Napier</handNote> </handNotes>
(describing an entry in which both Napier’s hand and that of his curate Gerence James are present).
NoteFor guidance on the <roleName>s and @xml:id values to be assigned to other scribes, see Hands in the casebooks.

<handNotes>

<handNotes> contains one or more <handNote>s recording the hand(s) in which the document is written.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<handNotes> <handNote sameAs="#gjames">Gerence James</handNote> <handNote sameAs="#rnapier">Richard Napier</handNote> </handNotes>

<handShift/>

<handShift/> (change of hand) marks the point at which the hand of an entry changes (if the transcribed section is written in more than one hand), pointing to the identity of the new hand with the @new attribute.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) att.responsibility (@cert, @resp) (att.source (@source))
@newindicates a <handNote> element describing the hand concerned.
Status Required
NoteThis attribute serves the same function as the @hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.
Example
Isaak morley <handShift new="#sforman"/>of <lb/>Lumbert strete
Note<handShift/> is not needed if the intervention of a second hand is limited to text marked up by an element (such as <add> or <note>) that has its own @hand attribute.

<head>

<head> (heading) marks a header of any sort, either of a whole document or a sub-section within one.
Attributesatt.typed (@type) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@rend(rendition) describes the placement of the heading. Permitted values: "right" (right-aligned), "left" (left-aligned), "center" (centred), or "indent0", "indent5", "indent10", "indent15" etc., up to "indent40", to indicate the approximate number of spaces by which a heading is indented if it is indented consistently.
Status Optional
Sample values include:
rightleftcenterindent0indent5indent10indent15indent20indent25indent30indent35indent40
Example
<head rend="center">A treatise touching the Defence of Astrology</head>
Note<head> may only appear as the first element in a <div>, <lg> or <list>.
It is extremely rare for anything definable as a <head> to appear in the consultation records: this element is principally used in transcriptions of ancillary texts such as the astrology guides.

<hi>

<hi> (highlight) marks text that has been distinctively rendered in some way, e.g. underlined, overlined, italicised, or in larger text or a different colour. The nature of the formatting is indicated in @rend.
Attributes
@rend(rendition) values are "allCaps" (capitalised), "bold" (bold), "dropCap" (drop capital), "italic" (italic), "overline" (overlined), "smallCaps" (small capitals), "subscript" (subscripted), "superscript" (superscripted), "underline" (single underlined), "doubleUnderline" (double underlined). @rend can also be used to indicate changes in text size with "large", "larger", "largest" and "small", "smaller", "smallest". It can also be used to indicate a change of writing medium, with "redInk" used to indicate that a word or phrase is written in red ink, "redUnderline" to indicate that a text string is underlined in red but not itself written in red, or "differentInk" if the text string is written in a different ink (of unknown colour).
Status Required
Legal values are:
superscriptsubscriptunderlinedoubleUnderlineoverlineitalicboldlargelargerlargestsmallsmallersmallestdropCapsmallCapsallCapsredInkredUnderlinedifferentInk
Example
… And the fault is in such fraudulent <hi rend="underline">fellowes</hi> fooles as them<lb/>selues, for they came with a lye, and they had an Answer <lb/>to a lye …
NoteWe do not attempt to record all the changes in size of Forman’s erratic handwriting, or the fact that he normally puts part at least of the subject’s name in much larger letters than the rest of the text. If such fluctuations do seem to be relevant to the interpretation of the text (e.g. deducing who is the subject in ambiguous cases), this can be mentioned in a comment tag. In practice, it is very rare for any values other than "superscript", "subscript", "overline" and "underline" to be needed in transcriptions of consultation records.
"redUnderline" is used to indicate that a text string not written in red has been underlined in red. However, if <hi rend="underline"> occurs within <hi rend="redInk">, both the text and underlining are presumed also to be in red if there is no indication to the contrary.

<idno>

<idno> (identifier) records the manuscript, and the page or folio within it, on which the entry appears.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey)
@typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Status Optional
NoteIn the vast majority of cases, this element and its content and attribute values are generated automatically before transcription begins. Its content only requires hand-crafting, as explained in the Guidelines, if an entry occupies more than one page or folio.

<incipit>

<incipit> contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.msExcerpt (@defective)

<item>

<item> contains an item within a <list>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey)
Example
<list> <head>parties suspected</head> <item>Thomas price</item> <item>frainces brodshowe</item> <item>Jeams vicars</item> <item>Robart fountain</item> <item>Jhon Laiton</item> <item>Richard Jobbar</item> <item>Wilm Norman&slash;</item> </list>
NoteThis element is used only rarely in Casebooks transcriptions, typically to encode items in formulaic lists, clearly set out as such in the original, of suspected witches, fathers (in paternity cases) or, as in the example given here (CASE1706), thieves.

<l>

<l> (verse line) contains a single, possibly incomplete, line of verse.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.fragmentable (@part)
NoteAt the time of writing, this element has never been used in the transcription of entries in the casebooks, only in that of one of the guides to astrology, but it may come in handy should Napier ever take it into his head to write one of his questions in verse.

<lacunaEnd/>

<lacunaEnd/> indicates the end of a lacuna in a mostly complete textual witness.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.rdgPart (@wit)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<lacunaStart/>

<lacunaStart/> indicates the beginning of a lacuna in the text of a mostly complete textual witness.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.rdgPart (@wit)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<language>

<language> (language) specifies a language used within the document. Permitted @ident values: "el" (Greek), "en" (English), "fr" (French), "he" (Hebrew), "la" (Latin), "und" (undetermined).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@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.
Status Required
@usagespecifies the approximate percentage (by volume) of the text which uses this language.
Status Optional
Example
<langUsage> <language ident="en">English</language> <language ident="la">Latin</language> </langUsage>
NoteEvery file will contain at least one <language> element except in the very rare case of entries that contain no text at all (and never did). Entries that have been deleted or damaged to such an extent that it is impossible to determine what language(s) they were in should be given the @ident value "und".

<langUsage>

<langUsage> (language usage) lists the language(s) used in a document, each in its own <language> element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declarable
Example
<langUsage> <language ident="la">Latin</language> <language ident="en">English</language> <language ident="el">Greek</language> </langUsage>

<lb/>

<lb/> (line break) marks the beginning of a line of prose, including the first line of a paragraph. Although formally defined as ‘line break’, it is more usefully thought of as ‘line beginning’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.edition (@edRef) att.spanning (@spanTo) att.breaking (@break)
Example
<p><lb/>M<hi rend="superscript">rs</hi> shawe of 50 yers <lb/>1596 the first of Aprille <lb/>Thursday An&flourish; m&flourish; 30 p 9 Diz</p>
NoteWhere <lb/> occurs between two words, one space should be left before it. Where it divides a single word or occurs at the beginning of a paragraph, there should be no space on either side of it.

<lem>

<lem> (lemma) contains the lemma, or base text, of a textual variation.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.textCritical (@type, @cause, @varSeq, @hand) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.witnessed (@wit)
NoteThis element is not used in transcriptions of Casebooks entries, only in those of the more discursive guides to astrology or similar texts.

<lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (@type) att.declaring (@decls)
Example
<lg> <l>The plannets vertue is proper and especiall.</l> <l>The vertue infused resulteth of them all.</l> <l>The first is like a workmans minde.</l> <l>The second like to his hand you shall finde</l> <l>The third is like a good instrument.</l> <l>The remnant like a thinge wrote to your intent.</l> </lg>
NoteAt the time of writing, this element has never been used in the transcription of entries in the casebooks, only in that of one of the guides to astrology, but it may come in handy should Napier ever take it into his head to write one of his questions in verse.

<list>

<list> (list) contains any number of items organised as a list.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey)
@typedescribes the form of the list.
Status Optional
Suggested values include:
orderedbulletedsimplegloss
NoteThe formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.
Example
<list> <head>parties suspected</head> <item>Thomas price</item> <item>frainces brodshowe</item> <item>Jeams vicars</item> <item>Robart fountain</item> <item>Jhon Laiton</item> <item>Richard Jobbar</item> <item>Wilm Norman</item> </list>
NoteThis element is used only rarely by the Casebooks Project, typically to encode formulaic lists, clearly set out as such in the original, of suspected witches, fathers (in paternity cases) or, as in the example given here (CASE1706), thieves.

<listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.declarableatt.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<listOrg>

<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.declarableatt.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<listPerson>

<listPerson> (list of persons) contains a list of people (and, if appropriate, <org>s and/or <personGrp>s) featuring in a consultation, and the relations between them.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.declarableatt.sortable (@sortKey)
Example
<listPerson> <person xml:id="sforman"> <persName><forename>Simon</forename> <surname>Forman</surname></persName> <sex value="1">M</sex> </person> <person xml:id="c"> <persName><surname type="married">Clark</surname></persName> <sex value="2">F</sex> </person> <person xml:id="wc"> <persName><forename>William</forename> <surname>Clark</surname></persName> <sex value="1">M</sex> <age value="30">30</age> </person> <listRelation> <relation name="wife" active="#c" passive="#wc"/> </listRelation> </listPerson>

<listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.declarableatt.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<listRelation>

<listRelation> (relationship list) contains any number of <relation> elements describing interpersonal relationships recorded in the entry.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.sortable (@sortKey)
Example
<listRelation> <relation name="servant" active="#ja" passive="#t"/> <relation name="cousin" mutual="#ja #pa"/> </listRelation>
This records that the person with the @xml:id value "ja" is servant to the person with the @xml:id value "@t" and that the people with @xml:id values "ja" and "pa" are cousins.
NoteAny <relation> elements should be nested in <listRelation>, even if there is only one recorded relationship in a given case.

<listWit>

<listWit> (witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<locus>

<locus> defines the page or pages on which an entry appears.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.pointing (@target)
@fromspecifies the starting point of the location in a normalized form, typically a page number.
Status Required
@tospecifies the end-point of the location in a normalized form, typically as a page number.
Status Required
Example
<locus from="0238r" to="0238r"/>
Example
<locus from="0059v" to="0060r"/>
Example
<locus from="0138v" to="0138v"/> <locus from="0137v" to="0137v"/>
NoteThe @from and @to values should always be four-digit integers, with however many leading zeros are needed to make up the four figures, followed immediately by r (recto) or v (verso) if the document is foliated rather than paginated (if it is paginated no suffix is needed). If, as is usually the case, the entry is on a single page, the @from and @to values will be identical. If the entry runs to more than one page in a logical sequence, e.g. from f. 59v to f. 60r or from f. 60r to f. 60v, the @from value will define the page it starts on and the @to value the page it ends on. If it runs to more than one page and is not in a logical sequence, e.g. it runs backwards or leapfrogs a page somewhere in the middle, it needs two or more <locus> elements, each defining one of the pages, listed in (what is presumed to be) the intended reading order.
If the <xml:id> and <n> values of the page (or one of the pages) in question has been given a suffix of A, B, etc. to allow for irregularities in the original foliation or pagination (see section II.4 b) ii) of the Header section of the Guidelines), the relevant @from and/or @to value(s) of <locus> take the same suffix.
This element is normally generated automatically before transcription begins. It only requires hand-crafting if the entry turns out to occupy more than one page.

<media>

<media> indicates the location of any form of external media such as an audio or video clip etc.
Attributesatt.typed (@type) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.resourced (@url) att.declaring (@decls) att.timed (@start, @end) att.media (@width, @height, @scale)
@mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Required
NoteThis element is not used in Casebooks transcriptions, only in the code that generates the project’s homepage.

<milestone/>

<milestone/> is analogous to <pb/> but only used in the extremely rare cases where the component pages of an entry appear in separate volumes.
Attributesatt.milestoneUnit (@unit) att.typed (@type) att.edition (@edRef) att.spanning (@spanTo) att.breaking (@break) att.global (@xml:lang, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
@n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
NoteSee the Guidelines for advice on how to apply this in the unlikely event of its ever again being necessary. At the time of writing, it has been used precisely once.

<msContents>

<msContents> (manuscript contents) contains, for Casebooks purposes, only the elements <msItem> and <title>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.msExcerpt (@defective)
@classidentifies the text types or classifications applicable to this object by pointing to other elements or resources defining the classification concerned.
Status Optional
Example
<msContents> <msItem> <locus from="0006r" to="0006r"/> <title sameAs="#main_title"/> </msItem> </msContents>
NoteThis element and its content are generated automatically before transcription begins, though if an entry runs to more than one page the <locus> values will have to be revised by the transcriber.

<msDesc>

<msDesc> defines the manuscript within which the entry occurs and the entry’s location within it.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey) att.typed (@type)
Example
<msDesc> <msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 13v</idno> &Forman001; </msIdentifier> <msContents> <msItem> <locus from="0013v" to="0013v"/> <title sameAs="#main_title"/> </msItem> </msContents> </msDesc>
NoteThis element is generated automatically before transcription begins.

<msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript being described.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="193">MS Ashmole 193, f. 51v</idno> </msIdentifier>
NoteThis element is generated automatically before transcription begins.

<msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.msExcerpt (@defective)
@classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
Status Optional
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<name>

<name> (name) is used for editors’ names in the <TEIHeader>, or for names of participants in cases where it is unclear whether the name given is a forename or surname (or, indeed, role name, nickname or anything else).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.typed (@type)
NoteIf a <name> is unclear or partially illegible in the original, the legible or conjecturable parts should be included in the header with appropriate <unclear>, <supplied> and/or <gap> elements.

<note>

<note> (note) records either an editorial note in the header or an authorial annotation in the body text. Editorial notes nest in <notesStmt> and have a @resp value pointing to the editor responsible and any of the following @type values: "blank" (for notes explaining when entries are wholly or substantially deleted, or have been abandoned), "editorial" (general notes about points of interpretation and ambiguity and records of general editorial intervention) "externalEvidence" (for notes recording remarks and updates elsewhere in the casebooks that are relevant to the case in question and that have provided information for its header), "interest" (notes that record interesting aspects of the entry or highlight entries of particular interest), "layout" (notes that explain complex layouts or unusual positioning of entries), "physical" (notes about the physical manuscript, from records of damage to oddities about binding). Authorial notes do not need a @type value, just a @place value indicating their placement. Values are "infralinear", "inline", "interlinear", "lineBeginning", "lineEnd", marginLeft", "marginRight", "pageTop", "pageBottom", or "chart" (for notes added inside an astrological chart).
Attributesatt.placement (@place) att.pointing (@target) att.responsibility (@cert, @resp) (att.source (@source)) att.typed (@type) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space)
Example
<notesStmt><note type="layout" resp="#jyoung">This entry is upside down.</note></notesStmt>
Example
<notesStmt><note type="editorial" resp="#rralley">It is not clear what role Mr Burton plays in this entry.</note></notesStmt>
Example
<p>Sara Musgrave <lb/>of Bletchsoe 23 <lb/>y march: 11. Tuesday <lb/>h. 12. 1606.<note place="chart">troubled in <lb/>mynde.</note></p>
Example
<p>… Apr. 15. Tuesday h. 6. 20 <lb/>p m. 1606.<note place="pageTop">M<hi rend="superscript">r</hi> Burton</note></p>
Note"marginLeft" and "marginRight" should be seen as relative to the point they relate to: for instance, notes that actually occur in the middle of the page as a whole should be considered "marginRight" if they pertain to a point in the left column or "marginLeft" if they pertain to a point in the right column

<notesStmt>

<notesStmt> (notes statement) functions as a container for one or more editorial notes on the document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<notesStmt><note type="layout" resp="#jyoung">This entry appears between the question and the chart for <ref target="CASE6333" type="case">CASE6333</ref>.</note></notesStmt>

<num>

<num> (number) contains a number, written in any form.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.ranging (@atLeast, @atMost)
@typeindicates the type of numeric value.
Status Optional
Suggested values include:
cardinalordinalfractionpercentage
NoteIf a different typology is desired, other values can be used for this attribute.
@valuesupplies the value of the number in standard form.
Status Optional
Values a numeric value.
NoteThe standard form used is defined by the TEI datatype data.numeric.
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<occupation>

<occupation> (occupation) describes a person’s occupation, using any of the terms recorded in the occupations master list and beginning with a capital letter.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
@schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
Status Optional
@codeidentifies an occupation code defined within the classification system or taxonomy defined by the @scheme attribute.
Status Optional
Example
<occupation>Shepherd</occupation>
Example
<occupation>Ratcatcher</occupation>
NoteWhere not explicitly stated, occupations may be inferred from evidence in either the transcribed or the untranscribed part of the entry. For instance, a statement such as ‘her master beateth her’ strongly suggests that the beaten person in question is a servant of some description. In such cases, <occupation> takes an @evidence value of "inferred" and, if there is any doubt about the inference, a @cert value of "high|medium|low".
If a person’s occupation is recorded only in the untranscribed part of the document, <occupation> takes an @evidence value of "internal".

<opener>

<opener> groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<org>

<org> (organisation) should be used where any of the parties to a consultation is not an individual person but a definable organisation, e.g. ‘the docters’ (in Forman’s case usually meaning the London College of Physicians) or ‘the Unversity of Oxford’. Each <org> takes a mandatory 3-letter @xml:id value, and as content the element <orgName>, containing a modernised version of the original description (with an initial capital).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.sortable (@sortKey)
@rolespecifies a primary role or classification for the organization.
Status Optional
NoteValues for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, family group, or political party, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
Example
<org xml:id="drs"><orgName>The doctors</orgName></org>
Example
<org xml:id="eag" type="ship"><orgName>The Eagle</orgName></org>
NoteA ship may be defined as an <org>, with the @type value "ship", in the (fairly rare) cases where the subject or object of a consultation appears to be the ship itself rather than any of the people on board it.

<orgName>

<orgName> (organisation name) records the name of anything defined as an <org>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type)
Example
<org xml:id="tcc"> <orgName>Trinity College, Cambridge</orgName> </org>

<orig>

<orig> (original form) contains the original form of a text string or symbol for which a regularised version has been provided, and nests together with <reg> (containing the regularised version) in a <choice> element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.responsibility (@cert, @resp) (att.source (@source))
Example
<p>Dec<choice><orig><hi rend="overline">e</hi></orig><reg>em</reg></choice>b<choice><orig><hi rend="superscript">r</hi></orig><reg>er</reg></choice></p>
Note<orig> always precedes <reg> within <choice>.

<p>

<p> (paragraph) contains <time> or <date> in the header (each in a separate <p> if both are present), or marks paragraphs in prose. No attributes are normally needed but @rend (rendition) is available, with the values "right" (right-aligned), "left" (left-aligned), "center" (centred), or "indent0", "indent5", "indent10", "indent15" etc., up to "indent40", to indicate the approximate number of spaces by which the first line of a paragraph is indented if the indentation is deemed to be at least potentially significant.
Attributesatt.declaring (@decls) att.fragmentable (@part) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Sample values include:
rightleftcenterindent0indent5indent10indent15indent20indent25indent30indent35indent40
Example
<p><lb/>Thomas Lavorok <lb/>of 60 yers 1598 2 may <lb/>Tuesday An m 30 p 9 Diz</p>

<particDesc>

<particDesc> (participant description) contains documentation for all the people involved in the case.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declarable
Example
<particDesc> <listPerson> <person xml:id="rnapier"> <persName><forename>Richard</forename> <surname>Napier</surname></persName> <sex value="1">M</sex> </person> <person xml:id="jh"> <persName><forename>Joan</forename> <surname>Hatch</surname></persName> <sex value="2">F</sex> <age value="53">53</age> <residence sameAs="#address1" key="databaseNormalizedIDKey"/> </person> </listPerson> </particDesc>
Note‘Participant’ is here defined very broadly, meaning the practitioner(s), the scribe(s) (if relevant), and anyone mentioned in the transcribed portion of the entry, even if they do not, strictly speaking, participate in it.
People mentioned in the untranscribed portion of the entry may also, at the editor’s discretion, be listed here if they seem relevant to the understanding of the case, for instance suspected witches or people accused of having harmed the subject in some way, with an @evidence value of @internal on their <person> elements. People mentioned merely in passing in the untranscribed section (e.g. ‘shee was in love but her father was against it’ where the subject’s love life does not appear to be the topic at issue) can be passed over in silence.

<pb/>

<pb/> (page break) marks the beginning of a new page in the document, and takes @xml:id and @n values as explained in the Guidelines.
Attributesatt.typed (@type) att.edition (@edRef) att.spanning (@spanTo) att.breaking (@break) att.global (@xml:lang, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
@n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Example
<div> <p><lb/>An dayrell 19 y troubled with the greene sicknes shortwinded greeped about the hart &amp; stuffed.</p> </div> <div><pb xml:id="f16r" n="16r"/> <p><lb/>Mrs Derrell craveth further my Counsell …</p> </div>
NoteIf the page break occurs outside the transcribed portion of the text (for instance, if the question and chart are on f. 146r but the judgment on f. 146v), <pb/> should be placed outside <div>. If, however, as in the example given here (CASE10178), the page break occurs within the transcribed portion, it should nest in <div>.
In the extremely rare event of text moving on to the same page more than once within a given file, the two @xml:id values should be distinguished by appending a hyphen and a numeral to the normal value, e.g. f46r-1, f46r-2, but the two @n values will be identical.
Where canonical images are available, <pb/> also takes a @facs value pointing to the URL for the image of the page in question. This is generated automatically and editors need not concern themselves with it.

<persName>

<persName> (personal name) contains as many as appropriate of the component parts of a person’s name, i.e. <roleName>, <forename>, <surname>, <genName>, <nameLink>, <name>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) )
@typeapplies only in the (extremely rare) cases of Decknamen (entirely false names either given by a querent or used by a practitioner to conceal the person's identity): this takes the value "deckname".
Status Optional
Legal values are:
deckname
Example
<persName><roleName>Mr</roleName> <forename>John</forename> <surname>Perkins</surname></persName>
Example
<persName><roleName>Lady</roleName> <surname>Throckmorton</surname></persName>
NoteIf some or all of a person's name is not explicitly stated, or is given in code, or is drastically abbreviated, but can be deduced from external evidence, <persName>, <forename> and <surname> (but not, for some reason, <name> or <genName>) can all take an @evidence value of "external" and, if there is any doubt about the identification, a @cert value of "high|medium|low". If all or part of the name is given only in one of the untranscribed sections of the entry in question, @evidence takes the value "internal".
The proper nouns in <persName> should be given in regularised forms as established in the pilot project or subsequently.
Where any part of <persName> is unclear or partially illegible in the original, the legible or conjecturable parts should be included in the header with appropriate <unclear>, <supplied> and/or <gap> elements.

<person>

<person> contains biographical data about a person, such as name, age, sex, residence, occupation.
Attributesatt.sortable (@sortKey) att.global (@n, @xml:lang, @xml:base, @xml:space) att.global.linking (@sameAs, @exclude) att.responsibility (@cert, @resp) att.source (@source)
@xml:id(identifier) provides a code (in lower case letters), normally generated from the initial(s) of the person in question, by which he or she may be referred to in other markup.
Status Optional
@evidenceexplains the grounds for inferring or conjecturing the person’s existence where he or she is not explicitly mentioned in the transcribed text. Permitted values: "internal" (evidence from the untranscribed part of the entry), "external" (evidence from a source external to the entry, including elsewhere in the casebooks), "conjecture".
Status Optional
Legal values are:
internalexternalinferredconjecture
Example
<person xml:id="af"> <persName><forename>Anne</forename> <surname>Foot</surname></persName> <sex value="2">F</sex> <age value="60">60</age> <residence sameAs="#address1" key="databaseNormalizedIDKey"/> </person>

<personGrp>

<personGrp> (personal group) is used where the ‘person’ in question is not an individual but a group of unnamed people not definable as an <org>. This takes a 3-letter xml:id value in the same way as <org> but does not include a <persName>. Instead, such groups are defined in terms of occupation, sex and/or relation(s) to any other particpants.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey) att.responsibility (@cert, @resp) att.source (@source)
@evidenceexplains the grounds for inferring or conjecturing the <personGrp>’s existence where it is not explicitly mentioned in the transcribed text. Permitted values: "internal" (evidence from the untranscribed part of the entry), "external" (evidence from a source external to the entry, including elsewhere in the casebooks), "conjecture".
Status Optional
Legal values are:
internalexternalinferredconjecture
Example
<personGrp xml:id="tbf"> <sex value="0">U</sex> </personGrp>
for ‘Thomas Bricknell’s friends’, where <listRelation> includes
<relation name="friend" mutual="#tb #tbf"/>
.
Example
<personGrp xml:id="ser"> <sex value="0">U</sex> <occupation>Servant</occupation> </personGrp>
for ‘the servants’, where it is not known whose servants they are (if this is known, obviously it should be stated in a <relation> element).
NoteNote that the content of <occupation> is always given in the singular, even when referring to an occupation shared by a number of people.
<sex> takes a @value value of "1" if all members of the group are known to be male, "2" if all members are known to be female, or "0" if their genders are not known. In the unlikely event that such a group is known to include both female and male members, it may be necessary to divide it into two groups, one female and the other male, but in practice it is extremely unusual for a <personGrp> to be defined in that much detail in the source.

<place>

<place> contains data about a geographic location
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<placeName>

<placeName> (place name) is used in the body text to mark up any specified location not representing the address of one or more of the participants. Where such place names need to be linked to from the header (for instance because they record places of birth, marriage or death), <placeName> takes an @xml:id value of "place1" (or "place2", "place3" etc. if more than one occurs in a given file). No attribute is needed for place names not linked to from the header.
Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type)
Example
<placeName>my bedroome</placeName>
Example
<placeName>Fraunce</placeName>
Example
… Inkeeper of <placeName>the white horse</placeName> …
In this example, the innkeeper of the White Horse may well live in the White Horse but cannot be assumed to do so without further evidence, so it is tagged as a <placeName> rather than an <rs type="address">.
Example
… borne in <placeName xml:id="place1">London</placeName> …
Here, the <placeName> will be linked to from the <birth> element in the relevant person’s entry in the header, so it needs an @xml:id value.
NoteIf (as is usually the case) a specified location does represent someone’s address, it should be marked up as <rs> with a @type value of "address" rather than as <placeName>.
As in the case of the innkeeper of the White Horse cited above, the distinction is particularly problematic when it comes to clerics attached to particular locations: ‘Mr Watson parson of bow brickle’ (CASE12648), for instance, does not necessarily live in Bow Brickhill, but had he been referred to as ‘Mr Watson of bowbrickle, parson’ it would be reasonable to suppose he does.

<postscript>

<postscript> contains a postscript, e.g. to a letter.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<profileDesc>

<profileDesc> (profile description) describes the contents of the file and of its source.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<profileDesc> <handNotes> <handNote sameAs="#rnapier">Richard Napier</handNote> </handNotes> <langUsage> <language ident="en">English</language> </langUsage> <textClass xml:base="../05-master-lists/consultation-types.xml"> <catRef target="#horary"/> </textClass> <particDesc> <listPerson> <person xml:id="rnapier"> <persName><forename>Richard</forename> <surname>Napier</surname></persName> <sex value="1">M</sex> </person> <person xml:id="as"> <persName><forename>Arthur</forename> <surname>Smith</surname></persName> <sex value="1">M</sex> <age value="37">37</age> <residence sameAs="#address1" key="databaseNormalizedIDKey"/> </person> </listPerson> </particDesc> <settingDesc> <p><date when="1600-02-26" n="Tuesday"/></p> <p><time when="12:30:00"/></p> <cb:consultation> <cb:consultant ref="#rnapier"/> <cb:practice name="napier"/> <cb:querent ref="#as"/> <cb:subject ref="#as" present="unclear"/> <cb:topic key="eyesight"><person sameAs="#as"/></cb:topic> <cb:judgment/> <cb:treatment/> <cb:info type="financial"/> </cb:consultation> </settingDesc> </profileDesc>
NoteThis element (but not its content) is generated automatically before transcripion begins.

<publicationStmt>

<publicationStmt> (publication statement) gives details about the release of the electronic document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<publicationStmt> <publisher>The Casebooks Project</publisher> <pubPlace>Cambridge</pubPlace> <date when="2014-06-09">09 June 2014</date> </publicationStmt>
NoteThis element is generated automatically before transcription begins, and the details of the <date> element modified automatically when the file is released.

<publisher>

<publisher> gives the name of the organisation responsible for publishing the file. For Casebooks Project purposes, this is invariably ‘The Casebooks Project’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<publicationStmt> <publisher>The Casebooks Project</publisher> <pubPlace>Cambridge</pubPlace> <date when="2010-07-05">05 July 2010</date> </publicationStmt>
NoteThis element is generated automatically before transcription begins.

<pubPlace>

<pubPlace> (publication place) gives the place of publication. For Casebooks purposes, this is invariably ‘Cambridge’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Example
<publicationStmt> <publisher>The Casebooks Project</publisher> <pubPlace>Cambridge</pubPlace> <date when="2010-07-05">05 July 2010</date> </publicationStmt>
NoteThis element is generated automatically before transcription begins.

<q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.ascribed (@who) att.source (@source)
@typemay be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
Status Optional
Suggested values include:
spokenthoughtwrittensoCalledforeigndistincttermemphmentioned
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.typed (@type) att.msExcerpt (@defective) att.source (@source)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<rdg>

<rdg> (reading) contains a single reading within a textual variation.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.witnessed (@wit) att.textCritical (@cause, @varSeq, @hand) att.responsibility (@cert, @resp) att.source (@source)
@typeindicates the nature of the variant reading's difference from the lemma. Permitted values: "caps" (the variant differs only from the lemma in its capitalisation), "orthographic" (the variant reading differs from the lemma in its spelling, use of brevigraphs or abbreviations, or word-division), "punctuation" (the variant reading differs from the lemma in its punctuation), "substantive" (the variant reading uses different words from the lemma), "hi" (the variant reading differs from the lemma only in the text's highlighting), "hicaps" (the variant reading differs from the lemma in its capitalisation and in highlighting applied to the text), "hiorth" (the variant reading differs from the lemma in its spellings, use of brevigraphs or abbreviations, or word-division, and in highlighting applied to the text), "hipunc" (the variant reading differs from the lemma in its capitalisation and in highlighting applied to the text), and "hisubs" (the variant reading uses different words from the lemma, and also differs in highlighting applied to the text).
Status Required
Legal values are:
capsorthographicpunctuationsubstantivehihicapshiorthhipunchisubs
NoteThis element is not used in transcriptions of Casebooks entries, only in those of the more discursive guides to astrology or similar texts.
A variant reading marked as substantive may include differences in punctuation, spelling and capitalisation; likewise, a variant reading marked as orthographic may include differences in capitalisation.

<ref>

<ref> (reference) supplies a link to another online location.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.internetMedia (@mimeType) att.typed (@type) att.declaring (@decls) att.cReferencing (@cRef)
@targetspecifies the destination of the reference by supplying one or more URI References
Status Required
NoteThis element is only used in Casebooks Project transcriptions within <notesStmt>, where it provides a link to another Casebooks entry referred to in the <note>. It takes a @type value of "case" and a @target value of (for instance) "CASE10018". If the case to be linked to has not yet been released at the time of transcription, and hence has no CASE number, a placeholder value of the relevant file's working title, minus the invariable prefix MS_Ashmole_ (e.g. ‘201-f0057v-1’ for the first entry on f. 57v of MS Ashmole 201) should be entered instead, as both the content and the @target value of <ref>. These will be automatically converted to the relevant CASE number when one has been assigned, so NB especial care should be taken to ensure that precisely the correct working title is used, as the slightest typographical error will lead to the link either pointing to the wrong entry or not pointing to anything at all.
The element also occurs in many of the files used to generate the website pages, in which case it may require the @type value "protected" if it links to an external resource subject to restricted access, but transcribers need not concern themselves with this.

<reg>

<reg> (regularisation) contains the regularised form of a text string (as it will appear in the ‘normalised’ view of the transcription), or a gloss (which will be displayed in a mouseover). <reg> follows <orig>, which contains the original text string, within a <choice> element and does not need any attributes unless it functions as a gloss.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
@typeexplains, in the event of there being any possible confusion, whether the content of <reg> is a "normalisation" or a "gloss". If no attribute is invoked, it is by default taken as a normalisation.
Status Optional
Legal values are:
glossnormalisation
Example
<p>Sept<choice><orig><hi rend="overline">e</hi></orig><reg>em</reg></choice>ber</p>
Example
<p>the 18 of march <lb/><choice><orig>an&flourish; m&flourish;</orig><reg>am</reg></choice> 45 <choice><orig>p.</orig><reg>post</reg><reg type="gloss">past</reg></choice> 7</p>
NoteA given text string may have both a normalisation and a gloss, as in the second example above.

<region>

<region> contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<relation>

<relation> (relationship) describes a relationship of any sort between participants where this is recorded in the source (including, if appropriate, untranscribed portions of the source).
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref) att.sortable (@sortKey) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@resp) att.source (@source)
@evidenceexplains the grounds on which an editorial interpretation of the nature of a relationship has been arrived at, using the values internal, external, inferred or conjecture.
Status Optional
Legal values are:
internalexternalinferredconjecture
@cert(certainty) states the level of certainty about such editorial interpretations, on a scale of high|medium|low.
Status Optional
Legal values are:
lowmediumhigh
@activepoints to the person(s), <personGrp>(s) or <org>(s) who has/have this relationship to another person or other people, or <org>(s).
Status Optional
@mutualpoints to two or more people and/or groups of people who have the same relationship to one another, e.g. cousin or friend.
Status Optional
@namedefines the nature of the relationship, using any of the terms recorded in the relations master list.
Status Required
@passivepoints to the person(s), <personGrp>(s) or <org>(s) to whom this relationship is had.
Status Optional
Example
<listRelation> <relation name="servant" active="#ja" passive="#t"/> <relation name="cousin" mutual="#ja #pa"/> </listRelation>
This records that the person with the @xml:id value "ja" is servant to the person with @xml:id value "t" and that the people with the @xml:id values "ja" and "pa" are cousins.
NoteOnly one of the attributes @active or @mutual may be supplied on a given <relation> element; if the attribute @active is supplied, the attribute @passive must be supplied too.

<repository>

<repository> contains the name of the repository within which the original document is housed. For Casebooks Project purposes, this is invariably ‘Bodleian Library’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Example
<msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 1r</idno> &Forman001; </msIdentifier>

<residence>

<residence> (residence) points where possible, by means of a @sameAs value, to an <rs> element in the transcribed text marking up a participant’s address. If an address is given in an untranscribed portion of the entry, <residence> takes no @sameAs value and contains a literal transcription of the address as given in the source.
Attributesatt.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) att.global.linking (@corresp, @sameAs, @copyOf, @exclude) att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom) att.naming (@role, @nymRef) att.canonical (@ref)
@key(key) always takes, provisionally, the value "databaseNormalizedIDKey". These values will all, in due course, be transformed into references to the relevant item in a master list of all the addresses recorded in the casebooks.
Status Required
Example
<residence sameAs="#address1" key="databaseNormalizedIDKey"/>
Example
<residence key="databaseNormalizedIDKey">of yardly Gubion</residence>
NoteWhere a former address is mentioned in an entry, this should be marked up in the same way but with <residence> taking a @notAfter ISO value of the last plausible date at which it might have been a current residence (the day before the consultation if no other evidence is available) or a @to value of the date on which it ceased to be one if this can be ascertained.

<revisionDesc>

<revisionDesc> records the work done on the electronic file, with dates and the identities of the editors who have done the work.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.docStatus
Example
<revisionDesc> <change when="2009-12-12">Data entered in Microsoft Excel spreadsheet by <name xml:id="rralley">Robert Ralley</name> as part of the Casebooks Pilot Project.</change> <change when="2010-07-05">XML file created by <name xml:id="mhawkins">Michael Hawkins</name> from Casebooks Pilot Project data.</change> <change when="2011-04-22">Transcribed by <name xml:id="jyoung">John Young</name>.</change> <change when="2011-04-28">Checked by <name sameAs="#rralley">Robert Ralley</name>.</change> <change when="2013-01-17">Facsimile coding added by <name sameAs="#mhawkins">Michael Hawkins</name>.</change> </revisionDesc>
NoteThe changes recorded within this element should be listed in chronological order.

<roleName>

<roleName> (role name) covers appellations such as ‘Mr’, ‘Mrs’, ‘Sir’, ‘Goodwife’, or other formulae besides personal names, job titles, or social or familial relations (e.g. ‘Mr Uvedales servant’, ‘Smiths cosen’) used to specify a person’s identity.
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) )
@typeis currently only used in the master name files. The only valid values currently allowed are "prefix" or "additional".
Status Optional
Legal values are:
prefixadditional
Example
<persName><roleName>Mr</roleName> <forename>John</forename> <surname>Perkins</surname></persName>
Example
<persName><roleName>Lady</roleName> <surname>Throckmorton</surname></persName>
NoteIf someone is identified solely by their role name and this is given in Latin (or any other language apart from English), it should be translated into English in the header.
Titular role names such as ‘Lord’, ‘Mrs’, ‘Alderman’, ‘Dr’, ‘Goodwife’ should be the first child element within <persName>, while more descriptive ones (e.g. ‘Bishop of London’) should be placed last. In most cases this reflects the way in which they are presented in the original. There are cases in which it is debatable whether a given formulation counts as a <roleName> or not. Less clear-cut examples will have to be resolved by editorial consultation.

<row>

<row> contains one row of a table.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.tableDecoration (@role, @rows, @cols)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<rs>

<rs> (referencing string) contains a general purpose name or referring string.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
@typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Legal values are:
addressdatetime
Example
<p>Elisabeth Haynes <rs type="address" xml:id="address1">of <lb/>Hanslop</rs>. 28 y.</p>
Example
<p>my Cosen Stocker intreated me to goe to <rs type="address" xml:id="address1" next="#address2">Mr Cutlers house</rs> to see him being extreme sicke &amp; I came thither <rs type="address" xml:id="address2" prev="#address1">in london</rs> march 29</p>
NoteFor Casebooks purposes, <rs> is used almost exclusively to mark up addresses as recorded in the source text and takes the @type value "address" and an @xml:id value of "address1" (or "address2", "address3" etc. if more than one address is recorded in a single document or the same address is mentioned more than once. If the same address is referred to more than once in a document, any subsequent references point back to the @xml:id value of the first one by means of a @sameAs value.
Any terminal punctuation should be placed after the <rs> tag (as in the first example above), though medial punctuation may be included within it.
Only current addresses (that is, current at the time of the consultation) should be marked up with <rs>. Former addresses and other place names should be marked up with <placeName>.
If the same address is referred to more than once in a given file, each mention after the first should be given its own <rs> tag with a @sameAs value pointing to the @xml:id value of the first corresponding <rs>.
The @next and @prev attributes are needed only in the fairly rare event of a single address being presented as two or more non-contiguous text strings separated by other text that does not form part of the address. Their values point to the @xml:id value of each other’s <rs> element, as in the final example above, and the relevant <residence> element in the header points to the first of the available @xml:id values.

<salute>

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<seg>

<seg> (arbitrary segment) represents any segmentation of text below the chunk level.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type) att.responsibility (@cert, @resp) (att.source (@source))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<settingDesc>

<settingDesc> (setting description) records the circumstances of the consultation itself, and contains <date> (if ascertainable), <time> (if ascertainable) and <cb:consultation> with all its component elements. <date> and <time> should each nest inside its own <p> element within <settingDesc>.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declarable
Example
<settingDesc> <p><date when="1605-12-26" n="Thursday"/></p> <p><time when="09:00:00"/></p> <cb:consultation> <cb:consultant ref="#rnapier"/> <cb:practice name="napier"/> <cb:querent ref="#at"/> <cb:subject ref="#at" present="unclear"/> <cb:topic key="unspecifiedMedical" evidence="internal"><person sameAs="#at"/></cb:topic> <cb:judgment/> <cb:info type="urine"/> <cb:info type="event" subtype="unclear"/> </cb:consultation> </settingDesc>
NoteThis element (but not its content) is generated automatically before transcription begins.

<settlement>

<settlement> contains the settlement within which the original document’s respository is to be found. For Casebooks Project purposes, this is invariably Oxford.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Example
<msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 1r</idno> &Forman001; </msIdentifier>
NoteThis element is generated automatically before transcription begins.

<sex>

<sex> records a participant’s sex.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@resp) att.source (@source)
@evidenceexplains the grounds on which someone’s sex has been determined or conjectured if this is not apparent from the transcribed part of the entry. A value of internal means the relevant evidence is in the untranscribed part of the entry, external means it is somewhere external to the entry (including elsewhere in the casebooks), and conjecture means there is no concrete evidence but there are grounds for supposing one of the options to be likelier than the other.
Status Optional
Legal values are:
internalexternalconjecture
@cert(certainty) expresses the editor’s level of certainty about a deduced sex if there is any doubt.
Status Optional
Legal values are:
highmediumlow
@valuedefines the sex of an individual according to ISO 5218:2004. 1: Male (with M as content), 2: Female (with F as content) and 0: Unknown (with U as content).
Status Required
Legal values are:
120
Example
<sex value="1">M</sex>
Example
<sex value="2">F</sex>
Example
<sex value="0">U</sex>
NoteThe (male) authors of this document would like to stress that it is not they but the ISO that has deemed women to be ‘the second sex’.
In most cases, a person’s sex is evident from her or his forename, role name or occupation, or from the personal pronouns or Latin adjectives applied to her or him. Where such evidence appears in the untranscribed part of the entry, @evidence takes the value "internal". Beware, however, of ambiguous forenames: ‘Matthew’, for instance, may at this period be either male or female, while ‘Frances/Francis’ is almost invariably spelled ‘Frances’ by Forman and ‘Francis’ by Napier, irrespective of gender.
Typical grounds for invoking an @evidence value of conjecture are someone’s having an occupation that was largely but not wholly confined to one gender (millers, for instance, are at this period far likelier to be male but female millers are not unheard-of), or someone’s being referred to in the entry by their surname alone, with no forename or role name: in most but by no means all of the cases where it has proved possible to ascertain such a person’s gender, it is male.

<sic>

<sic> (Latin for ‘thus’) contains a text string as originally written but which appears to represent a mistake on the part of the author or scribe.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.responsibility (@cert, @resp) (att.source (@source))
Example
… her leg swelleth and hath an <choice><sic>issoe</sic><corr>issue</corr></choice> …
Example
… Ian Brown of <choice><sic>of</sic><corr type="noText"/></choice> Akely …
Example
<choice><orig><choice><sic>h</sic><corr>&SaturnSymbol;</corr></choice></orig><reg type="gloss">Saturday</reg></choice>
Note<sic> always precedes <corr> (containing the proposed correction) within <choice>.
Where the erroneous text comprises part of a longer word or numeral, the <sic> and <corr> elements should contain the whole word or numeral, even if only one character requires correction.
Where the content of <sic> is a symbol or abbreviation that would otherwise be supplied with an expansion using <orig>/<reg>, no regularisation is needed within <sic>, though if the content of <corr> is itself a symbol or abbreviation, the entire <choice> string becomes the content of the <orig> part of a further <choice> string with the regularisation of the corrected version forming the content of <corr> (see the third example above).

<signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<socecStatus>

<socecStatus> (socio-economic status) contains an informal description of a person's perceived social or economic status.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
@schemeidentifies the classification system or taxonomy in use, for example by pointing to a locally-defined <taxonomy> element or by supplying a URI for an externally-defined system.
Status Optional
@codeidentifies a status code defined within the classification system or taxonomy defined by the @scheme attribute.
Status Optional
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<sourceDesc>

<sourceDesc> (source description) contains the elements describing the source document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declarable
Example
<sourceDesc> <bibl type="positionOnPage">1B</bibl> <msDesc> <msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 1r</idno> &Forman001; </msIdentifier> <msContents> <msItem> <locus from="0001r" to="0001r"/> <title sameAs="#main_title"/> </msItem> </msContents> </msDesc> </sourceDesc>
NoteThis element is generated automatically before transcription begins.

<sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.ascribed (@who)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<space>

<space> indicates space deliberately left blank in the source text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.dimensions (@quantity, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@cert) att.source (@source)
@unitdefines the unit in which the space is measured. Permitted values: "chars" (characters), "words" or "lines".
Status Required
Legal values are:
charswordslines
@extentgives the number of units in question, expressed as an integer in Arabic numerals.
Status Required
@dim(dimension) indicates whether the space is horizontal or vertical.
Status Required
Legal values are:
horizontalvertical
Example
… my Ladye <space unit="chars" extent="6" dim="horizontal"/> Greeneway …
In this example (CASE30043) it seems likely that Napier had forgotten Lady Greenway’s first name and intended to supply it later, but never got round to doing so.
Example
<p>… <foreign xml:lang="la">qu&aelig;rit an sit <lb/>gravida</foreign></p> <space unit="lines" extent="5" dim="vertical"/> <p><lb/>Mrs Smith <lb/><foreign xml:lang="la">qu&aelig;rit an sit gravida</foreign> …</p>
NoteThere is no need to obsess about the precise length of a <space>: a reasonable approximation is quite sufficient.
Not to be confused with <gap>, which indicates material omitted from the transcription for whatever reason (usually because it is missing or illegible). <space> is for gaps deliberately left blank in the original.

<state>

<state> contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.typed (@type) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<subst>

<subst> (substitution) contains a deletion and an addition where the added text replaces the deleted text.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) )
Example
… Will: Bale of <subst><del type="strikethrough">Newport</del> <add place="supralinear">Emmertone</add></subst> …
Example
… March. 10 Monday h. <lb/><subst><del type="over">2</del><add place="over">3</add></subst>. 30 p m. 1600 …
Note<del> should always precede <add> within <subst>, even if the caret mark or other insertion indicator appears, physically, before the deleted text string.

<supplied>

<supplied> marks up text that is illegible or lost in the original but can be at least conjecturally supplied, with a @cert value of "high|medium|low" if there is any doubt.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.source (@source)
@cert(certainty) expresses the degree of certainty about the proposed completion, on a scale of hi, medium or low.
Status Optional
Legal values are:
lowmediumhigh
@resp(responsible party) indicates who is responsible for the proposed completion, if he or she wishes to be held responsible, expressed as the relevant @xml:id value preceded by a hash character.
Status Optional
@reasonexplains why the original is illegible. Permitted values: "binding" (text is lost in the gutter due to over-zealous binding), "bleedthrough", blot" (blotted), "blotDel" (text is obliterated by what could either be an accidental blot or a deliberate deletion), "code" (text is written in a code that we can decipher), "copy" (poor quality of the image being transcribed from), "damage" (manuscript damage), "del" (illegible deletion), "faded", "foxed", "hand" (indecipherably poor handwriting), "omitted" (text appears to have been omitted from the original document but we have no means of supplying it), "over" (text is impossible to read because it is written over other text — if it is impossible to read because other text is written over it, it counts as "del").
Status Required
Legal values are:
bindingbleedthroughblotblotDelcodecopydamagedelfadedfoxedomittedoverhand
Example
… Mary waller of B<supplied reason="binding" cert="high">ed</supplied><lb/>ford …

<surname>

<surname> (surname) contains a family name, with the optional @type values "adopted", "alternate", "deckname", "maiden", "maidenAlternate", "maidenVariant", "married", "marriedAlternate", "marriedVariant", "nickname", "variant" (see the Guidelines for advice on exactly when and how to apply these).
Attributesatt.casebooks.certainty (@evidence) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) )
@typeexplains the type of surname. Permitted values: "adopted", "alternate" (the second of two alternative surnames by which a person is referred to, where neither can be given any other @type value based on the evidence within that entry), "variant" (the second of two alternative surnames by which a person was known, where neither can be given any other @type value based on the evidence within that entry, and where the two surnames closely resemble one another but are sufficiently distinct not to be different spellings of the same name), "maiden" (the surname that a girl or woman inherited from her parents, sometimes still used after marriage), "married" (the surname taken by a woman on marriage to match her husband's), "deckname" (a false surname either given by a querent or used by a practitioner to conceal the person's identity), "nickname" (for the extremely unusual situation in which we know that a surname was informally bestowed rather than being inherited, a married name, or given to conceal the person's identity), "maidenAlternate" (the second of two alternative maiden names by which a girl or woman is referred to), "maidenVariant" (the second of two alternative maiden names by which a girl or woman is referred to, where the two surnames closely resemble one another but are sufficiently distinct not to be different spellings of the same name), "marriedAlternate" (the second of two alternative married names), or "marriedVariant" (the second of two alternative married names, where the two surnames closely resemble one another but are sufficiently distinct not to be different spellings of the same name). Typically in case files only alternate, married and maiden are needed; the others should not be used without clearance from a senior editor.
Status Optional
Legal values are:
adoptedalternatedecknamemaidenmaidenAlternatemaidenVariantmarriedmarriedAlternatemarriedVariantnicknamevariant
Example
<persName><forename>Elizabeth</forename> <surname>Blundell</surname></persName>
Example
<persName><roleName>Mrs</roleName> <surname type="married">Mansell</surname></persName>
NoteIf a surname is unclear or partially illegible in the original, the legible or conjecturable parts should be included in the header with appropriate <unclear>, <supplied> and/or <gap> elements.
@type takes the value "adopted" in the case of someone adopting a different surname (as opposed to acquiring one by marriage or being referred to under a false name). In the one instance in which this has arisen at the time of writing, a man took to using his mother’s maiden name to bolster his claim to her father’s estate, for which there were no immediate male heirs.

<table>

<table> contains text displayed in tabular form, in rows and columns.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@rowsindicates the number of rows in the table.
Status Optional
NoteIf no number is supplied, an application must calculate the number of rows.
Rows should be presented from top to bottom.
@cols(columns) indicates the number of columns in each row of the table.
Status Optional
NoteIf no number is supplied, an application must calculate the number of columns.
Within each row, columns should be presented left to right.
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<taxonomy>

<taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<taxonomy xml:id="tax.b"> <bibl>Brown Corpus</bibl> <category xml:id="tax.b.a"> <catDesc>Press Reportage</catDesc> <category xml:id="tax.b.a1"> <catDesc>Daily</catDesc> </category> <category xml:id="tax.b.a2"> <catDesc>Sunday</catDesc> </category> <category xml:id="tax.b.a3"> <catDesc>National</catDesc> </category> <category xml:id="tax.b.a4"> <catDesc>Provincial</catDesc> </category> <category xml:id="tax.b.a5"> <catDesc>Political</catDesc> </category> <category xml:id="tax.b.a6"> <catDesc>Sports</catDesc> </category> </category> <category xml:id="tax.b.d"> <catDesc>Religion</catDesc> <category xml:id="tax.b.d1"> <catDesc>Books</catDesc> </category> <category xml:id="tax.b.d2"> <catDesc>Periodicals and tracts</catDesc> </category> </category> </taxonomy>

<TEI>

<TEI> (TEI document) is the parent element containing the whole of the electronic file, both metadata and transcription.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@versionspecifies the major version number of the TEI Guidelines against which this document is valid.
Status Optional
NoteThe major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the @source of the <schemaSpec> element. The current version is P5.
NoteThis element is generated automatically before transcription begins.

<teiHeader>

<teiHeader> (TEI header) contains all the metadata pertaining to the document in question.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@typespecifies the kind of document to which the header is attached, for example whether it is a corpus or individual text.
Status Optional
Sample values include:
textcorpus
Example
<teiHeader> <fileDesc> <titleStmt> <title xml:id="main_title">CASE118</title> </titleStmt> <publicationStmt> <publisher>The Casebooks Project</publisher> <pubPlace>Cambridge</pubPlace> <date when="2010-07-05">05 July 2010</date> </publicationStmt> <sourceDesc> <bibl type="positionOnPage">2</bibl> <msDesc> <msIdentifier> <country>UK</country> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <collection>Ashmole Mss</collection> <idno n="234">MS Ashmole 234, f. 16r</idno> &Forman001; </msIdentifier> <msContents> <msItem> <locus from="0016r" to="0016r"/> <title sameAs="#main_title"/> </msItem> </msContents> </msDesc> </sourceDesc> </fileDesc> <profileDesc> <handNotes> <handNote sameAs="#sforman">Simon Forman</handNote> </handNotes> <langUsage> <language ident="en">English</language> </langUsage> <textClass xml:base="../05-master-lists/consultation-types.xml"> <catRef target="#horary"/> </textClass> <particDesc> <listPerson> <person xml:id="sforman"> <persName><forename>Simon</forename> <surname>Forman</surname></persName> <sex value="1">M</sex> </person> <person xml:id="jw"> <persName><forename>Joan</forename> <surname>Walker</surname></persName> <sex value="2">F</sex> <age value="17">17</age> <residence sameAs="#address1" key="databaseNormalizedIDKey"/> </person> </listPerson> </particDesc> <settingDesc> <p><date when="1596-04-14" n="Wednesday"/></p> <p><time when="09:10:00"/></p> <cb:consultation> <cb:consultant ref="#sforman"/> <cb:practice name="forman"/> <cb:querent ref="#jw"/> <cb:subject ref="#jw" present="unclear"/> <cb:topic key="diz" resp="#sforman"><person sameAs="#jw"/></cb:topic> <cb:judgment/> <cb:treatment/> </cb:consultation> </settingDesc> </profileDesc> <revisionDesc> <change when="2009-12-12">Data entered in Microsoft Excel spreadsheet by <name xml:id="rralley">Robert Ralley</name> as part of the Casebooks Pilot Project.</change> <change when="2010-07-05">XML file created by <name xml:id="mhawkins">Michael Hawkins</name> from Casebooks Pilot Project data.</change> <change when="2010-09-13">Transcribed by <name sameAs="#rralley">Robert Ralley</name>.</change> <change when="2010-10-03">Checked by <name xml:id="jyoung">John Young</name>.</change> <change when="2012-07-05">Facsimile coding added by <name>Michael Hawkins</name>.</change> </revisionDesc> </teiHeader>
NoteThis element is generated automatically before transcription begins, though several of its component parts need to be added or modified by the transcribers or editors, as explained in the documentation for the relevant elements.

<text>

<text> for Casebooks purposes, contains on the element <body>, which in turn contains the text of the transcribed document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.declaring (@decls) att.typed (@type)
Example
<text xml:lang="en"> <body> <div> <p><lb/>Mary my meaden <lb/>did send her water. <lb/>Decemb 1. Thursday hor. 8. 40 <lb/>am. 1603.</p> <p><lb/>payned mightily in her hed.</p> </div> </body> </text>
NoteThis element is generated automatically before transcription begins, though the @xml:lang value needs to be manually revised if the principal language of the text is not English.

<textClass>

<textClass> (text classification) serves, for Casebooks purposes, solely as a container for a single <catRef/> specifying the type of text in question.
Attributesatt.declarableatt.global (@xml:id, @n, @xml:lang, @rend, @xml:space) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs)
@xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Status Required
Example
<textClass xml:base="../05-master-lists/consultation-types.xml"> <catRef target="#horary"/> </textClass>
NoteThis element is generated automatically at the time of the file’s creation. Transcribers need only concern themselves with the @target value of <catRef/>.

<time>

<time> records the time of the consultation or of an event recorded in it, such as a birth, death or marriage. It is described in ISO format (hh:mm:ss) and may be expressed as a range if a precise time cannot be determined. It has no content.
Attributesatt.global (@xml:id, @n) att.global.linking (@corresp, @sameAs, @copyOf, @exclude) att.editLike (@evidence) att.dimensions (@precision) att.responsibility (@cert, @resp) att.source (@source)
@whendefines a specific time.
Status Optional
@notBeforedefines the earliest possible time or beginning of a time range where this is not known precisely.
Status Optional
@notAfterdefines the latest possible time or end of a time range where this is not known precisely.
Status Optional
@fromdefines the beginning of a time range.
Status Optional
@todefines the end of a time range.
Status Optional
Example
<time when="17:45:00"/>
Example
<time notBefore="08:00:00" notAfter="13:17:00"/>
This means ‘some time between 8:00 am and 1:17 pm on the same day’. Where a range of (for instance) some time between 8:00 am on one day and 1:17 pm on another is needed, this should be recorded using the @notBefore-custom and @notAfter-custom values on <date>.
Example
<time when="07:15:00" xml:id="time1" exclude="#time2"/> <time when="19:15:00" xml:id="time2" exclude="#time1"/>
This is typically used if the entry gives the time as ‘15 p. 7’ and there is no means of ascertaining whether this means 7:15 am or 7:15 pm.
Example
<time when="08:00:00" xml:id="time3" exclude="#time4"/> <time when="08:05:00" xml:id="time4" exclude="#time3"/>
This is typically used where conflicting times are recorded in the same entry.
NoteNo <time> element is needed if a time range has been specified by using the @from-custom, @to-custom, @notBefore-custom and/or @notAfter-custom attributes on <date>.
Seconds are only there to keep the ISO happy. Forman and Napier quite often specify times down to the minute, but never more precisely than that, so in practice the last two figures of @when, @notBefore, @notAfter etc. will always be 00.
Where two or more mutually exclusive times are recorded for a given consultation or event, or the time stated is open to two or more interpretations, the alternatives should both or all be given, using the @xml:id and @exclude mechanism as illustrated above and explained in more detail in the Guidelines.

<title>

<title> contains the title of the electronic document.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.canonical (@key, @ref)
@typeclassifies the title according to some convenient typology.
Status Optional
Sample values include:
mainsubaltshortdesc
NoteThis attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.
@levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Legal values are:
amjsu
NoteThe level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level a, and one appearing within a <series> element of level s. For this reason, the @level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.
Example
<title xml:id="main_title">CASE1</title>
NoteThis element is generated automatically before transcription begins, and its content automatically modified when a CASE number has been assigned to the entry in question.

<titleStmt>

<titleStmt> (title statement) for Casebooks Project purposes serves only as a container for the <title> element.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
Example
<titleStmt> <title xml:id="main_title">CASE1</title> </titleStmt>
NoteThis element is generated automatically before transcription begins.

<trait>

<trait> (trait) is currently only used, for Casebooks purposes, within <person> or (theoretically) <personGrp>, where a person or group is described in an entry in terms of place of origin or regional affiliation. It takes the @type value "regionalIdentity" and contains <desc>, which in turn contains a succinct natural-language account of that identity, e.g. ‘Devonshire woman’, ‘Frenchman’.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) ) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
@typedescribes the type of trait being defined, the only currently permissible value being "regionalIdentity".
Status Required
Legal values are:
regionalIdentity
Example
<trait type="regionalIdentity"><desc>Kentish man</desc></trait>
NoteNot to be confused with <residence>, which defines someone’s current place of residence, whether or not this is the same as her or his place of origin. A Welshman living in Milton Keynes has ‘Welshman’ as a regional identity and ‘Milton Keynes’ as an address. In the above example (CASE8592) the person is described in the text as ‘a Kintesh man in Canterbery’.
This element is used only rarely, where there is an explicit statement of regional identity in the original record.

<unclear>

<unclear> denotes uncertain readings, with a @reason value indicating the reason for the uncertainty and a @cert value expressing the transcriber’s confidence in her or his reading on a scale of "high|mediumlow".
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.editLike (@evidence) att.dimensions (@unit, @quantity, @extent, @precision, @scope) att.ranging (@atLeast, @atMost) att.responsibility (@resp) att.source (@source)
@cert(certainty) indicates the degree of certainty associated with the data recorded by the element on a scale of hi, medium or low.
Status Required
Legal values are:
lowmediumhigh
@reasonPermitted values: "binding" (text is lost in the gutter due to over-zealous binding), "bleedthrough", "blot" (blotted), "blotDel" (text is obliterated by what could either be an accidental blot or a deliberate deletion), "code" (text is written in a code that we can only conjecturally decipher), "copy" (poor quality of the image being transcribed from), "damage" (manuscript damage), "del" (deletion),"faded", "foxed", "hand" (poor handwriting), "over" (text is hard to read because it is written over other text — if it is hard to read because other text is written over it, it counts as "del").
Status Required
Legal values are:
bindingbleedthroughblotblotDelcodecopydamagedelfadedfoxedoverhand
Example
<p>… qu&aelig;rit quis ei <lb/><unclear cert="high" reason="binding">s</unclear>urripuit argentum …</p>

<variantEncoding/>

<variantEncoding/> declares the method used to encode text-critical variants.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change)
@methodindicates which method is used to encode the apparatus of variants.
Status Required
Legal values are:
location-referenceddouble-end-pointparallel-segmentation
NoteThe value parallel-segmentation requires in-line encoding of the apparatus.
@locationindicates whether the apparatus appears within the running text or external to it.
Status Required
Legal values are:
internalexternal
NoteThe value external is inconsistent with the parallel-segmentation method of apparatus markup.
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<witEnd/>

<witEnd/> (fragmented witness end) indicates the end, or suspension, of the text of a fragmentary witness.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.rdgPart (@wit)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<witness>

<witness> contains either a description of a single witness referred to within the critical apparatus, or a list of witnesses which is to be referred to by a single sigil.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.sortable (@sortKey)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

<witStart/>

<witStart/> (fragmented witness start) indicates the beginning, or resumption, of the text of a fragmentary witness.
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude)) (att.global.facs (@facs)) (att.global.change) att.rdgPart (@wit)
NoteThis element is not currently used by the Casebooks Project. If you feel that this element is necessary, please consult the senior editors.

Model classes

model.addressLike

model.addressLike groups elements used to represent a postal or e-mail address. [1. ]
Used bymodel.pPart.data
Membersaffiliation

model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. ]
Used by
Membersmodel.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] state trait] idno rs]

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.11. ]
Used byevent model.inter model.msItemPart model.personPart org place sourceDesc state taxonomy trait
Membersbibl msDesc

model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.11. ]
Used bybibl
Membersmodel.imprintPart [pubPlace publisher] model.respLike [author funder] bibl listRelation msIdentifier

model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. ]
Used bychoice
Membersabbr corr ex expan orig reg seg sic unclear

model.common

model.common groups common chunk- and inter-level elements. [1.3. ]
Used byargument body div figure postscript
Membersmodel.divPart [model.lLike [l] model.pLike [ab p] lg sp] model.inter [model.biblLike [bibl msDesc] model.labelLike [desc] model.listLike [list listEvent listOrg listPerson listPlace listWit table] model.qLike [model.quoteLike [quote] q] model.stageLike]
NoteThis class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

model.dateLike

model.dateLike groups elements containing temporal expressions. [3.5.4. 13.3.6. ]
Used bymodel.pPart.data
Membersdate time

model.descLike

model.descLike groups elements which contain a description of their function.
Used bycategory gap graphic media space taxonomy
Membersdesc

model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. ]
Used bybody div figure lg list table
Membersmodel.divBottomPart [closer postscript signed] model.divWrapper [argument byline dateline salute]

model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. ]
Used bymodel.divBottom postscript
Memberscloser postscript signed

model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Used bybody div
Membersdiv

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. ]
Used bymacro.specialPara model.common
Membersmodel.lLike [l] model.pLike [ab p] lg sp
NoteNote that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. ]
Used bybody div lg list
Membersmodel.divTopPart [model.headLike [head] opener signed] model.divWrapper [argument byline dateline salute]

model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. ]
Used bymodel.divTop postscript
Membersmodel.headLike [head] opener signed

model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. ]
Used bymodel.divBottom model.divTop
Membersargument byline dateline salute

model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. ]
Used bymodel.highlighted model.limitedPhrase
Membersforeign title

model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Used byencodingDesc
MembersvariantEncoding

model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. ]
Used bymodel.global
MembersaddSpan gap space

model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. ]
Used bymodel.global
Memberslink
NoteElements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.9. ]
Used byfacsimile figure model.phrase table
Membersformula graphic media

model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Used byargument event figure listEvent listOrg listPerson listPlace listWit model.divTopPart msDesc org place state table trait
Membershead

model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. ]
Used bybibl model.phrase
Membersmodel.emphLike [foreign title] model.hiLike [hi]

model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. ]
Used bymodel.highlighted model.limitedPhrase model.linePart
Membershi

model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. ]
Used bymodel.biblPart
MemberspubPlace publisher

model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. ]
Used byhead lem macro.limitedContent macro.paraContent macro.specialPara model.common rdg
Membersmodel.biblLike [bibl msDesc] model.labelLike [desc] model.listLike [list listEvent listOrg listPerson listPlace listWit table] model.qLike [model.quoteLike [quote] q] model.stageLike

model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Used byevent lg model.inter org place state trait
Membersdesc

model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Used by
Membersmodel.hiLike [hi] model.pPart.transcriptional [add app corr del handShift orig reg sic supplied unclear] model.segLike [seg] choice

model.listLike

model.listLike groups list-like elements. [3.7. ]
Used bymodel.inter sourceDesc sp
Memberslist listEvent listOrg listPerson listPlace listWit table

model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Used byhead lg model.divPart sp
Membersl

model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. ]
Used bymodel.pPart.data
Membersgeo num

model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. 3.10.3. ]
Used bymodel.global subst
Membersanchor cb fw lb milestone pb

model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Used bymsItem
Membersmodel.biblLike [bibl msDesc] model.msQuoteLike [incipit title] model.quoteLike [quote] model.respLike [author funder] idno msItem

model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Used bymodel.msItemPart
Membersincipit title

model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Used bymodel.addrPart model.pPart.data org
Membersmodel.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] state trait] idno rs
NoteA superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. ]
Used bymodel.nameLike
Membersname orgName persName
NoteThis class is used in the content model of elements which reference names of people or organizations.

model.noteLike

model.noteLike groups globally-available note-like elements. [3.8. ]
Used byevent model.global notesStmt org place state trait
Membersnote

model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. ]
Used bymodel.nameLike
MembersgeogFeat

model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Used byorg
MemberslistOrg listPerson listPlace

model.orgStateLike

model.orgStateLike groups elements describing changeable characteristics of an organization which have a definite duration.
Used by
Membersstate

model.persEventLike

model.persEventLike groups elements describing specific events in a person's history, for example birth, marriage, or appointment.
Used bymodel.personPart
Membersbirth death event listEvent
NoteThese are not characteristics of an individual, but often cause an individual to gain such characteristics, or to enter a new state.

model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. ]
Used bymodel.nameLike
MembersaddName forename genName nameLink roleName surname

model.personLike

model.personLike groups elements which provide information about people and their relationships.
Used bylistPerson org particDesc
Membersorg person personGrp

model.personPart

model.personPart groups elements which form part of the description of a person. [15.2.2. ]
Used byperson personGrp
Membersmodel.biblLike [bibl msDesc] model.persEventLike [birth death event listEvent] model.persStateLike [affiliation age education faith floruit occupation persName residence sex socecStatus state trait] idno

model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Used bymodel.personPart
Membersaffiliation age education faith floruit occupation persName residence sex socecStatus state trait
NoteThese characteristics of an individual are typically a consequence of their own action or that of others.

model.placeEventLike

model.placeEventLike groups elements which describe events at or affecting a place.
Used byplace
Membersevent

model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Used bylistPlace org place settingDesc
Membersplace

model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. ]
Used bymodel.placeStateLike msIdentifier
Memberscountry district geogName placeName region settlement

model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Used bymodel.nameLike place
Membersmodel.placeNamePart [country district geogName placeName region settlement] state trait

model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. ]
Used by
Membersargument byline head

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. ]
Used bybibl model.phrase
Membersmodel.pPart.editorial [abbr choice ex expan subst] model.pPart.transcriptional [add app corr del handShift orig reg sic supplied unclear]

model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. ]
Used bymodel.limitedPhrase model.pPart.edit
Membersabbr choice ex expan subst

model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. ]
Used bymodel.limitedPhrase model.phrase
Memberslocus

model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. ]
Used bymodel.linePart model.pPart.edit
Membersadd app corr del handShift orig reg sic supplied unclear

model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Used byprofileDesc
MembershandNotes langUsage particDesc settingDesc textClass

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.6. ]
Used bybibl model.limitedPhrase model.phrase
Membersref

model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. ]
Used bypublicationStmt
Memberspublisher
NoteThe agency child elements, while not required, are required if one of the detail child elements is to be used. It is not valid to have a detail child element without a preceding agency child element.
See also model.publicationStmtPart.detail.

model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. ]
Used bypublicationStmt
Membersdate idno pubPlace
NoteA detail child element may not occur unless an agency child element precedes it.
See also model.publicationStmtPart.agency.

model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. ]
Used bymodel.inter sp
Membersmodel.quoteLike [quote] q

model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Used bymodel.msItemPart model.qLike
Membersquote

model.rdgLike

model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation. [12.1. ]
Used byapp
Membersrdg
NoteThis class allows for variants of the <rdg> element to be easily created via TEI customizations.

model.rdgPart

model.rdgPart groups elements which mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. ]
Used bylem rdg
MemberslacunaEnd lacunaStart witEnd witStart
NoteThese elements may appear anywhere within the elements <lem> and <rdg>, and also within any of their constituent elements.

model.resourceLike

model.resourceLike groups non-textual elements which may appear together with a header and a text to constitute a TEI document. [1.3. ]
Used byTEI
Membersfacsimile

model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Used bymodel.biblPart model.msItemPart titleStmt
Membersauthor funder

model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. 17.1. ]
Used bybibl model.linePart model.phrase
Membersseg
NoteThe principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Used byteiHeader
MembersencodingDesc profileDesc

model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. ]
Used bymsItem
Membersargument byline graphic

Attribute classes

att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [1. ]
Memberschange q sp
Attributes
@whoindicates the person, or group of people, to whom the element content is ascribed.
Status Optional
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the @who attribute.
<castItem type="role"> <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role"> <role xml:id="Francisco">Francisco</role> <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo"> <speaker>Bernardo</speaker> <l n="1">Who's there?</l> </sp> <sp who="#Francisco"> <speaker>Francisco</speaker> <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
NoteFor transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

att.breaking

att.breaking provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. ]
Memberscb lb milestone pb
Attributes
@breakindicates 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.
Status Recommended
Sample values include
yesnomaybe

att.canonical

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Membersatt.naming [att.personal [addName forename genName name orgName persName placeName roleName surname] affiliation author collection country district education geogFeat geogName occupation pubPlace region repository rs settlement socecStatus state trait] faith funder relation title
Attributes
@keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
<author> <name key="name 427308" type="organisation">[New Zealand Parliament, Legislative Council]</name> </author>
NoteThe value may be a unique identifier from a database, or any other externally-defined string identifying the referent.
No particular syntax is proposed for the values of the @key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a @ref attribute whose value is a tag URI as defined in RFC 4151.
@ref(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Status Optional
<name ref="http://viaf.org/viaf/109557338" type="person">Seamus Heaney</name>
NoteThe value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

att.casebooks.certainty

att.casebooks.certainty provides the attributes necessary for coding certainty.
MembersaddName cb:item cb:location forename genName cb:info cb:judgment nameLink cb:practice cb:recipe roleName surname cb:topic cb:treatment
Attributesatt.responsibility (@cert, @resp) (att.source (@source))
@evidence
Status Optional
Legal values are:
internalexternalinferredconjecture

att.casebooks.linking

att.casebooks.linking provides attributes necessary for coding mutually exclusive elements.
Memberscb:object cb:querent cb:subject
Attributes
@excludepoints to elements that are in exclusive alternation with the current element.
Status Optional
@xml:id(identifier)
Status Optional

att.casebooks.minimal.responsibility

att.casebooks.minimal.responsibility provides attributes indicating who is responsible for something asserted by the markup and the degree of certainty associated with it.
Membersatt.casebooks.participants.certainty [att.casebooks.participants [cb:consultant cb:messenger cb:subject] cb:object]
Attributes
@cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
@resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional

att.casebooks.participants

att.casebooks.participants provides the attributes for <cb:consultant>, <cb:querent>, <cb:subject> and <cb:messenger>.
Memberscb:consultant cb:messenger cb:subject
Attributesatt.casebooks.participants.certainty (@evidence) (att.casebooks.minimal.responsibility (@cert, @resp))
@reasonPlacement
Status Optional
Legal values are:
deletednotGivenmsDamagenotUnderstood
@presentpresent
Status Optional
Legal values are:
yesnounclear
@ref(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Status Required
NoteThe value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

att.casebooks.participants.certainty

att.casebooks.participants.certainty provides the attributes necessary for coding certainty.
Membersatt.casebooks.participants [cb:consultant cb:messenger cb:subject] cb:object
Attributesatt.casebooks.minimal.responsibility (@cert, @resp)
@evidence
Status Optional
Legal values are:
internalexternalinferredconjecture

att.cReferencing

att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.
Membersref
Attributes
@cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
Status Optional
NoteThe value of @cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.6.) is applied to it the result is a valid URI reference to the intended target
The <refsDecl> to use may be indicated with the @decls attribute.
Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
Membersaffiliation age change country district education faith floruit geogFeat geogName name occupation orgName persName placeName region relation settlement sex socecStatus state trait
Attributesatt.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
@calendarindicates the system or calendar to which the date represented by the content of this element belongs.
Status Optional
He was born on <date xmlns:sch="http://purl.oclc.org/dsdl/schematron" calendar="#Gregorian">Feb. 22, 1732</date> (<date xmlns:sch="http://purl.oclc.org/dsdl/schematron" calendar="#Julian" when="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).
@periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
Status Optional
NoteThis superclass provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.6. ]
Membersatt.datable [affiliation age change country district education faith floruit geogFeat geogName name occupation orgName persName placeName region relation settlement sex socecStatus state trait]
Attributes
@when-customsupplies the value of a date or time in some standard form.
Status Optional
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06" when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH </date>.</p> <p>The current world will end at the <date when="2012-12-21" when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date></p>
Not all custom date formulations will have Gregorian equivalents.The @when-custom attribute and other custom dating are not contrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
@notBefore-customspecifies the earliest possible date for the event in some custom standard form.
Status Optional
@notAfter-customspecifies the latest possible date for the event in some custom standard form.
Status Optional
@from-customindicates the starting point of the period in some standard form.
Status Optional
<event xml:id="FIRE1" datingMethod="#julian" from-custom="1666-09-02" to-custom="1666-09-05"> <head>The Great Fire of London</head> <p>The Great Fire of London burned through a large part of the city of London.</p> </event>
@to-customindicates the ending point of the period in some standard form.
Status Optional
@datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Status Optional
@datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date when-custom="1598" calendar="#julian" datingMethod="#julian">1598</date>. by Iohn Stow Citizen of London.
NoteHere the @calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the @datingMethod attribute also points to the Julian calendar to indicate that the content of the @when-custom attribute value is Julian too.

att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601 standard. [13.3.6. ]
Membersatt.datable [affiliation age change country district education faith floruit geogFeat geogName name occupation orgName persName placeName region relation settlement sex socecStatus state trait]
Attributes
@when-isosupplies the value of a date or time in a standard form.
Status Optional
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> <time when-iso="03:00">3 A.M.</time> <time when-iso="14">around two</time> <time when-iso="15,5">half past three</time>
All of the examples of the @when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q><time when-iso="12">around noon</time></q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the @when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes specification. The first occurence could not.
NoteThe value of the @when-iso attribute should be the normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601, using the Gregorian calendar.
@notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
@notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
@from-isoindicates the starting point of the period in standard form.
Status Optional
@to-isoindicates the ending point of the period in standard form.
Status Optional
NoteIf both @when-iso and @dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01" dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a regularized form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. 13.3.6. ]
Membersatt.datable [affiliation age change country district education faith floruit geogFeat geogName name occupation orgName persName placeName region relation settlement sex socecStatus state trait]
Attributes
@whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Examples of W3C date, time, and date & time formats.
<p> <date when="1945-10-24">24 Oct 45</date> <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date> <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time> <time when="14:12:38">fourteen twelve and 38 seconds</time> <date when="1962-10">October of 1962</date> <date when="--06-12">June 12th</date> <date when="---01">the first of the month</date> <date when="--08">August</date> <date when="2006">MMVI</date> <date when="0056">AD 56</date> <date when="-0056">56 BC</date></p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#Julian" when="1632-06-06">27th of May (old style)</date>.
<opener><dateline><placeName>Dorchester, Village,</placeName><date when="1828-03-02">March 2d. 1828.</date></dateline><salute>To Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
NoteThe value of the @when attribute should be the normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.
The most commonly-encountered format for the date part of the @when attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.
Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.
@notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
@notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
@fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
@toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Example
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>

att.datcat

att.datcat provides the @dcr:datacat and @dcr:ValueDatacat attributes which are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. [9.5.2. 18.3. ]
Membersatt.segLike [seg]
Attributes
@datcatcontains a PID (persistent identifier) that aligns the given element with the appropriate Data Category (or categories) in ISOcat.
Status Optional
@valueDatcatcontains a PID (persistent identifier) that aligns the content of the given element or the value of the given attribute with the appropriate simple Data Category (or categories) in ISOcat.
Status Optional
ExampleIn this example @dcr:datcat relates the feature name to the data category "partOfSpeech" and @dcr:valueDatcat the feature value to the data category "commonNoun". Both these data categories reside in the ISOcat DCR at www.isocat.org, which is the DCR used by ISO TC37 and hosted by its registration authority, the MPI for Psycholinguistics in Nijmegen.
<fs xmlns:dcr="http://www.isocat.org/ns/dcr"> <f name="POS" dcr:datcat="http://www.isocat.org/datcat/DC-1345" fVal="#commonNoun" dcr:valueDatcat="http://www.isocat.org/datcat/DC-1256"/> </fs>
NoteISO 12620:2009 is a standard describing the data model and procedures for a Data Category Registry (DCR). Data categories are defined as elementary descriptors in a linguistic structure. In the DCR data model each data category gets assigned a unique Peristent IDentifier (PID), i.e., an URI. Linguistic resources or preferably their schemas that make use of data categories from a DCR should refer to them using this PID. For XML-based resources, like TEI documents, ISO 12620:2009 normative Annex A gives a small Data Category Reference XML vocabulary (also available online at http://www.isocat.org/12620/), which provides two attributes, @dcr:datcat and @dcr:valueDatcat.

att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose @decls attribute.
Membersbibl langUsage listEvent listOrg listPerson listPlace particDesc settingDesc sourceDesc textClass
Attributes

att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. ]
Membersab body div facsimile geo graphic lg media p ref text
Attributes
@declsidentifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
NoteThe rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3..

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Membersatt.editLike [att.transcriptional [add addSpan subst] affiliation corr education ex expan faith floruit geogName name occupation org orgName persName place placeName reg residence socecStatus state trait]
Attributesatt.ranging (@atLeast, @atMost)
@unitnames the unit used for the measurement
Status Optional
Suggested values include:
cmmminlineschars
@quantityspecifies the length in the units specified
Status Optional
@extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Status Optional
<gap extent="5 words"/>
<height extent="half the page"/>
@precisioncharacterizes the precision of the values specified by the other attributes.
Status Optional
@scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Sample values include:
allmostrange

att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. ]
Membersdiv lg
Attributesatt.fragmentable (@part)
@org(organization) specifies how the content of the division is organized.
Status Optional
Legal values are:
compositeuniform
@sampleindicates whether this division is a sample of the original source and if so, from which part.
Status Optional
Legal values are:
initialmedialfinalunknowncomplete

att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Membersbibl change revisionDesc
Attributes

att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Memberscb lb milestone pb
Attributes
@edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status Optional

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind.
Membersatt.transcriptional [add addSpan subst] affiliation corr education ex expan faith floruit geogName name occupation org orgName persName place placeName reg residence socecStatus state trait
Attributesatt.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) att.responsibility (@cert, @resp) (att.source (@source))
@evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Legal values are:
internalexternalinferredconjecture

att.fragmentable

att.fragmentable groups structural elements which may be fragmented, usually as a consequence of some overlapping hierarchy.
Membersatt.divLike [div lg] att.segLike [seg] ab l p
Attributes
@partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Legal values are:
YNIMF
NoteThe values I, M, or F should be used only where it is clear how the element may be be reconstituted.

att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
MembersTEI ab abbr add addName addSpan affiliation age anchor app argument author bibl body byline catDesc catRef category cell change choice closer collection corr country dateline del desc district div education encodingDesc ex expan facsimile faith figDesc figure fileDesc floruit forename formula funder fw gap genName geo geogFeat geogName graphic handNote handNotes handShift idno incipit item l lacunaEnd lacunaStart langUsage language lb lem lg link list listEvent listOrg listPerson listPlace listRelation listWit locus media msContents msDesc msIdentifier msItem name nameLink notesStmt num occupation opener org orgName orig particDesc persName personGrp place placeName postscript profileDesc pubPlace publicationStmt publisher q quote rdg ref reg region relation repository revisionDesc roleName row rs salute seg settingDesc settlement sex sic signed socecStatus sourceDesc sp space state subst supplied surname table taxonomy teiHeader text title titleStmt trait unclear variantEncoding witEnd witStart witness
Attributesatt.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude) att.global.facs (@facs) att.global.change
@xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
NoteThe @xml:id attribute may be used to specify a canonical reference for an element; see section 3.10..
@n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
NoteThe value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.
@xml:lang(language) indicates the language of the element content using a tag generated according to BCP 47.
Status Optional
<p> … The consequences of this rapid depopulation were the loss of the last or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
NoteThe xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.
The authoritative list of registered language subtags is maintained by IANA and is available at . For a good general overview of the construction of language tags, see , and for a practical step-by-step guide, see .
The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its @ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their Internet Engineering Task Force definitions.
@rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
<head rend="align(center) case(allcaps)"><lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/><hi rend="case(mixed)">New Blazing-World</hi>. </head>
NoteThese Guidelines make no binding recommendations for the values of the @rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the @rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.
@xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Status Optional
<div type="bibl"> <head>Bibliography</head> <listBibl xml:base="http://www.lib.ucdavis.edu/BWRP/Works/"> <bibl> <author> <name>Landon, Letitia Elizabeth</name> </author> <ref target="LandLVowOf.sgm"> <title>The Vow of the Peacock</title> </ref> </bibl> <bibl> <author> <name>Compton, Margaret Clephane</name> </author> <ref target="NortMIrene.sgm"> <title>Irene, a Poem in Six Cantos</title> </ref> </bibl> <bibl> <author> <name>Taylor, Jane</name> </author> <ref target="TaylJEssay.sgm"> <title>Essays in Rhyme on Morals and Manners</title> </ref> </bibl> </listBibl> </div>
@xml:spacesignals an intention about how white space should be managed by applications.
Status Optional
Legal values are:
defaultpreserve
NoteThe XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

att.global.linking

att.global.linking defines a set of attributes for hypertextual linking.
Membersatt.global [TEI ab abbr add addName addSpan affiliation age anchor app argument author bibl body byline catDesc catRef category cell change choice closer collection corr country dateline del desc district div education encodingDesc ex expan facsimile faith figDesc figure fileDesc floruit forename formula funder fw gap genName geo geogFeat geogName graphic handNote handNotes handShift idno incipit item l lacunaEnd lacunaStart langUsage language lb lem lg link list listEvent listOrg listPerson listPlace listRelation listWit locus media msContents msDesc msIdentifier msItem name nameLink notesStmt num occupation opener org orgName orig particDesc persName personGrp place placeName postscript profileDesc pubPlace publicationStmt publisher q quote rdg ref reg region relation repository revisionDesc roleName row rs salute seg settingDesc settlement sex sic signed socecStatus sourceDesc sp space state subst supplied surname table taxonomy teiHeader text title titleStmt trait unclear variantEncoding witEnd witStart witness]
Attributes
@corresp(corresponds) points to elements that correspond to the current element in some way.
Status Optional
<group> <text xml:id="t1-g1-t2" xml:lang="en"> <body xml:id="t1-g1-t2-body1" corresp="#t1-g1-t1-body1"> <div type="chapter"> <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head> <p>…</p> </div> </body> </text> </group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using @corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the @corresp and the tag pointed to by the @corresp inherit the value from their immediate parent.
<!-- In a placeography --> <place xml:id="LOND1" corresp="#LOND2 #GENI1"> <placeName>London</placeName> <desc>The city of London...</desc> </place> <!-- In a literary personography --> <person xml:id="LOND2" corresp="#LOND1 #GENI1"> <persName type="lit">London</persName> <note> <p>Allegorical character representing the city of <ref target="LOND1.xml">London</ref>.</p> </note> </person> <person xml:id="GENI1" corresp="#LOND1 #LOND2"> <persName type="lit">London’s Genius</persName> <note> <p>Personification of London’s genius. Appears as an allegorical character in mayoral shows.</p> </note> </person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
@synch(synchronous) points to elements that are synchronous with the current element.
Status Optional
@sameAspoints to an element that is the same as the current element.
Status Optional
@copyOfpoints to an element of which the current element is a copy.
Status Optional
NoteAny content of the current element should be ignored. Its true content is that of the element being pointed at.
@nextpoints to the next element of a virtual aggregate of which the current element is part.
Status Optional
@prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
@excludepoints to elements that are in exclusive alternation with the current element.
Status Optional

att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. ]
MembershandNote handShift
Attributes
@scribegives a name or other identifier for the scribe believed to be responsible for this hand.
Status Optional
@scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
Status Optional
@scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
Status Optional
@scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
Status Optional
@mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
Status Optional
@scopespecifies how widely this hand is used in the manuscript.
Status Optional
Legal values are:
solemajorminor
NoteUsually either @script or @scriptRef, and similarly, either @scribe or @scribeRef, will be supplied.

att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Membersatt.media [graphic] ref
Attributes
@mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
ExampleIn this example @mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8" target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/>
NoteThis attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The @mimeType attribute must have a value taken from this list.

att.media

att.media provides attributes for specifying display and related properties of external media.
Membersgraphic
Attributesatt.internetMedia (@mimeType)
@widthWhere the media are displayed, indicates the display width
Status Optional
@heightWhere the media are displayed, indicates the display height
Status Optional
@scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
Status Optional

att.milestoneUnit

att.milestoneUnit provides an attribute to indicate the type of section which is changing at a specific milestone. [3.10.3. 2.3.6.3. 2.3.6. ]
Membersmilestone
Attributes
@unitprovides a conventional name for the kind of section changing at this milestone.
Status Required
Suggested values include:
pagecolumnlinebookpoemcantospeakerstanzaactscenesectionabsentunnumbered
NoteIf the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of @unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next <milestone/> tag for the edition in question is encountered.
In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. ]
Membersincipit msContents msItem quote
Attributes
@defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Status Optional
Default false
NoteIn the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. 13.3.5. ]
Membersatt.personal [addName forename genName name orgName persName placeName roleName surname] affiliation author collection country district education geogFeat geogName occupation pubPlace region repository rs settlement socecStatus state trait
Attributesatt.canonical (@key, @ref)
@rolemay be used to specify further information about the entity referenced by this name, for example the occupation of a person, or the status of a place.
Status Optional
@nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
NoteThe value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. ]
MembersaddName forename genName name orgName persName placeName roleName surname
Attributesatt.naming (@role, @nymRef) (att.canonical (@key, @ref))
@fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Legal values are:
yesabbinit
@sortspecifies the sort order of the name component in relation to others within the name.
Status Optional

att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears.
Membersfigure fw note
Attributes
@placePlacement
Status Recommended
Suggested values include:
inlinesupralinearinfralinearinterlinearovermarginRightmarginLeftlineBeginninglineEndpageBottompageTopchart
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

att.pointing

att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references.
Memberslink locus note
Attributes
@targetspecifies the destination of the reference by supplying one or more URI References
Status Optional
NoteOne or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

att.ranging

att.ranging provides attributes for describing numerical ranges.
Membersatt.dimensions [att.editLike [att.transcriptional [add addSpan subst] affiliation corr education ex expan faith floruit geogName name occupation org orgName persName place placeName reg residence socecStatus state trait] ] num
Attributes
@atLeastgives a minimum estimated value for the approximate measurement.
Status Optional
@atMostgives a maximum estimated value for the approximate measurement.
Status Optional

att.rdgPart

att.rdgPart attributes for elements which mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. ]
MemberslacunaEnd lacunaStart witEnd witStart
Attributes
@wit(witness or witnesses) contains a space-delimited list of one or more sigla indicating the witnesses to this reading beginning or ending at this point.
Status Optional
NoteThese elements may appear anywhere within the elements <lem> and <rdg>, and also within any of their constituent elements.

att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Membersgraphic media
Attributes
@url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
Status Required

att.responsibility

att.responsibility provides attributes indicating who is responsible for something asserted by the markup and the degree of certainty associated with it.
Membersatt.casebooks.certainty [addName cb:item cb:location forename genName cb:info cb:judgment nameLink cb:practice cb:recipe roleName surname cb:topic cb:treatment] att.editLike [att.transcriptional [add addSpan subst] affiliation corr education ex expan faith floruit geogName name occupation org orgName persName place placeName reg residence socecStatus state trait] att.textCritical [lem] abbr catRef handShift note orig seg sic
Attributesatt.source (@source)
@cert(certainty) indicates the degree of certainty associated with the data recorded by the element on a scale of hi, medium or low.
Status Optional
Legal values are:
lowmediumhigh
@resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. 17.1. ]
Membersseg
Attributesatt.datcat (@datcat, @valueDatcat) att.fragmentable (@part)
@functioncharacterizes the function of the segment.
Status Optional
NoteAttribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content.
Membersbibl event idno item list listEvent listOrg listPerson listPlace listRelation listWit msDesc org person personGrp place relation witness
Attributes
@sortKeysupplies the sort key for this element in an index, list or group which contains it.
Status Optional
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES"><term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term></index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
NoteThis attribute is only used in the topics master list

att.source

att.source provides attributes for pointing to the source of a bibliographic reference. [3.3.3. 8.3.4. ]
Membersatt.responsibility [att.casebooks.certainty [addName cb:item cb:location forename genName cb:info cb:judgment nameLink cb:practice cb:recipe roleName surname cb:topic cb:treatment] att.editLike [att.transcriptional [add addSpan subst] affiliation corr education ex expan faith floruit geogName name occupation org orgName persName place placeName reg residence socecStatus state trait] att.textCritical [lem] abbr catRef handShift note orig seg sic] q quote
Attributes
@sourceprovides a pointer to the bibliographical source from which a quotation or citation is drawn.
Status Optional
Example
<p><!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested term.</quote> <!-- ... --></p>
Example
<p> <!-- ... --> <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the less we seem to know.</quote> <!-- ... --></p> <!-- ... --> <bibl xml:id="chicago_15_ed"><title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>

att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [1.3.1. ]
MembersaddSpan cb lb milestone pb
Attributes
@spanToindicates the end of a span initiated by the element bearing this attribute.
Status Optional
NoteThe span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the @spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. ]
Memberscell row
Attributes
@roleindicates the kind of information held in this cell or in each cell of this row.
Status Optional
Suggested values include:
labeldata
NoteWhen this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the @role attribute of the parent <row> element.
@rowsindicates the number of rows occupied by this cell or row.
Status Optional
Default 1
NoteA value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.
@cols(columns) indicates the number of columns occupied by this cell or row.
Status Optional
Default 1
NoteA value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

att.textCritical

att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work. [12.1. ]
Memberslem
Attributesatt.responsibility (@cert, @resp) (att.source (@source))
@typeclassifies the reading according to some useful typology.
Status Optional
Sample values include:
substantiveorthographic
@causeclassifies the cause for the variant reading, according to any appropriate typology of possible origins.
Status Optional
Sample values include:
homeoteleutonhomeoarchypaleographicConfusionhaplographydittographyfalseEmendation
@varSeq(variant sequence) provides a number indicating the position of this reading in a sequence, when there is reason to presume a sequence to the variants.
Status Optional
NoteDifferent variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More complex variant sequences, with (for example) multiple branchings from single readings, may be expressed through the <join> element.
@handindicates the hand responsible for a particular reading in the witness.
Status Optional
NoteThis attribute is only available within an apparatus gathering variant readings in the transcription of an individual witness. It may not occur in an apparatus gathering readings from different witnesses.
NoteThis element class defines attributes inherited by <rdg>, <lem>, and <rdgGrp>.

att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. ]
Membersmedia
Attributes
@startindicates the location within a temporal alignment at which this element begins.
Status Optional
NoteIf no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.
@endindicates the location within a temporal alignment at which this element ends.
Status Optional
NoteIf no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [1. ]
Membersadd addSpan subst
Attributesatt.editLike (@evidence) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost)) ) (att.responsibility (@cert, @resp) (att.source (@source)) )
@handindicates the hand of the agent which made the intervention.
Status Optional
@statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
Status Optional
Sample values include:
duplicateduplicate-partialexcessStartexcessEndshortStartshortEndpartialunremarkable
NoteStatus information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.
Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.
@causedocuments the presumed cause for the intervention.
Status Optional
Legal values are:
fixunclear
@seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
Status Mandatory when applicable

att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Membersdesc
Attributes
@versionDatespecifies the date on which the source text was extracted and sent to the translator
Status Optional
NoteThe @versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the @versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way.
Membersab add addName addSpan altIdentifier anchor cb change collection country date desc district div figure geogFeat geogName graphic head incipit lb lg link listEvent listOrg listPerson listPlace listRelation media milestone msDesc name note org orgName pb place placeName quote ref region seg settlement state text
Attributes
@typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
<div xmlns:sch="http://purl.oclc.org/dsdl/schematron" type="verse"> <head>Night in Tarras</head> <lg type="stanza"> <l>At evening tramping on the hot white road</l> <l>…</l> </lg> <lg type="stanza"> <l>A wind sprang up from nowhere as the sky</l> <l>…</l> </lg> </div>
NoteThe @type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

att.witnessed

att.witnessed supplies the attribute used to identify the witnesses supporting a particular reading in a critical apparatus.
Memberslem rdg
Attributes
@wit(witness or witnesses) contains a space-delimited list of one or more pointers indicating the witnesses which attest to a given reading.
Status Optional
NoteIf the apparatus contains readings only for a single witness, this attribute may be consistently omitted.
This attribute may occur both within an apparatus gathering variant readings in the transcription of an individual witness and within an apparatus gathering readings from different witnesses.
Additional descriptions or alternative versions of the sigla referenced may be supplied as the content of a child <wit> element.

Macros

data.certainty

data.certainty defines the range of attribute values expressing a degree of certainty.
Used byElement:
relation/@certsex/@certsupplied/@certunclear/@cert
Declaration
data.certainty = "high" | "medium" | "low" | "unknown"
NoteCertainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. For more precise indication, data.probability may be used instead or in addition.

data.count

data.count defines the range of attribute values used for a non-negative integer value used as a count.
Used byElement:
age/@valuetable/@rowstable/@cols
Declaration
data.count = xsd:nonNegativeInteger
NoteOnly positive integer values (including zero) are permitted

data.duration.iso

data.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Used by
Declaration
data.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
NoteA duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first time number-letter pair.
For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

data.duration.w3c

data.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Used by
Declaration
data.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
NoteA duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first time number-letter pair.
For complete details, see the W3C specification.

data.enumerated

data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Used byElement:
addSpan/@placeapp/@typebibl/@typelocation/@typecorr/@typedate/@evidencedel/@statusdel/@typeevent/@typefigure/@subtypeforename/@typeformula/@notationfw/@typegenName/@typeidno/@typeinfo/@typelist/@typenameLink/@typenum/@typepersName/@typeperson/@evidenceq/@typerdg/@typereg/@typerelation/@evidencerelation/@nameroleName/@typers/@typesex/@evidencespace/@dimsurname/@typeteiHeader/@typetitle/@typetitle/@leveltrait/@typevariantEncoding/@methodvariantEncoding/@location
Declaration
data.enumerated = data.name
NoteAttributes using this datatype must contain a word which follows the rules defining a legal XML name (see ): for example they cannot include whitespace or begin with digits.
Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

data.language

data.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. ]
Used byElement:
foreign/@xml:langlanguage/@ident
Declaration
data.language = xsd:language | ""
NoteThe values for this attribute are language tags as defined in BCP 47. Currently BCP 47 comprises RFC 4646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.
A language tag, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
languageThe IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at . It is recommended that this code be written in lower case.scriptThe ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at . The IETF recommends this code be omitted unless it is necessary to make a distinction you need.regionEither an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case. The list of codes can be found at . The latter consist of 3 digits; the list of codes can be found at .variantAn IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.extensionAn extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.private useAn extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been grandfathered from previous specifications.
Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.
Examples include
snShonazh-TWTaiwanesezh-Hant-HKChinese written in traditional script as used in Hong Kongen-SLEnglish as spoken in Sierra LeoneplPolishes-MXSpanish as spoken in Mexicoes-419Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

data.name

data.name defines the range of attribute values expressed as an XML Name.
Used bydata.enumerated
Declaration
data.name = xsd:Name
NoteAttributes using this datatype must contain a single word which follows the rules defining a legal XML name (see ): for example they cannot include whitespace or begin with digits.

data.numeric

data.numeric defines the range of attribute values used for numeric values.
Used byElement:
num/@value
Declaration
data.numeric = xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
NoteAny numeric value, represented as a decimal number, in floating point format, or as a ratio.
To represent a floating point number, expressed in scientific notation, E notation, a variant of exponential notation, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.
A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

data.outputMeasurement

data.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Used by
Declaration
data.outputMeasurement = token { pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)" }
Example
<figure> <head>The TEI Logo</head> <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in between and <mentioned>text encoding initiative</mentioned> underneath, all on a white background.</figDesc> <graphic height="600px" width="600px" url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
NoteThese values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

data.pattern

data.pattern (regular expression pattern) defines attribute values which are expressed as a regular expression.
Used by
Declaration
data.pattern = token
NoteA regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)Wikipedia

data.pointer

data.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Used byElement:
app/@fromapp/@tocatRef/@targetcatRef/@schemelocation/@refhandShift/@newmsContents/@classmsItem/@classobject/@refoccupation/@schemeoccupation/@coderef/@targetrelation/@activerelation/@mutualrelation/@passivesocecStatus/@schemesocecStatus/@codesupplied/@resp
Declaration
data.pointer = xsd:anyURI
NoteThe range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

data.replacement

data.replacement defines attribute values which contain a replacement template.
Used by
Declaration
data.replacement = text

data.sex

data.sex defines the sex of an individual according to ISO 5218:2004. Male is 1, Female is 2 and Unknown is 0.
Used byElement:
sex/@value
Declaration
data.sex = string { pattern = "(1|2|0)" }
NoteValues for attributes using this datatype may be locally defined by a project, or may refer to an external standard, such as vCard's sex property (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People .

data.temporal.iso

data.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Used by
Declaration
data.temporal.iso = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
NoteIf it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.
For all representations for which ISO 8601 describes both a basic and an extended format, these Guidelines recommend use of the extended format.
While ISO 8601 permits the use of both 00:00 and 24:00 to represent midnight, these Guidelines strongly recommend against the use of 24:00.

data.temporal.w3c

data.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes specification.
Used byElement:
date/@whendate/@notBeforedate/@notAfterdate/@fromdate/@totime/@whentime/@notBeforetime/@notAftertime/@fromtime/@to
Declaration
data.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime
NoteIf it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

data.text

data.text defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.
Used byElement:
date/@nmilestone/@npb/@nresidence/@keyspace/@extenttopic/@key
Declaration
data.text = string
NoteAttributes using this datatype must contain a single token in which whitespace and other punctuation characters are permitted.

data.version

data.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Used byElement:
TEI/@version
Declaration
data.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
NoteThe value of this attribute follows the pattern specified by the Unicode consortium for its version number (). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

data.versionNumber

data.versionNumber defines the range of attribute values used for version numbers.
Used by
Declaration
data.versionNumber = token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

data.word

data.word defines the range of attribute values expressed as a single word or token.
Used byElement:
app/@locdate/@notBefore-customdate/@notAfter-customdate/@from-customdate/@to-customhead/@rendhi/@rendmedia/@mimeTypeorg/@rolep/@rendsupplied/@reasonunclear/@reason
Declaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
NoteAttributes using this datatype must contain a single word which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

data.xTruthValue

data.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Used by
Declaration
data.xTruthValue = xsd:boolean | "unknown" | "inapplicable"
NoteIn cases where where uncertainty is inappropriate, use the datatype data.TruthValue.

macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. ]
Used bydesc figDesc witness
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. ]
Used byab add corr del hi l orig p ref reg salute seg sic signed supplied title unclear
Declaration
macro.paraContent = ( text | model.gLike | model.phrase | model.inter | model.global | lg )*

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. ]
Used byabbr addName affiliation author birth country death district education expan faith floruit foreign forename fw genName geogFeat geogName incipit name nameLink num occupation orgName persName placeName pubPlace publisher region residence roleName rs settlement sex socecStatus surname
Declaration
macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )*

macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. ]
Used byage funder language
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. ]
Used bycell change handNote item note q quote
Declaration
macro.specialPara = ( text | model.gLikemodel.phrasemodel.intermodel.divPartmodel.global )*

macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Used bycollection ex locus repository
Declaration
macro.xtext = ( text | model.gLike )*

Document last modified: 8 November 2013

Cite this as: Casebooks Project (Element Set), http://www.magicandmedicine.hps.cam.ac.uk/using-our-edition/editorial-policies/element-set, accessed 2017-03-29.