<?tei:SOF p2cors.odd ?>
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- $Id: p2cors.odd,v 1.10 1998/01/30 16:41:14 tei Exp $ -->
<!--*
    * $Log: p2cors.odd,v $
    * Revision 1.10  1998/01/30 16:41:14  tei
    * Fix log format.
    *
    * Revision 1.9  1998/01/30 15:54:50  tei
    * more eg typos
    * 
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.7  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.6  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * 
    * Revision 1.5  1994/02/17  20:31:08  msmcq
    * revision for SC review
    *-->
<!-- P2COrs : Reference Systems                               -->
<!-- Revisions:                                               -->
<!-- 10 jan 98 : LB : fix egs -->
<!-- 94-04-07 : MSM : trivial typos                           -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-26 : MSM : typos from JL et al.                    -->
<!-- 94-02-17 : MSM : Added RCS id                            -->
<!-- 94-02-15 : MSM : supply missing /eg                      -->
<!-- 25 dec 93: LB: change milestone tags; add exx.           -->
<!-- 92-12-09 : MSM : correct two typos, one important        -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-07 : MSM : revise for publication                  -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 19 Oct 92 : LB some stylistic changes                    -->
<!-- 1 oct 92 : LB : change IDs to new scheme                 -->
<!-- 14 May 92 : CMSMcQ : assign numeric IDs to sections.     -->
<!-- 29-30 Apr 92 : CMSMcQ : reorder, revise somewhat.        -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2.                   -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0 (z69, sec. 5.6)  -->
<!-- Mar-Apr 89 : EM : drafted                                -->
 
<div2 id=CORS><head>Reference Systems</head>
 
<p>By <cited>reference system</cited> we mean the system by which names
or references are associated with particular passages of a text (e.g.
<cited>Ps. 23:3</cited> for the third verse of Psalm 23 or <cited>Amores
2.10.7</cited> for Ovid's <title>Amores</title>, book 2, poem 10, line
7).  Such names make it possible to mark a place within a text and
enable other readers to find it again.  A reference system may be based
on structural units (chapters, paragraphs, sentences; stanza and verse),
typographic units (page and line numbers), or divisions created
specifically for reference purposes (chapter and verse in Biblical
texts).  Where one exists, the traditional reference system for a text
should be preserved in an electronic transcript of it, if only to make
it easier to compare electronic and non-electronic versions of the text.
 
<p>Reference systems may be recorded in TEI-encoded texts in any of the
following ways:
 
<list type=bullets>
 
<item>where a reference system exists, and is based on the same
logical structure as that of the text's SGML markup, the reference for
a passage may be recorded as the value of the global <att>id</att> or
<att>n</att> attribute on an appropriate tag, or may be constructed by
combining attribute values from several levels of tags, as described
below in section <xref type=div3 target=CORS1>.
 
<item>where there is no pre-existing reference system, the global
<att>id</att> or <att>n</att> attributes may be used to construct one
(e.g. collections and corpora created in electronic form), as described
below in section <xref type=div3 target=CORS2>.
 
<item>where a reference system exists which is not based on the same
logical structure as that of the text's SGML markup, (for example, one
based on the page and line numbers of particular editions of the text
rather than on the structural divisions of it), then a distinct logical
structure representing the reference system may be encoded as a
concurrent markup stream, as described in section <xref target=NHRS>.
 
<item>where a reference system exists which does not correspond to any
particular logical structure, or where the logical structure concerned
is of no interest to the encoder except as a means of supporting the
referencing system, then references may be encoded by means of
<gi>mileStone</gi> elements, which simply mark points in the text at
which values in the reference system change, as described below in
section <xref type=div3 target=CORS5>.
 
</list>
 
The specific method used to record traditional or new reference systems
for a text should be declared in the TEI header, as further described in
section <xref type=div3 target=CORS6> and in chapter <xref target=CR>.
 
