<!-- $Id: p2dr.odd,v 1.11 1998/02/01 16:18:53 tei Exp $ -->
<!--*
    * $Log: p2dr.odd,v $
    * Revision 1.11  1998/02/01 16:18:53  tei
    * change system to public identifier (again)
    *
    * Revision 1.10  1998/01/31 19:50:52  tei
    * Change system 'tei2.dtd' to public identifier
    * fix log keyword (if not already fixed)
    * normalize the sgml
    *
    * Revision 1.9  94/04/01  16:20:38  msmcq
    * Changes to class declarations and teistr reference
    * -->
<!-- Revisions:                                               -->
<!-- 94-03-31 : MSM : protect teistr                          -->
<!-- 94-03-31 : MSM : define drmix                            -->
<!-- 94-03-30 : MSM : suppress declaration of perf cla (=comp.drama) -->
<!-- 94-03-29 : MSM : declare comp.drama                      -->
<!-- 93-08-20 : MSM : cosmetology                             -->
<!-- 93-08-19 : MSM : add def and ref to teistr               -->
<!-- 93-08-19 : MSM : add class stagedir                      -->
<!-- 93-08-16 : MSM : cosmetic fixes                          -->
<!-- 93-08-16 : MSM : suppress ref to dDRcast                 -->
<!-- 93-06-03 : MSM : add refs to div2 elements               -->
<!-- 21 May : replaced this file from P2X version     -->
<!-- 2 May 93 : rewrote section on front; splitup       -->
<!-- 28 Apr 93: further changes following discussion w JL -->
<!--          speech -> sp                  -->
<!--          removed section on header for now         -->
<!-- 18 jan: checked IDs and reformat -->

<div1 id="DR" n="10"><head>Base Tag Set for Drama</head>

<p>This base tag set is intended for use when encoding printed dramatic
texts, screen plays or radio scripts, and written transcriptions of any
form of performance.

<!-- Because its chief focus is on the high level structural  -->
<!-- features of such texts, the spoken text base tag set     -->
<!-- described in chapter < xref target=TS > may be more      -->
<!-- appropriate if an encoder wishes to focus on the         -->
<!-- temporal and speech based aspects of a dramatic          -->
<!-- performance.                                             --></p>

<p>Section <ptr target="DRfab"> discusses elements, such as cast lists,
which can appear only in the front or back matter of printed dramatic
texts.  Section <ptr target="DRbod"> discusses the structural
components of performance texts: these include major structural
divisions such as acts or scenes (section <ptr target="DRdiv">);
individual speeches (section <ptr target="DRsp">); stage directions
(section <ptr target="DRsta">); and the elements making up individual
speeches (section <ptr target="DRpal">).  Section <ptr target="DRemb">
discusses ways of encoding units which cross the simple hierarchic
structure so far defined, such as embedded songs or other masques.
Finally, section <ptr target="DRoth"> discusses a small number of
additional elements characteristic of screen plays and radio or
television scripts, as well as some elements for representing
technical stage directions such as lighting or blocking.</p>

 <p>To enable the base tag set for performance texts, the parameter
entity <term>TEI.drama</term> must be declared within the document
type subset with the value <code lang="sgml">INCLUDE</code>, as further
described in section <ptr target="STin">.  A document using the base
tag set for drama and no 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.drama 'INCLUDE' >
]>
]]>
</eg>

This declaration makes available all of the elements described in this
chapter, in addition to the core elements described in chapter <ptr
target="CO">.  The default structure for dramatic texts is similar to that
defined by chapter <ptr target="DS">, as further discussed in section
<ptr target="DRdiv">.</p>

<p>Three additional element classes are defined by this base tag set.
The <term>dramafront</term> class contains elements which can
appear only in the front or back matter of performance texts.
The <term>stageDirection</term> class contains a set of elements
for specialized stage directions, which can occur between or within
speeches.
The <term>comp.drama</term> class contains all elements which may appear
as components of performance texts, in addition to those defined in the
core.
The classes are defined using parameter entities as shown below:

<eg id=ddrcla>
<![ CDATA [
<!-- 10:  Class declarations for Performance Texts            -->
<!ENTITY % x.dramafront ''                                      >
<!ENTITY % m.dramafront '%x.dramafront castList | epilogue | 
           performance | prologue | set'                        >
<!ENTITY % x.stageDirection ''                                  >
<!ENTITY % m.stageDirection '%x.stageDirection camera | caption 
           | move | sound | tech | view'                        >
<!ENTITY % x.comp.drama ''                                      >
<!ENTITY % m.comp.drama '%x.comp.drama %m.stageDirection; | 
           castList'                                            >
<!ENTITY % mix.drama '| %m.comp.drama'                          >
]]>
</eg>

<!-- <cladecl type=model classdoc=perf>                       -->

The remainder of the DTD fragment defining the base tag set for drama
has the following overall shape:

<eg id=ddr>
<![ CDATA [
<!-- 10:  Base tag set for Performance texts                  -->
<!-- ... declarations from section 10.1                       -->
<!--  (Specialized front and back matter for performance      -->
<!-- texts)                                                   -->
<!--     go here ...                                          -->
<!-- ... declarations from section 10.2.3                     -->
<!--     (Stage directions)                                   -->
<!--     go here ...                                          -->
<!-- ... declarations from section 10.3.1                     -->
<!--     (Screen plays and other technical matters)           -->
<!--     go here ...                                          -->

<!-- The base tag set for drama uses the standard default     -->
<!-- text-structure elements, which are embedded here:        -->


<![ %TEI.singleBase [
<!ENTITY % TEI.structure.dtd system 'teistr2.dtd'               >
%TEI.structure.dtd;
]]&nil;>

]]>
</eg>

</p>

<!--* $Id: p2drfab.odd,v 1.10 1998/01/28 11:44:14 cmsmcq Exp $ *-->
<!--*
    * $Log: p2drfab.odd,v $
# Revision 1.10  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *-->
<!-- Revisions:                                               -->
<!-- 11 jan 98 : LB : tidy up egs -->
<!-- 93-08-20 : MSM : cosmetics                               -->
<!-- 93-08-19 : MSM : clean Peer Gynt title page (typo)       -->
<!--                  (and titlePart missing)                 -->
<!--                  close date in Godot performance element -->
<!-- 93-08-16 : MSM : last-minute tweaks                      -->
<!-- 93-08-16 : MSM : clean ID problem on dDRcast             -->
<div2 type=section id=DRfab><head>Front and Back Matter

<p>In dramatic texts, as in all TEI conformant documents, the header
element is followed by a <gi>text</gi> element, which contains optional
front and back matter, and either a <gi>body</gi> or else a
<gi>group</gi> of nested <gi>text</gi> elements.  For more information
on these, see chapter <ptr target="DS">.

<p>The <gi>front</gi> and <gi>back</gi> elements are most likely to be
of use when encoding preliminary materials in published performance
texts.  These often contain specific textual elements not generally
found in other forms of text.  These include:

<list type=gloss>
<label><gi>performance</gi></label>
<item>contains a section of front or back matter describing how a
dramatic piece is to be performed in general or how it was 
performed
on some specific occasion. </item>
<label><gi>prologue</gi></label>
<item>contains the prologue to a drama,  typically spoken by an 
actor out of
character, possibly in association with a 
particular performance or venue.</item>
<label><gi>epilogue</gi></label>
<item>contains the epilogue to a drama,  typically spoken by an 
actor
out of character, possibly in association with a 
particular performance
or venue.</item>
<label><gi>set</gi></label>
<item>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).</item>
<label><gi>castList</gi></label>
<item>contains a single cast list or dramatis personae.</item>
</list>


<p>Elements for encoding each of these specific kinds of front matter
are discussed in the remainder of this section, in the order given
above.  In addition, the front matter of dramatic texts may include the
same elements as that of any other kind of text, notably title pages and
various kinds of text division, as discussed in section
<ptr target=Dsfront>.  The encoder may choose to ignore the
specialized elements discussed in this section and instead use
constructions of the type <tag>div type=performance</tag> or
<tag>div1 type=set</tag>.

<p>Most other material in the front matter of a performance text will be
marked with the default text structure elements described in chapter
<ptr target=DS>.  For example, the title
page, dedication, other commendatory material, preface, etc., in a
printed text should be encoded using <gi>div</gi> or <gi>div1</gi>
elements, containing headings, paragraphs, and other core tags.

<p>The specialized elements for front and back matter of performance
texts are defined as follows:

<eg id=ddrfab>
<![ CDATA [
<!-- 10.1: Specialized front and back matter for performance  -->
<!-- texts                                                    -->
<!-- ... declarations from section 10.1.1                     -->
<!--     (The Set element)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 10.1.2                     -->
<!--     (Prologues and Epilogues)                            -->
<!--     go here ...                                          -->
<!-- ... declarations from section 10.1.3                     -->
<!--     (The Performance element)                            -->
<!--     go here ...                                          -->
<!-- ... declarations from section 10.1.4                     -->
<!--     (The cast list)                                      -->
<!--     go here ...                                          -->
<!-- This fragment is used in sec. 10                         -->
]]>
</eg>


<div3 type=subsection id=DRset><head>The Set Element</head>

<p>A special form of note describing the setting of a dramatic text
(that is, the time and place of its action) is sometimes found in the
front matter.

