<?tei:SOF p2vese.odd ?>
<!-- $Id: p2vese.odd,v 1.7 1998/02/01 17:38:08 tei Exp $ -->
<!--*
    * $Log: p2vese.odd,v $
    * Revision 1.7  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.5  1994/03/28  17:10:48  lou
    * fix seg attlist error
    * 
    * Revision 1.4  1994/03/15  10:08:12  lou
    * Typos etc.
    * 
    * Revision 1.3  1993/11/26  18:14:11  msmcq
    * MSM revisions for publication, as published
    * -->
<!-- Revisions:                                               -->
<!-- 11 jan 98 : LB : killed numbered segs pro tem -->
<!-- 93-11-22 : MSM : purely cosmetic                         -->
<!-- 93-11-21 : MSM : accept changes from David Robey         -->
<!-- 93-11-18 : MSM : fix some problems in exx                -->
<!-- 93-11-18 : MSM : Revisions as per LB for clarity         -->
<!-- 93-11-13 : MSM : correct references to SEG               -->
<!-- 93-11-13 : MSM : Added RCS id                            -->
<div2 id="VESE"><head>Components of the Verse Line</head>
 
<p>It is often convenient for various kinds of analysis to encode
subdivisions of verse lines.  The general purpose <gi>seg</gi> element
defined in the tag set for segmentation and alignment (section <xref
target="SASE">) is provided for this purpose:
 
<tagList>
<tagDesc tagDoc="SEG" atts="part">
</tagList></p>
 
<p>To use this element together with the base tag set for verse, the
tag set for segmentation and alignment must also be enabled, by an
additional declaration in the document type subset, as further
described in section <xref target="STIN">.  A document using the base
tag set for verse and this additional tag sets will thus begin as
follows:
 
<eg>
<![ CDATA [
 <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!ENTITY % TEI.verse 'INCLUDE' >
 <!ENTITY % TEI.linking 'INCLUDE' >
 ]>
]]>
</eg></p>

<p>In Old and Middle English alliterative verse, individual verse lines
are typically split into half lines. The <gi>seg</gi> element may be
used to mark these explicitly, as in the following example from
Langland's <title>Piers Plowman</title>:
 
<eg>
<![ CDATA [
<l><seg>In a somer seson,</seg>
   <seg>whan softe was the sonne,</seg></l>
<l><seg>I shoop me into shroudes</seg>
   <seg>as I a sheep were,</seg></l>
<l><seg>In habite as an heremite </seg>
   <seg>unholy of werkes,</seg></l>
<l><seg>Went wide in this world </seg>
   <seg>wondres to here.</seg></l>
<!-- ... -->
]]>
</eg>
<!-- Langland: The Vision of Piers Plowman B-text ed Schmidt --></p>
 
<p>The <gi>seg</gi> element can be nested hierarchically, in the same
way as the <gi>lg</gi> element, down to whatever level of detailed
structure is required.  In the following example, the line has been
divided into <term>feet</term>, each of which has been further
subdivided into into syllables.  (The eccentric formatting ensures that
no spaces are introduced within words unless they are within SGML tags
and thus not significant.)
 
<eg>
<![ CDATA [
   <l><seg type=foot>
         <seg type=syll>Ar</><seg
              type=syll>ma</>
         <seg type=syll>vi</></seg><seg
      type=foot><seg
              type=syll>rum</><seg
              type=syll>que</>
         <seg type=syll>ca</></seg><seg
      type=foot><seg
              type=syll>no</>
         <seg type=syll>Tro</></seg><seg
      type=foot><seg
              type=syll>iae</>
         <seg type=syll>qui</>
      </seg>
      <seg type=foot>
         <seg type=syll>pri</><seg
              type=syll>mus</>
         <seg type=syll>ab</>
      </seg>
      <seg type=foot>
         <seg type=syll>or</><seg
              type=syll>is</>
      </seg>
</l>
]]>
</eg></p>
 
<p>The <gi>seg</gi> element may be used to identify any subcomponent of
a line which has content; its type attribute may characterize such units
in any way appropriate to the needs of the encoder.  For the specific
case of labeling each foot with its formal type (<q>dactyl</q>,
<q>spondee</q>, etc.), and each syllable with its metrical or prosodic
status (syllables bearing primary or secondary stress, long syllables,
short syllables), however, the specialized attributes <att>met</att> and
<att>real</att> are defined, which provide a more systematic framework
than the <att>type</att> attribute; see section <xref target="VEME">
below.</p>
 
<p>In classical verse, a hexameter like that above may also be formally
divided into two <soCalled>hemistiches</soCalled>.  This example
provides an interesting case, in that the boundary of the first
hemistich falls in the middle of one of the feet (between the syllables
<q>no</q> and <q>Tro</q>).  If both kinds of segmentation are required,
the <att>part</att> attribute might be used to mark the overlapping
structure as follows.  (This example uses the slightly artificial
convention that word space is included within the syllable segments, and
all other white space is to be ignored; though convenient for visual
clarity in presentations like this one, this convention is not
recommended for normal use.)
 
<eg><![ CDATA [
   <l><seg type=hemistich>
         <seg type=foot>
           <seg type=syll> Ar</>
           <seg type=syll>ma </>
           <seg type=syll>vi</>
         </seg>
         <seg type=foot>
           <seg type=syll>rum</>
           <seg type=syll>que </>
           <seg type=syll>ca</>
           </seg>
         <seg type=foot part=I>
           <seg type=syll>no </>
         </seg>
      </seg>
      <seg type=hemistich>
         <seg type=foot part=F>
           <seg type=syll>Tro</>
         </seg>
         <seg type=foot>
            <seg type=syll>iae </>
            <seg type=syll>qui </>
         </seg>
      </seg>
   </l>
]]>
</eg>
 
<!-- <p>Numbered <gi>seg</gi> elements may also be used; these have the -->
<!-- disadvantage &mdash; or advantage &mdash; of requiring a -->
<!-- consistent, layer-by-layer analysis, and the advantage of providing a-->
<!-- useful</item> default for the <att>type</att> attribute, which must be-->
<!-- specified only once for each level, as well as allowing the omission-->
<!-- of many end-tags, which makes the presentation more compact.-->
 
<!--   <l><seg1 type=hemistich>-->
<!--          <seg2 type=foot>-->
<!--                <seg3 type=syll> Ar<seg3>ma <seg3>vi</>-->
<!--          <seg2><seg3>rum<seg3>que <seg3>ca</>-->
<!--          <seg2 part=I><seg3>no </>-->
<!--       <seg1>-->
<!--          <seg2 part=F><seg3>Tro</>-->
<!--          <seg2><seg3>iae <seg3>qui </>-->

<!--     </l>-->
<!-- ]]>-->

<!--     </l>-->
  <!-- ... -->
<!-- ]]>-->
<!-- </eg>-->
<!--     < l >  < seg1 type=hemistich >                       -->
<!--           < seg2 type=foot >                             -->
<!--             < seg3 type=syll >  Ar < / >                 -->
<!--             < seg3 > ma  < / >                           -->
<!--             < seg3 > vi < / >                            -->
<!--           < /seg2 >                                      -->
<!--           < seg2 >                                       -->
<!--             < seg3 > rum < / >                           -->
<!--             < seg3 > que  < / >                          -->
<!--             < seg3 > ca < / >                            -->
<!--             < /seg >                                     -->
<!--           < seg2 part=I >                                -->
<!--             < seg3 > no  < / >                           -->
<!--           < /seg >                                       -->
<!--        < /seg >                                          -->
<!--        < seg1 >                                          -->
<!--           < seg2 part=F >                                -->
<!--             < seg3 > Tro < / >                           -->
<!--           < /seg >                                       -->
<!--           < seg2 >                                       -->
<!--             < seg3 > iae  < / >                          -->
<!--             < seg3 > qui  < / >                          -->
<!--           < /seg >                                       -->
<!--    < !    ....    >                                      --></p>
 
<p>Instead of using the <att>part</att> attribute on the <gi>seg</gi>
element, it might be simpler just to mark the point at which the caesura
occurs.  An additional element is provided for analyses of this kind, in
which what is to be marked are points <q>between the words</q>, which
have some significance within a verse line:
 
<tagList>
<tagDesc tagDoc="CAESURA">
</tagList>
 
In classical prosody, the <term>caesura</term>, which occurs within a
foot, is distinguished from a <term>diaeresis</term>, which occurs on a
foot boundary (not to be confused with the division of a diphthong into
two syllables, or the diacritic symbol used to indicate such division,
each of which is also termed <term>diaeresis</term>).  This distinction
is rarely made nowadays, the term <cited>caesura</cited> being used for
any division irrespective of foot boundaries.  No special-purpose <gi
tei="no">diaeresis</gi> element is therefore provided.</p>
 
<p>As an example of the <gi>caesura</gi> element, we refer again to the
example from Langland.  An encoder might choose simply to record the
location of the caesura within each line, rather than encoding each
half-line as a segment in its own right, as follows:
 
<eg>
<![ CDATA [
<l>In a somer seson, <caesura> whan softe was the sonne, </l>
<l>I shoop me into shroudes <caesura> as I a sheep were, </l>
<l>In habite as an heremite <caesura> unholy of werkes, </l>
<l>Went wide in this world <caesura> wondres to here. </l>
]]>
</eg>
<!-- Langland: The Vision of Piers Plowman B-text ed Schmidt --></p>
 
<p>Logically, the opposite of caesura might be considered to be
enjambement.  The base tag set for verse defines an <att>enjamb</att>
attribute for the <gi>l</gi> element, which alllows the presence or
absence of enjambement to be signaled.  The following lines demonstrate
the use of the <att>enjamb</att> attribute to mark places where there is
a discrepancy between the boundaries of the <gi>l</gi> elements and the
syntactic structure of the verse (a discrepancy of some significance in
some schools of verse):
 
<eg>
<![ CDATA [
<l enjamb=y>Un astrologue, un jour, se laissa choir</l>
<l>Au fond d'un puits.
]]>
</eg>
<!-- La Fontaine, somewhere (Larousse) -->
 
<!-- There's no way of constraining enjamb to end of line.    -->
<!-- I think it wd be better as an attribute of l - like      -->
<!-- latching att on u (lb)                                   -->
<!-- I agree, but it seems rather late to change it now.      -->
<!-- But better late than never.  Changed! (msm)              --></p>
 
<p>The elements discussed in this section are formally defined as
follows:
<dtdFrag id="DVESE" n="Caesura" file="teivers2.dtd">
<tagDecl tagDoc="CAESURA">
</dtdFrag>
</p></div2>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
-->
<?tei:EOF p2vese.odd ?>