<p>When a text has no pre-existing associated reference system of any
kind, these Guidelines recommend as a minimum that at least the page
boundaries of the source text be marked using one of the methods
outlined in this section.  Retaining page breaks in the markup is also
recommended for texts which have a detailed reference system of their
own.  Line breaks in prose texts may be, but need not be, tagged.
<note place=foot>
Many encoders find it convenient to retain the line breaks of
the original during data entry, to simplify proof-reading,
but this may be done without inserting a tag for each line
break of the original.
<!-- For further discussion of tagging for pagination,        -->
<!-- lineation, and other physical characteristics of the     -->
<!-- copy text, see chapter <xref type=div1 target=PH >.      -->
</note>
 
<div3 id=CORS1><head>Using the ID and N Attributes</head>
 
<p>When traditional reference schemes represent a hierarchical
structuring of the text which mirrors that of the SGML document, the
<att>n</att> attribute defined for all elements may be used to indicate
the traditional identifier of the relevant structural units.  The
<att>n</att> attribute may also be used to record the numbering of
sections or list items in the copy text if the copy-text numbering is
important for some reason, for example because the numbers are out of
sequence.
 
<p>For example, a traditional reference to Ovid's <title>Amores</title>
might be <cited>Amores 2.10.7</cited>---book 2, poem 10, line 7. Book,
poem, and line are structural units of the work and will therefore be
tagged in any case.  (See chapter <xref type=div1 target=VE> for a
discussion of structural units in verse collections.)  In such cases, it
is convenient to record traditional reference numbers of the structural
units using the <att>n</att> attribute.  The relevant tags for our
example would be:
 
<eg>
<![ CDATA [
<div0 n=Amores type=volume>
    <div1 n='2' type=book>
         <div2 n='10' type=poem>
              <l n='7'> ...
]]>
</eg>
 
<p>One may also place the entire standard reference for each portion of
the text into the appropriate value for the <att>n</att> attribute,
though for obvious reasons this takes more space in the file:
 
<eg>
<![ CDATA [
<div0 n=Amores type=volume>
    <div1 n='Amores 2' type=book>
         <div2 n='Amores 2.10' type=poem>
              <l n='Amores 2.10.7'> ...
]]>
</eg>
 
<p>If the names used by the traditional reference system can be
formulated as SGML identifiers, then the references can be given as
values for the <att>id</att> attribute; this requires that the reference
be given without internal spaces, begin with a letter, and contain no
characters other than letters, digits, hyphens, and full
stops.<note place=foot>
The legal form of identifiers depends in part on the SGML
declaration.  With appropriate modifications in the declaration,
other characters may be made legal in identifiers; this is allowed
though not encouraged in TEI-conformant documents.
</note>
Unlike values for the <att>n</att> attribute, values for the
<att>id</att> attribute must be unique throughout the document.
Our example then looks like this:
 
<eg>
<![ CDATA [
<div0 id=AMORES type=volume>
    <div1 id='AM.2' type=book>
         <div2 id='AM.2.10' type=poem>
              <l id='AM.2.10.7'> ...
]]>
</eg>
 
<p>To document the usage and to allow automatic processing of these
standard references, it is recommended that the TEI header be used to
declare whether standard references are recorded in the <att>n</att> or
<att>id</att> attributes and which elements may carry standard
references or portions of them.  For examples of declarations for the
reference systems just shown, see section <xref type=div3 target=CORS6>.
 
<p>Using the <att>n</att> attribute one can specify only a single
standard referencing system, a limitation not without problems, since
some editions may define structural units differently and thus create
alternative reference systems.  For example, another edition of the
<title>Amores</title> considers poem 10 a continuation of poem 9, and
therefore would specify the same line as <cited>Amores 2.9.31</cited>.
In order to record both of these reference systems, one must either use
the <att>id</att> or <att>n</att> attribute for one, with competing
systems in concurrent markup hierarchies, as discussed below in section
<xref type=div3 target=NHRS>, or else use the <gi>mileStone</gi> tags
described in section <xref type=div1 target=CORS5>.
 
<div3 id=CORS2><head>Creating New Reference Systems</head>
 
<p>If a text has no canonical reference system of its own, a reference
system, if needed, may be derived from the structure of the electronic
text, specifically from the SGML markup of the text.  As with any
reference system intended for long-term use, it is important to see the
reference as an established, unchanging point in the text.  Should the
text be revised or rearranged, the reference-system identifiers
associated with any bit of text must stay with that bit of text, even if
it means the reference numbers fall out of sequence.  (A new reference
system may always be created beside the old one if out-of-sequence
numbers must be avoided.)
 
