Northeastern University Women Writers Project Textbase Encoding Language

Table of contents

WARNING: This is an in-development working system, and as such may at times be broken.

WARNING: Current processors probably cannot generate valid DTDs (and perhaps not even XSDs) from this ODD.

1. suggested usage

2. current report generation

Appendix A Elements

Appendix A.1 <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Member of
Contained by
core: teiCorpus
May contain
header: teiHeader
textstructure: text
Note

As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <elementRef key="text"/>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.xmlid,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.rend,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.responsibility.attribute.resp,
   ws_att.global.source.attribute.source,
   ws_att.typed.attributes,
   attribute xml:lang { text },
   attribute version { text }?,
   ( ws_teiHeader, ws_text )
}

Appendix A.2 <ab>

<ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [17.3. Blocks, Segments, and Anchors]
Modulelinking
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
caption
issue
commentary
timelineitem
placeholder
A placeholder to provide validity when the encoded portion of the document is not being transcribed, typically because it is out of scope for the WWO collection.
Member of
Contained by
May contain
Note

The <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. Unlike paragraphs, <ab> may nest and may use the type and subtype attributes.

Example
<div type="bookn="Genesis">  <div type="chaptern="1">   <ab>In the beginning God created the heaven and the earth.</ab>   <ab>And the earth was without form, and void; and      darkness was upon the face of the deep. And the      spirit of God moved upon the face of the waters.</ab>   <ab>And God said, Let there be light: and there was light.</ab> <!-- ...-->  </div> </div>
Schematron
<sch:rule context="tei:l//tei:ab"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText. </sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.abContent"/>
</content>
    
Schema Declaration
element ab
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.fragmentable.attributes,
   ws_att.typed.attribute.subtype,
   ws_att.written.attributes,
   attribute type
   {
      "caption" | "issue" | "commentary" | "timelineitem" | "placeholder"
   }?,
   ws_macro.abContent
}

Appendix A.3 <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
type(type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
suspension
(suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
(contraction) the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
(superscription) the abbreviation includes writing above the line.
acronym
(acronym) the abbreviation comprises the initial letters of the words of a phrase.
title
(title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
(organization) the abbreviation is for the name of an organization.
geographic
(geographic) the abbreviation is for a geographic name.
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { text }?,
   ws_macro.phraseSeq
}

Appendix A.4 <acrostic>

<acrostic> a derived element that contains the word or phrase (including any appropriate phrase-level encoding like <persName>) that are spelled by the initial letters of a passage (e.g., the first letter of each lineof a stanza or poem).
Modulederived-module-wwp-store
Attributes
targetpoints to the parent element (e.g., an <lg>) that contains the elements of which the first letter of each make up the acrostic.
StatusRequired
Datatypeteidata.pointer
componentsIdunno
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
Contained by
derived-module-wwp-store: acrostics
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element acrostic
{
   ws_att.global.attributes,
   attribute target { text },
   attribute components { list { * } }?,
   ws_macro.phraseSeq
}

Appendix A.5 <acrostics>

<acrostics> Container that occurs in <hyperDiv> and holds one or more <acrostic> elements.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
derived-module-wwp-store: acrostic
Content model
<content>
 <elementRef key="acrostic" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element acrostics { ws_att.global.attributes, ws_acrostic+ }

Appendix A.6 <actor>

<actor> contains the name of an actor appearing within a cast list. [7.1.4. Cast Lists]
Moduledrama
Attributes
sexspecifies the sex of the actor.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be locally defined by a project, or may refer to an external standard.

genderspecifies the gender of the actor.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
drama: castItem
May contain
Note

This element should be used only to mark the name of the actor as given in the source. Chapter 14. Names, Dates, People, and Places discusses ways of marking the components of names, and also of associating names with biographical information about a person.

Example
<castItem>  <role>Mathias</role>  <roleDesc>the Burgomaster</roleDesc>  <actor ref="https://en.wikipedia.org/wiki/Henry_Irving">Mr. Henry Irving</actor> </castItem>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element actor
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   ws_macro.phraseSeq
}

Appendix A.7 <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Derived fromatt.written
StatusRequired
Datatypeteidata.pointer
Member of
Contained by
May contain
Note

In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   ws_att.global.attributes,
   ws_att.transcriptional.attribute.cause,
   ws_att.transcriptional.attribute.seq,
   ws_att.editLike.attribute.evidence,
   ws_att.editLike.attribute.instant,
   ws_att.typed.attributes,
   attribute hand { text },
   ws_macro.paraContent
}

Appendix A.8 <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>). [12.3.1.4. Additions and Deletions]
Moduletranscr
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Derived fromatt.written
StatusRequired
Datatypeteidata.pointer
Member of
Contained by
May containEmpty element
Note

Both the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute.

Example
<handNote xml:id="HEOL"  scribe="HelgiÓlafsson"/> <!-- ... --> <body>  <div> <!-- text here -->  </div>  <addSpan n="added_gatheringhand="#HEOL"   spanTo="#P025"/>  <div> <!-- text of first added poem here -->  </div>  <div> <!-- text of second added poem here -->  </div>  <div> <!-- text of third added poem here -->  </div>  <div> <!-- text of fourth added poem here -->  </div>  <anchor xml:id="P025"/>  <div> <!-- more text here -->  </div> </body>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element addSpan
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.spanning.attributes,
   ws_att.transcriptional.attribute.cause,
   ws_att.transcriptional.attribute.seq,
   ws_att.editLike.attribute.evidence,
   ws_att.editLike.attribute.instant,
   ws_att.typed.attributes,
   attribute hand { text },
   empty
}

Appendix A.9 <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
core: address
May contain
Note

Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.

Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { ws_att.global.attributes, ws_macro.phraseSeq }

Appendix A.10 <address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
May contain
Note

This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.

ExampleUsing just the elements defined by the core module, an address could be represented as follows:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name>Italy</name> </address>
ExampleWhen a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <settlement>Bologna</settlement>  <country>Italy</country> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ( ws_model.global*, ( ( ws_model.addrPart, ws_model.global* )+ ) )
}

Appendix A.11 <adds>

<adds> Container that occurs in <hyperDiv> and holds one or more <add> elements.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
core: add
Note

Currently we only encode an <add> in the <hyperDiv> if its content is a note of some sort.

Content model
<content>
 <elementRef key="add" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element adds { ws_att.global.attributes, ws_add+ }

Appendix A.12 <advertisement>

<advertisement> A section of text, typically in the backmatter, that advertises other books by the same author, publisher, bookseller, etc.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
May contain
Note

These are different from the ‘advertisements’ that occur in front matter (prefatory materials that resemble introductions). The front-matter ‘advertisements’ should be recorded with <div type="prefatory">.

The advertisement usually contains a <bibl> element, since it often has information about the title and author of a book. Note, though, that prose descriptions of the texts should not be recorded within bibl.

Many advertisements will contain information about the pricing of the texts for sale. These prices should be recorded in <measure> if they are renditionally distinct. These prices should not, however, be recorded in <docSale>, as this element should be used exclusively in title pages.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.common"/>
  <classRef key="model.global"/>
  <classRef key="model.biblPart"/>
 </alternate>
</content>
    
Schema Declaration
element advertisement
{
   ws_att.global.attributes,
   ( ws_model.common | ws_model.global | ws_model.biblPart )*
}

Appendix A.13 <alt>

<alt> (alternation) identifies an alternation or a set of choices among elements or passages. [17.8. Alternation]
Modulelinking
Attributes
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
modestates whether the alternations gathered in this collection are exclusive or inclusive.
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
excl
(exclusive) indicates that the alternation is exclusive, i.e. that at most one of the alternatives occurs.
incl
(inclusive) indicates that the alternation is not exclusive, i.e. that one or more of the alternatives occur.
weightsIf mode is excl, each weight states the probability that the corresponding alternative occurs. If mode is incl each weight states the probability that the corresponding alternative occurs given that at least one of the other alternatives occurs.
StatusOptional
Datatype2–∞ occurrences of teidata.probability separated by whitespace
Note

If mode is excl, the sum of weights must be 1. If mode is incl, the sum of weights must be in the range from 0 to the number of alternants.

Member of
Contained by
May containEmpty element
Note

Here at the WWP, an <alt> with a type of element must have a subtype whose value is the name of an element (e.g., person). Further, each of the space-separated values of the target of such an <alt> must point to whatever element is named on subtype (e.g., <person>).

Example
<alt mode="excltarget="#we.fun #we.sun"  weights="0.5 0.5"/>
Schematron
<sch:rule context="wwp:alt[ @type eq 'element']"> <sch:assert test="@subtype castable as xs:Name">When the @type of <alt> is "element", the @subtype must be an element name</sch:assert> </sch:rule>
Schematron
<sch:rule context="wwp:alt[ @type eq 'element'][/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef]"> <sch:let name="path"  value="'https://www.wwp-test.neu.edu/wwo/texts/'"/> <sch:let name="TARGETs"  value="tokenize( normalize-space( @target ) )"/> <sch:let name="TPREFs"  value="for $t in $TARGETs return substring-before( $t,':')"/> <sch:let name="URLs"  value="for $p in $TPREFs return concat( $path, substring-before( /wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef//wwp:prefixDef[ @ident eq $p ]/@replacementPattern, '#' ) )"/> <sch:let name="KEYs"  value="for $t in $TARGETs return substring-after( $t,':')"/> <sch:let name="ALTERNATEs"  value="for $k in $KEYs return if ( count( index-of( $KEYs, $k ) ) eq 1 ) then if ( doc-available( $URLs[ index-of( $KEYs, $k )] ) ) then if ( document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] ) then document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] else . else . else ."/> <sch:let name="CORRECTs"  value="for $gi in $ALTERNATEs return name($gi) eq @subtype"/> <sch:report test="count( $TARGETs ) eq 0">Empty @target of <alt></sch:report> <sch:report test="$CORRECTs = false()">Each pointer in the @target of <alt> should point to a <<sch:value-of select="@subtype"/>>, but at least one of the pointers in this one ("<sch:value-of select="normalize-space( @target )"/>") point to: <sch:value-of select="if ( not( ALTERNATEs ) ) then 'nowhere' else for $a in $ALTERNATEs return if ( $a is . ) then ' nothing' else concat(' <', name($a), '>')"/>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element alt
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.pointing.attribute.targetLang,
   ws_att.pointing.attribute.evaluate,
   ws_att.typed.attributes,
   attribute target { list { * } }?,
   attribute mode { "excl" | "incl" }?,
   attribute weights { list { * } }?,
   empty
}

Appendix A.14 <altGrp>

<altGrp> (alternation group) groups a collection of <alt> elements and possibly pointers. [17.8. Alternation]
Modulelinking
Attributes
modestates whether the alternations gathered in this collection are exclusive or inclusive.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
excl
(exclusive) indicates that the alternation is exclusive, i.e. that at most one of the alternatives occurs.[Default]
incl
(inclusive) indicates that the alternation is not exclusive, i.e. that one or more of the alternatives occur.
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
core: desc ptr
linking: alt
Note

Any number of alternations, pointers or extended pointers.

Example
<altGrp mode="excl">  <alt target="#dm #lt #bb"   weights="0.5 0.25 0.25"/>  <alt target="#rl #dbweights="0.5 0.5"/> </altGrp>
Example
<altGrp mode="incl">  <alt target="#dm #rlweights="0.90 0.90"/>  <alt target="#lt #rlweights="0.5 0.5"/>  <alt target="#bb #rlweights="0.5 0.5"/>  <alt target="#dm #dbweights="0.10 0.10"/>  <alt target="#lt #dbweights="0.45 0.90"/>  <alt target="#bb #dbweights="0.45 0.90"/> </altGrp>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="alt"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element altGrp
{
   ws_att.global.attributes,
   ws_att.pointing.group.attributes,
   attribute mode { "excl" | "incl" }?,
   ( ws_model.descLike*, ( ws_alt | ws_ptr )* )
}

Appendix A.15 <am>

<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [12.3.1.2. Abbreviation and Expansion]
Moduletranscr
Attributes
Member of
Contained by
May contain
derived-module-wwp-store: regMe vuji
gaiji: g
character data
Example
do you <abbr>Mr<am>.</am> </abbr> Jones?
Example
<choice>  <abbr>Aug<am>g</am>  </abbr>  <expan>Aug<ex>ustorum duo</ex>  </expan> </choice>
Example
<abbr>eu<am>   <g ref="#b-er"/>  </am>y</abbr> <abbr>  <am>   <g ref="#b-per"/>  </am>sone </abbr> ...
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.pPart.transcriptional"/>
 </alternate>
</content>
    
Schema Declaration
element am
{
   ws_att.global.attributes,
   ws_att.editLike.attributes,
   ws_att.typed.attributes,
   ( text | ws_model.gLike | ws_model.pPart.transcriptional )*
}

Appendix A.16 <anagram>

<anagram> points to 2 or more textual elements to indicate they are anagrams of each other, OR points to a single textual element to indicate said element is an anagram of its content
Modulederived-module-wwp-store
Attributes
targetpoints to an element of which the current element is (roughly) an anagram, or points to 2 or more elements whose content are (roughly) anagrams of each other
Derived fromatt.pointing
StatusRequired
Schematron
<sch:rule context="anagram[normalize-space(.) eq '']"> <sch:let name="targets"  value="tokenize( normalize-space( @target ),' ')"/> <sch:assert test="count( $targets ) gt 1">An empty <anagram> element should point to 2 or more targets</sch:assert> </sch:rule> <sch:rule context="anagram[normalize-space(.) ne '']"> <sch:let name="targets"  value="tokenize( normalize-space( @target ),' ')"/> <sch:assert test="count( $targets ) eq 1">An <anagram> element that contains an anagram should point to only 1 target</sch:assert> </sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The elements pointed to should be intentional, if not exact, anagrams of one another. If one of the textual objects that is an anagram is made of several XML elements, then the target should point to either the first XML element (in document order) if they are connected with part or next & prev; or to a <link> or <join>. The point is, the target should not point to each XML element that is a component of a single anagram.

Contained by
derived-module-wwp-store: anagrams
May contain
Note
The <anagram> element may contain content to indicate the re-arranged order of the letters in the source, for use when the source does not indicate the re-arrangement itself. E.g., if the source says ‘He hired a new ‘crap built on lies’ officer’, but does not explain what ‘crap built on lies’ is an anagrom for, we might encode
<anagram target="#cbol">public relations</anagram> <!-- ... --> <lb/>He hired a new <soCalled xml:id="cbol">crap built on lies</soCalled> officer
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element anagram
{
   ws_att.global.attributes,
   ws_att.pointing.attribute.targetLang,
   ws_att.pointing.attribute.evaluate,
   attribute target { list { + } },
   ws_macro.phraseSeq
}

Appendix A.17 <anagrams>

<anagrams> Container that occurs in <hyperDiv> and holds one or more <anagram> elements.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
derived-module-wwp-store: anagram
Content model
<content>
 <elementRef key="anagram" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element anagrams { ws_att.global.attributes, ws_anagram+ }

Appendix A.18 <analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
May contain
Note

May contain titles and statements of responsibility (author, editor, or other), in any order.

The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item.

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   ws_att.global.attributes,
   (
      ws_author
    | ws_editor
    | ws_respStmt
    | ws_title
    | ws_model.ptrLike
    | ws_date
    | textLang
    | ws_idno
    | ws_availability
   )*
}

Appendix A.19 <anchor>

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 17.5. Correspondence and Alignment]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Schematron
<sch:rule context="wwp:anchor/@rend"> <sch:report test="contains( ., 'post(')"  role="warning">We do not normally use the post() keyword on the @rend of <anchor>, we use pre() instead.</sch:report> </sch:rule>
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May containEmpty element
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s> <s>Help me find it.<ptr target="#A234"/> </s>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element anchor
{
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmllang,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.responsibility.attribute.resp,
   ws_att.global.source.attribute.source,
   ws_att.cmc.attributes,
   ws_att.typed.attributes,
   attribute xml:id { text },
   attribute rend { list { + } }?,
   empty
}

Appendix A.20 <argument>

<argument> (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
core: item lg list
drama: castList
figures: table
May contain
Example
<argument>  <p>Monte Video — Maldonado — Excursion    to R Polanco — Lazo and Bolas — Partridges —    Absence of Trees — Deer — Capybara, or River Hog —    Tucutuco — Molothrus, cuckoo-like habits — Tyrant    Flycatcher — Mocking-bird — Carrion Hawks —    Tubes formed by Lightning — House struck</p> </argument>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.headLike"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element argument
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   (
      ( ws_model.global | ws_model.headLike )*,
      ( ( ws_model.common, ws_model.global* )+ )
   )
}

Appendix A.21 <att>

<att> (attribute) contains the name of an attribute appearing within running text. [23. Documentation Elements]
Moduletagdocs
Attributes
scheme(scheme) supplies an identifier for the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(Text Encoding Initiative) this attribute is part of the TEI scheme.[Default]
DBK
(Docbook) this attribute is part of the Docbook scheme.
XX
(unknown) this attribute is part of an unknown scheme.
imaginary
(imaginary) the attribute is from a non-existent scheme, for illustrative purposes only
XHTML
(XHTML) the attribute is part of the XHTML language
XML
(XML) the attribute is part of the XML language
XI
(XI) the attribute is defined in the xInclude schema
Member of
Contained by
May contain
XSD Name
Note

As an alternative to using the scheme attribute a namespace prefix may be used. Where both scheme and a prefix are used, the prefix takes precedence.

Example
<p>The TEI defines several <soCalled>global</soCalled> attributes; their names include <att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>, and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p>
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element att
{
   ws_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}

Appendix A.22 <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
main
a primary author.[Default]
other
an author whom the Women Writers Project for some reason wishes to consider as occupying a subsidiary role.
Member of
Contained by
May contain
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Schematron
<sch:rule context="wwp:teiHeader/wwp:fileDesc/wwp:titleStmt/wwp:author/wwp:persName |wwp:teiHeader/wwp:fileDesc/wwp:sourceDesc//wwp:author/wwp:persName"> <sch:assert test="@ref">Authors should have a reference to the personography.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author
{
   ws_att.global.attributes,
   ws_att.datable.attributes,
   ws_att.naming.attributes,
   attribute type { "main" | "other" }?,
   ws_macro.phraseSeq
}

Appendix A.23 <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
core: p
header: licence
linking: ab
Note

A consistent format should be adopted

Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( ws_model.availabilityPart | ws_model.pLike )+
}

Appendix A.24 <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Note

At the WWP a <titleBlock> is permitted in the content of <back> after a <trailer> (or other member of model.divBottomPart). This was originally put in to accomodate smith.conversations.xml.

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.frontPart"/>
    <classRef key="model.divLike"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <elementRef key="titlePage"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   ws_att.global.attributes,
   ws_att.declaring.attributes,
   (
      (
         ws_model.frontPart
       | ws_model.pLike.front
       | ws_model.pLike
       | ws_model.listLike
       | ws_model.global
      )*,
      (
         (
            ws_model.divLike,
            ( ws_model.frontPart | ws_model.divLike | ws_model.global )*
         )?
      ),
      (
         (
            ws_model.divBottomPart,
            ( ws_model.divBottomPart | ws_titlePage | ws_model.global )*
         )?
      )
   )
}

Appendix A.25 <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
  <elementRef key="epigraph"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.declarable.attributes,
   ws_att.docStatus.attributes,
   ws_att.sortable.attributes,
   ws_att.typed.attributes,
   (
      text
    | ws_model.gLike
    | ws_model.highlighted
    | ws_model.pPart.data
    | ws_model.pPart.edit
    | ws_model.segLike
    | ws_model.ptrLike
    | ws_model.biblPart
    | ws_model.global
    | ws_epigraph
   )*
}

Appendix A.26 <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   ws_att.global.attributes,
   ws_att.citing.attributes,
   ws_macro.phraseSeq
}

Appendix A.27 <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
derived-module-wwp-store: advertisement
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Example
<biblStruct type="newspaper">  <analytic>   <author>    <forename>David</forename>    <surname>Barstow</surname>   </author>   <author>    <forename>Susanne</forename>    <surname>Craig</surname>   </author>   <author>    <forename>Russ</forename>    <surname>Buettner</surname>   </author>   <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>   <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>  </analytic>  <monogr>   <title level="j">The New York Times</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>A. G. Sulzberger</publisher>    <date when="2018-10-03">Wednesday, October 3, 2018</date>   </imprint>   <biblScope unit="volume">CLXVIII</biblScope>   <biblScope unit="issue">58,104</biblScope>   <biblScope unit="page">1</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <sequence>
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.declarable.attributes,
   ws_att.docStatus.attributes,
   ws_att.sortable.attributes,
   ws_att.typed.attributes,
   (
      ws_analytic*,
      ( ( ws_monogr, ws_series* )+ ),
      ( ws_model.noteLike | ws_model.ptrLike | relatedItem | ws_citedRange )*
   )
}

Appendix A.28 <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="2"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="0" maxOccurs="1">
     <elementRef key="projectDesc"
      minOccurs="1" maxOccurs="1"/>
     <sequence minOccurs="2"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   ws_att.structuralCategorization.attributes,
   ws_att.global.attributes,
   ws_att.declaring.attributes,
   (
      ws_model.global*,
      ( ( ws_model.divTop, ( ws_model.global | ws_model.divTop )* )? ),
      (
         (
            ws_model.divLike,
            ws_model.global*,
            ws_model.divLike,
            ws_model.global*,
            ( ws_model.divLike, ws_model.global* )*
         )
       | (
            ( ( ( schemaSpec | ws_model.common ), ws_model.global* )+ ),
            (
               (
                  ws_projectDesc,
                  (
                     ws_model.divLike,
                     ws_model.global*,
                     ws_model.divLike,
                     ws_model.global*,
                     ( ws_model.divLike, ws_model.global* )*
                  )
               )?
            )
         )
      ),
      ( ( ws_model.divBottom, ws_model.global* )* )
   )
}

Appendix A.29 <respLine>

<respLine> (byline) contains a statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docRole> element.

Example
<respLine>Written by a CITIZEN who continued all the while in London. Never made publick before.</respLine>
Example
<respLine>Written from her own MEMORANDUMS</respLine>
Example
<respLine>By George Jones, Political Editor, in Washington</respLine>
Example
<respLine>BY <docRole>THOMAS PHILIPOTT,</docRole> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</respLine>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="docAuthor"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element respLine
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ( text | ws_model.gLike | ws_model.phrase | ws_docAuthor | ws_model.global )*
}

Appendix A.30 <calendar>

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Moduleheader
Attributes
Contained by
header: calendarDesc
May contain
core: p
linking: ab
Example
<calendarDesc>  <calendar xml:id="julianEngland">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendar
{
   ws_att.global.attributes,
   ws_att.pointing.attributes,
   ws_att.typed.attributes,
   ws_model.pLike+
}

Appendix A.31 <calendarDesc>

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
header: calendar
Note

In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <elementRef key="calendar" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendarDesc { ws_att.global.attributes, ws_calendar+ }

Appendix A.32 <castGroup>

<castGroup> (cast list grouping) groups one or more individual <castItem> elements within a cast list. [7.1.4. Cast Lists]
Moduledrama
Attributes
gender
StatusOptional
Datatypewwpdata.sex
Contained by
May contain
Note

The rend attribute may be used, as here, to indicate whether the grouping is indicated by a brace, whitespace, font change, etc.

Note that in this example the role description ‘friends of Mathias’ is understood to apply to both roles equally.

Example
<castGroup rend="braced">  <castItem>   <role>Walter</role>   <actor>Mr Frank Hall</actor>  </castItem>  <castItem>   <role>Hans</role>   <actor>Mr F.W. Irish</actor>  </castItem>  <roleDesc>friends of Mathias</roleDesc> </castGroup>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.headLike"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="castItem"/>
    <elementRef key="castGroup"/>
    <elementRef key="roleDesc"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="trailer"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element castGroup
{
   ws_att.global.attributes,
   attribute gender { text }?,
   (
      ( ws_model.global | ws_model.headLike )*,
      ( ( ( ws_castItem | ws_castGroup | ws_roleDesc ), ws_model.global* )+ ),
      ( ( ws_trailer, ws_model.global* )? )
   )
}

Appendix A.33 <castItem>

<castItem> (cast list item) contains a single entry within a cast list, describing either a single role or a list of non-speaking roles. [7.1.4. Cast Lists]
Moduledrama
Attributes
typecharacterizes the cast item.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
role
the item describes a single role.[Default]
list
the item describes a list of non-speaking roles.
gender
StatusOptional
Datatypewwpdata.sex
ValuesIf not specified, the value should be considered unknown unless there is a gender on an ancestor, in which case the closest such value is used. Exception: when that closest ancestor gender is mixed, the value here is still considered unknown.
Contained by
May contain
Example
<castItem>  <role>Player</role>  <actor>Mr Milward</actor> </castItem>
Example
<castItem type="list">Constables, Drawer, Turnkey, etc.</castItem>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.castItemPart"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element castItem
{
   ws_att.global.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "role" | "list" }?,
   attribute gender { text }?,
   (
      text
    | ws_model.gLike
    | ws_model.castItemPart
    | ws_model.phrase
    | ws_model.global
   )*
}

Appendix A.34 <castList>

<castList> (cast list) contains a single cast list or dramatis personae. [7.1.4. Cast Lists 7.1. Front and Back Matter ]
Moduledrama
Attributes
Member of
Contained by
May contain
Example
<castList>  <castGroup>   <head rend="braced">Mendicants</head>   <castItem>    <role>Aafaa</role>    <actor>Femi Johnson</actor>   </castItem>   <castItem>    <role>Blindman</role>    <actor>Femi Osofisan</actor>   </castItem>   <castItem>    <role>Goyi</role>    <actor>Wale Ogunyemi</actor>   </castItem>   <castItem>    <role>Cripple</role>    <actor>Tunji Oyelana</actor>   </castItem>  </castGroup>  <castItem>   <role>Si Bero</role>   <roleDesc>Sister to Dr Bero</roleDesc>   <actor>Deolo Adedoyin</actor>  </castItem>  <castGroup>   <head rend="braced">Two old women</head>   <castItem>    <role>Iya Agba</role>    <actor>Nguba Agolia</actor>   </castItem>   <castItem>    <role>Iya Mate</role>    <actor>Bopo George</actor>   </castItem>  </castGroup>  <castItem>   <role>Dr Bero</role>   <roleDesc>Specialist</roleDesc>   <actor>Nat Okoro</actor>  </castItem>  <castItem>   <role>Priest</role>   <actor>Gbenga Sonuga</actor>  </castItem>  <castItem>   <role>The old man</role>   <roleDesc>Bero's father</roleDesc>   <actor>Dapo Adelugba</actor>  </castItem> </castList> <stage type="mix">The action takes place in and around the home surgery of Dr Bero, lately returned from the wars.</stage>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="castItem"/>
    <elementRef key="castGroup"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element castList
{
   ws_att.global.attributes,
   (
      ( ws_model.divTop | ws_model.global )*,
      ( ( ws_model.common, ws_model.global* )* ),
      ( ( ( ws_castItem | ws_castGroup ), ws_model.global* )+ ),
      ( ( ws_model.common, ws_model.global* )* )
   )
}

Appendix A.35 <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>. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
header: category
May contain
derived-module-wwp-store: mcr
header: idno
msdescription: dimensions height width
tagdocs: att code gi ident tag val
transcr: am ex subst
character data
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="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc> </catDesc>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
    
Schema Declaration
element catDesc
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ( text | ws_model.limitedPhrase | ws_model.catDescPart )*
}

Appendix A.36 <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Moduleheader
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
main
the primary classification of a text's genre. There should only be one <catRef> with this type per textfile.[Default]
other
a classification of a text's genre, but not the single most important classification.
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May containEmpty element
Note

The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

Example
<catRef scheme="#myTopics"  target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics">  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   ws_att.global.attributes,
   ws_att.pointing.attributes,
   attribute type { "main" | "other" }?,
   attribute scheme { text }?,
   empty
}

Appendix A.37 <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
core: desc gloss
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   ws_att.global.attributes,
   ws_att.datcat.attributes,
   (
      ( ws_catDesc+ | ( ws_model.descLike | equiv | ws_gloss )* ),
      ws_category*
   )
}

Appendix A.38 <cb>

<cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column beginnings relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb> element is placed at the head of the column to which it refers.