<list type=gloss>
<label><gi>set</gi></label>
<item>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).</item>
</list>


Descriptions of the setting may also appear as initial stage directions
in the body of the play, but such descriptions should be marked as stage
directions, not <gi>set</gi>.  The <gi>set</gi> element should be used
only where the description forms part of the front matter, as in the
following examples:

<eg>
<![ CDATA[
<front>
  <castList>
   <castItem>  <!-- ... --> </castItem>
  </castList>
  <set>The action of the play is set in Chicago's
       Southside, sometime between World War II and the
       present.</set>
</front>
]]>
</eg>

<eg rend=skel>
<![ CDATA [
<front>
  <titlePage> ... </titlePage>
  <div type='copyright page'> ... </div>
  <div type='Contents'> ... </div>
  <div type='Introduction'> ... </div>
  <div type=''><head>Note on the Translation</head> <!--...--> </div>
  <titlePage type='half-title'>
  <docTitle><titlePart>Peer Gynt</></docTitle>
  </titlePage>
  <div type='Dramatis Personae'><head>Characters</> <!--...--> </div>
  <set>The action, which opens in the early years of the
       last century and closes about fifty years later,
       takes place partly in the Gudbrand Valley in Norway
       and on the mountains around it, partly on the
       Moroccan coast, partly in the Sahara Desert,
       the asylum in Cairo, at sea, etc.</set>
   <performance> <!-- ...  --> </performance>
</front>
]]>
</eg>

<p>The <gi>set</gi> element is formally defined as follows:

<eg id=ddrset>
<![ CDATA [
<!-- 10.1.1:  The Set element                                 -->
<!ELEMENT set           - -  (head?, %specialPara)              >
<!ATTLIST set                %a.global;                         >
<!-- This fragment is used in sec. 10.1                       -->
]]>
</eg>


<div3 type=subsection id=DRpro><head>Prologues and Epilogues</head>

<p>Many plays in the Western tradition include in their front matter a
prologue, spoken by an actor, generally not in character.  Similar
speeches often also occur at the end of the play, as epilogues.  The
elements <gi>prologue</gi> and <gi>epilogue</gi> are provided for the
encoding of such features within the front or back matter, where
appropriate.

<list type=gloss>
<label><gi>prologue</gi></label>
<item>contains the prologue to a drama,  typically spoken by an 
actor out of
character, possibly in association with a 
particular performance or venue.</item>
<label><gi>epilogue</gi></label>
<item>contains the epilogue to a drama,  typically spoken by an 
actor
out of character, possibly in association with a 
particular performance
or venue.</item>
</list>


A prologue may be encoded just like a distinct poem, as in the following
example:

<eg>
<![ CDATA[
<front>
<prologue>
<head>Prologue, spoken by <name>Mr. Hart</name></head>
<l>Poets like Cudgel'd Bullys, never do
<l>At first, or second blow, submit to you;
<l>But will provoke you still, and ne're have done,
<l>Till you are weary first, with laying on:
<!-- ... -->
<l>We patiently you see, give up to you,
<l>Our Poets, Virgins, nay our Matrons too.
</prologue>
<castlist>
<head>The Persons</head>
   <castItem>  <!-- ... --> </castItem>
</castlist>
<set><head>The SCENE</>
London</set>
</front>
]]>
</eg>
<!-- Wycherley, Country Wife, 1675 -->

<p>A prologue or epilogue may also be encoded as a speech, using the
<gi>sp</gi> element described in section <ptr target=COdr>.  This is
particularly appropriate where stage directions, etc., are involved, as
in the following example:

<eg><![ CDATA[
<epilogue>
<head>Written by <name>Colley Cibber, Esq</name>
and spoken by <name>Mrs. Cibber</name></head>
<sp>
<lg type=stanza>
<l>Since Fate has robb'd me of the hapless Youth,</l>
<l>For whom my heart had hoarded up its truth;</l>
<l>By all the Laws of Love and Honour, now,</l>
<l>I'm free again to chuse, &mdash; and one of you</l>
</lg>
<!-- ... -->
<lg>
<l>Suppose I search the sober Gallery; &mdash; No,</l>
<l>There's none but Prentices &mdash; &amp; Cuckolds all a row:</l>
<l>And these, I doubt, are those that make 'em so.</l></lg>
<stage>Pointing to the Boxes.</stage>
<lg>
<l>'Tis very well, enjoy the jest:</l>
<!-- ... -->
</sp>
</epilogue>
]]>
</eg>
<!-- G. Lillo, The London Merchant  (1731) -->

<p>In cases where the prologue or epilogue is clearly a significant part
of the dramatic action, it may be preferable to include it in the body
of a text, rather than in the front or back matter.  In such cases, the
encoder (and theatrical tradition) will determine whether or not to
regard it as a new scene or division, or simply the final speech in the
play.  In the First Folio version of Shakespeare's
<title>Tempest</title>, for example, Prospero's final speech is clearly
marked off as a distinct textual unit by the headings and layout of the
page, and might therefore be encoded as back matter:

<eg>
<![ CDATA [
<body>
<div1 type=scene>
<!-- ... -->
<sp who=PR>
<l part=y>I'le deliver all,</l>
<l>And promise you calme Seas, auspicious gales,</l>
<!-- ... -->
<l>Be free and fare thou well: please you, draw neere.</l>
<stage>Exeunt omnes.</stage>
</div1>
</body>
<back>
<epilogue>
<head>Epilogue, spoken by Prospero.</head>
<sp>
<l>Now my Charmes are all ore-throwne,</l>
<l>And what strength I have's mine owne</l>
<!-- ... -->
<l>As you from crimes would pardon'd be,</l>
<l>Let your Indulgence set me free.</l></sp>
<stage>Exit</stage>
</epilogue>

<set>The Scene, an un-inhabited Island.</set>

<castList>
<head>Names of the Actors.</head>
<castitem>Alonso, K. of Naples</castItem>
<castItem>Sebastian, his Brother.</castItem>
<castItem>Prospero, the right Duke of Millaine.</castItem>
<!-- ... -->
</castList>
<!-- <trailer>FINIS</trailer> -->
</back>

]]>
</eg>
<!-- The Tempest, first folio -->

<p>In many more modern editions, the editors have chosen to regard
Prospero's speech as a part of the preceding scene:

<eg>
<![ CDATA [
<sp who=PR><speaker>Prospero</speaker>
<l part=y>I'll deliver all,</l>
<l>And promise you calm seas, auspicious gales,</l>
<!-- ... -->
<l>Be free and fare thou well. <stage>Exit Ariel</stage>
Please you, draw near.
<stage>Exeunt all but Prospero</stage>
<note place=margin>Epilogue</note></l>
<l>Now my charms are all o'erthrown,</l>
<l>And what strength I have's mine own</l>
<!-- ... -->
<l>As you from crimes would pardoned be,</l>
<l>Let your indulgence set me free.</l>
</sp>
<stage>He awaits applause, then exit.</stage>
]]>
<!-- Wells and Taylor OUP 1986 -->
</eg>
<!-- In nearly every example I have looked at, the prologue -->
<!-- precedes the dramatis personae.   (LB) -->

<p>Prologues and epilogues are formally defined as follows:

<eg id=ddrpro>
<![ CDATA [
<!-- 10.1.2:  Prologues and Epilogues                         -->
<!ELEMENT prologue      - -  ((%m.divtop)*, (%component)+, 
                             (%m.divbot)*)                      >
<!ATTLIST prologue           %a.global;                         >
<!ELEMENT epilogue      - -  ((%m.divtop)*, (%component)+, 
                             (%m.divbot)*)                      >
<!ATTLIST epilogue           %a.global;                         >
<!-- This fragment is used in sec. 10.1                       -->
]]>
</eg>


<div3 type=subsection id=DRperf><head>Records of Performances</head>

<p>Performance texts are not only printed in books to be read, they are
also performed.  It is common practice therefore to include within the
front matter of a printed dramatic text some brief account of particular
performances, using the following element:

<list type=gloss>
<label><gi>performance</gi></label>
<item>contains a section of front or back matter describing how a
dramatic piece is to be performed in general or how it was 
performed
on some specific occasion. </item>
</list>


The <gi>performance</gi> element may be used to group any and all
information relating to the actual performance of a play or screenplay,
whether it specifies how the play should be performed in general or how
it was performed in practice on some occasion.

<p>Performance information may include complex structures such as cast
lists, or paragraphs describing the date and location of a performance,
details about the setting portrayed in the performance and so forth.
(See the discussion of these specialized structures in section <ptr
target=DRfab> above.)  If
information for more than one performance is being recorded, then more
than one <gi>performance</gi> element should be used.

<p>Names of persons, places, and dates of particular significance within
the performance record may be explicitly marked using the general
purpose <gi>name</gi>, <tag>rs type=place</tag> and <gi>date</gi>
elements described in section <ptr target=COnada>.
<!-- ; the more detailed tagging for names and dates defined by -->
<!-- chapter  <ptr target=ND> may also be employed. -->
No particular elements for such features as theatres,
directors, etc., are proposed at this time.

<p>For example:

<eg>
<![ CDATA [
<performance>
<head>Death of a Salesman</head>
<p>A New Play by Arthur Miller</>
<p>Staged by Elia Kazan</>
<castList>
<head>Cast</head>
<note place='inline' rend='small type flush left'>
(in order of appearance)
</note>
<castItem><role>Willy Loman</> <actor>Lee J. Cobb</></>
<castItem><role>Linda</>       <actor>Mildred Dunnock</></>
<castItem><role>Biff</>        <actor>Arthur Kennedy</></>
<castItem><role>Happy</>       <actor>Cameron Mitchell</></>
<!-- ... -->
</castList>
<p>The setting and lighting were designed by <name>Jo Mielziner</>.
<p>The incidental music was composed by <name>Alex North</>.
<p>The costumes were designed by <name>Julia Sze</>.
<p>Presented by <name rend=unmarked>Kermit Bloomgarden</> and
<name rend=unmarked>Walter Fried</> at the <rs type=place>Morosco
Theatre in New York</> on <date>February 10, 1949</>.
</performance>
]]>
</eg>
<!-- N.B. first two 'p' elements might also be BYLINE?        -->
<!-- NOTE could be part of title (but is clearly marked by    -->
<!-- typography as distinct segment ...)                      -->
<!-- Last series of P elements could be LIST TYPE=SIMPLE      -->
<!-- -msm                                                     -->

Or:

<eg>
<![ CDATA[
<performance>
<p>La Machine Infernale a &eacute;t&eacute;
repr&eacute;sent&eacute;e pour la premi&egrave;re fois au
<rs type='place (theatre)'>th&eacute;&acirc;tre Louis-Jouvet</rs>
<rs type='place (theatre)'>(Com&eacute;die des
Champs-&Eacute;lys&eacute;es)</rs>
<date>le 10 avril 1934</date>,
avec les d&eacute;cors et les costumes de
<name>Christian B&eacute;rard.</name>
<!-- ... -->
</performance>
]]>
</eg>
<!-- La Machine Infernale, Jean Cocteau -->

<p>The <gi>performance</gi> element is formally defined as follows:

<eg id=ddrperf>
<![ CDATA [
<!-- 10.1.3:  The Performance element                         -->
<!ELEMENT performance   - -  ((%m.divtop)*, (%component)+, 
                             (%m.divbot)*)                      >
<!ATTLIST performance        %a.global;                         >
<!-- This fragment is used in sec. 10.1                       -->
]]>
</eg>


<div3 type=subsection id=DRcast><head>Cast Lists</head>

<p>A <term>cast list</term> is a specialized form of list,
conventionally found at the start or end of a play, usually listing all
the speaking and non-speaking roles in the play, often with additional
description (<q>Cataplasma, a maker of Periwigges and Attires</q>) or
the name of an actor or actress (<q>Old Lady Squeamish. Mrs
Rutter</q>).  Cast lists may be encoded with the general purpose
<gi>list</gi> element described in section <ptr target=COli>, but for
more detailed work the following specialized elements are provided:

<list type=gloss>
<label><gi>castList</gi></label>
<item>contains a single cast list or dramatis personae.</item>
<label><gi>castGroup</gi></label>
<item>groups one or more individual <gi>castItem</gi>
elements 
within a cast list.</item>
<label><gi>castItem</gi></label>
<item>contains a single entry within a cast list, describing

either a single role or a list of non-speaking roles.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>characterizes the cast item.
Sample values include:
<list type=gloss>
<label><term>role</term></label>
<item>the item describes a single role.</item>
<label><term>list</term></label>
<item>the item describes a list of non-speaking roles.</item>
</list></item>
</list>
</item>
<label><gi>role</gi></label>
<item>the name of a dramatic role, as given in a cast list.</item>
<label><gi>roleDesc</gi></label>
<item>describes a character's role in a drama.</item>
<label><gi>actor</gi></label>
<item>Name of an actor appearing within a cast list.</item>
</list>


Cast lists often have an internal structure of their own; it is quite
usual to find, for example, nobility and commoners, or male and female
roles, presented in different groups or sublists.  Roles are also often
grouped together by their function, for example:

<list type=simple>
<item>Sons of Cato:
<list type=simple>
<item>Portius
<item>Marcus
</list>
</list>

<p>A cast list relating to a specific performance may be accompanied by
notes about the time or place of that performance, indicating (for
example) the name of the theatre where the play was first presented, the
name of the producer or director, and so forth.  When the cast list
relates to a specific performance, it should be embedded within a
<gi>performance</gi> element (see section <ptr target=DRperf>), as in
the following example:

<eg>
<![ CDATA[
<performance>
  <p>The first performance in Great Britain of <title>Waiting for
Godot</title> was given at the Arts Theatre, London, on
<date>3rd August 1955</>. It was directed by <name>Peter Hall</name>,
and the d&eacute;cor was by <name>Peter Snow</name>. The cast
was as follows:</p>
<castList>
   <castItem>Estragon: Peter Woodthorpe
   <castItem>Vladimir: Paul Daneman
   <!--   ... -->
  </castList>
</performance>
]]>
</eg>
<!-- S Beckett, W for G, Faber, 1956 -->

<p>In this example, the <gi>castItem</gi> elements have no substructure.
If desired, however, their components may be more finely distinguished
using the elements <gi>role</gi>, <gi>roleDesc</gi>, and <gi>actor</gi>.
For example, the first cast item above might be encoded as follows:

<eg>
<![ CDATA[
   <castItem>
     <role id=VLAD>Vladimir</role>:
     <actor>Paul Daneman</actor>
   </castItem>
]]>
</eg>

<p>The global <att>id</att> attribute may be used to specify a unique
identifier for the <gi>role</gi> element, where it is desired to link
speeches within the text explicitly to the role, using the
<att>who</att> attribute, as further discussed in section <ptr
target=DRsp> below.

<p>The occasionally lengthy descriptions of a role sometimes found in
written play scripts may be marked using the <gi>roleDesc</gi> element,
as in the following example:

<eg>
<![ CDATA[
 <castItem>
 <role>Tom Thumb the Great</role>
 <roleDesc>a little hero with a great soul, something
  violent in his temper, which is a little abated
  by his love for Huncamunca</roleDesc>
 <actor>Young Verhuyk</actor>
 </castItem>
]]>
</eg>
<!-- Fielding, Tragedy of Tragedies (1737) -->

For non-speaking or un-named roles, a <gi>castItem</gi> may contain a
<gi>roleDesc</gi> without an accompanying <gi>role</gi>, for example

<eg>
<![ CDATA[
 <castItem>
  <roleDesc>Costermonger</roleDesc>
 </castItem>
]]>
</eg>

<p>When a list of such minor roles is given together, the
<att>type</att> attribute of the <gi>castItem</gi> should indicate that
it contains more than one role.  The encoder may or may not elect to
encode each separate constituent within such a composite
<gi>castItem</gi>.  Thus, either of the following is acceptable:

<eg>
<![ CDATA[
  <castItem type=list>Constables, Drawer, Turnkey,  etc.</castItem>

  <castItem type=list>
     <roleDesc>Constables,</roleDesc>
     <roleDesc>Drawer,</roleDesc>
     <roleDesc>Turnkey,</roleDesc>
     etc.
   </castItem>
]]>
</eg>

<p>A group of cast items forming a distinct subdivision of a cast list
may be marked as such by using the special purpose <gi>castGroup</gi>
element.  The <att>rend</att> attribute should be used to indicate
whether this grouping is indicated in the text by layout alone (i.e. the
use of whitespace), by long braces or by some other means.  A
<gi>castGroup</gi> consists of an optional heading (represented as
usual by a <gi>head</gi> element) followed by a series of
<gi>castItem</gi> elements.

<eg>
<![ CDATA[
 <castGroup rend=braced><head>friends of Mathias</head>
    <castItem>
        <role>Walter</role><actor>Mr Frank Hall</actor>
    </castItem>
    <castItem>
       <role>Hans</role><actor>Mr F.W. Irish</actor>
    </castItem>
 </castGroup>
]]>
</eg>
<!-- Leopold Lewis, The Bells (1871) -->

<p>The following example demonstrates the use of the <gi>castGroup</gi>
element to structure the whole of a <gi>castList</gi>, reflecting the
way it is presented on the page:

<eg>
<![ CDATA[
<castList>
<castGroup>
  <head rend=braced>Mendicants</head>
  <castItem><role>Aafaa</>   <actor>Femi Johnson</></>
  <castItem><role>Blindman</><actor>Femi Osofisan</></>
  <castItem><role>Goyi</>    <actor>Wale Ogunyemi</></>
  <castItem><role>Cripple</> <actor>Tunji Oyelana</></>
</castGroup>
<castItem><role>Si Bero</>
          <roleDesc>Sister to Dr Bero</>
          <actor>Deolo Adedoyin</></>
<castGroup>
  <head rend=braced>Two old women</head>
  <castItem><role>Iya Agba</><actor>Nguba Agolia</></>
  <castItem><role>Iya Mate</><actor>Bopo George</></>
</castGroup>
<castItem><role>Dr Bero</>
          <roleDesc>Specialist</>
          <actor>Nat Okoro</></>
<castItem><role>Priest</>
          <actor>Gbenga Sonuga</></>
<castItem><role>The old man</>
          <roleDesc>Bero's father</>
          <actor>Dapo Adelugba</></>
</castlist>
]]>
</eg>
<!-- Soyinka, Madmen and Specialists, Methuen 1971 -->

<p>The <gi>castList</gi> element and its components have the following
formal definitions:

<eg id=ddrcast>
<![ CDATA [
<!-- 10.1.4:  The cast list                                   -->
<!ELEMENT castList      - -  ((%m.divtop)*, (%component)*, 
                             (castItem | castGroup)+, 
                             (%component)*)                     >
<!ATTLIST castList           %a.global;                         >
<!ELEMENT castGroup     - -  (head?, (castItem | castGroup)+, 
                             trailer?)                          >
<!ATTLIST castGroup          %a.global;                         >
<!ELEMENT castItem      - O  (role | roleDesc | actor | 
                             (%phrase.seq))*                    >
<!ATTLIST castItem           %a.global;
          type               (role | list)       role           >
<!ELEMENT role          - O  (%phrase.seq)                      >
<!ATTLIST role               %a.global;                         >
<!ELEMENT roleDesc      - -  (%phrase.seq)                      >
<!ATTLIST roleDesc           %a.global;                         >
<!ELEMENT actor         - O  (%phrase.seq)                      >
<!ATTLIST actor              %a.global;                         >
<!-- This fragment is used in sec. 10.1                       -->
]]>
</eg>

<!-- $Id: p2drbod.odd,v 1.13 1998/02/01 16:18:53 tei Exp $ -->
<!--*
    * $Log: p2drbod.odd,v $
    * Revision 1.13  1998/02/01 16:18:53  tei
    * change system to public identifier (again)
    *
    * Revision 1.12  1998/01/31 19:50:52  tei
    * Change system 'tei2.dtd' to public identifier
    * fix log keyword (if not already fixed)
    * normalize the sgml
    *
    * Revision 1.11  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.10  1994/03/07  15:36:11  lou
    * remove ^Z
    *
    * Revision 1.9  1994/03/07  14:50:48  lou
    * fix typos noted by DTB
    *
    * Revision 1.8  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * -->
<!-- Revisions:                                               -->
<!-- 11 jan 98 : LB : fix egs -->
<!-- 9 jan: remove spurious <moves> element -->
<!-- 93-08-20 : MSM : correct bad typo (no tagc on tagdesc for l) -->
<!-- 93-08-20 : MSM : which caused lg desc to be omitted      -->
<!-- 93-08-20 : MSM : also cosmetic changes                   -->
<!-- 93-08-19 : MSM : suppress dot in qu., oph. WHO atts      -->
<!--                  suppress end-tags of L inside Q         -->
<!--                  (quick hack for mixed content problem)  -->
<!--                  add explicit end-tag p in O'Casey       -->
<!-- 93-08-19 : MSM : comment out ellipsis in Barnardo        -->
<!--                  change tagging in O'Casey examples      -->
<!-- 93-08-18 : MSM : cast list must contain cast items, not roles -->
<!-- 93-08-16 : MSM : last-minute tweaks                      -->
<!-- 93-06-02 : WP : Spellchecked, added ATT around "next".   -->

<div2 id="DRbod" type="section"><head>The Body of a Performance Text</head>

<p>The body of a performance text may be divided into structural units,
variously called acts, scenes, stasima, entr'actes, etc.  All such
formal divisions should be encoded using an appropriate text-division
element (<gi>div</gi>, <gi>div1</gi>, <gi>div2</gi>, etc.), as further


discussed in section <ptr target="DRdiv">.  Whether divided up into such
units or not, all performance texts consist of sequences of speeches
(see <ptr target="DRsp">) and stage directions (see <ptr
target="DRsta">).
Speeches will generally consist of a sequence of
<term>chunk</term>-level items:  paragraphs, verse lines, stanzas, or
(in case of uncertainty as to whether something is verse or prose)
<gi>seg</gi> elements (see <ptr target="DRpal">).</p>

<p>The boundaries of formal units such as verse lines or paragraphs do
not always coincide with speech boundaries.  Units such as songs may be
discontinuous or shared among several speakers.  As described below in
section <ptr target="DRemb">, such fragmentation may be encoded in a
relatively simple fashion using the linkage and aggregation mechanisms
defined in chapter <ptr target="SA">.</p>

<div3 id="DRdiv" type="subsection"><head>Major Structural Divisions</head>

<p>Large divisions in drama such as acts, scenes, stasima, or entr'actes
are indicated by numbered or unnumbered <gi>div</gi> elements, as
described in section <ptr target="DSdiv">.  The <att>type</att> and
<att>n</att> attributes may be used to define the type of division being
marked, and to provide a name or number for it, as in the following
example:

<eg>
<![ CDATA[
  <body>
    <div1 type=scene n=1>
      <head>Night&mdash;Faust's Study (i)</head>
      <!-- ... -->
    </div1>
    <div1 type=scene n=2>
      <head>Outside the City Gate</head>
      <!-- ... -->
    </div1>
  </body>
]]>
</eg>
<!-- Goethe, Faust Part 1. Penguin, 1949 --></p>

<p>Where the largest divisions of a performance text are themselves
subdivided, most obviously in the case of plays traditionally divided
into acts and scenes, further nested text-division elements may be used,
as in this example:

<eg>
<![ CDATA[
<body>
  <div1 type=act n=1>
     <head>Act One</head>
     <div2 type=scene n='1'>
       <stage>Pa Ubu, Ma Ubu</stage>
       <sp><speaker>Pa Ubu</speaker><p>Pschitt!</p>
       <!-- ... -->
     </div2>
     <div2 type=scene n=2>
        <stage>A room in Pa Ubu's house, where a magnificent
        collation is set out</stage>
        <!-- ... -->
     </div2>
     <!-- ... -->
  </div1>
  <div1 type=act n=2>
    <head>Act Two</head>
    <div2 type=scene n=1>
      <head>Scene One</head>
      <!-- ... -->
    </div2>
    <div2 type=scene n=2>
      <head>Scene Two</head>
      <!-- ... -->
    </div2>
 </div1>
 <!-- ... -->
 </body>
]]>
</eg>
<!-- Jarry, Ubu Plays (trans C. Connolly & S Watson-Taylor, Methuen 1968 --></p>

<p>In the example above, the <gi>div2</gi> element has been used to
represent the <socalled>French scene</socalled> convention, (where the
entrance of each new set of characters is marked as a distinct unit in
the text) and the <gi>div1</gi> element to represent the acts into which
the play is divided.  The elements chosen are determined only by the
hierarchic position of these units in the text as a whole.  If the text
had no acts, but only scenes, then the scenes might be represented by
<gi>div1</gi> elements.  Equally, if a play is divided only into
<q>acts</q>, with no smaller subdivisions, then the <gi>div1</gi>
element might be used to represent acts.  The <att>type</att> should be
used, as above, where it is desired to make explicit the name associated
with a particular category of subdivision.</p>

<p>As an alternative to the use of these <socalled>numbered</socalled>
divisions, the encoder may represent all subdivisions with the same
element, the <socalled>unnumbered</socalled> <gi>div</gi>.  The second
act in the above example would then be represented as follows:

<eg>
<![ CDATA [
  <div type=act n=2>
    <head>Act Two</head>
    <div type=scene n=1>
      <head>Scene One</head>
      <!-- ... -->
    </div>
    <div type=scene n=2>
      <head>Scene Two</head>
      <!-- ... -->
    </div>
 </div>
]]>
</eg></p>

<p>For further discussion of the use of numbered and unnumbered
divisions, see section <ptr target="DSdiv">.</p></div3>

<div3 id="DRsp" type="subsection"><head>Speeches and Speakers</head>

<p>The following elements are used to identify speeches and speakers in
a performance text:

<list type=gloss>
<label><gi>sp</gi></label>
<item>An individual speech in a performance text, or a passage

presented as such in a prose or verse text.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>identifies the speaker of the part by supplying an ID.</item>
</list>
</item>
<label><gi>speaker</gi></label>
<item>A specialized form of heading or label, giving the name of

one or more speakers in a dramatic text or fragment.</item>
</list>
</p>

<p>As noted above, the structure of many performance texts may be
analysed as multiply hierarchic:  a scene of a verse play, for example,
may be divided into speeches and, at the same time, into verse lines.
The end of a line may or may not coincide with the end of a speech, and
vice versa.  Other structures, such as songs, may be discontinuous or
split up over several speeches.  For some purposes it will be
appropriate to regard the verse-structure as the fundamental organizing
principle of the text, and for others the speech structure; in some
cases, the choice between the two may be arbitrary.  The discussion in
the remainder of this chapter assumes that it is the speech-based
hierarchy which most prominently determines the structure of performance
texts, but the same mechanisms could be employed to encode a view of a
performance text in which individual speeches were entirely subordinate
to the formal units of prose and verse.  SGML's CONCUR feature also
allows for two (or more) such conflicting hierarchic views to be
presented in a single document.  For more detailed discussion and
examples of alternative treatments of this fundamental issue, refer to
chapter <ptr target="NH">.</p>

<p>The <att>who</att> attribute and the <gi>speaker</gi> element are
both used to indicate the speaker or speakers of a speech, but in rather
different ways.  The <gi>speaker</gi> element is used to encode the word
or phrase actually used within the source text to indicate the speaker:
it may contain any string or prefix, and may be thought of as a highly
specialized form of stage direction.  The value of the <att>who</att>
attribute however is a unique code, probably made up by the transcriber,
which will unambiguously identify the character to whom the speech is
assigned.  To enforce this uniqueness, the base tag set for drama
defines the value of this attribute as IDREFS.  This means that the
codes included in it must correspond with codes which are specified
elsewhere in the document as identifiers for particular elements,
typically the <gi>role</gi> element in the cast list where the character
is named or described, as discussed in <ptr target="DRfab"> above.

<eg><![ CDATA[
<!-- in the front matter ... -->
<castList>
<!-- ... -->
<castItem><role id=M2>Menaechmus</></>
<castItem><role id=Pen>Peniculus</></>
<!-- ... -->
</castList>
<!-- ... -->

<!-- in the text ... -->
<sp who=M2><speaker>Menaechmus</speaker>
  <l>Responde, adulescens, quaeso, quid nomen tibist?</l></sp>
<sp who=Pen><speaker>Peniculus</speaker>
  <l>Etiam derides, quasi nomen non noveris?</l></sp>
<sp who=M2><speaker>Menaechmus</speaker>
  <l>Non edepol ego te, quot sciam, umquam ante hunc diem</l>
  <l>Vidi neque novi; ...</l></sp>
]]>
</eg>
<!-- Plautus, Menaechmi, 498-9  --></p>

<p>If present, a <gi>speaker</gi> element may only appear as the first
part of a <gi>sp</gi> element.  The distinction between the
<gi>speaker</gi> element and the <att>who</att> attribute makes it
possible to encode uniformly characters whose names are not indicated in
a uniform fashion throughout the play, or characters who appear in
disguise, as in the following examples:

<eg>
<![ CDATA[
<castList>
  <!-- ... -->
  <castItem><role id=HH>Henry Higgins</role></castItem>
  <!-- ... -->
</castList>
<!-- ... -->

<!-- in the text ... -->

<sp who="HH">
<speaker>The Notetaker</speaker>
<p><!-- ... -->
</sp>
]]>
</eg>
<!-- GB Shaw, Pygmalion --></p>

<p>If the speaker attributions are completely regular (and may thus be
reconstructed mechanically from the values given for the <att>who</att>
attribute), or are of no interest for the encoder of the text (as might
be the case with editorially supplied attributions in older texts), then
the <gi>speaker</gi> element need not be used; the former example above
then might look like this:

<eg><![ CDATA[
<!-- in the front matter ... -->
<castList>
<castItem><role id=M2>Menaechmus</></>
<castItem><role id=Pen>Peniculus</></>
<!-- ... -->
</castList>
<!-- ... -->

<!-- in the text ... -->
<sp who=M2 ><l>Responde, adulescens, quaeso, quid nomen tibist?</l></sp>
<sp who=Pen><l>Etiam derides, quasi nomen non noveris?</l></sp>
<sp who=M2 ><l>Non edepol ego te, quot sciam, umquam ante hunc diem</l>
            <l>Vidi neque novi; ...</l></sp>
]]>
</eg>
<!-- Plautus, Menaechmi, 498-9  --></p>

<p>More than one IDREF may be listed as value for the <att>who</att>
attribute if the speech is spoken by more than one person, as in the
following example:

<eg>
<![ CDATA[
<stage>Nano and Castrone sing</stage>
<sp who="NAN CAS">
<l>Fools, they are the only nation
<l>Worth men's envy or admiration
<!-- ... -->
]]>
</eg>
<!-- Jonson, Volpone, p.14 --></p>

<p>The <gi>sp</gi> and <gi>speaker</gi> elements are both declared
within the core tag set (see section <ptr target="COdv">).

<!-- so we don't need this DTD frag here -->
<!-- dtdfrag id=dDRsp n="Speeches and Speakers" -->
<!-- tagdecl tagdoc=sp -->
<!-- tagdecl tagdoc=speaker -->
<!-- /dtdfrag --></p></div3>

<div3 id="DRsta" type="subsection"><head>Stage Directions</head>

<p>Both between and within the speeches of a written performance text,
it is normal practice to include a wide variety of descriptive
directions to indicate non-verbal action.  The following elements are
provided to represent these:

<list type=gloss>
<label><gi>stage</gi></label>
<item>contains any kind of stage direction within a dramatic text 
or
fragment.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the kind of stage direction.
Suggested values include:
<list type=gloss>
<label><term>delivery</term></label>
<item>describes how a character speaks.</item>
<label><term>mixed</term></label>
<item>more than one of the above</item>
<label><term>location</term></label>
<item>describes a location.</item>
<label><term>entrance</term></label>
<item>describes an entrance.</item>
<label><term>business</term></label>
<item>describes stage business.</item>
<label><term>exit</term></label>
<item>describes an exit.</item>
<label><term>modifier</term></label>
<item>gives some detail about a character.</item>
<label><term>setting</term></label>
<item>describes a setting.</item>
<label><term>novelistic</term></label>
<item>is a narrative, motivating stage direction.</item>
</list></item>
</list>
</item>
<label><gi>move</gi></label>
<item>marks the actual entrance or exit of one or more characters 
on stage.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>identifies the character or characters performing the 
movement.</item>
<label><att>type</att></label>
<item>characterizes the movement, for example as an entrance or 
exit.
Suggested values include:
<list type=gloss>
<label><term>entrance</term></label>
<item>character is entering the stage.</item>
<label><term>exit</term></label>
<item>character is exiting the stage.</item>
<label><term>onstage</term></label>
<item>character moves on stage</item>
</list></item>
<label><att>where</att></label>
<item>specifies the direction of a stage movement.
Sample values include:
<list type=gloss>
<label><term>L</term></label>
<item>stage left</item>
<label><term>C</term></label>
<item>centre stage</item>
<label><term>R</term></label>
<item>stage right</item>
</list></item>
<label><att>perf</att></label>
<item>identifies the performance or performances in which this 
movement occurred as specified.</item>
</list>
</item>
</list>
</p>

<p>A satisfactory typology of stage directions is difficult to define.
Certain basic types such as <q>entrance</q>, <q>exit</q>,
<q>setting</q>, <q>delivery</q>, are easily identified.  But the list is
not a closed one, and it is not uncommon to mix types within a single
direction.  No closed set of values for the <att>type</att> attribute is
therefore proposed at the present time, though some suggested values are
indicated in the list below, which also indicates the range of
possibilities.

<eg><![ CDATA [
<stage type="setting">The throne descends.</stage>
<stage type="setting">Music</stage>
<stage type="entrance">Enter Husband as being thrown off
       his horse.</stage>
<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="delivery">Aside.</stage>
<stage type="delivery">Not knowing what to say.</stage>
<stage type="costume">Disguised as Ansaldo.</stage>
<stage type="location">At a window.</stage>
<stage type="novelistic">Having had enough, and embarrassed
        for the family.</stage>
]]>
</eg></p>

<p>Where possible, the values used for the <att>type</att> attribute on
<gi>stage</gi> elements should be defined within the <gi>tagUsage</gi>
element of the TEI header (described in section <ptr target="HD57">).
For example:

<eg>
<![ CDATA [
<tagUsage gi=stage>This element is used for all stage directions,
editorial or authorial.  The TYPE attribute on this element takes
one or more of the following values:
<list type=gloss>
<label>setting</>   <item>describes the set</>
<label>blocking</>  <item>describes movement across stage,
position, etc.</>
<label>business</>  <item>describes movement other than blocking</>
<label>delivery</>  <item>describes how the line is said</>
<label>motivation</><item>describes character's emotional state
or through line</>
</list>
]]>
</eg></p>

<p>The <gi>stage</gi> element may appear both between and within
<gi>sp</gi> elements.  It may contain a mixture of phrase level
elements, possibly combined into paragraphs, as in the following
example:

<eg><![ CDATA [
<div1 type=act n=1>
<stage type=setting><p>
Scene. &mdash A room furnished comfortably and
tastefully but not extravagantly ...
The floor is carpeted and a fire burns in the stove.
It is winter.
<p>A bell rings in the hall; shortly afterwards the
door is heard to open. Enter NORA humming a tune ...
</stage>
<sp><speaker>Nora</speaker>
<p>Hide the Christmas Tree carefully, Helen. Be sure the
children do not see it till this evening, when it is
dressed. <stage type=delivery>To the PORTER taking
out her purse</stage> How much?
</sp>
]]>
</eg>
<!-- Ibsen, A Dolls House tr Sharp, EML, 1910 --></p>

<p>The <gi>stage</gi> element may also be used in non-theatrical
texts, to mark sound effects or musical effects, etc., as further
discussed in section <ptr target="DRoth">.</p>

<p>The <gi>move</gi> element is intended to help overcome the fact that
the stage directions of a printed text may often not provide full
information about either the intended or the actual movement of actors
etc. on stage.  It may be used to keep track of entrances and exits in
detail, so as to know which characters are on stage at which time.  Its
attributes permit a relatively formal specification for movements of
characters, using user-defined codes to identify the characters involved
(the <att>who</att> attribute), the direction of the movement
(<att>type</att> attribute), and optionally which part of the stage is
involved (<att>where</att> attribute).  For stage-historical purposes, a
<att>perf</att> attribute is also provided; this allows the recording of
different <gi>move</gi> elements
as taken in different performances of the same text.</p>

<p>The <gi>move</gi> element should be located at the position in the
text where the move is presumed to take place.  This will often coincide
with a stage direction, as in the following simple example:

<eg>
<![ CDATA [
<stage type="entrance">
  <move who=B type="enter">
  Enter Bellafront mad.
</stage>
]]>
</eg></p>

<p>The <gi>move</gi> element can however appear independently of a stage
direction, as in the following example:

<eg>
<![ CDATA [
<sp>
<speaker>Gent.</speaker>
<p>Neither to you, nor any one; having no witness
to confirm my speech. <move who=LM type=enter where=C>
Lo you! here she comes. This is her very guise; and,
upon my life, fast asleep.</p>
]]>
<!-- Macbeth (arden ed) p 143 -->
</eg></p>

<p>The <gi>stage</gi> element is defined by the core TEI tag set (see
section <ptr target="COdv">).  The <gi>move</gi> element is defined as
follows:

<eg id=ddrsta>
<![ CDATA [
<!-- 10.2.3:  Stage directions                                -->
<!-- Stage is defined as part of the core.                    -->

<!ELEMENT move          - O  EMPTY                              >
<!ATTLIST move               %a.global;
          who                IDREFS              #REQUIRED
          where              CDATA               #IMPLIED
          perf               IDREFS              #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 10                         -->
]]>
</eg>
</p></div3>

<div3 id="DRpal" type="subsection"><head>Speech Contents</head>

<p>The actual speeches of a dramatic text may be composed of running
text, which must be formally organized into paragraphs, in the case of
prose (see section <ptr target="COpa">), verse lines or line groups in
that of verse (see section <ptr target="COdv">), or <gi>seg</gi>
elements, in case of doubt as to whether the material should be treated
as verse or prose.  The following elements, all of which are defined in
the core, are available for marking units of prose or verse within
speeches:

<list type=gloss>
<label><gi>p</gi></label>
<item>marks paragraphs in prose.</item>
<label><gi>lb</gi></label>
<item>marks the start of a new (typographic) line in some

edition or version of a text.
Attributes include:
<list type=gloss>
<label><att>n</att></label>
<item>indicates the number or other value associated with the 
line which follows the point of insertion of this 
<gi>lb</gi>.</item>
<label><att>ed</att></label>
<item>indicates the edition or version in which the line break is 
located at this point</item>
</list>
</item>
<label><gi>l</gi></label>
<item>contains a single, possibly incomplete, line of verse.
Attributes include:
<list type=gloss>
<label><att>part</att></label>
<item>specifies whether or not the line is metrically complete.
Legal values are:
<list type=gloss>
<label><term>F</term></label>
<item>the final part of an incomplete line</item>
<label><term>Y</term></label>
<item>the line is metrically incomplete</item>
<label><term>N</term></label>
<item>either the line is complete, or no claim is made as to its 
completeness</item>
<label><term>I</term></label>
<item>the initial part of an incomplete line</item>
<label><term>M</term></label>
<item>a medial part of an incomplete line</item>
</list></item>
</list>
</item>
<label><gi>lg</gi></label>
<item>contains a group of verse lines functioning as a formal 
unit
e.g. a stanza, refrain, verse paragraph, etc.</item>
<label><gi>seg</gi></label>
<item>contains any arbitrary phrase-level unit of text (including
other <gi>seg</gi> elements).</item>
</list>
</p>

<p>As members of the class <term>metrical</term>, the elements <gi>l</gi>
and <gi>lg</gi> share the following attributes:
<list type=gloss>
<label><att>met</att></label>
<item>contains a user-specified encoding for the conventional 
metrical structure of the element.</item>
<label><att>rhyme</att></label>
<item>specifies the rhyme scheme applicable to a group of verse 
lines.</item>
</list>
</p>

<p>As a member of the class <term>divn</term>, the element <gi>lg</gi>
also bears the following attributes:
<list type=gloss>
<label><att>part</att></label>
<item>specifies whether or not the division is fragmented by some 
other structural element, for example a speech which is 
divided between two or more verse stanzas.
Legal values are:
<list type=gloss>
<label><term>F</term></label>
<item>the final part of an incomplete division</item>
<label><term>Y</term></label>
<item>the division is incomplete in some respect</item>
<label><term>N</term></label>
<item>either the division is complete, or no claim is made as to 
its completeness.</item>
<label><term>I</term></label>
<item>the initial part of an incomplete division</item>
<label><term>M</term></label>
<item>a medial part of an incomplete division</item>
</list></item>
<label><att>type</att></label>
<item>specifies a name conventionally used for this level of 
subdivision, e.g. <q>act</q>, <q>volume</q>, <q>book</q>, 
<q>section</q>, <q>canto</q>, etc.</item>
</list>
</p>

<p>In many texts, prose and verse may be inextricably mingled;
particularly in earlier printed texts, prose may be printed as verse or
verse as prose, or it may be impossible to distinguish the two.  In
cases of doubt, an encoder may prefer to tag the dubious material
consistently as verse, to tag it all as prose, to follow the typography
of the source text, or to use the neutral <gi>seg</gi>
element to contain the speech itself.  When this question arises, the
<gi>tagUsage</gi> element in the <gi>encodingDesc</gi> element of the
header should be used to record explicitly what policy has been adopted.</p>

<p>The <att>part</att> attribute of the <gi>l</gi> and <gi>lg</gi>
elements provides one simple way of indicating where the boundaries of a
speech and of a verse line or line group do not coincide.  The encoder
may simply indicate that a line or line group is incomplete by
specifying the value <code>Y</code> or <code>N</code>, as in the following example:

<eg>
<![ CDATA [
<sp who=VOLP>
<!-- ... -->
<l part=Y>Now, now my clients
<l>Begin their visitation! Vulture, kite,
<l>Raven, and gorcrow, all my birds of prey,
<l>That think me turning carcase, now they come:
<l part=Y>I am not for 'em yet.
<stage>Re-enter MOSCA with the gown, etc.</stage>
<l part=Y>How now? the news?
</sp>
]]>
</eg>
<!-- Jonson, Volpone, I.1 177ff (ed Bamborough, p 15) -->
<!-- why not just embed the STAGE in the L? -msm --></p>

<p>Alternatively, where the fragments of the line or line group are
consecutive in the text (though possibly interrupted by stage
directions), the values <code>i</code> (initial), <code>m</code> (medial) and
<code>f</code> (final) may be used:

<!-- or first, medial and last? -->
<eg>
<![ CDATA [
<sp who='Barnardo'> <!-- ... -->
 <l>If you do meet Horatio and Marcellus,</l>
 <l>The rivals of my watch, bid them make haste.</l></sp>
<stage>Enter Horatio and Marcellus.</>
<sp who='Francisco'>
 <l>I think I hear them. &mdash; Stand! Who's there?</l>
<sp who='Horatio'>
 <l part=i>Friends to this ground.</l>
<sp who='Marcellus'>
 <l part=f>And liegemen to the Dane.</l>
<!-- ... -->
]]>
</eg></p>

<p>In dramatic texts, the <gi>lg</gi> or line group element is most
often of use for the encoding of songs and other stanzaic material, as
further discussed in the next section.  Line groups may be fragmented
across speakers in the same way as individual lines, and the same set of
attributes is available to record this fact.  In the following example,
a <gi>lg</gi> element is used to represent one verse of a song, which is
divided between several voices:

<eg>
<![ CDATA [
<stage type=head>Song &mdash Sir Joseph</stage>
<sp who=JOPO>
<lg part=I>
<l>I am the monarch of the sea,
<l>The ruler of the Queen's Navee.
<l>Whose praise Great Britain loudly chants.
</lg></sp>
<sp who=HE><speaker>Cousin Hebe</speaker>
<lg part=M>
<l>And we are his sisters and his cousins and his aunts!
</lg></sp>
<sp who=REL><speaker>Rel.</speaker>
<lg part=F>
<l>And we are his sisters and his cousins and his aunts!
</lg></sp>
]]>
</eg>
<!-- W.S. Gilbert: HMS Pinafore p. 11 -->

These elements are all defined in the core, and are thus available to
every TEI document without formality.  A more detailed discussion of the
encoding of verse is provided in chapter <ptr target="VE">.</p></div3>

<div3 id="DRemb" type="subsection"><head>Embedded Structures</head>

<p>Although primarily composed of speeches, performance texts often
contain other structural units such as songs or strophes which are
shared among different speakers.  More generally, complex nested
structures of plays within plays, interpolated masques, or interludes
are far from uncommon.  In more modern material, comparably complex
structural devices such as flashback or nested playback are equally
frequent.  In all kinds of performance material, it may be necessary to
indicate several actions which are happening simultaneously.</p>

<p>A number of different devices are available within the TEI scheme to
support these complexities in the general case.  Texts may be composite
or self-nesting (see section <ptr target="DSgrp">) and multiple
hierarchies may be defined (see chapter <ptr target="NH">).  The TEI
encoding scheme provides a variety of linking mechanisms, which may be
used to indicate temporal alignment and aggregation of fragmented
structures.  In this section we provide a few specific examples of the
application of these techniques to performance texts:

<list type="bullets">
<item>the use of embedded <gi>text</gi> elements</item>
<item>the use of the <att>part</att> attribute on fragmentary
<gi>lg</gi> elements</item>
<item>the use of the <att>next</att> and <att>prev</att> attributes on
fragments of embedded structures to join them into a larger whole</item>
<item>the use of the <gi>join</gi> element to define a
<socalled>virtual element</socalled> composed of the fragments
indicated</item>
</list>

Full information and descriptions are provided in other chapters of this
document, as indicated in the individual discussions.</p>

<p>When a song appears, in its entirety, within a single speech, it may
be treated as an extended quotation or as an embedded <gi>text</gi>
element, or both, according to the preference of the encoder.  In the
following example, an embedded song is treated as a self-standing text:

<eg>
<![ CDATA [
<sp><speaker>Kelly</> <stage>(calmly).</>
  <p>Aha, so you've bad minds along with th' love of gain.
     You thry to pin on others th' dirty decorations that
     may be hangin' on your own coats.
  <stage>(He points, one after the other at Conroy, Bull,
     and Flagonson.  Lilting):</>
  <q><text><body>
     <l>Who were you with last night?</l>
     <l>Who were you with last night?</l>
     <l>Will you tell your missus when you go home</l>
     <l>Who you were with last night?</l>
  </body></text></q></p></sp>
<sp><speaker>Flagonson</> <stage>(in anguished indignation).</>
  <p>This is more than a hurt to us:  this hits at the
     decency of the whole nation!</p></sp>
]]>
</eg>

It might, however, also be treated simply as a quotation:

<eg>
<![ CDATA [
<sp><speaker>Kelly</> <stage>(calmly).</>
  <p>Aha, so you've bad minds along with th' love of gain.
     <!-- ... -->
  <stage>(He points, one after the other at Conroy, Bull,
     and Flagonson.  Lilting):</>
  <q><l>Who were you with last night?
     <l>Who were you with last night?
     <l>Will you tell your missus when you go home
     <l>Who you were with last night?
  </q>
</sp>
]]>
</eg></p>

<p>When an embedded structure extends across more than one <gi>sp</gi>
element, each of its constituent parts must be regarded as a distinct
fragment; the problem then facing the encoder is to reconstitute the
interrupted whole in some way.</p>

<p>As already noted above, the <att>part</att> attribute may be used to
indicate that an <gi>l</gi> element contains a partial, not a complete,
verse line.  The same attribute may be used on the <gi>lg</gi> element,
to indicate that the line group is partial rather than complete, thus:

<eg>
<![ CDATA [
<sp><speaker>Kelly</>
    <stage>(wheeling quietly in his semi-dance, as he goes out):</>
    <lg part=i>
        <l>Goodbye to holy souls left here,</l>
        <l>Goodbye to man an' fairy;</l>
    </lg>
</sp>
<sp><speaker>Widda Machree</>
    <stage>(wheeling quietly in her semi-dance, as she goes out):</>
    <lg part=f>
        <l>Goodbye to all of Leicester Square,</l>
        <l>An' the long way to Tipperary.</l>
    </lg>
</sp>
]]>
</eg></p>

<p>When the fragments of a song are separated by other intervening
dialogue, or even when not, they may be linked together with the
<att>next</att> and <att>prev</att> attributes defined in section
<ptr target="SAag">.  For example, the line groups making up Ophelia's song
might be encoded as follows:

<eg>
<![ CDATA [
<div1 type="act" n=4>
<!-- ... -->
<div2 type="scene" n=5>
<stage>Elsinore. A room in the Castle.</stage>
<!-- ... -->
<stage type="setting">Enter Ophelia, distracted.</stage>
<sp who="Oph"><speaker>Ophelia</speaker>
    <p>Where is the beauteous Majesty of Denmark?</p>
</sp>
<sp who="Qu"><speaker>Queen</speaker>
    <p>How now, Ophelia?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <stage>Singing</stage>
    <lg type=song ID="TL1" part=Y next=TL2 >
        <l>How should I your true-love know</l>
        <l>From another one?</l>
        <l>By his cockle hat and staff</l>
        <l>And his sandal shoon.</l>
    </lg>
</sp>
<sp who="Qu"><speaker>Queen</speaker>
    <p>Alas, sweet lady, what imports this song?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <p>Say you? Nay, pray you mark.</p>
    <stage>Sings</stage>
    <lg ID="TL2" part=Y prev=TL1>
        <l>He is dead and gone, lady,</l>
        <l>He is dead and gone;</l>
        <l>At his head a grass-green turf,</l>
        <l>At his heels a stone.</l>
    </lg>
    <p>O, ho!</p>
</sp>
<!-- ... -->
</div2>
</div1>
]]>
</eg></p>

<p>The <att>next</att> and <att>prev</att> attributes are discussed in
section <ptr target="SAag">:  they form part of the additional tag set
for alignment and linking, and are therefore not automatically available
to dramatic texts.  To enable this tag set as well as the base tag set
for drama, the document type declaration of a document might take the
following form:

<eg>
<![ CDATA [
<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
  <!ENTITY % TEI.drama   'INCLUDE'>
  <!ENTITY % TEI.linking 'INCLUDE'>
]>
]]>
</eg>

See chapter <ptr target="ST"> for general discussion of the way in which
TEI tag sets are enabled.</p>

<p>The fragments of Ophelia's song might also be linked together using
the <gi>join</gi> mechanism described in section <ptr target="SAag">.
The <gi>join</gi> element is specifically intended to encode the fact
that several discontiguous elements of the text together form one
<socalled>virtual</socalled> element.  Using this mechanism, the example
might be encoded as follows:

<eg>
<![ CDATA [
<text><body><div1 type="act" n=4>
<!-- ... -->
<div2 type="scene" n=5>
<stage type="setting">Elsinore. A room in the Castle.</stage>
<!-- ... -->
<sp who="Qu"><speaker>Queen</speaker>
    <p>How now, Ophelia?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <stage type="delivery">Singing</stage>
    <lg type=song ID="TL1" part=Y>
        <l>How should I your true-love know</l>
        <l>From another one?</l>
        <l>By his cockle hat and staff</l>
        <l>And his sandal shoon.</l>
    </lg>
</sp>
<sp who="Qu">
<speaker>Queen</speaker>
    <p>Alas, sweet lady, what imports this song?</p>
</sp>
<sp who="Oph">
<speaker>Ophelia</speaker>
    <p>Say you? Nay, pray you mark.</p>
    <stage type="delivery">Sings</stage>
    <lg ID="TL2" part=Y >
        <l>He is dead and gone, lady,</l>
        <l>He is dead and gone;</l>
        <l>At his head a grass-green turf,</l>
        <l>At his heels a stone.</l>
    </lg>
<p>O, ho!</p>
<join targets='TL1 TL2' type=lg>
</sp>
<!-- ... -->
</div2>
</div1></body></text>
]]>
</eg>
<!-- Suppressed N att on JOIN on the theory that N is for     -->
<!-- numbers or similar symbols, and 'True Love Know' does    -->
<!-- not qualify.  (msm)                                      -->

The location of the <gi>join</gi> element is not significant; here it
has been placed shortly after the conclusion of the song, in order to
have it close to the fragments it unifies.</p>

<p>Like the <att>next</att> and <att>prev</att> attributes, the
<gi>join</gi> element requires the additional tag set for linking, which
is selected as shown above.</p></div3>

<div3 id="DRsim"><head>Simultaneous Action</head>

<p>In printed or written versions of performance texts, a variety of
techniques may be used to indicate the temporal alignment of speeches or
actions.  Speeches may be printed vertically aligned on the page, or
braced together; stage directions (e.g. <q>Speaking at the same
time</q>) are also often used.  In operatic or musical works in
particular, the need to indicate timing and alignment of individual
parts of a song may lead to very complex layout.</p>

<p>One simple method of indicating the temporal alignment of speeches or
actions is to use the <att>corresp</att> attribute discussed in section
<ptr target="SAcs">, as in the following example:

<eg>
<![ CDATA [
<sp who="M"><speaker>Mangan</>
  <stage type="delivery">wildly</stage>
  <p>Look here: I'm going to take off all my clothes.</p>
  <stage type="action">he begins tearing off his coat.</stage>
</sp>
<sp who="LU" id=S1><speaker>Lady Utterword</speaker>
  <p>Mr Mangan!</p>
</sp>
<sp who="CS" id=S2><speaker>Captain Shotover</speaker>
  <p>Whats that?</p>
</sp>
<sp who="H" id=S3><speaker>Hector</speaker>
  <p>Ha! ha! Do. Do.</p>
</sp>
<sp who="E" id=S4><speaker>Ellie</speaker>
  <p>Please dont.</p>
</sp>
<stage id=D1 type="delivery" corresp="S1 S2 S3 S4">
  in consternation</stage>

<sp who="MH"><speaker>Mrs. Hushabye</speaker>
  <stage type="action">catching his arm and stopping him</stage>
  <p>Alfred: for shame! Are you mad?</p>
</sp>
]]>
</eg></p>

<p>In the original, the stage direction <q>in consternation</q> is
printed opposite a brace grouping all four speeches, indicating that all
four characters speak at once, and that the stage direction applies to
all of them.  In the example, the <gi>stage</gi> element has been moved
to an arbitrary place, and the four speeches with which it is to be
associated are specified by identifier as the value of the
<att>corresp</att> attribute.  This attribute, which is enabled by the
linking tag set, provides the simplest way of indicating the temporal
alignment of speeches or actions in a play.

<!-- I need help deciding how (or whether) to represent this -->
<!-- with the ALIGN element                                  --></p>

<p>More powerful and more precise mechanisms for temporal alignment are
defined in chapter <ptr target="TS">.  These would be appropriate for
encodings the focus of which is on the actual performance of a text
rather than its structure or formal properties.  The tag set described
in that chapter includes a large number of other detailed proposals for
the encoding of such features as voice quality, prosody, etc., which
might be relevant to such a treatment of performance texts.
</p>
</div3></div2>
<!-- With any luck, almost all the temporal alignment         -->
<!-- mechanisms should be moving to tagset SA / TEI.linking,  -->
<!-- but for now this note is retained. (msm)                 -->
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->
<!-- Revisions:                                               -->
<!-- 93-08-20 : MSM : fix typo before publication             -->
<!-- 93-08-19 : MSM : fix exx after parsing TESTDR.TEI        -->
<!-- 93-08-16 : MSM : suppress ref to CODE att on TECH (n'existe plus) -->
<!-- 93-08-16 : MSM : fix MS end problem                      -->
<div2 type=section id=DRoth><head>Other Types of Performance Text</head>

<p>Most of the elements and structures identified thus far are derived
from traditional theatrical texts.  Although other performance texts,
such as screen plays or radio scripts, have not been discussed
specifically, they can be encoded using the elements and structures
listed above.  Encoders may however find it convenient to use, as well,
the additional specialized elements discussed in this section.  For
scripts containing very detailed technical information, the
<gi>tech</gi> element discussed in section <ptr target=DRtec> may also
be useful.

<p>Like other texts, screen plays and television or radio scripts may
be divided into text divisions marked with <gi>div</gi> or
<gi>div1</gi>, etc.  Within units corresponding with the traditional
<q>act</q> and <q>scene</q>, further subdivisions or sequences may be
identified, composed of individual <q>shots</q>, each associated with
a single camera angle and setting.  Shots and sequences should be
encoded using an appropriate text-division element (i.e., a
<gi>div3</gi> element if numbered division elements are in use and the
next largest unit is a <gi>div2</gi>, or a <gi>div</gi> element if
un-numbered divisions are in use) specifying <code>sequence</code> or
<code>shot</code> as the value of the <att>type</att> attribute, as
appropriate.

<p>It is normal practice in screenplays and radio scripts to distinguish
directions concerning camera angles, sound effects, etc., from other
forms of stage direction.  Such texts also generally include far more
detailed specifications of what the audience actually sees:
descriptions of actions and background, etc.  Scripts derived from
cinema and television productions may also include texts displayed as
captions superimposed on the action.  All of these may be encoded using
the general purpose <gi>stage</gi> element discussed in section <ptr
target=DRsta>, and distinguished by means of its <att>type</att>
attribute.  Alternatively, or in addition, the following more specific
elements may be used, where clear distinctions can be made:

<list type=gloss>
<label><gi>view</gi></label>
<item>describes the visual context of some part of a screen play 
in
terms of what the spectator sees, generally independent 
of any
dialogue.</item>
<label><gi>camera</gi></label>
<item>describes a particular camera angle or viewpoint in a 
screen play.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>characterizes the camera angle in some respect, e.g. as a 
close-up, medium shot, etc.</item>
</list>
</item>
<label><gi>caption</gi></label>
<item>contains the text of a caption or other text displayed as 
part of
a film script or screenplay.</item>
<label><gi>sound</gi></label>
<item>describes a sound effect or musical sequence specified 
within a
screen play or radio script.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the sound in some respect, e.g. as music, 
special effect, etc.</item>
<label><att>discrete</att></label>
<item>indicates whether the sound overlaps the surrounding 
speeches or interrupts them.
Sample values include:
<list type=gloss>
<label><term>u</term></label>
<item>unknown or inapplicable</item>
<label><term>y</term></label>
<item>the sound is heard between the surrounding speeches</item>
<label><term>n</term></label>
<item>the sound overlaps the surrounding speeches</item>
</list></item>
</list>
</item>
</list>

<!-- dd notes that SOUND is not a good name for the tag: proposes SFX -->
<!-- or how about EFFECT? -->

<p>Some examples of the use of these elements follow:

<eg>
<![ CDATA [
<camera>Angle on Olivia.</camera>
<view>Ryan's wife, standing nervously alone on the sidelines,
biting her lip. She's scared and she shows it.</view>
]]>
</eg>

<p>Where particular words or phrases within a direction are emphasized
(by change of typeface or use of capital letters), an appropriate
phrase-level element may be used to indicate the fact, as in the
following examples, where certain words in the original are given in
small capitals:

<eg><![ CDATA [
<view>George glances at the window--and freezes.
<camera>New angle--shock cut</camera> Out the window
the body of a dead man suddenly slams into
<hi>frame</hi>. He dangles grotesquely,
held up by his coat caught on a protruding bolt.
George gasps. The train <hi>whistle</hi> screams.
</view>
]]>
</eg>
<!-- source? -->

<eg><![ CDATA [
<view>Ext. TV control van&mdash;Early morning.
The <name>T.V. announcer</name> from the Ryan interview
stands near the Control Van, the lake in b.g.
</view>
<sp who="announcer">
<speaker>T.V. Announcer</speaker>
<p>Several years ago, Jack Ryan was a highly
successful hydroplane  racer....</p>
</sp>
]]>
</eg>
<!-- source? -->

<p>All of these elements, like other stage directions, can appear both
within and between speeches.

<eg>
<![ CDATA [
<sp>
<speaker>TV Announcer VO</speaker>
<p>Working with Ryan are his two coworkers&mdash;
Strut Bowman, the mechanical engineer&mdash;
<view><camera>Angle on Strut</camera>
standing in the tow boat, walkie-talkie in hand,
watching Ryan carefully.</view>
&mdash;and Roger Dalton, a rocket
systems analyst, and one of the scientists
from the Jet Propulsion Lab....</p></sp>
]]>
</eg>

<eg><![CDATA [
<sp><speaker>Benjy</speaker>
  <p>Now to business.</p></sp>
<sp><speaker>Ford and Zaphod</speaker>
  <p>To business.</p></sp>
  <sound>Glasses clink.</sound>
<sp><speaker>Benjy</speaker>
  <p>I beg your pardon?</p></sp>
<sp><speaker>Ford</speaker>
  <p>I'm sorry, I thought you were
  proposing a toast.</p></sp>
]]>
</eg>
<!-- Hitch-hikers Guide, p.83 -->

<eg><![CDATA [
<camera>Zoom in to overlay showing some stock film
  of hansom cabs galloping past.</camera>
<caption>London, 1895.</caption>
<caption>The residence of Mr Oscar Wilde.</caption>
<sound>Suitably classy music starts.</sound>
<view>Mix through to Wilde's drawing room. A crowd of suitably
  dressed folk are engaged in typically brilliant conversation,
  laughing affectedly and drinking champagne.</view>
<sp who=TJ><speaker>Prince of Wales</speaker>
  <p>My congratulations, Wilde. Your latest play is a great success.
  </p></sp>
]]>
</eg>
<!-- Monty Pythons Flying Circus, vol 2, p 230 -->

<div3 type=subsection id=DRtec><head>Technical Information</head>
<!-- was: Prop plots and lighting scripts -->

<p>Traditional stage scripts may contain additional technical
information about such production-related factors as lighting,
<socalled>blocking</socalled> (that is, detailed notes on actors'
movements) or props required at particular points.  More technical
information about intended production effects may also appear in
published versions of screen plays or movie scripts.  Where these are
presented simply as marginal notes, they may be encoded using the
general-purpose <gi>note</gi> element defined in section <ptr
target=cono>.  Alternatively, they may be formally distinguished from
other stage directions by using the specialized <gi>tech</gi> element:

<list type=gloss>
<label><gi>tech</gi></label>
<item>describes a special purpose stage direction that is not

meant for the actors.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the technical stage direction.
Suggested values include:
<list type=gloss>
<label><term>sound</term></label>
<item>a sound cue.</item>
<label><term>light</term></label>
<item>a lighting cue.</item>
<label><term>prop</term></label>
<item>a prop cue.</item>
<label><term>block</term></label>
<item>a blocking instruction</item>
</list></item>
<label><att>perf</att></label>
<item>identifies the performance or performances to which this 
technical direction applies.</item>
</list>
</item>
</list>


<p>Like stage directions, <gi>tech</gi> elements can appear anywhere
within a speech or between speeches.

<p>The elements discussed in the section are formally defined as
follows:

<eg id=ddroth>
<![ CDATA [
<!-- 10.3.1:  Screen plays and other technical matters        -->
<!ELEMENT view          - O  (%specialPara)                     >
<!ATTLIST view               %a.global;                         >
<!ELEMENT camera        - -  (%paraContent)                     >
<!ATTLIST camera             %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT sound         - O  (%paraContent)                     >
<!ATTLIST sound              %a.global;
          type               CDATA               #IMPLIED
          discrete           (y | n | u)         u              >
<!ELEMENT caption       - O  (%paraContent)                     >
<!ATTLIST caption            %a.global;                         >
<!ELEMENT tech          - O  (%paraContent)                     >
<!ATTLIST tech               %a.global;
          perf               IDREFS              #IMPLIED
          type               (light | sound | prop | block) 
                                                 #IMPLIED       >
<!-- This fragment is used in sec. 10                         -->
]]>
</eg>

</div1>
<!-- *** end of P2 DR *************************************** -->
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->

             <!-- 10 Drama -->