<p>The global attributes <att>n</att> and <att>id</att> may be used to
assign reference identifiers to segments of the text.  Identifiers
specified by either attribute apply to the entire element for which they
are given.  SGML enforces uniqueness on ID attributes within a single
document, and ID values must begin with a letter.  No such restrictions
are made on the values of <att>n</att> attributes.
 
<!-- <p>A convenient method of mechanically generating        -->
<!-- unique values for <att>id</att> or <att>n</att>          -->
<!-- attributes, based on the SGML structure of the document  -->
<!-- is to use the <soCalled>typed path</soCalled> or         -->
<!-- <term>untyped path</term> methods described in section   -->
<!-- <xref type=div1 target=SA> to identify elements within   -->
<!-- the <gi>text</gi> segment of a TEI document.             -->
 
<!-- The discussion referred to no longer exists; following   -->
<!-- paragraphs (through example) added as substitute.        -->
<!-- (msm)                                                    -->
 
<p>A convenient method of mechanically generating unique values for
<att>id</att> or <att>n</att> attributes based on the SGML structure of
the document is to construct, for each element, a <term>domain-style
address</term> comprising a series of components separated by full
stops, with one component for each level of the SGML document hierarchy.
Two methods may be used.  In the <term>typed path</term> form of
identifier, each component in the identifier takes the form <ident
type=var>element-type</ident> <cited>-</cited> <ident
type=var>number</ident>.  The element name specifies what type of
element to be sought, and the number specifies which occurrence of that
element type is to be selected.  (The hyphen and number may be omitted
if there is only one element of the given type.)  In the <term>untyped
path</term> form of identifier, each component consists of a number,
indicating which element in the sequence of nodes at each level is to be
selected.  A fixed prefix beginning with a letter may be used to make
the untyped path legal as an SGML <code type=kw>ID</code> value.
 
<p>Identifiers generated with these methods should use the <gi>text</gi>
element as their starting point, rather than the <gi>tei.2</gi> or
<gi>body</gi> elements. The <gi>tei.2</gi> element may be taken
as a starting point only if identifiers need to be generated for the
<gi>teiHeader</gi>, which is not usually the case;  using the
<gi>body</gi> element as a root would prevent assignment of identifiers
for the front and back matter.  The component corresponding to the root
element can be omitted from identifiers, if no confusion will result.
In collections and corpora, the component corresponding to the root may
be replaced by the unique identifier assigned to the text or sample.
 
<p>In the following example, each element within the <gi>text</gi>
element has been given a typed-path identifier as its <att>id</att>
value, and an untyped-path identifier as its <att>n</att> value; the
latter are prefixed with the string <cited>AB</cited>, which may be
imagined to be the general identifier for this text.
 
<eg>
<![ CDATA [
   <text id='TEXT-1' n='AB'>
     <front id='FRONT' n='AB.1'>
       <div       id='FRONT.div-1'     n='AB.1.1'><p> ... </div>
       <titlePage id='FRONT.titlePage' n='AB.1.2'>
                 <titlePart> ... </titlePart>       </titlePage>
       <div       id='FRONT.div-2'     n='AB.1.3'><p> ... </div>
     </front>
     <body id='BODY' n='AB.2'>
       <p id='BODY.p-1' n='AB.2.1'> ... </p>
       <p id='BODY.p-1' n='AB.2.2'> ... </p>
       <div id='BODY.div-1' n='AB.2.3'>
         <head id='BODY.div-1.head' n='AB.2.3.1'> ... </head>
         <p    id='BODY.div-1.p-1'  n='AB.2.3.2'> ... </p>
         <p    id='BODY.div-1.p-2'  n='AB.2.3.3'> ... </p>
         </div>
       <div id='BODY.div-2' n='AB.2.4'>
         <head id='BODY.div-2.head' n='AB.2.4.1'> ... </head>
         <p    id='BODY.div-2.p-1'  n='AB.2.4.2'> ... </p>
         <p    id='BODY.div-2.p-2'  n='AB.2.4.3'> ... </p>
         </div>
     </body>
  </text>
]]>
</eg>
 
 
The typed and untyped path methods are convenient, but are in no way
required for anyone creating a reference system.
 