ExampleMarkup of an early English dictionary printed in two columns:
<pb/> <cb n="1"/> <entryFree>  <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>: <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner    sinks into the Ground, to find out and disappoint the Enemies Mines,    or to prepare one</sense>. </entryFree> <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or <sense>lie groveling</sense>.</entryFree> <!-- remainder of column --> <cb n="2"/> <entryFree>  <form>Wey</form>, <sense>the greatest Measure for dry Things,    containing five Chaldron</sense>. </entryFree> <entryFree>  <form>Whale</form>, <sense>the greatest of    Sea-Fishes</sense>. </entryFree>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element cb
{
   ws_att.global.attributes,
   ws_att.breaking.attributes,
   ws_att.cmc.attributes,
   ws_att.edition.attributes,
   ws_att.spanning.attributes,
   ws_att.typed.attributes,
   empty
}

Appendix A.39 <cell>

<cell> (cell) contains one cell of a table. [15.1.1. TEI Tables]
Modulefigures
Attributes
Contained by
figures: row
May contain
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element cell
{
   ws_att.global.attributes,
   ws_att.tableDecoration.attributes,
   ws_macro.specialPara
}

Appendix A.40 <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
Derived fromatt.ascribed
StatusRequired
Datatype1–6 occurrences of anyURI separated by whitespace
Note

At the WWP the who should be expressed as 1–6 name keys each preceded by the ‘p:’ prefix.

whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusRequired
Datatypeteidata.temporal.w3c
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
namesdates: persName
tagdocs: att code gi tag val
character data
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="gi"/>
  <elementRef key="ptr"/>
  <elementRef key="code"/>
  <elementRef key="att"/>
  <elementRef key="quote"/>
  <elementRef key="list"/>
  <elementRef key="val"/>
  <elementRef key="persName"/>
  <elementRef key="tag"/>
  <elementRef key="name"/>
  <elementRef key="date"/>
  <elementRef key="emph"/>
  <elementRef key="title"/>
  <elementRef key="note"/>
 </alternate>
</content>
    
Schema Declaration
element change
{
   ws_att.global.attributes,
   ws_att.datable.attribute.period,
   ws_att.datable.custom.attribute.when-custom,
   ws_att.datable.custom.attribute.notBefore-custom,
   ws_att.datable.custom.attribute.notAfter-custom,
   ws_att.datable.custom.attribute.from-custom,
   ws_att.datable.custom.attribute.to-custom,
   ws_att.datable.custom.attribute.datingPoint,
   ws_att.datable.custom.attribute.datingMethod,
   ws_att.datable.iso.attribute.when-iso,
   ws_att.datable.iso.attribute.notBefore-iso,
   ws_att.datable.iso.attribute.notAfter-iso,
   ws_att.datable.iso.attribute.from-iso,
   ws_att.datable.iso.attribute.to-iso,
   ws_att.datable.w3c.attribute.notBefore,
   ws_att.datable.w3c.attribute.notAfter,
   ws_att.datable.w3c.attribute.from,
   ws_att.datable.w3c.attribute.to,
   ws_att.docStatus.attributes,
   ws_att.typed.attributes,
   attribute who { list { ?, ?, ?, ?, ? } },
   attribute when { text },
   attribute target { list { + } }?,
   (
      text
    | ws_gi
    | ws_ptr
    | ws_code
    | ws_att
    | ws_quote
    | ws_list
    | ws_val
    | ws_persName
    | ws_tag
    | ws_name
    | ws_date
    | ws_emph
    | ws_title
    | ws_note
   )*
}

Appendix A.41 <char>

<char> (character) provides descriptive information about a character. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
Contained by
gaiji: charDecl
May contain
derived-module-wwp-store: advertisement
figures: figure
gaiji: mapping
Example
<char xml:id="circledU4EBA">  <localProp name="Name"   value="CIRCLED IDEOGRAPH 4EBA"/>  <localProp name="daikanwavalue="36"/>  <unicodeProp name="Decomposition_Mapping"   value="circle"/>  <mapping type="standard"></mapping> </char>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="unicodeProp"/>
  <elementRef key="unihanProp"/>
  <elementRef key="localProp"/>
  <elementRef key="mapping"/>
  <elementRef key="figure"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.descLike"/>
 </alternate>
</content>
    
Schema Declaration
element char
{
   ws_att.global.attributes,
   (
      unicodeProp
    | unihanProp
    | localProp
    | ws_mapping
    | ws_figure
    | ws_model.graphicLike
    | ws_model.noteLike
    | ws_model.descLike
   )*
}

Appendix A.42 <charDecl>

<charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: desc
gaiji: char
Example
<charDecl>  <char xml:id="aENL">   <unicodeProp name="Name"    value="LATIN LETTER ENLARGED SMALL A"/>   <mapping type="standard">a</mapping>  </char> </charDecl>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="char"/>
   <elementRef key="glyph"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element charDecl
{
   ws_att.global.attributes,
   ( ws_desc?, ( ws_char | glyph )+ )
}

Appendix A.43 <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="sic"/>
   <elementRef key="corr"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="abbr"/>
   <elementRef key="expan"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="orig"/>
   <elementRef key="reg"
    maxOccurs="unbounded"/>
  </sequence>
  <elementRef key="unclear" minOccurs="2"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="2"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   (
      ( ws_sic, ws_corr+ )
    | ( ws_abbr, ws_expan+ )
    | ( ws_orig, ws_reg+ )
    | ( ws_unclear, ws_unclear, ws_unclear* )
    | ( ws_supplied, ws_supplied, ws_supplied* )
   )
}

Appendix A.44 <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <citedRange from="3">p. 3ff</citedRange>.

Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   ws_att.global.attributes,
   ws_att.citing.attributes,
   ws_att.pointing.attributes,
   ws_macro.phraseSeq
}

Appendix A.45 <classDecl>

<classDecl> (classification declarations) contains a taxonomy (in a <taxonomy>) defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Note

The WWP version of this element more restrictive than TEI. The TEI allows one or more <taxonomy> children, whereas we allow only one.

Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States — Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy"/>
</content>
    
Schema Declaration
element classDecl { ws_att.global.attributes, ws_taxonomy }

Appendix A.46 <closer>

<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
core: lg list note
figures: table
May contain
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   (
      text
    | ws_model.gLike
    | ws_signed
    | ws_dateline
    | ws_salute
    | ws_model.phrase
    | ws_model.global
   )*
}

Appendix A.47 <code>

<code> contains literal code from some formal language such as a programming language. [23.1.1. Phrase Level Terms]
Moduletagdocs
Attributes
lang(formal language) a name identifying the formal language in which the code is expressed.
StatusOptional
Datatypeteidata.word
Member of
Contained by
May containCharacter data only
Example
<code lang="JAVA"> Size fCheckbox1Size = new Size(); fCheckbox1Size.Height = 500; fCheckbox1Size.Width = 500; xCheckbox1.setSize(fCheckbox1Size); </code>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element code { ws_att.global.attributes, attribute lang { text }?, text }

Appendix A.48 <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.editLike.attributes,
   ws_att.typed.attributes,
   ws_macro.paraContent
}

Appendix A.49 <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
linking: ab
Note

May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correction
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   ws_model.pLike+
}

Appendix A.50 <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [14.2.3. Place Names]
Modulenamesdates
Contained by
core: pubPlace
May contain
Note

At the WWP, <country> (and <region> and <settlement>) are only used as a child of <pubPlace>.

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element country { ws_macro.phraseSeq }

Appendix A.51 <damageSpan>

<damageSpan> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
Member of
Contained by
May containEmpty element
Note

Both the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor> element may be used for this purpose.

The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 12.3.3.1. Damage, Illegibility, and Supplied Text and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

Example
<p>Paragraph partially damaged. This is the undamaged portion <damageSpan spanTo="#a34"/>and this the damaged portion of the paragraph.</p> <p>This paragraph is entirely damaged.</p> <p>Paragraph partially damaged; in the middle of this paragraph the damage ends and the anchor point marks the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p>
Schematron
<sch:rule context="tei:damageSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:damageSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element damageSpan
{
   ws_att.global.attributes,
   ws_att.damaged.attributes,
   ws_att.spanning.attributes,
   ws_att.typed.attributes,
   empty
}

Appendix A.52 <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="wwp:date/@type"> <sch:assert test="../parent::wwp:imprint/parent::wwp:monogr/ancestor::wwp:sourceDesc"> An issuance date should only occur in a monogr element inside a source description in the TEI header. </sch:assert> </sch:rule>
Legal values are:
issuance
indicates a publication date for a single issue, volume, or other portion of a serially-published text.
Member of
Contained by
May contain
Note
A B.C. date is encoded per ISO 8601:2019 (not ISO 8601:1988 and thus TEI), which (like the astronomical calendar) has a year 0. Thus the year AD 1 (or 1 CE, 0001) was immediately preceded by the year BC 1 (or 1 BCE, 0000), which was immediately preceded by the year BC 2 (or 2 BCE, -0001).
<date when="-1077">1078 B.C.</date>

Unlike TEI, where the temporal attributes like when and notAfter are normalizations of the date in question to Gregorian or proleptic Gregorian, at the WWP temporal attributes are merely regularized versions of the date as presented in the source, i.e. whether it be in Gregorian, Julian (aka ‘N.S.’ or ‘O.S.’), or something else, only the format is changed.

Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Schematron
<sch:pattern> <sch:rule context="tei:application |tei:date[ not(@prev) and ( @calendar = ('#cal_Gregorian','#cal_NS','#cal_Julian') or not( @calendar ) ) ] |tei:time[ not(@prev) and ( @calendar = ('#cal_Gregorian','#cal_NS','#cal_Julian') or not( @calendar ) ) ]">  <sch:assert test="@when or @when-custom or @when-iso or @notBefore or @notBefore-custom or @notBefore-iso or @notAfter or @notAfter-iso or @notAfter-custom or @from or @from-custom or @from-iso or @to or @to-custom or @to-iso">At least one temporal normalization attribute should be specified on a <<sch:value-of select="name(.)"/>><sch:value-of select="if (@calendar) then concat(' with calendar=', @calendar) else ''"/> (unless it has @prev).</sch:assert> </sch:rule> </sch:pattern>
Schematron
<sch:pattern> <sch:rule context="tei:date[ @prev or @calendar = ('#cal_Mundi','#cal_undetermined') ] |tei:time[ @prev or @calendar = ('#cal_Mundi','#cal_undetermined') ]">  <sch:report test="@when or @when-custom or @when-iso or @notBefore or @notBefore-custom or @notBefore-iso or @notAfter or @notAfter-iso or @notAfter-custom or @from or @from-custom or @from-iso or @to or @to-custom or @to-iso">No temporal normalization attributes may be specified on a <<sch:value-of select="name(.)"/>> that has <sch:value-of select="if (@prev) then 'a @prev attriute' else concat('has calendar=', @calendar )"/>.</sch:report> </sch:rule> </sch:pattern>
Schematron
<sch:rule context="tei:docDate/tei:date"> <sch:let name="dateLen"  value="string-length(normalize-space(.) )"/> <sch:let name="docDateLen"  value="string-length(normalize-space(..))"/> <sch:report test="$docDateLen - $dateLen gt 2"  role="warn">Having a date element nested inside a docDate is rarely required</sch:report> <sch:report test="$docDateLen - $dateLen le 2"  role="error">The date element is not used inside docDate to represent the same date as the docDate — just use the attributes of docDate.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:date/@cert"> <sch:assert test="ancestor::wwp:sourceDesc">Here at the WWP we only indicate uncertain dates inside the <sourceDesc>.</sch:assert> <sch:assert test="normalize-space(.) eq 'low'">The value of @cert on <date> should be "low" (or there should be no @cert).</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:imprint/tei:date[2]"> <sch:let name="numDates"  value="count( ../tei:date )"/> <sch:let name="numIssua"  value="count( ../tei:date[@type eq 'issuance'] )"/> <sch:assert test="$numDates - $numIssua = 1">One and only of these <date> elements should NOT have type=issuance; all the others should.</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   ws_att.global.attributes,
   ws_att.calendarSystem.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "issuance" }?,
   ( text | ws_model.gLike | ws_model.phrase | ws_model.global )*
}

Appendix A.53 <dateline>

<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. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Member of
Contained by
core: lg list
drama: castList
figures: table
May contain
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
  <elementRef key="docDate"/>
 </alternate>
</content>
    
Schema Declaration
element dateline
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ( text | ws_model.gLike | ws_model.phrase | ws_model.global | ws_docDate )*
}

Appendix A.54 <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

At the WWP we do not (currently) use type on <del>.

Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegiblequantity="5"   unit="character"/> </del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.dimensions.attributes,
   ws_att.transcriptional.attributes,
   ws_att.typed.attribute.subtype,
   ws_macro.paraContent
}

Appendix A.55 <delSpan>

<delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [12.3.1.4. Additions and Deletions]
Moduletranscr
Attributes
Member of
Contained by
May containEmpty element
Note

Both the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan> element, the ending by the target of the spanTo attribute.

The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <delSpan> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element should be used to signal the areas of text which cannot be read with confidence. See further sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the <delSpan> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

The <delSpan> tag should not be used for deletions made by editors or encoders. In these cases, either the <corr> tag or the <gap> tag should be used.

Example
<p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p>
Schematron
<sch:rule context="tei:delSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:delSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element delSpan
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.spanning.attributes,
   ws_att.transcriptional.attributes,
   ws_att.typed.attributes,
   empty
}

Appendix A.56 <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
deprecationInfo
(deprecation information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec module="tei"  ident="teidata.point"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
Contained by
May contain
Note

When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

ExampleExample of a <desc> element inside a documentation element.
<dataSpec module="tei"  ident="teidata.point">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
ExampleExample of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
SchematronA <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.translatable.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "deprecationInfo" }?,
   ws_macro.limitedContent
}

Appendix A.57 <dimensions>

<dimensions> (dimensions) contains a dimensional specification. [11.3.4. Dimensions]
Modulemsdescription
Attributes
typeindicates which aspect of the object is being measured.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
leaves
dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)
ruled
dimensions relate to the area of a leaf which has been ruled in preparation for writing.
pricked
dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable).
written
dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.
miniatures
dimensions relate to the miniatures within the manuscript
binding
dimensions relate to the binding in which the codex or manuscript is contained
box
dimensions relate to the box or other container in which the manuscript is stored.
Member of
Contained by
May contain
derived-module-wwp-store: format
msdescription: height width
Note

Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
ExampleThis element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="reliefunit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
ExampleWhen simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height unit="cmscope="most"   quantity="90"/>  <width unit="cmscope="mostquantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
Schematron
<sch:rule context="tei:dimensions"> <sch:report test="count(tei:width) gt 1"> The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:height) gt 1"> The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:depth) gt 1"> The element <sch:name/> may appear once only </sch:report> </sch:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="format"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="height"/>
   <elementRef key="width" minOccurs="0"/>
   <elementRef key="depth" minOccurs="0"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="width"/>
   <elementRef key="depth" minOccurs="0"/>
  </sequence>
  <elementRef key="depth"/>
 </alternate>
</content>
    
Schema Declaration
element dimensions
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { text }?,
   (
      ws_format
    | ( ws_height, ws_width?, depth? )
    | ( ws_width, depth? )
    | depth
   )
}

Appendix A.58 <distinct>

<distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
Modulecore
Attributes
typespecifies the sublanguage or register to which the word or phrase is being assigned.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
timespecifies how the phrase is distinct diachronically.
StatusOptional
Datatypeteidata.text
spacespecifies how the phrase is distinct diatopically.
StatusOptional
Datatypeteidata.text
socialspecifies how the phrase is distinct diastratically.
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
Example
Next morning a boy in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct> keep secret.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distinct
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute time { text }?,
   attribute space { text }?,
   attribute social { text }?,
   ws_macro.phraseSeq
}

Appendix A.59 <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back body div front
May contain
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:pattern> <sch:rule context="tei:div[ @type eq 'epigraph'][ descendant::tei:epigraph ]">  <sch:assert test="true()"/> </sch:rule> <sch:rule context="tei:div[ not( @type eq 'epigraph') ]">  <sch:assert test="descendant::tei:div or descendant::tei:l[ not( ancestor::tei:epigraph )] or descendant::tei:ab[ not( ancestor::tei:epigraph )] or descendant::tei:p[ not( ancestor::tei:epigraph )] or descendant::tei:floatingText[ not( ancestor::tei:epigraph )] or descendant::tei:lg[ not( ancestor::tei:epigraph )] or descendant::tei:sp[ not( ancestor::tei:epigraph )] or descendant::tei:bibl[ not( ancestor::tei:epigraph )] or descendant::tei:biblFull or descendant::tei:biblStruct[ not( ancestor::tei:epigraph )] or descendant::tei:list[ not( ancestor::tei:epigraph )] or descendant::tei:listBibl[ not( ancestor::tei:epigraph )] or descendant::tei:table[ not( ancestor::tei:epigraph )] or descendant::tei:listEvent or descendant::tei:quote[ not( ancestor::tei:epigraph )] or descendant::tei:stage[ not( ancestor::tei:epigraph )] or descendant::tei:castList[ not( ancestor::tei:epigraph )] or descendant::tei:gap[ not( ancestor::tei:epigraph )] or descendant::tei:join or descendant::tei:joinGrp or descendant::wwp:advertisement[ not( ancestor::tei:epigraph )] or descendant::tei:note[ not( ancestor::tei:epigraph )] or descendant::tei:figure[ not( ancestor::tei:epigraph )] or descendant::wwp:unknown[ not( ancestor::tei:epigraph )] or descendant::tei:trailer or descendant::wwp:elision[ not( ancestor::tei:epigraph )]"><<sch:name/>> with no significant content (i.e., none of: ab advertisement bibl biblFull biblStruct castList div elision figure floatingText gap join joinGrp l lg list listBibl listEvent note p quote sp stage trailer unknown)</sch:assert> </sch:rule> </sch:pattern>
Schematron
<sch:rule context="wwp:div[ @type eq 'contents']"> <sch:assert test=".//wwp:*[ @type eq 'toc']"> A division intended for a table of contents should have one (e.g., a <list type="toc">). </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:div"> <sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.common"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divLike"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   ws_att.structuralCategorization.attributes,
   ws_att.global.attributes,
   ws_att.declaring.attributes,
   ws_att.divLike.attributes,
   ws_att.written.attributes,
   (
      ( ws_model.divTop | ws_model.global )*,
      (
         ( ( ws_model.divLike, ws_model.global* )+ )
       | (
            ( ( ws_model.common, ws_model.global* )+ ),
            ( ( ws_model.divLike, ws_model.global* )* )
         )
      )?,
      ( ( ws_model.divBottom, ws_model.global* )* )
   )
}

Appendix A.60 <docRole>

<docRole> (document role) contains an indication of a person or organization who played a significant role in the production of the source book, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]
Moduletextstructure
Attributes
type
StatusRequired
Legal values are:
author
A person who has written some or all of the main content of the text
editor
A person who has edited the text without contributing to its main content (adding annotations or providing other editorial oversight)
translator
A person who has translated the main content of the text from one language into another
publisher
A person or entity responsible for the publication (i.e. the sponsorship of the production and dissemination) of the work; in some cases this may be the author
printer
A person or entity responsible for the physical printing process
bookseller
A person or entity responsible for the sale and distribution of the work
printer-publisher
A person or entity who undertook both responsibilities or performed both tasks
licensee
licensor
uncertain
Member of
Contained by
May contain
Note

The document author's name often occurs within a byline, but the <docRole> element may be used whether the <respLine> element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with <respLine> without <docRole>.)

Example
<titleBlock>  <docTitle>   <titlePart>Travels into Several Remote Nations of the World, in Four      Parts.</titlePart>  </docTitle>  <respLine> By <docRole>Lemuel Gulliver</docRole>, First a Surgeon,    and then a Captain of several Ships</respLine> </titleBlock>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docRole
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   attribute type
   {
      "author"
    | "editor"
    | "translator"
    | "publisher"
    | "printer"
    | "bookseller"
    | "printer-publisher"
    | "licensee"
    | "licensor"
    | "uncertain"
   },
   ws_macro.phraseSeq
}

Appendix A.61 <docAuthorization>

<docAuthorization> contains a formal statement authorizing the publication of a work; differs from <imprimatur> because FIXME .
Modulederived-module-wwp-store
Attributes
Member of
Contained by
textstructure: back front titleBlock
May contain
Note

We have 4 elements for this kind of thing:

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element docAuthorization { ws_att.global.attributes, ws_macro.paraContent }

Appendix A.62 <docDate>

<docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

Cf. the general <date> element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it.

Example
<docImprint>Oxford, Clarendon Press, <docDate>1987</docDate> </docImprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docDate
{
   ws_att.global.attributes,
   ws_att.calendarSystem.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_macro.phraseSeq
}

Appendix A.63 <docEdition>

<docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titleBlock
May contain
Note

Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

Example
<docEdition>The Third edition Corrected</docEdition>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element docEdition { ws_att.global.attributes, ws_macro.paraContent }

Appendix A.64 <docImprint>

<docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titleBlock
May contain
Note

Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

Example
<docImprint>Oxford, Clarendon Press, 1987</docImprint>
Imprints may be somewhat more complex:
<docImprint>  <pubPlace>London</pubPlace> Printed for <name>E. Nutt</name>, at <pubPlace>Royal Exchange</pubPlace>; <name>J. Roberts</name> in <pubPlace>wick-Lane</pubPlace>; <name>A. Dodd</name> without <pubPlace>Temple-Bar</pubPlace>; and <name>J. Graves</name> in <pubPlace>St. James's-street.</pubPlace>  <date>1722.</date> </docImprint>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="pubPlace"/>
  <elementRef key="docDate"/>
  <elementRef key="publisher"/>
  <elementRef key="docAuthor"/>
  <elementRef key="docSale"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element docImprint
{
   ws_att.global.attributes,
   (
      text
    | ws_model.gLike
    | ws_model.phrase
    | ws_pubPlace
    | ws_docDate
    | ws_publisher
    | ws_docAuthor
    | ws_docSale
    | ws_model.global
   )*
}

Appendix A.65 <docSale>

<docSale> (document sales information) used to encode commercial transaction infromation (e.g., price) as appears in a <titleBlock>.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
textstructure: docImprint titleBlock
May contain
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element docSale { ws_att.global.attributes, ws_macro.specialPara }

Appendix A.66 <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
derived-module-wwp-store: advertisement
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { ws_att.global.attributes, ws_macro.phraseSeq }

Appendix A.67 <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
derived-module-wwp-store: translator
linking: ab
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   ws_att.global.attributes,
   ( ws_model.pLike+ | ( ws_edition, ws_model.respLike* ) )
}

Appendix A.68 <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
Note

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

Example
<editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element editor
{
   ws_att.global.attributes,
   ws_att.datable.attributes,
   ws_att.naming.attributes,
   ws_macro.phraseSeq
}

Appendix A.69 <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.editorialDeclPart"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   ( ( ws_model.editorialDeclPart+, ws_model.pLike* ) | ws_model.pLike+ )
}

Appendix A.70 <elision>

<elision> marks cases in which material is excerpted in a quotation or other textual representation within the source text.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
May contain
derived-module-wwp-store: advertisement elision unknown
figures: figure
gaiji: g
linking: alt anchor link
character data
ExampleI (Syd) think this would be how this should be used, but I may be mistaken; or we may change our minds.
<lg> <!-- ... -->  <l>Beneath accumulated horror, ſinks</l>  <l>The deſolate mourner!</l> </lg> <elision>  <lb/>* * * * * * * * * * <lb/>* * * * * * * * * * <lb/>* * * * * * * * * * </elision> <lg type="indeterminate">  <l>The feudal Chief, whoſe <rs type="properAdjective">Gothic</rs> battlements</l>  <l>Frown on the plain beneath, returning home</l> <!-- ... --> </lg>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.global"/>
  <macroRef key="macro.xtext"/>
 </alternate>
</content>
    
Schema Declaration
element elision
{
   ws_att.global.attributes,
   ws_att.typed.attributes,
   ws_att.dimensions.attributes,
   ( ws_model.global | ws_macro.xtext )+
}

Appendix A.71 <email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The format of a modern Internet email address is defined in RFC 2822

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_macro.phraseSeq
}

Appendix A.72 <emph>

<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
Contained by
May contain
Example
You took the car and did <emph>what</emph>?!!
Example
<q>What it all comes to is this,</q> he said. <q>  <emph>What    does Christopher Robin do in the morning nowadays?</emph> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element emph
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.73 <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Member of
Contained by
header: teiHeader
May contain
core: p
derived-module-wwp-store: include
gaiji: charDecl
linking: ab
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element encodingDesc
{
   ws_att.global.attributes,
   ( ws_model.encodingDescPart | ws_model.pLike )+
}

Appendix A.74 <epigraph>

<epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
core: bibl lg list
drama: castList
figures: table
May contain
Example
<epigraph xml:lang="la">  <cit>   <bibl>Lucret.</bibl>   <quote>    <l part="F">petere inde coronam,</l>    <l>Vnde prius nulli velarint tempora Musae.</l>   </quote>  </cit> </epigraph>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.common"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element epigraph
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ( ws_model.common | ws_model.global )*
}

Appendix A.75 <ex>

<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [12.3.1.2. Abbreviation and Expansion]
Moduletranscr
Attributes
Member of
Contained by
May contain
gaiji: g
character data
Example
The address is Southmoor <choice>  <expan>R<ex>oa</ex>d</expan>  <abbr>Rd</abbr> </choice>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element ex
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   ws_macro.xtext
}

Appendix A.76 <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<choice xml:lang="la">  <abbr>Imp</abbr>  <expan>Imp<ex>erator</ex>  </expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.editLike.attributes,
   ws_macro.phraseSeq
}

Appendix A.77 <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
derived-module-wwp-store: advertisement
header: fileDesc
May contain
core: measure
msdescription: dimensions
Example
<extent>  <measure unit="pagesquantity="48"/> </extent> <extent>  <dimensions unit="cmtype="leaves">   <format>quarto</format>   <height>19</height>   <width>13</width>  </dimensions> </extent>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="measure"/>
  <elementRef key="dimensions"/>
 </alternate>
</content>
    
Schema Declaration
element extent { ws_att.global.attributes, ( ws_measure | ws_dimensions ) }

Appendix A.78 <fallback>

<fallback> Wrapper for fallback elements if an XInclude fails
Namespacehttp://www.w3.org/2001/XInclude
Modulederived-module-wwp-store
Contained by
derived-module-wwp-store: include
May containANY
Content model
<content>
 <anyElement/>
</content>
    
Schema Declaration
element fallback { anyElement_fallback_1 }

Appendix A.79 <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. [15.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Contained by
figures: figure
May contain
Note

This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Example
<figure>  <graphic url="emblem1.png"/>  <head>Emblemi d'Amore</head>  <figDesc>A pair of naked winged cupids, each holding a    flaming torch, in a rural setting.</figDesc> </figure>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element figDesc { ws_att.global.attributes, ws_macro.limitedContent }

Appendix A.80 <figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Member of
Contained by
May contain
Example
<figure>  <head>The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc>  <graphic url="http://www.example.org/fig1.png"   scale="0.5"/> </figure>
Content model
<content>
 <classRef key="model.global" minOccurs="0"
  maxOccurs="unbounded"/>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="head"/>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <elementRef key="lg"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="figDesc"/>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
 <sequence minOccurs="0" maxOccurs="1">
  <elementRef key="floatingText"/>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <elementRef key="lg"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element figure
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attributes,
   ws_att.written.attributes,
   ws_model.global*,
   ( ( ws_head, ws_model.global* )* ),
   ( ( ( ws_model.pLike | ws_lg ), ws_model.global* )* ),
   ( ws_figDesc, ws_model.global* ),
   ( ( ws_floatingText, ws_model.global* )? ),
   ( ( ( ws_model.pLike | ws_lg ), ws_model.global* )* )
}

Appendix A.81 <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
derived-module-wwp-store: include
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="titleStmt"/>
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="editionStmt"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="include" minOccurs="1"
     maxOccurs="1"/>
   </alternate>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   ws_att.global.attributes,
   (
      (
         ws_titleStmt,
         ( ws_editionStmt | ws_include ),
         ws_extent?,
         ws_publicationStmt,
         seriesStmt?,
         ws_notesStmt?
      ),
      ws_sourceDesc+
   )
}

Appendix A.82 <floatingText>

<floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]
Moduletextstructure
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Member of
Contained by
May contain
Note

