LISTSERV mailing list manager LISTSERV 16.0

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  April 2001

TEI-L April 2001

Subject:

Re: TEI and drama

From:

"C. M. Sperberg-McQueen" <[log in to unmask]>

Reply-To:

C. M. Sperberg-McQueen

Date:

Thu, 19 Apr 2001 08:10:25 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (170 lines)

At 2001-04-16 08:16, Tobin Nellhaus wrote:

 > So my main question is not so much whether TEI tags can be adapted
 > to fit the need -- by adding a tag set or in some other way
 > modifying the DTD, they certainly can -- and more whether TEI has
 > adopted the most suitable philosophical assumption in establishing
 > the existing drama tag set.  Perhaps an analogy within TEI would
 > help.  In theory the verse tag set could do without the line <l> and
 > line group <lg> tags, and instead use various combinations of
 > (slightly adjusted) <p> and <divn> tags -- but would you want to?
 > Imagine the conceptual contortions one would have to go through if
 > those tags were missing.  Imagine the protests from encoders of
 > verse!  It was my understanding that, even though encoders often
 > modify DTDs, the tag sets are meant to cover the concepts of
 > structure that are most basic to each genre (plus a few that are
 > more unusual), and that's for reason the plethora of tags.

The concepts which are most basic, or the concepts which are most
clearly agreed on.  Remember that 'basic' does not necessarily mean
'most fundamental'; it may mean only 'unavoidable'.  You suggest that
the TEI drama tag set is better suited for describing the text than
the performance; I think that's probably a fair assessment of the DTD
without any extensions.

There are several plausible reasons one might assign for this:

   - it's relatively clear how to represent the text, and the
     tradeoffs among choices are reasonably well understood; it is much
     less clear and there was much less consensus about how to
     represent aspects of a particular performance, or even what
     aspects of a performance are most often likely to be recorded by
     those with an interest in performance (blocking? sentence
     intonation? length of pauses?  lighting cues? synchronization with
     a videotape or audio recording?  contents of the stage manager's
     copy of the script?  lighting booth copy? director's copy? ...)

   - the best way to represent a performance in linear forms depends
     on what you want to do with the representation

   - those interested in the drama (which I take as the name of a
     literary genre) need the text, not the performance, while those
     interested in the performance will often (perhaps usually) need
     both a representation of the text and a representation of the
     performance

   - the TEI currently does best with written artifacts

   - the TEI currently does best with abstractions of written
     artifacts (it does less well with the physical description
     of text carriers)

There are also some implausible reasons (by 'implausible' I mean I
think they are false):

   - the text is more important than the performance

   - the text is not intrinsically more important than the
     performance, but the creators of the TEI tag set for drama thought
     that it was

   - the creators of the TEI wanted to discourage the study of
     theatrical performance

   - the creators of the TEI thought written artifacts were the
     only important thing, or that linguistic objects were the
     only important thing

You may well be right that some fundamental change of assumptions
would be the most helpful way of developing a way to represent
performance information.  Even if you are not right about this in the
general case, you may well be right in feeling that the assumptions
made in the TEI drama tag set are not congenial to your point of view,
or even that they are in flat contradiction to it -- in this case it
is not only your prerogative, but also (some would say) your
intellectual responsibility to design a tag set that reflects the
assumptions you believe are fundamental.  And I believe anyone who
regularly reads this list will be very interested to see what you come
up with. (And, for what it is worth, assuming that you document your
DTD properly and provide a header, you can claim that the result is
TEI-conformant.)

I would suggest, however, that any attempt to represent a performance
which does not manage to represent the script is likely to be
problematic for many purposes.  It is in this sense that the tags in
the drama tag set represent 'basic' information.

 > In other words: *Can* these documents be marked up just by
 > using/adding existing tags? Yes, although with a bit of difficulty
 > and possibly with some maltreatment of the TEI guidelines.  But
 > *should* it be done that way?  I don't think so -- not when looking
 > at something that is a normal and *essential* part of drama, even if
 > completely unrepresented in the ordinary published script.

I'm not sure I understand what you mean -- prompt books and so on are
a normal part of modern Western European theatrical practice (and
possibly of theatrical practice in other cultures as well), so I
suspect you are using "drama" here as a synonym for "theatrical
performance" or even "literary works destined for theatrical
performance".  The term "drama" does get used more broadly, and drama
(qua literary genre) can certainly exist without performance and thus
without prompt books.  The absence of prompt books for any performance
of Tolkien's verse play about the battle of Maldon does not seem to
mean that it is not drama.  It does means the play has never been
performed. The absence of prompt books for the few chapters of Moby
Dick which are written in dramatic form doesn't mean that they aren't
in dramatic form; it only means they aren't performed or (in the usual
sense of the word) performable.