<p>If the <att>id</att> attribute is used to record the reference
identifiers generated, each value should record the entire path.  If the
<att>n</att> attribute is used, each value may record either the entire
path or only the subpath from the SGML parent element.  The attribute
used, the elements which can bear standard reference identifiers, and
the method for constructing standard reference identifiers, should all
be declared in the header as described in section <xref target=HD54>.
 
<p>When the hierarchy of the SGML-encoded document and that of the
reference system differ (e.g. for reference systems based on page and
line numbers) or when more than one reference system is to be encoded,
the encoder may choose to represent the alternative reference system(s)
as elements in one or more concurrent document hierarchies.  For an
introduction to the concept of concurrent hierarchies, see the
discussion of the <code type=kw>CONCUR</code> feature in section <xref
type=div1 target=SG152>.  For further discussion of this and other
mechanisms, see chapter <xref target=NH>.
 
<div3 id=CORS5><head>Milestone Tags</head>
 
<p>If concurrent markup is not desired (e.g. because the available SGML
parser does not support the CONCUR feature), or if the desired reference
system does not correspond to any particular structural hierarchy, it
may be more convenient to mark up changes in the reference system by using
one or more of the following <term>milestone</term> elements:
 
<tagList>
<tagDesc tagDoc=MILEST  atts='ed n unit'>
<tagDesc tagDoc=PAGEBR atts='ed n'>
<tagDesc tagDoc=LINEBR atts='ed n'>
<tagDesc tagDoc=COLBR atts='ed n'>
</tagList>
 
<p>These elements simply mark the points in a text at which some
category in a reference system changes.  They have no content but
subdivide the text into regions, rather in the same way as milestones
divide a road into segments.  The elements <gi>pb</gi>, <gi>cb</gi>,
and <gi>lb</gi> are provided to mark specific types of milestone,
namely page, column, and line boundaries, as further described in
chapter <xref type=div1 target=PH>.  No SGML validation of a reference
system based on <gi>mileStone</gi> tags is possible, so it will be the
responsibility of the encoder or the application software to ensure
that milestone tags occur in a correct order.
 
<p>Milestone tags may be useful where a text has two competing
structures. For example, many English novels were first published as
serial works, individual parts of which do not always contain a whole
number of chapters. An encoder may decide to represent the
chapter-based  structure using <gi>div1</gi> elements, with
<gi>mileStone</gi> elements to mark the points at which individual
parts end; or the reverse. Thus, an encoding in which chapters are
regarded as more important than parts might encode some work in which
chapter three begins in part one and is concluded in part two as
follows:
 
<eg rend=skel>
<![ CDATA [
<text><body>
  <mileStone unit=part>
  <div1 n=1 type=chapter>
  <!-- text of chapter 1 here -->
  </div1>
  <div1 n=2 type=chapter>
  <!-- text of chapter 2 here -->
  </div1>
  <div1 n=3>
  <!-- part of text of chapter 3 here -->
  <mileStone unit=part>
  <!-- remainder of text of chapter 3 here -->.
  </div1>
</body></text>
]]>
</eg>
 
An encoding of the same work in which parts are regarded as more
important than chapters might begin as follows:
 
<eg> <![ CDATA [
<text><body>
  <div1 n=1 type=part>
  <mileStone unit=chapter>
  <p><!-- text of chapter 1 here -->
  <mileStone unit=chapter>
  <p><!-- text of chapter 2 here -->
  <mileStone unit=chapter>
  <p><!-- part of text of chapter 3 here -->
  </div1><div1 n=2 type=part>
  <p><!-- remainder of text of chapter 3 here -->
  <mileStone unit=chapter>
  <!-- ... -->
</body></text>
]]>
</eg>
 
<p>Milestone tags also make it possible to record the reference systems
used in a number of different editions of the same work. The reference
system of any one edition can be recreated from a text in which all are
marked by simply ignoring all elements that do not specify that edition
on their <att>ed</att> attribute.
 
<p>As a simple example, assuming that edition E1 of some collection of
poems regards the first two poems as constituting the first book, while
edition E2 regards the first poem as prefatory, a markup scheme like
the following might be adopted:
 