A floating text has the same content as any other <text> and may thus be interrupted by another floating text, or contain a <group> of tesselated texts.

Example
<body>  <div type="scene">   <sp>    <p>Hush, the players begin...</p>   </sp>   <floatingText type="pwp">    <body>     <div type="act">      <sp>       <l>In Athens our tale takes place [...]</l>      </sp> <!-- ... rest of nested act here -->     </div>    </body>   </floatingText>   <sp>    <p>Now that the play is finished ...</p>   </sp>  </div> </body>
Schematron
<sch:rule context="wwp:floatingText"> <sch:let name="textID"  value="normalize-space( /wwp:TEI/wwp:text/@xml:id )"/> <sch:assert test="substring( normalize-space( @xml:id ), 1, 7 ) eq substring( $textID, 1, 7 )">floatingText TR# <sch:value-of select="@xml:id"/> does not match main text TR# <sch:value-of select="$textID"/>.</sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="hyperDiv"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element floatingText
{
   ws_att.structuralCategorization.attributes,
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmllang,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.rend,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.responsibility.attribute.resp,
   ws_att.global.source.attribute.source,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   attribute xml:id { text },
   (
      ws_model.global*,
      ( ( ws_hyperDiv, ws_model.global* )? ),
      ( ( ws_front, ws_model.global* )? ),
      ( ws_body | ws_group ),
      ws_model.global*,
      ( ( ws_back, ws_model.global* )? )
   )
}

Appendix A.83 <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore
Attributes
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign
{
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.xmlid,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.rend,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.responsibility.attribute.resp,
   ws_att.global.source.attribute.source,
   ws_att.cmc.attributes,
   attribute xml:lang { text },
   ws_macro.phraseSeq
}

Appendix A.84 <format>

<format> contains the named format of a printed item
Modulederived-module-wwp-store
Contained by
msdescription: dimensions
May containEmpty element
Content model
<content> 
 
 
 broadsheetduodecimofoliohalf-sheetoctavoquartounknown
 
</content>
    
Schema Declaration
element format
{
   "broadsheet"
 | "duodecimo"
 | "folio"
 | "half-sheet"
 | "octavo"
 | "quarto"
 | "unknown"
}

Appendix A.85 <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Note

Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla      pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί        θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently. ...</p>  </div> </front>
Example
<front>  <div type="abstract">   <div>    <head> BACKGROUND:</head>    <p>Food insecurity can put children at greater risk of obesity because        of altered food choices and nonuniform consumption patterns.</p>   </div>   <div>    <head> OBJECTIVE:</head>    <p>We examined the association between obesity and both child-level        food insecurity and personal food insecurity in US children.</p>   </div>   <div>    <head> DESIGN:</head>    <p>Data from 9,701 participants in the National Health and Nutrition        Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.        Child-level food insecurity was assessed with the US Department of        Agriculture's Food Security Survey Module based on eight        child-specific questions. Personal food insecurity was assessed with        five additional questions. Obesity was defined, using physical        measurements, as body mass index (calculated as kg/m2) greater than        or equal to the age- and sex-specific 95th percentile of the Centers        for Disease Control and Prevention growth charts. Logistic        regressions adjusted for sex, race/ethnic group, poverty level, and        survey year were conducted to describe associations between obesity        and food insecurity.</p>   </div>   <div>    <head> RESULTS:</head>    <p>Obesity was significantly associated with personal food insecurity        for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to        2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%        CI 0.51 to 1.51). Child-level food insecurity was not associated        with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>   </div>   <div>    <head> CONCLUSIONS:</head>    <p>Personal food insecurity is associated with an increased risk of        obesity only in children aged 6 to 11 years. Personal        food-insecurity measures may give different results than aggregate        food-insecurity measures in children.</p>   </div>  </div> </front>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence>
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence>
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   ws_att.global.attributes,
   ws_att.declaring.attributes,
   (
      (
         ws_model.frontPart
       | ws_model.pLike
       | ws_model.pLike.front
       | ws_model.global
      )*,
      (
         (
            (
               (
                  ws_model.div1Like,
                  ( ws_model.div1Like | ws_model.frontPart | ws_model.global )*
               )
             | (
                  ws_model.divLike,
                  ( ws_model.divLike | ws_model.frontPart | ws_model.global )*
               )
            ),
            (
               (
                  ws_model.divBottom,
                  ( ws_model.divBottom | ws_model.global )*
               )?
            )
         )?
      )
   )
}

Appendix A.86 <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
derived-module-wwp-store: advertisement
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.datable.attributes,
   ws_macro.phraseSeq.limited
}

Appendix A.87 <mw>

<mw> (metawork) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [12.6. Headers, Footers, and Similar Matter]
Moduletranscr
Attributes
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
border
used to signify that there is border around a page.
border-rule
used to signify that there is a border made of ruled lines.
border-ornamental
used to signify that there is an ornamental border.
catch
(catchword) for catch words.
lineNum
(line number) for printed line numbers (usually in poetry)
listHead
(list (or similar) heading) for list headings. Often used in tables of contents for the ‘page’ heading.
pageNum
(page number) for page numbers.
pressFig
(press figure) for press figures. These are usually numbers, but are not sequential or regularly printed like signatures.
sig
(signature) for printed signatures.
unknown
for a metawork whose function you do not know.
vol
(volume number) for printed volume numbers.
other
Anything not covered by the above values.
Note

We use other (among other possibilities) for an ornament, decorated tool line, or symbol(s) that is not officially a delimiter (and thus there is no element on which to put pre() or post()) but is used to fill space at the bottom of a page so that a <floatingText> or similar can start at the top of the next.

Member of
Contained by
May contain
Note

Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <mw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

Example
<mw type="sigplace="bottom">C3</mw>
SchematronDisallow most phrase-level encoding in catchwords and unspecified features used for organization
<sch:rule context="wwp:mw[ @type eq 'catch'] | wwp:rs[ @type eq 'ufo' ]"> <sch:let name="me"  value="if ( self::wwp:mw ) then 'a catchword' else 'an unspecified feature used for organization'"/> <sch:report test=" wwp:persName | wwp:placeName | wwp:name | wwp:vuji | wwp:choice | wwp:mcr | wwp:date | wwp:regMe | wwp:title | wwp:orgName | wwp:rs | wwp:ref[ @type ne 'error' ] | wwp:abbr | wwp:emph | wwp:term | wwp:bibl"> Precise phrase-level encoding (persName, placeName, name, vuji, mcr, date, regMe, title, orgName, etc.) should not occur in <sch:value-of select="$me"/>. </sch:report> </sch:rule>
SchematronNote: this ODD file contains a Schematron Quick Fix for easy repair of the two likely errors tested for, below. However, the regex attribute of <sqf:stringReplace> ‘must meet the requirements of the regex attribute of the <xsl:analyze-string> element’ according to the schema. In XSLT 2.0 that attribute has a restriction that the regular expression must not be one that matches a zero-length string. This restriction was removed in XSLT 3.0, and thus Saxon le 9.5 enforces this restriction, ge 9.6 does not. So whether this Quick Fix works or not depends on which version of oXygen (and thus which version of Saxon) you are running. Since our encoders are typically still using an older version of oXygen, this Quick Fix has been commented out for now.
<sch:rule context="wwp:mw[@type eq 'catch']"> <sch:report test="matches(@rend,'pre\([^#)]*\)')"> Generally speaking, delimters in a catchword are encoded as content, not on @rend. </sch:report> <sch:report test="matches(@rend,'post\([^#)]*\)')"> Generally speaking, delimters in a catchword are encoded as content, not on @rend. </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mw
{
   ws_att.global.attributes,
   ws_att.typed.attribute.subtype,
   ws_att.written.attributes,
   attribute type
   {
      "border"
    | "border-rule"
    | "border-ornamental"
    | "catch"
    | "lineNum"
    | "listHead"
    | "pageNum"
    | "pressFig"
    | "sig"
    | "unknown"
    | "vol"
    | "other"
   },
   ws_macro.phraseSeq
}

Appendix A.88 <g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
Modulegaiji
Attributes
refpoints to a description of the character or glyph intended.
StatusRequired
Datatypeteidata.pointer
Schematron
<sch:rule context="wwp:g[@ref][/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef]"> <sch:let name="ref"  value="substring( normalize-space( @ref ), 2 )"/> <sch:let name="reffed"  value="if ( //wwp:charDecl ) then id( $ref ) else document('../common-boilerplate.xml', /) // *[ @xml:id eq $ref ]"/> <sch:let name="test"  value="$reffed[ self::wwp:char ]"/> <sch:assert test="$test">The @ref of <g> should point to a <char>; this one (<sch:value-of select="@ref"/>) points to <sch:value-of select="if ($reffed) then concat('a <', name($reffed),'>') else 'nothing'"/>.</sch:assert> </sch:rule>
Member of
Contained by
May containEmpty element
Note

At the WWP, <g> is further constrained (than vanilla TEI) as follows:

  • must be empty
  • must have a ref attribute
  • the ref attribute must point to a <char>
Example
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier ctlig like the following:
<glyph xml:id="ctlig"> <!-- here we describe the particular ct-ligature intended --> </glyph>
Example
<g ref="#per-glyph">per</g>
The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows:
<glyph xml:id="per-glyph"> <!-- ... --> </glyph>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element g
{
   ws_att.global.attributes,
   ws_att.typed.attributes,
   attribute ref { text },
   empty
}

Appendix A.89 <gap>

<gap> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.
Modulecore
Attributes
unit
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
chars
(characters) characters of text
words
words, i.e. whitespace-separated tokens
lines
lines of text
pages
pages, i.e. one side of a leaf
cm
(centimetres)
mm
(millimetres)
in
(inches)
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Derived fromatt.dimensions
StatusRequired
Datatypeteidata.text
reason
StatusRequired
Datatypeteidata.enumerated
Legal values are:
damaged
the text has been damaged due to tearing, creasing, folding, fire, insects, etc.
excerpt
a portion of the text has been deliberately omitted from the larger document as determined by the WWP's editorial policy
flawed-reproduction
for cases where the illegibility is caused by our reproduction of the text, and we have reason to believe the original is still legible (e.g. edges have been unintentionally cropped during copying or filming, under- or over-exposure, objects superimposed on the original when it was reproduced)
illegible-handwriting
for cases where the illegibility is caused by handwriting that the modern encoder cannot read
obscured
the page is intact but the original text is illegible for some reason other than deletion (e.g. water staining, uninked letters)
omitted
for features which our policy is to ignore (bookplates, embossing, stamping, modern handwriting, etc.)
other
used only when none of the above values are appropriate
handin the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, signifies the hand which made the deletion.
StatusOptional
Datatypeteidata.pointer
Schematron
<sch:pattern> <sch:rule context="*[ starts-with( @hand,'#') ]">  <sch:assert test="//wwp:handNote[ @xml:id = substring-after( current()/@hand,'#') ]">hand= attribute of <<sch:name/>> does not point to a <handNote> (local)</sch:assert> </sch:rule> <sch:rule context="*[ contains( @hand,'#') ]">  <sch:assert test="document( substring-before( @hand,'#') ) //wwp:handNote[ @xml:id = substring-after( current()/@hand,'#') ]">hand= attribute of <<sch:name/>> does not point to a <handNote> (external)</sch:assert> </sch:rule> <sch:rule context="*[@hand]">  <sch:report test="not(contains(@hand,'#'))">hand=    attribute of <<sch:name/>> must point to particular    <handNote> element via its xml:id=</sch:report> </sch:rule> </sch:pattern> <sch:pattern> <sch:rule context="wwp:gap[@hand|@agent|@degree|@group]">  <sch:assert test="substring-before( @reason, '-') ='damaged'"> The    hand=, agent=, degree=, and group= attributes of    <<sch:name/>> should only be specified if the reason= attribute is one that    indicates damage in the source (i.e., starts with “damaged-”).</sch:assert> </sch:rule> </sch:pattern>
Valuesmust be one of the hand identifiers declared in the document header (see section 12.3.2.1. Document Hands).
desc
StatusRequired
Legal values are:
attachment
for anything stuck, glued, stapled, or otherwise affixed to the page (e.g. bookplates)
embossing
for anything added to the page by embossing or other forms of pressure (including pricking holes in the page)
handwriting
for handwriting that has been added to the printed original
printed
for text or images printed on the page
unknown
for cases where we don't know what has been omitted (e.g. if the page has been torn out and we cannot tell what was on it)
other
used only when none of the above values are appropriate
Member of
Contained by
May containEmpty element
Note

The WWP version of <gap> has some additional restrictions and a transormation. The restrictoins are on the

Schematron
<sch:rule context="wwp:gap"> <sch:report role="error"  test=" ( @reason = ('damaged','deleted','obscured','flawed-reproduction','excerpt','other') and @desc = ('attachment','embossing') ) or ( @reason eq 'obscured' and @desc eq 'unknown' ) ">reason="<sch:value-of select="@reason"/>" and desc="<sch:value-of select="@desc"/>" of <gap> is an invalid combination</sch:report> <sch:report role="warning"  test=" ( @reason = ('deleted','flawed-reproduction','excerpt','omitted','illegible-handwriting') and @desc eq 'unknown' ) or ( @reason eq 'other' and @desc = ('handwriting','printed') ) ">are you sure the combination of reason="<sch:value-of select="@reason"/>" and desc="<sch:value-of select="@desc"/>" of <gap> makes sense?</sch:report> <sch:assert role="error"  test="if ( @desc eq 'other' ) then id( substring( normalize-space( @corresp ), 2 ) )[self::wwp:note] else true()">When the description is just "other", there should be a <gi>note</gi> explaining the gap (and @corresp should point to that note)</sch:assert> <sch:report role="error"  test="@reason eq 'illegible-handwriting' and @desc ne 'handwriting'">When the reason a gap is not readable is 'illegible-handwriting', then the description of that which is unreadable should be 'handwriting'</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element gap
{
   ws_att.global.attributes,
   attribute unit
   {
      "chars" | "words" | "lines" | "pages" | "cm" | "mm" | "in"
   }?,
   attribute extent { text },
   attribute reason
   {
      "damaged"
    | "excerpt"
    | "flawed-reproduction"
    | "illegible-handwriting"
    | "obscured"
    | "omitted"
    | "other"
   },
   attribute hand { text }?,
   attribute desc
   {
      "attachment"
    | "embossing"
    | "handwriting"
    | "printed"
    | "unknown"
    | "other"
   },
   empty
}

Appendix A.90 <gi>

<gi> (element name) contains the name (generic identifier) of an element. [23. Documentation Elements 23.5. Element Specifications]
Moduletagdocs
Attributes
schemesupplies the name of the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
this element is part of the TEI scheme.[Default]
DBK
(docbook) this element is part of the Docbook scheme.
XX
(unknown) this element is part of an unknown scheme.
Schematron
this element is from Schematron.
HTML
this element is from the HTML scheme.
Member of
Contained by
May contain
XSD Name
Example
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element gi
{
   ws_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}

Appendix A.91 <gloss>

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Content model
<content>
 <sequence minOccurs="1"
  maxOccurs="unbounded">
  <macroRef key="macro.phraseSeq"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element gloss
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.pointing.attribute.targetLang,
   ws_att.pointing.attribute.evaluate,
   ws_att.translatable.attributes,
   ws_att.typed.attributes,
   ( ( ws_macro.phraseSeq, ws_quote* )+ )
}

Appendix A.92 <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
Note

The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded.

Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<facsimile>  <surfaceGrp n="leaf1">   <surface>    <graphic url="page1.png"/>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>   </surface>  </surfaceGrp> </facsimile>
Example
<facsimile>  <surfaceGrp n="leaf1xml:id="spi001">   <surface xml:id="spi001r">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001r.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001r.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001v.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001v.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic type="normal"      subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>     <graphic type="normal"      subtype="low-res"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic type="normal"      subtype="high-res"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="low-res"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="high-res"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element graphic
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.media.attributes,
   ws_att.resourced.attributes,
   ws_att.typed.attributes,
   ws_model.descLike*
}

Appendix A.93 <group>

<group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText group text
May contain
Example
<text> <!-- Section on Alexander Pope starts -->  <front> <!-- biographical notice by editor -->  </front>  <group>   <text> <!-- first poem -->   </text>   <text> <!-- second poem -->   </text>  </group> </text> <!-- end of Pope section-->
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence>
   <alternate>
    <elementRef key="text"/>
    <elementRef key="group"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="text"/>
    <elementRef key="group"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
  <classRef key="model.divBottom"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element group
{
   ws_att.global.attributes,
   ws_att.declaring.attributes,
   ws_att.typed.attributes,
   (
      ( ws_model.divTop | ws_model.global )*,
      ( ( ws_text | ws_group ), ( ws_text | ws_group | ws_model.global )* ),
      ws_model.divBottom*
   )
}

Appendix A.94 <handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
transcr: handNotes
May contain
Example
<handNotes>  <handNote xml:id="yien.major_hand"   scope="majormedium="brown_inkscribe="author"   scribeRef="#KL">Handwriting of the copyist Karol Libelt, brown ink, in German cursive script.</handNote>  <handNote xml:id="yien.pencil"   scope="minormedium="pencilscribe="annotator">A note, pencil, unknown author.</handNote>  <handNote xml:id="yien.pencil2"   scope="minormedium="pencilscribe="archivist">Writer of the title page Józef Łepkowski, pencil.</handNote>  <handNote xml:id="yien.pencil3"   scope="minormedium="pencilscribe="archivist2"   scribeRef="#BJK">Note on the title page, pencil, by Józef Korzeniowski.</handNote> </handNotes>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element handNote
{
   ws_att.global.attributes,
   ws_att.handFeatures.attributes,
   ws_macro.specialPara
}

Appendix A.95 <handNotes>

<handNotes> contains one or more <handNote> elements documenting the different hands identified within the source texts. [12.3.2.1. Document Hands]
Moduletranscr
Attributes
Member of
Contained by
header: profileDesc
May contain
header: handNote
Example
<handNotes>  <handNote xml:id="H1script="copperplate"   medium="brown-ink">Carefully written with regular descenders</handNote>  <handNote xml:id="H2script="print"   medium="pencil">Unschooled scrawl</handNote> </handNotes>
Content model
<content>
 <elementRef key="handNote" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element handNotes { ws_att.global.attributes, ws_handNote+ }

Appendix A.96 <handShift>

<handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [12.3.2.1. Document Hands]
Moduletranscr
Attributes
newindicates a <handNote> element describing the hand concerned.
StatusRecommended
Datatypeteidata.pointer
Note

This 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.

Member of
Contained by
May containEmpty element
Note

The <handShift> element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

Example
<l>When wolde the cat dwelle in his ynne</l> <handShift medium="greenish-ink"/> <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element handShift
{
   ws_att.global.attributes,
   ws_att.handFeatures.attributes,
   attribute new { text }?,
   empty
}

Appendix A.97 <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
sub
Member of
Contained by
May contain
Note

The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
ExampleThe <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attribute.subtype,
   ws_att.written.attributes,
   attribute type { "sub" }?,
   (
      text
    | ws_lg
    | ws_model.gLike
    | ws_model.phrase
    | ws_model.inter
    | ws_model.lLike
    | ws_model.global
   )*
}

Appendix A.98 <headItem>

<headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headItem> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headItem { ws_att.global.attributes, ws_macro.phraseSeq }

Appendix A.99 <headLabel>

<headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headLabel> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headLabel { ws_att.global.attributes, ws_macro.phraseSeq }

Appendix A.100 <height>

<height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May contain
gaiji: g
character data
Example
<height unit="inquantity="7"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element height
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_macro.xtext
}

Appendix A.101 <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...
Schematron
<sch:rule context="tei:text//tei:hi | tei:text//tei:mcr | tei:text//tei:emph"> <sch:let name="myName"  value="local-name(.)"/> <sch:let name="myDefaultRendition"  value="/tei:TEI/tei:teiHeader/tei:encodingDesc/tei:tagsDecl/tei:rendition[ $myName = tokenize( @selector,'[ ,]+') ]"/> <sch:let name="myRealRend"  value="concat( $myDefaultRendition, @rend )"/> <sch:assert test="contains( $myRealRend, '(')">Wha? This <gi>  <sch:value-of select="$myName"/>  </gi> element has no (usable) rendition</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.102 <hyperDiv>

<hyperDiv> (hyper division) Those things that are part of the textual content of the document, or directly related to it, but do not fit into the front matter, body, or back matter.
Modulederived-module-wwp-store
Contained by
textstructure: floatingText text
May contain
derived-module-wwp-store: acrostics adds anagrams notes
drama: castList
linking: altGrp linkGrp
Note

Currently, the content of the <hyperDiv> is quite restrictive. It consists of 0 or 1 of each of the following, in the specified order:

  • <castList>, for speaking roles that occur in the drama, but for which there is no entry in the printed cast list.
  • <linkGrp>, for <link>s; at the moment we only use these for indicating a grouping of disparate elements
  • <altGrp> for <alt>s; at the moment we only use these for indicating an alternation of possible referents (e.g., ‘Green Lantern’ would be encoded with a ref that points to an <alt> that has target="#Guy_Garnder #John_Stewart").
  • <acrostics>, for <acrostic>s
  • <anagrams>, for <anagram>s
  • <adds>, for additions (encoded with <add>) that are the addition of a footnote or marginal note (encoded with <note>)
  • <notes>, for footnotes and marginal notes (encoded with <note>)

In the future we may consider loosening or re-arranging this.

Schematron
<sch:rule context="tei:adds/tei:add/child::*"> <sch:assert test="self::wwp:note">An <add> inside <adds> inside the <hyperDiv> should not have any children other than <note> (and there is a <<sch:name/>> here).</sch:assert> </sch:rule>
Content model
<content>
 <classRef key="model.hyperDivPart"
  expand="sequenceOptional"/>
</content>
    
Schema Declaration
element hyperDiv
{
   ws_castList?,
   ws_linkGrp?,
   ws_altGrp?,
   ws_acrostics?,
   ws_anagrams?,
   ws_adds?,
   ws_notes?
}

Appendix A.103 <hyphenation>

<hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
some
end-of-line hyphenation has been retained in some cases.[Default]
hard
all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
none
all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
Member of
Contained by
May contain
core: p
linking: ab
Example
<hyphenation eol="some">  <p>End-of-line hyphenation silently removed where appropriate</p> </hyphenation>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element hyphenation
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   ws_model.pLike+
}

Appendix A.104 <ident>

<ident> (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [23.1.1. Phrase Level Terms]
Moduletagdocs
Attributes
Member of
Contained by
May containCharacter data only
Note

In running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements <gi> and <att> are provided.

Example
<ident type="ns">http://www.tei-c.org/ns/Examples</ident>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element ident { ws_att.global.attributes, ws_att.typed.attributes, text }

Appendix A.105 <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
Attributes
typecategorizes the number, for example as an ISBN or other standard series.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
clu
(University of California, Los Angeles)
cluc
(William Andrews Clark Memorial Library)
csmh
(Henry E. Huntington Library)
cty
(Yale University, Sterling Memorial Library)
ctybr
(Yale University, Beinecke Library)
dfo
(Folger Shakespeare Library)
dlc
(US Library of Congress)
geu
(Emory University Library)
iau
(University of Iowa)
icj
(John Crerar Library)
icjkm
(Jesuit Krauss McCormick Library)
icn
(Newberry Library)
icrl
(Center for Research Libraries)
icu
(University of Chicago)
ien
(Northwestern University)
inre
(Earlham College Library)
inu
(Indiana University)
iu
(University of Illinois, Urbana)
mb
(Boston Public Library)
mbat
(Boston Athenæum)
mbco
(Harvard University Medical School, Countway Library)
mh
(Harvard University)
mhh
(Harvard University, Houghton Library)
miu
(University of Michigan)
mns
(Smith College)
mwa
(American Antiquarian Society)
nbrocku
(State University of New York, College at Brockport)
nhd
(Dartmouth College)
njp
(Princeton University)
nn
(New York Public Library)
nnc
(Columbia University)
nnut
(Union Theological Seminary)
npv
(Vassar College Library)
oonl
(Library and Archives Canada)
pp
(Free Library of Philadelphia)
pu
(University of Pennsylvania)
rpb
(Brown University)
rpjcb
(John Carter Brown Library)
uk
(British Library [duplicate])
uk
(British Library)
ukcu
(Cambridge University)
uklougc
(University of London, Goldsmith’s Library)
uklpr
(Public Record Office, London)
ukmajru
(John Rylands Library, University of Manchester)
ukoxu
(Bodleian Library)
ukoxu
(Oxford University, Bodleian Library [duplicate])
viu
(University of Virginia)
wimauma
(University of Wisconsin Madison Archives)
wlabnl
(National Library of Wales)
unknown
(unknown)
wwp:corvey
(The Corvey Library, Germany)
wwp:hindle
(C. J. Hindle collection, Bodleian)
wwp:iedt
(Trinity College, Dublin)
wwp:ukblt
(Thomason Collection, British Library)
wwp:ukoxw
(Worcester College, Oxford)
ou
(Ohio State University)
Evans
()
STC
(Short Title Catalogue)
Wing
()
Ca-MvGOO
(Google) Google Books
MiAaHDL
(Hathitrust)
MiAaPQ
(Proquest) I.e., EEBO and ECCO.
URL
(Uniform Resource Locator) This element contains the URL that points to the WWO ‘browsing’ version of this file. Typically http://www.wwp.northeastern.edu/texts/ followed by the name of the file with .html instead of .xml.
unknown
(unknown)
WWP
(Women Writers Project) This element contains the WWP transcription number, as obtained from the OT database. Generally speaking should match the regular expression TR[0-9]{5}. The same string is used as the value of xml:id of the main <text>.
Note

Values are listed with libraries first followed by catalogues followed by other values.

Most of these codes are obtained from MARC at the Library of Congress. Several, prefixed with wwp:, are constructed in a similar manner to MARC codes (e.g., using the country code as the first few chars) by the WWP because, at the time we added that library, MARC did not have a code for it.

Member of
Contained by
May contain
gaiji: g
header: idno
character data
Note

<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.sortable.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "clu"
    | "cluc"
    | "csmh"
    | "cty"
    | "ctybr"
    | "dfo"
    | "dlc"
    | "geu"
    | "iau"
    | "icj"
    | "icjkm"
    | "icn"
    | "icrl"
    | "icu"
    | "ien"
    | "inre"
    | "inu"
    | "iu"
    | "mb"
    | "mbat"
    | "mbco"
    | "mh"
    | "mhh"
    | "miu"
    | "mns"
    | "mwa"
    | "nbrocku"
    | "nhd"
    | "njp"
    | "nn"
    | "nnc"
    | "nnut"
    | "npv"
    | "oonl"
    | "pp"
    | "pu"
    | "rpb"
    | "rpjcb"
    | "uk"
    | "uk"
    | "ukcu"
    | "uklougc"
    | "uklpr"
    | "ukmajru"
    | "ukoxu"
    | "ukoxu"
    | "viu"
    | "wimauma"
    | "wlabnl"
    | "unknown"
    | "wwp:corvey"
    | "wwp:hindle"
    | "wwp:iedt"
    | "wwp:ukblt"
    | "wwp:ukoxw"
    | "ou"
    | "Evans"
    | "STC"
    | "Wing"
    | "Ca-MvGOO"
    | "MiAaHDL"
    | "MiAaPQ"
    | "URL"
    | "unknown"
    | "WWP"
   }?,
   ( text | ws_model.gLike | ws_idno )*
}

Appendix A.106 <imprimatur>

<imprimatur> (imprimatur) contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titleBlock
May contain
Example
<imprimatur>Licensed and entred acording to Order.</imprimatur>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <macroRef key="macro.paraContent"/>
  <elementRef key="docAuthor"/>
 </alternate>
</content>
    
Schema Declaration
element imprimatur
{
   ws_att.global.attributes,
   ( ws_macro.paraContent | ws_docAuthor )+
}

Appendix A.107 <imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: monogr
May contain
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate>
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt" minOccurs="0"
    maxOccurs="unbounded"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element imprint
{
   ws_att.global.attributes,
   (
      ( classCode | ws_catRef )*,
      (
         (
            ( ws_model.imprintPart | ws_model.dateLike ),
            ws_respStmt*,
            ws_model.global*
         )+
      )
   )
}

Appendix A.108 <include>

