<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.10.3 Milestone Elements
Modulecore — 3 Elements Available in All TEI Documents
Attributes att.typed (@type, @subtype)
ed(edition) indicates the edition or version to which the milestone applies.
Status Recommended
Datatype 

<rng:ref name="data.code"/>
data.code
Values Any string of characters; usually a siglum conventionally used for the edition.
unitprovides a conventional name for the kind of section changing at this milestone.
Status Required
Datatype 

<rng:ref name="data.enumerated"/>
data.enumerated
Suggested values include:
page
physical page breaks (synonymous with the pb element).
column
column breaks.
line
line breaks (synonymous with the lb element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
Note
If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next milestone tag for the edition in question is encountered.
In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).
Used by
model.milestoneLike
May containEmpty element
Declaration

<rng:element name="milestone">
<rng:ref name="att.global.attributes"/>
<rng:ref name="att.typed.attributes"/>
<rng:optional>
 <rng:attribute name="ed">
  <rng:ref name="data.code"/>
 </rng:attribute>
</rng:optional>
<rng:attribute name="unit">
 <rng:choice>
  <rng:value>page</rng:value>
  <rng:value>column</rng:value>
  <rng:value>line</rng:value>
  <rng:value>book</rng:value>
  <rng:value>poem</rng:value>
  <rng:value>canto</rng:value>
  <rng:value>speaker</rng:value>
  <rng:value>stanza</rng:value>
  <rng:value>act</rng:value>
  <rng:value>scene</rng:value>
  <rng:value>section</rng:value>
  <rng:value>absent</rng:value>
  <rng:value>unnumbered</rng:value>
  <rng:data type="Name"/>
 </rng:choice>
</rng:attribute>
<rng:empty/>
</rng:element>
element milestone
{
   att.global.attributes,
   att.typed.attributes,
   attribute ed { data.code }?,
   attribute unit
   {
      "page"
    | "column"
    | "line"
    | "book"
    | "poem"
    | "canto"
    | "speaker"
    | "stanza"
    | "act"
    | "scene"
    | "section"
    | "absent"
    | "unnumbered"
    | xsd:Name
   },
   empty
}
Example
<milestone n="23" ed="La" unit="Dreissiger"/>
...
<milestone n="24" ed="AV" unit="verse"/>
...
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.