<eg>
<![ CDATA [
 
 <mileStone ed=E1 unit=work>
 <mileStone ed=E2 unit=work>
 <mileStone ed=E1 unit=book>
 <mileStone ed=E1 unit=poem>
 <mileStone ed=E2 unit=poem>
  <!-- text of first poem here -->
 <mileStone ed=E2 unit=book>
 <mileStone ed=E1 unit=poem>
 <mileStone ed=E2 unit=poem>
  <!-- text of second poem here -->
 
]]>
</eg>
 
<p>In this case no <att>n</att> value is specified, since the numbers
rise predictably and the application can keep a count from the start of
the document, if desired.
 
<p>The value of the <att>n</att> attribute may but need not include the
identifiers used for any larger sections.  That is, either of the
following styles is legitimate:
<eg>
<![CDATA[
 <mileStone ed=E1 unit=work n='Amores'>
 <mileStone ed=E1 unit=book n=1>
 <mileStone ed=E1 unit=poem n=1>
  <!-- text of Amores 1.1 -->
 <mileStone ed=E1 unit=poem n=2>
  <!-- text of Amores 1.2 -->
 <mileStone ed=E1 unit=book n=3>
]]>
</eg>
or
<eg>
<![CDATA[
 <mileStone ed=E1 unit=work n='Amores'>
 <mileStone ed=E1 unit=book n=1>
 <mileStone ed=E1 unit=poem n='1.1'>
 <!-- text of Amores 1.1 -->
 <mileStone ed=E1 unit=poem n='1.2'>
  <!-- text of Amores 1.2 -->
 <mileStone ed=E1 unit=book n='1.3'>
]]>
</eg>
 
<p>
When using <gi>mileStone</gi> tags, line numbers may be supplied for
every line or only periodically (every fifth, every tenth line).  The
latter may be simpler; the former is more reliable.
 
<p>The style of numbering used in the values of <att>n</att> is
unrestricted:  for the example above, <code type=val>I.i</code>, <code
type=val>I.ii</code>, and <code type=val>I.iii</code> could have been
used equally well if preferred.  The special value <code
type=val>unnumbered</code> should be reserved for marking sections of
text which fall outside the normal numbering system (e.g. chapter heads,
poem numbers, titles, or speaker attributions in a verse drama).
 
<!-- dropped second reference pace Eynsham -->
<!-- p>No automatic validation of any hierarchical ordering   -->
<!-- can be defined for the various types of <                -->
<!-- gi>milestone</ gi> tag; it is the encoder's              -->
<!-- responsibility to ensure that milestone values are       -->
<!-- valid.                                                   -->
 
<p>Because the <att>ed</att> attribute is unrestricted, no change need be
made to the document type declaration of a file before adding tags to
describe a new reference system.  (The value of <att>ed</att> may be
restricted to a defined set of edition symbols by using the techniques
described in chapter <xref type=div1 target=MD>.)
 
<p>See below, section <xref type=div3 target=CORS6>, for examples of
declarations for the reference systems just shown.
 
<p>The milestone elements are formally defined
as follows:
<!--  tag has the following formal declaration: -->
<dtdFrag id=DCORSM n='Milestone tags'>
<tagDecl tagDoc=MILEST>
<tagDecl tagDoc=PAGEBR>
<tagDecl tagDoc=LINEBR>
<tagDecl tagDoc=COLBR>
</dtdFrag>
 
<div3 id=CORS6><head>Declaring Reference Systems</head>
 
<p>Whatever kind of reference system is used in an electronic text, it
is recommended that the TEI header contain a description of its
construction in the <gi>refsDecl</gi> element described in section <xref
type=div3 target=HD54>.  As described there, the declaration may consist
either of a formal declaration using the <gi>step</gi> tag or an
informal description in prose.  The former is recommended because unlike
prose it can be processed by software.
 
<p>The three examples given in section <xref type=div3 target=CORS1>
would be declared as follows.  The first example encodes the standard
references for Ovid's <title>Amores</title> one level at a time, using
the <att>n</att> attribute on the <gi>div0</gi>, <gi>div1</gi>,
<gi>div2</gi>, and <gi>l</gi> tags.  The header for such an encoding
should look something like this:
 
<eg rend=skel>
<![ CDATA [
<teiHeader>
    <fileDesc> ...
    </fileDesc>
    <encodingDesc>
         ...
         <refsDecl>
              <step refunit='work' delim=' '
                    from='DESCENDANT (1 DIV0 N %1)' to='DITTO' >
              <step refunit='book' delim='.'
                    from='CHILD (1 DIV1 N %1)' to='DITTO' >
              <step refunit='poem' delim='.'
                    from='CHILD (1 DIV2 N %1)' to='DITTO' >
              <step refunit='line'
                    from='CHILD (1 L N %1)' to='DITTO' >
         </refsDecl>
         ...
    </encodingDesc>
</teiHeader>
]]>
</eg>
 
<p>The second example encodes the same reference system, again using the
<att>n</att> attribute on the <gi>div0</gi>, <gi>div1</gi>,
<gi>div2</gi>, and <gi>l</gi> tags, but giving the reference string in
full on each tag.  If canonical references are made only to lines, the
reference system could be declared as follows:
 
<eg>
<![ CDATA [
 <refsDecl>
   <step refunit='line'
         from='DESCENDANT (1 L N %1)' to='DITTO' >
 </refsDecl>
]]>
</eg>
 
Since no delimiter is specified, the entire canonical reference string
is sought as the value of the <att>n</att> attribute on an <gi>l</gi>
element.
 
<p>In order to handle references to works, books, and poems as well as
to individual lines, the declaration for the reference system must be
more complicated:
 
<eg>
<![ CDATA [
 <refsDecl>
   <step from='DESCENDANT (1 (DIV[012]|L) N %1)' to='DITTO' >
 </refsDecl>
]]>
</eg>
 
This declaration indicates that the entire reference string must be
sought as the value of the <att>n</att> attribute on a <gi>div0</gi>,
<gi>div1</gi>, <gi>div2</gi>, or <gi>l</gi> element.
 
<p>The third example encodes the same reference system, this time giving
the entire reference string as the value of the <att>id</att> attribute
on the relevant tags.  The reference system declaration for such an
encoding would be:
 
<eg>
<![ CDATA [
<refsDecl>
    <step from="ID (%1)" to="DITTO">
</refsDecl>
]]>
</eg>
 
<p>As in the previous example, no single value can be given for the
<att>refunit</att> attribute in this declaration, as the single step
handles references to works, books, and poems, as well as to lines.  The
<att>type</att> attribute on the <gi>div0</gi>, <gi>div1</gi>, and
<gi>div2</gi> elements may be used, however, to indicate the type of the
result returned from a match.
 
<!-- , or the declaration can be expanded:                    -->
<!--                                                          -->
<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <refsDecl>                                               -->
<!--     <step refunit='work' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='book' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='poem' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='line' from="ID (%1)" to="DITTO">      -->
<!-- </refsDecl>                                              -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->
 
<p>Reference systems recorded by means of milestone tags can also be
declared; the following prose description could be used to declare
the example given in section <xref type=div3 target=CORS5>.
 
<eg>
<![ CDATA [
<refsDecl>
    <p>Standard references to work, book, poem, and line may be
    constructed from the Milestone tags in the text.
</refsDecl>
]]>
</eg>
 
Or in this way, using a formal declaration for this reference scheme
derived from edition <code type=value>E1</code>.
 
<eg>
<![ CDATA [
<refsDecl>
    <state delim=' ' unit=work ed='E1'>
    <state delim='.' unit=book ed='E1'>
    <state delim=':' unit=poem ed='E1'>
    <state unit=line ed='E1'>
</refsDecl>
]]>
</eg>
 
<p>This is synonymous with the following declaration using the
<gi>step</gi> element:
 
<eg>
<![ CDATA [
<refsDecl>
    <step refunit='work' delim=' '
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT work N %1)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT work)' >
    <step refunit='book' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT book N %2)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT book)' >
    <step refunit='poem' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT poem N %3)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT poem)' >
    <step refunit='line'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT line N %4)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT line)' >
</refsDecl>
]]>
</eg>
 
<!-- JL:  question for P4:  can we specify the edition in     -->
<!-- some way as a parameter?                                 -->
<?tei:EOF p2cors.odd ?>