<include> The W3C XInclude element
Namespacehttp://www.w3.org/2001/XInclude
Modulederived-module-wwp-store
Attributes
hrefpointer to the resource being included
StatusOptional
Datatypeteidata.pointer
parse
StatusOptional
Legal values are:
xml
[Default]
text
xpointer
StatusOptional
Datatypeteidata.text
encoding
StatusOptional
Datatypeteidata.text
accept
StatusOptional
Datatypeteidata.text
accept-charset
StatusOptional
Datatypeteidata.text
accept-language
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
derived-module-wwp-store: fallback
Content model
<content>
 <elementRef key="fallback" minOccurs="0"/>
</content>
    
Schema Declaration
element include
{
   ws_att.global.attributes,
   attribute href { text }?,
   attribute parse { "xml" | "text" }?,
   attribute xpointer { text }?,
   attribute encoding { text }?,
   attribute accept { text }?,
   attribute accept-charset { text }?,
   attribute accept-language { text }?,
   ws_fallback?
}

Appendix A.109 <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
targetindicates the portion of the content to which this entry in the table of contents, index, or other reference list refers.
StatusRecommended
Datatype1–∞ occurrences of anyURI separated by whitespace
Schematron
<sch:rule context="wwp:list[ @type = ('index','reference','toc') ]/wwp:item/@target"> <sch:let name="targets" value="tokenize(.)"/> <sch:let name="myFileName"  value="( base-uri(/) => tokenize('/') )[last()]"/> <sch:let name="myAuthorName"  value="substring-before( $myFileName, '.')"/> <sch:let name="regexp"  value="'^((\./)?'||$myAuthorName||'\.[a-z0-9_-]+\.xml)?#\i\c*$'"/> <sch:let name="every_target_resolvable"  value="every $t in $targets satisfies if ( starts-with( $t,'#') ) then id( substring( $t, 2 ) ) else document( substring-before( $t,'#'), . )/id( substring-after( $t, '#') )"/> <sch:assert test="every $t in $targets satisfies matches( $t, $regexp )"> one (or more) of the pointers in this target is not in the proper format </sch:assert> <sch:assert test="$every_target_resolvable"> one (ore more) of the pointers in this target is not resolvable </sch:assert> </sch:rule>
Valuesreference to the xml:ids of element(s) to which this entry refers.
Note

For tables of contents, typically points to to a chapter, act, or poem encoded with a <div>. For indices may point to somewhat smaller chunks of text. If there are not already elements at the appropriate location, then generic <anchor> or <seg> elements must inserted and given xml:id values to be pointed at.

If the passage to be pointed at overlaps existing encoded logical structures, it should be encoded using multiple <seg> elements which should be pointed at with a <join> to which the target of <item> can point.

Contained by
core: list
May contain
Note

The WWP-added attribute target is only permitted an an <item> whose parent <list> has a type of toc, reference, or index.

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Schematron
<sch:pattern> <sch:rule context="wwp:list[ not( @type = ('toc', 'reference', 'index' ) ) ]">  <sch:report test="child::wwp:item/@target"><item> elements should only have target= attributes if the list is a table of contents, index, or other reference list</sch:report> </sch:rule> </sch:pattern>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="argument"/>
  <macroRef key="macro.specialPara"/>
 </alternate>
</content>
    
Schema Declaration
element item
{
   ws_att.global.attributes,
   ws_att.sortable.attributes,
   attribute target { list { + } }?,
   ( ws_argument | ws_macro.specialPara )*
}

Appendix A.110 <l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron
<sch:rule context="wwp:l"> <sch:report test="descendant::wwp:l">A metrical line should not contain a metrical line</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element l
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.fragmentable.attributes,
   (
      text
    | ws_model.gLike
    | ws_model.phrase
    | ws_model.inter
    | ws_model.global
   )*
}

Appendix A.111 <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
speaker
if this were drama, would be a <speaker>
Member of
Contained by
May contain
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attribute.subtype,
   ws_att.written.attributes,
   attribute type { "speaker" }?,
   ws_macro.phraseSeq
}

Appendix A.112 <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
linking: ab
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   ( ws_model.pLike+ | ws_language+ )
}

Appendix A.113 <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader
Attributes
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 may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   ws_att.global.attributes,
   ws_att.scope.attributes,
   attribute ident { text },
   attribute usage { text }?,
   ws_macro.phraseSeq.limited
}

Appendix A.114 <lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <lb> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking the beginning of each new topographic line on a manuscript or printed page, at the point where it occurs; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.

The type attribute may be used to characterize the line beginning in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the beginning of the new topographic line is word-breaking, or to note the source from which it derives.

ExampleThis example shows the encoding of the beginning of each new topographic line within a metrical line, indicating where it occurs in both the 1667 and 1674 editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
ExampleThis example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lb
{
   ws_att.global.attributes,
   ws_att.breaking.attributes,
   ws_att.cmc.attributes,
   ws_att.edition.attributes,
   ws_att.spanning.attributes,
   ws_att.typed.attributes,
   empty
}

Appendix A.115 <lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore
Attributes
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
common
couplet
couplet-heroic
drama
indeterminate
octet
ottava-rima
para
poem
quatrain
quintet
refrain
rime-royal
section
septet
sestet
spenserian
stanza
tercet
subtype
StatusOptional
Datatypeteidata.enumerated
Legal values are:
dramatic-verse
verse
indeterminate
stanzaic
sonnet-shakespearean
sonnet
sonnet-petrarchan
acrostic
ode-english
spatial
Member of
Contained by
May contain
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

Example
<lg type="free">  <l>Let me be my own fool</l>  <l>of my own making, the sum of it</l> </lg> <lg type="free">  <l>is equivocal.</l>  <l>One says of the drunken farmer:</l> </lg> <lg type="free">  <l>leave him lay off it. And this is</l>  <l>the explanation.</l> </lg>
Schematron
<sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.lLike"/>
   <elementRef key="said"/>
   <elementRef key="quote"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.lLike"/>
   <elementRef key="lg"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.stageLike"/>
    <classRef key="model.labelLike"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.divLike.attributes,
   attribute type
   {
      "common"
    | "couplet"
    | "couplet-heroic"
    | "drama"
    | "indeterminate"
    | "octet"
    | "ottava-rima"
    | "para"
    | "poem"
    | "quatrain"
    | "quintet"
    | "refrain"
    | "rime-royal"
    | "section"
    | "septet"
    | "sestet"
    | "spenserian"
    | "stanza"
    | "tercet"
   },
   attribute subtype
   {
      "dramatic-verse"
    | "verse"
    | "indeterminate"
    | "stanzaic"
    | "sonnet-shakespearean"
    | "sonnet"
    | "sonnet-petrarchan"
    | "acrostic"
    | "ode-english"
    | "spatial"
   }?,
   (
      ( ws_model.divTop | ws_model.stageLike | ws_model.global )*,
      ( ws_model.lLike | ws_said | ws_quote | ws_lg ),
      (
         ws_model.lLike
       | ws_lg
       | ws_model.stageLike
       | ws_model.labelLike
       | ws_model.global
      )*,
      (
         (
            ws_model.divBottom,
            ( ws_model.stageLike | ws_model.labelLike | ws_model.global )*
         )*
      )
   )
}

Appendix A.116 <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
header: availability
May contain
Note

A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence
{
   ws_att.global.attributes,
   ws_att.datable.attributes,
   ws_att.pointing.attributes,
   ws_macro.specialPara
}

Appendix A.117 <line>

<line> contains the transcription of a topographic line in the source document. [12.2.2. Embedded Transcription]
Moduletranscr
Attributes
Member of
Contained by
transcr: line
May contain
Note

This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use <l>) nor to mark line beginnings within text which has been encoded using structural elements such as <p> (for which use <lb>).

ExampleThis example shows topographical lines as a means of preserving the visual appearance of a poem:
<surface>  <zone>   <line>Poem</line>   <line>As in Visions of — at</line>   <line>night —</line>   <line>All sorts of fancies running through</line>   <line>the head</line>  </zone> </surface>
Example
<surface>  <zone>   <line>Hope you enjoyed</line>   <line>Wales, as they      said</line>   <line>to Mrs FitzHerbert</line>   <line>Mama</line>  </zone>  <zone>   <line>Printed in England</line>  </zone> </surface>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.global"/>
  <classRef key="model.gLike"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element line
{
   ws_att.global.attributes,
   ws_att.coordinated.attributes,
   ws_att.typed.attributes,
   ws_att.written.attributes,
   ( text | ws_model.global | ws_model.gLike | ws_model.linePart )*
}

Appendix A.119 <linkGrp>

<linkGrp> (link group) defines a collection of associations or hypertextual links. [17.1. Links]
Modulelinking
Attributes
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
core: desc ptr
linking: link
Note

May contain one or more <link> or <ptr> elements.

A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

Example
<linkGrp type="translation">  <link target="#CCS1 #SW1"/>  <link target="#CCS2 #SW2"/>  <link target="#CCS #SW"/> </linkGrp> <div type="volumexml:id="CCS"  xml:lang="fr">  <p>   <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>   <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>  </p> <!-- ... --> </div> <div type="volumexml:id="SWxml:lang="en">  <p>   <s xml:id="SW1">For a long time I used to go to bed early.</s>   <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>  </p> <!-- ... --> </div>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element linkGrp
{
   ws_att.global.attributes,
   ws_att.pointing.group.attributes,
   ( ws_model.descLike*, ( ws_link | ws_ptr )+ )
}

Appendix A.120 <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
subtype(subtype) provides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

type
StatusOptional
Legal values are:
toc
(table of contents)
errata
subscriber
gloss
Member of
Contained by
May contain
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
ExampleThe following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.sortable.attributes,
   attribute subtype { text }?,
   attribute type { "toc" | "errata" | "subscriber" | "gloss" }?,
   (
      ( ws_model.divTop | ws_model.global | ws_desc* )*,
      (
         ( ( ws_item, ws_model.global* )+ )
       | (
            ws_headLabel?,
            ws_headItem?,
            ( ( ws_label, ws_model.global*, ws_item, ws_model.global* )+ )
         )
      ),
      ( ( ws_model.divBottom, ws_model.global* )* )
   )
}

Appendix A.121 <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declarable.attributes,
   ws_att.sortable.attributes,
   ws_att.typed.attributes,
   (
      ws_model.headLike*,
      ws_desc*,
      ( ws_model.milestoneLike | relation | listRelation )*,
      (
         (
            ws_model.biblLike+,
            ( ws_model.milestoneLike | relation | listRelation )*
         )+
      )
   )
}

Appendix A.122 <listPrefixDef>

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
Member of
Contained by
May contain
ExampleIn this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psn"   matchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="bibl"   matchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="prefixDef"/>
   <elementRef key="listPrefixDef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listPrefixDef
{
   ws_att.global.attributes,
   ( ws_desc*, ( ws_prefixDef | ws_listPrefixDef )+ )
}

Appendix A.123 <listTranspose>

<listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [12.3.4.5. Transpositions]
Moduletranscr
Attributes
Member of
Contained by
May contain
core: desc
transcr: transpose
Example
<listTranspose>  <transpose>   <ptr target="#ib02"/>   <ptr target="#ib01"/>  </transpose> </listTranspose>
This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source.
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="transpose" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element listTranspose { ws_att.global.attributes, ( ws_desc*, ws_transpose+ ) }

Appendix A.124 <mapping>

<mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
valueThe Unicode Standard Notation of the character(s) to which the character or glyph being described should be mapped.
StatusOptional
Datatype1–8 occurrences of teidata.word separated by whitespace
Note

Since this is a space-separated list of values, if you actually need to indicate a space use U+0020.

Contained by
gaiji: char
May contain
gaiji: g
character data
Note

Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph> element or contain a character that is intended to be the target of this mapping.

Example
<mapping type="modern">r</mapping> <mapping type="standard"></mapping>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element mapping
{
   ws_att.global.attributes,
   ws_att.datable.attributes,
   ws_att.typed.attributes,
   attribute value { list { ?, ?, ?, ?, ?, ?, ? } }?,
   ws_macro.xtext
}

Appendix A.125 <mcr>

<mcr> (meaningful change in rendition) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made, other than there is some meaning present.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
May contain
Example
<p>  <mcr>Item</mcr>, 200 Crowns to <persName>Iſabella</persName> for undertaking. </p>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element mcr { ws_att.global.attributes, ws_macro.paraContent }

Appendix A.126 <measure>

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typespecifies the type of measurement in any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
ExampleThis example references a definition of a measurement unit declared in the TEI header:
<measure type="weight">  <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="merktype="area">    <label>merk</label>    <placeName ref="#Scotland"/>    <desc>A merk was an area of land determined variably by its agricultural        productivity.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure quantity="40unit="hogshead"  commodity="rum">2 score hh rum</measure> <measure quantity="12unit="count"  commodity="roses">1 doz. roses</measure> <measure quantity="1unit="count"  commodity="tulips">a yellow tulip</measure>
Example
<head>Long papers.</head> <p>Speakers will be given 30 minutes each: 20 minutes for presentation, 10 minutes for discussion. Proposals should not exceed <measure max="500unit="count"   commodity="words">500    words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element measure
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.measurement.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { text }?,
   ws_macro.phraseSeq
}

Appendix A.127 <mentioned>

<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mentioned
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_macro.phraseSeq
}

Appendix A.128 <metamark>

<metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [12.3.4.2. Metamarks]
Moduletranscr
Attributes
functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
StatusOptional
Datatypeteidata.word
targetidentifies one or more elements to which the metamark applies.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Example
<surface>  <metamark function="usedrend="line"   target="#X2"/>  <zone xml:id="zone-X2">   <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>   <line>The tears of foolish passion yet undried</line>   <line>upon my cheeks.</line> <!-- ... -->   <line>I pass through <add>the</add> travels and <del>fortunes</del> of   <retrace>thirty</retrace>   </line>   <line>years and become old,</line>   <line>Each in its due order comes and goes,</line>   <line>And thus a message for me comes.</line>   <line>The</line>  </zone>  <metamark function="used"   target="#zone-X2">Entered - Yes</metamark> </surface>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element metamark
{
   ws_att.global.attributes,
   ws_att.spanning.attributes,
   attribute function { text }?,
   attribute target { list { + } }?,
   ws_macro.specialPara
}

Appendix A.129 <milestone>

<milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]
Modulecore
Attributes
unit
StatusRequired
Datatypeteidata.enumerated
Legal values are:
sig
An idealized leaf signature. Typically should be a sequence of characters that indicate the printed signature (or what would be the printed signature if there were one) or first part thereof followed by a number (if the printed signature did not end with a number) and either ‘r’ (recto) or ‘v’ (verso), all optionally preceded by the word “facing” or “preceding” and a space. See https://www.wwp.neu.edu/research/publications/documentation/internal/#!/entry/signatures_narrative.
Member of
Contained by
May containEmpty element
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

The order in which <milestone> elements are given at a given point is not normally significant.

Example
<milestone n="23ed="Launit="Dreissiger"/> ... <milestone n="24ed="AVunit="verse"/> ...
SchematronTest that the n of a <milestone> that has a unit of sig has as its value a reasonable idealized signature. Note that this constraint is curently fired for all <milestone> elements. Luckily there are none other than idealized signatures.
<sch:rule context="wwp:milestone"> <sch:let name="me"  value="normalize-space(@n)"/> <sch:assert test="matches( $me,'((facing|preceding) )?(\p{L}|\p{M}|\p{N}|\p{P}|\p{S})*[0-9]+[\])]?[rv]')"> The idealized signature “<sch:value-of select="@n"/>” does not match the defintion thereof. </sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element milestone
{
   ws_att.global.attributes,
   ws_att.breaking.attributes,
   ws_att.cmc.attributes,
   ws_att.edition.attributes,
   ws_att.spanning.attributes,
   ws_att.typed.attributes,
   attribute unit { "sig" },
   empty
}

Appendix A.130 <mod>

<mod> represents any kind of modification identified within a single document. [12.3.4.1. Generic Modification]
Moduletranscr
Attributes
Member of
Contained by
May contain
Example
<mod type="subst">  <add>pleasing</add>  <del>agreable</del> </mod>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element mod
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.spanning.attributes,
   ws_att.transcriptional.attributes,
   ws_att.typed.attributes,
   ws_macro.paraContent
}

Appendix A.131 <monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item.

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope unit="pagefrom="377to="380">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title type="mainlevel="m">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title type="mainlevel="s">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <sequence>
    <alternate>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title" minOccurs="1"
     maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="edition"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   ws_att.global.attributes,
   (
      (
         (
            ( ws_author | ws_editor | meeting | ws_respStmt ),
            ( ws_author | ws_editor | meeting | ws_respStmt )*,
            ws_title+,
            ( ws_model.ptrLike | ws_idno | textLang | ws_editor | ws_respStmt )*
         )
       | (
            ( ws_title | ws_model.ptrLike | ws_idno )+,
            ( textLang | ws_author | ws_editor | meeting | ws_respStmt )*
         )
       | ( authority, ws_idno )
      )?,
      ws_availability*,
      ws_model.noteLike*,
      (
         (
            ws_edition,
            (
               ws_idno
             | ws_model.ptrLike
             | ws_editor
             | ws_sponsor
             | ws_funder
             | ws_respStmt
            )*
         )*
      ),
      ws_imprint,
      ( ws_imprint | ws_extent | ws_biblScope )*
   )
}

Appendix A.132 <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
properAdjective
file
(filename or filepath) An operating system filepath or filename
class
A TEI attribute or model class
macro
A TEI macro
constraint
A TEI constraint; i.e., the value of the ident attribute of a <constraintSpec>
Member of
Contained by
May contain
Note

Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.editLike.attributes,
   ws_att.personal.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "properAdjective" | "file" | "class" | "macro" | "constraint"
   }?,
   ws_macro.phraseSeq
}

Appendix A.133 <normalization>

<normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
Member of
Contained by
May contain
core: p
linking: ab
Example
<editorialDecl>  <normalization method="markup">   <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern      20th century typographical practice, the <gi>choice</gi> element has been used to      enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values      respectively. ... </p>  </normalization>  <normalization method="silent">   <p>Spacing between words and following punctuation has been regularized to zero spaces;      spacing between words has been regularized to one space.</p>  </normalization>  <normalization source="http://www.dict.sztaki.hu/webster">   <p>Spelling converted throughout to Modern American usage, based on Websters 9th      Collegiate dictionary.</p>  </normalization> </editorialDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element normalization
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   attribute method { "silent" | "markup" }?,
   ws_model.pLike+
}

Appendix A.134 <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
authorial
The note was written by the author, whether contemporaneously with the rest of the text or not.[Default]
editorial
The note was written by an editor or publisher.
temp
The note is intended for intra-WWP communication, particularly to flag an issue to be reslolved later; intent is to remove it after the issue is resolved (hopefully, but not always, prior to publication).
public
Indicates an editorial note (which may be in the <notesStmt>) supplied by the encoder or textbase editor, intended for public consumption.
internal
A note generated by WWP, not intended for public consumption; often used for notes to our future selves to avoid confusion or repeated work.
Member of
Contained by
May contain
ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="gloss"  resp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Schematron
<sch:rule context="wwp:text//wwp:note[not(@target)]"> <sch:report test="ancestor::wwp:hyperDiv | ancestor::wwp:div[@type='endnotes']">ERROR: <sch:value-of select="if (@xml:id) then concat('the note with id=', @xml:id ) else concat('note #',count( preceding::wwp:note))"/> does not have a @target, but should (because it is an endnote or is inside <hyperDiv>)</sch:report> </sch:rule>
Schematron
<sch:rule context="wwp:note[@target|@targetEnd]"> <sch:let name="ptr2me"  value="concat('#', @xml:id )"/> <sch:report test="tokenize( normalize-space( string-join( ( @target, @targetEnd ), ' ') ), ' ' ) = $ptr2me">ERROR: the note element with id=<sch:value-of select="@xml:id"/> refers to itself</sch:report> </sch:rule>
Schematron
<sch:rule context="wwp:note[ @type eq 'public']"> <sch:assert test="parent::wwp:notesStmt">public notes should be in the <gi>notesStmt</gi> in the TEI header.</sch:assert> </sch:rule>
Schematron
<sch:rule context="wwp:note[ @type = ('editorial','authorial') ]"> <sch:report test="parent::wwp:notesStmt">  <sch:value-of select="@type"/> notes should not be in the <gi>notesStmt</gi> in the TEI header.</sch:report> </sch:rule>
Schematron
<sch:rule context="wwp:note[ ( not(@type) or @type eq 'authorial' ) and @target ]"> <sch:report test=" (: open outer sequence of values :) ( (: take each separate pointer in my @target, generate an item that is that pointer with the '#' stripped off :) for $T in tokenize( @target )!substring-after( .,'#') return (: and, for each of those #-less targets (stored as $T), a) get the element that it refers to; b) take that element’s @corresp; c) tokenize that @corresp value string into separate pointers (As a side comment, there will generally be only 1, rarely 2, and we don’t have any 3+ as of 2023-03-17; d) strip the '#' off each of those pointers; e) compare each if those #-less pointers to the current <note> elment’s @xml:id. If any one of them is equal, then we return true; otherwise false :) tokenize( id( $T )/@corresp )!substring-after( .,'#') = @xml:id (: close outer sequence of values :) ) (: So we now have a sequence of xs:boolean values, one for each separate pointer in this <note> element’s @target, each of which is true iff at least one of the target’s @corresp values points back to the same <note>. :) (: Ask “is any one of these values false?” Iff so, then we have a problem, warn the user. :) = false()">One or more of the values of target of the note with ID <sch:value-of select="@xml:id"/> points to an element whose corresp does not point back</sch:report> <sch:assert test="count( tokenize( @target ) ) > 0">Empty @target of <note></sch:assert> </sch:rule>
Schematron
<sch:rule context="wwp:note"> <sch:report test="*/wwp:add and not( */text()[ normalize-space(.) ne '' ] )">  <sch:value-of select="if (@xml:id) then concat('the note with id=', @xml:id ) else concat('note #', count( preceding::wwp:note ) ) "/> should probably be an <gi>add</gi> with a <gi>note</gi> inside instead, as it seems to have no content other than an <gi>add</gi>. </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.noteContent"/>
</content>
    
Schema Declaration
element note
{
   ws_att.global.attributes,
   ws_att.anchoring.attributes,
   ws_att.cmc.attributes,
   ws_att.pointing.attributes,
   ws_att.typed.attribute.subtype,
   ws_att.written.attributes,
   attribute type
   {
      "authorial" | "editorial" | "temp" | "public" | "internal"
   }?,
   ws_macro.noteContent
}

Appendix A.135 <notes>

<notes> Container that occurs in <hyperDiv> and holds one or more <note> elements.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
derived-module-wwp-store: hyperDiv
May contain
core: note
Content model
<content>
 <elementRef key="note" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element notes { ws_att.global.attributes, ws_note+ }

Appendix A.136 <notesStmt>

<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
core: note
derived-module-wwp-store: advertisement
Note

Information of different kinds should not be grouped together into the same note.

Example
<notesStmt>  <note>Historical commentary provided by Mark Cohen</note>  <note>OCR scanning done at University of Toronto</note> </notesStmt>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.noteLike"/>
  <elementRef key="relatedItem"/>
 </alternate>
</content>
    
Schema Declaration
element notesStmt
{
   ws_att.global.attributes,
   ( ws_model.noteLike | relatedItem )+
}

Appendix A.137 <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typeindicates the type of numeric value.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
fraction
fraction, e.g. one half or three-quarters
percentage
a percentage
Note

If a different typology is desired, other values can be used for this attribute.

valuesupplies the value of the number in standard form.
StatusOptional
Datatypeteidata.numeric
Valuesa numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
Contained by
May contain
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The <num> element is intended for use in simple applications.

Example
<p>I reached <num type="cardinalvalue="21">twenty-one</num> on my <num type="ordinalvalue="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>  </num> cm per second.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element num
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" }?,
   attribute value { text }?,
   ws_macro.phraseSeq
}

Appendix A.138 <opener>

<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. [4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
core: lg list note
drama: castList
textstructure: body div group postscript
May contain
Example
<opener>  <dateline>Walden, this 29. of August 1592</dateline> </opener>
Example
<opener>  <dateline>   <name type="place">Great Marlborough Street</name>   <date>November 11, 1848</date>  </dateline>  <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="dateline"/>
  <elementRef key="epigraph"/>
  <elementRef key="salute"/>
  <elementRef key="signed"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element opener
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   (
      text
    | ws_model.gLike
    | ws_model.phrase
    | ws_argument
    | ws_byline
    | ws_dateline
    | ws_epigraph
    | ws_salute
    | ws_signed
    | ws_model.global
   )*
}

Appendix A.139 <orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.editLike.attributes,
   ws_att.personal.attributes,
   ws_att.typed.attributes,
   ws_macro.phraseSeq
}

Appendix A.140 <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Schematron
<sch:rule context="wwp:orig"> <sch:report test="ancestor::wwp:mw">An <gi>orig</gi> should not be inside an <gi>mw</gi> </sch:report> <sch:report test="ancestor::wwp:orig"  role="warning">Generally speaking, an <gi>orig</gi> should not be within an <gi>orig</gi> </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_macro.paraContent
}

Appendix A.141 <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:p"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.fragmentable.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.142 <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself.

The type attribute may be used to characterize the page beginning in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page beginning is word-breaking, or to note the source from which it derives.

ExamplePage numbers may vary in different editions of a text.
<p> ... <pb n="145ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
ExampleA page beginning may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>  <pb n="1facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb n="2facs="page2.png"/> <!-- similarly, for page 2 -->  <p> <!-- ... -->  </p> </body>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element pb
{
   ws_att.global.attributes,
   ws_att.breaking.attributes,
   ws_att.cmc.attributes,
   ws_att.edition.attributes,
   ws_att.spanning.attributes,
   ws_att.typed.attributes,
   empty
}

Appendix A.143 <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
properAdjective
regularized
titlePage
person-female
person
person-male
Member of
Contained by
May contain
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
SchematronWill not work with probatron; see description of "shyTests".
<sch:pattern> <sch:rule context="wwp:persName/@ref [/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef] | wwp:change/@who [/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef] | */@author [/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef] | */@resp [/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef]">  <sch:let name="path"   value="'https://www.wwp.neu.edu/wwo/texts/'"/>  <sch:let name="myElement" value="."/>  <sch:let name="gi" value="local-name(..)"/>  <sch:let name="att" value="local-name(.)"/>  <sch:let name="val"   value="normalize-space(.)"/>  <sch:let name="TOKs"   value="tokenize( normalize-space( $val ), ' ')"/>  <sch:let name="REFs"   value="for $t in $TOKs return if ( matches( $t, '\i\c*:\i\c*') ) then $t else '∅'"/>  <sch:let name="SHRTs"   value="for $t in $TOKs return if ( matches( $t, '#\i\c*') ) then $t else '∅'"/>  <sch:let name="NOTs"   value="$TOKs[ not( matches( ., '(#|\i\c*:)\i\c*') ) ]"/>  <sch:let name="TARs"   value="for $s in $SHRTs return if ( $s eq '∅') then $s else substring-after( $s,'#')"/>  <sch:let name="PREFs"   value="for $r in $REFs return if ( $r eq '∅') then $r else substring-before( $r,':')"/>  <sch:let name="KEYs"   value="for $r in $REFs return if ( $r eq '∅') then $r else substring-after( $r,':')"/>  <sch:let name="URLs"   value="for $p in $PREFs return concat( $path, substring-before( /wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef//wwp:prefixDef[ @ident eq $p ]/@replacementPattern, '#' ) )"/>  <sch:let name="PERSONs_via_prefix"   value="for $k in $KEYs return if ( count( index-of( $KEYs, $k ) ) eq 1 ) then if ( doc-available( $URLs[ index-of( $KEYs, $k )] ) ) then if ( document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] ) then document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] else $myElement else $myElement else $myElement"/>  <sch:let name="PERSONs_via_short"   value="for $t in $TARs return //*[ @xml:id eq $t ]"/>  <sch:let name="nodes_via_prefix"   value="$PERSONs_via_prefix[ not( . eq '' or . eq '∅' or . is $myElement ) ]"/>  <sch:let name="nodes_via_short"   value="$PERSONs_via_short[self::*]"/>  <sch:let name="num_not_via_prefix"   value="count( $nodes_via_prefix ) - count( $nodes_via_prefix[ self::TEI:person | self::TEI:personGrp | self::TEI:alt ])"/>  <sch:let name="num_not_via_short"   value="count( $nodes_via_short ) - count( $nodes_via_short [ self::wwp:person | self::wwp:personGrp | self::wwp:alt ])"/>  <sch:let name="node_names"   value="string-join( for $p in ( $nodes_via_prefix, $nodes_via_short ) return concat(' <', name($p), '>'), ', ')"/>  <sch:report test="count( $NOTs ) eq count( $TOKs )">No usable pointers in @<sch:value-of select="$att"/> of <<sch:value-of select="$gi"/>></sch:report>  <sch:report test="count( $NOTs ) gt 0 and count( $NOTs ) lt count( $TOKs )">At least one of the pointers in @<sch:value-of select="$att"/> of <<sch:value-of select="$gi"/>> is not processable as a pointer (problemetic value(s): "<sch:value-of select="$NOTs"/>").</sch:report>  <sch:report test="false()">   <sch:value-of select="concat('debug: ',count($TOKs), ' TOKs=', string-join( $TOKs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($REFs), ' REFs=', string-join( $REFs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($SHRTs),' SHRTs=',string-join( $SHRTs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($NOTs), ' NOTs=', string-join( $NOTs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($PREFs),' PREFs=',string-join( $PREFs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($URLs), ' URLs=', string-join( $URLs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($KEYs), ' KEYs=', string-join( $KEYs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($TARs), ' TARs=', string-join( $TARs,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($PERSONs_via_prefix), ' PERSONs_via_prefix; ')"/>   <sch:value-of select="concat('debug: ',count($PERSONs_via_short), ' PERSONs_via_short=', string-join( $PERSONs_via_short,'^'), '; ')"/>   <sch:value-of select="concat('debug: ',count($nodes_via_prefix), ' nodes_via_prefix; ')"/>   <sch:value-of select="concat('debug: ',count($nodes_via_short), ' nodes_via_short; ')"/>   <sch:value-of select="concat('debug: num_not_via_prefix=', $num_not_via_prefix, '; ')"/>   <sch:value-of select="concat('debug: num_not_via_short=', $num_not_via_short, '; ')"/>   <sch:value-of select="concat('debug: ',count($NOTs), ' NOTs=', string-join( $NOTs,'^'), '; ')"/>   <sch:value-of select="'debug: counts of nodes ='"/>   <sch:value-of select="for $n in ( $nodes_via_prefix, $nodes_via_short ) return count( $n )"/>   <sch:value-of select="'; '"/>  </sch:report>  <sch:report test="count( $nodes_via_prefix ) + count( $nodes_via_short ) eq 0">Each pointer in the <sch:value-of select="$att"/> attribute of <<sch:value-of select="$gi"/>> should point to a <person> (or <personGrp> or an <alt>), but the pointer(s) in this one ("<sch:value-of select="$val"/>") point to nothing</sch:report>  <sch:report test="$num_not_via_prefix + $num_not_via_short gt 0"> Each pointer in the <sch:value-of select="$att"/> attribute of <<sch:value-of select="$gi"/>>    should point to a <person> (or <personGrp> or an <alt>), but at least one of the pointers    in this one ("<sch:value-of select="$val"/>") does not.  <sch:value-of select="if ( $nodes_via_prefix | $nodes_via_short ) then concat(' Those that point to elements point to:', $node_names, ' (not necessarily in that order).') else ''"/>  </sch:report> </sch:rule> </sch:pattern>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.editLike.attributes,
   ws_att.personal.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "properAdjective"
    | "regularized"
    | "titlePage"
    | "person-female"
    | "person"
    | "person-male"
   }?,
   ws_macro.phraseSeq
}

Appendix A.144 <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
properAdjective
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Schematron
<sch:pattern> <sch:rule context="wwp:placeName[@ref][/wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef]">  <sch:let name="path"   value="'https://www.wwp-test.neu.edu/wwo/texts/'"/>  <sch:let name="val"   value="normalize-space( @ref )"/>  <sch:let name="gi" value="local-name(.)"/>  <sch:let name="REFs"   value="tokenize( $val, ' ')"/>  <sch:let name="PREFs"   value="for $r in $REFs return substring-before( $r,':')"/>  <sch:let name="URLs"   value="for $p in $PREFs return concat( $path, substring-before( /wwp:TEI/wwp:teiHeader/wwp:encodingDesc/wwp:listPrefixDef//wwp:prefixDef[ @ident eq $p ]/@replacementPattern, '#' ) )"/>  <sch:let name="KEYs"   value="for $r in $REFs return substring-after( $r,':')"/>  <sch:let name="PLACEs"   value="for $k in $KEYs return if ( doc-available( $URLs[ index-of( $KEYs, $k )] ) ) then if ( document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] ) then document( $URLs[ index-of( $KEYs, $k )] )//TEI:*[ @xml:id eq $k ] else . else ."/>  <sch:report test="count( $REFs ) eq 0">Empty @ref of <placeName></sch:report>  <sch:report test="count( $PLACEs[ not( self::TEI:place ) ] ) gt 0">Each pointer in the @ref attribute of <placeName> should point to a <place>, but the pointers in this one ("<sch:value-of select="$val"/>") point to: <sch:value-of select="if ( not( $PLACEs ) ) then 'nowhere' else for $p in $PLACEs return if ( $p is . ) then ' nothing' else concat(' <', name($p), '>')"/>.</sch:report> </sch:rule> </sch:pattern>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.editLike.attributes,
   ws_att.personal.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "properAdjective" }?,
   ws_macro.phraseSeq
}

Appendix A.145 <postscript>

<postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
core: lg list
figures: table
textstructure: back body div front group
May contain
Example
<div type="letter">  <opener>   <dateline>    <placeName>Rimaone</placeName>    <date when="2006-11-21">21 Nov 06</date>   </dateline>   <salute>Dear Susan,</salute>  </opener>  <p>Thank you very much for the assistance splitting those    logs. I'm sorry about the misunderstanding as to the size of    the task. I really was not asking for help, only to borrow the    axe. Hope you had fun in any case.</p>  <closer>   <salute>Sincerely yours,</salute>   <signed>Seymour</signed>  </closer>  <postscript>   <label>P.S.</label>   <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p>  </postscript> </div>
Content model
<content>
 <macroRef key="macro.noteContent"/>
</content>
    
Schema Declaration
element postscript
{
   ws_att.declaring.attributes,
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ws_macro.noteContent
}

Appendix A.146 <prefixDef>

<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatypeteidata.prefix
Note

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

Contained by
May contain
core: p
linking: ab
Note

The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<prefixDef ident="ref"  matchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element prefixDef
{
   ws_att.global.attributes,
   ws_att.patternReplacement.attributes,
   attribute ident { text },
   ws_model.pLike*
}

Appendix A.147 <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Member of
Contained by
header: teiHeader
May contain
derived-module-wwp-store: include
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <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="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { ws_att.global.attributes, ws_model.profileDescPart* }

Appendix A.148 <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
textstructure: body
May contain
core: p
linking: ab
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   ws_model.pLike+
}

Appendix A.149 <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
correction
div
error
pageNum
pageRange
Member of
Contained by
May containEmpty element
Note

The target and cRef attributes are mutually exclusive.

Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.internetMedia.attributes,
   ws_att.pointing.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "correction" | "div" | "error" | "pageNum" | "pageRange" }?,
   empty
}

Appendix A.150 <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
textstructure: docImprint
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <macroRef key="macro.phraseSeq"/>
  <elementRef key="country"/>
  <elementRef key="region"/>
  <elementRef key="settlement"/>
 </alternate>
</content>
    
Schema Declaration
element pubPlace
{
   ws_att.global.attributes,
   ws_att.naming.attributes,
   ( ws_macro.phraseSeq | ws_country | ws_region | ws_settlement )*
}

Appendix A.151 <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
derived-module-wwp-store: include
linking: ab
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
Content model
<content>
 <alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   ws_att.global.attributes,
   (
      (
         (
            ws_model.publicationStmtPart.agency,
            ws_model.publicationStmtPart.detail*
         )+
      )
    | ws_model.pLike+
   )
}

Appendix A.152 <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
textstructure: docImprint
May contain
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element publisher
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_macro.phraseSeq
}

Appendix A.153 <quotation>

<quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no quotation marks have been retained
some
some quotation marks have been retained
all
all quotation marks have been retained
Member of
Contained by
May contain
core: p
linking: ab
Example
<quotation marks="none">  <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the  <gi>q</gi> element is used to specify what kinds of quotation mark was used, according    to the following list: <list type="gloss">    <label>dq</label>    <item>double quotes, open and close</item>    <label>sq</label>    <item>single quotes, open and close</item>    <label>dash</label>    <item>long dash open, no close</item>    <label>dg</label>    <item>double guillemets, open and close</item>   </list>  </p> </quotation>
Example
<quotation marks="all">  <p>All quotation marks are retained in the text and are represented by appropriate Unicode    characters.</p> </quotation>
Schematron
<sch:rule context="tei:quotation"> <sch:report test="not( @marks ) and not( tei:p )"> On <sch:name/>, either the @marks attribute should be used, or a paragraph of description provided </sch:report> </sch:rule>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element quotation
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   attribute marks { "none" | "some" | "all" }?,
   ws_model.pLike*
}

Appendix A.154 <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
adaptation
the quoted material is changed from its original context in a deliberate way, possibly to fit into the text
parody
the quotation is significantly different from the original text, and appears to be a deliberate parody
remix
the quoted material has been re-ordered or otherwise significantly modified from the original in a deliberate fashion (other than a paraphrase or parody)
undetermined
as of yet undeterminted
Note

Paraphrases may have changes to the quotation that are deliberate or necessary because of how it fits into the text.

cit(prose citation reference) points to (one or more) bibliographic citation(s) for this quotation as they appear in the source
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

At the current time we do not use this attribute; we may, however, use it in the future.

Member of
Contained by
May contain
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Schematron
<sch:pattern> <sch:rule context="wwp:quote[ starts-with( @cit,'#' ) ]">  <sch:assert test="//wwp:bibl[ @xml:id eq substring-after( current()/@cit,'#' ) ]">cit= attribute of <<sch:name/>> does not point to a <bibl>.</sch:assert> </sch:rule> <sch:rule context="wwp:quote[ contains(@cit,'#') ]">  <sch:assert test="document( substring-before( @cit,'#') )//wwp:bibl[ @xml:id = substring-after( current()/@cit,'#') ]">cit= attribute of <<sch:name/>> does not point to a <bibl>.</sch:assert> </sch:rule> <sch:rule context="wwp:quote[ @cit ]">  <sch:report test="not( contains( @cit,'#') )">cit= attribute of <<sch:name/>> must point to particular <bibl> element via its xml:id=</sch:report> </sch:rule> </sch:pattern>
Content model
<content>
 <classRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.msExcerpt.attributes,
   ws_att.notated.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "adaptation" | "parody" | "remix" | "undetermined" }?,
   attribute cit { list { + } }?,
   ws_macro.specialPara
}

Appendix A.155 <redo>

<redo> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [12.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr
Attributes
targetpoints to one or more elements representing the interventions which are being reasserted.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containEmpty element
Example
<line>  <redo hand="#g_ttarget="#redo-1"   cause="fix"/>  <mod xml:id="redo-1rend="strikethrough"   spanTo="#anchor-1hand="#g_bl"/>Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken </line> <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/> </line>
This encoding represents the following sequence of events:
  • "Ihr hagren, triſten, krummgezog nenener Nacken/ Wenn ihr nur piepſet iſt die Welt ſchon matt." is written
  • the redundant letters "nen" in "nenener" are deleted
  • the whole passage is deleted by hand g_bl using strikethrough
  • the deletion is reasserted by another hand (identified here as g_t)
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element redo
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.spanning.attributes,
   ws_att.transcriptional.attributes,
   attribute target { list { + } }?,
   empty
}

Appendix A.156 <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
correction
div
error
pageNum
pageRange
goTo
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.internetMedia.attributes,
   ws_att.pointing.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "correction" | "div" | "error" | "pageNum" | "pageRange" | "goTo"
   }?,
   ws_macro.paraContent
}

Appendix A.157 <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.editLike.attributes,
   ws_att.typed.attributes,
   ws_macro.paraContent
}

Appendix A.158 <regMe>

<regMe> (regularize me) Canonical abbreviation, citation, or reference flagged for automated regularization.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
May contain
Note

Used as a temporary replacement for a <choice> element with the content of this <regMe> as the content of a child <reg>, with an automatically created sibling <orig>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element regMe
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_macro.phraseSeq
}

Appendix A.159 <region>

<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. [14.2.3. Place Names]
Modulenamesdates
Contained by
core: pubPlace
May contain
Note

At the WWP, <region> (and <country> and <settlement>) are only used as a child of <pubPlace>.

Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element region { ws_macro.phraseSeq }

Appendix A.160 <rendition>

<rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
schemeidentifies the language used to describe the rendition.
Derived fromatt.styleDef
StatusOptional
Datatypeteidata.enumerated
Legal values are:
css
xslfo
free
other
wwp
(Women Writers Project rendition ladder) indicates that the content of the element uses the WWP rendition ladders notation; indicates that the selector attribute uses CSS plus three special pseudo-classes, particularly for use with <mw>[Default]
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatypestring
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
Note

Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

While rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

Contained by
header: tagsDecl
May contain
gaiji: g
character data
Note

Note that vanilla TEI does not permit the <g> element in the content of <rendition>, but we do here at the WWP, as we have a lot of non-Unicode characters in pre() or post().

Note that the language used in selector is not CSS, but rather is wwp. The difference is that the WWP language has three additional psuedo-classes:

romulus
the first (or elder) of a pair of ‘twin’ elements, i.e. elements of the same element type that occur with nothing between them except perhaps a whitespace-only text node.
remus
the second (or younger) of a pair of ‘twin’ elements, or any other than the first of a sequence of twin elements (i.e. a series of two or more elements of the same element type that occur with nothing between any two except perhaps whitespace-only text nodes).
twinLess
an element that does not have a closest sibling of the same element type

At the moment we only use these pseudo-classes with the selector for the element type <mw>.

Example
<tagsDecl>  <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>  <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>  <rendition xml:id="r-largescheme="css">font-size: large;</rendition>  <rendition xml:id="initcaps"   scope="first-letterscheme="css">font-size: xx-large</rendition> </tagsDecl>
Schematron
<sch:rule context="wwp:rendition"> <sch:let name="myIDref"  value="concat('#', normalize-space( @xml:id ) )"/> <sch:assert test="@selector or ( @xml:id and /wwp:TEI/wwp:text//@rendition[ $myIDref = tokenize( normalize-space( . ),' ') ] ) ">default <gi>rendition</gi> #<sch:value-of select="(@xml:id, count( preceding::wwp:rendition )+1 )[1]"/> is not the default for anything (no <att>selector</att> and not pointed to by any <att>rendition</att>)</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element rendition
{
   ws_att.global.attributes,
   ws_att.styleDef.attribute.schemeVersion,
   attribute scheme { "css" | "xslfo" | "free" | "other" | "wwp" }?,
   attribute selector { text }?,
   ws_macro.xtext
}

Appendix A.161 <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
author
See corresponding @type value on docAuthor.
author-secondary
a person or organization credited as an author, but given lower precedence than the main author(s)
bookseller
See corresponding @type value on docAuthor.
printer
See corresponding @type value on docAuthor.
translator
See corresponding @type value on docAuthor.
Contained by
core: respStmt
May contain
Note

The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element resp
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.datable.attributes,
   attribute type
   {
      "author" | "author-secondary" | "bookseller" | "printer" | "translator"
   }?,
   ws_macro.phraseSeq.limited
}

Appendix A.162 <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
core: name resp
namesdates: orgName persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <classRef key="model.nameLike.agent"/>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="resp" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.nameLike.agent"
    minOccurs="1" maxOccurs="unbounded"/>
   <elementRef key="resp"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element respStmt
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_model.nameLike.agent,
   ( ws_resp+ | ( ws_model.nameLike.agent+, ws_resp ) )
}

Appendix A.163 <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
core: list
header: change
Note

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="listChange"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   ws_att.global.attributes,
   ws_att.docStatus.attributes,
   ( ws_list+ | listChange+ | ws_change+ )
}

Appendix A.164 <role>

<role> (role) contains the name of a dramatic role, as given in a cast list. [7.1.4. Cast Lists]
Moduledrama
Attributes
gender
StatusOptional
Datatypewwpdata.sex
ValuesIf not specified, the value should be considered unknown unless there is a gender on an ancestor, in which case the closest such value is used. Exception: when that closest ancestor gender is mixed, the value here is still considered unknown.
Member of
Contained by
drama: castItem
May contain
Note

It is important to assign a meaningful ID attribute to the <role> element, since this ID is referred to by who attributes on many other elements.

Example
<role xml:id="jt">Joan Trash</role> <roleDesc>A Ginger-bread-woman</roleDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element role
{
   ws_att.global.attributes,
   attribute gender { text }?,
   ws_macro.phraseSeq
}

Appendix A.165 <roleDesc>

<roleDesc> (role description) describes a character's role in a drama. [7.1.4. Cast Lists]
Moduledrama
Attributes
Member of
Contained by
May contain
Example
<roleDesc>gentlemen of leisure</roleDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element roleDesc { ws_att.global.attributes, ws_macro.phraseSeq }

Appendix A.166 <row>

<row> (row) contains one row of a table. [15.1.1. TEI Tables]
Modulefigures
Attributes
Contained by
figures: table
May contain
figures: cell
Example
<row role="data">  <cell role="label">Classics</cell>  <cell>Idle listless and unimproving</cell> </row>
Content model
<content>
 <elementRef key="cell" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element row
{
   ws_att.global.attributes,
   ws_att.tableDecoration.attributes,
   ws_cell+
}

Appendix A.167 <rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
Attributes
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
collectivity
place
properAdjective
source
title
ufo
(unspecified feature used for organization) Used for encoding a string that refers the reader to another portion of the document, typically by quoting its <head>; an internal cross reference.
verb
Member of
Contained by
May contain
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.naming.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "collectivity"
    | "place"
    | "properAdjective"
    | "source"
    | "title"
    | "ufo"
    | "verb"
   },
   ws_macro.phraseSeq
}

Appendix A.168 <said>

<said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
Modulecore
Attributes
aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
StatusOptional
Datatypeteidata.xTruthValue
<p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;    I believe she would not accept him.</said> Celia felt that this was a pity. <!-- ... --> </p>
Note

The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
StatusOptional
Datatypeteidata.xTruthValue
Defaulttrue
<!-- in the header --><editorialDecl>  <quotation marks="none"/> </editorialDecl> <!-- ... --> <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>. The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>, but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said> </p>
Note

The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

Member of
Contained by
May contain
Example
<!-- in the header --><editorialDecl>  <quotation marks="all"/> </editorialDecl> <!-- ... --> <p>  <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and    gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill    his wine, and blunt his sword, and say his name begins with X, and in the end the Duke    will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O      rider of the sun!'</said>"</said> </p>
Example
<p>  <said aloud="truerend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear. <said aloud="truerend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see.    Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove    yourself, now that's interesting. … So where shall I put you?</said> </p> <p>Harry gripped the edges of the stool and thought, <said aloud="falserend="italic">Not    Slytherin, not Slytherin</said>.</p>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element said
{
   ws_att.global.attributes,
   ws_att.ascribed.directed.attributes,
   ws_att.cmc.attributes,
   attribute aloud { text }?,
   attribute direct { text }?,
   ws_macro.specialPara
}

Appendix A.169 <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. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Contained by
textstructure: closer opener
May contain
Example
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element salute
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.170 <samplingDecl>

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   ws_model.pLike+
}

Appendix A.171 <seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
Modulelinking
Attributes
Member of
Contained by
May contain
Note

The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

Example
<seg>When are you leaving?</seg> <seg>Tomorrow.</seg>
Example
<s>  <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield. </s>
Example
<seg type="preamble">  <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>  <seg>Sinfiotli was the eldest of his sons ...</seg>  <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element seg
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.notated.attributes,
   ws_att.segLike.attributes,
   ws_att.typed.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.172 <series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Member of
Contained by
derived-module-wwp-store: advertisement
May contain
Example
<series xml:lang="de">  <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>  <respStmt>   <resp>Herausgegeben von</resp>   <name type="person">Manfred Thaller</name>   <name type="org">Max-Planck-Institut für Geschichte</name>  </respStmt>  <title level="s">Serie A: Historische Quellenkunden</title>  <biblScope>Band 11</biblScope> </series>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   ws_att.global.attributes,
   (
      text
    | ws_model.gLike
    | ws_title
    | ws_model.ptrLike
    | ws_editor
    | ws_respStmt
    | ws_biblScope
    | ws_idno
    | textLang
    | ws_model.global
    | ws_availability
   )*
}

Appendix A.173 <set>

<set> (setting) contains a description of the setting, time, locale, appearance, etc., of the action of a play, typically found in the front matter of a printed performance text (not a stage direction). [7.1. Front and Back Matter ]
Moduledrama
Attributes
Member of
Contained by
textstructure: back front
May contain
Note

Contains paragraphs or phrase level tags.

This element should not be used outside the front or back matter; for similar contextual descriptions within the body of the text, use the <stage> element.

Example
<set>  <p>The action takes place on February 7th between the hours of noon and six in the    afternoon, close to the Trenartha Tin Plate Works, on the borders of England and Wales,    where a strike has been in progress throughout the winter.</p> </set>
Example
<set>  <head>SCENE</head>  <p>A Sub-Post Office on a late autumn evening</p> </set>
Example
<front> <!-- <titlePage>, <div type="Dedication">, etc. -->  <set>   <list type="gloss">    <label>TIME</label>    <item>1907</item>    <label>PLACE</label>    <item>East Coast village in England</item>   </list>  </set> </front>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element set
{
   ws_att.global.attributes,
   (
      ( ws_model.headLike | ws_model.global )*,
      ( ( ws_model.common, ws_model.global* )* )
   )
}

Appendix A.174 <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [14.2.3. Place Names]
Modulenamesdates
Contained by
core: pubPlace
May contain
Note

At the WWP, <settlement> (and <country> and <region>) are only used as a child of <pubPlace>.

Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement { ws_macro.phraseSeq }

Appendix A.175 <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore
Attributes
type
StatusOptional
Legal values are:
metawork
used (on an empty <sic> w/o a <choice> parent) to indicate a missing piece of metawork
seq
(sequencing) the error represents an error in the sequencing of some countable feature, e.g. pages or list items.
Member of
Contained by
May contain
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.
Schematron
<sch:rule context="wwp:sic[@type eq 'metawork']"> <sch:report test="parent::wwp:choice or (preceding-sibling::*[1]|following-sibling::*[1])[self::wwp:corr]">At the WWP we do not correct metawork errors</sch:report> </sch:rule>
Schematron
<sch:rule context="wwp:sic[@type eq 'metawork']"> <sch:report test=".//* | .//text()[ normalize-space(.) != '']">Metawork error flags should not have content</sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   attribute type { "metawork" | "seq" }?,
   ws_macro.paraContent
}

Appendix A.176 <signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Contained by
textstructure: closer opener
May contain
Example
<signed>Thine to command <name>Humph. Moseley</name> </signed>
Example
<closer>  <signed>Sign'd and Seal'd,  <list>    <item>John Bull,</item>    <item>Nic. Frog.</item>   </list>  </signed> </closer>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element signed
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   ws_macro.paraContent
}

Appendix A.177 <soCalled>

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call <soCalled>nuts</soCalled> to Scrooge.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element soCalled
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_macro.phraseSeq
}

Appendix A.178 <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
figures: table
linking: ab
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   (
      ws_model.pLike+
    | ( ws_model.biblLike | ws_model.sourceDescPart | ws_model.listLike )+
   )
}

Appendix A.179 <sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
Modulecore
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
Derived fromatt.ascribed
StatusRequired
Schematron
<sch:rule context="wwp:sp[@who]"> <sch:let name="whos"  value="tokenize( normalize-space( @who ), ' ')"/> <sch:let name="WHOs"  value="for $w in $whos return substring-after( $w,'#')"/> <sch:let name="points2something"  value="for $w in $WHOs return exists( id( $w ) )"/> <sch:let name="pointed2by_who"  value="for $w in $WHOs return id($w)"/> <sch:report test="$points2something = false()">One or more of the pointers in this @who does not point to a local element.</sch:report> <sch:assert test="count( $pointed2by_who ) eq count( $pointed2by_who[self::wwp:role|self::wwp:actor] )">The @who of <sp> is supposed to point a <role> or an <actor>, but this one points to: <sch:value-of select="for $e in $pointed2by_who return concat('<', $e/name(.), '> ')"/>.</sch:assert> </sch:rule>
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
derived-module-wwp-store: advertisement docSale
figures: cell
transcr: metamark
May contain
Note

The who attribute on this element may be used either in addition to the <speaker> element or as an alternative.

Example
<sp>  <speaker>The reverend Doctor Opimian</speaker>  <p>I do not think I have named a single unpresentable fish.</p> </sp> <sp>  <speaker>Mr Gryll</speaker>  <p>Bream, Doctor: there is not much to be said for bream.</p> </sp> <sp>  <speaker>The Reverend Doctor Opimian</speaker>  <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>  <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I    will forbear [...]</p> </sp>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="speaker"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="lg"/>
    <classRef key="model.lLike"/>
    <classRef key="model.pLike"/>
    <classRef key="model.listLike"/>
    <classRef key="model.stageLike"/>
    <classRef key="model.attributable"/>
   </alternate>
   <alternate minOccurs="1" maxOccurs="1">
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="q"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element sp
{
   ws_att.global.attributes,
   ws_att.ascribed.directed.attribute.toWhom,
   ws_att.written.attributes,
   attribute who { list { + } },
   (
      ws_model.global*,
      ( ( ws_speaker, ws_model.global* )? ),
      (
         (
            (
               ws_lg
             | ws_model.lLike
             | ws_model.pLike
             | ws_model.listLike
             | ws_model.stageLike
             | ws_model.attributable
            ),
            ( ws_model.global* | q )
         )+
      )
   )
}

Appendix A.180 <spGrp>

<spGrp> (speech group) contains a group of speeches or songs in a performance text presented in a source as constituting a single unit or ‘number’. [7.2.3. Grouped Speeches]
Moduledrama
Attributes
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
couplet
indeterminate
octet
quatrain
quintet
refrain
septet
sestet
simultaneous
stanza
tercet
Note

This list is not neccesarily complete. If you find something that you do not think fits into any of these catagories, use indeterminate and bring it up at an encoding meeting. —Syd, 2018-08-13

Member of
Contained by
derived-module-wwp-store: advertisement docSale
drama: castList set
figures: cell
transcr: metamark
May contain
Example
<sp>  <speaker>FRAULEIN SCHNEIDER:</speaker>  <p> Herr Schultz! Can I believe what I see? <stage>(HERR SCHULTZ nods      proudly)</stage> But this is — too much to accept. So rare — so costly —    so luxurious. </p> </sp> <stage>(She sings)</stage> <spGrp n="4">  <sp>   <l>If you bought me diamonds, If you bought me pearls,</l>   <l>If you bought me roses like some other gents</l>   <l>Might bring to other girls,</l>   <l>It couldn't please me more</l>   <l>Than the gift I see -</l>   <stage>(She takes a large pineapple out of the bag)</stage>   <l>A pineapple for me!</l>  </sp>  <sp>   <speaker>SCHULTZ:</speaker>   <stage>(Singing) </stage>   <l>If, in your emotion, </l>   <l>You began to sway, </l>   <l>Went to get some air, </l>   <l>Or grabbed a chair </l>   <l>To keep from fainting dead away, </l>   <l>It couldn't please me more </l>   <l>Than to see you cling </l>   <l>To the pineapple I bring.</l>  </sp>  <sp>   <speaker>BOTH:</speaker>   <l>Ah, ah, ah, ah, ah, ah, ah, ah</l>  </sp> <!-- ... -->  <stage>(They dance)</stage> </spGrp> <sp>  <speaker>FRAULEIN SCHNEIDER: </speaker>  <p>But you must not bring me    any more pineapples! Do you hear? It is not proper. It is a gift a    young man would present to his lady love. It makes me blush!  </p> </sp>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <elementRef key="sp"/>
   <classRef key="model.stageLike"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element spGrp
{
   ws_att.global.attributes,
   ws_att.ascribed.directed.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "couplet"
    | "indeterminate"
    | "octet"
    | "quatrain"
    | "quintet"
    | "refrain"
    | "septet"
    | "sestet"
    | "simultaneous"
    | "stanza"
    | "tercet"
   },
   ( ws_model.headLike*, ( ws_model.global | ws_sp | ws_model.stageLike )+ )
}

Appendix A.181 <space>

<space> (space) indicates the location of a significant space in the text. [12.4.1. Space]
Moduletranscr
Attributes
resp(responsible party) (responsible party) indicates the individual responsible for identifying and measuring the space.
Derived fromatt.global.responsibility
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
dim(dimension) indicates whether the space is horizontal or vertical.
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
horizontal
the space is horizontal.
vertical
the space is vertical.
Note

For irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.

Member of
Contained by
May contain
core: desc
Note

This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

Example
By god if wommen had writen storyes As <space quantity="7unit="minims"/> han within her oratoryes
Example
στρατηλάτ<space quantity="1unit="chars"/>ου
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element space
{
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.xmlid,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmllang,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.rend,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.source.attribute.source,
   ws_att.dimensions.attributes,
   ws_att.typed.attributes,
   attribute resp { list { + } }?,
   attribute dim { "horizontal" | "vertical" }?,
   ( ws_model.descLike | ws_model.certLike )*
}

Appendix A.182 <speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
Modulecore
Attributes
Contained by
core: sp
May contain
Note

This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an <sp> element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used.

Example
<sp who="#ni #rsa">  <speaker>Nancy and Robert</speaker>  <stage type="delivery">(speaking simultaneously)</stage>  <p>The future? ...</p> </sp> <list type="speakers">  <item xml:id="ni"/>  <item xml:id="rsa"/> </list>
Schematron
<sch:rule context="wwp:speaker"> <sch:report test="wwp:persName"  role="warning">We do not normally put <gi>persName</gi> inside of a <gi>speaker</gi> </sch:report> <sch:report test="wwp:choice/wwp:abbr|wwp:abbr|wwp:expan"  role="warning">We do not typically record or normalize abbreviations (or expansions) inside of a <gi>speaker</gi> </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element speaker
{
   ws_att.global.attributes,
   ws_att.written.attributes,
   ws_macro.phraseSeq
}

Appendix A.183 <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
derived-module-wwp-store: advertisement
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.

Example
<sponsor>Association for Computers and the Humanities</sponsor> <sponsor>Association for Computational Linguistics</sponsor> <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element sponsor
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.datable.attributes,
   ws_macro.phraseSeq.limited
}

Appendix A.184 <stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions]
Modulecore
Attributes
typeindicates the type of stage direction.
StatusRequired
Datatype1–5 occurrences of teidata.enumerated separated by whitespace
Legal values are:
business
describes stage business—that is, some activity taking place while the lines are being spoken (for example, “While toying with her fan” or “Rocks fall from above”)
delivery
describes the delivery of a line, either to whom or in what manner it is spoken (for example, “Sotto voce”, “Aside”, “To Acrasia”); this should be distinguished from stage business, which describes accompanying action rather than the speech itself
entrance
describes an entrance to the stage (for instance, “Enter, a Clown”)
exit
describes an exit from the stage (for example, “Exits”, “Exeunt omnes”)
location
describes the location from which a line is delivered (such as “From the couch”, “At the door”, or “Seated at the table”); this should not be confused with setting, which describes aspects of the entire scene rather than the position of a character for a particular line
modifier
describes a character's appearance or some detail of that character (for example, “Disguised as a juggler”, “Wearing a fright wig”, “Laden with tin pots”)
novelistic
describes the state of mind or motivations of a character, as if from an omniscient narrator's point of view (for example, “Fed up with the situation, and becoming impatient”, “Wondering what she means”, “Privately contemplating escape”)
present
used in cases where a stage direction gives the names of characters present on the stage without offering any further information on their appearance or actions (for example, “Alice and Amelia”)
prop
describes props that are onstage or indicates the presence of props (for example “the shield of Minerva”); this value should be used only when props are significant in the text
remains
indcates characters who remain on the stage when others exit (for example “manet Norfolk”)
setting
indicates a setting for the dramatic scene, possibly involving some details of stage layout, lighting, time, place, or occasion (for instance, “A ballroom lit with candles, soft music playing” or “Venice in the seventeenth century, the sky bright with the early light of a summer morning”)
Member of
Contained by
May contain
Note

The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

Example
<stage type="setting">A curtain being drawn.</stage> <stage type="setting">Music</stage> <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage> <!-- Middleton : Yorkshire Tragedy --> <stage type="exit">Exit pursued by a bear.</stage> <stage type="business">He quickly takes the stone out.</stage> <stage type="delivery">To Lussurioso.</stage> <stage type="novelistic">Having had enough, and embarrassed for the family.</stage> <!-- Lorraine Hansbury : a raisin in in the sun --> <stage type="modifier">Disguised as Ansaldo.</stage> <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage> <!-- Middleton: The Widow --> <stage type="location">At a window.</stage> <stage rend="inlinetype="delivery">Aside.</stage>
Example
<l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when    straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on    two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the  <hi>Prologue</hi> was spoken, which being ended, they descended in    order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element stage
{
   ws_att.global.attributes,
   ws_att.ascribed.directed.attributes,
   ws_att.cmc.attributes,
   ws_att.written.attributes,
   attribute type
   {
      list
      {
         (
            "business"
          | "delivery"
          | "entrance"
          | "exit"
          | "location"
          | "modifier"
          | "novelistic"
          | "present"
          | "prop"
          | "remains"
          | "setting"
         ),
         (
            "business"
          | "delivery"
          | "entrance"
          | "exit"
          | "location"
          | "modifier"
          | "novelistic"
          | "present"
          | "prop"
          | "remains"
          | "setting"
         )?,
         (
            "business"
          | "delivery"
          | "entrance"
          | "exit"
          | "location"
          | "modifier"
          | "novelistic"
          | "present"
          | "prop"
          | "remains"
          | "setting"
         )?,
         (
            "business"
          | "delivery"
          | "entrance"
          | "exit"
          | "location"
          | "modifier"
          | "novelistic"
          | "present"
          | "prop"
          | "remains"
          | "setting"
         )?,
         (
            "business"
          | "delivery"
          | "entrance"
          | "exit"
          | "location"
          | "modifier"
          | "novelistic"
          | "present"
          | "prop"
          | "remains"
          | "setting"
         )?
      }
   },
   ws_macro.specialPara
}

Appendix A.185 <subst>

<subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [12.3.1.5. Substitutions]
Moduletranscr
Attributes
Member of
Contained by
May contain
linking: anchor
transcr: mw surplus
Example
... are all included. <del hand="#RG">It is</del> <subst>  <add>T</add>  <del>t</del> </subst>he expressed
Example
that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>  <del>very</del>  <lb/>  <add>principally</add> </subst> remembered in her Will.
Example
<ab>τ<subst>   <add place="above">ῶν</add>   <del>α</del>  </subst> συνκυρόντ<subst>   <add place="above">ων</add>   <del>α</del>  </subst> ἐργαστηρί<subst>   <add place="above">ων</add>   <del>α</del>  </subst> </ab>
Example
<subst>  <del>   <gap reason="illegiblequantity="5"    unit="character"/>  </del>  <add>apple</add> </subst>
Schematron
<sch:rule context="tei:subst"> <sch:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">  <sch:name/> must have at least one child add and at least one child del or surplus</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <elementRef key="add"/>
  <elementRef key="surplus"/>
  <elementRef key="del"/>
  <classRef key="model.milestoneLike"/>
 </alternate>
</content>
    
Schema Declaration
element subst
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.transcriptional.attributes,
   ( ws_add | ws_surplus | ws_del | ws_model.milestoneLike )+
}

Appendix A.186 <substJoin>

<substJoin> (substitution join) identifies a series of possibly fragmented additions, deletions, or other revisions on a manuscript that combine to make up a single intervention in the text. [12.3.1.5. Substitutions]
Moduletranscr
Attributes
Member of
Contained by
May contain
core: desc
Example
While <del xml:id="r112">pondering</del> thus <add xml:id="r113">she mus'd</add>, her pinions fann'd <substJoin target="#r112 #r113"/>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element substJoin
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.pointing.attributes,
   ws_att.transcriptional.attributes,
   ( ws_model.descLike | ws_model.certLike )*
}

Appendix A.187 <supplied>

<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
reason
StatusRequired
Datatypeteidata.enumerated
Legal values are:
damaged
the original page has been damaged through tearing, folding, creasing, foxing, fire or water damage, etc.
flawed-reproduction
for cases where the reproduction of the source document causes illegiblity but we have reason to believe the original is still legible (i.e. photocopies with insufficient contrast, smearing, edges cut off during filming, underexposure, etc.)
obscured
the original page is intact but the text is illegible due to poorly inked type, patches applied to the original page surface, partial deletion, etc.
other
Anything not covered by the above values.
Member of
Contained by
May contain
Note

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Example
I am dr Sr yr <supplied reason="illegible"  source="#amanuensis_copy">very humble Servt</supplied> Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element supplied
{
   ws_att.fragmentable.attributes,
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   attribute reason
   {
      "damaged" | "flawed-reproduction" | "obscured" | "other"
   },
   ws_macro.paraContent
}

Appendix A.188 <surplus>

<surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Attributes
reasonone or more words indicating why this text is believed to be superfluous, e.g. repeated, interpolated etc.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Member of
Contained by
May contain
Example
I am dr Sr yrs <surplus reason="repeated">yrs</surplus> Sydney Smith
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element surplus
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   attribute reason { list { + } }?,
   ws_macro.paraContent
}

Appendix A.189 <table>

<table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]
Modulefigures
Attributes
subtype(subtype) provides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

type
StatusOptional
Legal values are:
toc
(table of contents)
errata
subscriber
gloss
rows(rows) indicates the number of rows in the table.
StatusOptional
Datatypeteidata.count
Note

If 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.
StatusOptional
Datatypeteidata.count
Note

If no number is supplied, an application must calculate the number of columns.

Within each row, columns should be presented left to right.

Member of
Contained by
May contain
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Example
<table rows="4cols="4">  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>  <row role="label">   <cell role="data"/>   <cell role="data">Dossing Cribs or Lodging Houses</cell>   <cell role="data">Beds</cell>   <cell role="data">Needys or Nightly Lodgers</cell>  </row>  <row role="data">   <cell role="label">Bury St Edmund's</cell>   <cell role="data">5</cell>   <cell role="data">8</cell>   <cell role="data">128</cell>  </row>  <row role="data">   <cell role="label">Thetford</cell>   <cell role="data">3</cell>   <cell role="data">6</cell>   <cell role="data">36</cell>  </row>  <row role="data">   <cell role="label">Attleboro'</cell>   <cell role="data">3</cell>   <cell role="data">5</cell>   <cell role="data">20</cell>  </row>  <row role="data">   <cell role="label">Wymondham</cell>   <cell role="data">1</cell>   <cell role="data">11</cell>   <cell role="data">22</cell>  </row> </table>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="row"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element table
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   attribute subtype { text }?,
   attribute type { "toc" | "errata" | "subscriber" | "gloss" }?,
   attribute rows { text }?,
   attribute cols { text }?,
   (
      ( ws_model.headLike | ws_model.global )*,
      (
         ( ( ws_row, ws_model.global* )+ )
       | ( ( ws_model.graphicLike, ws_model.global* )+ )
      ),
      ( ( ws_model.divBottom, ws_model.global* )* )
   )
}

Appendix A.190 <tag>

<tag> (tag) contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [23. Documentation Elements]
Moduletagdocs
Attributes
typeindicates the type of XML tag intended.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
start
a start-tag, with delimiters < and > is intended
end
an end-tag, with delimiters </ and > is intended
empty
an empty tag, with delimiters < and /> is intended
pi
a pi (processing instruction), with delimiters <? and ?> is intended
comment
a comment, with delimiters <!-- and --> is intended
ms
a marked-section, with delimiters <[CDATA[ and ]]> is intended
schemesupplies the name of the schema in which this tag is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(text encoding initiative) This tag is defined as part of the TEI scheme.[Default]
DBK
(docbook) this tag is part of the Docbook scheme.
XX
(unknown) this tag is part of an unknown scheme.
Schematron
HTML
Member of
Contained by
May containCharacter data only
Example
Mark the start of each italicised phrase with a <tag>hi rend="it"</tag> tag, and its end with a <tag type="end">hi</tag> tag. <tag type="comment">Example updated on 2008-04-05</tag>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element tag
{
   ws_att.global.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "start" | "end" | "empty" | "pi" | "comment" | "ms" }?,
   attribute scheme { text }?,
   text
}

Appendix A.191 <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader
Attributes
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatypeteidata.truthValue
Note

TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Member of
Contained by
header: encodingDesc
May contain
header: rendition
Example
<tagsDecl partial="true">  <rendition xml:id="rend-itscheme="css"   selector="emph, hi, name, title">font-style: italic;</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467"/>   <tagUsage gi="titleoccurs="45"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>
If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.
Content model
<content>
 <sequence>
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   ws_att.global.attributes,
   attribute partial { text }?,
   ( ws_rendition*, namespace* )
}

Appendix A.192 <taxonomy>

<taxonomy> (taxonomy) explicitly defines a typology used to classify texts using a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
header: classDecl
May contain
header: category
Note

The WWP version of this element is more restrictive than TEI, which permits defining the taxonomy implicitly via a bibliographic reference to it.

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>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>
Content model
<content>
 <elementRef key="category" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element taxonomy
{
   ws_att.global.attributes,
   ws_att.datcat.attributes,
   ws_category+
}

Appendix A.193 <teiCorpus>

<teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more <TEI> elements, each containing a single text header and a text. [4. Default Text Structure 16.1. Varieties of Composite Text]
Modulecore
Attributes
version(version) specifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Member of
Contained by
core: teiCorpus
May contain
core: teiCorpus
header: teiHeader
textstructure: TEI text
Note

Should contain one <teiHeader> for the corpus, and a series of <TEI> elements, one for each text.

As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <teiCorpus version="4.8.1" xml:lang="en" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- header for corpus -->  </teiHeader>  <TEI>   <teiHeader> <!-- header for first text -->   </teiHeader>   <text> <!-- content of first text -->   </text>  </TEI>  <TEI>   <teiHeader> <!-- header for second text -->   </teiHeader>   <text> <!-- content of second text -->   </text>  </TEI> <!-- more TEI elements here --> </teiCorpus>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.describedResource"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element teiCorpus
{
   ws_att.global.attributes,
   ws_att.typed.attributes,
   attribute version { text }?,
   ( ws_teiHeader, ws_model.resource*, ws_model.describedResource+ )
}

Appendix A.194 <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
core: teiCorpus
textstructure: TEI
May contain
Note

One of the few elements unconditionally required in any TEI document.

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
Schematron
<sch:pattern> <sch:rule context="wwp:teiHeader">  <sch:assert test="wwp:profileDesc/wwp:textClass">The WWP requires at least one <textClass> element be present.</sch:assert>  <sch:assert test="wwp:fileDesc/wwp:editionStmt or wwp:fileDesc/xi:include[ contains( @xpointer, 'WWPedition') ]">The WWP requires at least one <editionStmt> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:projectDesc or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPprojectDescription') ]">The WWP requires at least one <projectDesc> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:samplingDecl or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPsamplingDeclaration') ]">The WWP requires at least one <samplingDecl> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:editorialDecl or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPeditorialDeclaration') ]">The WWP requires at least one <editorialDecl> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:charDecl or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPcharacterDeclaration') ]">The WWP requires at least one <charDecl> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:classDecl or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPclassificationDeclaration') ]">The WWP requires at least one <classDecl> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:listPrefixDef or wwp:encodingDesc/xi:include[ contains( @xpointer, 'WWPlistPrefixDefinitions') ]">The WWP requires at least one <listPrefixDef> element be present or included.</sch:assert>  <sch:assert test="wwp:encodingDesc/wwp:listPrefixDef">WARNING: <listPrefixDef> not found, so values of @ref will not be tested — if you are using the supraSchemas project, just ignore this warning; otherwise, to validate @refs, perform XInclude processing before validation (to do so in oXygen check “Enable XInclude Processing” in the XML / XML Parser / XInclude Options preferences pane)</sch:assert> </sch:rule> </sch:pattern>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   ws_att.global.attributes,
   ( ws_fileDesc, ws_model.teiHeaderPart*, ws_revisionDesc? )
}

Appendix A.195 <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term xml:id="TDPV1rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element term
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.declaring.attributes,
   ws_att.pointing.attribute.targetLang,
   ws_att.pointing.attribute.evaluate,
   ws_att.sortable.attributes,
   ws_att.typed.attributes,
   ws_macro.phraseSeq
}

Appendix A.196 <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
volume
Indicates this text is one volume of a multi-volume work
Member of
Contained by
core: teiCorpus
textstructure: TEI group
May contain
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>  <front> <!-- front matter for the whole group -->  </front>  <group>   <text> <!-- first text -->   </text>   <text> <!-- second text -->   </text>  </group> </text>
Schematron
<sch:rule context="/wwp:TEI/wwp:teiHeader/wwp:text//wwp:text"> <sch:let name="textID"  value="normalize-space( /wwp:TEI/wwp:text/@xml:id )"/> <sch:assert test="substring( normalize-space( @xml:id ), 1, 7 ) eq substring( $textID, 1, 7 )">sub-text TR# <sch:value-of select="@xml:id"/> does not match main text TR# <sch:value-of select="$textID"/>.</sch:assert> </sch:rule>
SchematronExcept for a specific list of elements, test that any descendant of <text> has some content which could be used to represent source content. Note that the comments inserted into tadpoles are also exempted. (As is any other comment that contains the string ‘$$$’.)This constraint is defined here as it only applies to most descendants of <text>. Might be better to define an abstract pattern here, and give each individual element a concrete instance. Hmmm …
<sch:rule context="/*/wwp:text//* except ( self::wwp:ref[ @type = ('correction','error') ] | self::wwp:sic | self::wwp:ab[ @type eq 'placeholder'] | self::wwp:addSpan | self::wwp:alt | self::wwp:altGrp | self::wwp:anchor | self::wwp:cb | self::wwp:cell | self::wwp:choice | self::wwp:corr | self::wwp:delSpan | self::wwp:format | self::wwp:g[ @ref ] | self::wwp:gap | self::wwp:lb | self::wwp:link | self::wwp:linkGrp | self::wwp:milestone | self::wwp:mw[ @type = ('border','border-rule','border-ornamental','unknown','other') ] | self::wwp:pb | self::wwp:ptr | self::wwp:space | self::wwp:substJoin | self::wwp:transpose | self::xi:include )"> <sch:assert role="warning"  test=" normalize-space(.) ne '' or descendant-or-self::*/@copyOf or descendant-or-self::*/@sameAs or descendant::wwp:g or descendant::wwp:gap or descendant::wwp:anchor (: see [1] below :) or descendant::wwp:ab[ @type eq 'placeholder'] or descendant::wwp:ref[ @type = ('error','correction') ] or descendant-or-self::wwp:anagram[ contains( normalize-space( @target ), ' ') ] or child::comment()[matches( ., '\$\$\$') ] or @wwp:affirmed "> element requires some sort of representation of actual content from the source. </sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="hyperDiv"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   ws_att.global.attribute.affirmed,
   ws_att.global.attribute.n,
   ws_att.global.attribute.xmllang,
   ws_att.global.attribute.xmlbase,
   ws_att.global.attribute.xmlspace,
   ws_att.global.change.attribute.change,
   ws_att.global.linking.attribute.corresp,
   ws_att.global.linking.attribute.sameAs,
   ws_att.global.linking.attribute.next,
   ws_att.global.linking.attribute.prev,
   ws_att.global.rendition.attribute.rend,
   ws_att.global.rendition.attribute.style,
   ws_att.global.rendition.attribute.rendition,
   ws_att.global.responsibility.attribute.cert,
   ws_att.global.responsibility.attribute.resp,
   ws_att.global.source.attribute.source,
   ws_att.declaring.attributes,
   ws_att.written.attributes,
   attribute xml:id { text },
   attribute type { "volume" }?,
   (
      ws_model.global*,
      ( ( ws_hyperDiv, ws_model.global* )? ),
      ( ( ws_front, ws_model.global* )? ),
      ( ws_body | ws_group ),
      ws_model.global*,
      ( ( ws_back, ws_model.global* )? )
   )
}

Appendix A.197 <textClass>

<textClass> (text classification) [2.4.3. The Text Classification]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
header: catRef
Note

The WWP version of this element is more restrictive than TEI, which permits other methods of indicating the text's classification.

Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <elementRef key="catRef" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element textClass
{
   ws_att.global.attributes,
   ws_att.declarable.attributes,
   ws_catRef+
}

Appendix A.198 <time>

<time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
Modulecore
Attributes
Member of
Contained by
May contain
Note

At the WWP we use when-iso on <time>, not when, because in the vast majority of cases we do not have sufficient precision to include seconds (which W3C requires).

Example
As he sat smiling, the quarter struck — <time when="11:45:00">the quarter to twelve</time>.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element time
{
   ws_att.global.attributes,
   ws_att.calendarSystem.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attribute.period,
   ws_att.datable.custom.attribute.when-custom,
   ws_att.datable.custom.attribute.notBefore-custom,
   ws_att.datable.custom.attribute.notAfter-custom,
   ws_att.datable.custom.attribute.from-custom,
   ws_att.datable.custom.attribute.to-custom,
   ws_att.datable.custom.attribute.datingPoint,
   ws_att.datable.custom.attribute.datingMethod,
   ws_att.datable.iso.attribute.when-iso,
   ws_att.datable.iso.attribute.notBefore-iso,
   ws_att.datable.iso.attribute.notAfter-iso,
   ws_att.datable.iso.attribute.from-iso,
   ws_att.datable.iso.attribute.to-iso,
   ws_att.datable.w3c.attribute.notBefore,
   ws_att.datable.w3c.attribute.notAfter,
   ws_att.datable.w3c.attribute.from,
   ws_att.datable.w3c.attribute.to,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   ws_att.typed.attributes,
   ( text | ws_model.gLike | ws_model.phrase | ws_model.global )*
}

Appendix A.199 <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
Attributes
type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
sub
indicates a subtitle
main
used for the primary or main title of the work
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The 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.

Member of
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   ws_att.global.attributes,
   ws_att.canonical.attributes,
   ws_att.cmc.attributes,
   ws_att.datable.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "sub" | "main" }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   ws_macro.paraContent
}

Appendix A.200 <titleBlock>

<titleBlock> (title block) used to to encode the contents of title pages, acting as a container or wrapper for the title page's discrete elements. [4.6. Title Pages]
Moduletextstructure
Attributes
typeclassifies the title block.
StatusOptional
Legal values are:
titlePage
(title page) a page of bibliographic information about the current work[Default]
halfTitle
(half title) half titles, bastard titles, or other pages or portions thereof that contian bibliographic information, but less than the true title page
captionTitle
(caption title) a short snippet of bibliographic information smaller than a half title
colophon
A short inscription, typically at the end of a book or manuscript, containing the title, printer, date and place of printing, etc.
Member of
Contained by
textstructure: back front
May contain
Example
<titleBlock>  <docTitle>   <titlePart type="main">THOMAS OF Reading.</titlePart>   <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>  </docTitle>  <docEdition>Now the fourth time corrected and enlarged</docEdition>  <respLine>By T.D.</respLine>  <figure>   <head>TP</head>   <p>Thou shalt labor till thou returne to duste</p>   <figDesc>Printers Ornament used by TP</figDesc>  </figure>  <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>   <date>1612.</date>  </docImprint> </titleBlock>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.titlepagePart"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.titlepagePart"/>
   <classRef key="model.global"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element titleBlock
{
   ws_att.global.attributes,
   ws_att.typed.attribute.subtype,
   attribute type { "titlePage" | "halfTitle" | "captionTitle" | "colophon" }?,
   (
      ws_model.global*,
      ws_model.titlepagePart,
      ( ws_model.titlepagePart | ws_model.global )*
   )
}

Appendix A.201 <titlePart>

<titlePart> (title part) contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages]
Moduletextstructure
Attributes
type
StatusRequired
Datatypeteidata.enumerated
Legal values are:
address
alt
date
desc
main
reason
second
sub
vol
Member of
Contained by
textstructure: back front titleBlock
May contain
Note

The WWP version of this element is more permissive than the TEI version: we permit <docRole> (structurally <docRole>).

Example
<docTitle>  <titlePart type="main">THE FORTUNES    AND MISFORTUNES Of the FAMOUS    Moll Flanders, &amp;c.  </titlePart>  <titlePart type="desc">Who was BORN in NEWGATE,    And during a Life of continu'd Variety for    Threescore Years, besides her Childhood, was    Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof    once to her own Brother) Twelve Year a <hi>Thief,</hi>    Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>,    at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a  <hi>Penitent</hi>.</titlePart> </docTitle>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <macroRef key="macro.paraContent"/>
  <elementRef key="docAuthor"/>
 </alternate>
</content>
    
Schema Declaration
element titlePart
{
   ws_att.global.attributes,
   ws_att.typed.attribute.subtype,
   attribute type
   {
      "address"
    | "alt"
    | "date"
    | "desc"
    | "main"
    | "reason"
    | "second"
    | "sub"
    | "vol"
   },
   ( ws_macro.paraContent | ws_docAuthor )+
}

Appendix A.202 <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
derived-module-wwp-store: translator
header: funder sponsor
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence>
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <classRef key="model.respLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt
{
   ws_att.global.attributes,
   ( ws_title+, ws_model.respLike* )
}

Appendix A.203 <trailer>

<trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
core: lg list note
drama: castGroup
figures: table
May contain
Example
<trailer>Explicit pars tertia</trailer>
Example
<trailer>  <l>In stead of FINIS this advice <hi>I</hi> send,</l>  <l>Let Rogues and Thieves beware of <lb/>   <hi>Hamans</hi> END.</l> </trailer>
From EEBO A87070
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element trailer
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.typed.attributes,
   ws_att.written.attributes,
   (
      text
    | ws_lg
    | ws_model.gLike
    | ws_model.phrase
    | ws_model.inter
    | ws_model.lLike
    | ws_model.global
   )*
}

Appendix A.204 <translator>

<translator> contains the name (typically encoded in <persName> or <orgName>) of the entity that translated the bibliograhic item from one natural language to another.
Modulederived-module-wwp-store
Attributes
Member of
Contained by
core: bibl
derived-module-wwp-store: advertisement
May contain
Note

The WWP <translator> element may be thought of as syntactic sugar for either <tei:editor role="translator"> or <tei:respStmt><tei:resp>translator</tei:resp><!-- ... --></tei:respStmt></code>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element translator
{
   ws_att.global.attributes,
   ws_att.naming.attributes,
   ws_macro.phraseSeq
}

Appendix A.205 <transpose>

<transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [12.3.4.5. Transpositions]
Moduletranscr
Attributes
Contained by
transcr: listTranspose
May contain
core: ptr
Note

Transposition is usually indicated in a document by a metamark such as a wavy line or numbering.

The order in which <ptr> elements appear within a <transpose> element should correspond with the desired order, as indicated by the metamark.

Example
<transpose>  <ptr target="#ib02"/>  <ptr target="#ib01"/> </transpose>
The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01.
Content model
<content>
 <elementRef key="ptr" minOccurs="2"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element transpose { ws_att.global.attributes, ( ws_ptr, ws_ptr, ws_ptr* ) }

Appendix A.206 <unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
reason
StatusOptional
Datatypeteidata.enumerated
Legal values are:
damaged
the original page has been damaged through tearing, folding, creasing, foxing, fire or water damage, etc.
flawed-reproduction
for cases where the reproduction of the source document causes illegiblity but we have reason to believe the original is still legible (i.e. photocopies with insufficient contrast, smearing, edges cut off during filming, underexposure, etc.)
obscured
the original page is intact but the text is illegible due to poorly inked type, patches applied to the original page surface, partial deletion, etc.
agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility.

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear
{
   ws_att.global.attributes,
   ws_att.cmc.attributes,
   ws_att.dimensions.attributes,
   ws_att.editLike.attributes,
   attribute reason { "damaged" | "flawed-reproduction" | "obscured" }?,
   attribute agent { text }?,
   ws_macro.paraContent
}

Appendix A.207 <undo>

<undo> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [12.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
Moduletranscr
Attributes
targetpoints to one or more elements representing the interventions which are to be reverted or undone.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containEmpty element
Example
<line>This is <del change="#s2rend="overstrike">   <seg xml:id="undo-a">just some</seg>    sample <seg xml:id="undo-b">text</seg>,    we need</del>  <add change="#s2">not</add> a real example.</line> <undo target="#undo-a #undo-b"  rend="dottedchange="#s3"/>
This encoding represents the following sequence of events:
  • "This is just some sample text, we need a real example" is written
  • At stage s2, "just some sample text, we need" is deleted by overstriking, and "not" is added
  • At stage s3, parts of the deletion are cancelled by underdotting, thus reinstating the words "just some" and "text".
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element undo
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_att.spanning.attributes,
   ws_att.transcriptional.attributes,
   attribute target { list { + } }?,
   empty
}

Appendix A.208 <unknown>

<unknown> used to indicate a passage about which the proper encoding is not known to the encoder.
Modulederived-module-wwp-store
Attributes
desc
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
character data
macro.anyXML
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <macroRef key="macro.anyXML"/>
  <textNode/>
 </alternate>
</content>
    
Schema Declaration
element unknown
{
   ws_att.global.attributes,
   ws_att.ascribed.attributes,
   ws_att.typed.attributes,
   attribute desc { list { + } }?,
   ( macro.anyXML | text )*
}

Appendix A.209 <val>

<val> (value) contains a single attribute value. [23. Documentation Elements 23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
Member of
Contained by
May containCharacter data only
Example
<val>unknown</val>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element val { ws_att.global.attributes, text }

Appendix A.210 <vuji>

<vuji> shorthand for <orig> and <reg> (in <choice>) for VUJI phenomena
Modulederived-module-wwp-store
Attributes
Member of
Contained by
May containEmpty element
Note

This element is syntactic sugar for a <choice> element whose child <orig> contains the content of this <vuji>, and whose child <reg> contains the regularized version thereof. I.e.

<vuji> contentconverted <orig>converted <reg>
vvu
VVU
uuv
UUV
jji
JJI
iij
IIJ
vvvvw
VVVVW

Thus in general what you see on the page should be the content of <vuji>.

Content model
<content> 
 
 vVuUjJiIvvVVVv
 
</content>
    
Schema Declaration
element vuji
{
   ws_att.global.attributes,
   ( "v" | "V" | "u" | "U" | "j" | "J" | "i" | "I" | "vv" | "VV" | "Vv" )
}

Appendix A.211 <width>

<width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [11.3.4. Dimensions]
Modulemsdescription
Attributes
Member of
Contained by
May contain
gaiji: g
character data
Note

If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

Example
<width unit="in">4</width>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element width
{
   ws_att.global.attributes,
   ws_att.dimensions.attributes,
   ws_macro.xtext
}

Appendix B Model classes

Appendix B.1 model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
Moduletei
Used by
Membersmodel.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs] addrLine

Appendix B.2 model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Moduletei
Used by
Membersaddress email

Appendix B.3 model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Moduletei
Used by
Membersmodel.quoteLike[quote] floatingText said

Appendix B.4 model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Memberslicence

Appendix B.5 model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
Membersbibl biblStruct listBibl

Appendix B.6 model.biblPart

Appendix B.7 model.castItemPart

model.castItemPart groups component elements of an entry in a cast list, such as dramatic role or actor's name.
Moduletei
Used by
Membersmodel.labelLike[desc label] actor role roleDesc

Appendix B.8 model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.cmc model.divPart[model.lLike[l] model.pLike[ab p] lg sp spGrp] model.inter[model.attributable[model.quoteLike[quote] floatingText said] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike[desc label] model.listLike[list table] model.oddDecl model.stageLike[stage] castList l lg]
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

Appendix B.9 model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Used by
Membersdate time

Appendix B.10 model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei
Used by
Membersdesc

Appendix B.11 model.describedResource

model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document. [1.3. The TEI Class System]
Moduletei
Used by
MembersTEI teiCorpus

Appendix B.12 model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersmodel.divBottomPart[closer postscript trailer] model.divWrapper[argument respLine dateline docRole docDate epigraph]

Appendix B.13 model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages]
Moduletei
Used by
Memberscloser postscript trailer

Appendix B.14 model.divLike

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

Appendix B.15 model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.lLike[l] model.pLike[ab p] lg sp spGrp
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

Appendix B.16 model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersmodel.divTopPart[model.headLike[head] opener] model.divWrapper[argument respLine dateline docRole docDate epigraph] model.labelLike[desc label]

Appendix B.17 model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Moduletei
Used by
Membersmodel.headLike[head] opener

Appendix B.18 model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersargument respLine dateline docRole docDate epigraph

Appendix B.19 model.editorialDeclPart

model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times.
Moduletei
Used by
Memberscorrection hyphenation normalization quotation

Appendix B.20 model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Memberscode distinct emph foreign gloss ident mentioned soCalled term title

Appendix B.21 model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei
Used by
MemberscharDecl classDecl editorialDecl include listPrefixDef projectDesc samplingDecl tagsDecl

Appendix B.22 model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]
Moduletei
Used by
Membersmodel.frontPart.drama[castList set] docAuthorization imprimatur listBibl titleBlock

Appendix B.23 model.frontPart.drama

model.frontPart.drama groups elements which appear at the level of divisions within front or back matter of performance texts only. [7.1. Front and Back Matter ]
Moduletei
Used by
MemberscastList set

Appendix B.24 model.gLike

model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
Moduletei
Used by
Membersg

Appendix B.26 model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Moduletei
Used by
MembersaddSpan damageSpan delSpan elision gap space

Appendix B.27 model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersalt link listTranspose substJoin
Note

Elements 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.

Appendix B.28 model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Moduletei
Used by
Membersgraphic

Appendix B.29 model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
Membershead

Appendix B.30 model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membershi mcr

Appendix B.31 model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membersmodel.emphLike[code distinct emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi mcr]

Appendix B.32 model.hyperDivPart

model.hyperDivPart groups together elements that may appear inside the <hyperDiv>.
Classes definedsequenceOptional
Modulederived-module-wwp-store
Used by
Membersacrostics adds altGrp anagrams castList linkGrp notes

Appendix B.33 model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Moduletei
Used by
MembersbiblScope pubPlace publisher

Appendix B.34 model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.attributable[model.quoteLike[quote] floatingText said] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike[desc label] model.listLike[list table] model.oddDecl model.stageLike[stage] castList l lg

Appendix B.35 model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Moduletei
Used by
Membersl

Appendix B.36 model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
Membersdesc label

Appendix B.38 model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Moduletei
Used by
Membersmodel.hiLike[hi mcr] choice del handShift line mod redo seg unclear undo

Appendix B.39 model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
Memberslist table

Appendix B.40 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.6.3. Numbers and Measures]
Moduletei
Used by
Membersheight measure num width

Appendix B.41 model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements]
Moduletei
Used by
Membersanchor cb mw lb milestone pb

Appendix B.42 model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

Appendix B.43 model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
Membersname orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

Appendix B.44 model.noteBottom

model.noteBottom groups together elements that may appear at the bottom of a <note> or <postscript>.
Modulederived-module-wwp-store
Used by
MembersrespLine closer trailer

Appendix B.45 model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Moduletei
Used by
Membersadvertisement note

Appendix B.47 model.noteTop

model.noteTop groups together elements that may appear at the top of a <note> or <postscript>.
Modulederived-module-wwp-store
Used by
Membersmodel.headLike[head] model.labelLike[desc label] opener ref

Appendix B.49 model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
Moduletei
Used by
Membersargument respLine dateline docRole docDate docEdition docImprint epigraph head titlePart

Appendix B.50 model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
Membersmodel.addressLike[address email] model.dateLike[date time] model.measureLike[height measure num width] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs]

Appendix B.51 model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersmodel.pPart.editorial[abbr am choice ex expan subst] model.pPart.transcriptional[corr del handShift mod orig redo reg regMe sic supplied surplus unclear undo vuji]

Appendix B.52 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.5. Simple Editorial Changes]
Moduletei
Used by
Membersabbr am choice ex expan subst

Appendix B.53 model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [11. Manuscript Description]
Moduletei
Used by
Membersdimensions

Appendix B.54 model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Moduletei
Used by
Memberscorr del handShift mod orig redo reg regMe sic supplied surplus unclear undo vuji

Appendix B.57 model.phrase.xml

model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values. [23. Documentation Elements]
Moduletei
Used by
Membersatt gi tag val

Appendix B.58 model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names]
Moduletei
Used by
MembersplaceName

Appendix B.59 model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
Membersmodel.placeNamePart[placeName]

Appendix B.60 model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei
Used by
MemberscalendarDesc handNotes include langUsage listTranspose textClass

Appendix B.61 model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Moduletei
Used by
Membersptr ref

Appendix B.62 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. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Memberspublisher
Note

The ‘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.

Appendix B.63 model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Membersmodel.ptrLike[ptr ref] address availability date idno include pubPlace
Note

A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

See also model.publicationStmtPart.agency.

Appendix B.64 model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei
Used by
Membersquote

Appendix B.65 model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Moduletei
Used by
Memberstext

Appendix B.66 model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei
Used by
Membersauthor editor funder respStmt sponsor translator

Appendix B.67 model.segLike

model.segLike groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Moduletei
Used by
Membersseg
Note

The 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.

Appendix B.68 model.stageLike

model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]
Moduletei
Used by
Membersstage
Note

Stage directions are members of class inter: that is, they can appear between or within component-level elements.

Appendix B.69 model.teiHeaderPart

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

Appendix B.70 model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docRole>, <docImprint>, or <epigraph>. [4.6. Title Pages]
Moduletei
Used by
Membersargument respLine docRole docAuthorization docDate docEdition docImprint docSale epigraph graphic imprimatur titlePart

Appendix C Attribute classes

Appendix C.1 att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Moduletei
Membersnote
Attributes
anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 17.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234">  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.  </note>  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.  </note> </noteGrp>

Appendix C.2 att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Membersatt.ascribed.directed[said sp spGrp stage] change unknown
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <role> 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>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

Appendix C.3 att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Memberssaid sp spGrp stage
Attributes
toWhomindicates the person, or group of people, to whom a speech act or action is directed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.
<castItem type="role">  <role xml:id="emil">Emilius.</role> </castItem> <castItem type="role">  <role xml:id="lov">Lovisa</role> </castItem> <castItem type="role">  <role xml:id="serv">A servant</role> </castItem> <!-- ... --> <sp who="#emil"  toWhom="#lov">  <speaker>Emil.</speaker>  <l n="1">My love!</l> </sp> <sp who="#lov"  toWhom="#emil">  <speaker>Lov.</speaker>  <l n="2">I have no Witness of my Noble Birth</l>  <stage who="emil"   toWhom="#serv">Pointing to her Woman.</stage>  <l>But that poor helpless wretch——</l> </sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

Appendix C.4 att.breaking

att.breaking provides attributes 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.11.3. Milestone Elements]
Moduletei
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.
StatusRecommended
Datatypeteidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, the words lāðost and reord-berendum each start on one line and continue onto the next.
<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

Appendix C.5 att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersdate docDate time
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

Appendix C.6 att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming[att.personal[name orgName persName placeName] author editor pubPlace rs translator] actor bibl biblStruct catDesc date docRole funder publisher regMe resp respStmt sponsor term time title
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

The 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.

ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

The 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.

ExampleIn this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange.

These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange.

Appendix C.7 att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei
MembersbiblScope citedRange
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word

Appendix C.8 att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei
Membersab abbr address alt anchor argument bibl biblStruct respLine cb choice closer corr date dateline del desc distinct docRole docDate email emph epigraph expan figure floatingText foreign gloss graphic head hi idno l label lb lg link list listBibl measure mentioned milestone name note num opener orgName orig p pb persName placeName postscript ptr quote ref reg rs said salute seg sic signed soCalled stage table term time title trailer unclear
Attributes
generatedBy(generated by) categorizes how the content of an element was generated in a CMC environment.
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:*[@generatedBy]"> <sch:assert test="ancestor-or-self::tei:post">The @generatedBy attribute is for use within a <post> element.</sch:assert> </sch:rule>
Suggested values include:
human
the content was ‘naturally’ typed or spoken by a human user
template
the content was generated after a human user activated a template for its insertion
system
the content was generated by the system, i.e. the CMC environment
bot
the content was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself
unspecified
the content was generated by an unknown or unspecified process
automatic system message in chat: user moves on to another chatroom
<post type="event"  generatedBy="system"  who="#system"  rend="color:blue">  <p>   <name type="nickname"    corresp="#A02">McMike</name> geht    in einen anderen Raum: <name type="roomname">Kreuzfahrt</name>  </p> </post>
automatic system message in chat: user enters a chatroom
<post type="event"  generatedBy="system">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> betritt    den Raum. </p> </post>
automatic system message in chat: user changes his font color
<post type="event"  generatedBy="system"  rend="color:red">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> hat die    Farbe gewechselt.  </p> </post>
An automatic signature of user including an automatic timestamp (Wikipedia discussion, anonymized). The specification of generatedBy at the inner element <signed> is meant to override the specification at the outer element <post>. This is generally possible when the outer generatedBy value is "human".
<post type="standard"  generatedBy="human"  indentLevel="2"  synch="#t00394407"  who="#WU00005582">  <p> Kurze Nachfrage: Die Hieros für den Goldnamen stammen    auch von Beckerath gem. Literatur ? Grüße —</p>  <signed generatedBy="template"   rend="inline">   <gap reason="signatureContent"/>   <time generatedBy="template">18:50, 22. Okt. 2008 (CEST)</time>  </signed> </post>
Wikipedia talk page: user signature
<post type="written"  generatedBy="human"> <!-- ... main content of posting ... -->  <signed generatedBy="template">   <gap reason="signatureContent"/>   <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>  </signed> </post>

Appendix C.9 att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Moduletranscr
Membersline
Attributes
startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
StatusOptional
Datatypeteidata.pointer
ulxgives the x coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
pointsidentifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
StatusOptional
Datatype3–∞ occurrences of teidata.point separated by whitespace

Appendix C.10 att.damaged

att.damaged provides attributes describing the nature of any physical damage affecting a reading. [12.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes]
Moduletei
MembersdamageSpan
Attributes
agentcategorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The <damage> element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as <supplied>.
StatusOptional
Datatypeteidata.probCert
Note

The <damage> element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the <unclear> tag (for partial illegibility) or the <gap> tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.

groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
StatusOptional
Datatypeteidata.count

Appendix C.11 att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersauthor change date docDate editor funder idno licence mapping name orgName persName placeName resp sponsor time title
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s, or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="*[@calendar]"> <sch:assert test="/wwp:TEI/wwp:teiHeader/wwp:profileDesc/wwp:calendarDesc/wwp:calendar/@xml:id = substring( normalize-space(@calendar), 2 )">The @calendar attribute of <sch:value-of select="name(.)"/> should point to a <gi>calendar</gi> element, but this one ("<sch:value-of select="normalize-space(@calendar)"/>") does not; this error will always occur unless you perform XInclude processing before validation (to do so in oXygen check “Enable XInclude Processing” in the XML / XML Parser / XInclude Options preferences pane)</sch:assert> </sch:rule>
Note

This ‘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.

Appendix C.12 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). [14.4. Dates]
Modulenamesdates
Membersatt.datable[author change date docDate editor funder idno licence mapping name orgName persName placeName resp sponsor time title]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
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 constrained 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.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<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 custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred.
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.pointer
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.
In this example, 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.
<date when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> </date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

Appendix C.13 att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 14.4. Dates]
Modulenamesdates
Membersatt.datable[author change date docDate editor funder idno licence mapping name orgName persName placeName resp sponsor time title]
Attributes
when-isosupplies the value of a date or time in a standard form.
StatusOptional
Datatypeteidata.temporal.iso
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 Second Edition specification. The first occurence could not.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If 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-01dur-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.

Appendix C.14 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.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersatt.datable[author change date docDate editor funder idno licence mapping name orgName persName placeName resp sponsor time title]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
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>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a 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 portion of a temporal 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.

Appendix C.15 att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [10.5.2. Lexical View 19.3. Other Atomic Feature Values]
Moduletei
Membersatt.segLike[seg] category taxonomy
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </f> <!-- ... --> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f name="POSfVal="#commonNoun"/> <!-- ... --> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol xml:id="commonNounvalue="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNounvalue="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
ExampleIn the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true"> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...-->  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> <!--...--> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... -->   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
ExampleThe att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

Appendix C.16 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. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersavailability bibl biblStruct correction editorialDecl hyphenation langUsage listBibl normalization projectDesc quotation samplingDecl sourceDesc textClass
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

Appendix C.17 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. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersab back body div floatingText front gloss graphic group lg p postscript ptr ref term text
Attributes
author
StatusOptional
Datatype1–7 occurrences of teidata.pointer separated by whitespace
Suggested values include:
p:tbd-check
(to be determined, check) We do not yet know who this author is; the encoder is expecting a WWP staff member to check and replace this value.
p:tbd-female
(to be determined, female) We are confident this author is a woman, but have yet to figure out exactly who she is.
p:tbd-male
(to be determined, male) We are confident this author is a man, but have yet to figure out exactly who he is.
p:tbd
(to be determined) We do not know who this author is, but expect (or at least hope) to find out in the near future.
p:unknown-female
We do not know who this author is, but are reasonably confident she is a woman. While it is possible her identity is ascertained in the future, we are not expecting it.
p:unknown-male
We do not know who this author is, but are reasonably confident he is a man. While it is possible his identity is ascertained in the future, we are not expecting it.
p:unknown.zzx
We do not know how this author is. While it is possible his or her identity is ascertained in the future, we are not expecting it.
p:collective
Used to indicate that authorship is attributed to a collection of individuals, sex unspecified.
Note

Should point to one or more <person> elements from our personography, preferably using the p: prefix.

decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text.

Appendix C.18 att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersatt.damaged[damageSpan] addSpan date del delSpan dimensions elision ex gap height mod redo space subst substJoin supplied surplus time unclear undo width
Attributes
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

Appendix C.19 att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Moduletei
Membersdiv lg
Attributes
org(organization) specifies how the content of the division is organized.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

Appendix C.20 att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl biblStruct change revisionDesc
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21"   status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01status="frozen"   who="#MSM"/>  <change when="2010-03-01status="draft"   who="#LB"/> </revisionDesc>

Appendix C.21 att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersatt.transcriptional[add addSpan del delSpan mod redo subst substJoin undo] am corr date ex expan name orgName persName placeName reg supplied surplus time unclear
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
StatusOptional
Datatypeteidata.xTruthValue
Defaultfalse
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

Appendix C.22 att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Moduletei
Memberscb lb milestone pb
Attributes
ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>  <bibl xml:id="stapledon1937">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>  </bibl>  <bibl xml:id="stapledon1968">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>  </bibl> </listBibl> <!-- ... --> <p>Looking into the future aeons from the supreme moment of the cosmos, I saw the populations still with all their strength maintaining the<pb n="411edRef="#stapledon1968"/>essentials of their ancient culture, still living their personal lives in zest and endless novelty of action, … I saw myself still preserving, though with increasing difficulty, my lucid con-<pb n="291edRef="#stapledon1937"/>sciousness;</p>

Appendix C.23 att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei
Membersatt.divLike[div lg] att.segLike[seg] ab l p supplied
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.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

Note

In general, part should not be used on an element instance that contains an instance of itself. E.g., part should not be on <div> that has a child <div>, or a <seg> that has a grandchild <seg>. In these cases use next and prev instead.

The part attribute should only be used on an element that is inside an instance of itself when all of the partial elements being aggregated are inside the same instance outer copy of the element. E.g., a chapter (<div type="chapter">) contains a single letter (<div type="letter">) that is presented in two pieces with a significant narrative interuption. Because those two pieces are in the same <div>, it makes sense to use part. If the letter starts in chapter 2 and ends in chapter 3 it is probably better to use next and prev instead.

Appendix C.24 att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width
Attributes
affirmedUse of this attribute indicates a seal of approval for the encoding of the element on which it appears, a seal earned by staff affirmation (or at least consensus), typically at an encoding meeting.
StatusOptional
Datatypeteidata.truthValue
Note

This attribute is used to indicate that some thorny or difficult encoding that is not easily looked up in our documentation is, per WWP staff, a correct encoding. The encoding in question might be a descendant of the element on which this attribute occurs.

xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatypeteidata.text
Note

The 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.
StatusOptional
Datatypeteidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note