But my reservations about your statement are a side issue.  You seem
to be working yourself up to the conclusion that tagging prompt books
might require you to add new elements and attributes to the DTD, and
you seem (a) to be unhappy with the conclusion and (b) to believe that
it is best motivated by the view that the TEI has missed something
essential.  I think you are making heavier weather of this than you
need to. It can be desirable or even necessary to extend the TEI DTD,
even without the DTD having missed something essential.  (In the Model
Editions Partnership, for example, the 'hi' element is supplemented by
specific elements for underlining, italics, bold, and small caps.
Nothing essential was missing from the TEI DTD, but having distinct
elements helped make the MEP data capture DTD somewhat more convenient
for editors.)

 > (Likewise, not all poems use stanzas or have line segments, but the
 > <lg> and <seg> tags are considered a normative part of the verse
 > set.)  Bear in mind that I'm suggesting the need for only a handful
 > of new tags, which is not much in the TEI world.

As Syd Bauman has succinctly said, there is nothing wrong with
extending the TEI DTD.  The DTD is designed to be extended, and a fair
bit of work went into the design of the extension mechanisms.  As Syd
points out, even TEI P3 uses the extension mechanism -- in part to
underscore the idea that there is nothing wrong with extending the
DTD.

You may, if you wish, harbor the thought that if the designers of the
DTD had only done their jobs RIGHT, no extensions would be necessary,
and thus that any extension identifies a place where a mistake has
been made, but you will have a hard time persuading some of us.
Opportunities for improvement in a future revision, yes.  Mistakes,
maybe but not necessarily. One of the key axioms of the TEI design is
that "No markup language with a finite vocabulary can be complete" in
the sense of handling equally well all texts from all periods and
languages, for all different scholarly or non-scholarly purposes.  It
follows as a consequence that "in order to be generally useful a
markup language must be extensible." (L&LC 6 (1991): 36).

If I were tagging stage managers' books as I was taught to make them,
I would almost certainly add specialized element types for lighting
cues and sound cues and "WARN RAFI" and the like.  But I would be
puzzled by any suggestion that this would tell us much about any
particular *performance* of the play.  The prompt book, alas, does not
tell us whether the seagull cries actually came in at the right
moment, or after too long a pause.  (And the note "WARN RAFI" becomes
relevant to the audience's perception of the performance only when the
stage manager fails to perform the task and Mrs. Rafi misses her
entrance.)  At best the prompt book tells us about a production, not
about a performance.  And it's quite a narrow view at that.

As you foresee, and as Wendell Piez has confirmed, you are going to
face quite a challenge in handling synchronization (light cues that
cover three and half speeches) and dramaturgical revision of the text.
Some of the techniques in Barnard et al. 1995 may come in handy; those
in the chapters on synchronization and alignment and manuscript
transcription may also be useful.  Some specialized elements may make
the tagging more convenient.  But overlap is hard to tag in SGML
and XML in ways that are both convenient and easily processable.

Good luck.

-C. M. Sperberg-McQueen

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994
December 1993
November 1993
October 1993
September 1993
August 1993
July 1993
June 1993
May 1993
April 1993
March 1993
February 1993
January 1993
December 1992
November 1992
October 1992
September 1992
August 1992
July 1992
June 1992
May 1992
April 1992
March 1992
February 1992
January 1992
December 1991
November 1991
October 1991
September 1991
August 1991
July 1991
June 1991
May 1991
April 1991
March 1991
February 1991
January 1991
December 1990
November 1990
October 1990
September 1990
August 1990
July 1990
June 1990
April 1990
March 1990
February 1990
January 1990

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager