<locus> defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references. [10.3.5 References to Locations within a Manuscript]
Modulemsdescription — Manuscript Description
Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate)
schemeidentifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource.
Status Optional
Datatype teidata.pointer
fromspecifies the starting point of the location in a normalized form, typically a page number.
Status Optional
Datatype teidata.word
tospecifies the end-point of the location in a normalized form, typically as a page number.
Status Optional
Datatype teidata.word
Member of
Contained by
analysis: cl phr s span
figures: cell figDesc
iso-fs: fDescr fsDescr
linking: ab seg
spoken: u writing
tagdocs: eg valDesc
verse: metSym rhyme
May contain
gaiji: g
character data

The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the first example above. To associate a locus element with a page image or other comparable representation, the global facs attribute should be used instead, as shown in the second example. Use of the target attribute to indicate an image is strongly deprecated. The facs attribute may be used to indicate one or more image files, as above, or alternatively it may point to one or more appropriate XML elements, such as the surface, zone element, graphic, or binaryObject elements.


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


<!-- within ms description --><msItem n="1">
 <locus target="#F1r #F1v #F2rfrom="1r"
ff. 1r-2r</locus>
 <author>Ben Jonson</author>
 <title>Ode to himself</title>
 <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
 <incipit>Com leaue the loathed stage</incipit>
 <explicit>And see his chariot triumph ore his wayne.</explicit>
  <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
<!-- within transcription ... -->
<pb xml:id="F1r"/>
<!-- ... -->
<pb xml:id="F1v"/>
<!-- ... -->
<pb xml:id="F2r"/>
<!-- ... -->

The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:

 <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
Content model
 <macroRef key="macro.xtext"/>
Schema Declaration
<rng:element name="locus">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.rendition.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.global.responsibility.attributes"/>
 <rng:ref name="att.global.source.attributes"/>
 <rng:ref name="att.pointing.attributes"/>
  <rng:attribute name="scheme">
   <rng:ref name="teidata.pointer"/>
  <rng:attribute name="from">
   <rng:ref name="teidata.word"/>
  <rng:attribute name="to">
   <rng:ref name="teidata.word"/>
 <rng:ref name="macro.xtext"/>
element locus
   attribute scheme { teidata.pointer }?,
   attribute from { teidata.word }?,
   attribute to { teidata.word }?,