The 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.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

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 (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

Schematron
<sch:rule context="@xml:id"> <sch:let name="thisID"  value="normalize-space(.)"/> <sch:report test="../(ancestor::*|preceding::*)/@xml:id[ normalize-space(.) eq $thisID ] ">The @xml:id "<sch:value-of select="$thisID"/>" on <<sch:value-of select="name(..)"/>> duplicates an @xml:id found earlier in the document</sch:report> </sch:rule>
Note

The WWP does not currently use the XML base attribute. It is permitted by this schema so that validation post-XInclude processing works.

The rendition attribute is currently only used in those cases where a non-Unicode character is required in the value of the rendition ladder.

Appendix C.25 att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr
Membersatt.global[TEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width]
Attributes
changepoints to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

Appendix C.26 att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
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 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.
sameAspoints to an element that is the same as the current element.
StatusOptional
Datatypeteidata.pointer
nextpoints to the next element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

Schematron
<sch:rule context="*[@xml:id]"> <sch:let name="isAprev"  value="//@prev/normalize-space(.) = concat('#',@xml:id)"/> <sch:let name="isAnext"  value="//@next/normalize-space(.) = concat('#',@xml:id)"/> <sch:report test="@next and not( $isAprev )"  sqf:fix="notpreved">Element <sch:value-of select="@xml:id"/> has a next= but is not pointed at by a prev=</sch:report> <sch:report test="@prev and not( $isAnext )"  sqf:fix="notnexted">Element <sch:value-of select="@xml:id"/> has a prev= but is not pointed at by a next=</sch:report> <sch:report test="not( @next ) and $isAprev"  sqf:fix="nextless">Element <sch:value-of select="@xml:id"/> is pointed at by a prev= but does not have a next=</sch:report> <sch:report test="not( @prev ) and $isAnext"  sqf:fix="prevless">Element <sch:value-of select="@xml:id"/> is pointed at by a next= but does not have a prev=</sch:report> </sch:rule> <sqf:fixes> <sqf:fix id="notpreved">  <sqf:description>   <sqf:title>Point at me with a @prev</sqf:title>   <sqf:p>Add a @prev that points to me to the element I point to with @next</sqf:p>  </sqf:description>  <sch:let name="next"   value="id( substring(@next,2) )"/>  <sch:let name="ptr2me"   value="concat('#', @xml:id )"/>  <sqf:add target="prev"   node-type="attribute" match="$next" select="$ptr2me"/> </sqf:fix> <sqf:fix id="notnexted">  <sqf:description>   <sqf:title>Point at me with a @next</sqf:title>   <sqf:p>Add a @next that points to me to the element I point to with @prev</sqf:p>  </sqf:description>  <sch:let name="prev"   value="id( substring(@prev,2) )"/>  <sch:let name="ptr2me"   value="concat('#', @xml:id )"/>  <sqf:add target="next"   node-type="attribute" match="$prev" select="$ptr2me"/> </sqf:fix> <sqf:fix id="nextless">  <sqf:description>   <sqf:title>Add missing @next</sqf:title>   <sqf:p>For an element that is pointed to by a @prev but does not have an @next, add the @next</sqf:p>  </sqf:description>  <sch:let name="myID" value="@xml:id"/>  <sqf:add node-type="attribute"   target="next"   select="concat('#',//*[@prev/normalize-space(.) eq concat('#',$myID)][1]/@xml:id)"/> </sqf:fix> <sqf:fix id="prevless">  <sqf:description>   <sqf:title>Add missing @prev</sqf:title>   <sqf:p>For an element that is pointed to by a @next but does not have an @prev, add the @prev</sqf:p>  </sqf:description>  <sch:let name="myID" value="@xml:id"/>  <sqf:add node-type="attribute"   target="prev"   select="concat('#',//*[@next/normalize-space(.) eq concat('#',$myID)][1]/@xml:id)"/> </sqf:fix> </sqf:fixes>
Schematron
<sch:rule context="@prev|@next"> <sch:let name="element" value=".."/> <sch:let name="me"  value="normalize-space(.)"/> <sch:let name="ptr"  value="if ( starts-with( $me,'#') ) then substring-after( $me,'#') else 'ERROR!?!'"/> <sch:let name="hasSpace"  value="contains( $me,' ')"/> <sch:let name="points2local"  value="exists( id( $ptr ) )"/> <sch:let name="points2same"  value="id( $ptr ) is $element"/> <sch:let name="points2sameGI"  value="name( $element ) eq name( id( $ptr ) )"/> <sch:let name="pointsAfter"  value="id( $ptr ) >> $element"/> <sch:let name="pointsBefore"  value="$element >> id( $ptr )"/> <sch:let name="msg_part_1"  value="concat( '@', name(.), ' of <', name( $element ), '> ', if (../@xml:id) then concat('(with @xml:id "', ../@xml:id,'")') else '' )"/> <sch:report test="$hasSpace">  <sch:value-of select="$msg_part_1"/> has more than 1 pointer (a space in a URI should be written '%20')</sch:report> <sch:assert test="if ( not( $hasSpace ) ) then ( $points2local ) else true()">  <sch:value-of select="$msg_part_1"/> does not point to a local element.</sch:assert> <sch:report test="if ( not( $hasSpace ) ) then ( $points2same ) else false()">  <sch:value-of select="$msg_part_1"/> points to itself.</sch:report> <sch:assert test="if ( not( $hasSpace ) and $points2local ) then ( $points2sameGI ) else true()">  <sch:value-of select="$msg_part_1"/> points to a <<sch:value-of select="name( id( $ptr ) )"/>> (it should point to another <<sch:value-of select="name( $element )"/>>).</sch:assert> <sch:assert test="if ( not( $hasSpace ) and $points2local and local-name(.) eq 'prev' and not( $points2same ) ) then ( $pointsBefore ) else 'true()'">  <sch:value-of select="$msg_part_1"/> points to a <<sch:value-of select="name( id( $ptr ) )"/>> that is after itself.</sch:assert> <sch:assert test="if ( not( $hasSpace ) and $points2local and local-name(.) eq 'next' and not( $points2same ) ) then ( $pointsAfter ) else 'true()'">  <sch:value-of select="$msg_part_1"/> points to a <<sch:value-of select="name( id( $ptr ) )"/>> that is prior to itself.</sch:assert> </sch:rule>
Note

The WWP does not use the TEI synch, copyOf, exclude, or select attributes.

Appendix C.27 att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global[TEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<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>
Note

These 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.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text.
StatusOptional
Datatypeteidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rendition="#normal">New Blazing-World</hi>. </head> <!-- elsewhere... --> <rendition xml:id="sc"  scheme="css">font-variant: small-caps</rendition> <rendition xml:id="normal"  scheme="css">font-variant: normal</rendition> <rendition xml:id="ac"  scheme="css">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

Appendix C.28 att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global[TEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr resp="#editorcert="high">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<!-- in the <text> ... --><lg> <!-- ... -->  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

Appendix C.29 att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global[TEI ab abbr acrostic acrostics actor add addSpan addrLine address adds advertisement alt altGrp am anagram anagrams analytic anchor argument att author availability back bibl biblScope biblStruct body respLine calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change char charDecl choice citedRange classDecl closer code corr correction damageSpan date dateline del delSpan desc dimensions distinct div docRole docAuthorization docDate docEdition docImprint docSale edition editionStmt editor editorialDecl elision email emph encodingDesc epigraph ex expan extent figDesc figure fileDesc floatingText foreign front funder mw g gap gi gloss graphic group handNote handNotes handShift head headItem headLabel height hi hyphenation ident idno imprimatur imprint include item l label langUsage language lb lg licence line link linkGrp list listBibl listPrefixDef listTranspose mapping mcr measure mentioned metamark milestone mod monogr name normalization note notes notesStmt num opener orgName orig p pb persName placeName postscript prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher quotation quote redo ref reg regMe rendition resp respStmt revisionDesc role roleDesc row rs said salute samplingDecl seg series set sic signed soCalled sourceDesc sp spGrp space speaker sponsor stage subst substJoin supplied surplus table tag tagsDecl taxonomy teiCorpus teiHeader term text textClass time title titleBlock titlePart titleStmt trailer translator transpose unclear undo unknown val vuji width]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source; it provides a pointer to the bibliographic citation for the source from which a quotation, citation, or passage of direct speech is drawn; or a pointer to the complete bibliographic entry in our external bibliography that corresponds to a transcribed bibliographic citation in a text; or the source from which an untranscribably passage encoded as <supplied> was obtained. At the WWP this means that in general it should point to a <bibl>; furthermore that <bibl> is usually in XXXX.

The location may be provided using any form of URI. At the WWP our usual practice is to use a private URI scheme by prefixing the xml:id of the target <bibl> with a b:.

If a quotation may have come from more than one source, pointers to multiple <bibl>s may be provided. E.g. source="b:IT50057 b:IT50059 b:IT50060".

Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
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>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

Appendix C.30 att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [12.3.2.1. Document Hands]
Moduletei
MembershandNote handShift
Attributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatypeteidata.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

Appendix C.31 att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media[graphic] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
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="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This 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.

Appendix C.32 att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei
Membersmeasure
Attributes
unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
page
leaves
Note

Here at the WWP, the only possible value of unit is page; furthermore, unit is always used on the <measure> inside the <extent> of the <monogr> in the <sourceDesc>, and never used within the <text>. That is, we use unit in metadata, not transcribed data.

unitRefpoints to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
StatusOptional
Datatypeteidata.pointer
quantity(quantity) specifies the number of the specified units that comprise the measurement
StatusOptional
Datatypeteidata.numeric
commodity(commodity) indicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron
<sch:rule context="wwp:extent/wwp:measure"> <sch:assert test="@unit">When <measure> is used inside <extent> (typically in the <teiHeader>) it should have a @unit.</sch:assert> </sch:rule> <sch:rule context="wwp:measure[ not( parent::wwp:extent ) ]"> <sch:report test="@unit">When <measure> is used as a transcriptional element (i.e., inside <text>, not <teiHeader>) it should not have a @unit.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@unitRef]"> <sch:report test="@unit" role="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure quantity="0.5unit="gal"   commodity="ice cream">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure quantity="1.893unit="L"   commodity="ice cream">half    a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

Appendix C.33 att.media

att.media provides attributes for specifying display and related properties of external media.
Moduletei
Membersgraphic
Attributes
widthWhere the media are displayed, indicates the display width.
StatusOptional
Datatypeteidata.outputMeasurement
heightWhere the media are displayed, indicates the display height.
StatusOptional
Datatypeteidata.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size.
StatusOptional
Datatypeteidata.numeric

Appendix C.34 att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [11.6. Intellectual Content]
Modulemsdescription
Membersquote
Attributes
defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
StatusOptional
Datatypeteidata.xTruthValue
Note

In 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.

Appendix C.35 att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms]
Moduletei
Membersatt.personal[name orgName persName placeName] author editor pubPlace rs translator
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The 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.

Appendix C.36 att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
Membersquote seg
Attributes
notationnames the notation used for the content of the element.
StatusOptional
Datatypeteidata.enumerated

Appendix C.37 att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement. [17.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
MembersprefixDef
Attributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatypeteidata.pattern
Note

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.

replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
StatusRequired
Datatypeteidata.replacement
Note

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

Appendix C.38 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. [14.2.1. Personal Names]
Moduletei
Membersname orgName persName placeName
Attributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

Appendix C.39 att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Membersatt.pointing.group[altGrp linkGrp] alt anagram calendar catRef citedRange gloss licence link note ptr ref substJoin term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to 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 (IETF)Internet Engineering Task Force definitions.

targetspecifies the destination of the reference by supplying one or more URI References.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One 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.

evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

Appendix C.40 att.pointing.group

att.pointing.group provides a set of attributes common to all elements which enclose groups of pointer elements. [17. Linking, Segmentation, and Alignment]
Moduletei
MembersaltGrp linkGrp
Attributes
domainsoptionally specifies the identifiers of the elements within which all elements indicated by the contents of this element lie.
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
Note

If this attribute is supplied every element specified as a target must be contained within the element or elements named by it. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but in the wrong context. If this attribute is not supplied, then target elements may appear anywhere within the target document.

targFunc(target function) describes the function of each of the values of the target attribute of the enclosed <link>, <join>, or <alt> tags.
StatusOptional
Datatype2–∞ occurrences of teidata.word separated by whitespace
Note

The number of separate values must match the number of values in the target attribute in the enclosed <link>, <join>, or <alt> tags (an intermediate <ptr> element may be needed to accomplish this). It should also match the number of values in the domains attribute, of the current element, if one has been specified.

Appendix C.41 att.resourced

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

Appendix C.42 att.scope

att.scope provides attributes to describe, in general terms, the scope of an element’s application.
Moduletei
Membersatt.handFeatures[handNote handShift] language
Attributes
scopeindicates the scope of application of the element
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sole
only this particular feature is used throughout the document
major
this feature is used through most of the document
minor
this feature is used occasionally through the document
<langUsage>  <language ident="en"   scope="major"/>  <language ident="es"   scope="minor"/>  <language ident="x-ww"   scope="minor">An invented language the children call <name>Wikwah</name>.</language> </langUsage>
<handNote scope="sole">  <p>Written in insular phase II half-uncial with    interlinear Old English gloss in an Anglo-Saxon    pointed minuscule.</p> </handNote>

Appendix C.43 att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Moduletei
Membersseg
Attributes
function(function) characterizes the function of the segment.
StatusOptional
Datatypeteidata.enumerated
Note

Attribute 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.

Appendix C.44 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. [10.1. Dictionary Body and Overall Structure]
Moduletei
Membersbibl biblStruct idno item list listBibl term
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
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.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

Appendix C.45 att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [12.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
Moduletei
MembersaddSpan cb damageSpan delSpan lb metamark milestone mod pb redo undo
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatypeteidata.pointer
SchematronThe @spanTo attribute must point to an <anchor> element
<sch:rule context="wwp:*[@spanTo]"> <sch:let name="spanTo"  value="substring(@spanTo,2)"/> <sch:let name="spanEnd"  value="id( $spanTo )"/> <sch:assert test="$spanEnd/self::wwp:anchor"> The @spanTo of <gi>  <sch:name/>  </gi> must point to an <gi>anchor</gi>; this one (<val>  <sch:value-of select="@spanTo"/>  </val>) points to a <gi>  <sch:value-of select="local-name($spanEnd)"/>  </gi>. </sch:assert> </sch:rule>
SchematronThe @spanTo attribute must point to an element following the current element; however, this can only be tested if both this element and the one pointed to are in the same document.
<sch:rule context="tei:*[ starts-with( @spanTo, '#') ]"> <sch:assert test="id( substring( @spanTo, 2 ) ) >> .">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current <sch:name/> element </sch:assert> </sch:rule>
Note

The 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.

Appendix C.46 att.structuralCategorization

att.structuralCategorization provides a type attribute with a closed value list suitable for use with structural elements like <text>, <floatingText>, and <div>.
Modulederived-module-wwp-store
Membersbody div floatingText
Attributes
subtypeprovides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

type
StatusOptional
Datatypeteidata.enumerated
Legal values are:
act
An act in a dramatic text.
advert
An advertisement for a printed work or other product.
argument
A short passage at the start of a document or section giving a prose description of its contents.
book
A major structural component of a long work, identified explicitly in the text as a ‘book’.
calendar
A formal calendar; a document or document section identifying itself as a calendar
castlist
A list of characters in a dramatic text
chapter
A chapter, typically in a prose document
colophon
A short inscription, typically at the end of a book or manuscript, containing the title, printer, date and place of printing, etc.
concluding
Any section of the back matter that does not carry a more specific designation; includes afterwords, epilogues, codas, etc.
confession
A section that is identified explicitly as a ‘confession’ in a text that uses this as a main structural division.
contents
A table of contents.
corrigenda
A section describing corrections to be made to the document.
ded
A dedication.
dialogue
A section that is identified explicitly as a ‘dialogue’ in a text that uses this as a main structural division.
docAuthorization
A statement indicating that the document's printing was officially authorized.
drama
A dramatic text.
dramaPart
A portion of a drama other than a prologue, act, scene, or epilogue.
endnotes
A section containing endnotes for the document.
entry
An entry in a document that is organized as a log or diary with dated entries.
epigraph
A short quotation at the start of a document or section, often accompanied by an attribution.
epilogue
A short concluding section, usually of a dramatic or fictional work.
essay
A short prose non-fiction document.
examination
A section that is identified explicitly as an ‘examination’ in a text that uses this as a main structural division.
frontispiece
A portrait or other image (usually of the author, usually full page) printed at the front of a document.
imprimatur
A formal indication (usually on the title page or in the front matter) that the document has received official license to be printed.
index
An alphabetical listing of the topics in a document, usually with accompanying page references
letter
Any document in epistolary form, i.e. addressed by a sender to a recipient.
meditation
A section that is described explicitly as a ‘meditation’ in a document that uses this as a main structural division.
narrative
An embedded narrative.
nonfictionProse
A text intended to be nonfiction consisting primarily of prose.
novel
A novel.
novelPart
A portion of a novel.
part
A major component of a work, containing further subdivisions.
petition
A formal plea to an authority.
placeholder
A placeholder to provide validity when the encoded portion of the document is not being transcribed, typically because it is out of scope for the WWO collection.
poem
A poem.
poemGroup
A group of two or more poems under a common heading.
prayer
A prayer.
prefatory
A section of the front matter that does not carry a more specific designation.
prologue
An opening section of a literary work (typically drama or poetry).
recipe
A recipe in a cookbook.
scene
A scene in a dramatic text
section
A generic section of a larger work.
speech
A section described as a speech or public lecture, in a document that uses this as a main structural division.
subsection
A generic subdivision of a section.
timeline
A timeline.
tract
A short treatise in pamphlet form often on a religious subject.
undetermined
A text component whose genre has not been determined.
vignette
A brief and illustrative prose account, such as an anecdeote or sketch, typically published in a periodical and combining elements of both fact and fiction.
volume
Schematron
<sch:rule context="wwp:body[@type]"> <sch:assert test="@type = ('act', 'confession', 'dialogue', 'drama', 'dramaPart', 'essay', 'examination', 'letter', 'meditation', 'narrative', 'nonfictionProse', 'novel', 'novelPart', 'petition', 'poem', 'poemGroup', 'prayer', 'speech', 'tract', 'undetermined')">warning: the "<sch:value-of select="@type"/>" value of @type is not intended to be used on <body>.</sch:assert> </sch:rule>
Schematron
<sch:rule context="wwp:div[ not( @type ) ]"> <sch:report test="true()">divisions should be catagorized, but this one is not (i.e., @type is required, but is missing here)</sch:report> </sch:rule>
Schematron
<sch:rule context="wwp:div"> <sch:assert test="@type = ('act', 'advert', 'argument', 'book', 'calendar', 'castlist', 'chapter', 'colophon', 'concluding', 'confession', 'contents', 'corrigenda', 'ded', 'dialogue', 'docAuthorization', 'drama', 'endnotes', 'entry', 'epigraph', 'epilogue', 'essay', 'examination', 'frontispiece', 'imprimatur', 'index', 'letter', 'meditation', 'narrative', 'part', 'petition', 'poem', 'poemGroup', 'prayer', 'prefatory', 'prologue', 'recipe', 'scene', 'section', 'speech', 'subsection', 'timeline', 'tract', 'undetermined', 'vignette')">warning: the "<sch:value-of select="@type"/>" value of @type is not intended to be used on <div>.</sch:assert> </sch:rule>

Appendix C.47 att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [15. Tables, Formulæ, Graphics, and Notated Music]
Modulefigures
Memberscell row
Attributes
role(role) indicates the kind of information held in this cell or in each cell of this row.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
label
labelling or descriptive information only.
data
data values.[Default]
Note

When 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.

rows(rows) indicates the number of rows occupied by this cell or row.
StatusOptional
Datatypeteidata.count
Default1
Note

A 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.
StatusOptional
Datatypeteidata.count
Default1
Note

A 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.

Appendix C.48 att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [12.3.1.4. Additions and Deletions]
Moduletei
Membersadd addSpan del delSpan mod redo subst substJoin undo
Attributes
causedocuments the presumed cause for the intervention.
StatusOptional
Datatypeteidata.enumerated
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
StatusOptional
Datatypeteidata.count
Note

The WWP does not use the TEI transcriptional status attribute.

Appendix C.49 att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Moduletagdocs
Membersdesc gloss
Attributes
versionDatespecifies the date on which the source text was extracted and sent to the translator
StatusOptional
Datatypeteidata.temporal.working
Note

The 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.

Appendix C.50 att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
Membersatt.pointing.group[altGrp linkGrp] TEI ab abbr add addSpan alt am anchor bibl biblStruct calendar castItem cb change corr damageSpan date del delSpan desc dimensions distinct elision figure mw g gloss graphic group head ident idno label lb lg line link listBibl mapping measure milestone mod name note num orgName pb persName placeName ptr quote ref reg rs seg spGrp space tag teiCorpus term time title titleBlock titlePart trailer unknown
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div 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>
Note

The 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.

subtype(subtype) provides a sub-categorization of the element, if needed.
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists .

Appendix C.51 att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membersatt.damaged[damageSpan] att.transcriptional[add addSpan del delSpan mod redo subst substJoin undo] ab closer dateline div emph figure mw head hi label line note opener p postscript salute seg signed sp speaker stage text trailer
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

Appendix D Macros

Appendix D.1 macro.abContent

macro.abContent (anonymous block content) defines the content of anonymous block elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
  <elementRef key="ab"/>
 </alternate>
</content>
    
Declaration
ws_macro.abContent = ( text | ws_model.paraPart | ws_ab )*

Appendix D.2 macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
ws_macro.limitedContent = ( text | ws_model.limitedPhrase | ws_model.inter )*

Appendix D.3 macro.noteContent

macro.noteContent 
Modulederived-module-wwp-store
Used by
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
   <sequence minOccurs="1" maxOccurs="1">
    <sequence minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteTop"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.notePart"/>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.noteBottom"/>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </sequence>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="byline"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Declaration
ws_macro.noteContent =
   (
      ws_model.global*,
      (
         ( ( ws_model.noteTop, ws_model.global* )* ),
         (
            ( ( ws_model.notePart, ws_model.global* )+ ),
            ( ( ws_model.noteBottom, ws_model.global* )* )
         )
      )
   )
 | ( ( ws_byline, ws_model.global* )+ )

Appendix D.4 macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
ws_macro.paraContent = ( text | ws_model.paraPart )*

Appendix D.5 macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
ws_macro.phraseSeq =
   (
      text
    | ws_model.gLike
    | ws_model.attributable
    | ws_model.phrase
    | ws_model.global
   )*

Appendix D.6 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. Standard Content Models]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
ws_macro.phraseSeq.limited =
   ( text | ws_model.limitedPhrase | ws_model.global )*

Appendix D.7 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. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
ws_macro.specialPara =
   (
      text
    | ws_model.gLike
    | ws_model.phrase
    | ws_model.inter
    | ws_model.divPart
    | ws_model.global
   )*

Appendix D.8 macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    
Declaration
ws_macro.xtext = ( text | ws_model.gLike )*

Appendix E Datatypes

Appendix E.1 teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
ws_teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty 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.

Appendix E.2 teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
ws_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

Appendix E.3 teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
    
Declaration
ws_teidata.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>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A 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.

Appendix E.4 teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
    
Declaration
ws_teidata.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>
Example
<time dur="PT0.02S">20 ms</time>
Note

A 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.

Appendix E.5 teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei
Used by
teidata.gender teidata.sexElement:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
ws_teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

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.

Appendix E.6 teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
ws_teidata.gender = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 10.3.1. Information on Written and Spoken Forms).

Appendix E.7 teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
ws_teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 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.

language
The 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 https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The 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 https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either 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 searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An 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’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. There are currently only two extensions in use. Extension T indicates that the content was transformed. For example en-t-it could be used for content in English that was translated from Italian. Extension T is described in the informational RFC 6497. Extension U can be used to embed a variety of locale attributes. It is described in the informational RFC 6067.
private use
An 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

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

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

Appendix E.8 teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei
Used by
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
ws_teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

Appendix E.9 teidata.namespace

teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Moduletei
Used by
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
ws_teidata.namespace = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

Appendix E.10 teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
ws_teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any 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.

Appendix E.11 teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
    
Declaration
ws_teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
   }
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="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
Note

These 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.

Appendix E.12 teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"/>
</content>
    
Declaration
ws_teidata.pattern = token
Note
A 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

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

Appendix E.13 teidata.point

teidata.point defines the data type used to express a point in cartesian space.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
    
Declaration
ws_teidata.point =
   token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>  <surface ulx="0uly="0lrx="400lry="280">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png"/>   </zone>  </surface> </facsimile>
Note

A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

Appendix E.14 teidata.pointer

teidata.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.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
ws_teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The 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/

Appendix E.15 teidata.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
ws_teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
Note

This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

Appendix E.16 teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
ws_teidata.probCert = teidata.probability | teidata.certainty

Appendix E.17 teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Moduletei
Used by
teidata.probCertElement:
Content model
<content>
 <dataRef name="double">
  <dataFacet name="minInclusive" value="0"/>
  <dataFacet name="maxInclusive" value="1"/>
 </dataRef>
</content>
    
Declaration
ws_teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

Appendix E.18 teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Moduletei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
ws_teidata.replacement = text

Appendix E.19 teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
ws_teidata.sex = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Appendix E.20 teidata.temporal.iso

teidata.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.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </alternate>
</content>
    
Declaration
ws_teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If 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:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

Appendix E.21 teidata.temporal.w3c

teidata.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 Second Edition specification.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
ws_teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If 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.

Appendix E.22 teidata.temporal.working

teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
  <dataRef name="dateTime"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
 </alternate>
</content>
    
Declaration
ws_teidata.temporal.working =
   xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
 | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
Note

If 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.

The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z.

Appendix E.23 teidata.text

teidata.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.
Moduletei
Used by
Element:
  • distinct/@time
  • distinct/@space
  • distinct/@social
  • gap/@extent
  • include/@xpointer
  • include/@encoding
  • include/@accept
  • include/@accept-charset
  • include/@accept-language
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
ws_teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

Appendix E.24 teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
ws_teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

Appendix E.25 teidata.unboundedCount

teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="nonNegativeInteger"/>
  <valList type="closed">
   <valItem ident="unbounded"/>
  </valList>
 </alternate>
</content>
    
Declaration
ws_teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )

Appendix E.26 teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
ws_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). 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.

Appendix E.27 teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
    
Declaration
ws_teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

Appendix E.28 teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
teidata.enumeratedElement:
Content model
<content rend="replace">
 <dataRef name="token"
  restriction="(\p{L}|\p{N}|\p{P}|\p{S}|⸿)+"/>
</content>
    
Declaration
ws_teidata.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S}|⸿)+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Appendix E.29 teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
    
Declaration
ws_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

Appendix E.30 teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Moduletei
Used by
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Declaration
ws_teidata.xmlName = xsd:NCName
Note

The rules defining an XML name form a part of the XML Specification.

Appendix E.31 teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
ws_teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Appendix E.32 wwpdata.sex

wwpdata.sex Possible values for representation of sex and gender
Modulederived-module-wwp-store
Used by
Element:
Content model
<content> 
 
 malefemalemixedunknowninapplicablefemale-as-malemale-as-female
 
</content>
    
Declaration
ws_wwpdata.sex =
   "male"
 | "female"
 | "mixed"
 | "unknown"
 | "inapplicable"
 | "female-as-male"
 | "male-as-female"
ExampleIn The Matrimonial Trouble by Margaret Cavendish, ‘Mister Disguise’ is the persona adopted by Mistress Forsaken.
<castItem>  <role gender="female-as-male">   <persName>Monſieur Diſguiſe</persName>.</role> </castItem>

Appendix F Constraints

Schematron
<sch:rule context="wwp:teiHeader"> <sch:let name="hdr"  value="substring-before( normalize-space( @xml:id ),'.hdr')"/> <sch:let name="idno"  value="normalize-space( wwp:fileDesc/wwp:publicationStmt/wwp:idno[@type eq 'WWP'] )"/> <sch:let name="textID"  value="normalize-space( ../wwp:text/@xml:id )"/> <sch:let name="sourceDescs"  value="/wwp:TEI/wwp:teiHeader/wwp:fileDesc/wwp:sourceDesc"/> <sch:let name="sourceDesc"  value="$sourceDescs[ not( @default eq 'false') ]"/> <sch:let name="source"  value="normalize-space( $sourceDesc/@n )"/> <sch:assert test="matches( $hdr, '^TR[0-9]{5}(\.[0-9]{2})?$')">TEI Header ID is not in correct format</sch:assert> <sch:assert test="matches( $idno, '^TR[0-9]{5}(\.[0-9]{2})?$')">WWP idno is not in correct format</sch:assert> <sch:assert test="matches( $textID,'^TR[0-9]{5}(\.[0-9]{2})?$')">  <att>xml:id</att> of <gi>text</gi> is not a proper TR number</sch:assert> <sch:assert test="matches( $source,'^OT[0-9]{5}(\.[0-9]{2})?$')">  <att>n</att> of <gi>sourceDesc</gi> is not a proper OT number</sch:assert> <sch:assert test="$idno eq $textID and substring( $idno, 3 ) eq substring( $source, 3 ) and $idno eq $hdr">TR and OT numbers do not all match.</sch:assert> </sch:rule>
Schematron
<sch:rule context="*[ @corresp ]"> <sch:let name="ptr2me"  value="concat('#', @xml:id )"/> <sch:report test="tokenize( normalize-space( @corresp ),' ') = $ptr2me">ERROR: the <sch:value-of select="name()"/> element with id=<sch:value-of select="@xml:id"/> corresponds to itself</sch:report> </sch:rule>
Schematron
<sch:rule context="/*"> <sch:let name="training"  value="contains( base-uri(/), '/training/' )"/> <sch:let name="myfn"  value="tokenize( base-uri(/),'/')[last()]"/> <sch:let name="mybase"  value="replace( $myfn, '\.x(m|inc)l$','')"/> <sch:let name="URLidno"  value="wwp:teiHeader/wwp:fileDesc/wwp:publicationStmt/wwp:idno[@type eq 'URL']"/> <sch:let name="URLidnobase"  value="substring-before( tokenize( $URLidno,'/')[last()],'.html')"/> <sch:let name="svnIDnot"  value="exists( /comment()[contains( ., concat('$','Id','$') ) ] )"/> <sch:let name="SVN"  value="tokenize( normalize-space( /comment()[contains( ., concat('$','Id',':') ) ] ), ' ')"/> <sch:let name="SVNfn" value="$SVN[2]"/> <sch:let name="SVNbase"  value="substring-before( $SVNfn,'.xml')"/> <sch:assert test="$URLidnobase eq $mybase">URL idno "<sch:value-of select="$URLidnobase"/>" does not match filename "<sch:value-of select="$mybase"/>"</sch:assert> <sch:report test="count( $SVN ) eq 0 and not( $svnIDnot )">Subversion 'Id' keyword comment not found</sch:report> <sch:report test="count( $SVN ) eq 0 and $svnIDnot">Subversion 'Id' keyword has not been substituted</sch:report> <sch:assert test="$training or matches( $URLidno,'^https?://www\.wwp\.northeastern\.edu/texts/[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.html$')">URL idno is not in correct format</sch:assert> <sch:assert test="$training or $SVNbase eq $mybase">Subversion 'Id' filename "<sch:value-of select="$SVNbase"/>" does not match actual filename "<sch:value-of select="$mybase"/>" (because myfn=<sch:value-of select="$myfn"/>)</sch:assert> <sch:assert test="$training or $SVNbase eq $URLidnobase">Subversion 'Id' filename "<sch:value-of select="$SVNbase"/>" does not match URL idno "<sch:value-of select="$URLidnobase"/>"</sch:assert> </sch:rule>
Schematron
<sch:pattern id="nest_me_part_not"> <sch:rule context="*[@part][.//@part]">  <sch:let name="myGI" value="name(.)"/>  <sch:let name="descendentGIs"   value=".//*[@part]/name()"/>  <sch:report test="$myGI = $descendentGIs"> This <sch:value-of select="$myGI"/> element has an @part, but also has a descendant <sch:value-of select="$myGI"/> that has an @part. (This is not allowed, use @next &amp; @prev instead.)  </sch:report> </sch:rule> </sch:pattern>
Schematron
<sch:pattern id="LessThan3InitialCharsDropped"> <sch:rule context="*[ matches( @rend,'class\s*\(#DIC\)') ]">  <sch:let name="len"   value="if ( .//wwp:sic | .//wwp:corr ) then max(( string-length( string-join(.//wwp:sic/normalize-space(), '') ), string-length(string-join( .//wwp:corr/normalize-space(), '')) )) else string-length( normalize-space(.) )"/>  <sch:assert test="$len lt 3"> A dropped initial capital is typically only 1 or at    most 2 characters long; this one is <sch:value-of select="$len"/> characters long.  </sch:assert> </sch:rule> </sch:pattern> <sch:pattern id="concrete_rend_keyword_checker"  is-a="abstract_rendition_keyword_checker"> <sch:param name="rendLadderContext"  value="wwp:rendition"/> </sch:pattern> <sch:pattern id="concrete_rendition_keyword_checker"  is-a="abstract_rendition_keyword_checker"> <sch:param name="rendLadderContext"  value="wwp:*/@rend"/> </sch:pattern> <sch:pattern id="abstract_rendition_keyword_checker"  abstract="true"> <sch:rule context="$rendLadderContext">  <sch:let name="me"   value="normalize-space(.)"/>  <sch:let name="myself"   value="replace( replace( $me, ' ?\) ?',')'), ' ?\( ?','(')"/>  <sch:let name="I"   value="replace( replace( $myself,'\\\)','⸩'), '\\\(','⸨')"/>  <sch:let name="we"   value="replace( $I, 'be(stow|queath) \( \(([a-z-]+\([^)]*\))+\) \(([A-Za-z][A-Za-z0-9._-]*[ ]?)+\) \)', '','x')"/>  <sch:let name="us"   value="tokenize( $we, '\([^)]*\)')"/>  <sch:assert test="every $ego in $us satisfies ( $ego = ('align', 'bestow', 'border', 'braced', 'bracing', 'break', 'case', 'columns', 'face', 'fill', 'first-indent', 'indent', 'place', 'pos', 'post', 'pre', 'rotate', 'slant', 'space-above', 'sub', 'sup', 'underline', 'underscore') or $ego = ('', 'class', 'inverted', 'myAnchor', 'right-indent', 'rotate', 'rotate-y') )"> I parsed the <sch:value-of select="if (self::wwp:rendition) then concat('content of <rendition> #', (@xml:id,count( preceding::wwp:rendition)+1)[1]) else concat('@rend of a <', local-name(..),'>' )"/>,    "<sch:value-of select="."/>", into the keywords "<sch:value-of select="for $ego in ($us) return concat('{',$ego,'}')"/>",    at least one of which is not a proper keyword.  </sch:assert> </sch:rule> </sch:pattern>
SchematronReminder: the resulting tests will never fire when used with probatron or other use of the reference implimentation iso_svrl_for_xslt2.xsl, because it outputs a ‘continuation’ <apply-templates> that selects only elements, not all nodes. However, neither oXygen nor mausatron has this problem, so this test does work while editing in oXygen or if you use mausatron (aka SchXslt). Note also that if there are two soft hyphens on one line both the ‘two shy!’ and ‘non-whitespace after shy!’ errors fire.
<sch:rule context="text()[contains(.,'­')]"> <sch:let name="len" value="43"/> <sch:let name="me"  value="normalize-space(.)"/> <sch:let name="ellipsis"  value="if (string-length($me) > $len) then '…' else ''"/> <sch:let name="snippet"  value="concat( substring( $me, 1, $len), $ellipsis )"/> <sch:report test="ancestor::wwp:teiHeader">“<sch:value-of select="$snippet"/>”: shy in metadata!</sch:report> <sch:report test="matches(.,'­.*­')">“<sch:value-of select="$snippet"/>”: two shy!</sch:report> <sch:assert test="matches(.,'­\s*$')">“<sch:value-of select="$snippet"/>”: non-whitespace after shy!</sch:assert> <sch:assert test="following::text()">“<sch:value-of select="$snippet"/>”: nothing follows shy!</sch:assert> </sch:rule>
Syd Bauman. Date: $Id: wwp-store.html 50485 2025-06-09 17:02:29Z aclark $